Related
So I see from the Development subforum that the Droid 4 hasn't been rooted yet. Correct? Does anyone have a plain english update as to what's going on on that front?
I see there's a bounty on someone's head, or something like that, but that's all I've got.. and I'm not savvy enough to know what to do myself or know what's really happening there. I'd love a one click root method. How far away are we from that functionality?
sorry for the pretty dumb question
tamarw said:
So I see from the Development subforum that the Droid 4 hasn't been rooted yet. Correct? Does anyone have a plain english update as to what's going on on that front?
I see there's a bounty on someone's head, or something like that, but that's all I've got.. and I'm not savvy enough to know what to do myself or know what's really happening there. I'd love a one click root method. How far away are we from that functionality?
sorry for the pretty dumb question
Click to expand...
Click to collapse
Root has been achieved. Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=1492843
kwyrt said:
Root has been achieved. Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=1492843
Click to expand...
Click to collapse
thank you Guess I was just searching for the phrase "root."
tamarw said:
thank you Guess I was just searching for the phrase "root."
Click to expand...
Click to collapse
No problem. Happy rooting. And be careful!
Root was achieved on this device by djrbliss before it was even released actually, but we still do not yet have a full XML.zip of fastboot images to restore with, so it is very dangerous to make any significant mods at this stage.
I have been pushing all my sources very hard to find this file, but so far everyone has come up empty.
Until we have it we are all working without a safety net because signed factory images are needed to restore a soft bricked device.
Stick to rooting your phone, for the time being. You can disable bloatware, and customize the hell out of the stock ROM that's already on there. That should be enough to get you through, for the time being. Don't get me wrong, we're all salivating over a real safety net.
Go with a simple root or safestrap it. I bricked my phone using safestrap.
Root for now, wait for fastboot files.
Hello, I have a Nexus 6 that is running 5.1 build number LMY47D and I want to update to 5.1.1-LMY47Z. How do I do this with root and a custom recovery? I've done it before but I can't for the life of me remember.
I would like to update in a way that I don't lose any data. I've read of people flashing only the files needed from the update but there wasn't a clear explanation of how they did it. Is there a better way?
Thanks in advance.
PersonFromThatPlace said:
Hello, I have a Nexus 6 that is running 5.1 build number LMY47D and I want to update to 5.1.1-LMY47Z. How do I do this with root and a custom recovery? I've done it before but I can't for the life of me remember.
I would like to update in a way that I don't lose any data. I've read of people flashing only the files needed from the update but there wasn't a clear explanation of how they did it. Is there a better way?
Thanks in advance.
Click to expand...
Click to collapse
I believe I've already answered your question in the general Q and A thread.
PersonFromThatPlace said:
Hello, I have a Nexus 6 that is running 5.1 build number LMY47D and I want to update to 5.1.1-LMY47Z. How do I do this. . . ..
Click to expand...
Click to collapse
http://www.wugfresh.com
A word of advice on toolkits:
Not recommended unless you already have knowledge of ADB/fastboot.
Also, completely unnecessary for a nexus as all flashing can be done manually in virtually the same amount of time. Plus, you know exactly what is being flashed to your device unlike flying blind with a toolkit.
Evolution_Tech said:
A word of advice on toolkits:
Not recommended unless you already have knowledge of ADB/fastboot.
Also, completely unnecessary for a nexus as all flashing can be done manually in virtually the same amount of time. Plus, you know exactly what is being flashed to your device unlike flying blind with a toolkit.
Click to expand...
Click to collapse
In general I can agree with you about toolkits.
But the Nexus Root Toolkit of Wugfresh is an exception. Every step/command is written to a log, and is being commented.
So by using the NRT you can learn about Adb and Fasboot.
The nice thing of this kit is that the needed stuff is downloaded by the kit.
NLBeev said:
In general I can agree with you about toolkits.
But the Nexus Root Toolkit of Wugfresh is an exception. Every step/command is written to a log, and is being commented.
So by using the NRT you can learn about Adb and Fasboot.
The nice thing of this kit is that the needed stuff is downloaded by the kit.
Click to expand...
Click to collapse
Explain that to the number of people crying for help when they're stuck and a simple fastboot command or two fixes the issue.
NLBeev said:
In general I can agree with you about toolkits.
But the Nexus Root Toolkit of Wugfresh is an exception. Every step/command is written to a log, and is being commented.
So by using the NRT you can learn about Adb and Fasboot.
The nice thing of this kit is that the needed stuff is downloaded by the kit.
Click to expand...
Click to collapse
lol, not really. good try though.
Evolution_Tech said:
Explain that to the number of people crying for help when they're stuck and a simple fastboot command or two fixes the issue.
Click to expand...
Click to collapse
As with many methods there are not only advantages.
There are some threads about Wugfresh's toolkit explaining pro's and con's.
Many users appreciate Wugfresh's toolkit and help.
It could be helpfully in the same way as your posts about fixing issues.
I appreciate both methods, info and help.
Got my new nexus 6 today
updated to android 5.1.1
am from touchwiz most of my life
any apps i sud be using
and how to root this thing?
i mostly used odin all my life guess no use of that here anymore
so any guidance is highly appreciated....
advance thanks
MD0038 said:
Got my new nexus 6 today
updated to android 5.1.1
am from touchwiz most of my life
any apps i sud be using
and how to root this thing?
i mostly used odin all my life guess no use of that here anymore
so any guidance is highly appreciated....
advance thanks
Click to expand...
Click to collapse
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
http://forum.xda-developers.com/showthread.php?t=2948481
Face_Plant said:
http://forum.xda-developers.com/showthread.php?t=2948481
Click to expand...
Click to collapse
will go through thee whole thing and understand if not hope you al help me a bit
XxCyberHackerxX said:
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
Click to expand...
Click to collapse
ok, or you can root your device the right way, within 3-4 minutes. where is the guidance in using a tool kit? considering you learn absolutely zero from it, and toolkits occasionally mess things up as well.
simms22 said:
ok, or you can root your device the right way, within 3-4 minutes. where is the guidance in using a tool kit? cinsidering you learn absolutely zero from it, and toolkits occasionally mess things up as well.
Click to expand...
Click to collapse
Very true. But he indicated he was a novice so the toolkit would guide him through the process
XxCyberHackerxX said:
Very true. But he indicated he was a novice so the toolkit would guide him through the process
Click to expand...
Click to collapse
Toolkit is good but i want to learn all things
XxCyberHackerxX said:
Very true. But he indicated he was a novice so the toolkit would guide him through the process
Click to expand...
Click to collapse
tool kits are not for novices, at all. they do not guide you through anything. toolkits are fine to use, when you know whats going on. but when you dont, you arent taught a single thing.
XxCyberHackerxX said:
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
Click to expand...
Click to collapse
DO NOT use the toolkit till unlocked and know how to use manual fastboot. Will not know why toolkit failed and will not know how to recover as it will take fastboot to recover. I did Odin also. It was a dependable tool. Fastboot is the old tried and true Nexus, HTC tool. Virtually unbrickable. The toolkit can brick you and will require fastboot knowledge to fix. Fastboot update only takes 2-3 minutes once set up and know what you are doing.
Just to echo what everyone else is saying, toolkits are great but only use them if you understand what they're doing. Using fastboot the first time.round is essential for learning.
All.threads are in nexus 6 general > sticky roll-up
Including my adb and fastboot thread,. Which is good for noobs.
HaHaa. I actually had more problems and failed flashes with Odin and "the toolkit". Never had a fail with fastboot.
Toolkits.... Not. Do it manually with all the proven guides posted!
MD0038 said:
and how to root this thing?
Click to expand...
Click to collapse
There are already advices given by real experts.
I humble add some " why's " not to start rooting for the first time with a toolkit.
A. There are so many options; it easy to make a mistake.
B. Toolkits use scripts and once started you are not fast enough to stop the process when you do something wrong.
C. When you know how to use command lines
with adb and fastboot, you will be prepared for toolkits.
D. You will find here complete rooting guidelines in sticky threads. Read them.
Nice rooting!
Thanks everyone for overwhelming support read half of the thread will do rest of the work tomorrow some assignments to do
Sent from my Nexus 6 using Tapatalk
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?
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Edit: This was meant to try to help beginners understand that the chainfire root method is for Lollipop and not for Marshmallow. I do not believe this should be taken down, just labeled for Lollipop so beginners don't soft brick their phones using this guide on a phone with Marshmallow.
Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Click to expand...
Click to collapse
root process for lollipop..
unlock your bootloader
fastboot flash twrp recovery
flash supersu via your new recovery
reboot and youll have root.
how hard is that? if its too hard, id suggest doing some reading about the process first, its all over google.
There's a new post every day about someone following the root process for lollipop when they have Marshmallow. I am far from computer illiterate and from the number of posts on this I think it speaks for itself.
At least label it more obviously that it's for lollipop.
I used chainfires root method and personally I don't see how anyone that's got a brain could screw this up. All ya gotta do is read and read then read some more. It's not hard people's . Chainfires method is about as simple as it can get. @Chainfire is a genius I hope he doesn't see this post, hell I'm embarrassed for him.
Sent from my HTC6600LVW using Tapatalk
the difference bwtween lollipop and marshmallow is that you also have to flash a custom kernel in twrp right before you flash supersu. besides that, its identicle.
I'm agree with you if you're talking about Android M. It's really crazy.
But as far as I remember, there was no notable obstacle on LP version root.
Unlock bootloader. Flash recovery and flash supersu....any other step?
If they are not familiar with adb, I guess they may face trouble. Actually the problem occurs from the start at downloading adb tool(platform_tools on SDK) with that sucking google tool.
..However, if they are, they shouldn't do root. It's too risky if they don't even know the basics.
So the instructions for how to root lollipop should be removed because some people don't take the time to read everything and confirm which version of Android they have on their phone?
PielunA said:
I'm agree with you if you're talking about Android M. It's really crazy.
But as far as I remember, there was no notable obstacle on LP version root.
Unlock bootloader. Flash recovery and flash supersu....any other step?
If they are not familiar with adb, I guess they may face trouble. Actually the problem occurs from the start at downloading adb tool(platform_tools on SDK) with that sucking google tool.
..However, if they are, they shouldn't do root. It's too risky if they don't even know the basics.
Click to expand...
Click to collapse
actually, wrong. if you have issues with adb, thats nice, but adb has NOTHING to with rooting a nexus device. rooting uses fastboot, not adb.
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
Rodeojones said:
So the instructions for how to root lollipop should be removed because some people don't take the time to read everything and confirm which version of Android they have on their phone?
Click to expand...
Click to collapse
removed, no. it should stay to show the history of rooting, among other things. but people should edicate themselves before ever rooting their devices. stupid people isnt an excuse to get rid of our history.
simms22 said:
actually, wrong. if you have issues with adb, thats nice, but adb has NOTHING to with rooting a nexus device. rooting uses fastboot, not adb.
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
removed, no. it should stay to shiw the history of rooring, among other things. but people should edicate themselves before ever rooting their devices. stupid people isnt an excuse to get rid of our history.
Click to expand...
Click to collapse
Ah.. you're right. Fastboot flash and unlock, right. I was talking about Android SDK(platform-tools) but it seems that I mistaked it, since I'm with adb console window for pulling something now(..)
PielunA said:
Ah.. you're right. Fastboot flash and unlock, right. I was talking about Android SDK(platform-tools) but it seems that I mistaked it, since I'm with adb console window for pulling something now(..)
Click to expand...
Click to collapse
thats alright.. seems as most accidentally say adb instead of fastboot, which isnt a big deal. unless youre a new user and keep trying to use adb to root.
Hey just trying to help the beginners. Take a look at this thread and tell me where it mentions its for lollipop.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Or where it mentions its not for Marshmallow. I'll save you the trouble. Nowhere.
I don't deserve all the ignorant remarks here. Uncalled for.
Some of you are right, taking it down is not the right path, but mentioning what version of Android its for is the right path.
Clay said:
Hey just trying to help the beginners. Take a look at this thread and tell me where it mentions its for lollipop.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Or where it mentions its not for Marshmallow. I'll save you the trouble. Nowhere.
I don't deserve all the ignorant remarks here. Uncalled for.
Some of you are right, taking it down is not the right path, but mentioning what version of Android its for is the right path.
Click to expand...
Click to collapse
then you have to think when it was written.. before marshmallow. before marshmallow, rooting was exactly the same for any nexus, all the way back to the nexus one. they had no idea that marshmallow would change things. what we can do as people is inform others of the changes.
Look at it from a beginners standpoint, which this site is always going to have plenty of. For them to know all that you mentioned is asking a lot. I am no longer going to bicker with everyone in this thread. Just wanted to help the beginners and share my view point as a beginner. I have learned a lot and appreciate all those that contribute to this site. Looking forward to rooting my phone and trying out some roms. Have a good day all.
Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated.
Click to expand...
Click to collapse
I can imagine your disappointment or frustration. But I can't agree with this post.
New things or methods do not need to work immediately for 100%. It is a process of creating, trial and error. And make things better every time. Stopping this process is fortunately impossible, but it should be also wrong. Because it's a free choice for everyone to be a part of it or not.
simms22 said:
then you have to think when it was written.. before marshmallow. before marshmallow, rooting was exactly the same for any nexus, all the way back to the nexus one. they had no idea that marshmallow would change things. what we can do as people is inform others of the changes.
Click to expand...
Click to collapse
NLBeev said:
I can imagine your disappointment or frustration. But I can't agree with this post.
New things or methods do not need to work immediately for 100%. It is a process of creating, trial and error. And make things better every time. Stopping this process is fortunately impossible, but it should be also wrong. Because it's a free choice for everyone to be a part of it or not.
Click to expand...
Click to collapse
So you believe that labeling a root method with the version of Android it works for and which version the method knowingly soft bricks you phone is not a good idea? Brilliant.
Clay said:
So you believe that labeling a root method with the version of Android it works for and which version the method knowingly soft bricks you phone is not a good idea? Brilliant.
Click to expand...
Click to collapse
well, if you root marshmallow the way you root any other nexus before marshmallow, it wont soft brick the device, it just wont gain root. i guess a soft brick is possible, but thats an easy fix. if it hard bricked devices, then thats a different story. but a soft brick can happen in a typical day of modding your device, and learning to fix a soft brick should be done before ever rooting your device.
Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Edit: This was meant to try to help beginners understand that the chainfire root method is for Lollipop and not for Marshmallow. I do not believe this should be taken down, just labeled for Lollipop so beginners don't soft brick their phones using this guide on a phone with Marshmallow.
Click to expand...
Click to collapse
Just read. Seriously. The last 10-20 pages of that thread are non-stop warnings and info, repeated over and over and over and over.
When you follow a guide, check the date, check the versions applicable, and read recent commentary for up-to-date information. If that is two hard, XDA DEVELOPERS is too hard for you...
Lets not encourage people to rampantly flash anything unless it has flashing red warnings... That is the wrong mentality. People should learn enough to understand what they are doing, not just be encouraged to follow the flashing red arrows.
We have the guide that we have, because it was the last one someone took the time to write, or because no one has written one the matches it since. All the information is in it... Even if you maybe have to read more then one post.
If you don't make something better, you have little right to complain. Its open source community development. We only have the things people made for us.
how i see any android mods or ways you do things.. if its 1 month or older, i assume that its out of date first. if no newer ways exist, then i try it. but i always make a backup in my recovery first, just in case. things move by within android relatively fast, so one month old can easily be out of date.
OK everyone. I get it. I am a beginner and should have gained complete knowledge of everything rooting and Android before starting this process.
I started this thread to try to help beginners that seem to, on a daily basis, use the chainfire root method on Marshmallow and soft brick their phones. Nothing more, nothing less. If having interest in helping these guys out before they go down the wrong road is wrong then tell me what is right. I am walking away from this thread as nothing good will come of it.
Clay said:
OK everyone. I get it. I am a beginner and should have gained complete knowledge of everything rooting and Android before starting this process.
I started this thread to try to help beginners that seem to, on a daily basis, use the chainfire root method on Marshmallow and soft brick their phones. Nothing more, nothing less. If having interest in helping these guys out before they go down the wrong road is wrong then tell me what is right. I am walking away from this thread as nothing good will come of it.
Click to expand...
Click to collapse
theres much good that has come from this thread already!
anyways, i learned all that i could learn before i ever first rooted(to an extreme maybe). i started with android two weeks before the g1 ever was released(got mine two weeks early). at the time, nobody knew anything about android. so, we all learned along the way. before rooting, i became the leader in the biggest android forums(at the time). only about 6 months after, i rooted my g1, before any legit root method ever existed. we learned, and we taught.. before any real methods existed. now that there are real methods, they change constantly as well, so we keep on learning and teaching