Database Develop

The Recovery Battle: WCX vs Twrp vs CWM

What recovery do you guys prefer?
I've seen a lot of Vivids with WCX these days.
Post your experience with each one!

Stock CWM ftw

CWM still has a lot of issues. It's been causing quite a few hard bricks. Anyone that still has it, I would highly suggest switching to WCX recovery. I have yet to try TWRP but from what I've heard from all the devs, it still has a few kinks. I wouldn't recommend anything other than WCX at the moment.
I don't really see it as whats "preferred". You don't want something on your device that can potentially cause a hard brick. A recovery is something you don't use very often, so it's best to go with the one that just works.

Nice answer, right now I'm on the stock RUU ICS rom with an unlocked bootloader and I want to flash the WCX recovery, I just have to put the wcxrecovery.img in the microSD root, enter in Hboot, select recovery and then flash it with "fastboot flash recovery wcxrecovery.exe"?
Do I have to make a backup of something after doing this?
Thanks in advance for your answer.

Archector said:
Nice answer, right now I'm on the stock RUU ICS rom with an unlocked bootloader and I want to flash the WCX recovery, I just have to put the wcxrecovery.img in the microSD root, enter in Hboot, select recovery and then flash it with "fastboot flash recovery wcxrecovery.exe"?
Do I have to make a backup of something after doing this?
Thanks in advance for your answer.
Click to expand...
Click to collapse
Actually, just put the wcxrecovery on your computer where you have adb and fastboot set up. If you don't know where that is, just download the wcxjb root zip from the guide in my signature and unzip it to your desktop. Enter hboot on your phone and select fastboot. Shift + right click on your computer inside the folder you just unzipped and select open a command window here. THEN, type in the command "fastboot flash recovery wcxrecovery.img" and you're good to go.

slapshot30 said:
Actually, just put the wcxrecovery on your computer where you have adb and fastboot set up. If you don't know where that is, just download the wcxjb root zip from the guide in my signature and unzip it to your desktop. Enter hboot on your phone and select fastboot. Shift + right click on your computer inside the folder you just unzipped and select open a command window here. THEN, type in the command "fastboot flash recovery wcxrecovery.img" and you're good to go.
Click to expand...
Click to collapse
Crap I moved back to linux after I s-off'ed, is there anyway I can use fastboot without having to dig out my aging Pentium 4?

Brand New said:
Crap I moved back to linux after I s-off'ed, is there anyway I can use fastboot without having to dig out my aging Pentium 4?
Click to expand...
Click to collapse
I know it's possible, but I've never tried it. The best tip I've picked up from the guide was this
- Tip 3: On Linux, remember to run fastboot under sudo
Click to expand...
Click to collapse
If you have any idea what that means, it may be of help to you.

Stock CWM. Never used anything else, never had problems, never plan to use anything else.

Brand New said:
Crap I moved back to linux after I s-off'ed, is there anyway I can use fastboot without having to dig out my aging Pentium 4?
Click to expand...
Click to collapse
Just download and install the Android SDK for linux, what distribution are you using?
I suppose you're using Ubuntu or some .deb based distribution, this tutorial may serve for you:
Running something on "sudo" is giving superuser attributes to the processes and services that a program or whatever you are running needs to have to function properly. Yes it's important when you flash with fastboot.
If you can flash on a laptop will be better for you, a friend of mine bricked his galaxy sII when he was flashing and there was an electricity short.

Archector said:
What recovery do you guys prefer?
I've seen a lot of Vivids with WCX these days.
Post your experience with each one!
Click to expand...
Click to collapse
I use the recovery-beta2 recovery from thecubed. I tried WCX but I couldn't get any ROM's to flash with it... nothing but bootloops for some strange reason (yes I fastboot flashed the boot.img first people). I reflashed thecubed's recovery right after having issues and flashing ROM's worked again. I'm sticking with what works and I've had zero issues with thecubed's recovery after using for several months.

I know I sound redundant, but does anyone have a link to the latest WCX recovery?

You have to download from WildChild's website.... It's included in his ROM zip. You have to have 10 posts on his site before you can download anything so be prepared to "earn" the download.
Sent from my HTC PH39100 using xda premium

dusty2422 said:
I use the recovery-beta2 recovery from thecubed. I tried WCX but I couldn't get any ROM's to flash with it... nothing but bootloops for some strange reason (yes I fastboot flashed the boot.img first people). I reflashed thecubed's recovery right after having issues and flashing ROM's worked again. I'm sticking with what works and I've had zero issues with thecubed's recovery after using for several months.
Click to expand...
Click to collapse
Did you use the recovery un-installer to get rid of CWM before you tried the WCX recovery? I remember some people having issues trying to use WCX over one of the previous CWMs without un-installing it first.

Actually your incorrect,its available freely from the rooting flashing thread on here...as far as earning something....dont like participation dont use my work either way tomorrows another day and life goes on now doesnt it....theres no entitilement to [email protected] "earned" comment....
WC
dusty2422 said:
You have to download from WildChild's website.... It's included in his ROM zip. You have to have 10 posts on his site before you can download anything so be prepared to "earn" the download.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse

Some people just throw stuff out like they know what's going on... Wow get facts right first bro

Y'know if CWM loops, it's because your rom of choice had a useless ext4 performance tuning script in it that changed some of the mount options of /cache.
If you have CWM and find that after flashing a ROM that does weird things to your Vivid, just reboot to fastboot, then issue "fastboot erase cache" then boot to recovery and format /cache.
CWM hasn't caused any hard bricks, it's ROM developers that aren't properly checking their 'init.d tweaks' and updater-scripts. Now that we have s-off, a bad tweak or updater-script can and WILL make your phone hard to fix.

just used TWRP on my Sprint Gnex and love the interface! I used CWM on my old Epic 4G and it worked great too. To me, seeing all the options on that screen is easier....seems stable.
---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------
Great point but how would the average Joe know that about a rom before a flash? I'd love to be able to know that and avoid bricking altogether (but wouldn't we all). any tips?

Wild Child said:
Actually your incorrect,its available freely from the rooting flashing thread on here...as far as earning something....dont like participation dont use my work either way tomorrows another day and life goes on now doesnt it....theres no entitilement to [email protected] "earned" comment....
WC
Click to expand...
Click to collapse
I don't mind participation... I just find it hard to participate in a forum where I can't download anything. Kind of hard to comment on something that you can't download IMO.
robertmoore208 said:
Some people just throw stuff out like they know what's going on... Wow get facts right first bro
Click to expand...
Click to collapse
Not sure if this was directed at me but I'll assume it is. WC closed all of his dev threads on XDA (Vivid forum at least) which is why I assumed it wasn't here anymore (yes I searched before replying). Not sure that I've ever seen dev related content stuck in a [GUIDE] thread (maybe a link to the thread that has it) so not sure why this was the place chosen and probably why I missed it. Apparently I'm not the only one since I've seen multiple people asking who can't find it. I appreciate you keeping me honest though "bro".

Archector said:
What recovery do you guys prefer?
I've seen a lot of Vivids with WCX these days.
Post your experience with each one!
Click to expand...
Click to collapse
WCX all the way, ROM's, Recovery, & Kernel. Now, I'm not trying to say that CWM doesn't work, I used it alot when I was rooting & flashing my Aria... but I've had nothing but 100% success using WCX Recovery & ROM's since before I started beta testing for him (along with all the other dedicated members).
I've never used TWRP before, & all I think about when I see that word is Big Booty Shaking!!! ;-)

WCX! I have to say that EVERYTHING that he and his team put out is top notch!

[Q] First Nexus

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.

How to root the HTC One M9 on T-Mobile (Windows)(S-Off too!)(Works on .33 update)

For RUUs, stock recoveries, stock Nandroids (in case you need to return to stock, unrooted), TWRP links, and other important tools, please check this thread by Rydah805. It has the stuff you want.
Note: S-Off link at the bottom of the OP. You'll need the HTCDev unlock method completed first and you'll need root access to make it work. So once you're done with this little guide (or the noob friendly one in the HTC One international forums here), you can hop right on over to Sunshine (linked at the bottom) to get that done if you don't mind the $25 fee.
I can confirm this works on the following:
Android 5.0.2
HTC Sense Version 7.0
Software Number 1.32.531.25 (tested and working with software update 1.32.531.33)
Kernel Version [email protected] #1 SMP PREEMPT
Baseband version 01.01_U11440251_64.04.50312G_2_F
Build Number 1.32.531.25 CL505029 release-keys
As usual, you do this at your own risk. It's not my fault if you mess things up (although I sympathize completely if you do). I cannot confirm this works on any other version than this one, although I've seen this work on the AT&T, Verizon, Sprint, and International variants. Feel free to link there or just copy paste the whole damn thing and post it over in those forums to make it easier for those folks. I really, honestly don't mind.
It took me a while so I figured i'd make a thread on it to make it easier for our fellow T-Mobile M9 peoples. This is essentially a link dump so you can get to the places you need to go faster. Before continuing, please read this advice from Rydah805 because it's invaluable. Thankfully, we won't be using the 2.8.5.0 version of TWRP in this quick tutorial but the important part of the message is that you should make a nandroid of the unmodified stock ROM BEFORE rooting. Otherwise you will have many problems down the line. If you have thanks to give, give them to the posters of all these various threads. I did nothing special, just went through the steps to see how it worked.
Please note, if you're using Mac or Linux, I don't use those things and couldn't try/test/use the root method on those platforms. I assume Linux works pretty much the same way as Windows (you'll have to get ADB/Fastboot a different way of course).
Let's get started
Pre-requisites:
1. You'll need SuperSU by Chainfire. You can download it here. Put this on your device where you can find it later. I've seen people say it needs to be on an external SD card, but I've seen it work from both internal and external.
2. You'll need a modified version of 2.8.6.0 of TWRP. You can download that here. The link is at the bottom of the post where it says "Beta version with system backup fixed...". That's the one you want.
3. You will need ADB and Fastboot. I recommend Minimal ADB and Fastboot. You can find that here. Install it like any other Windows application AND MAKE SURE TO LET IT CREATE A DESKTOP ICON. This will make finding it later much easier. Linux users will need to find a different way to get ADB/Fastboot. Probably just downloading the SDK...although if you're running Linux you know all this already so let's just move on.
4. You'll need the HTC One drivers. I did this by installing HTC Sync Manager and it worked fine for me. You can download the HTC Sync Manager here.
Okay now for the actual root method.
1. First you'll need to unlock the bootloader using HTDdev.com. Follow this tutorial to do that.
2. Once your bootloader is unlocked. You'll want to flash the TWRP recovery to your HTC One M9. Rename the TWRP file you downloaded in the pre-requisits it to "recovery" (no quotes, and the .img shouldn't be visible) and place it in the Minimal ADB and Fastboot folder on your COMPUTER. For windows, this is usually under your C drive > Program Files (x86) > Minimal ADB and Fastboot.
3. On your One M9, turn it off. Press the volume down key and power simultaneously and you'll get a black screen. Using the volume keys to scroll, go to Download Mode and click the power button to confirm.
4. On your computer, open Minimal ADB and Fastboot using the icon I told you make earlier (you listened, right? ). If you renamed the TWRP image you downloaded earlier to "recovery" and put it in the proper folder as I stated earlier, then all you need to do is type the following:
Code:
fastboot flash recovery recovery.img
5. At this point the recovery should flash successfully. HOWEVER, in my experience, you may get some silly errors (unknown error, Fastboot crashed, too many links, etc). If this is the case, don't panic. Turn the device off, re-enter download mode again, close the command window and re-open Minimal ADB and Fastboot and try again. All I did to get it to work was try a couple of times over again. Sometimes it goes, sometimes it doesn't. Silly Windows being silly I presume.
6. Okay, you should now have recovery. Enter recovery by pressing and holding volume up and volume down while pressing power to enter bootloader mode. Scroll using the volume keys to "Recovery" and hit the power button. You should now be in a weird looking TWRP. This is normal.
7. CREATE A FREAKING NANDROID BACKUP RIGHT NOW. According to some recognized members of the community, HTC updates only work on an unmodified system. If you ever want to receive official updates from HTC, you HAVE to create a NANDROID RIGHT NOW. Do it. I'll wait.
8. Did you create a Nandroid yet? No? You naught boy/girl, go do that now please.
9. But no really, create a Nandroid please.
10. Once your Nandroid is complete and you have an unmodified, unrooted system backed up, we can actually root the damn thing. You should have SuperSU on your device (as per the pre-requisites). If not, go download that using the link I provided above and put it on your device. Anywhere should be fine.
11. Okay now here's the tricky part. TWRP boots into recovery as Read Only but ONLY on unmodified systems. The reason for this is because HTC updates can't install if the recovery is read/write enabled. Since you're not yet rooted, your TWRP is booting up to Read Only. That means even if you flash SuperSU right now, it won't actually do anything because TWRP can't write to /system (yes, it will say it flashed successfully, it's a liar liar pants on fire).
12. To overcome this, you'll need to follow the instructions in this post.
13. Once you have manually mounted the system partition using the post I linked above (did you thank him? I think you should've thanked him), you may now flash SuperSU.zip as you normally would.
14. Reboot, and you should now be rooted. Don't forget to install BusyBox (search "busybox" in the Google Play Store, download the one developed by Stephen (Stericson). Once installed, open it, give it Superuser permission, then just hit install). Once busybox is installed, you will have the full root experience and can use apps like Titanium Backup.
And that should do it folks. Again, don't thank me, all I did was gather links and put the steps in order. The other people deserve your praise.
Now as for updating, I don't know how it will work yet, but this is how I believe it'll work in theory.
If you have a system update:
1. Create a titanium backup of all of your apps (trust me).
2. Reboot to recovery, restore your unrooted, unmodified Nandroid that I told you literally 5 times to make.
3. Reboot, then check for updates. Install the system update.
4. Re-root your device using the steps above (by then I'm sure there will be a more stable TWRP, make sure you always have the most updated one!)
5. Restore your apps via Titanium Backup.
Again, that's how I believe it should work in theory but I won't know for sure until I receive a system update.
IF YOU HAVE PROBLEMS, please contact the smarter people in the threads I linked who are actively working on helping people with issues. I suppose you can post them here, but as you can see by my post count, I rarely pay much attention
Enjoy!
*Edit*
Bonus points: Our device is compatible with the S-Off method brought by Sunshine. It's a $25 purchase but it does work (tested) and I've seen people report that it works on the .33 update as well. Click here to check out Sunshine.

great write up. mind making a stock backup with the beta 2.8.6.0 twrp and posting it?

Rydah805 said:
great write up. mind making a stock backup with the beta 2.8.6.0 twrp and posting it?
Click to expand...
Click to collapse
I could, definitely. Maybe create a clean one (without my stuff logged in) and upload here...what would I have to include so people could actually use it? I've never tried restoring a borrowed Nandroid backup before lol.

All you need to post is system and boot. You don't need to wipe your info, all of that is stored on the data partition, which we don't necessarily need. So just backup using the beta TWRP 2.8.6.0 you mentioned and zip and upload the following files:
Boot.emmc.win
Boot.emmc.win.md5
Recovery.log
System.ext4.win000.win
System.ext4.win000.win.md5
System.ext4.win001.win
System.ext4.win001.win.md5
System.ext4.win002.win
System.ext4.win002.win.md5
System.info
Click to expand...
Click to collapse
The ".md5" files are only created if you have the generate md5 option on in TWRP. If this option isn't enabled, they aren't necessary.
I hope you haven't used TWRP 2.8.5.0 on your M9 at all. Have you?
Edit:
I'm assuming you have root already and what we need is an untouched system partition. If you haven't touched the system partition then we are good, but if not, don't bother making a backup. The easiest way to check if your system partition is still good to use for OTA's, boot into TWRP and go to the mount options and if "System" is an option, it's no good and a stock backup from that particular device is useless, but if the "System" option isn't there, please make the backup and share it. Lol
Sent From My HTC One (M9)

Rydah805 said:
All you need to post is system and boot. You don't need to wipe your info, all of that is stored on the data partition, which we don't necessarily need. So just backup using the beta TWRP 2.8.6.0 you mentioned and zip and upload the following files:
The ".md5" files are only created if you have the generate md5 option on in TWRP. If this option isn't enabled, they aren't necessary.
I hope you haven't used TWRP 2.8.5.0 on your M9 at all. Have you?
Edit:
I'm assuming you have root already and what we need is an untouched system partition. If you haven't touched the system partition then we are good, but if not, don't bother making a backup. The easiest way to check if your system partition is still good to use for OTA's, boot into TWRP and go to the mount options and if "System" is an option, it's no good and a stock backup from that particular device is useless, but if the "System" option isn't there, please make the backup and share it. Lol
Sent From My HTC One (M9)
Click to expand...
Click to collapse
I followed my exact instructions before I posted them I got my device last night and did all of this today (in fact, I wrote it as I completed each step). I have an untouched /system in my nandroid and my TWRP was only 2.8.6.0. Curiously enough, my Nandroid has a system.emmc.win and boot.emmc.win...will that be a problem? I flashed the 2.8.6.0 modified one that allows for backups beforehand but I don't have ext4 I guess.

DunningKrugerEffect said:
I followed my exact instructions before I posted them I got my device last night and did all of this today (in fact, I wrote it as I completed each step). I have an untouched /system in my nandroid and my TWRP was only 2.8.6.0. Curiously enough, my Nandroid has a system.emmc.win and boot.emmc.win...will that be a problem? I flashed the 2.8.6.0 modified one that allows for backups beforehand but I don't have ext4 I guess.
Click to expand...
Click to collapse
Must be my setup. Yours should be perfect. Looking forward to downloading a copy. ? thanks in advance.
Sent From My HTC One (M9)

Could someone please upload the stock recovery for this phone? I need it because I'm interested in flashing TWRP and rooting the phone but I need the stock recovery in case an OTA update hits.

Prasad said:
Could someone please upload the stock recovery for this phone? I need it because I'm interested in flashing TWRP and rooting the phone but I need the stock recovery in case an OTA update hits.
Click to expand...
Click to collapse
When an OTA arrives, download it and it'll contain the stock recovery. By then, I'll post it...
Sent From My HTC One (M9)

Rydah805 said:
When an OTA arrives, download it and it'll contain the stock recovery. By then, I'll post it...
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Thanks! I tried to flash TWRP and got this:
$ fastboot flash recovery twrp-2.8.6.0-hima.img
sending 'recovery' (35928 KB)... OKAY
writing 'recovery'... FAILED (remote: cannot flash this partition in s-on state)
Click to expand...
Click to collapse
EDIT: Never mind.. Got it to work!

[Q] Any benefit to unlock bootloader only?
So I have rooted many of my phones and just received my M9 last night. Not really interested in rooting it just yet. Although I was curious if there is any benefit to only unlocking the bootloader. or just wait for when I root it?

Gravityrat said:
So I have rooted many of my phones and just received my M9 last night. Not really interested in rooting it just yet. Although I was curious if there is any benefit to only unlocking the bootloader. or just wait for when I root it?
Click to expand...
Click to collapse
Unlocking the bootloader gives you access to installing custom ROMs, kernels and rooting the phone. You only really need to unlock it if and when you're doing any of these.

Figured as much. I wanna run it stock for a bit to see how it runs. I will admit, I am impressed with the battery life so far. I made it 12 hours at work with 17% left when I got home.

Worked for me. Thanks

Am I missing something? While in recovery, after I've already made a backup(It's uploading) I go to advance>terminal and I type in
Code:
mount -t ext4 /dev/block/bootdevice/by-name/system /system
it returns
Code:
mount: mounting /dev/block/bootdevice/by-name/system on /system failed: Device or resource busy
Edit: Apparently it still worked.

Here is a TWRP backup of my phone right after I unlocked it, so it should be completely stock. I didn't remove any of the files, so the data files are in there as well. (Again, right after I wiped from unlocking)
Just drag the folder into your twrp backup folder and you should be good to go.
Goolge Drive

xxquicksh0txx said:
Here is a TWRP backup of my phone right after I unlocked it, so it should be completely stock. I didn't remove any of the files, so the data files are in there as well. (Again, right after I wiped from unlocking)
Just drag the folder into your twrp backup folder and you should be good to go.
Goolge Drive
Click to expand...
Click to collapse
mind if i link that in my thread?

Rydah805 said:
mind if i link that in my thread?
Click to expand...
Click to collapse
That's what it's there for
:good:

does anybody know if this works on mac?

child0fdecadance said:
does anybody know if this works on mac?
Click to expand...
Click to collapse
I unlocked, flashed TWRP, backed up and rooted the M9 on a Mac.

Prasad said:
I unlocked, flashed TWRP, backed up and rooted the M9 on a Mac.
Click to expand...
Click to collapse
sweet! did you have to change any of the procedure or did you do it step by step?

CyanogenMod 12.1 for the HTC Desire 510

Introduction
Hello! It's time for some fresh blood to get a chance to have some fun. Continue reading if you care about my semi-personal details. If not, then skip down below. I'm r3pwn, a 16 year-old developer and I enjoy messing around with technology in my free time (That's about as personal as it's going to get).
If you have any questions related to this rom, don't hesitate to ask either in this thread or via PM.
Disclaimer
CyanogenMod members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Click to expand...
Click to collapse
Known Issues
- Turning WiFi off causes a reboot
- Activating Airplane Mode causes a reboot
- It seems that cellular data is not working
- Camera is not working
- When WiFi is on, the phone randomly reboots (seems to be a Cricket thing)
Well, what DOES work, then?
- FM Radio
- WiFi (please note the issues listed above)
- Bluetooth
- Calling/Texting
Screenshots
I attached a handful of screenshots, which you can see at the bottom of this post.
Downloads
ROM: cm-12.1-20150813-UNOFFICIAL-a11.zip
MD5: 7c075b6fb8da3c96bcb38bb866c489d4
Older/Previous Releases
Please note that the file above does not include Google apps, such as Gmail, YouTube, or the Google Play Store. You will have to install those manually, just make sure they are compatible with Android 5.1.
Sweet! How do I install it?
Well, that depends on one thing. Are you S-OFF or S-ON?
If you don't know what this means, then you're S-ON.
If you're S-ON
1. Download the ROM zip to your computer.
2. Extract the "boot.img" from the zip file.
3. Put the zip file on your device and flash it in TWRP.
4. Reboot the device to fastboot mode and, on your computer, flash the boot image you extracted to your device by issuing the command "fastboot flash boot boot.img"
5. Reboot normally
If you're S-OFF
1. Place the zip on your device and flash in TWRP
2. Reboot normally
Changelog
- 8/13/15
--- Fixed an issue that caused CDMA users not to be able to place calls or send/receive text messages
XDA:DevDB Information
CyanogenMod 12.1 for the HTC Desire 510, ROM for the HTC Desire 510
Contributors
r3pwn, rbheromax
Source Code: https://github.com/r3pwn
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: None
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-08-12
Last Updated 2015-08-12

Yes! Downloading now. Thanks r3pwn... Your the man!

NfamousDroid said:
Yes! Downloading now. Thanks r3pwn... Your the man!
Click to expand...
Click to collapse
No problem.
I added another disclaimer to the OP, basically saying that it's not quite daily-driver material yet, just in case anyone decided to skip over the issues list.

Gapps package
r3pwn said:
No problem.
I added another disclaimer to the OP, basically saying that it's not quite daily-driver material yet, just in case anyone decided to skip over the issues list.
Click to expand...
Click to collapse
is the Lollipop Base Gapps package 5.1.1: gapps-511-base-20150807-1-signed.zip the right one to use with CyanogenMod 12.1 for the HTC Desire 510 ??

MAME Arcade said:
Click to expand...
Click to collapse
Please make sure that the MD5 of the zip you have is the same as the MD5 that I have posted in the OP. What is the error exactly?

Going to try this out later tonight when I get back home from work. Looking forward to seeing this progress.

never mind i forgot to factory reset.
BizarreMan said:
Going to try this out later tonight when I get back home from work. Looking forward to seeing this progress.
Click to expand...
Click to collapse
but now i have another problem, whenever wifi is turned on (cricket model) it will freeze thewn reboot a a fewv seconds later.
---------- Post added at 03:02 PM ---------- Previous post was at 02:51 PM ----------
r3pwn said:
Please make sure that the MD5 of the zip you have is the same as the MD5 that I have posted in the OP. What is the error exactly?
Click to expand...
Click to collapse
but now i have another problem, whenever wifi is turned on (cricket model) it will freeze thewn reboot a a fewv seconds later.

Appreciate your work man. you're a 16 yr. old badass in my book.
Prepare yourself though for lots of headaches from the many many users who just wont take the time to read your instructions. Never seen anything like it during my time here on XDA.
What you have done so far is remarkable (you too Mr. Mike) I can wait for stabilization if it comes, if not no biggie. You'll never hear a complaint from me bro.
You need anything, just ask. I'm available to those who are serious like yourself (you too Mr. Mike )
Anyways, thanks buddy. For everything.

MAME Arcade said:
but now i have another problem, whenever wifi is turned on (cricket model) it will freeze thewn reboot a a fewv seconds later.
Click to expand...
Click to collapse
I'll talk more to my Cricket tester and see if he has the same issue.
EDIT: I updated the OP and added this.
CSP III said:
Appreciate your work man. you're a 16 yr. old badass in my book.
Prepare yourself though for lots of headaches from the many many users who just wont take the time to read your instructions. Never seen anything like it during my time here on XDA.
What you have done so far is remarkable (you too Mr. Mike) I can wait for stabilization if it comes, if not no biggie. You'll never hear a complaint from me bro.
You need anything, just ask. I'm available to those who are serious like yourself (you too Mr. Mike )
Anyways, thanks buddy. For everything.
Click to expand...
Click to collapse
Thanks! This is actually further than I initially envisioned myself making it. It's fun to do this type of stuff actually. I bought my 510 off-contract and never activated it, with the intent of just doing this stuff to it.

r3pwn said:
I'll talk more to my Cricket tester and see if he has the same issue.
EDIT: I updated the OP and added this.
Thanks! This is actually further than I initially envisioned myself making it. It's fun to do this type of stuff actually. I bought my 510 off-contract and never activated it, with the intent of just doing this stuff to it.
Click to expand...
Click to collapse
Love the progress. This rom is awesome. I have two HTC Desire 510's. After reading the "Not Working Section" I realized that data doesn't work on virgin mobile just yet. So, I will re-install this rom on my non activated one and follow your progress until calls, messaging and camera works. Then, I will install it on my activated one. But, thumbs up my friend. You beat MIUI to the punch in getting a modern rom started for this device. They still work on dinosaur HTC device roms. LOL!!

when will this be stable this rom looks awesome keep up the good work

Man r3pwn killin it!! Amazing work my dude mad props too! Goin test this out later on my vm desire, thanks r3pwn!
Sent from my 0PCV1 using XDA Free mobile app

s3llz said:
Love the progress. This rom is awesome. I have two HTC Desire 510's. After reading the "Not Working Section" I realized that data doesn't work on virgin mobile just yet. So, I will re-install this rom on my non activated one and follow your progress until calls, messaging and camera works. Then, I will install it on my activated one. But, thumbs up my friend. You beat MIUI to the punch in getting a modern rom started for this device. They still work on dinosaur HTC device roms. LOL!!
Click to expand...
Click to collapse
Data doesn't work, but calls and texts should work fine.
michaelvu1811 said:
when will this be stable this rom looks awesome keep up the good work
Click to expand...
Click to collapse
I have no idea when I will be able to get everything working.
Flash_Aholic said:
Man r3pwn killin it!! Amazing work my dude mad props too! Goin test this out later on my vm desire, thanks r3pwn!
Sent from my 0PCV1 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! I have the Sprint variant, myself.

r3pwn said:
Data doesn't work, but calls and texts should work fine.
I have no idea when I will be able to get everything working.
Thanks! I have the Sprint variant, myself.
Click to expand...
Click to collapse
I must have done something wrong when installing. LOL!! I'm not an expert at flashing. So I don't doubt that I did something wrong. Ok, i'm gonna go back and retrace my steps on the flash and make sure I didn't miss any steps. Wait, I think I did. Is the boot image that needs to be extracted from the zip for those of us who are still s-on does that mean it needs to be completely out of the zip and then flashed in fastboot? If so, that is were I messed up at. And when whipping, do we factory whip or advance whip? Just wanna make sure. If I can at least get calls and text working, I'll be fine.

s3llz said:
I must have done something wrong when installing. LOL!! I'm not an expert at flashing. So I don't doubt that I did something wrong. Ok, i'm gonna go back and retrace my steps on the flash and make sure I didn't miss any steps. Wait, I think I did. Is the boot image that needs to be extracted from the zip for those of us who are still s-on does that mean it needs to be completely out of the zip and then flashed in fastboot? If so, that is were I messed up at. And when whipping, do we factory whip or advance whip? Just wanna make sure. If I can at least get calls and text working, I'll be fine.
Click to expand...
Click to collapse
You can leave the zip as it is, you just have to make sure that you flash the boot image in fastboot. When I wipe, I usually pick "Advanced Wioe" and wipe system, data, cache, dalvik-cache and sometimes even internal storage.

will this work with boost mobile ?? i 1. Download the ROM zip to your computer.
2. Extract the "boot.img" from the zip file.
3. Put the zip file on your device and flash it in TWRP.
4. Reboot the device to fastboot mode and, on your computer, flash the boot image you extracted to your device by issuing the command "fastboot flash boot boot.img"
5. Reboot normally that all went great ! but cant - Call , Text ,

markuaw1 said:
will this work with boost mobile ?? i 1. Download the ROM zip to your computer.
2. Extract the "boot.img" from the zip file.
3. Put the zip file on your device and flash it in TWRP.
4. Reboot the device to fastboot mode and, on your computer, flash the boot image you extracted to your device by issuing the command "fastboot flash boot boot.img"
5. Reboot normally that all went great ! but cant - Call , Text ,
Click to expand...
Click to collapse
It should work, but based on what other people are saying, I guess not. I'll update the OP

thank you sir
r3pwn said:
It should work, but based on what other people are saying, I guess not. I'll update the OP
Click to expand...
Click to collapse
it did install with no problem and wifi is working fine

r3pwn said:
It should work, but based on what other people are saying, I guess not. I'll update the OP
Click to expand...
Click to collapse
Hey, you are doing fine. No complaints here. I know from experience that it takes time to get these roms fully running. Plus, I'd rather you be in good spirit while working on this masterpiece. :fingers-crossed::victory:

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