[Q] First Nexus - Nexus 6 Q&A, Help & Troubleshooting

So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!

Cf auto root does not remove all data per se, but unlocking your phone will if it is not.. And it's part of the process.
Rooting probably doesn't affect OTAs, and if it does, can easily be undone.
Yes, I haven't found a common root app that isn't compatible.

Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
1. No it does not wipe your data unless your bootloader was locked.
2. It has no effect. You'll be able to accept the OTA and lose root (you can enable a survival script).
3. Yes.

Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:

TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.

zephiK said:
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
Click to expand...
Click to collapse
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.

TheSkillfulTroll said:
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
Click to expand...
Click to collapse
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.

For information sake (I have already rooted via TK) your post actually does prove a point. For myself and maybe others, would you be willing to P.M me the instructions to do it via ADB/Fastboot just in case , I , myself get screwed over. Thanks Z
Sent from my Nexus 6 using XDA Free mobile app

flash you phone manually you will learn a lot about how the toolkits work.
I find it faster to flash manually than to use a tool kit.
once an OTA is available you can grap the image from the google site and flash the files manually.
There is a way to manually flash you phone and save userdata so you keep all your apps.
One you learn and get a little practice It will be so easy you will be able to flash like it is second nature. (I was a noob that came from iphone and jailbreaking)
I can actually flash the files manually faster that an OTA can update a phone and I type with maybe a total of 6 fingers. because i never took a typing class

zephiK said:
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Sent from my Nexus 6 using XDA Free mobile app

if you have drivers installed already from first link above then you can follow these steps:
Download the required factory image files to your computer and extract them
1) Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
2) If all you want to do is unlock your bootloader, skip to step 6 in this section.
3) Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
4) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
5) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
6) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
7) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu just cd to the directory.
Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-some-description-number.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot format cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
I'm not the original writer of these instructions, but I found these helpful to people wanting the step by step instructions.

TheSkillfulTroll said:
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Click to expand...
Click to collapse
Read the first couple of posts of the following threads. The first talks about how to root, and the other, about how to flash the factory images. Very detailed.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
How true. I certainly don't want a paper weight...

Larzzzz82 said:
How true. I certainly don't want a paper weight...
Click to expand...
Click to collapse
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.

zephiK said:
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
Click to expand...
Click to collapse
I agree the hardest part for me was on windows trying to get the stupid drivers to work correctly.
Dumped windows for Linux and followed the manual steps i found on XDA and never looked back.
No drivers needed in Linux either.

TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?

miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app

TheSkillfulTroll said:
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah ok, this is what i was looking for.

miike1106 said:
Ah ok, this is what i was looking for.
Click to expand...
Click to collapse
Or... You could live dangerously and try a dirty flash first every time... Worst case... You go back and wipe in recovery

miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
You can dirty flash but this is only the case when you update from the same ROM to a newer update of the version.
When we say wipe, it only wipes the OS not internal storage.

Related

[Q] ICS Update for Nexus One

Hi,
My Nexus One details are as follows:
Model number : Nexus One
Android version : 2.3.4
Baseband version : 32.50.00.32U_5.12.00.08
Kernel version : 2.6.35.7-ge0fb012
[email protected] #1
Build number : GRJ22
Which is the best way for me to update my phone to ICS (Android 4.0). I have read the official message from Google on categorizing Nexus One as "old" and will no more air the updates.
I am not familiar with the MODs and so; eventhough I scanned through the ROM section; I couldn't figure out myself which way should I opt to upgrade my phone.
Thanks to all for reading my request as it might be a thousandth time such a request is coming through. Thanks for your patience and your advise is eagerly awaited.
Jabir
PS: I have never done a "jailbreak" or "rooting" (whatever name is it) on my phone except those Google aired updates.
You are going to have to root--no way around it
I did it the old fashion way and installed sdk/fastboot oem unlock/flash recovery and a rom with super user in it or flash super user
instructions are in Wiki
there are different ways now I am not familiar with, but prefer the sdk method
you will also need to be on hboot 35.0017 to install blasckrose, although some ICS roms have a miniversion that can run on stock hboot
However, I would root and flash some roms like CM7 stable to get use to things. The hboot and ICS is a bit more complicated at first--read the threads carefully before attempting
Start reading.
http://forum.xda-developers.com/showthread.php?t=1366897
ursJAR said:
Hi,
My Nexus One details are as follows:
Model number : Nexus One
Android version : 2.3.4
Baseband version : 32.50.00.32U_5.12.00.08
Kernel version : 2.6.35.7-ge0fb012
[email protected] #1
Build number : GRJ22
Which is the best way for me to update my phone to ICS (Android 4.0). I have read the official message from Google on categorizing Nexus One as "old" and will no more air the updates.
I am not familiar with the MODs and so; eventhough I scanned through the ROM section; I couldn't figure out myself which way should I opt to upgrade my phone.
Thanks to all for reading my request as it might be a thousandth time such a request is coming through. Thanks for your patience and your advise is eagerly awaited.
Jabir
PS: I have never done a "jailbreak" or "rooting" (whatever name is it) on my phone except those Google aired updates.
Click to expand...
Click to collapse
0. Set up ADB correctly.
1. Root.
2. Optional: Unlock the bootloader
3. Optional: Set SecuFlag off, i.e. S-OFF
4. Fastboot flash a custom recovery
5. Fastboot flash blackrose's hboot. Either stock blackrose or the one specifically for ICS (custom partition layout)
6. Download an ICS ROM of your choosing. My pick would be texasice's.
7. Download an A2SD script as the default one is a li'l buggy.
8. Boot into the recovery of your choosing (4EXT or AmonRa preferred)
9. Make a FULL wipe of settings and partitions and wipe cache and dalvik cache.
10. Flash the ROM zip file
11. Flash the A2SD script file
12. Reboot and boot up your phone. Enter a terminal emulator. Type: su
13. Accept the root request and then type a2sd install,
14. Let your phone reboot on its own and then boot it up again,
15. Return to the terminal emulator, type su and then a2sd cachesd and let it reboot once more.
16. Now you're good to go.
Find out all info on your own, I simply tell you what you need to do.
Theshawty said:
0. Set up ADB correctly.
1. Root.
2. Optional: Unlock the bootloader
3. Optional: Set SecuFlag off, i.e. S-OFF
4. Fastboot flash a custom recovery
Click to expand...
Click to collapse
If you are going to be using fastboot to flash a custom recovery, root is not needed and unlocking the bootloader is not Optional. Root is only needed if you are going to flash the recovery through Android with a program like ROM Manager. Also, S-Off also is something we can't officially get with our phones without using the XTC Clip. But for pretty much all things that we need to do with our phones, S-Off is not required due to it being a dev phone.
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
I only started modding recently (a month ago) and in that time, I've already moved to ICS and using a custom Blackrose HBOOT. Its fairly easy - you just have to have the ability to read patiently.
Here is what I would advise, being a bit of a noob myself - yet having never had a single hiccup. This is pretty much the fastest way to do it.
1. Enable USB debugging (in settings>applications>development)
2. Download SuperOneClick (Google it, also has USB drivers if necessary)
3. Connect your phone to the computer, and once all drivers are installed, fire up SuperOneClick, hit 'Root' and watch the magic unfold
4. Download ROM Manager from the Market, follow the instructions (Flash recovery>Download a ROM (CM7 recommended))
Once you are familiar with the basics of installing a ROM from ZIP, head over to the Dev forums, and download ICS for stock HBOOT to get you started!
mrhohoha said:
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
Click to expand...
Click to collapse
This is true. I was just going off the instructions that Theshawty wrote. In the instructions he included directions to use fastboot. And without replacing the bootloader to Blackrose (which is probably too in depth to do include here), using fastboot would require the bootloader to be unlocked.
bassmadrigal said:
If you are going to be using fastboot to flash a custom recovery, root is not needed and unlocking the bootloader is not Optional. Root is only needed if you are going to flash the recovery through Android with a program like ROM Manager. Also, S-Off also is something we can't officially get with our phones without using the XTC Clip. But for pretty much all things that we need to do with our phones, S-Off is not required due to it being a dev phone.
Click to expand...
Click to collapse
I have S-OFF'd my device and I didn't use anything called XTC Clip?
Yep. Nothing special required for S-OFF. Heck, you can S-OFF in like 20 seconds by just installing Blackrose! And revert to stock S-ON HBOOT whenever you like!
Using Blackrose does not actually make your device S-Off. The upgraded HBOOT just ignores the flag that is set saying the S-On is still there and displays that you are S-Off. And so, essentially you have S-Off when you use blackrose, but that is only because blackrose ignores the actual setting saying the S-On is still in place. The one thing this will not allow is relocking the bootloader, which full S-Off, when acheived with the XTC Clip, will do.
mrhohoha said:
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
I only started modding recently (a month ago) and in that time, I've already moved to ICS and using a custom Blackrose HBOOT. Its fairly easy - you just have to have the ability to read patiently.
Here is what I would advise, being a bit of a noob myself - yet having never had a single hiccup. This is pretty much the fastest way to do it.
1. Enable USB debugging (in settings>applications>development)
2. Download SuperOneClick (Google it, also has USB drivers if necessary)
3. Connect your phone to the computer, and once all drivers are installed, fire up SuperOneClick, hit 'Root' and watch the magic unfold
4. Download ROM Manager from the Market, follow the instructions (Flash recovery>Download a ROM (CM7 recommended))
Once you are familiar with the basics of installing a ROM from ZIP, head over to the Dev forums, and download ICS for stock HBOOT to get you started!
Click to expand...
Click to collapse
The SuperOneClick Application just gets not responding when I click the Root button and after these messages on the right pane are shown
* daemon not running . starting it now on port 5037 *
* daemon started successfully *
Please advise..
Make sure you run it with administrator rights (right click to see the option), and verify that USB Debugging is turned on on the phone. If it is turned on, you need to make sure you have the adb drivers installed (different than the standard USB drivers that windows automatically installs).
Hi all. I have read quite a few pages of the s off blacks install guide. Not really getting it. Can someone please give me simple steps to install blackrose?
Please and thank you.
Sent from my Nexus One using xda premium
Blackrose install guide
Sent from my Nexus One using xda premium
hardrockinandroid said:
Blackrose install guide
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
Black rose thread http://forum.xda-developers.com/showthread.php?t=1270589
I've read that and everything sounds so complicated. I've watched the vid for resizing partition but they don't say anything. Can someone give a step by step for us noobs for resizing partition please?
Sent from my Nexus One using xda premium
do you have all requirements met from br op page
if so, you need to download the latest br from op and extract it to the download folder you just downloaded br to. then open the extracted folder and clickon br.exe
follow instructions inside the command window that opens
then you need to resize partition to ics sizes thru the breditor
What is op page?Yes bootloader unlocked. Rooted. I have the blackrose zip.the adb and fastboot drivers for windows. Don't know what to do now. I put both files on my desktop. Now what?
Sent from my Nexus One using xda premium
OP page is first page of Dev's thread--mmm
Needs read as well as most of thread to get an understanding of this--lots of folks are running into big trouble if they don't understand it first--
If you are rooted and unlocked do you have sdk installed and can you run adb devices and fastboot devices in command window and see phone's serial number? If so you don't need the usb drivers from OP page--
Yes I have ran commands on a my touch4g, a HTC sensation and a g 2x. Do I just do exactly as the YouTube video shows and then flash the blackrose zip after resizing
the partition? Then flash an Ics Rom?
Sent from my Nexus One using xda premium

HTC One Dev edition root question

Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2
Mindstar1 said:
Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off
Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root
Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root
Click to expand...
Click to collapse
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2
What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off
Click to expand...
Click to collapse
How do I check which hboot I have?
Sent from my HTC One using Tapatalk 2
At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app
NxNW said:
At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
OK, I just did what you said and the HBOOT is 1.44.0000. So, based on what was said earlier, I am good to do the Revone option? If I do Revone, what am I missing out on compared to any other option? Thanks for the help!
Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.
Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Mindstar1 said:
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Click to expand...
Click to collapse
Yeah, I want to flash. If all I do is root, am I still able to flash other ROMs? I can never keep straight what each of the different processes do.
NxNW said:
Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.
Click to expand...
Click to collapse
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942. My goal is to flash 4.2.2 roms and soon 4.3, so would I want to do both or just Revone.
Mindstar1 said:
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942.
Click to expand...
Click to collapse
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.
NxNW said:
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.
Click to expand...
Click to collapse
Its funny, I came across the first article while looking for answers while I waited for your response. I never mess with radios so S-Off is not really important to me. The second article was even better and more clear so I think I know where I am now.
The last question for you is what you would suggest I use for the most trouble free rooting process. I am looking for a pretty low impact route, and you did seem to imply that it took some work to get revone working for you. The toolkit seems to be a good way to go, but it also says that it unlocks the boot, which I already have with the dev edition. Will that be a problem if the process tries to unlock an already unlocked phone?
Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.
NxNW said:
Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.
Click to expand...
Click to collapse
I ran into an issue following your directions (which were basically the same as the YouTube video about the "easiest way to install custom recovery for the htcone" that I got off another xda thread. I run the command to fastboot flash recovery, and my PC gives me an error saying that fastboot is not a valid command. I have the proper drivers installed, and I am in fastboot on my phone but it won't work. I did notice that on the thread you linked to above, they want my recovery file to be in some sdk folder or something. My directions didn't mention that and the directions you linked to mention an sdk file in the bootloader section, but it tells me to skip that if I have a dev edition. Is the sdk file the reason why my computer won't recognize the command? For what it's worth, I tried that toolkit and it did not seem to recognize my phone either.
Sent from my HTC One using Tapatalk 2
EDIT Just a general tip - you can copy the text of any error message you get and paste it into google and you will doubtless turn up a bunch of interesting info - you are very likely not the first person to encounter the issue.
Anyway here's what I think is happening:
Sometimes when you try to give a command from the command line, a computer doesn't know where the necessary executable file is.
If the SDK was installed ok , then somewhere on your computer is the actual fastboot.exe executable.
Find it.
If it is in a folder called C:\path\to\files\blah\blah then you need to actually type out C:\path\to\files\blah\blah\fastboot.exe to run it.
If you will be doing more commands in this location or any commands that refer to other files in the same location (and some if these procedures assume you will since you'll be putting the flashable image files in this location), you really should tell your terminal program to just change the "working directory" to that location: then whenever you refer to something the computer will look there first. Here's how that looks:
cd C:\path\to\files\blah\blah
fastboot
(Final note- going forward you can make it easier to launch executables by adding their location to your "PATH variable" - google it. )
Maybe you knew all this? But for the benefit of anyone else following these bread crumbs, here's the upshot: Most of these "procedures" that people write down assume some general knowledge of command line syntax. If you're not comfortable with that yet, you're going to need to be persistent and search google a lot.

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...

Bricked Nexus 6

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.

Easy to follow Root Steps for Stock Android 6.0?

Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
TPADroid said:
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
Click to expand...
Click to collapse
First this does not belong in the Development sections, moved here. Secondly please read the Forum Rules on posting...thanks.
Thank you for moving to the appropriate location.
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
simms22 said:
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Click to expand...
Click to collapse
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
The boot.img files that your referring to are probably to un-encrypt your phone. I personally don't but other always have. Supposed to make it faster although i haven't been bothered by it being slow.
To unlock the bootloader all you have to do is used fastboot oem unlock via fastboot while your phone is in the bootloader mode.
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
mbiscuits said:
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
Click to expand...
Click to collapse
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
thats a kernel thatll let you unencrypt, if you want.
simms22 said:
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
Click to expand...
Click to collapse
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
mbiscuits said:
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
Click to expand...
Click to collapse
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
mbiscuits said:
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
Click to expand...
Click to collapse
which is why i always recommend that someone new root their phone the proper way the first time, to learn how to do it, and to learn a general way to fix your phone in case you mess up. after the first time, use toolkits all you want. but the learning how to do it properly is a very important.
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
That modified img allows for root because you cant just flash SU on the stock one (not yet anyway). Unlocking the bootloader is something different.
simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
Anybody knows where is the correct toolkit?
cpugeeker said:
Anybody knows where is the correct toolkit?
Click to expand...
Click to collapse
in my opening, there is no 'correct" toolkit.
Jnewell05 said:
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
If you haven't rooted for over a year why do it now? There are sure to be updates to how to root on the Nexus 6 and since I don't use my nexus 6 very much I hate to steer you in the wrong direction, as to backup information. I recently got the android 7.0 update and I haven't really had a chance to check it out yet. But I bet there are dozens of ways to backup if you would search Google.
Sent from my SAMSUNG-SM-G935A using Tapatalk
jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
istperson said:
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
Click to expand...
Click to collapse
Thank you very much!!!!

Categories

Resources