Database Develop

[Newbie Guide] adb/fastboot/bootloader/android 101

The purpose of this document is to clarify a few basics about HTC Android Phones and basic commands to interface with the phones. Think of this as a beginner's guides to the Android device from a non-traditional user's point of view. I'll keep it simple and plain as much as I can for the new users. I'll also try to keep all the technical aspects true as much as I can while keeping it simple.
Before you go on, please read this and understand the basic concepts and how and why following commands are being used. Do not follow anyone's instructions/tutorials/guides without prior basic understanding of what each command do. I do want to believe it's humans visiting this forum and not lemmings. If you do not understand, feel free to ask here. I will or someone else also knowledgeable will answer your questions. DO NOT QUOTE THIS AS A WHOLE. My pet peeves and a complete waste of screen space.
Sometime, depending on your OS, command names may change (e.g: mouse / mouse.exe / mouse-linux / mouse-mac). For general purpose, we'll use mouse instead of an OS specific commands in this instructions.
So to repeat myself, if you understood the concepts of the commands, and you are on a linux system and someone's guide says touch index.php, you will automatically type touch-linux or whatever the name of your executable is on your system.
​
We shall assume you know how to install needed drivers and where to get android sdk and put the sdk binaries (executables) in the system path. If we need to expend this let me know and I'll expend this here.
Further, if I get any parts wrong, PM me and I'll get those parts corrected.
Android Partition, SPL etc.
Partitions:
Followings are a list of partitions on your android phone.
misc - misc partition -
recovery - Recovery Partition - This is where the original HTC recovery or Amon Ra's recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the phone, this area is wiped)
So, if you replace the recovery image, you are pretty much set for updates provided here at XDA. Note: By replacing your recovery image, you may not be able to have OTA updates.
ROM images will normally replace boot and system images at the same time and often time, userdata and cache too; reseting the phone completely.
SPL/Bootloader/Radio/Bricking Phones:
SPL / Bootloader is like BIOS on a computer. At least I think of it that way. SPL can be updated! SPL comes as either Security-On of Security-Off (S-ON/S-OFF).
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one and only reason for phones being bricked. You can not brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into HTC for repair.
How do I know the phone is bricked? A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Commands:
adb - Android Debug Bridge - One of the two things you'll need to know if you ever want to do anything non-conventional on your android based phone.
List of commands that can be used by adb can be prompted by typing adb at the system shell (command prompt or terminal)
Notable adb commands:
adb devices - If you don't know anything, this is the ONE thing you have to know.
adb devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
adb reboot (bootloader|recovery)
adb reboot - this will reboot your phone normally.
adb reboot bootloader - this will reboot your phone back into the bootloader (white screen with the android on wheels)
adb reboot recovery - this will reboot your phone back into recovery console (either default or amon_ra's recovery).
adb shell - this will shell into the phone and you can now explore the phone. Remember phone's native backend os is linux so know your linux commands.
adb remount - remounts the system partition on the phone so you can you read/write to it.
adb push xxx yyy - will push xxx file from computer into yyy location/file on phone (needs rooted access)
adb pull xxx yyy - will pull xxx file from phone into yyy location/file on computer (needs rooted access)
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Notable fastboot commands:
fastboot devices - If you don't know anything, this is the ONE thing you have to know.
fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - this will unlock your bootloader - NOTE THIS WILL VOID YOUR NEXUS ONE WARRANTY
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
If anyone needs me to dig deep into using anything else, please PM me. I'll add it on here. Hopefully this will help all newbies about the basic commands and what they do.
FAQs (UPDATED Feb 09, 2010)
Q: One question about the Android SDK. Do I need it to flash my N1 or just to program new apps? Where can I get it?
A: Android SDK is not entirely needed to flash the N1. However, there are tools in there that you need. Adb / Fastboot etc. Although they can be downloaded by themselves, the windows version of the SDK also have the Drivers that are needed for android devices for USB connection. So, it is recommended to get it. You can get it from developer.android.com
Q:I have never experienced anything like this when I did a hard-spl on my winmo phone. Radio versions are included with SPL's, right?
A: Official packages from HTC did come with nbh packaging, meaning it is a all in one upgrader that will update Radio, ROM, System etc, it is very much common for active development area here at XDA to get the radio or SPL or ROM separately and independently of one another. And as such, you will most likely flash them seperately (who wants to wait 6-8 months). Also, since this phone is released by google, HTC will most likely not update any major Radios. However, it is very likely that we will be hacking in Radio updates or any other "updates" from HTC from their new device - HTC Bravo.
Q: Is there a guide for snow leopard? I'm kind of stuck.
A: I personally ran android SDK and aforementioned executable on both MAC OS 10.5 and 10.6. Like I posted, the commands and the executable names may be slightly different. I may call adb and you may find it as adb-mac. I am not going to write 3 separate documents for 3 separate OSes. You have to know that adb=adb-mac (on your mac), adb-linux (for linux) etc. And yes the above guide will work universally.
Q: Can i replace the splash image..?? (unlocking related)
A: As of the above date (next to the FAQ) no you can not. Issue is probably a few folds. One of them is that splash1.img is not going in due to security lock. Remember, you unlocked the phone. HTC will not like it. Anyhow, I like the current quad color X. If you are thinking of getting rid of the lock logo, good luck. Even if you can get rid of it, you will still have to overcome the pink text that says ***UNLOCKED*** on your bootloader.
Q: Can you run Windows Mobile on Android Phones?
A: With enough resources given, sure. Will it ever happen? No. Why? Windows mobile compiler and builder cost $. As a matter of fact, as of version 5, it was going to cost me $75 per device. That's one of the reasons why handset makers went to Android open platform. Android is free and universal so as long as you use certain chipsets and certain items, you are good to go. Can it ever be ported? Sure. With right amount of time and money anything can be done. But at this point, it's cheaper for you to go buy a windows mobile smartphone.
Q: How do I know the phone is bricked?
A: You can not brick a phone unless you are flashing Radio/SPL packages. Make sure if you are doing that, you follow directions VERY CAREFULLY. A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Q: I have installed the Android SDK however, i cannot seem to get the laptop to detect the nexus. What have i left out?
A: Most common item that people forget to enable is USB Debugging. Settings => Applications => Development => USB debugging [checked]
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Q: Which step of the rooting / recovery procedure does it give root?
A: Root and Recovery are two totally different things. Recovery is a partition that contain recovery information. Stock recovery is what allows OTA updates etc. Normally it will search for update.zip in the root folder of the SD card. Amon_RA's Recovery or any other recovery images are there to enhance the traditional stock recovery. Amon Ra's Recovery for example, contains thing such as ability to update from different zip files, and backup/restore of your data/system.
Rooting is not done by recovery but is a kernel level access (simply put) that will give root or "SU". It is done by patching the boot partition of the your android device.
Q: What are the differences, advantages, disadvantages of the different ROM's?
A: They are all different. Some have some features, some are plain stock, some are made for bleeding edge kernel etc. You'll have to try them out and figure out yourself. I may make a chart of what they are (see the bottom at my signature - wiki) but with too many android devices, I will need some major help. One person alone will not have total knowledge of all the ROM releases. There are just way too many devices and ROMs.
Q: Which ROM will allow OTA updates?
A: Stock ROM WITH Stock Recovery.
Q: If the phone is SIM/carrier unlocked and you root do you have to SIM unlock again?
A: SIM/Carrier unlock has nothing to do with rooting your phone. You can still have root and still be carrier locked. Nexus One comes carrier unlocked from factory.
Q: How much space is there for apps? is using the sd card really necessary? (on Nexus One)
A: Search google? The phone has 512MB or space. That SHOULD be more than enough for you. If not, you have some serious issues. I do not believe you will not App2SD for Nexus One. Google did say during the release conference that they will update Android/N1 so that apps can be run/installed to SD but that requires some system and security changes (mainly to prevent pirated software - Yes if I write something, I deserve to get paid for it).
Q: When you do "flash zip from sdcard" or "fastboot flash image" does this merge and overwrite the files in to the partition?
A: When you update a software (via recovery), software my be merged. However, if you fastboot flash, just like the word flash says, it will flash and overwrite the partition.
Q: Which partition does "flash zip from sdcard" affect?
A: Depends on what you are flashing. It could be any or all of the partitions such as SPL, Boot, System, Recovery, Radio. You should study first before randomly flashing things.

sorry, got it!

blakestimac said:
i apologize if this is the wrong place for this but, but i have adb setup perfectly, but fastboot is not recognized at all. could i have missed something?
Click to expand...
Click to collapse
I need your system info.
What os are you running? where did you get fastboot? what are you trying to do?

Don't forget fastboot boot for testing images. My most used command

I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe

really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?

wishmaker738 said:
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
Click to expand...
Click to collapse
Check the FAQ.

dylanfan424 said:
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
Click to expand...
Click to collapse
Ok. I need to know what you actually did. I am not understanding what you are trying to do.

Can't run adb commands - device not found
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.

Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.

dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
I'm a noob so can't offer much help...but I would make sure the usb drivers are installed if you're using windows....this probably should have happened when you installed the sdk, but you can also install it through the device manager and point it to the folder where the usb drivers are located. Also make sure the phone is in USB debugging mode. also you may need to reboot your pc. Make sure you have setup running when you run the adb commands. you need to be in the same directory as the adb file, or in the case of the superboot pack you need to type "adb-windows" not just "adb". you may also need to put .exe, ie adb-windows.exe.

pwnvds said:
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Click to expand...
Click to collapse
You run fastboot from the white screen. Android on non-white screen. It's one or the other. It's ADB or Fastboot (depending on the mode of the phone).

dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
Is the directory where ADB/fastboot (SDK) is installled in your system path?
I am guessing it's not. If it was, just by typing adb alone (without commands), it'll give you a list of commands. Click here if you want to know how to change your system path to include a particular folder.
We're now in the age of nintendo pilots and point and click OS that no one knows how to use command lines and system paths anymore.

recovery
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?

umplarry said:
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
Click to expand...
Click to collapse
Answered in FAQ area.

seraph1024 said:
Answered in FAQ area.
Click to expand...
Click to collapse
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?

umplarry said:
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
Click to expand...
Click to collapse
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Click to expand...
Click to collapse
There you go.

seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
Thanks for your help

seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
I had it downloaded, just had not flashed it

I've been looking all over, but I probably need to check the HTC Dream forum or something.
How do I install a custom ROM? I know you have to adb push update.zip somewhere, but I can't find any info about this. Please help.

[GUIDE] Turkeys' Ultimate Guide to Root Wildfire v42.1.2 (Easy & Safe!)

Turkeys' ULTIMATE Guide to Rooting v42.1.2
Note: It does not work on 2.2.1 Wildfire's (i.e. - Any bought after Feb - March 2011)
Like this guide? Hit the thanks button at the bottom left of this post
Before You Start
This is a new type of guide, an experiment if you like. The whole point is to get you with a fully functioning, rooted phone. But also to teach you something. Each step first tells you what you're going to do before you do it. By the end not only should you have a rooted phone but you will hopefully have priceless knowlege of how Android works.
Enjoy.
Need Help?
If at any point during this guide you need help, something's gone wrong or you need some extra clarification. Hit the help button.
The help button will link you to the #rootmydroid IRC help chat channel, where you can ask questions or get walked through the whole thing if you really need to. We have experts on hand to help you out.
PLEASE NOTE: At peak times our experts may be busy so please be patient.
So, Mr. Turkeys, what have you got for us today?
Root Guide
Post 1 - Intro
Post 2 - UnrEVOked (Rooting)
Post 3 - Flashing a ROM
Post 4 - Flashing a new Radio
Other Guides
Unroot
A2SD
More Coming Soon... Stay tuned!
So, click a link to the guide you want and get cracking, enjoy!
Donate
Should you feel the crazy need to donate to me, you can do so below.
GBP
EUR
USD

So, you wanna root?
Rooting is not easy like some people make it out to be. All these 1 click Noob-Proof tools can actually go wrong. And they do.
But lets get this clear, IT'S ALMOST impossible to brick. I'd put the odds on about a 99.9% chance you will not brick beyond repair. However, things probably will go wrong, which is why you will need to follow the instructions very carefully.
Pre-Root Info
I want to make sure the rooting process goes well for as many as you as possible, so get ready to read lots of information that will turn you from a Noob into a lean, mean rooting machine.
And for those of you who like to slack off and think "I cba to read all that crap", I've made it so you have to answer a question to get the download links. Aren't I nice. Seriously though, it really will be a lot easier for you if you read all of this, you will thank me for it one day.
Pro users who know what HBOOT is, how to flash a ROM and can use ADB can safely skip this step
Android Glossary
This page is probably the most valuble bit of information you will ever need during your rooted life. Behold, the VillainROM Android Glossary. (Cheers Pulser )
http://bit.ly/9HtICk
Read it. Read it ALL. No questions asking for these terms will be tolerated in this thread and you will be teased so much you will want to die. So please, read it carefully.
Downloads
Now, for the bit you've been dreading. 2 downloads. 2 questions. One answer will link you to the download. The other two will link you to a humorous fail picture. (And for all you sneaky cheaters out there, I've bit.ly'd the links. Take that.)
Question 1 - UnrEVOked download
What do you use to flash a ROM?
A) UnrEVOked
B) ADB
C) Recovery
Question 2 - Other Stuff Download (We may ask you to use this on the help channel)
What is a RUU?
A) A tool to root your phone
B) A tool to return your phone to 'stock' (unroot)
C) A tool to flash a ROM
You can also get countless lulz from adding a + to the end of those links and comparing the wrong answers to the correct ones. Yes people really don't read the information.
OK, I've talked enough now, let's get down to business...

So, hopefully you now know all the terms, which makes my life a lot easier as I don't have to explain everything. Let's begin.
Root Guide - Pt. 2 - UnrEVOked
1) Ensure you have downloaded and extracted the first download in the above post to somewhere you can remember and access easily. For the purpose of this guide, I will refer to that folder as the 'Root Pack'.
Next, we are going to prepare the UnrEVOked program to run. If you are a Windows user, this means installing the drivers, if you use Linux or Mac you just have to run the app as mentioned later. We have to install HTC Sync to get adb drivers and we have to uninstall it again as it interferes with UnrEVOked. The drivers however remain which is why you need to install it.
2) (Windows Only) If you have not already, download HTC Sync and install it. Then uninstall HTC Sync as well as any other software that may interfere such as doubletwist. Next, follow this guide to set up the hacked HBOOT drivers. Make sure you reboot your PC after doing this.
Next, we need to prepare your phone. We will make sure USB Debugging is on as UnrEVOked needs this to send adb commands to the phone. We also need to enable Unknown Sources so that UnrEVOked can push busybox and SuperUser Permissions apps to the phone.
3) With your phone go to Settings > Connect to PC > Default connection type > Charge Only and untick Ask Me. Then go to Settings > Applications > Development > Make sure USB Debugging is ticked. Then go back to Applications and make sure Unknown Sources is ticked.
Next, we're going to run UnrEVOked. What it does is reboot into HBOOT mode, and use an exploit to gain a temporary NAND unlock. Then it uses fastboot to flash a recovery image, and then pushes the su files required for root.
4) WINDOWS USERS: Right click on the 'unrevoked.exe' file (Or something similar) in the Root Pack and click 'Run as Admin' (Not required for XP)
LINUX USERS: Right click the 'ClickHereToRoot.sh' file and UnrEVOked will start. (Make sure you chmod 755'd it first)
MAC USERS:
mattbeef said:
Unrevoked, if your a mac user like myself then drag the app inside the dmg to the desktop and run it from there. Most mac users are lazy and will try to run it from the dmg.
Click to expand...
Click to collapse
GETTING A MISC RELATED ERROR? See post eight.
Your phone should now reboot and then congratulations! Your phone is rooted. However, the root that UnrEVOked gives you is basic. No ROMs or good stuff. So you must read on to the next post to flash a custom ROM...

Now you've rooted, let's flash a ROM. We will backup all your apps then flash a ROM then restore your apps. Ready?
Pt. 3 - Flashing Your First ROM
**NOTE: You can repeat Pt. 3 every time you want to flash a new ROM or update
Next we're going to download and use Titanium Backup to backup all your apps as we will have to wipe your phone to install the ROM. You can use the same method if you ever want to backup/restore in the future too.
1) Download & Install Titanium Backup from the market. Open it and hit the 'Problems' button to download busybox, a suite of commands for rooted phones.
Then hit menu then batch, and tap the button next to Backup All User Apps + System Data. Let it complete before moving on to the next step.
Next we're going to reboot into recovery mode to flash the ROM. You can use this if you ever need to get into recovery in the future.
2) Turn your phone off and turn it on again holding POWER + VOL DOWN to enter HBOOT mode. Wait a few seconds while it checks for images before using the VOLUME KEYS to scroll and POWER to select Recovery. Your phone will now vibrate and reboot into recovery mode!
Next we're going to do a full backup of your phone using Nandroid. This will backup the entire state of your phone in case you ever
want to go back. You should really do this every time you flash a new ROM.
3) Use the TRACKBALL to scroll down to where it says Backup or Nandroid or Backup / Restore. Then select Backup and wait for it to finish.
Now we need to wipe your phone. Whenever you flash a different ROM you should Always do this, when you are updating the ROM you should check on the release thread for information.
4) If you are not on the Main Menu in recovery, hit back a couple of times to get there. Then, use the TRACKBALL to navigate down to 'Wipe Data / Factory Reset' and accept the scary warning to wipe your phone.
Now we can flash the ROM! Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card. The flashing process may take a few minutes.
5) From the Main Menu, scroll down to and select Install zip from SD Card and then select Choose zip from SD Card then select where you put your ROM and wait for it to complete. Then, select Reboot System Now to reboot into your shiny new ROM!
Your phone will now reboot, it may take a while to reboot as it's rebuilding the Dalvik Cache. If it still doesn't boot up after 10mins, pull the battery and consult the ROM thread for troubleshooting.
Now we're going to restore that Titanium Backup you made before starting Pt. 3. It will restore all your apps back but not system data. (ie Settings) You can use Titanium Backup any time you want to backup/restore your phone.
6) Download & Install Titanium Backup again and tap Menu Button > Batch > Restore Missing apps + data. It should prompt you to reinstall every app again.
--------
Congratulations, you have qualified with a rooted phone from the Turkeh Root School!
(Unless you're reading this without having actually done any of this guide)
So, go off and ask questions, answer questions, and contribute to the community! We'd also really appreciate it if you could hang out in the help channel to help other people trying to root too.
Thanks for rooting! You can also follow some of the other guides to install all apps on the SD card, Unroot & S-OFF

Pt. 4 - Flashing a New Radio
Flashing a Radio
The radio is the lowest part of your phone. (ie It's the very first thing that loads when you turn your phone on.
Most ROMs will have a required radio version, but most will agree that it's best to be on the latest as they often improve battery life etc.
You can downgrade your radio and you can find your radio version by going to Settings > About Phone > Software Information > Baseband Version.
Your ROM should tell you on it's thread what the recommended radio version is, so download it, transfer it to the root of your SD card as you did in Pt. 3 then follow this.
Now we're going to reboot into recovery mode as we did in Pt. 3 to flash the new radio. There is also an app on the market called 'Quick Boot' which you can use to quickly get into recovery. The next step will assume you have this.
1) Open Quick Bootand tap Recovery then tap Allow on the SuperUser permissions prompt.
Note: The SuperUser Permissions app will prompt you whenever an app is requesting to use root. You should look over which app is requesting this before you allow it.
Next, we need to flash the radio. You do this exactly the same way as you flash a ROM, which you did in Pt. 3.
2) Use the same method you flashed the new ROM in Pt. 3 to flash the radio. You do not need to Nandroid backup or wipe to do this, just flash the zip.
Note: Your phone may reboot a couple of times and will show a picture of the Android Robot while it is flashing the radio. It has NOT crashed, it is flashing it. DO NOT pull the battery, it will reboot when it is done.
Your new radio has now flashed!

A2SD
Note: It has come to my attention that doing this with ROM Manager doesn't work most of the time. If you have problems please partition your card another way. (I recommend GParted - There is a Live CD if you don't have Linux)
First, we need to partition your SD card with ROM Manager. This will wipe all the data on your SD card so please backup before continuing.
1) Open ROM Manager (Download it from the Market if you don't have it - Although you will need the Market Mod to show all apps) and press Menu > Manually Override Recovery **Not sure exactly what it says, pls could someone help me out here** Then scroll down to Partition SD Card. Choose the ext size you want for your apps to be installed on, then tap 0 for swap size, then tap OK to reboot into recovery and start partitioning!
Note: While it's partitioning it will show a picture of an Android. You can press (Power?) to see what it's actually doing and if there's any errors.
Now, you need to check the ROM thread for info. Most ROMs activate it automatically when it detects an ext partition on your phone. On some others you need to flash a special update.zip. If you are unsure hit the help button on post 1 and we'll help you out.
Congratulations, you now have Apps2SD! Exactly what you will have (dalvik2sd etc) will vary between ROMs.

Unroot
These RUU programs that you use to unroot are Windows only, but fortunatley I wrote a tool for Linux called OpenRUU so you can flash them on there. If you are a Mac user, take a moment to ask yourself 'Why am I using a Steve Jobs product?' as there is no way for you to run the RUUs.
First, we are going to identify what RUU you need to download and flash then download it. (Bravo is the codename for Desire, all RUUs use this name)
1) Go to shipped-roms.com, click on the Android Robot then click on Buzz. Now, you need to recall what version of Android you were on before you rooted. If you had a carrier supplied device you should also get the one that is applicable, but if you are unsure or your carrier is not listed go for one that says WWE. (World Wide English - All Languages) Or come on our IRC channel for advice.
Note: HTC Sync must be installed before continuing. The next step will also wipe all your apps + settings!
Next we're going to run the RUU, this should take around 5-10mins. DO NOT touch your phone during the flashing process!
2) Double click on the RUU file you downloaded in step 1, read the readme, and click to start the flashing process.
After it's done! Your phone now should be completley back to stock status!
If you get an error during the flashing process, try again and then come on our IRC help channel for assistance if it persists.

Fixing the Annoying unrEVOked Backup CID Missing errors
NEW, EASY METHOD
I managed to find unrEVOked 3.2. If you want to use that as a fast-track then that's fine, but please read the following carefully:
Code:
[B]DISCLAIMER:[/B]
Please be aware that this build was pulled from unrevoked.com because it was not safe.
USE AT YOUR OWN RISK!
If it ****s up and you point the finger at me, I will laugh at you.
This is only for 'Backup CID Missing' errors. if you use this on any other type of misc error it might brick.
Download. Run in replace of unrEVOked 3.21 in the standard guide.
You can still use the old, misc editing guide below:
(Guide edited from http://home.kennynet.co.uk/~kenny/bcid-fix.txt to be more noob-friendly)
This fixes:
Backup CID Missing
Unfortunately, because a couple of people corrupted their misc partitions during the testing of unrEVOked 3.2, they brought in a load of stupid, annoying safety features that included checking the misc partition on your phone.
/rant
What is misc?
Misc is a partition on your phone. It holds various switches and stuff, such as your:
Official HTC ROM Version
Your CID (Which tells the phone what carrier/region your phone is)
However, sometimes, the CID is not in misc or your misc is corrupted. This process will add in the CID to misc and reflash misc. (which may fix other misc related errors but probably wont)
Warning! Misc is quite an important part of your phone. If it gets severely corrupted you may loose USB access. Me or anyone on our IRC help channel take no responsibility if you **** up somehow.
This guide is designed for Windoze, Linux users use common sense adapting the instructions and can use a Linux hex editor like ghex. (Works just the same)
Please ensure you have downloaded the other stuff file on the second post before continuing and have extracted it to C:\root.
First, we need to use adb to grab misc off your phone. We will get temporary root then grab misc.
1) Open a command prompt on your computer by going to Start > Run and typing cmd then pressing enter. Now type the following pressing enter on each line. (Make sure your phone is connected and you have the drivers installed.)
Code:
cd \
cd root\adb
adb-windows devices <---- Make sure it finds your phone before continuing
adb-windows shell <----- You should see a $
$ /system/__unrevoked_su <---- Getting temp root
# cat /dev/mtd/mtd0 > /sdcard/misc.img <---- Copying misc to your SD Card
# getprop ro.cid <----- This is your CID. Remember what this says, it should say something like HTC_000 or 1111111 if you have a goldcard
# exit
adb-windows pull /sdcard/misc.img misc.img <---- Getting the misc we copied before
You should now have a file called misc.img in the C:\root\adb folder.
Now come on to the IRC help channel here. We will stick the CID into the misc.img so you can carry on as it really is complicated. You can also post here if nobody is avalible and I will sort it ASAP.
(If you've done hex editing before, all you do is put the CID you got above in at position 0 then add a 00 at the end so the hex string looks something like "48 54 43 5F 5F 30 30 31 00")
Make sure you save the file that we give you back to C:\root\adb overwriting the original misc.img file.
Next we're going to push misc back on to the phone using a similar method to step 1. Have open a command prompt and cd to the correct directory as in step 1 before proceeding.
2) Type the following in the command prompt:
Code:
adb push misc.img /sdcard/new-misc.img <---- Pushing misc back to your SD card
adb-windows shell
$ /system/__unrevoked_su <---- getting temp root again
# /data/local/flash_image misc /sdcard/new-misc.img <---- Using flash_image to flash the new misc
# exit
Now rerun unrEVOked and everything should be as shiny as the plastic Samsung use to make their phones.
Click to expand...
Click to collapse

Reserved for good measure.

I'm sure this will help many people. Should be sticky'd

HCDR.Jacob said:
I'm sure this will help many people. Should be sticky'd
Click to expand...
Click to collapse
Good Idea!!!
For the rru you need to click on the windows mobile section and select buzz NOT bravo

Added A2SD guides, misc fix & unroot guide. Bump to v42.1.2

Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin

PanGalactic said:
Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin
Click to expand...
Click to collapse
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now

42turkeys said:
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now
Click to expand...
Click to collapse
And buzz is under windows mobile for some reason

The guide really great....but the shipped rom website don't have RUU for Buzz

coltrain said:
The guide really great....but the shipped rom website don't have RUU for Buzz
Click to expand...
Click to collapse
Look under windows mobile - who put it there? Those files do work.

This thread still not stickied?

Piece of art already. Should be stickied for sure.

I thought a bit about 'reporting' the thread to make a mod notice it but it said specifically what report was to be used for , so i didn't do it , i guess we'll have to bump it up so it gets stickied. Great post !!

Root guide with lots of pictures and instructions [AndroidNZ]

Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.

Would be nice if you posted that guide on this forum too.
Thanks for the guide.

Oooohh pictures

Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic

Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?

Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.

"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.

JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"

Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!

mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.

mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!

[Q] Newb here making progress. Got a question for my next step on rooting.

So I have done my homework and read tutorial guide and the nexus all in one beginners guide.
It took me a few hours to be able to get my pc to recognize my computer in fastboot mode using sdk and adp. (Hopefully my terminology is on track but doubtfully so).
So now in the command prompt, i can get the pc to recognize the phone in fastboot mode. Now all I really want to do is (this may sound silly) is to be able to use Air Mirror in airdroid... for now. I do like the stock android feel to this phone as I am new to nexus from the touchwiz **** from samsung.
So can i proceed to the commands of:
fastboot oem unlock
then
fastboot reboot
and then be done with it? Proceed to set up my google account and download my previous apps and contacts yada yada?
TIA

Hamm1701 said:
So I have done my homework and read tutorial guide and the nexus all in one beginners guide.
It took me a few hours to be able to get my pc to recognize my computer in fastboot mode using sdk and adp. (Hopefully my terminology is on track but doubtfully so).
So now in the command prompt, i can get the pc to recognize the phone in fastboot mode. Now all I really want to do is (this may sound silly) is to be able to use Air Mirror in airdroid... for now. I do like the stock android feel to this phone as I am new to nexus from the touchwiz **** from samsung.
So can i proceed to the commands of:
fastboot oem unlock
then
fastboot reboot
and then be done with it? Proceed to set up my google account and download my previous apps and contacts yada yada?
TIA
Click to expand...
Click to collapse
yup, make sure you have all data backed up to a pc, OEM Unlock will wipe your internal storage.
you also need to unlock developer settings, by tapping the build multiple times. Once unlocked you need to go into developer settings and click the check box to allow OEM Unlock
Afterwords if you want to run root, don't fastboot reboot you can use chainfires auto root and root-windows.bat and let it do its thing, then it will reboot and you can setup google account and move your files back over
If you want to flash TWRP, download that .img file and either use flashify to flash it from the google market or use fastboot flash recovery recovery.img

so it sounds like if i want root access, to do things such as air mirror from airdroid I need to flash cf's auto root?
Also in the all in one guide in imlicitly states to not skip the fastboot reboot step. Is this just a if you can do it, then do it step?
And yea, everything is backed up into google drive/cloud/plus and so on. So I am hoping once I am done I can setup my google account and everything should sync back as normal?
BTW thanks for the speedy reply.

Hamm1701 said:
so it sounds like if i want root access, to do things such as air mirror from airdroid I need to flash cf's auto root?
Also in the all in one guide in imlicitly states to not skip the fastboot reboot step. Is this just a if you can do it, then do it step?
And yea, everything is backed up into google drive/cloud/plus and so on. So I am hoping once I am done I can setup my google account and everything should sync back as normal?
BTW thanks for the speedy reply.
Click to expand...
Click to collapse
If you want to go the CF Auto root, you can just run root-windows.bat and it will actually perform the OEM Unlock step and complete that process for you, then it will root the phone and youll be back at the setup screen to enter your google account info, I think this will be the easiest route. It will take care of OEM Unlock, Adding Superuser and the binaries so you can run air mirror and any other root required app.
Yup if everything is backed up then once your login to the google account it will resync your apps and you can login to anything that needs credentials.

should I run fastboot reboot after it does its thing?

Hamm1701 said:
should I run fastboot reboot after it does its thing?
Click to expand...
Click to collapse
no, once you execute the root-windows.bat it will do all the fastboot commands, youll just have to hit a key on the CMD prompt after executing, it gives you a warning that OEM Unlock will wipe data, but you are already aware of that.
Basically, download cf-autoroot for shamu
unzip the zip into the same folder you have ADB installed (platform-tools)
get into adb and boot into bootloader mode or if your phone is in android already, adb reboot-bootloader
then root-windows.bat in the cmd window
and it will walk you through it from that point.

Circaflex said:
no, once you execute the root-windows.bat it will do all the fastboot commands, youll just have to hit a key on the CMD prompt after executing, it gives you a warning that OEM Unlock will wipe data, but you are already aware of that.
Click to expand...
Click to collapse
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img

Hamm1701 said:
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Click to expand...
Click to collapse
Do you have file extensions turned on for windows?
Depending on your version of windows it is different, but if they are turned on you would see the extensions for all files, if they are not turned on your files will not be showing extensions. If there is no extension rename the file to recovery and that's all if there are extensions youll see two .img's
Place that in your platform-tools folder as well, once autoroot is all installed and does its thing, set your phone up completely and get all the good stuff going
then power down and boot into boot loader or again use adb reboot-bootloader
then fastboot format cache (this wont harm any data or settings)
very important to then boot into recovery and let it load, then use recovery to reboot phone and youll be back in the android system
OR
download Flashify from the play store and select the .img you downloaded and it will flash the file, it works great

Hamm1701 said:
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Click to expand...
Click to collapse
Just manually flash it....
fastboot flash recovery whatever-your-file-is-called.img
No need to rename it.
If you're going to remain rooted, it's a good idea to understand adb and fastboot correctly. Please take the time to read my thread.
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500

@Hamm1701 how did it go

Circaflex said:
@Hamm1701 how did it go
Click to expand...
Click to collapse
Yikes, didnt realize my post didnt go through last night. Well it went very well. I'll admit that when the little android guy was staying on "erasing" for a few to 5 ish min i started to panic a little. I was expecting something like erasing then installing then some other imaginative windows installation words.
But I am now trying to figure out why a certain app is not working 100% as it was before the root and unlock procedure. Ill be researching on learning how to provide feedback developers can use to make any neccasry changes. Do you know of any such threads/posts I can read up on in this regard?

Hamm1701 said:
Yikes, didnt realize my post didnt go through last night. Well it went very well. I'll admit that when the little android guy was staying on "erasing" for a few to 5 ish min i started to panic a little. I was expecting something like erasing then installing then some other imaginative windows installation words.
But I am now trying to figure out why a certain app is not working 100% as it was before the root and unlock procedure. Ill be researching on learning how to provide feedback developers can use to make any neccasry changes. Do you know of any such threads/posts I can read up on in this regard?
Click to expand...
Click to collapse
which app is misbehaving? Basically if you have a problem the easiest solution is to pull a catlog that will detail what your phone was doing and show the error. You can do this through ADB or a free program from playstore is called Catlog.

Circaflex said:
which app is misbehaving? Basically if you have a problem the easiest solution is to pull a catlog that will detail what your phone was doing and show the error. You can do this through ADB or a free program from playstore is called Catlog.
Click to expand...
Click to collapse
It was the manual camera app. So I think i figure out how to view and store catlogs. Going to post my question about it over in dev Q&A.

[Guide] How to Unlock and Magisk Root on Stock OOS 9.0.7 (For Beginners)

NOTE: Since I am a semi-amateur at unlocking/rooting, this is not independent development. Instead, I noticed these forums don't seem to have a single one-stop guide that lays out the process for safely rooting the latest (9.0.7) Oxygen OS 9.0.7. This process may seem obvious to experts, but for people who are rusty or new to this, I wanted a process that didn't require lots of extra cross-referencing and research. I hope this is ok.
Big thanks to Dameon87 who supplied the patched boot rom, and deserves all the credit for the actual hard work with the patched boot image.
STEP 1: PREPARATION
Check that your phone is on 9.0.7.
On PC: Download patched_boot-9.0.7.img and MagiskManager-v6.0.1.apk from Dameon87's thread ( https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498 ) . Download ADB Tools if you don't have them ( https://developer.android.com/studio/releases/platform-tools#download ) and extract to a folder. Copy patched_boot-9.0.7.img to your PC’s ADB root directory (the directory with fastboot.exe and adb.exe).
On phone: Boot into OOS. Navigate to Setup->About Phone. Tap Build Number until you turn on Developer Options.
On phone: Navigate to System->Developer Options. Enable OEM Unlocking and USB Debugging.
STEP 2: UNLOCKING
Connect your phone to your PC. Click ok on the OEM Debugging prompt on your phone.
On PC: Open a command prompt [Windows: Start->type "cmd.exe"], and navigate to the ADB tools directory. Run this command in the command prompt:
Code:
adb reboot bootloader
The phone should reboot to the bootloader.
On PC: When phone finishes rebooting to the bootloader, run this command in the command prompt:
Code:
fastboot oem unlock
IMPORTANT: ALL DATA WILL BE ERASED WHEN YOU DO THIS, INCLUDING ANY PERSONAL DATA, TEXTS, PHOTOS, MUSIC, ETC. If the phone has been used, please move your files off your device first! The phone will take some time to factory reset.
On Phone: Repeat Preparation Steps 3-4 to turn back on OEM Debugging in OOS.
STEP 3: INSTALLING MAGISK
On PC: Copy MagiskManager-v6.0.1.apk to the phone.
On PC: In the command prompt window, run this command (note this .img file should be in the adb.exe and fastboot.exe directory):
Code:
fastboot boot patched_boot-9.0.7.img
Phone will reboot.
On Phone: Use a file manager app to install MagiskManager-v6.0.1.apk (I use Astro or ES, but admittedly there are probably better ones out there).
On Phone: Open the Magisk Manager App, agree to the setup popup, and click install. When prompted, choose Direct Install.
On Phone: Reboot.
On Phone: In the OS, open Magisk Manager again and add MagiskHide exceptions.
This enabled all apps that I typically need SafetyNet for, including Pokemon Go, Netflix and Google Pay, as well as of course all root apps like TItanium Backup.
Again, apologies if this seems basic, but I hope this is useful for some who don't know all of the inner workings of android unlocking and rooting by heart. If you have any improvements, feel free to suggest them.

You need to change adb oem unlock to fastboot oem unlock. Otherwise good job!

Dameon87 said:
You need to change adb oem unlock to fastboot oem unlock. Otherwise good job!
Click to expand...
Click to collapse
Ah, thanks! Fixed.

Does OTA update lock bootloader?

BesoC said:
Does OTA update lock bootloader?
Click to expand...
Click to collapse
No it doesn't, the root will be lost though.

geminium said:
No it doesn't, the root will be lost though.
Click to expand...
Click to collapse
I'm also a semi amateur at unlocking/rooting so I'm the target audience of the OP.
Ready to get my hands dirty and try it out. Last time I rooted it was on my old phone before Magisk was a thing.
I ended up not updating out of laziness.
Does magisk make OTA updates / keeping the phone up to date easier?
What's the best method for doing so if you want to keep your phone rooted?

spudsrus said:
I'm also a semi amateur at unlocking/rooting so I'm the target audience of the OP.
Ready to get my hands dirty and try it out. Last time I rooted it was on my old phone before Magisk was a thing.
I ended up not updating out of laziness.
Does magisk make OTA updates / keeping the phone up to date easier?
What's the best method for doing so if you want to keep your phone rooted?
Click to expand...
Click to collapse
Well there's quite detailed procedure explained on the forum. You'll find easily...
In general, you have to restore images in magisk, then install OOS OTA update, then install magisk to inactive slot... It's one of the easiest steps for keeping root and be up to date .

I've been rooting for almost a decade and I am grateful for this. I don't know why some of these devs always assume you know when their talking about using a PC or running shell commands. Lol. Everyone started as a noob.
Sent from my OnePlus6TSingle using XDA Labs

ScaryBugThing said:
NOTE: Since I am a semi-amateur at unlocking/rooting, this is not independent development. Instead, I noticed these forums don't seem to have a single one-stop guide that lays out the process for safely rooting the latest (9.0.7) Oxygen OS 9.0.7. This process may seem obvious to experts, but for people who are rusty or new to this, I wanted a process that didn't require lots of extra cross-referencing and research. I hope this is ok.
Big thanks to Dameon87 who supplied the patched boot rom, and deserves all the credit for the actual hard work with the patched boot image.
STEP 1: PREPARATION
Check that your phone is on 9.0.7.
On PC: Download patched_boot-9.0.7.img and MagiskManager-v6.0.1.apk from Dameon87's thread ( https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498 ) . Download ADB Tools if you don't have them ( https://developer.android.com/studio/releases/platform-tools#download ) and extract to a folder. Copy patched_boot-9.0.7.img to your PC’s ADB root directory (the directory with fastboot.exe and adb.exe).
On phone: Boot into OOS. Navigate to Setup->About Phone. Tap Build Number until you turn on Developer Options.
On phone: Navigate to System->Developer Options. Enable OEM Unlocking and USB Debugging.
STEP 2: UNLOCKING
Connect your phone to your PC. Click ok on the OEM Debugging prompt on your phone.
On PC: Open a command prompt [Windows: Start->type "cmd.exe"], and navigate to the ADB tools directory. Run this command in the command prompt:
Code:
adb reboot bootloader
The phone should reboot to the bootloader.
On PC: When phone finishes rebooting to the bootloader, run this command in the command prompt:
Code:
fastboot oem unlock
IMPORTANT: ALL DATA WILL BE ERASED WHEN YOU DO THIS, INCLUDING ANY PERSONAL DATA, TEXTS, PHOTOS, MUSIC, ETC. If the phone has been used, please move your files off your device first! The phone will take some time to factory reset.
On Phone: Repeat Preparation Steps 3-4 to turn back on OEM Debugging in OOS.
STEP 3: INSTALLING MAGISK
On PC: Copy MagiskManager-v6.0.1.apk to the phone.
On PC: In the command prompt window, run this command (note this .img file should be in the adb.exe and fastboot.exe directory):
Code:
fastboot boot patched_boot-9.0.7.img
Phone will reboot.
On Phone: Use a file manager app to install MagiskManager-v6.0.1.apk (I use Astro or ES, but admittedly there are probably better ones out there).
On Phone: Open the Magisk Manager App, agree to the setup popup, and click install. When prompted, choose Direct Install.
On Phone: Reboot.
On Phone: In the OS, open Magisk Manager again and add MagiskHide exceptions.
This enabled all apps that I typically need SafetyNet for, including Pokemon Go, Netflix and Google Pay, as well as of course all root apps like TItanium Backup.
Again, apologies if this seems basic, but I hope this is useful for some who don't know all of the inner workings of android unlocking and rooting by heart. If you have any improvements, feel free to suggest them.
Click to expand...
Click to collapse
Can you elaborate a bit more on how you got Pokemon Go working.
OS. 9.0.2 Magisk v18. Successfully rooted.
I'm selecting Pokemon Go under Magisk hide. But it still detects it. PoKe will sometimes run for about 30 secs then it gives me the error incompatible os.
Sent from my [device_name] using XDA-Developers Legacy app

Ok I'm new to this as well..I'm trying to understand the patched boot img part...so do u need the patched boot img for whichever oos ur currently running so to install magisk cleanly is that it...also I can't find the tutorial on how to install the ota's after ur rooted to where everything doesn't get erased etc..I need sumone to point me in the right area to look..I found a lil bit on it once but now I can't seem to find it..thx to everyone in this great community for all the time and effort all put into this. It's so easy to overlook all the hard work that gets done behind the scenes..so I just thank u personally for what u do for us...