Related
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).
ellesshoo said:
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).
Click to expand...
Click to collapse
there really is no measurable risk. the only difference is that you cant use fastboot but you can use alternatives to that (you dont need to worry about this)
most people unlocked the bootloader because the method to root without unlocking was just discovered recently.
I did the root without unlock a few days ago, as far as I can tell I can do it all and I do not get the unlocked icon. I have custom recovery, custom ROM, using root only apps like metamorph, titanium backup, etc. Best decision I have made. This phone is amazing.
Sent from my Nexus One using XDA App
Where are the instructions for doing so? I am an Android noob and just got the Nexus after the iPhone. I am kinda worried about bricking it if I root. Plus the only reason I want to root is because I hear that after that you are able to save all your apps to the SD card instead of the phone. If i was able to do that without rooting, I would be happy, but that's the only reason why i would like to do that.
phone_fanatic said:
Where are the instructions for doing so? I am an Android noob and just got the Nexus after the iPhone. I am kinda worried about bricking it if I root. Plus the only reason I want to root is because I hear that after that you are able to save all your apps to the SD card instead of the phone. If i was able to do that without rooting, I would be happy, but that's the only reason why i would like to do that.
Click to expand...
Click to collapse
froyo lets you do this....but it still takes up a lot of space on the phone (i was full after only 200 total apps)
the tutorial is stickied in the android development section of this forum
That's the thing though, I do have Froyo. However not all apps allow me to select that 'Move to SD card' setting for some reason. Some of the apps it's just greyed out and it isn't clickable. Out of say 10-11 apps, only 3 had that option available and I was able to move them to the SD card.
phone_fanatic said:
That's the thing though, I do have Froyo. However not all apps allow me to select that 'Move to SD card' setting for some reason. Some of the apps it's just greyed out and it isn't clickable. Out of say 10-11 apps, only 3 had that option available and I was able to move them to the SD card.
Click to expand...
Click to collapse
its because app devs have to allow to install it that way. if you want to force it, use adb to do the following
adb shell
pm setInstallLocation 2
So if the developers will be implementing it soon enough then why rush it right? I mean I don't mind waiting....as long as all the app developers will be doing it sooner or later?
Hi all,
I am supposed to receive my nexus 7 tomorrow.
I just cant decide on whether I should root or no.
I can say for sure that I do not plan to change roms, I only want to root in order to use storage via usb-otg (also not sure I will use it eventually).
I do know that I want to receive OTA updates and that's why I don't like the idea of rooting.
Any suggestions?
Thanks a lot!
Asaf
Yes you should root it if you want to use usb-otg. I decided not to root mine on day one and now I'm looking for a method that won't erase everthing on my device. So if you see yourself needing that in the future do it now rather than later .
shemsha said:
Hi all,
I am supposed to receive my nexus 7 tomorrow.
I just cant decide on whether I should root or no.
I can say for sure that I do not plan to change roms, I only want to root in order to use storage via usb-otg (also not sure I will use it eventually).
I do know that I want to receive OTA updates and that's why I don't like the idea of rooting.
Any suggestions?
Thanks a lot!
Asaf
Click to expand...
Click to collapse
This is a Nexus device which makes to easy to root and unroot..
If an OTA comes out you can be unrooted and back stock in a matter of minutes..
Oddly, I have had no reason or desire to root my N7 and I even put my GNex back stock...
If you do root, do it before you install all kinds of stuff. You have to reset to root. Not sure how the Google credit works, but you might want to register the device, get the credit, then root. Just in case.
Sent from my Nexus 7 using Tapatalk 2
I was reluctant to root or not. CM10 is only a preview, other roms not much better than stock, I don't need OTG, so why root? For one crucial app: TITANIUM BACKUP. When you unlock and root everything is wiped!
My suggestion is unlock the bootloader right away since that part wipes data, then root when (and if) you decide to download an app that needs root access.
Easier to Root now rather than later. Rooting requires you to wipe losing all apps and settings.
Sent from my Nexus 7 using Tapatalk 2
Yes. First thing I always do on a Nexus device is unlock and root. It's just as easy to lock it again and flash the stock rom if ever needed.
I would unlock the bootloader at a minimum, before you set anything up, as that action will wipe data. If you decide to root later on you'll be in great shape.
Sent from my ADR6400L using Tapatalk 2
Might be better to wait and see if any problems arise with the device first?
I rooted mine using the One click root tool, very easy.
Got to be worth it to install ad block and sixaxis.
Like others have said, at the very minimum, unlock the bootloader (a prerequisite for rooting) right away. If you decide to unlock it later you'll have to wipe the device.
Absolutely. Just make sure you bookmark (in the cloud) how to unroot before you root (including restoring stock bootloader). It would also be smart to read what issues other folks have had, and what they did to solve their problems. (In short, always have a concrete, detailed exit plan before you start something.)
Sent from my ThinkPad Tablet using Tapatalk 2
shaneydroid said:
Might be better to wait and see if any problems arise with the device first?
Click to expand...
Click to collapse
That is an excellent point I am very anzy ( think I killed that word) to unlock and root but I want to give it atleast a week to make sure there are no kinks, dead pixels or anything that would require me to return it but so far so good on my first day. I bought Titu with the $25 credit forgetting that it requires root lol but it's all good becuase now I have it for my Vivid but to use six axis you need root as well.
shaneydroid said:
Might be better to wait and see if any problems arise with the device first?
Click to expand...
Click to collapse
clago87 said:
That is an excellent point I anzy ( think I killed that word) to unlock and root but I want to give it atleast a week to make sure there are no kinks, dead pixels or anything that would require me to return it but so far so good on my first day. I bought Titu with the $25 credit forgetting that it requires root lol but it's all good becuase now I have it for my Vivid but to use six axis you need root as well.
Click to expand...
Click to collapse
Other than checking out the basic functions, I wouldn't bother waiting. The device is designed to be unlocked so it is not a hardware warranty issue and that is what you would be returning the device for. If you plan on having root, you need root to test the things you will be using it for.
Plus, it then allows you to back up the device so that if you do have to get another one, it is a very simple process to restore your backup and be back up and running (one of the primary reasons for root)
krelvinaz said:
Other than checking out the basic functions, I wouldn't bother waiting. The device is designed to be unlocked so it is not a hardware warranty issue and that is what you would be returning the device for. If you plan on having root, you need root to test the things you will be using it for.
Plus, it then allows you to back up the device so that if you do have to get another one, it is a very simple process to restore your backup and be back up and running (one of the primary reasons for root)
Click to expand...
Click to collapse
I am actually glad to be at work for once. I am very easily swayed and am ready to unlock and root lol. I have read all the info on it and it does not seem too much of a burden compared to my atrix
I'm kind of confused, do I unlocked the bootlocker first or install 4.1.1 updates?
If I install then unlock, would the updates be gone?
Would I be able to update even after unlock and root?
i rooted even though i had already installed apps etc... its very handy to be able to use external storage and apps like titanium backup.. i dont really intend installing customs roms.. but the otg support was enough to warrant rooting for me
You can backup and restore your device with ADB. Backup, unlock, restore. You don't have to lose everything to root it later on.
hydroxyde said:
You can backup and restore your device with ADB. Backup, unlock, restore. You don't have to lose everything to root it later on.
Click to expand...
Click to collapse
Yep was just about to say this, picked this method up in the OneX forums, life saver
Sent from my Nexus 7 using xda premium
Ever since I've rooted my Moto G 2nd Gen (Consumer Cellular) with Kingroot it has been starting to take a full 5-7 minutes just to boot up. The weird part of it is that the device reboots itself automatically 3 times just to finally boot to the OS. I have no clue of what's going on at the moment, but this is an incredibly irritating issue. Any thoughts? Any help will obviously be appreciated.
Who did you tell to use some rooting tool like Kingroot or whatever?
To root your Moto G you have to unlock your bootloader on Motorola page,flash or boot into custom recovery (TWRP) and then flash latest super SU from there.
Or after unlocking use chainfires autoroot.
All this you can read here:
http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Never use some rooting tool when it´s not recommended...
Wolfcity said:
Who did you tell to use some rooting tool like Kingroot or whatever?
To root your Moto G you have to unlock your bootloader on Motorola page,flash or boot into custom recovery (TWRP) and then flash latest super SU from there.
Or after unlocking use chainfires autoroot.
All this you can read here:
http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Never use some rooting tool when it´s not recommended...
Click to expand...
Click to collapse
Thanks.
I have the same problem anyone know what causes this long boot time? The kingroot works great in every other way and no need for unlocking boot loader or even the need for a pc making it a very easy option. Any experience of this root method from anyone here?
xs1m0nx said:
I have the same problem anyone know what causes this long boot time? The kingroot works great in every other way and no need for unlocking boot loader or even the need for a pc making it a very easy option. Any experience of this root method from anyone here?
Click to expand...
Click to collapse
That's an awful way to root and frankly almost if not impossible to do. This phone needs to be unlocked to root and anything other than that way is bound to fail.
Well that's not the case it does not fail it works great with just a small issue of longer boot time. Far from being an awful way it's actually a brilliant way as it makes it so easy for people with minimum fuss. What I'm really looking for is some constructive information from someone who has good knowledge of this root method. The boot time is not really a big deal I'm just interested to know why it does this.
xs1m0nx said:
Well that's not the case it does not fail it works great with just a small issue of longer boot time. Far from being an awful way it's actually a brilliant way as it makes it so easy for people with minimum fuss. What I'm really looking for is some constructive information from someone who has good knowledge of this root method. The boot time is not really a big deal I'm just interested to know why it does this.
Click to expand...
Click to collapse
Well have at it. It's obviously a poor choice as you'll eventually discover. Some people just look for ways to fail.
I think it's more people look for new ways and that's not a bad thing. Everything moves on and what was not possible to do becomes possible. Yes it maybe true that there can be problems but there are few that can't be overcome. Every method was unknown and risky as some point but that's just how it will always be. You got to admit kingroot have done what everyone said was impossible so that's pretty clever of them. Hopefully someone a lot more clever than me will work out about the little side effect in time.
Update: Tel864 is quite right although this does root your phone it causes problems with boot that just get worse over time. I've flashed stock back on mine I'll probably re root but with the recommended method so yes I retract all the above!
What scares me about Kingroot is the fact that it's just a collection of exploits that forces changes to the bootloader. It sort of goes against the very thing that makes Android safer.
Sent from my GT-P5210 using Tapatalk
Yes your right and I imagine eventually may brick the phone. I have rooted the proper way now and installed a custom ROM so ended up with a much better situation.
Sent from my Moto G 2014 using Tapatalk
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
jsmithfms said:
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
Click to expand...
Click to collapse
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
KennyG123 said:
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
Click to expand...
Click to collapse
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Honestly for the time being I wouldn't bother with ROMS for that Device and carrier at the moment. Especially being that its someone elses device. Towelroot should be a good start. If Im not mistaken I don't think its supposed to trip knox.
Sent from my HTCEVODesign4G using XDA Free mobile app
jsmithfms said:
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Click to expand...
Click to collapse
This is the riddle of the Sphinx my friend. I am sure the super devs have tried their best so far to crack it. It has been an ongoing effort to make phones more and more secure, not against the amateur developers and rooters, but against the hackers. These smartphones are now our personal computers, diaries, personal assistants, financial operator, and more. They basically are a person's (and business's) life. AT&T and Verizon have taken the big steps to appeal to the Exchange clients, corporate, government and military contracts. Even the general public want to know their phone is secure. This is what keeps me stuck on the Sprint network.
Have you tried Kingroot?
I successfully rooted my wife's AT&T S4 on OC3 lollipop (supposedly unrootable) with the desktop version. Mobile version didn't work but desktop did without a hiccup. Maybe it'll work on the S5.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
S5 on lollipop has a new nasty boot loader.... it was a miracle on its own that they ever came up with safestrap to duck the boot loader on earlier versions of android
Hi, long time lurker here. I want to start by saying how great and informative this site is. Anyway, my nexus 6 came in from the mail like 5 hours ago, did all the updates from 5.0 to 6.0 and it's now running Marshmallow mra58n. Question is should I root it immediately and if so, are there any guides I can follow? Much love to you all, I'm not exactly pro at this kind of things but I can follow instructions since I have competently rooted my past phones which were an HTC M7, M8 and a Samsung Galaxy Note 10.1 tablet.
Thank you.
Edit: Phone is also unlocked, I currently have no SIM card
start here..
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've been looking at the Nexus Root Toolkit since I am kind of confused on how to proceed with anything at all, is that ill advised since I've read that there are problems with the USB cable disconnecting during reboot?
Also, thank you for the reply.
I used the NRT without issue. Just follow the guide step by step.
Sent from my Nexus 6 using Tapatalk
and, dont touch the usb cable while the phone is processing your commands!
j/k, never even heard of the USB cable "problem"
I just used the toolkit today to unlock and root my N6.
Sent from my Nexus 6 using Tapatalk
I rooted last night initially using manual method described in the first link provided, however after some driver issues ultimately used the 2.1.0 rootkit to uninstall and reinstall all drivers. That too alone saved me tons of time and either method is simple if you can follow instructions.
Totally recommend rooting and then experimenting with custom roms, its like getting a new phone everyone you install a new rom.
Have fun!
Kristine,
In answer specifically to your question "Should I...?" my answer is "No". It really depends on what you think you'll get from it - why do you want to do it? What specific benefits do you want?
The reason that I say "no" is that I've been rooted on all my several phones for years, and I've decided that for me the annoyance of having to manually flash ROMs outweighs the benefits - particularly now that Google are releasing frequent security updates. The moment you root your device the OTA (over the air) updates no longer work.
For me the major reason for rooting was to have a firewall. The other things (wakelock detection, double tap to wake, auto-hibernation...) were great but not showstoppers. Now that there is a non-root firewall (Netguard) I'm happy to leave my phone unrooted. I haven't had an OTA to apply yet, so if I have any problems then I might change my mind, but my advice would be to think hard about why you want root before you buy yourself into a world of tinkering...
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Dammit, are you kidding me? I just downloaded and setup everything, figured I'd do all everything else tomorrow... Oh, well I can do it again I suppose.
Kristine-N said:
Question is should I root it immediately....
Click to expand...
Click to collapse
Because I don't want a white interface, rooting is necessary. Google forces to many things, like forced encryption, useless apps and a white interface (battery drain). When rooting was impossible I would not have bought a Nexus.
Short answer: No!
Long answer: Well, it's sill no, but you can or even should do a couple of things.
First if all, allow OEM Unlocking in development settings. There are gazillion how-tos to switch developer mode on, and tick that switch. Google has borked OTAs already, and if your phone doesn't boot, and the switch is off, then you're boned, you can send it for repair. But if you can unlock you bootloader, then you can flash a custom recovery and make your phone working again.
Second, if you do plan to root your phone in the near future, you should unlock the bootloader now, while it's still new, because it will erase everything (IMHO this would be sufficient as a security measure, the Enable OEM Unlocking is overkill).
As for the main question if you don't have any specific ideas what you want the root for, then don't root your phone. It's a clear and present security risk, and you're just one too many "Allow" taps from letting someone acquire your passwords, clone your IMEI, and download your personal stuff. My motto is, if you don't know what exactly root is, what it does, then you don't know how to prevent exploits that need it to run.
Also if you modify your phone in any way, and that includes rooting, you won't receive the monthly OTAs, and will have to flash it manually.
And finally, don't use toolkits on a Nexus. Spend another hour reading about the matter and you will find out typing adb and fastboot commands is a easy as clicking buttons on toolkits. There is nothing extra in them, they just download the images to flash, and "type" these commands for you.
Unlock bootloader and don't root it for now. After some time, if you feel like you're missing some features that you can obtain only with root, then go ahead. But for now I would strongly recommend to stay stock and see how it goes...