{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the Nexus 5 All-In-One Guide. If you are a new user that is looking for the opportunity to take advantage of your device and do it right the first time, this guide is here to point the way. This thread exists to keep all the necessary methods and material in one common place just for you. As always: Do your homework first.
If followed correctly, this guide can be a useful tool. These steps are listed in the order in which they should be completed. The intent is to seamlessly unlock, root, backup and/or flash, leaving as little room for error as possible. This process will erase and/or reset everything on your device. All steps are assuming you have backed up your contacts, texts, pictures, videos, etc. I do not take credit for any of this material or information. This is all the work of great people that I have simply brought together. Cheers!
**WARNING!** All information and attached links is for the Nexus 5 ONLY! No one here is responsible for anything that may happen to your device. Proceed at your own risk.
>>>>>>Before you begin, make sure your N5 has USB Debugging Mode switched on<<<<<<
Step 1: Read. Read. Succeed.
Your journey down the Android path of rooting and modifying can be smooth, fun and educational, based on your attempt at learning everything you can before you begin. This is entirely up to you, the user. There is some excellent material here on XDA that I highly recommend reading over as part of step 1. Don't skip this information!
A message from the moderators - All users please read
Yep, read it. It's for your own good. Included with some very useful general forum information, it also contains the forum rules which should also be read and understood.
[FAQ][REF]★All you need to know about Android | Read this before you post/root★
This awesome thread by @abaaaabbbb63 is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with. Get on over there and read it.
Step 2: Unlocking, Rooting & Custom Recoveries
For those of you who want to get most out of your Nexus 5, you will certainly want to root it. Rooting your device provides you as the user many, many benefits. That's why you're here right now reading this. You want it all. Please note that there is always the chance of error during these processes. Bad or faulty USB cables, USB ports, bad/old device drivers on the computer, an active virus scanner. These are a few of the issues that can cause your device to fail to connect or prohibit a successful root/flash. Use good and original OEM USB cables. Uninstall any drivers you may have installed for Samsung Mobile Devices and disable your virus scanner.
[Nexus 5] CF-Auto-Root
The thread linked here is the work of our beloved @Chainfire. This guide will direct you through the root process. CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmware and be the quickest and easiest way for your first root.
**If you want to have root access only you can stop here.**
[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root
This one-stop thread by @Chromium_ will get you setup with the necessary tools like the Android SDK and Nexus 5 drivers while also giving you instructions for unlocking your Nexus 5 bootloader, installing a custom recovery and gaining root access. Don't be afraid of ADB commands. You'll need to begin learning them at some point.
A word on custom recoveries: A recovery image is the system level software for your Android that lets you perform several maintenance and recovery tasks. The stock recovery image is quite limited in what it allows you to do and therefore, flashing a custom recovery image is required to gain full control of your device’s administration. A custom recovery image allows you to perform the following tasks:
- Wipe your phone’s data (Factory reset) and cache
- Make, restore and manage backups of your phone’s operating system and software
- Mount, unmount and format your phone’s internal as well as external storage partitions
- Install a custom ROM or application from a zip file to your phone
- Wipe Dalvik cache and battery statistics
- Make logs for error reporting and debugging
Additionally, you can download the Goo Manager app to install TWRP updates or the Rom Manager app to update your CWM. At this moment, there is no official CWM.
*NOTE: I do not recommend Rom Manager or Goo Manager as a tool to do anything but just install and/or update your recovery Do not flash ROMs from these applications.
STEP 3: Making A Backup
Making a Nandroid will allow you to try out new ROMs while still keeping a safe backup in the event you experience issues during or after a custom OS or kernel installation. Be sure your device is fully charged before proceeding to the backup and flashing procedures.
If you are not already booted into recovery then do so now.
1. Boot into fastboot mode (Volume Down + Power)
2. Browse with the volume keys to Recovery Mode and press the power button
3. You are now in custom recovery.
4. In CWM go to Backup and Restore and select Backup. In TWRP select Backup. Name and select the options you want. Swipe to backup.
5. In TWRP, after the nandroid is finished, select "Name" and create a name for your EFS backup. Deselect everything except for EFS then swipe to backup.
6. After backup is finished, select reboot system now or stay in recovery to continue with this guide.
Optional Step 7: Check out the Modem/EFS thread listed below in Post #2 by @autoprime. Another fast and easy way to back up that EFS.
*NOTE: Be sure to save a copy of these backups to your computer and/or micro sd card. Having a recent backup saved to your computer and micro SD card can be useful if something happens to your phones internal memory.
Step 4A: Wiping Your Device
When flashing any ROM, it is always important to follow the proper wipe procedures in order for everything to function properly. There are various levels of wiping based on what sort of transition you may be making. In this guide, I will list the procedures for a full wipe, presuming that you are coming from the stock firmware and changing your OS completely. This is all assuming you have made the appropriate backups. ALWAYS perform the appropriate wipe before flashing a new ROM or update!
1. If you are not already in recovery, boot in now.
In CWM:
2. Select Wipe data/factory reset
3. Select Wipe Cache
4. Select Advanced and Wipe Dalvik Cache
5. Select Mounts and Storage and format /system
6. If you are transitioning from Android versions (4.4 to 4.x, etc) you must also format /data. You will lose all personal data so back it up first.
In TWRP:
2. Select Wipe
3. Select Factory Reset and wipe
4. Select System and wipe
5. If you are transitioning from Android versions (4.4 to 4.x, etc) you must also select Data and wipe. You will lose all personal data so back it up first.
Step 4B: Flashing a Custom ROM
Once you have selected a ROM for your Nexus 5:
1. Download the ROM. Be sure to download the appropriate gapps as well.
2. From your PC, place the ROM/gapps on your internal storage. Remember where they are.
3. Boot into custom recovery.
4. Perform the wipe listed above if you have not already.
5. From the main recovery screen:
>>CWM - Choose the "install .zip from SD Card" and confirm.
>>TWRP - Choose Install and locate the desired ROM on your internal storage.
6. Repeat step 5 and select the gapps package.
7. Reboot system. It will take several minutes to load so be patient and don't worry. Once the phone is booted, let it sit for 5 minutes, reboot and enjoy!
>>>>>Fixes and Additional Resources<<<<<
Post #2 will, as it claims, contains further useful information and links that will hopefully restore, repair or update your device and continue to make your device-modding travels safe, smooth and fun. Please do not disregard the initial purpose of this thread and all the useful steps and information listed above. Cheers!
[MODEM] [EFS] Nexus 5 Flashable Modems and EFS Backup
Don't skip this. Backing up your EFS is highly recommended. It's incredibly fast and simple and you could really be helping yourself out in the event of some unforeseen IMEI problem down the road. @autoprime has a sweet little zip waiting for you in this guide. Go check it out.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
In case you somehow missed it in the General section or just found your way here via a search, here you go. A nicely told story by @abaaaabbbb63 on how to undo all that cool stuff you've been up to since you bought the device.
Nice to see your work here
Edit, you should take out reference to the external sd card. It shows up in flashing a rom.
jd1639 said:
Nice to see your work here
Click to expand...
Click to collapse
just trying to keep the information and questions centralized for new users.
again, glad to see you here. cheers :good:
Just to make sure, with the Nexus line of phones, you can gain root anytime you want right?
It's not the case that Google would push out a security update that would stop these from working?
Wow, this is really helpful. Thanks!
.jond said:
Just to make sure, with the Nexus line of phones, you can gain root anytime you want right?
It's not the case that Google would push out a security update that would stop these from working?
Click to expand...
Click to collapse
you sound as though you are coming from experiences on an htc or samsung device, controlled by a major carrier.
you'll be all set. :good:
Backup
Hey guys, am really android newbie with my first Android phone ever, I`ve red the guides and tutorial, few things want to clarify:
1/ I want to make FULL backup of device - is there a way to make CLONE of all content of the phone before I start using it and customising, rooting etc? I guess the right word for this is Nandroid, right? From reading to do a Nandroid, I have to install custom recovery into phone which doesnt make sense as I would like to backup it without any modification made. Any advice?
2/ What about some easy tool to run on computer, connect phone via USB cable, turn to recovery mode and perform full backup this way???
Since I will have full backup I can start messing with the rest, thx for answer
Nexus5-32GB said:
Hey guys, am really android newbie with my first Android phone ever, I`ve red the guides and tutorial, few things want to clarify:
1/ I want to make FULL backup of device - is there a way to make CLONE of all content of the phone before I start using it and customising, rooting etc? I guess the right word for this is Nandroid, right? From reading to do a Nandroid, I have to install custom recovery into phone which doesnt make sense as I would like to backup it without any modification made. Any advice?
2/ What about some easy tool to run on computer, connect phone via USB cable, turn to recovery mode and perform full backup this way???
Since I will have full backup I can start messing with the rest, thx for answer
Click to expand...
Click to collapse
Making a nandroid when you first get your phone is a perfect way to start. You do need to do it in the custom recovery. It'll back up your system and data. If you ever want to return the phone to a like new, right out of the box, you can flash the factory image to do that. Look in the development forum for the factory image.
Good luck on your experience and keep reading and learning. It's the best thing you can do.
jd1639 said:
Making a nandroid when you first get your phone is a perfect way to start. You do need to do it in the custom recovery. It'll back up your system and data. If you ever want to return the phone to a like new, right out of the box, you can flash the factory image to do that. Look in the development forum for the factory image.
Good luck on your experience and keep reading and learning. It's the best thing you can do.
Click to expand...
Click to collapse
Just out of curiosity, what purpose does a nandroid image of a new/unused/uncustomized phone serve? In case of issues, isn't flashing the factory image going to do the same?
jj14 said:
Just out of curiosity, what purpose does a nandroid image of a new/unused/uncustomized phone serve? In case of issues, isn't flashing the factory image going to do the same?
Click to expand...
Click to collapse
Restoring the nandroid is a little easier then flashing the image. I just like to have a nandroid as I start playing with apps, some of which I won't keep. That way I can easily go back to a clean slate. Also if you ever have a bad flash flashing custom roms you have something on your phone to fall back to.
xBeerdroiDx said:
you sound as though you are coming from experiences on an htc or samsung device, controlled by a major carrier.
you'll be all set. :good:
Click to expand...
Click to collapse
Thanks!
Yeah, coming from an HTC EVO LTE on Sprint.
With the EVO, if you didn't grab s-off when there happened to be an exploit, you could lose the opportunity for months.
HTC offered a root tool, but it didn't S-Off, and would also watermark the boot screen showing that you rooted it(thus voiding any warranty).
Glad to be on Nexus now....
jd1639 said:
Restoring the nandroid is a little easier then flashing the image. I just like to have a nandroid as I start playing with apps, some of which I won't keep. That way I can easily go back to a clean slate. Also if you ever have a bad flash flashing custom roms you have something on your phone to fall back to.
Click to expand...
Click to collapse
ok. I've always created a nandroid backup as well, but only for non-Nexus devices (kinda harder to get the factory image at times), and/or after making changes to get the phone customized just right (screens/apps/settings etc) - hence the question
Thanks
@xBeerdroiDx, I just sent you a pm. This is twrp 2.6.3.1 fir the N5 http://d-h.st/Mxu. Feel free to use it as a template for other recoveries. I have limited dev-host space so I'm not going to be able to host these unless I pay for more space.
jd1639 said:
@xBeerdroiDx, I just sent you a pm. This is twrp 2.6.3.1 fir the N5 http://d-h.st/Mxu. Feel free to use it as a template for other recoveries. I have limited dev-host space so I'm not going to be able to host these unless I pay for more space.
Click to expand...
Click to collapse
:good:
thanks for the zip. i'll use the template in the near future for recovery updates and host them as well. cheers
xBeerdroiDx said:
:good:
thanks for the zip. i'll use the template in the near future for recovery updates and host them as well. cheers
Click to expand...
Click to collapse
Thanks for putting my thread in the OP. Unfortunately, I later realized that my title wasn't correct Could you delete the "the" in it? Thanks!
abaaaabbbb63 said:
Thanks for putting my thread in the OP. Unfortunately, I later realized that my title wasn't correct Could you delete the "the" in it? Thanks!
Click to expand...
Click to collapse
:good: done.
Thank you!
6ctomorphox said:
Thank you!
Click to expand...
Click to collapse
welcome to the community.
@xBeerdroiDx to complement twrp here's cwm unofficial 6.0.4.4. http://forum.xda-developers.com/showthread.php?p=47156423
Related
This is a tutorial for those who need the latest Rom but do not have a computer they can access. I would also like to note if you see your work in this tutorial and do not wish to have it, please send me an IM and I will remove it immediately.
First thing is first, of course make sure you are rooted with [Recovery]RA-nexus-v1.6.2 already on your phone. Also make sure you have a memory car in your phone. Finally I highly recommend using a wifi source.
Disclaimer: Myself and any other Developer are not responsible for anything that happens to your phone.
1. Download and install "ASTRO file manager (Metago)" from the android market so you can download the zip file
2. Find the ROM you wish to use and download it using the android browser and download it to your phone.
3. Open up ASTRO file manger /sdcard/downloads (or whatever your download folder is)
4. long press and edit, then click copy or move which ever you wish.
5. Place in /sdcard (also known as the root of the SD card)
6. Now turn off your phone and boot into recovery by holding the volume - (down) and power button.
7. Now in recovery follow the developers directions (if wipe needed do so now)
8. Now go to update from zip and you are done when it is finished flashing, you just need to reset the device.
Disclaimer: Myself and any other Developer are not responsible for anything that happens to your phone.
any questions, comments, concerns or improvements state them.
reserved for questions
will check in the morning on my N1 if anything comes up. Good night forums
this is great but not to burst your bubble but all you need is to download android zip from the market. that's what ive been using.
So, being new to android, maybe a dumb question, but do rooted users lose update possibilities?
I mean OTA ones?
AllanJacques said:
So, being new to android, maybe a dumb question, but do rooted users lose update possibilities?
I mean OTA ones?
Click to expand...
Click to collapse
Yes to an extent. Meaning you will not receive the update OTA. You will more than likely get it a couple weeks earlier than OTA. Rooted users always seem to get the jump over non rooted users. Devs like Enom and Cyanogen see to that.
Okay tutorial I suppose...it's better to just flash the RA recovery and then you don't have to name things update.zip
AllanJacques said:
So, being new to android, maybe a dumb question, but do rooted users lose update possibilities?
I mean OTA ones?
Click to expand...
Click to collapse
Of course, but you're getting features and updates sooner than OTA. Sometimes months sooner.
way to many steps, what you need to do is suck it up and install the RA recovery, then just download any rom leave it in the root of your sd card and boot to recvoery and hit flash zip from sd, and select the zip done!
th3fallen said:
way to many steps, what you need to do is suck it up and install the RA recovery, then just download any rom leave it in the root of your sd card and boot to recvoery and hit flash zip from sd, and select the zip done!
Click to expand...
Click to collapse
Thats what I would do when I was on my G1.
Don't need to rename the zip like others have said but I can understand why it would be easy for noobs. The only thing I see missing is telling how to reboot in recovery (volume down + power --> Recovery)
Sorry all its my first attempt at a step by step process for those who have just started rooting and flashing other roms. I know it may be lengthy for experienced users, I will be next to my computer and refine the process for all users hopefully tomorrow. But I'm in vacation in St Augustine for the time being.
All input is welcome, and thanks for the helpful comments.
Don't forget to support your devs
-Charlie
Ok I've simplified the process now basically like th3fallen stated in later comments, once again if you have questions let me know
-Charlie
i'm about to root my moto x dev.
i want to keep a backup of the original firmware in case i want to go back.
does it make any difference that it is encrypted? i'm guessing no...
also, any good dumb proof steps? the main info thread only mentions restoring stock by downloading a firmware not using a backed up one.
gcbxda said:
i'm about to root my moto x dev.
i want to keep a backup of the original firmware in case i want to go back.
does it make any difference that it is encrypted? i'm guessing no...
also, any good dumb proof steps? the main info thread only mentions restoring stock by downloading a firmware not using a backed up one.
Click to expand...
Click to collapse
Rooting how? What version of android are you on? These are very important considerations to be able to make a recommendation.
Assuming you intend to unlock your bootloader, you can make a backup with TWRP Custom Recovery BEFORE you root.
If you are using the PIE exploit (only current root method for 4.4.2+), you cannot flash custom recovery. If this is the case, your only option to return to stock will be to flash the official SBF file for your carrier as listed in the "Return to Stock" thread. Not really important since the changes are lost upon reboot anyways.
Regardless, we need more details.
EDIT: Just saw you are using DEV edition.
Very easy!
FIRST: When you unlock your bootloader, it ERASES EVERYTHING. Save anything important first. You cannot make a backup until after you flash twrp, which you can only do AFTER you unlock the BL.
Additionally, according to this thread, it is impossible to backup an encrypted device. So after unlock, you are advised to not choose to encrypt, otherwise no backup can be made: http://forum.xda-developers.com/moto-x/moto-x-qa/twrp-device-encryption-t2711700
Once Unlocked, flash TWRP custom recovery with mfastboot:
mfastboot flash recovery twrpfilename.img
link to download twrp here: http://forum.xda-developers.com/moto-x/development/recovery-twrp-official-support-moto-x-t2779637
then use fastboot to reboot into bootloader:
fastboot reboot-bootloader
now VOL DOWN to "recovery" and VOL UP to open it.
There is a BIG backup button. Use it.
Afterwards, click exit. When you do, it will tell you that you are not rooted and ask if you want to flash SuperSU Installer.
Say yes! Once rebooted, run SuperSU installer and it will root & install SuperSU for you. It will give you 2 options: Choose Play Store Option.
Good Luck
@gcbxda
Keep in mind, since unlocking the bootloader also does a factory reset and puts you back to "fresh out box" the backup you do once you flash TWRP on your phone, will be no different than "Stock Rom" (except TWRP recovery). So why not use the factory firmware to flash the phone back instead of restoring such a backup?
Oh, and keep in mind, if you do backup while in TWRP, you'll want to copy that back up file from the phone to the PC for storage. Future Factory Resets and such will likely wipe the X's internal /SDcard so the backup file would be lost.
Now if your intent is to unlock the bootloader, setup your phone the way you like it before rooting, back up, and then root.... I can see the value in that.
You can also use 'adb pull /sdcard c:\' to backup any files you have
Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Also, what if I do a backup of the partitions with ADB? ...man sometimes the android community pisses me off. everything must be packaged in a app or some GUI that hides all the information. ...just wasted 2 days reading xposed source to learn that all i had to do, instead of even installing xposed, was to edit a single sql value from 1 to 0... i'm all for the nice guis, but don't hide the actual steps like it is some black magic.
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore
Stock
gcbxda said:
Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Also, what if I do a backup of the partitions with ADB? ...man sometimes the android community pisses me off. everything must be packaged in a app or some GUI that hides all the information. ...just wasted 2 days reading xposed source to learn that all i had to do, instead of even installing xposed, was to edit a single sql value from 1 to 0... i'm all for the nice guis, but don't hide the actual steps like it is some black magic.
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore
Click to expand...
Click to collapse
Hello,
You can find all the stock roms here - - > http://sbf.droid-developers.org/phone.php?device=0
MikeNaples said:
Hello,
You can find all the stock roms here - - > http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
thanks. i also saw that motorola offer it themselves.. is this their own repository?
but regardless, it is always nice to already have your own handy
gcbxda said:
thanks. i also saw that motorola offer it themselves.. is this their own repository?
but regardless, it is always nice to already have your own handy
Click to expand...
Click to collapse
Moto officially offers recovery images (full stock rom) for the GSM Dev/GSM Unlocked XT1053 and Verizon XT1060 by request on their web site here -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images They are the most currently released rom only. You wont find older versions there.
SBF.Droid-Developers.org is neither owned, operated nor sponsored by Moto. They keep every version full stock roms (SBF files) they find. I'm not going to speculate how they come across them, but they have many SBF files that Moto hasn't officially released to the public too. i.e. Sprint, ATT, and other carriers.
---------- Post added at 07:27 AM ---------- Previous post was at 07:01 AM ----------
gcbxda said:
Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Click to expand...
Click to collapse
There are ways to get back to stock to be able to take an OTA -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
gcbxda said:
Also, what if I do a backup of the partitions with ADB? ...
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
You can certainly back up that way. But I haven't tried backing up that way and restoring, so I don't know.
gcbxda said:
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore
Click to expand...
Click to collapse
With my HTC Incredible and HTC Thunderbolt and Moto Droid, I did backups in CWM, and restores. It was mainly for when a new upgrade came out. I would backup my current device setup, apps, etc. Apply the update, and if I didn't like the update or had problems, I could revert to my pre-update backup, rather than flash a stock rom and have to set it up all over again, install all my apps, etc. But the HTC devices had S-OFF, so downgrading wasn't an issue.
With my Droid Bionic, the bootloader wasn't unlocked, so it wasn't an option. And there were issues with GPT.Bin and other items preventing downgrading roms, even when flashing official full SBF files.
I haven't really done this with my VZW Dev X, mostly due to the fact that while the bootloader is unlocked, its not unlocked as much as a Nexus device, or an HTC with S-Off, where you can downgrade and flash any parts no matter what. Security issues, things like GPT.BIN, MotoBoot, etc can still get in the way when trying to downgrade. So I never felt it worth the risk. Not to mention the limited space on the X, and time/effort to make the back up and move the file to the PC, and then getting it back on the phone should I ever need to restore it since there is no real SD card.
If your intent of backing up stock roms is so you can revert to stock, having the Moto SBF files available elevates most users concerns. When flashing the same version, there are ways to do it without losing your Apps/Data (like in the case of running 4.4.2 rooted and modded, but wanting to get back to stock to take the 4.4.3 OTA).
If you want to do a backup/restore inside TWRP, you can. I have read many posts from users who were successful. I just advise that you keep track of the version you back up, and only restore if the same Android version is still on your phone (i.e. only restore a 4.4.2 back up if 4.4.2 is on your phone, only restore a 4.4 back up if 4.4 is still on your phone, etc)
wait, what are the limitations i will have with a unlocked Dev device?
with my nexus and touchpad i often tried 4.3 roms and went back to 4 or 2.3 even...
i tried searching the terms you mentioned but it spawn all sort of threads with OP having some flashing problem and then pages of comments starting with "i think..."
I'm extremely confused now
Sent from my XT1053 using XDA Free mobile app
gcbxda said:
wait, what are the limitations i will have with a unlocked Dev device?
with my nexus and touchpad i often tried 4.3 roms and went back to 4 or 2.3 even...
i tried searching the terms you mentioned but it spawn all sort of threads with OP having some flashing problem and then pages of comments starting with "i think..."
I'm extremely confused now
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Unlocked or Locked Moto X... you have to be concerned when flashing backwards. The Security features on the X prevent downgrading certain components. Attempting to do so will brick or set you up to brick in the future.
Please see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm
Short version... once you have 4.4.2 on your phone, do NOT attempt to downgrade.
KidJoe said:
Moto officially offers recovery images (full stock rom) for the GSM Dev/GSM Unlocked XT1053 and Verizon XT1060 by request on their web site here -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images They are the most currently released rom only. You wont find older versions there.
Click to expand...
Click to collapse
Lol. looking back at that thread i whish i had went ahead and did all the backups on all OTA updates before each twrp/root and did not trust motorola to have my back.
I'm a moron. Bumping this as a lesson to others
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.
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?
Hey all,
Just decided to get a nexus 6. Had so many different phones over the years but never a nexus. I like the phone and love Stock android but I want some options that I can't believe are still missing from stock android (tap to wake, custom nav buttons/quick toggles)
I haven't rooted a phone in a couple years, can someone point me in the right direction for root and recovery?
I think I'm gonna go with Pure Nexus rom but any other suggestions would be appreciated.
Sorry if this is a really noob question but if you want to wipe the whole phone with the internal storage (is that ever necessary?) How do you get the install file back on the device if there's no sd card?
mottyengel said:
I haven't rooted a phone in a couple years, can someone point me in the right direction for root and recovery?
Click to expand...
Click to collapse
If you are going to install a custom ROM you won't need to root prior. Unlock the bootloader and flash TWRP. Something like this thread should do it, you can skip the obtain root section as it really isn't necessary if you plan on flashing a custom ROM.
I think I'm gonna go with Pure Nexus rom but any other suggestions would be appreciated.
Click to expand...
Click to collapse
ROMs are personal preferences. Does the ROM have the features you want and need? If yes, then you found the ROM for you. If not, you may want to check out some other ROM(s).
Sorry if this is a really noob question but if you want to wipe the whole phone with the internal storage (is that ever necessary?) How do you get the install file back on the device if there's no sd card?
Click to expand...
Click to collapse
Unlocking the bootloader wipes the device, this is mandatory. If you want to remove encryption, you will also need to wipe internal storage. Otherwise no you generally won't have to wipe the entire device. You will likely need to perform a factory reset between different ROMs, and ROMs that have done some heavy changes between versions. A factory reset in TWRP doesn't wipe the internal storage, but will wipe all of your apps and settings. You can also mount the phone or use ADB in TWRP if you need to transfer files from a computer.
cupfulloflol said:
If you are going to install a custom ROM you won't need to root prior. Unlock the bootloader and flash TWRP. Something like this thread should do it, you can skip the obtain root section as it really isn't necessary if you plan on flashing a custom ROM.
ROMs are personal preferences. Does the ROM have the features you want and need? If yes, then you found the ROM for you. If not, you may want to check out some other ROM(s).
Unlocking the bootloader wipes the device, this is mandatory. If you want to remove encryption, you will also need to wipe internal storage. Otherwise no you generally won't have to wipe the entire device. You will likely need to perform a factory reset between different ROMs, and ROMs that have done some heavy changes between versions. A factory reset in TWRP doesn't wipe the internal storage, but will wipe all of your apps and settings. You can also mount the phone or use ADB in TWRP if you need to transfer files from a computer.
Click to expand...
Click to collapse
Thanks for all the info!