Related
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Cf auto root does not remove all data per se, but unlocking your phone will if it is not.. And it's part of the process.
Rooting probably doesn't affect OTAs, and if it does, can easily be undone.
Yes, I haven't found a common root app that isn't compatible.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
1. No it does not wipe your data unless your bootloader was locked.
2. It has no effect. You'll be able to accept the OTA and lose root (you can enable a survival script).
3. Yes.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
zephiK said:
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
Click to expand...
Click to collapse
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
TheSkillfulTroll said:
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
Click to expand...
Click to collapse
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
For information sake (I have already rooted via TK) your post actually does prove a point. For myself and maybe others, would you be willing to P.M me the instructions to do it via ADB/Fastboot just in case , I , myself get screwed over. Thanks Z
Sent from my Nexus 6 using XDA Free mobile app
flash you phone manually you will learn a lot about how the toolkits work.
I find it faster to flash manually than to use a tool kit.
once an OTA is available you can grap the image from the google site and flash the files manually.
There is a way to manually flash you phone and save userdata so you keep all your apps.
One you learn and get a little practice It will be so easy you will be able to flash like it is second nature. (I was a noob that came from iphone and jailbreaking)
I can actually flash the files manually faster that an OTA can update a phone and I type with maybe a total of 6 fingers. because i never took a typing class
zephiK said:
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Sent from my Nexus 6 using XDA Free mobile app
if you have drivers installed already from first link above then you can follow these steps:
Download the required factory image files to your computer and extract them
1) Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
2) If all you want to do is unlock your bootloader, skip to step 6 in this section.
3) Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
4) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
5) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
6) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
7) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu just cd to the directory.
Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-some-description-number.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot format cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
I'm not the original writer of these instructions, but I found these helpful to people wanting the step by step instructions.
TheSkillfulTroll said:
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Click to expand...
Click to collapse
Read the first couple of posts of the following threads. The first talks about how to root, and the other, about how to flash the factory images. Very detailed.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
How true. I certainly don't want a paper weight...
Larzzzz82 said:
How true. I certainly don't want a paper weight...
Click to expand...
Click to collapse
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
zephiK said:
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
Click to expand...
Click to collapse
I agree the hardest part for me was on windows trying to get the stupid drivers to work correctly.
Dumped windows for Linux and followed the manual steps i found on XDA and never looked back.
No drivers needed in Linux either.
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah ok, this is what i was looking for.
miike1106 said:
Ah ok, this is what i was looking for.
Click to expand...
Click to collapse
Or... You could live dangerously and try a dirty flash first every time... Worst case... You go back and wipe in recovery
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
You can dirty flash but this is only the case when you update from the same ROM to a newer update of the version.
When we say wipe, it only wipes the OS not internal storage.
I am on my. Way to return the phone to best buy. I was rooted and with an unlocked bootloader and had TWRP. I used the Nexus Toolkit and relocked the phone before flashing stock and now it won't boot. It just shows the team win logo flashing over and over. Please please help as they close in 30 minutes. Also it isn't detected in adb or fast boot.
EDIT: fixed it!
I am at this same point. How did you fix it?
chris23445 said:
I am on my. Way to return the phone to best buy. I was rooted and with an unlocked bootloader and had TWRP. I used the Nexus Toolkit and relocked the phone before flashing stock and now it won't boot. It just shows the team win logo flashing over and over. Please please help as they close in 30 minutes. Also it isn't detected in adb or fast boot.
EDIT: fixed it!
Click to expand...
Click to collapse
TheAnarchist1 said:
I am at this same point. How did you fix it?
Click to expand...
Click to collapse
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
ADB is your friend!
TheAnarchist1 said:
I am at this same point. How did you fix it?
Click to expand...
Click to collapse
Hold the power and volume down button until it boots into recovery. Then plug the phone into your computer. Download the stock 5.0.1 zip (luckily I already had it downloaded). Use the toolkit and unlock the bootloader. It will say its successful but the phone will boot loop again. Boot into recovery and should say the bootloader is unlocked. Then flash the stock zip file and it should work! I had to figure it all out as I went because I couldn't figure it out online lol.
radicalisto said:
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
To be fair, I was in a huge rush and relocked the bootloader before flashing stock. Totally a user error and not a toolkit error.
Boot loops
radicalisto said:
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
Or, the moral is follow the toolkit developer's directions.......
aiiee said:
Or, the moral is follow the toolkit developer's directions.......
Click to expand...
Click to collapse
Yep. That/don't rush when resetting the phone and do it in the wrong order.
aiiee said:
Or, the moral is follow the toolkit developer's directions.......
Click to expand...
Click to collapse
No, it isn't because...
chris23445 said:
I had to figure it all out as I went because I couldn't figure it out online lol.
Click to expand...
Click to collapse
but if a toolkit had never been used in the first place, there would be nothing to figure out as it would all have been learned in the rooting process.
rootSU said:
No, it isn't because...
but if a toolkit had never been used in the first place, there would be nothing to figure out as it would all have been learned in the rooting process.
Click to expand...
Click to collapse
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
chris23445 said:
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
Click to expand...
Click to collapse
Thus proving my point.
radicalisto said:
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
rootSU said:
Thus proving my point.
Click to expand...
Click to collapse
Not in the slightest . Your analysis is flawed. You assume this problem was caused by not understanding the underlying structure but it wasn't. It was caused by failing to follow directions. Which would have caused him problems had he used ADB or not.
aiiee said:
Not in the slightest . Your logic is skewed. Good luck with that.
Click to expand...
Click to collapse
How is it skewed? If, when he first got his phone, he unlocked and rooted in the normal way and not used a toolkit. He would have known how to use fastboot, including how to flash stock and lock the boot loader. He would not have used a toolkit today and wouldn't have used the wrong order and this thread wouldn't exist.
If you're an advocate for the cheat way and the way that makes it harder for us to help people, so be it. But 95%.of us prefer users to learn things properly and not become a burden to the forum. But you can help them all. Good luck with that.
chris23445 said:
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
Click to expand...
Click to collapse
how to properly root.
1. run the command "fastboot oem unlock" in fastboot. this unlocks your bootloader.
2. flash a custom recovery via fastboot.
3. flash the latest supersu in your new recovery.
4. reboot with root.
5. woohoo!
this takes about 3-5 minutes.
aiiee said:
Which would have caused him problems had he used ADB or not.
Click to expand...
Click to collapse
Adb is absolutely nothing to do with any of this. Another misconception of toolkit users. Which again, proves my point.
aiiee said:
Not in the slightest . Your analysis is flawed. You assume this problem was caused by not understanding the underlying structure but it wasn't. It was caused by failing to follow directions. Which would have caused him problems had he used ADB or not.
Click to expand...
Click to collapse
you dont use adb to root. nor will adb work while you are in the bootloader. fastboot is what you use
simms22 said:
you dont use adb to root. nor will adb work while you are in the bootloader. fastboot is what you use
Click to expand...
Click to collapse
You can use adb. Fastboot is used for the oem i lock and recovery flash. If you want to put the supersu file on the phone without downloading it on the phone you can just adb push and flash in recovery. Done.
Thanks
chris23445 said:
Hold the power and volume down button until it boots into recovery. Then plug the phone into your computer. Download the stock 5.0.1 zip (luckily I already had it downloaded). Use the toolkit and unlock the bootloader. It will say its successful but the phone will boot loop again. Boot into recovery and should say the bootloader is unlocked. Then flash the stock zip file and it should work! I had to figure it all out as I went because I couldn't figure it out online lol.
To be fair, I was in a huge rush and relocked the bootloader before flashing stock. Totally a user error and not a toolkit error.
Click to expand...
Click to collapse
Thanks for the clear explanation.:good:
@rootSU
For those curious. I figured I would check back in with this thread. I did not use a toolkit to begin with. I have the sdk properly set up and know my fastboot and adb commands and the difference between both. What I did:
1. Fastboot oem unlock
2. Fastboot flash recovery recovery.img (it was twrp)
3. Booted into recovery and it would not let me access the recovery, just kept flashing the TWRP splash over and over and over.
The issue I think for me, was that I did not wait until the Nexus had wiped itself and booted back into Android to rebuild the file system. Hence TWRP farting out. I simply started from scratch again, flashed all the proper stuff that was needed and followed steps, and I was alright after that.
I have since returned the device though and exchanged it with a new Nexus 6, because my back cover had started to pop up in the top right corner above the power and volume buttons....but THAT is another story for another thread : p
Cheers all!
PS: It has been a while since I have owned a Nexus device, hence my own failure to follow the rules. Things have changed a bit with this Nexus it seems, and it was my fault. I am all good now though (or I will be after I set up this new Nexus 6)
PSS: No toolkits were used, or will ever be used in the creation and resolution of this debacle. My life is hard enough without blindly wandering through the forest of Android customization with my hand held by a complete stranger.
: p
TheAnarchist1 said:
@rootSU
For those curious. I figured I would check back in with this thread. I did not use a toolkit to begin with. I have the sdk properly set up and know my fastboot and adb commands and the difference between both. What I did:
1. Fastboot oem unlock
2. Fastboot flash recovery recovery.img (it was twrp)
3. Booted into recovery and it would not let me access the recovery, just kept flashing the TWRP splash over and over and over.
The issue I think for me, was that I did not wait until the Nexus had wiped itself and booted back into Android to rebuild the file system. Hence TWRP farting out. I simply started from scratch again, flashed all the proper stuff that was needed and followed steps, and I was alright after that.
I have since returned the device though and exchanged it with a new Nexus 6, because my back cover had started to pop up in the top right corner above the power and volume buttons....but THAT is another story for another thread : p
Cheers all!
PS: It has been a while since I have owned a Nexus device, hence my own failure to follow the rules. Things have changed a bit with this Nexus it seems, and it was my fault. I am all good now though (or I will be after I set up this new Nexus 6)
PSS: No toolkits were used, or will ever be used in the creation and resolution of this debacle. My life is hard enough without blindly wandering through the forest of Android customization with my hand held by a complete stranger.
: p
Click to expand...
Click to collapse
after fastboot oem unlock, you have to reboot once before flashing the recovery. rarely it doesnt stick, so you just flash it again if nothing appears
I am on VZW. My phone status was "UNLOCKED" upon arrival from Moto. Since then, I found that the status has changed to "LOCKED". The status has not changed back to "UNLOCKED" after a factory reset. I have neither unlocked the bootloader or rooted.
Does the status refer to the bootloader, or did my phone lock to the carrier. Either way, is there a way to return the status to "UNLOCKED"?
gmermel said:
I am on VZW. My phone status was "UNLOCKED" upon arrival from Moto. Since then, I found that the status has changed to "LOCKED". The status has not changed back to "UNLOCKED" after a factory reset. I have neither unlocked the bootloader or rooted.
Does the status refer to the bootloader, or did my phone lock to the carrier. Either way, is there a way to return the status to "UNLOCKED"?
Click to expand...
Click to collapse
Are you talking about the status in the bootloader?
If you want to unlock your bootloader there are a few guides on here to show you how.
skaforey said:
Are you talking about the status in the bootloader?
Click to expand...
Click to collapse
I am on the recovery screen itself. Before moving to the bootloader screen.
gmermel said:
I am on the recovery screen itself. Before moving to the bootloader screen.
Click to expand...
Click to collapse
Bootloader comes before recovery. The screen where you pick to boot to recovery, is the bootloader. Is this where you mean?
rootSU said:
Bootloader comes before recovery. The screen where you pick to boot to recovery, is the bootloader. Is this where you mean?
Click to expand...
Click to collapse
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
gmermel said:
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
Click to expand...
Click to collapse
well, when verizon finally releases, it might be sim locked. but you bought from motorola directly, and wont be sim locked to verizon, ever.
gmermel said:
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
Click to expand...
Click to collapse
The phone shouldn't have come unlocked from the factory. I suggest you backup your data and oem unlock the phone.
How do do an oem unlock?
gmermel said:
How do do an oem unlock?
Click to expand...
Click to collapse
Using fastboot commands you type fastboot OEM unlock to unlock your bootloader. This will wipe all of your data so you should back up anything you don't want to lose.
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
encephalon9986 said:
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
not really. the right way is the easiest way, and you learn along the way. using a toolkit, you will learn nothing, not even the basics. the right way to do it takes about 3-5 minutes..
1. fasdtboot oem unlock(this unlocks the bootloader)
2. fastboot flash a custom recovery
3. flash supersu in your new recovery
4. reboot with root.
simms22 said:
not really. the right way is the easiest way, and you learn along the way. using a toolkit, you will learn nothing, not even the basics. the right way to do it takes about 3-5 minutes..
1. fasdtboot oem unlock(this unlocks the bootloader)
2. fastboot flash a custom recovery
3. flash supersu in your new recovery
4. reboot with root.
Click to expand...
Click to collapse
Just because I am using the toolkit doesn't mean I don't know the basics. I've been modding phones since the droid x days and before android I had windows mobile. I just prefer the simplicity of toolkits. Wugfresh does an excellent job making this program. I agree knowing the basics is a good thing because you should know what needs to be done for this all to happen but then again toolkit is very simple.
encephalon9986 said:
Just because I am using the toolkit doesn't mean I don't know the basics. I've been modding phones since the droid x days and before android I had windows mobile. I just prefer the simplicity of toolkits. Wugfresh does an excellent job making this program. I agree knowing the basics is a good thing because you should know what needs to be done for this all to happen but then again toolkit is very simple.
Click to expand...
Click to collapse
who said anything about YOU? if you know what you are doing already, use a toolkit, i dont care. but if you are new to this, toolkits are not for beginners. simply because they dont teach anything, nor do you learn any of the basics.
simms22 said:
who said anything about YOU? if you know what you are doing already, use a toolkit, i dont care. but if you are new to this, toolkits are not for beginners. simply because they dont teach anything, nor do you learn any of the basics.
Click to expand...
Click to collapse
Very true I agree. Learning the actual way is the best to learn. Sometimes I like using the cmd because its more fun doing it yourself. Either way works but remember mod at your own risk (for the op).
encephalon9986 said:
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Are there Mac tools as powerful and straightforward as Wugfresh?
I rooted my N7 using this tool. Simple for even me. However, that was when I had bootcamp on my Mac and could use Windows.
I use Apex launcher and am happy working in stock. The feature I miss is being able to use Titanium/TWRP for recovery. I have learned how to rebuild my system easily via file transfer, and using Terminal to root the phone isn't worth the down-side risks to me.
gmermel said:
Are there Mac tools as powerful and straightforward as Wugfresh?
I rooted my N7 using this tool. Simple for even me. However, that was when I had bootcamp on my Mac and could use Windows.
I use Apex launcher and am happy working in stock. The feature I miss is being able to use Titanium/TWRP for recovery. I have learned how to rebuild my system easily via file transfer, and using Terminal to root the phone isn't worth the down-side risks to me.
Click to expand...
Click to collapse
You can use fastboot on a Mac. Its even easier than windows. If you don't know how to use fastboot, if you've been reading the thread, we're saying do not use a toolkit.
Do you even need an unlocked bootloader? I don't think it came unlocked from the factory.
rootSU;58263052
Do you even need an unlocked bootloader? I don't think it came unlocked from the factory.[/QUOTE said:
Probably not. I was more interested in whether the "lock" referred to the phone/SIM. As long as that's not an issue I'm good.
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
gmermel said:
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
what is fastboot? http://www.androidcentral.com/android-z-what-fastboot
download fastboot for Mac http://www.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
gmermel said:
Probably not. I was more interested in whether the "lock" referred to the phone/SIM. As long as that's not an issue I'm good.
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
You would have to use a terminal but its very simple.
A terminal just means you type stuff and press enter instead of clicking buttons.
Fastboot is on both the phone and the computer. From the computer there is a fastboot for windows, Linux and Mac. You simply install them and type the commands from terminal.
This is my nexus 5 thread. Everything is relevant except the windows USB driver section
http://forum.xda-developers.com/showthread.php?t=2807273
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
TPADroid said:
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
Click to expand...
Click to collapse
First this does not belong in the Development sections, moved here. Secondly please read the Forum Rules on posting...thanks.
Thank you for moving to the appropriate location.
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
simms22 said:
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Click to expand...
Click to collapse
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
The boot.img files that your referring to are probably to un-encrypt your phone. I personally don't but other always have. Supposed to make it faster although i haven't been bothered by it being slow.
To unlock the bootloader all you have to do is used fastboot oem unlock via fastboot while your phone is in the bootloader mode.
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
mbiscuits said:
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
Click to expand...
Click to collapse
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
thats a kernel thatll let you unencrypt, if you want.
simms22 said:
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
Click to expand...
Click to collapse
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
mbiscuits said:
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
Click to expand...
Click to collapse
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
mbiscuits said:
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
Click to expand...
Click to collapse
which is why i always recommend that someone new root their phone the proper way the first time, to learn how to do it, and to learn a general way to fix your phone in case you mess up. after the first time, use toolkits all you want. but the learning how to do it properly is a very important.
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
That modified img allows for root because you cant just flash SU on the stock one (not yet anyway). Unlocking the bootloader is something different.
simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
Anybody knows where is the correct toolkit?
cpugeeker said:
Anybody knows where is the correct toolkit?
Click to expand...
Click to collapse
in my opening, there is no 'correct" toolkit.
Jnewell05 said:
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
If you haven't rooted for over a year why do it now? There are sure to be updates to how to root on the Nexus 6 and since I don't use my nexus 6 very much I hate to steer you in the wrong direction, as to backup information. I recently got the android 7.0 update and I haven't really had a chance to check it out yet. But I bet there are dozens of ways to backup if you would search Google.
Sent from my SAMSUNG-SM-G935A using Tapatalk
jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
istperson said:
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
Click to expand...
Click to collapse
Thank you very much!!!!
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree
OK
ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk
istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)
jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.