Need help rooting Nexus 6 on 6.0.0 - Nexus 6 Q&A, Help & Troubleshooting

I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks

dbzturtle said:
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk

blueyes said:
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.

dbzturtle said:
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
Click to expand...
Click to collapse
Fastboot flash twrp, and then flash 2.52superuser.sip in recovery. Look up wugfresh Nexus root toolkit, it'll explain the process.
Sent from my Nexus 6 using Tapatalk

I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.

dahawthorne said:
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
Click to expand...
Click to collapse
The problem with using toolkits when they are "idiot-proof" is that if you go into the process as an idiot, you leave the process still an idiot, so if something goes wrong with the device at a later date, the user has not got the skills to fix it, which becomes a problem on these forums as rather than telling someone how to fix it, we also have to teach the skills that should already have been learned.
Toolkits are great if you know what they're doing but if you dont, use fastboot the first time to get an understanding of it and also to ensure you know it is working on your computer correctly. It's easier to troubleshoot PC configurations when the device is fully working rather than waiting until it is "broken"

"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...

dahawthorne said:
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
Click to expand...
Click to collapse
It's not really the long way round. Once everything is installed, its as quick if not quicker. And as I said, you need all this installed for ongoing maintenance anyway so may as well do this whilst your device is working.
You can't brick your device by flashing to the wrong partition so there are no floods of posts from people doing things manually at all. .if you flash to the wrong partition,.just flash to the right partition. It's not rocket science either. If you flash a radio, flash it to the radio partition. If you flash system, flash it to the system partition. ...and if you type something wrong, it won't do anything at all.
Fastboot is well documented (by me and others) in the general forum. People should feel free to nude toolkits once they have learned it, but noobs should definitely learn it and use it the first time for the reasons I have already mentioned.
To root is so simple.
1. In fastboot, use
"fastboot oem unlock"
2. In fastboot, flash a custom twrp recovery image
"fastboot flash recovery twrp.img "
3. If marshamallow, flash a custom boot.img to allow it to be rooted
"fastboot flash boot boot.img"
4. Copy SuperSU to sdcard
5. Flash SuperSU zip from recovery
Once these steps have been carried out, you've used fastboot, know how it works and also have proof your computer has working fastboot. That ticks essential boxes.that every root user needs to have ticked. Once they're ticked, use toolkits to your hearts desire.
The worst thing about noobs using toolkits is when we need them to use fastboot when helping with their issues, they don't know what it is and we have to teach them that. We also need to troubleshoot setting it up which can be extremely hard if their device is bricked or in a state of needing repair. 10 minutes learning now can help prevent hours of wasting our time later. Surely it's only being courteous to learn these things ?

Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password

getmoneygreen said:
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
Click to expand...
Click to collapse
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.

I am an Android Noob! My first Android devices were the Nexus Player and the Nexus 6. (I came from iPhones and Apple TV) It did not take me long at all to learn how to use fastboot and adb. I manually flashed my Nexus 6 and Nexus Player to 6.0 before the OTAs were rolling out no problem. I have root on both of my devices.
My point is, if I can learn how to do this in a matter of a day (I have not had my Nexus 6 a full month yet) You can learn how to do it as well. There are tons of guides out there on how to do all of this. Google is your friend. You will feel awesome and have a sense of accomplishment if you take the time to learn this stuff. It is easy to learn, not hard at all! I come from a pretty extensive tech background so I was a step ahead, but anyone can do / learn this stuff.
There are toolkits that can do this stuff for you pretty much. I have not downloaded or used one myself. I don't trust someone else's code with my device. That's just me though. I like to feel in control when I flash stuff.

@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.

dahawthorne said:
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
Click to expand...
Click to collapse
Radio may boot but won't connect to a network.
Boot is the kernel so it won't boot without it (bootloop)
Both can be fixed by flashing the correct image to the correct partition.
The images in the factory image are appropriately labelled too, so it would be difficult to flash to the wrong partition without realizing it was wrong.. Eg
"fastboot flash radio boot.img" looks wrong when you have radio.img too.

Thanks, danarama. I suppose that's the point I was trying to make at the top - that if you're a bit of a thicko then you could flash to the wrong partition, which a predefined script won't. As long as it's recoverable, no problem, but I remember the pumping heart and breathlessness as I watched my devices on several occasions sitting with the boot animation for 10-15 minutes and thinking "What the hell do I do now?"
I know I'm hijacking this thread (sorry...) but is there anything you can think of that would definitely hard-brick my device if I'm being thick or careless? I've never managed it, and maybe as Android progresses it's becoming harder to hard-brick, but is there ever a time when I need to think "There's no way back from this one"?

danarama said:
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
Click to expand...
Click to collapse
Thank for the heads up really appreciate that. BTW what is the default password for twrp

getmoneygreen said:
Thank for the heads up really appreciate that. BTW what is the default password for twrp
Click to expand...
Click to collapse
Not sure, Im not encrypted. But its documented somewhere by twrp dev. Maybe on their site or in their thread

Related

[Q] Nexus 6 Rooting Help

I just received my Nexus 6 that I bought from Best Buy yesterday and have got it activated today.
I really want to root and try flashing my first rom. I have been reading thread after thread trying to learn and understand what it takes to root a Nexus 6, flash a rom, and what the proper way to do it is. Spent at least 5 hours reading threads and I have been so confused as to what to do.
First, I have read that you should do the ADB way to unlock, root, flash etc. (Nexus 6 all in one Beginners Guide) because using a toolkit will make flashing roms more trouble than its worth.
Next, I have read repeatedly that the method used when the Nexus 6 first came out is still a valid and perfectly fine way to unlock, root, flash, etc , but then I have found in another thread that in order to root it you will need to flash a custom kernal of some sort so i'm unsure what I need to do.
The Nexus 6 All-in-One Beginners Guide seems pretty straightforward and easy, however this is my first time flashing anything and rooting a Nexus device so i'm unsure what I should trust.
Thanks in advance for anyone willing to help give this newbie some advice.
Any help is appreciated, I am just frustrated with trying to find a current method of unlocking, rooting, flashing, etc because nearly every thread I have read is dated back to when the device first came out and I usually am able to learn visually very easily but many videos for the N6 on youtube are from when the N6 came out, dating back 6-9 months ago.
So again, any help would be greatly appreciated because I am getting a bit frustrated with sorting out all the information and learning what I can trust so I don't damage my phone beyond repair.
Thank you again for reading and giving advice if you choose to and I apologize if this sounded like a rant. I just really need some help understanding what to do. Thank you.
If anyone is able to clear up my confusion on the issues I brought up, thank you.
1. Use Wugs to unlock and root
(Sure knowing how to adb is important, but just do that)
2. Wugs will install a custom recovery - you flash roms in said recovery.
3. Apps I recommend you get after obtaining root:
(Some paid, some free)
SuperSU Pro (paid)
Buaybox Pro (paid)
Root Explorer (paid)
Titanium Backup (paid/free)
Then you'll have a pretty good start at supporting the devs, while having a good file/folder control app, and a way to protect yourself against data loss - with a simple way of reverting back to a previous build should you dislike a rom.
Keep reading. You're off to a gold start but I learn more and more every day. Never underestimate the value of reading everything prior to flashing/modifying it just might save you a headache when your phone inevitably bootloops for a silly reason.
iRub1Out said:
1. Use Wugs to unlock and root
(Sure knowing how to adb is important, but just do that)
2. Wugs will install a custom recovery - you flash roms in said recovery.
3. Apps I recommend you get after obtaining root:
(Some paid, some free)
SuperSU Pro (paid)
Buaybox Pro (paid)
Root Explorer (paid)
Titanium Backup (paid/free)
Then you'll have a pretty good start at supporting the devs, while having a good file/folder control app, and a way to protect yourself against data loss - with a simple way of reverting back to a previous build should you dislike a rom.
Keep reading. You're off to a gold start but I learn more and more every day. Never underestimate the value of reading everything prior to flashing/modifying it just might save you a headache when your phone inevitably bootloops for a silly reason.
Click to expand...
Click to collapse
Thank you for your advice. May I ask the difference of doing it with a Toolkit rather than the ADB way ? It just seems that one is easier than the other.
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Iandrew124 said:
Thank you for your advice. May I ask the difference of doing it with a Toolkit rather than the ADB way ? It just seems that one is easier than the other.
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Click to expand...
Click to collapse
The adb way teaches you how to do it at the base level - this method would allow you to pull files/folders without the phone booting, or flash individual partitions without having to flash a whole image - there's a LOT of reasons to know and understand adb, and you eventually should, as it could save your phone when all else fails.... It has its benefits, but for simplicity's sake - for now - just use Wugs.
Using toolkits in effect gives you a crutch. With this crutch you then are forced to depend on this crutch for future needs. What happens when you get a update or different phone that Wugs doesn't work with or do what you need to do? THATS where adb understanding would come in handy.
I NEVER recommend people use toolkits exclusively as this can and WILL eventually lead to major issues that the user is now at step 1 of the learning process all over again - or - are forced to wait for toolkits to be made to do something as simple as obtain root. That's annoying.
In this case, I hope you will make yourself more familiar with adb when you can, use it, try it out, understand what it does and what it's for - but just to get you up and running you can use the kit, just don't expect it to be that easy every time because, I promise you, it won't be and at some point adb will be the only option you have. You don't want to have to be in a panic situation when that knowledge could have saved you.
That's just how I like to help people learn this stuff. Start off slow just so they can do what they want to do - but heavily stress the importance of HOW that toolkit works - because its doing what you need to learn how to do - it just does it all for you.
Don't rely on that crutch - it won't always be there.
Iandrew124 said:
. . .
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Click to expand...
Click to collapse
Manual flashing has the advantage that you controls the 'speed of the process. Because you have to enter commands one by one.
Toolkits use scripts instead of commands. And you have a choice from many options.
You won't be fast enough to stop when using a wrong option/script.
The post of irub1out is a good method.
After point 1. wait a day and go on with reading and posting.
adb is not used in the rooting process. fastboot is used to unlock the bootloader and then flash a custom recovery.
It's a really simple process after installing fastboot.
1. fastboot oem unlock
2. fastboot flash recovery recovery.img
3. Put SuperSU flashable zip on sdcard
4. Boot into recovery and flash that zip
There really shouldn't be any need to use a toolkit and if you do it manually, you KNOW your computer is configured properly so if you need it for recovery purposes later and something is not working, you know it's not the computer that is the issue.
Use the toolkit for other things once you've done the unlock and flash manually by all means. But NEVER use the toolkit first. This is a recipe for disaster.
Although the previous posts stress the importance of learning manually, they kind of miss part of the point as to why and I bet 90% of our experienced users here will agree with me...NO SHORTCUTS FIRST TIME.
If you need more info on fastboot, there's an adb and fastboot thread in general > sticky roll-up thread.
I concur with @danarama. We spend half our time in this forum trying to fix mistakes made with toolkit.
really, if the user doesnt have the proper knowledge to make the simple choices given in the toolkit, they are not going to choose the right files to do it manually.
so it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
but regardless of what any user might claim, the toolkit doesnt make mistakes. it executes the same commands you would use manually via a script based on your choices.
there is no margin of error other than the users input.
j
bweN diorD said:
really, if the user doesnt have the proper knowledge to make the simple choices given in the toolkit, they are not going to choose the right files to do it manually.
so it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
but regardless of what any user might claim, the toolkit doesnt make mistakes. it executes the same commands you would use manually via a script based on your choices.
there is no margin of error other than the users input.
Click to expand...
Click to collapse
first off, toolkits DO occasionally make mistakes, it has been proven, so dont argue with that. sure, its not always, but it happens. secondly, the user choosing files.. ok, if you do it the right way, there are only two files you need. and the user doesnt have a choice to pick them. they are the twrp recovery, and supersu. the user has to go find them, not pick out of a list. and witj my time on the n6 since last November, not one person picked the wrong files to root their phones. again, its because they arent given a choice.
bweN diorD said:
it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing
Click to expand...
Click to collapse
...and to ensure fastboot is Working, as I mentioned in my post. So it does make a difference.
a person gaining knowledge to understand what they are doing is by far the most important thing that can happen. thats something thatll never happen with a root toolkit.
Iv'e had several good flashes and some bad using the exact same files and same options during testing and playing. Worst button/option to even be available to noobs is the lock after flash or even a relock button at all. Remove that option and you are pretty much safe from hard brick. Then only have to come back and ask us to walk through fastboot when the flash goes belly up. Need an audit on how many times we have seen this exact scenario.
prdog1 said:
Iv'e had several good flashes and some bad using the exact same files and same options during testing and playing. Worst button/option to even be available to noobs is the lock after flash or even a relock button at all. Remove that option and you are pretty much safe from hard brick. Then only have to come back and ask us to walk through fastboot when the flash goes belly up. Need an audit on how many times we have seen this exact scenario.
Click to expand...
Click to collapse
That's another good point.. When 5.1 came out and locking the bootloader after flash, if it didn't boot, it would be a brick.. Toolkits would do this after a flash and brick phones.. You have to wait until the toolkit is updated before using it safely.
simms22 said:
j
first off, toolkits DO occasionally make mistakes, it has been proven, so dont argue with that. sure, its not always, but it happens. secondly, the user choosing files.. ok, if you do it the right way, there are only two files you need. and the user doesnt have a choice to pick them. they are the twrp recovery, and supersu. the user has to go find them, not pick out of a list. and witj my time on the n6 since last November, not one person picked the wrong files to root their phones. again, its because they arent given a choice.
Click to expand...
Click to collapse
i sir, will argue with whatever i wish.
in the year i maintained a toolkit for the last moto i had, 20k+ downloads, not one user accused the toolkit of flashing something it wasnt supposed to. the code is fairly simple, one option points to a command and file (simply put), etc. etc.
is it possible some one in a million error happened, doubtful but ok.
my comment was more directed at the previous poster who said something about spending 1/2 his time helping users with toolkit problems.
thats very unlikely, unless the toolkit coding is done very poorly.
---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------
danarama said:
...and to ensure fastboot is Working, as I mentioned in my post. So it does make a difference.
Click to expand...
Click to collapse
how about you quote the rest of my sentence next time, where i agreed with your logic on that.
unless your intentionally trying to start an argument? cause thats what it looks like.
bweN diorD said:
how about you quote the rest of my sentence next time, where i agreed with your logic on that.
Click to expand...
Click to collapse
Because the rest of your sentence was nothing to do with what I wanted to say and you didn't agree with my logic at all. In fact your sentence (even complete) suggests that what I had said wouldn't even factor in to anything.
bweN diorD said:
unless your intentionally trying to start an argument? cause thats what it looks like.
Click to expand...
Click to collapse
I'm 35 years old. I've got better things to do than try to create arguments in Internet forums. I was expanding on your sentence on something you missed. Kick yourself for the omission, not me for pointing it out.
Don't be so bloody confrontational. You're coming off as a petulant child, as does everyone who starts a sentence "how about" without trying to understand what they're talking about first.
bweN diorD said:
i sir, will argue with whatever i wish.
in the year i maintained a toolkit for the last moto i had, 20k+ downloads, not one user accused the toolkit of flashing something it wasnt supposed to. the code is fairly simple, one option points to a command and file (simply put), etc. etc.
is it possible some one in a million error happened, doubtful but ok.
my comment was more directed at the previous poster who said something about spending 1/2 his time helping users with toolkit problems.
thats very unlikely, unless the toolkit coding is done very poorly.
Click to expand...
Click to collapse
if i can get someone that will make a toolkit that does what it does, and goes through every step explaining the process of what its doing and how to do it manually, id be a happy man. seriously.
danarama said:
Because the rest of your sentence was nothing to do with what I wanted to say and you didn't agree with my logic at all. In fact your sentence (even complete) suggests that what I had said wouldn't even factor in to anything.
I'm 35 years old. I've got better things to do than try to create arguments in Internet forums. I was expanding on your sentence on something you missed. Kick yourself for the omission, not me for pointing it out.
Don't be so bloody confrontational. You're coming off as a petulant child, as does everyone who starts a sentence "how about" without trying to understand what they're talking about first.
Click to expand...
Click to collapse
funny, it looks like i am agreeing with the manual logic...
other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
Click to expand...
Click to collapse
simms22 said:
if i can get someone that will make a toolkit that does what it does, and goes through every step explaining the process of what its doing and how to do it manually, id be a happy man. seriously.
Click to expand...
Click to collapse
I honestly considered making that in the past.
---------- Post added at 05:44 PM ---------- Previous post was at 05:37 PM ----------
bweN diorD said:
funny, it looks like i am agreeing with the manual logic...
Click to expand...
Click to collapse
That's not what we're talking about. I never said you didn't agree with the "manual logic"
Please re-read my post. I think you've misunderstood what I said. Let me know if you'd like me to explain what were talking about afterwards if you still dont understand
Tbh, not using toolkits comes down to this:
Its the easiest ****ing thing ever to do with out one. If you need one, you have a major gap in your understanding... And you need to fix that first. Well you don't "need" to unfortunately, but acquiring root access is taking over being the admin for your device. If you are choosing to do that, you should probably understand the basic tools.
I am in approximately the same position as the OP with a brand new Nexus 6 and I have a question. Should I take any OTA updates that are available before starting the unlock bootloader and rooting process?

Nexus 6 is horrible

I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
That's a rather non-descript post. Who's your carrier, what Rom's are you talking about, any custom kernels, did you perform a wipe before installing? As far as the Audio goes, I've got no complaints from the speakers nor using headphones (both hardwired and BT headphones). You do realize that the first boot after installing a fresh Rom can take several minutes, some as long as 8 minutes while everything is set in place. More info so that we can help, please.
alucke said:
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
Click to expand...
Click to collapse
lol your doing something wrong.
i have flashed most of the available roms, in total hundreds of times, never failed to boot, not even once.
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Is this a rant or are you asking for help? This is a development forum, so not really the place to rant. If you want help, please ask specific questions whilst supplying relevant information
Need education
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
---------- Post added 21st September 2015 at 12:09 AM ---------- Previous post was 20th September 2015 at 11:59 PM ----------
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this Android phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online by self at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus 6 is back in order. I some how managed to use the Root Tool Kit v2.0.4 and "pushed" the factory, I downloaded from Google, to the phone. I assume this restored my ABD allowing debug thereby establishing USB connection between PC and Nexus 6, I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the Nexus 6 bootloader or Fastboot.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
This is the most idiotic post I've seen here all day. Seriously sell your nexus 6 and go buy a different phone if you don't like the phone or face the fact that you either don't know how to use a nexus device or you have a defective phone. But I'm almost entirely convinced this is 100% user error
Sent from my Nexus 6 using XDA Free mobile app
ray6279 said:
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
Click to expand...
Click to collapse
here is a good place to start
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
good luck!
Android documentation is kinda lacking
Its not terrible... Its just not entirely coherent, well organized or complete. A lot of poking around and learn by doing, patching together threads that document how things work ect...
Here is my suggestion:
Follow the second link posted by simms22 above, this one here: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Go here: https://developers.google.com/android/nexus/images?hl=en
And download the latest image for your phone (shamu, the images at the bottom of the list are most recent. All carriers currently use same build, unless your on tmobile or Fi)
Use some kind of unzipping program (not sure if winrar can do .tgz, if not just google "Windows .tgz") to decompress the image you download. This will have a few .img files in it and a .zip Unzip the .zip for the rest of the partition images for the phone.
With these you can use fastboot to re-format partition to stock.
Here is an older guide, while devices may vary a little... and things have changed since 2011, were still mostly talking about system, boot, recovery, data....
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
I would say read through the above guides thoroughly, then manually update your phone to stock.
You will notice the stock flash-all script will
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.101.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy48m.zip
You probably don't want to do all this... You will notice the last command I showed is fastboot -w update image-shamu-lmy48m.zip (assuming you downloaded the lmy48m image)
We already unzipped this, so rather then flash it in bulk (flashing userdata.img will wipe device) lets flash everything but leave data in place.
So get fastboot working, go to bootloader, and as the script does
With fastboot:
Flash the bootloader
then use fastboot to reboot, to the bootloader
flash the radio
then use fastboot to reboot to the bootloader
then fasboot flash system, recovery, boot and cache images, skipping userdata to avoid wiping the sd card.
At this point reboot. It may take a while for the first boot as android sets itself up and optimizing applications. If things appear to be hung give it 10 minutes before forcing a reboot checking your images and trying again. Pay attention to the output of the commands and make sure there are no errors. If there are read them, and google them.
Now you should be able to boot, and you will be fully stock. This is what it takes to recover from almost any situation. Often you can just flash system to update. Boot will overwrite your kernel, so it is often skipped when custom kernels are used... particularly when not encrypted.
Now find the website for twrp and find the image for your device, then go back to bootloader mode and flash recovery, after flashing reboot directly to recovery.
Also find chainfire's website with the recovery flashable supersu (should be a .zip)
Make sure the supersu install zip is on your phone, and the recovery is on your computer.
Reboot to bootloader and fastboot flash twrp to your recovery partition, then immediately reboot to recovery mode to finish the install.
In recovery make a backup of your working stock system.
After that install supersu
Reboot, and you should be stock and rooted with a backup of your completely stock system.
From here if your want to install a rom reboot to recovery, wipe caches, system and data. On future upgrades backup first, and try only wiping system and caches, then flash the new version of the rom and you wont have to set anything back up. You will have to reinstall xposed if your use it, as well as supersu if your rom does not include it for some reason.
If you do all that, read those guides to the point where you understand each step, and read the thread or at least the last hand full of pages of any rom or utility that you use... Things should work pretty good.
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
And likewise to this post , useless as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
nevermind
simms22 said:
nevermind
Click to expand...
Click to collapse
:laugh: :laugh:
Was going to post, and had this thought also....
btw JJD loves his N6 and his speakers Rock!
#nuffsaid
Nexus 6 ftw!
disturb1 said:
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
Click to expand...
Click to collapse
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it either.
What file manager do you use, and did you have gvfs-mtp or kio-mtp installed?
What utilities were you using to mount the mtp drive?
These instructions are for arch linux, https://wiki.archlinux.org/index.php/MTP#simple-mtpfs (I use simple mtpfs), adapt them to your distro, find your distros documentation.
But then you don't really need it to show up in the OS? Does fastboot recognize it? Have you installed udev rules for it?
ok, thanks for all the input. I will give the nexus 6 a try again, root it. Can anyone point me to a custom rom that is somewhat close to stock?
I like Pure Nexus
scryan said:
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it
Click to expand...
Click to collapse
Not sure if I just have issues with lollipop or the hardware and lollipop
I have it rooted now and also still hate it I don't have the sound issues that some have but freezing was a constant with nexus T-Mobile stock ROM or maybe I have a lucky lemon ether way
I don't blame others or look to others to do my rooting rom installation or themes nor do I assume that it the phone every time all I am saying is we need to stop blaming every confused user as noob and assume people are not trying to learn
I been here 3 years but I lurk and learn and move on but I constantly see issues of flaming it is sad ...I see your reply and that fact that you offered help is what I like to see what I would offer if I knew an answer..
Honestly I am just not a fan of the phone but I made my bed and in it I must... hack at it till I am happy...

not really a noob, but still confused anyway... need a little help from my friends...

Project Fi Nexus 6 rooted here on 5.1.1 LVY48E
I keep getting a notice that a system update has been downloaded (29.1) megs..a tad annoying
Would like to run the update, but can't because of TWRP... Also would like to try 6.0 if it is out, just don't want to lose root, and or have to have my phone reset...
I have Wug's nexus root toolkit too
How do I update to the latest L and or/ M???
Looking for some friendly advice....
Thanks!
Forgot to mention that I have tried flashing the update manually to no avail..
Drumrjoe
You can't update your rooted phone with Ota update, only way is to flash the factory image, download latest Nexus 6 factory image from Google and flash it with the tool kit, if you don't know how to flash a factory image, you should see the main thread
And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?
aiiee said:
And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?
Click to expand...
Click to collapse
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..
drumrjoe said:
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..
Click to expand...
Click to collapse
Just do it manually using fastboot. Or since you have TWRP, find a pre-rooted rom.zip you can flash from there.
Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.
istperson said:
Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.
Click to expand...
Click to collapse
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.
zelendel said:
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.
Click to expand...
Click to collapse
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,
danarama said:
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,
Click to expand...
Click to collapse
I know. All we can do is advise and the lazy will still be lazy and then end up with issues. This is why you will see people post about issues and then the min they mention they have used a root kit all replies stop. There are many of us that refuse to help people that have used a root kit. It shows they should not be messing around with their devices if they dont have the time to learn to do things properly.
Duly noted -
But seriously, thanks for the info.. will be figuring this out!
Best all
DJ
Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA
drumrjoe said:
Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA
Click to expand...
Click to collapse
Not 100% sure of this but I believe that Marshmallow will not achieve root without some modification. At least I couldn't

Issues after trying to Root : Bootloader Code 3 : Soft Bricked?

Using this guy's guide for the Nexus 5 I had no issues, bought a N6 today and was giddy to flash on Cataclysm for N6 and figured might as well use same person's guide for next phone up.
http://www.androidrootz.com/2014/12/how-to-root-nexus-6-windowsmaclinuxubun.html
Was able to unlock bootloader, then installed TWRP but now am getting the 'corrupt phone' message, however unlike others like I have read on XDA, am unable to boot up by just letting it sit. Screen turns off and that's that. Before beginning entire process I enabled "enable/allow oem unlocking". I'm assuming that when the phone factory resets after the bootloader unlock I need to go back in and recheck 'allow oem unlock' in dev options, but I didn't as I assume/ed that it wasn't necessary and the guide doesn't tell you to.
Tried relocking the bootloader to maybe get phone to open up, but terminal tells me that I need to have 'allow oem unlock' checked. Nice Catch-22 http://puu.sh/moOUf/d0f8fa9050.png
Tried formatting data from within TWRP and factory resetting/wiping everything but it tells me that it is unable to mount '/data'
Have since tried WugsToolkit and flashing to stock with 'softbricked' option enabled the shamu-mmb29k-fact....tgz image that I downloaded and imported myself into Wugs (was taking 10 minutes to dl 1%). That seemed to work and told me it was a success, however when I then went back to re-enable the bootloader via wugs it fails and reboots with the lock sign still open and boots again onto 'corruption' screen that then flashes off and turns phone off, left it for 30 minutes at one point and didn't boot so don't think I'm lucky enough to be able to sit if through like others who had that issue
Where to go from here? Really hoping I didn't brick this phone less that 3 hours after getting it. I can still boot and see the Google screen and can get onto the bootloader and used to be able to get into recovery (since wugs have been getting the android with red triangle)
Been rooting/rom'ing since day one that I've had androids. Had a Samsung Apollo with CM on it, same for the Nexus S, then the Galaxy Nexus, then the N5 and looks like my chain of no issues ended tonight
Anything you can do for guys would be greatly appreciated. No clue where to go from here....
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
DO NOT RELOCK THE BOOTLOADER!!!!! I cannot emphasize how critical it is that you do not relock the bootloader, given the position you are in. If you somehow manage to relock the bootloader and "enable OEM unlock" is toggled off and Android will not boot (even after attempting a factory reset), then you are 100% bricked with no way to fix your phone. Personally, I leave my bootloader unlocked 100% of the time so that I can fix anything that may go wrong with my phone. Additionally, I (as well as many other users on here) will always advise against using Wug's or any other toolkit in order to do stuff to your phone. While they do provide a nice GUI as well as an easy way to install the necessary drivers, using the regular platform-tools command line method isn't all that hard to figure out, and it allows you to know exactly what you have done to your phone. With Wug's and the like, you never really know what commands that they are running and exactly at what point in the process a flash may fail. Right now, I would advise you to read up on using the platform-tools method to flash stock images. After you have all of the necessary drivers, platform-tools, etc. working properly on your computer, I would strongly advise that you download MMB29S (the latest official update) from the Google Developer page and flash it using the platform-tools method, NOT with Wug's. And whatever you do, I repeat, DO NOT LOCK YOUR BOOTLOADER!
---------- Post added at 07:03 AM ---------- Previous post was at 06:51 AM ----------
triguyrn said:
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
Click to expand...
Click to collapse
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
matthew2926 said:
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
Click to expand...
Click to collapse
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
No problem! It's too bad to hear about your device but at least you got a new one on the way. There is really no harm to at least trying the flash-all script. It will either work and save you time or fail halfway through and force you to flash everything manually.
triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
Flash-all script is still broken, flash the img files individualy in fastboot.
gee2012 said:
Flash-all script is still broken, flash the img files individualy in fastboot.
Click to expand...
Click to collapse
You guys are life savers, thank you so much
Got it to work after I was getting ready to phone it in and bring it to a repair shop and eat whatever the charge might've been

Nexus 6 Rooted and Unlocked and now new Feb OTA - Pls guide

Nexus 6 Rooted and Unlocked and now new Feb OTA - Pls guide
Dear Friends,
I am currently having Nexus 6 with Build Number MMB29S which is rooted unlocked. Last time I had to wipe clean Nexus 6 just to update to this build. The nexus toolkit was somehow not working for me.
Now I see again that there is an OTA called Feb Security update for android 6.0.1.
I really don’t want to flash factory image bcz it will overwrite everything and erase all. Last time was a bad exp.
Kindly help.
Reformatting and again restoring is too much of pain.
[img=http://s8.postimg.org/vv4cdmkw5/Screenshot_20160213_1702331.png]
image upload
Have you tried WugFresh's Nexus Root Tool (NRT)? Backup your device via recovery, and save your backup in a safe location like your PC.
Then use NRT "no wipe' install.
I've rooted everything starting with the OG Droid and beyond; so now days I don't bother rooting by hand unless I have to, and if someone has a good tool I use it. I'm a big fan of Wug's NRT the only time it gave me any trouble was during the transition to M.
If the OP doesn't have the experience to be able to resolve problems that might crop up in the process of using a rootkit like the WugFresh tool like you apparently do, you shouldn't be recommending the rootkit tool to the OP. He should instead have a properly working ADB/Fastboot setup and issue the commands manually.
Assuming your bootloader is still unlocked, flashing from factory image should not wipe your data (just make sure you don't flash userdata.img). I don't use NRT, but I'm told it does have the option to flash factory image without wiping your data (again, assuming your bootloader is still unlocked).
If your bootloader is locked, you have no option but to unlock it (which will wipe your device). Bite the bullet and do it - and don't lock your bootloader after that. Mark it as a lesson learned
Edit: I'd urge you to learn using fastboot directly, instead of using the toolkit. That way, you'd know exactly what step does what. It really is not that hard - read the sticky threads about how to flash using fastboot. It is fairly straightforward, and more importantly, you'll know what you are doing.
http://forum.xda-developers.com/showpost.php?p=65136208&postcount=13
excellent thank you
however need help i last two steps
followd word by word
If it were me, I'd welcome the suggestion to use NRT, so I think he should be recommending the rootkit tool to the OP.
@aiiee: Seriously? Nexus phones are the easiest to root and modify, requiring nothing more than ADB, Fastboot, and the drivers for the device. Rootkits are complete rubbish for a Nexus device. All they do is automate a process that you can do yourself, simply by using your head, and a keyboard.
Since using a rootkit doesn't actually teach you how to root the device, if you encounter a problem using one, what will you do? Will you be like most everyone else who uses one and come to XDA begging for help because you couldn't be bothered to learn how to do it the right way? Or will you be a smart one and figure out the solution to the problem by doing research?
The best solution is to ask yourself first what root is and whether you really need it. If you determine to yourself that you do need root, then you start reading threads in the forum, and start learning about the proper root processes for this device. When you not only have read everything, but also have understood it, then and only then do you attempt the procedure yourself.
Under no circumstances should anyone be recommending a rootkit. Everyone should know how to use ADB and Fastboot to do the job. It doesn't take long and it's really simple to do.
meh, I just don't like your strident tone. And your argument doesn't hold any water. If I get in trouble with a rootkit, then I can learn what it does. To listen to you we should all build our own cars in case they break down. ehhh, not so much you know?
I know several people on this forum who would disagree with you regarding said argument not holding water. But frankly, what you think about me or my argument is irrelevant. Rooting is serious business, period. While it is possible to brick a device using either Fastboot or a rootkit, by learning everything you possibly can about how it's done through use of the tools Google provides, you have a chance of reviving your device. Otherwise, you're coming here to beg for help.
@Strephorn Alkaholi, not a fan of the "begging" comments, and frankly what you think of me or my argument is also irrelevant. Isn't that nice?
Not a fan of the begging comments? Too damn bad. This is XDA Developers, not XDA Help-me-because-I-can't-be-bothered-to-learn-how-to-properly-root-my-device.
I can dismiss your opinion because you provide no solid reasoning to back it up. Meanwhile, not only do I provide a reason, I provide methodology which happens to follow site rules, which happens to be "search before you post."
Don't bother replying, as you and another poster in this forum have reaffirmed my belief that humanity in general is a parasite that has become larger than the host.
wow

Categories

Resources