Anyone can tell me easiest way to flash stock image to Nexus 6 I am not very experienced with fast boot and Adb stuffs. Now my phone is getting "this device is corrupted...." Please help..
Btw I am on stock ROM + twrp recovery
The easy way is simply learning how to flash images through fastboot, using the command "fastboot flash [partition] [image.img]". The lazy way is through using a toolkit like Wugfresh.
use Nexus Root Toolkit , with one click you can do so much
AJDA said:
use Nexus Root Toolkit , with one click you can do so much
Click to expand...
Click to collapse
This is the single most dangerous thing you can suggest to someone new. Things like this are not really meant for new users. More for the ones that know what they are doing but are in a pinch for time.
zelendel said:
This is the single most dangerous thing you can suggest to someone new. Things like this are not really meant for new users. More for the ones that know what they are doing but are in a pinch for time.
Click to expand...
Click to collapse
i dont agree with you , there is guide for use this tool also how its dangerous to select the tgz file and flash all thing with one click for you in the same time
for me its more dangerous to use adb command , and for that reason is the developers create this tool to make it easy for us
plus you have a lot of options when you are brick or in normal mode
AJDA said:
i dont agree with you , there is guide for use this tool also how its dangerous to select the tgz file and flash all thing with one click for you in the same time
for me its more dangerous to use adb command , and for that reason is the developers create this tool to make it easy for us
plus you have a lot of options when you are brick or in normal mode
Click to expand...
Click to collapse
And when something goes wrong you come right back here asking for help. And when you tell people you used a one click method you find almost no help. If you don't know what you are doing with command lines then you really shouldn't be messing with your device.
There are very real risks. Even when using things like this.
@AJDA: On another thread a senior member asked me, incredulously, why I didn't push a toolkit. My answer was rather simple: the user needs to know how to use fastboot, as his next device may not have a toolkit available. On top of that, using fastboot is so easy the toolkits are ridiculous. Thus you have the easy way with fastboot and the lazy way with a toolkit.
For the record, the person asking for help in the first place on that other thread successfully used fastboot to restore his device. He learned something in the process and no longer needs a toolkit to do what everyone lately seems unable to accomplish without outside help.
The easy way is to use Wug's tool kit witch I highly recommended. However after you get you're phone back to normal you should really learn the fastboot method. It has saved my device's more time's than I can count,and is way more rewarding knowing you can do it yourself?
i have tried wugfresh toolkit to root yes it easy. but i tried restoring to stock image i keep failing & getting that error all over again and again, i tried 3x on the toolkit i cant get it to work. please help
And @zelendel's point is proven.
OP, search in general for the Nexus 6 all in one flashing guide and start reading.
Why when I flash TWRP or multirom I get that error?
Related
I'm going to be coming over as soon as Verizon officially picks this phone up (I know we can use it now but I'm using my Edge upgrade to purchase). I've seen sparring matches over it and want to know what is better and why? Is there really anything to argue or is it apples and oranges like when people fight over android vs. iphone? I'm not a developer but I'd like to think I'm pretty handy so even though I've never used adb I should be able to figure it out.
thegamerdarkseid said:
I'm going to be coming over as soon as Verizon officially picks this phone up (I know we can use it now but I'm using my Edge upgrade to purchase). I've seen sparring matches over it and want to know what is better and why? Is there really anything to argue or is it apples and oranges like when people fight over android vs. iphone? I'm not a developer but I'd like to think I'm pretty handy so even though I've never used adb I should be able to figure it out.
Click to expand...
Click to collapse
Firstly, you only use adb to push files to your phone. You unlock the bootlaoder using fastboot. Fastboot and adb are 2 completely different things.7
Please read my thread about this if you're unsure. Nexus 6 General > All-in-one guide > Question 28
In regards to which to use, thats up to you. Many senior members here would prefer you to use fastboot. Why? Because toolkits take away the understanding of the process. Its a very simple process anyway so there is no real need to use a toolkit and by using fastboot you're helping us. If you use a toolkit and get in to trouble later, we will try to help you fix it but the chances are, we will need you to use fastboot or adb. If you used a toolkit and do not understand these principles, it makes it much more difficult for us to help you fix your phone. So if you do not understand adb and fastboot, use them and learn them. Otherwise, we'll start losing patience if we're trying to hekp you fix your phone and also having to teach you the things every rooted user should already know.
On the other hand, if you're well versed in adb and fastboot, use what you want.
rootSU said:
Firstly, you only use adb to push files to your phone. You unlock the bootlaoder using fastboot. Fastboot and adb are 2 completely different things.7
Please read my thread about this if you're unsure. Nexus 6 General > All-in-one guide > Question 28
In regards to which to use, thats up to you. Many senior members here would prefer you to use fastboot. Why? Because toolkits take away the understanding of the process. Its a very simple process anyway so there is no real need to use a toolkit and by using fastboot you're helping us. If you use a toolkit and get in to trouble later, we will try to help you fix it but the chances are, we will need you to use fastboot or adb. If you used a toolkit and do not understand these principles, it makes it much more difficult for us to help you fix your phone. So if you do not understand adb and fastboot, use them and learn them. Otherwise, we'll start losing patience if we're trying to hekp you fix your phone and also having to teach you the things every rooted user should already know.
On the other hand, if you're well versed in adb and fastboot, use what you want.
Click to expand...
Click to collapse
Thank you, that was the exact answer I was looking for.
thegamerdarkseid said:
Thank you, that was the exact answer I was looking for.
Click to expand...
Click to collapse
No probs.
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
Anyone else having issues getting the new T-Mobile 28k update to work? I have downloaded it from the official Google images site. When I try to flash through nrt it will not boot after its flashed just sits at goolge on the device. I've also tried flashing each file individually through fastboot and still same issue. It's like there isn't a system image being flashed even though I flashed one.. Any suggestions? I'm puzzled
Sent from my Nexus 6 using XDA Free mobile app
I don't use the NRT, so can't comment on it.
When flashing using fastboot, what images did you flash? And were all successful? (If you flashed bootloader and/or radio, did you reboot bootloader after each of those?)
Did you flash cache.img? If not, flash the cache.img and see if that helps
beachbum40 said:
Anyone else having issues getting the new T-Mobile 28k update to work? I have downloaded it from the official Google images site. When I try to flash through nrt it will not boot after its flashed just sits at goolge on the device. I've also tried flashing each file individually through fastboot and still same issue. It's like there isn't a system image being flashed even though I flashed one.. Any suggestions? I'm puzzled
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I just finished flashing my phone to 28K with NRT. I was on 48M, unlocked it and flashed it to 28J and then flashed it to 28K using the image dowloaded from Google. I had the Force Flash option checked.
Sound more like you have a corrupted boot.img since it looping at the splash. Try fastboot a boot.img from a new or custom download. Have seen images corrupted on download.
jj14 said:
I don't use the NRT, so can't comment on it.
When flashing using fastboot, what images did you flash? And were all successful? (If you flashed bootloader and/or radio, did you reboot bootloader after each of those?)
Did you flash cache.img? If not, flash the cache.img and see if that helps
Click to expand...
Click to collapse
Yea I finally got it I don't know what is going on I used fastboot adb and manually flashed about 30 times and still bootloop. I gave up on nrt. I like the tool for time saving but like I said it refused to flash with nrt and manual fastboot then all the sudden it worked. I downloaded the 28K factory images about 30 times as well. If it was corrupted it just finally decided to work. I've never had an issue like this in the past.
Sent from my Nexus 6 using XDA Free mobile app
prdog1 said:
Sound more like you have a corrupted boot.img since it looping at the splash. Try fastboot a boot.img from a new or custom download. Have seen images corrupted on download.
Click to expand...
Click to collapse
Don't want to sound to ignorant but could you explain to me how these boot.img get corrupted? I'm sure that's what it was because when NRT was checking the images and it said to verify the hash mdn and I copied the mdn from Google's official site and pasted it in the dialog box on nrt it said match the first time when I tried to flashed 28K then it failed. Then I tried again and put the same mdn in the dialog box and nrt said mismatch. So I'm confused as hell.
Sent from my Nexus 6 using XDA Free mobile app
beachbum40 said:
Don't want to sound to ignorant but could you explain to me how these boot.img get corrupted? I'm sure that's what it was because when NRT was checking the images and it said to verify the hash mdn and I copied the mdn from Google's official site and pasted it in the dialog box on nrt it said match the first time when I tried to flashed 28K then it failed. Then I tried again and put the same mdn in the dialog box and nrt said mismatch. So I'm confused as hell.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Usually when get a bad download you can't unzip it. When they put these images inside the zip the zip is good but don't mean the image is good. That is why they give you an MD5 with the download. Under normal conditions such as rom download can pretty much tell if download is bad cause can't access the file with 7zip ect. It is different with the zipped images. Any one image can be corrupt. but zip is good. I have had downloads with either/or/and system.img or boot.img was bad and all the others worked. Hope this makes sense. Lol
---------- Post added at 12:07 AM ---------- Previous post was at 12:00 AM ----------
Skip the toolkits till understand how it works with manual fastboot. Will save a lot of head banging when you need to fastboot fix a toolkit fail. I have used toolkit to play with it. Had many fails and used fastboot to fix. If using toolkit never pick the lock bootloader option. Good way to brick the device.
prdog1 said:
Skip the toolkits till understand how it works with manual fastboot.
Click to expand...
Click to collapse
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.
NLBeev said:
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.
Click to expand...
Click to collapse
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Sent from my Nexus 6 using XDA Free mobile app
NLBeev said:
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.
Click to expand...
Click to collapse
I use adb fastboot and have manually installed plenty times. Tool kits are convenience
Sent from my Nexus 6 using XDA Free mobile app
beachbum40 said:
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Click to expand...
Click to collapse
Same here. Nice to meet you.
beachbum40 said:
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
timesaver toolkits are not, as things are quicker when done the right way. for example, it takes about 3 minutes to root your phone, if done the right way.
i tend to disagree on this one.
if the tool is made properly, all its doing is automating the commands and steps you would be using manually.
its not like its using a whole different method.
the tool could actually be better to use, if made properly, with Mfastboot. most users would use standard fastboot, instead of moto's fastboot, Mfastboot.
beachbum40 said:
I use adb fastboot and have manually installed plenty times. Tool kits are convenience
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Adb and fastboot are two completely different tools.
bweN diorD said:
i tend to disagree on this one.
if the tool is made properly, all its doing is automating the commands and steps you would be using manually.
its not like its using a whole different method.
the tool could actually be better to use, if made properly, with Mfastboot. most users would use standard fastboot, instead of moto's fastboot, Mfastboot.
Click to expand...
Click to collapse
Our point is using tool kits doesn't help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
All I was saying is I use both toolkit and fastboot. That's all. Thank you have a nice day?
Sent from my Nexus 6 using XDA Free mobile app
beachbum40 said:
All I was saying is I use both toolkit and fastboot. That's all. Thank you have a nice day?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I was just correcting you when you said "adb fastboot" as if it was one thing, not two unrelated things.
danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
i should have quoted simms last post.
i dont disagree with what you are saying, but do with the inference that toolkits use some inferior method, which isnt the case.
danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
your first line. toolkits does help the learning process. with that i disagree 1000000%. why? because the tool kits dont go through and explain each process to the user. they tend not to explain anything actually.
---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------
ok, toolkits.. they do work usually(every once in a while they do mess up). problem is with new users. toolkits dont teach them anything, not even basics, in case they mess up(and they do). by going through the rooting process the first time, properly, instead of toolkit, the user gets to learn the basics of every android process. by knowing thise basics, the yser can fix 99.99% of issues that pop up. with a toolkit, you dont get to learn the basics. so i tell everyone that toolkits are fine, just do thd rooting one time manually, then use the toolkit whenever you want after that.
simms22 said:
your first line. toolkits does help the learning process. with that i disagree 1000000%. why? because the tool kits dont go through and explain each process to the user. they tend not to explain anything actually.
---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------
ok, toolkits.. they do work usually(every once in a while they do mess up). problem is with new users. toolkits dont teach them anything, not even basics, in case they mess up(and they do). by going through the rooting process the first time, properly, instead of toolkit, the user gets to learn the basics of every android process. by knowing thise basics, the yser can fix 99.99% of issues that pop up. with a toolkit, you dont get to learn the basics. so i tell everyone that toolkits are fine, just do thd rooting one time manually, then use the toolkit whenever you want after that.
Click to expand...
Click to collapse
problem is, as long as there is a toolkit, 99% of people wont listen to you and will use the toolkit. there simply lazy and will never really appreciate any mods they do, because they did nothing more than click a few buttons...
bweN diorD said:
problem is, as long as there is a toolkit, 99% of people wont listen to you and will use the toolkit. there simply lazy and will never really appreciate any mods they do, because they did nothing more than click a few buttons...
Click to expand...
Click to collapse
thats ok, as long as at least one person listens then im not wasting my time. and i know that at the very least that at least one person has listened to my advice
the other 99%, some will think that their phone is bricked, some will go back and learn, some will be successfull with toolkits. and some just wont ever learn a thing
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
droidstyle said:
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
Click to expand...
Click to collapse
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
hadifreestyler said:
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
Click to expand...
Click to collapse
no you are bricked unfortunately. the unlock bootlader option in dev options really seems to have caused more issues then good.
I am wondering if Jtag will fix these devices?
jpl81905 said:
Suggestions?
Click to expand...
Click to collapse
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
scryan said:
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
Click to expand...
Click to collapse
Thank you. I think.
jpl81905 said:
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
Click to expand...
Click to collapse
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
backdown00 said:
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
Click to expand...
Click to collapse
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
danarama said:
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
Click to expand...
Click to collapse
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
backdown00 said:
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
Click to expand...
Click to collapse
..but even so, your method is overkill. It is really simple to boot into TWRP and look in the menu for the "Enable MTP" option. Once that is done, the phone appears in "Computer" as an MTP device, just like when you boot into android. Then, simply dragging and dropping a ROM onto that device then flashing it via recovery will get him back up and running. There is nothing simpler or quicker than this.
Sorry, I do not intend to be confrontational here.
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