Related
Here is a batch file I have made to do a couple things for an HTC EVO 3D through adb. NO NEED TO INSTALL ADB!!!
It gives you three choices, either reboot to fastboot, which can supply you with a command prompt, reboot to recovery through fastboot, (YES, HBOOT 1.5 USERS CAN USE THIS TO FLASH TO THE BOOT PARTITION, THIS INCLUDES KERNELS, AND RECOVERIES). Or to just ADB reboot (comes in handy for Freezes or Lockups).
To avoid any frustration, I have included adb and fastboot in the folder (NO ADB INSTALL).
I have not included a recovery image, so you will have to download one of your choice, place it in the folder, and rename it to "Recovery.img" (NO Quotation Marks). If a recovery doesn't boot, no worries, this doesn't flash it, just places the recovery in a temporary partition to boot, your current recovery will stay intact
DON'T WORRY, IT SOUNDS MORE DIFFICULT THAN IT IS, YOU GET USED TO IT.
1. Unzip to any folder on your computer
2. Copy your choice of recovery (Recovery.img) to folder
3. Run "Reboot.bat"
4. Make your choice of Fastboot, Recovery, or Reboot
a) If you choose Fastboot, you have the choice of opening a prompt for manual fastboot commands. Choose yes (Y) or no (N).
b1) If you choose Recovery, your phone will reboot into Fastboot
I CAN NOT STRESS ENOUGH, TO WAIT UNTIL THE PHONE HAS ENTERED FASTBOOT, BEFORE CONTINUING TO RECOVERY. No harm will be done to your phone, but it wont boot recovery unless "fastboot" gets the dang command...
b2) Press any button, AFTER your phone has entered fastboot. This will send the command to your phone to boot the recovery you placed in the folder, not the one flashed on your phone. (Good Way To Test Recoveries Before Flashing).
c) If you choose Reboot... UM??? Your phone will reboot...
5. YOU ARE DONE!!!
IF ANYONE WOULD LIKE TO OPEN THE BATCH TO EXAMINE IT, YOU ARE MORE THAN WELCOME. I JUST ASK THAT YOU DO NOT MODIFY OR COPY IT WITHOUT MY PERMISSION.
I am currently in the process of making a batch that will flash the recovery as well.
MD5:603E2B5009E97350E922A49AFCBAAA78
New recovery flashing capabilities
I have added a recovery flashing capability to the batch, it has a lot of warnings, but it needs them... It just flashes the previously stated recovery.img, instead of booting a temporary recovery through fastboot...
MD5:5494B0BD03179332F9EBCA28D389A8A7
Preamble
This is the S-OFF upgrade from GingerBread to HoneyComb
Do not perform this procedure if you have the official HTC hboot, it will not work. You must have a revolutionary hboot (see prerequisites).
***If you performed this procedure with previously and have hboot version 6.14.5555 please update to the new hboot, 6.14.5555 is no longer supported***
Upgrade instructions at the bottom of the procedures.
Prerequisites
You must have performed Revolutionary S-OFF
If running on windows you will need these fastboot drivers
If running the procedure on Linux or MacOS you must have fastboot working.
There are no other software prerequisites for this procedure, it does not matter what ROM/Kernel or recovery you are using.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any.
Run on a real machine.
Windows Instructions
Download this file MD5=c62cc1d0453799a7277abfea444d20e4
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the RUU_Express_B02 directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Alternative Installation Instruction (Any OS)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the RUU_Express_B02_RAW.zip file PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Do not mirror files from this post.
No discussion of Honeycomb content or changes or the relative merits of Gingerbread and Honeycomb. This thread is for the procedure and support thereof only! Also please don't quote the first post because your post becomes an automatic TLDR.
Update Instructions
Use these instructions if you currently have hboot 6.14.5555 - Your data should be preserved but take a backup first just in case.
Method 1
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Copy the file to the root of your external SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
Method 2
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PG41IMG.zip
[I][COLOR="Red"]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/COLOR][/I]
fastboot reboot
[Revision History]
B02 - updated full version: hboot 6.14.5556
New bootloader to patch bugs with fastboot flashing
- Fastboot flashing splash1 fixed
- Fastboot flashing hboot fixed
Patch for upgrading from a previous version added.
B01 - Initial full version: hboot 6.14.5555
BETA- Developer preview
Special thanks: contradude for the early and riskiest testing, and Maine_Coon for all the ongoing testing
Downgrade to Gingerbread
Preamble
This is the S-OFF downgrade from HoneyComb to S-OFF GingerBread if you are not S-OFF and have a HTC (not revolutionary) hboot then do not do this it will not work.
The full versions of these files will give you a fully functional Gingerbread installation with S-OFF, CWM recovery and boot image with the secure flag turned off.
Windows Instructions
Download this file MD5=f5afc4b457a17f88cc611b40e6c7cdc8
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the Express_Downgrade directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Alternative Installation Instruction (Any OS)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the file downloaded in step1 to PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Do not mirror files from this post.
wow you are really fast, excellent men.
One for me please
reserved 2
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
vancraft said:
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
Click to expand...
Click to collapse
This is an attempt to make downgrading easier for us.
spartan1987 said:
This is an attempt to make downgrading easier for us.
Click to expand...
Click to collapse
Right. That's the "recovery" part.
But its also described as "root, and all". I'm wondering if this allows the installer to root the OTA Honeycomb? Or will more work be required before the install can be further changed (i.e. s-off, eventually upgraded to ICS, etc.)?
It works
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
risb577 said:
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
Click to expand...
Click to collapse
so, does that mean you could, in theory, flash a custom HC rom once we get one?
Throw up some screenshots or a video would you?
edit: oh and test rom manager and titanium backup if you don't mind.
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
stuck on soft brick..
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Maine_Coon said:
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
Click to expand...
Click to collapse
No, as it says in the OP, You MUST be s-off and THEN run an RUU. Accept all updates to include the HC update and the view will be soft bricked. THEN use fastboot to push the mini ruu.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
myowin said:
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Click to expand...
Click to collapse
If it says it's an unrecognized command, then either you do not have fastboot installed, or you haven't gone into environment variables (assuming it's a windows box) and added those commands to the path. try that first (google is your friend and you can google in XDA). Good luck.
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
thank you so much for quick respond..
I think I found it here how to do that.. (for someone like me... )
http://forum.xda-developers.com/showthread.php?t=532719
root
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
I haven't done this yet, but I'm dling the RUU right now to do it and help people troubleshoot.
To answer your question, if you hold down the power button long enough, the view will power off, then you can hold power + vol down to get back into the bootloader and select fastboot mode, then open cmd, type fastboot devices and check to make sure yours shows up, then proceed with pushing the mini-ruu. If I'm wrong guys, correct me. Hope it works out for you.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
Im not sure if this matters, but when I was in soft brick, I rebooted a few times and could not get into the bootloader. It just seemed to ignore the vol down keypress. I then unplugged the usb, powered off from soft brick, and held the vol. down button down even before I hit the power button as I was turning it on. Once I was in bootloader, I just plugged the usb back in.
EDIT: More tips:
1.After I flashed the initial stock ruu, and before I accepted any updates, I turned off fastboot in the power options and enabled usb debugging.
2. I did this from a Windows 7 laptop. When I initially tried to perform the softbrick steps, I got an access denied error message. The files were sent ok, but errored on saving. I closed the command prompt, and re-lauched the command prompt as administrator. The commands sent successfully.
3. Also, once you send the mini ruu over, the Tablet sat in the the oem loader with a 70% full progress bar after I successfully sent the mini ruu. I waited about 10 minutes because I was unsure how to proceed. I finally issued:
fastboot reboot-bootloader
Once back into bootloader, I mounted usb storage, copied SU to the card, and flashed from zip
risb577 said:
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
Click to expand...
Click to collapse
Yeah, rom manager won't work bc we don't have official support from Koush for CWM recovery so that's no issue, I was just curious is all lol. I'm glad to hear titanium detects root, as that was an issue initially for the view. Try to backup your apps, test radios (3g, 4g, wifi, bluetooth, GPS, ETC), run quadrant. I don't know how familiar you are with honeycomb to test out all of it's functions, but we are going to need a few people to test this out for globatron so he can make fixes and/or adjustments as necessary, which is why he specifically asked for devs and people familiar with troubleshooting to do this first. That's the beauty of open source, we're all guinea pigs.
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
soft brick screen
ElAguila said:
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
Click to expand...
Click to collapse
It looks like this pic. Plus another clue you are soft bricked is it stays here longer than 10 minutes if you care to wait lol
Hello,
Point of this is to get s-off roms to work on an s-on phone, s-on is how a phone is stock, so if you dont know which you are or what this is, your phone came s-on and thats what you have.
Thought I would make a quick noob guide to flashing boot.img files for the S-on users. It was something that confused me and thanks to a few guys in here I got it going and want to return the favor by making a SUPER easy (hopefully) list of directions. Any input on making these directions easier would be appreciated as well. Keep in mind you already need to have an unlocked bootloader which you can do through htc and have installed amonra recovery to flash your rom. I had an easy time using hasoon2000's all in one tool kit found in here for unlocking and flashing the amonra recovery. I am assuming your comfortable flashing roms at this point and have probably even tried a few but now want to try the s-off ones without actually going s-off.
Doing this you take your own responsibility for whatever may happen, but this works on my phone and should on yours too.
Needed programs:
Android sdk toolkit http://developer.android.com/sdk/index.html
HTC drivers http://www.htc.com/www/software/htc-sync-manager/
winrar or winzip- I use download.com
rom of choice
Read the directions first and understand them before you flash an s-off rom on your phone. If you mess up dont worry make a backup so you can restore it to working order or have a safe rom you know already works handy in case something goes wrong.
Whenever you see something in quotes, type only whats inside the quotes and dont include the quotes.
---------------------------------------------------------
setting up the computer for this process
---------------------------------------------------------
Step 1: Download the android sdk toolkit, htc drivers/snyc, winrar and install them
Go ahead, download the programs and install them the normal way they guide you to do. Pay attention when installing the android toolkit, it will tell you where it is going to save it too, it will come in handy on step 2, but I also include where it saved it on my computer in step 2. This should be the same for all windows 7 computers as well as vista.
Note: during sdk toolkit install select install for only me option or it wont put it in the correct directory in windows.
Step 2: Locate the installed folder and make a shortcut onto your desktop
-you need to go into your c drive in windows, then its most likely stored in the users folder, then click the user name you have, then appdata, then local, then android. Once at android-sdk right click and select send to desktop to make a shortcut. Now click on android-sdk and do the same for the platform-tools folder.
The folder path will be similar to the one below:
android-sdk folder path C:\Users\yourUSERname\AppData\Local\Android\android-sdk
platform-tools path C:\Users\yourUSERname\AppData\Local\Android\android-sdk\platform-tools
------------------------------------------------------------------------------------------------------------
At this point lets assume you have the s-off rom on your phone and your pc
------------------------------------------------------------------------------------------------------------
Step 3: Place the boot.img file of the rom your going to install into the folder: platform-tools
How do you get the boot.img? Well you have to get the rom you want and extract it from the rom zip file. That's where winrar or winzip come in handy. Make a folder on your desktop and name it whatever you want, I name them with the rom name. Now place your rom in here, right click the rom, and you will see an extract option. "Extract to here" will be there with winrar but winzip should have the option too. Once all the files are extracted you will see another file called boot.img. That is the boot file you need to install to get the rom working. Now that you have the file handy, right click and select copy. Now go into the platform-tools shortcut you made on your desktop and paste the boot.img file there.
---------------------------------------------
If you read everything already and understand it, this is where you can start flashing your s-off rom on your phone and wait for it to finish
---------------------------------------------
Step 4: Open the windows command line on your computer
With windows 7 and I think vista also just open the windows menu on the bottom left and type "cmd" in the search bar, select the cmd.exe and a black window will pop up.
Step 5: Type "cd where ever platform tools folder was located"
Now you need to navigate cmd to the boot.img file; so we will tell cmd how to get there. Basically we need to type the location of the platform-tools folder but since its long I will show you a short way a member here showed me. Type "cd" without the quotes then hit the spacebar. Now we will go to the desktop and look for the android-sdk shortcut we made earlier. Open that shortcut. Inside you will see the platform-tools folder, click and hold on that folder and drag it to the black cmd box. If you did it right you will see the long path to the platform-tools folder in the cmd section. Now click on the cmd window to make sure its selected and hit enter on the keyboard.
step 6: After rom install put phone in bootloader, on pc type "fastboot devices" to confirm you have your phone hooked up properly
Now we need to get the phone ready, at this point your phone should have had the new rom flashed, once it was done installing the rom in amonra, select developer menu and select bootloader. At this point connect your phone to a usb 2.0 slot, for some reason none of the usb 3.0 slots will recognize with this process so make sure its usb 2.0. You will see usb-fastboot on your phone if the computer sees it. To be sure in the cmd screen type "fastboot devices" and you will see a device name come up, thats your phone. If nothing popped up the computer isnt seeing it.
step 7: type "fastboot flash boot boot.img"
So at this point we know everything is ready to flash the boot.img. Simply type "fastboot flash boot boot.img" and let it do its thing, once its done, your ready to reboot the phone and start playing with it. If you want to reboot it through cmd which I do the text is below or you can simply just hit the reboot option in the phone.
step 8 once done type "fastboot reboot"
After typing the above command in cmd let the phone reboot. Once it starts to reboot you can disconnect the phone and close everything out.
Enjoy
-----------------
tip Understanding commands
-----------------
what does "fastboot flash boot boot.img" mean anyways?
This command is like ordering someone to do something.
Hey fastboot, I need you to flash a boot file called boot.img is basically what you told the computer to do.
Commands are like that and hope it helps you remember them
----------------------
Thanks to:
Luis86dr
famoustarsandstraps1
--Both of these guys helped me understand these tools and I want to return the favor to the other members--
Or you could use a ph98img.zip from, for example, nils rom. Just open both zips with winrar or 7zip and drag the boot.img from the rom into the ph98img.zip and flash the zip in bootloader after you flash the rom. Thats just my personal preference because I transfer the roms to my phone with wifi file explorer so I never have to hook my phone up to my pc.
highdro said:
Or you could use a ph98img.zip from, for example, nils rom. Just open both zips with winrar or 7zip and drag the boot.img from the rom into the ph98img.zip and flash the zip in bootloader after you flash the rom. Thats just my personal preference because I transfer the roms to my phone with wifi file explorer so I never have to hook my phone up to my pc.
Click to expand...
Click to collapse
Thanks a great point, but I had trouble with the asop roms with that method. Would timeout on parsing. I dont know if they got the asop ones working that way yet
66racer said:
Thanks a great point, but I had trouble with the asop roms with that method. Would timeout on parsing. I dont know if they got the asop ones working that way yet
Click to expand...
Click to collapse
works fine for me. running neo's new build right now. I've always used the zip from nils rom though. Maybe something is different in the text file that's inside of the zip that you tried. I've never had an issue and I've flashed a lot of kernels
highdro said:
works fine for me. running neo's new build right now. I've always used the zip from nils rom though. Maybe something is different in the text file that's inside of the zip that you tried. I've never had an issue and I've flashed a lot of kernels
Click to expand...
Click to collapse
Thanks for the info, I was messing around with it when it first came out trying different ph98 files with luis and kept getting the parsing error. It was with the cm9 builds. Maybe they got it sorted out on the rom side of things and thats why its now working. I will try it out on the next rom i try. Thanks
I just use Hasoon's all in one toolkit for all of it. Unlocking, flashing Amon Ra, SuperSU for root and flashing ROMs.
Just plug your phone in as directed and use the boot to recovery option. Do your wipe on the phone and flash your ROM. Put the boot.img from your ROM in the kernels folder in the data folder of the utility. Use the boot to bootloader option. Once you get into bootloader, use the flash kernel option. It runs all the adb commands for you.
Yes, I have SDK installed and know the commands but I can flash one of these S-Off ROMs faster with Hasoons utility than I can typing the adb commands manually.
Sent from my ADR6425LVW using xda app-developers app
note that you can also simply fastboot boot recovery into memory. in this scenario,recovery is able to write the boot image,so roms are able to be installed with no modification,just flash as if you were s-off
a little more info:
http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html
Great guide brother!!
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
scotty1223 said:
note that you can also simply fastboot boot recovery into memory. in this scenario,recovery is able to write the boot image,so roms are able to be installed with no modification,just flash as if you were s-off
a little more info:
http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html
Click to expand...
Click to collapse
This. I did not know. Thanks for the Info
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
I know there are other threads out there that offer exactly what this does, but even with those, I think it can still be a bit tricky to figure out what to do if you're looking to root and modify your phone. I made this thread to collect everything I've done in one place. This should make everything very straightforward and basically n00b-proof.
I take no credit for any of this work. Please thank all the hardworking devs!
**Following all of these steps will WIPE all data from your phone. Backup before beginning. While these should all be safe, there's always the possibility of bricking your phone. I take no responsibility if you do.**
What you'll need:
USB Cable
USB port
HTC Droid DNA (without the OTA update!)
PC running Windows
Glass of Orange Juice (for the Vitamin C!)
**All of this shouldn't take more than 30 minutes but just in case, make sure your phone has at least a 70% charge.**
Preparing (Installing SDK, Setting PATH, testing ADB)
I highly recommend creating a directory on the root of your C: drive on your PC to hold ALL related files. I called mine "android" but you can call yours whatever you'd like. Whenever issuing any ADB command, make sure you navigate to this folder first.
1. Connect your phone to your computer. One of the pop ups will ask to install HTC Sync. Install this to install the drivers onto your computer. Once installed, you can go into your Add/Remove Programs and uninstall the HTC Sync software if you want.
2. Enable USB Debugging in your HTC Droid DNA from the path “Settings > Applications > Development > USB debugging”. The option of USB Debugging should be ticked.
2. Download the latest version of the Android SDK to your PC here.
3. Extract the files to your PC (I recommend something easy like C:\android)
4. Run the SDK Manager and uncheck everything but the Platform Tools and install
5. Add the SDK tools to your system PATH file by doing the following:1. Simultaneously hold down the Windows Key + R
2. type 'sysdm.cpl' into the run dialogue box and click OK
3. On the system properties window that just opened, click on the 'advanced' tab. Then click on 'Environment Variables'
4. Scroll down through the System variables until you find the PATH. Click 'Edit', then add ';C:\android' (or whatever you named your folder) to the end of the line
5. Click OK and close the open windows.6. Test ADB by connecting your phone to your PC then:1. Open a new command prompt window by pressing Windows+R and typing "cmd" into the box
2. Type 'adb devices' and press enter. You should see your phone's UID listed.
If it says adb devices is not a recognizable command then you didn't setup your PATH correctly
If it says <waiting for device> then your missing the drivers or you didn't enable USB debugging. Try rebooting, and if it still doesn't show, reinstall HTC sync.
Other Tips
You can download all the files necessary at the beginning and do everything through ADB.
Always check the MD5-hash after downloading a file. If they don't match, the download is corrupt and you should try again. I use this simply tiny, no-install MD5 checker.
Always Test after each install to ensure it is working properly. Don't just string all of these together without rebooting once. Bad things might happen and you'd have no idea what's causing it.
You can reboot your phone into the bootloader by either issuing the command "adb reboot bootloader" or pressing and holding the PWR and VOL DN buttons simultaneously when you reboot your phone.
From the bootloader you can enter recovery or you can issue the command "adb reboot recovery"
If your command prompt hangs pressing Ctrl+C will break out of the running command.
Some useful command prompt (DOS) commands:
cd - change directory (ie. 'cd C:\android' will change to the 'C:\android' directory)
cd .. - moves up one directory level
dir /p - lists files within the current directory
Unlocking Bootloader
The next step is to unlock the bootloader. The best method right now is provided by jcase. NOTE: Don't install the OTA update or you won't be able to do this!Step 1: Get SuperCID
Full instructions can be found here.
1. Download .apk from link above.
2. Run the app
3. Run the following Commands via ADB
Code:
adb reboot bootloader
(wait for phone to reboot into bootloader)
fastboot oem readcid
If you see 22222222 you're good to proceed. If you see anything else, reboot the phone and try again.
Step 2: Unlock via HTC Dev site
Go to the HTC Developer website and carefully follow the instructions. They're very straight forward.
When completed you'll have unlocked the bootloader. You'll see a new warning on the splash screen and the bootloader will say *tampered* at the top.Install Custom Recovery
You can choose either ClockworkMod (my preference) or TWRP recoveries.
1. Download the latest version of your preferred recovery. rename it "recovery.img"
2. Using ADB issue the following commands
Code:
adb reboot bootloader
(once the phone reboots into the bootloader)
fastboot flash recovery recovery.img
(once installation is complete)
fastboot reboot
Now you'll have a custom recovery, and can make a full nandroid backup (recommended!).
S-OFF
Full instructions can be found here. beaups did an excellent job writing this up so it would be pointless for me to reproduce here.
Root / Custom ROM
Choose any ROM you'd like. I prefer Team Venom's ViperDNA. I'll use that as the basis for the next steps.
1. Download the full ROM found in the second post in the above link to your phone.
2. Reboot into recovery
3. Select "install zip from sdcard" and choose the ROM .zip file mentioned above. Follow the instructions on screen.
Note: If you choose a different ROM make sure it either includes a kernel that supports system write or you have to install one first by doing the following. Also, if you have WiFi issues after flashing the ROM follow these steps to reinstall the kernel.Installing the Kernel
1. Download a Kernel (such as dsb's Cubed Kernel)
2. Unzip the file and copy the modules.zip file to your phone.
3. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot flash boot boot.img
(once complete)
fastboot reboot recovery
The phone will reboot into recovery, at which point you should flash the modules.zipENG HBOOT
This is *Optional* and allows for additional ADB commands to be used.
1. Download the HBOOT-8064 file found here. (thanks to fnoji111 and Argumentation)
2. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot oem rebootRUU
(once rebooted to the black HTC screen)
fastboot flash zip PL83IMG.zip
(once complete)
fastboot reboot
Mods
These are some mods I found to be essential.Remove the Splash Screen disclaimer
Full instructions can be found here.
1. Go to the above link and download the RegawMOD tool (first post) AND the Droid DNA ENG Hboot plugin (2nd post).
2. Make sure the plugin is in the same folder as the tool.
3. Customize it how you'd like. I chose to replace the disclaimer with my own, that basically reads
If Found, Please Return to
*Drumz0rz*
*My Home Phone Number*
Click to expand...
Click to collapse
4. When you're finished press "Create ZIP" and save the file.
5. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot oem rebootRUU
(once rebooted to black HTC screen)
fastboot flash zip <YourZipName>.zip
(once complete)
fastboot reboot
Now you should have a fully unlocked S-OFF custom ROM, custom Kernel, HBOOT Droid DNA! I hope this helps!
Will this method work for new ota ?
Sent from my HTC6435LVW using xda premium
No, it's just a summary of what's out there. When someone releases a new method to unlock the bootloader I'll update it.
Thank you, when I rooted using the guide linked from one of the sticky posts most of the links were dead, so it is nice to have this.
One suggestion - perhaps include the steps to finish up for those that want to stay on stock rom but be rooted.
drumz0rz said:
No, it's just a summary of what's out there. When someone releases a new method to unlock the bootloader I'll update it.
Click to expand...
Click to collapse
Thanks def look forward to that
Sent from my HTC6435LVW using xda premium
Thanks! Having these steps in a simple guide saved me a good bit of time.
Minor confusion on "Installing the Kernal". I extracted Cubed.Stock.System.Write.zip, flashed boot.img, then flashed Modules.zip in recovery. From the guide, does renaming the package to boot.img work as well?
Lastly, I'm not sure if you want to include flashing/loading ViperDNA's OTA updates.
Is there a way to factory reset phone and eliminate OTA update? I'm assuming no but never hurts to ask....
Sent from my HTC6435LVW using xda app-developers app
John58543 said:
Is there a way to factory reset phone and eliminate OTA update? I'm assuming no but never hurts to ask....
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
No
Sent from my HTC6435LVW using xda app-developers app
steventrev said:
Thanks! Having these steps in a simple guide saved me a good bit of time.
Minor confusion on "Installing the Kernal". I extracted Cubed.Stock.System.Write.zip, flashed boot.img, then flashed Modules.zip in recovery. From the guide, does renaming the package to boot.img work as well?
Lastly, I'm not sure if you want to include flashing/loading ViperDNA's OTA updates.
Click to expand...
Click to collapse
As in renaming the zip? No, you need to do what you said, I left out the flashing the modules. I'll fix that, thanks.
Detailed guide, one question what if you don't have orange juice and want to use Gatorade as a substitute?
Sent from my HTC6435LVW
I'm no nutritionist but I think those two serve very different purposes. Now if you want to substitute it for a glass of say whiskey... that I think is more than acceptable.
Heisenberg's How-To Guide For Beginners
Nexus 6P
{
"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"
}
Intro
This thread will serve as a location for basic how-to guides for the Nexus 6P. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
If you're unsure about something please read the FAQ section in post #3 before creating a post to ask a question.
Prerequisites
Always update your phone to the latest build available before starting the unlocking/rooting process. This guide is always current/correct as per the requirements of the most recent build available.
You'll need a working adb/fastboot environment on your PC to get through some of these guides.
Google have finally decided to allow us to install adb & fastboot without needing to install the entire Android SDK. Hurrah! What does this mean for you? Much less mucking around. Grab the appropriate version for your OS:
Platform tools for Windows | Google USB driver for Windows
Platform tools for Linux
Platform tools for Mac
Main Page
Simply download and extract the archive (and follow the linked instructions for the Google USB Driver for Windows). Once you've extracted the download you should have a platform-tools folder, within that folder you should see fastboot and adb. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Please see older method for installing adb/fastboot here:
You must have Java installed and up to date in order to use the SDK Manager, please ensure that this is taken care of before installing the SDK.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library, Google USB Driver
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Quick Tips
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
How to boot into recovery:
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
Index
Post #1
1. How To Unlock Your Bootloader
2. How To Install A Custom Recovery On Your Device
3. How To Decrypt Your Data Partition
4. How To Make A Nandroid Backup With TWRP Recovery
5. How To Make An EFS Backup With TWRP Recovery
6. How To Root
Post #2
7. How To Install A ROM with TWRP Recovery
8. How To Install A Custom Kernel With TWRP Recovery
9. How To Update To A New Build Of The Stock ROM
10. How To Flash The Factory Images (Return To Stock)
11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
12. How To ADB Sideload an incremental OTA update package.
13. How To ADB Sideload a full OTA update package.
14. How To Update To Android 7.0 Nougat
FAQ can be found in post #3!
1. How To Unlock Your Bootloader
Go into Settings/About Phone, scroll down and click on “build number†continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock†checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue the unlock command:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Note: After unlocking your bootloader, each time your phone boots up you'll be greeted with a warning that says "Your device software can't be checked for corruption. Please lock the bootloader". This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is unlocked it will stay there.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader (section 1).
Download the latest TWRP Recovery.
Make sure you check the md5 of the file to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Boot into the bootloader. Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot flash recovery <filename>.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader you can use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable.
When TWRP boots up you'll be asked whether you want to allow system modifications or to keep it read-only, choose to allow system modifications, there's no benefit to keeping it read-only.
On Nougat you need to flash SuperSU after booting into TWRP otherwise TWRP won't stick (see section 6).
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.
3. How To Decrypt Your Data Partition
This is no longer necessary as long as you use TWRP 2.8.7.1 or newer, unless you are using the Android N developer preview, in which case you must decrypt.
Prerequisites: unlocked bootloader (section 1).
TWRP recovery cannot decrypt your data partition at this stage. In order for TWRP to be able to read/write on your data partition (to root or create a nandroid backup) you will need to format it, a format will remove encryption.
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot format userdata
Please note: this will erase all user data from the device!
Once the process has completed you can either reboot normally:
Code:
fastboot reboot
Or you can reboot back to the bootloader in order to undertake another task:
Code:
fastboot reboot-bootloader
4. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Warning: before you make a backup with TWRP you must remove all lockscreen security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin will result in an "incorrect pin" message), you'll be forced to perform a factory reset to boot into Android. To remove lockscreen security go to Settings>Security>Screen Lock and set it to swipe/none.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot into TWRP and select the backup option from the TWRP home screen, check the system/data/boor boxes, and swipe to backup. The process will take a few minutes.
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key.
5. How To Make An EFS Backup With TWRP Recovery
An EFS backup is very important to have, if your EFS partition becomes corrupt you will have no IMEI, and therefore will not be able to use the phone as a phone. Making an EFS backup is insurance against this catastrophic event. Without a backup, restoring your EFS can be extremely difficult or impossible. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot into TWRP and select the backup option from the TWRP home screen, make sure only the EFS box is selected, and swipe to backup. The process will take a few seconds. Keep a copy of the backup on your phone and also keep another copy somewhere safe.
6. How To Root
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest root version (Magisk, SuperSU) of your choosing to your phone:
Magisk Stable
Magisk Beta
SuperSU Stable
SuperSU Beta
Boot into TWRP recovery and enter the install menu.
Navigate to where you have the root zip stored on your internal storage and select it.
Swipe to install.
Once the zip has installed you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this. You do have root, ignore this every time it comes up.
FAQ can be found in post #3!
Donate To Me
FAQ can be found in post #3!
7. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device. You'll also need to find out what build your ROM is based on and download the vendor image for that build, you'll find the latest in my index here.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your internal storage and select it. You can hit the "add more zips" button now to queue up your gapps package to be flashed after the ROM zip.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
Hit the home button once everything has finished installing.
Install the appropriate vendor image.
Select the install option from the TWRP home screen.
Click the "install image" button in the bottom-right corner.
Navigate to where you have the vendor image stored on your internal storage and select it.
You'll now be asked which partition to flash the image to, select vendor.
Swipe to install.
Once you've installed all necessary zips/images you'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button and you'll boot into your new ROM.
8. How To Install A Custom Kernel With TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
9. How To Update To A New Build Of The Stock ROM
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the latest build via the appropriate factory images for your model (Nexus 6P/Angler) here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
Once all operations are complete you can reboot the device.
You'll have to flash SuperSU again now, plus add any mods that you previously had.
10. How To Flash The Factory Images (And Return To Stock)
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all operations are complete you can reboot the device.
11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box, except it will not wipe any of your personal data (photos, music, etc) from the internak storage.
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into TWRP recovery and enter the wipe menu, select advanced wipe, check only the data box and swipe to wipe.
Go to the TWRP main menu and enter the reboot menu, select bootloader. The phone will now boot into the bootloader, once it has you can connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
12. How To ADB Sideload an incremental OTA update package.
Prerequisites: Completely stock setup (the only modification allowed on the phone is the unlocked bootloader).
Download the appropriate OTA zip from my index. OTA updates must be taken in order so you must select the right zip. For example, if you're currently on the MMB29Q build you must select the MMB29Q --> MHC19I zip. The filename will be quite long so to make things easier you can rename it to something easier. For the purposes of this guide let's say we'll rename it to "ota.zip". Place the file in your fastboot folder on your PC.
Boot into the bootloader, use the volume buttons to scroll the options and use the power button to select recovery mode.
Once the phone has booted into the stock recovery (you should see Andy Android with an exclamation mark) hold power and tap volume up to get into the recovery menu. Use the volume buttons to scroll and use the power button (you might need to hold it) to select "apply update from adb".
On your PC navigate to your fastboot folder, hold shift and right-click your mouse, select "open command prompt here". Issue the following command:
Code:
adb sideload ota.zip
Wait for the operation to complete (it'll tell you once it's finished) and once it's all done you can reboot your phone, the first boot might take a while.
13. How To ADB Sideload a full OTA update package.
Prerequisites: Completely stock setup (the only modification allowed on the phone is the unlocked bootloader).
Download the OTA zip that you want to upgrade to from my index. You don't need to be on any specific build prior to flashing a full OTA package. You can only move to a higher build though. The filename will be quite long so to make things easier you can rename it to something easier. For the purposes of this guide let's say we'll rename it to "fullota.zip". Place the file in your fastboot folder on your PC.
Boot into the bootloader, use the volume buttons to scroll the options and use the power button to select recovery mode.
Once the phone has booted into the stock recovery (you should see Andy Android with an exclamation mark) hold power and tap volume up to get into the recovery menu. Use the volume buttons to scroll and use the power button (you might need to hold it) to select "apply update from adb".
On your PC navigate to your fastboot folder, hold shift and right-click your mouse, select "open command prompt here". Issue the following command:
Code:
adb sideload fullota.zip
Wait for the operation to complete (it'll tell you once it's finished) and once it's all done you can reboot your phone, the first boot might take a while.
14. How To Update To Android 7.0 Nougat
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the Nougat factory images for your model (Nexus 6P/Angler) here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
You can skip flashing the recovery if you wish, but even if you do the stock recovery may be patched on the first boot anyway. So you'll need to flash TWRP and SuperSU again if you need/want those, as well as any other system modifications you may have had.
Note: Do not flash the userdata.img
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
You'll have to flash SuperSU again now, plus add any mods that you previously had.
FAQ can be found in post #3!
Donate To Me
Frequently Asked Questions
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
[/INDENT]
[INDENT]adb reboot bootloader[/INDENT]
[INDENT]
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
2. How do I boot into recovery?
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
[/INDENT]
[INDENT]adb reboot recovery[/INDENT]
[INDENT]
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
3. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.
4. After unlocking the bootloader I get a message that says "Your device software can't be checked for corruption. Please lock the bootloader". What's going on? Can I get rid of it?
This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is locked it will stay there.
5. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot, see section 9 of this guide for full instructions.
6. Does taking an OTA update wipe my user data?
No, it doesn't.
7. Do I need to make an EFS backup?
Yes. Absolutely yes. An EFS backup is extremely important, if your EFS partition becomes corrupt your IMEI will disappear and you will not be able to use the phone as a phone. Without a backup it can be extremely difficult (or impossible) to restore your EFS.
8. Do I need to flash the userdata.img from the factory images?
You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
[/INDENT]
[INDENT]fastboot format userdata[/INDENT]
[INDENT]
Reserved
Reserved
Reserved
Reserved
thanks
works great
The_android_Modder said:
works great
Click to expand...
Click to collapse
Lol, how?
Heisenberg said:
Lol, how?
Click to expand...
Click to collapse
Magic
tyvar1 said:
Magic
Click to expand...
Click to collapse
xxtruplayaxx16 said:
lmao
Click to expand...
Click to collapse
He must be from the future...
The_android_Modder said:
works great
Click to expand...
Click to collapse
thank you for the morning lolz
If we wanted, could we just go to step 4, and not do the rest? I.e just root stock and leave it as is?
Is that safe?
If it is, can I flash a rom on later?
Thanks
(I know the device isn't out yet, just getting prepared for it.)
tf2manu994 said:
If we wanted, could we just go to step 4, and not do the rest? I.e just root stock and leave it as is?
Is that safe?
If it is, can I flash a rom on later?
Thanks
(I know the device isn't out yet, just getting prepared for it.)
Click to expand...
Click to collapse
No, because you need a custom recovery in order to flash SuperSU, and you need an unlocked bootloader to flash a custom recovery. Why not just unlock the bootloader?
Heisenberg said:
No, because you need a custom recovery in order to flash SuperSU, and you need an unlocked bootloader to flash a custom recovery. Why not just unlock the bootloader?
Click to expand...
Click to collapse
Ah you misunderstood me, I mean like do all steps upto 4, and then not do the rest?
Sorry for misunderstanding
tf2manu994 said:
Ah you misunderstood me, I mean like do all steps upto 4, and then not do the rest?
Sorry for misunderstanding
Click to expand...
Click to collapse
Ahh ok, now I understand. Yes of course, they're not actually steps that all need to be completed, they're just numbered sections. So if all you want to achieve is to root your stock ROM then you only need to follow steps 1-4.
Hemm sorry but are we talking about a phone that doesn't exist?
Fentadroid said:
Hemm sorry but are we talking about a phone that doesn't exist?
Click to expand...
Click to collapse
It certainly does exist, it just hasn't been released yet. And as it says in the OP these processes remain virtually unchanged from model to model in the Nexus line.
Heisenberg said:
It certainly does exist, it just hasn't been released yet. And as it says in the OP these processes remain virtually unchanged from model to model in the Nexus line.
Click to expand...
Click to collapse
I hope that too!!!
Great Job
Thanks for your Hardwork:good: