Database Users

How To: Unlock bootloader and Root using a Mac

This process is very similar to how its done on Windows but I thought I would go ahead and post it here for those who have never rooted or used terminal before. I know the first time I rooted an Android device I was very happy to have a Mac specific guide to follow . Many of you may think this is simplified too much but, like I said, I created this with first time rooters in mind. If a Mod would like to sticky it thats fine. Also, I've tried to be very careful and thorough with the instructions, but if anyone notices a problem please let me know.
As always, I am not responsible if something goes wrong and your device gets bricked. I will try to be as specific as possible and this process worked for me. Also, I don't claim to have the knowledge to fix any problems you may encounter along the way. There are a lot of very talented people here who have extensive knowledge of Android, but I am not one of them. I can unlock my bootloader and root my device but that's about it. So if you do encounter a problem I will try to help but there is no guarantee I can fix the issue (in fact the odds are that I can't fix the issue). Proceed with caution!
Important: Unlocking your bootloader will wipe your device! Please backup anything that is important (pics, vids, documents, etc)!
This guide only applies to the 2013 Nexus 7
A. Prep
1. Charge the Nexus 7 to at least 80% so it doesn't turn off during the process
2. Unlock developer options by navigating to -- settings > about tablet -- and then click the build number 7 times
3. Enable USB Debugging by navigating to -- settings > developer options -- and select the USB Debugging box
4. Download the Android SDK for Mac here and unzip it once it has downloaded. DO NOT use the link posted below for the sdk. It does not contain fastboot and you will not be able to complete the rooting process. Please use the full sdk from Google that I have linked here. EDIT: Google has changed the download for the SDK. Please see posts 73-75 on page 8 for instructions regarding how to get everything you will need for the SDK.
5. Download the latest TWRP for your device here and place it in the platform-tools folder of the SDK. Make sure the TWRP file you download is for the 2013 Nexus 7...not the 2012 version. To find the platform-tools folder -- open the adt-bundle-mac folder you downloaded and unzipped > sdk > platform-tools -- place the TWRP file here. Other files in the platform-tools folder should include adb, api, fastboot, notice.txt, and a few others.
B. Unlock the Bootloader - Warning--This will wipe your device! Backup anything important!
1. With your device powered on, plug it into your Mac
2. Open up terminal and navigate to the platform-tools folder which has the adb, fastboot, and TWRP files. An easy way to do this is to type "cd" (without the quotes) into terminal, add a single space, and then drag and drop the platform-tools folder onto terminal and then press enter.
3. Type this command into terminal: ./adb reboot bootloader
4. If you correctly navigated to the platform-tools folder, you should get an error message saying the device is unauthorized. Go to the Nexus 7 and there should be a dialogue box asking you to authorize the computer. Authorize the computer.
5. Re-type the command: ./adb reboot bootloader
6. Your device should now boot into fastboot mode. On your N7, the word "start" will be at the top in green and you can also see a lot of your device information on this screen
7. Type into terminal: ./fastboot oem unlock
8. Your Nexus 7 will now display a message about unlocking your device. Use the volume button to select the option to unlock the device and then press the power button to confirm the choice.
9. Your device will return to the fastboot mode screen and you can now see in the device information section near the bottom that the device is unlocked. While on this screen, press the power button to select the green "start", which will reboot your device. You must restart your device here or you will run into a softbrick issue during the root process!
10. Congrats! Your device is now unlocked. If you want to root proceed to the next section.
C. Rooting
1. Once your device has rebooted from the unlocking process, everything will have been wiped and reset. You will have to go back and unlock developer options again and you will also have to enable USB debugging again, which can be found part A. Prep of this guide.
2. Download the current version of SuperSU to your Nexus 7. It will go to the download folder on your N7. It can be found here. (Note: The version of SuperSU I have linked to is 1.93, but it gets updated from time to time. You might want to look around and see if a more current version is available. The thread for SuperSU can be found here.)
3. Turn your N7 off and then boot into fastboot mode by pressing the Volume Down button while also pressing the Power Button to turn the device on. If done correctly you should see the green "start" again at the top and the device information near the bottom.
4. Plug the N7 into the computer and make sure terminal is still directed to your platform-tools folder. For instructions on how to navigate to the platform-tools folder see part B. Unlock the bootloader.
5. Type the following into terminal: ./fastboot flash recovery nameofTWRPrecovery.img
5a. For the nameofTWRPrecovery.img part above, you must type the exact file name of whatever TWRP (or other) recovery you've decided to use. This is the same file that you downloaded and placed in the platform-tools folder in Part A. Step 5. above. For me the file name I had to type was openrecovery-twrp-2.6.0.0-flo.img and the total command looked like this: ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
6. In terminal you should see the process taking place and it will tell you when its finished and how long it took (less than a second).
7. Now, while still in fastboot mode, use the volume button to navigate to Recovery and press the power button.
8. The N7 will boot into TWRP which we just installed.
9. Using the touch screen, select install and then navigate to the download folder where you saved the SuperSU file
10. Select the SuperSU file using the touchscreen and then swipe to flash it. You will see the rooting process occur on the screen.
11. Congrats! You are now rooted. Select Reboot System and you are done!

Your instructions couldn't be any simpler. I am unlocked and rooted now. This is my first Android device. Thank you very much.

Glad it was helpful for you!

Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Very nice guide! Well done
Sent from my Nexus 7 2013 using xda app-developers App

redhat_123 said:
Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .

geckocavemen said:
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .
Click to expand...
Click to collapse
Thanks a lot. This is the first time I used MAC to unlock and root a device and it was very quick. Appreciate your effort in putting up the detailed steps.

I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999

wad3g said:
I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999
Click to expand...
Click to collapse
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
EDITED TO ADD: Please only use the link in the how-to for the full sdk from Google. wad3g's link only has adb but not fastboot. To complete the rooting process you will need fastboot also.

geckocavemen said:
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
Click to expand...
Click to collapse
Yes, it is from the same link as above on Google's developer site. They hadn't updated the SDK yet, so each time I downloaded ADB v1.0.29 - ADB for 4.2. I was finally able to find ADB & Fastboot v1.0.31 for Android 4.3. Also, just so you know, the .zip on my thread is not the full SDK. If you're not a developer you don't need the full SDK, so for most the rooter's here my zip will be all that is needed.
You may just want to mention checking what version of ADB you're running prior to start or if you're having any issues. If you're running an older version than 1.0.31 you need to update.
{
"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"
}
Hope this helps! Let me know if you have any other questions.

Thanks wad3g. But just to clarify, Google updated the Mac version of the sdk on the 29th of July so the link in the original how-to will work for any version of Android. It's the same thing I used to download the sdk and I'm running version 1.0.31. Also, as mentioned it does contain more than is strictly necessary for unlocking and rooting. However, the original link in the how-to will provide you with the most up-to-date version of the Mac sdk that Google has released, should they update it in the future.

Please Help!!!
Hi I followed all your instructions and right when i was ready and tried to flash the recovery, I get this list of options after waiting for device:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
I don't understand what I should pick or if I should pick any. Please help as soon as possible.
EDIT: The reason I got this list is because I dragged in the fastboot into the terminal because when I tried to enter ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img, it said this: -bash: fastboot: command not found

Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.

Hope that last edit of mine helped out. Just follow the how-to step by step (including my links) and you'll be ok.

Thanks So Much But One Last Question
geckocavemen said:
Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.
Click to expand...
Click to collapse
Again in a bit of a sticky pickle. I got it to work because my problem was that I didn't direct the terminal to the folder. Now I am booted into TWRP but I don't understand what you mean by the SuperSu file. I it just the whole folder titled UPDATE-SUPERSU-v1.51?
EDIT: OMG IT WORKED!!! Thanks so much I got it rooted and it works awesome now!!!

Best tutorial for mac ever
I found this so helpful and easy! My nexus 7 is rooted now!:good:

:good::good::good::good:
thanks a lot

Thanks for the guide.

Want to say thanks for your very detailed explanations.
If I may, I would like to suggest one more step after the final step. Make a Nandroid backup. That really helps a lot for people who screwed stuff up.

Yes, creating a nandroid backup is very important and can definitely save you when flashing Roms and stuff if something goes wrong. Creating a nandroid before rooting could get you back to stock with an unlocked botloader too. But I guess that isn't as important now that Google has released the factory images.
Sent from my Nexus 7 using xda app-developers app

[GUIDE] Lenovo Yoga Tab 3 8 / YT3-850F - How to unlock and root

Hello there!
After searching the internet up and down for a guide how to root this device and having found nothing, i decided to do it by myself - with success.
Here i want to share my way of unlocking this device for others:
Warning: Backup all your data first, as the unlocking of the device will reset it to factory defaults!
This is a guide for people who are aware of the risks of flashing, it lies completely in your own responsibility!
Before doing anything at all, read this post carefuly!
Requirements:
Lenovo Yoga Tab 3 8 / YT3-850F (obviously)
Having ADB and fastboot installed.
Getting a proper twrp version & Chainfires SuperSU
Links:
15 seconds ADB Installer v1.4.3: https://forum.xda-developers.com/showthread.php?t=2588979
Fitting twrp: http://www.htcmania.com/showthread.php?t=1291696
The thread's in spanish, i used google translate.
Chainfires SuperSU: https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
This one worked for me, first i flashed an older version and got stuck within a bootloop. Reflashing this newer version and wiping all caches within twrp helped.
Step by step:
1. First you want to unlock the "developer options" in your settings.
To do this go into settings -> about this device and tap on "BuildNumber" 7 times.
After two taps, a small pop up notification should appear saying "you are now X steps away from being a developer" with a number that counts down with every additional tap.
unlocked developer options.
2. Now you can go into the developer options and activate both "USB debugging" and "OEM Unlock".
Both are needed for beeing able to flash anything onto your device in the first place.
3. Install Lenovos USB drivers & the 15 seconds ADB Installer v1.4.3
4. Boot your device into Recovery Mode. To do this, turn it on while holding both the On-Button as well as Volume-Up.
Inside the Recovery console select "boot into bootloader" with the volume keys and confirm with the on button.
See: https://forum.xda-developers.com/wiki/Lenovo_Yoga_Tab_3_-_8"-_YT3-850F
5. Connect your Tablet to your PC via USB.
Now open a console prompt on your PC and Type "fastboot oem unlock" (without the quotes of course).
This should unlock the bootloader for flashing.
6. Flash the twrp image supplied in the links section.
For Android 6 extract the "TWRP 3.0.2.7 (a)" folder from the downloaded archive, for Android 5 the "TWRP 2.8.7.7" folder.
Inside this folder, there should be a folder called "img", enter it.
Inside the img folder open a new console by “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” from the context menu.
Now type "fastboot twrp.img", this should install twrp onto your device.
Now type "fastboot reboot" to reboot your device.
See: http://rootmygalaxy.net/install-twrp-recovery-via-fastboot/
Note: I have done this step on Android 6, so noe guarantee for Android 5.
7. You can enter twrp the same way now like the original recovery menu.
It will boot up in russian language, but you can change it to english or some other choices:
{
"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"
}
8. It is advisable that you do a backup of your system files now with twrp, in case something goes wrong with SuperSU.
9. Copy the zip of Chainfires SuperSU onto your Device.
Within twrp you can now install SuperSU, which will root your device.
10. Done! Enjoy your newly rootet device!
Final words: To the moderators: Feel free to edit this thread for better understandability.

Hi, would you know if this method also works for model Lenovo Yoga Tab 3 10.1 / YT3-X50F? Thanks in advance.

ale_aas said:
Hi, would you know if this method also works for model Lenovo Yoga Tab 3 10.1 / YT3-X50F? Thanks in advance.
Click to expand...
Click to collapse
I have the same model, did it work for you?

fede01_8 said:
I have the same model, did it work for you?
Click to expand...
Click to collapse
Hi, please, feel free to follow the steps in this post: https://forum.xda-developers.com/th...e-yoga-tab-3-10-1-yt3-x50f-twrp-root-t3695297
I just uploaded it, and work fine for me.

Thanks so much!
Thanks So much, yYour guide worked successfully, but I was not very clear how to install the TWRP recovery, so I had to install it manually using the guide on this page:
http://www.techmoviles.com/instalar-twrp-recovery-en-depositivos-android-mediante-fastboot/
In this guide is more detailed, it can serve any other also
regards! very thankful.
PD: My YogaTab3 is of model YT3-850F, in case someone has doubts
drwakey said:
Hello there!
After searching the internet up and down for a guide how to root this device and having found nothing, i decided to do it by myself - with success.
Here i want to share my way of unlocking this device for others:
Warning: Backup all your data first, as the unlocking of the device will reset it to factory defaults!
This is a guide for people who are aware of the risks of flashing, it lies completely in your own responsibility!
Before doing anything at all, read this post carefuly!
Requirements:
Lenovo Yoga Tab 3 8 / YT3-850F (obviously)
Having ADB and fastboot installed.
Getting a proper twrp version & Chainfires SuperSU
Links:
15 seconds ADB Installer v1.4.3: https://forum.xda-developers.com/showthread.php?t=2588979
Fitting twrp: http://www.htcmania.com/showthread.php?t=1291696
The thread's in spanish, i used google translate.
Chainfires SuperSU: https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
This one worked for me, first i flashed an older version and got stuck within a bootloop. Reflashing this newer version and wiping all caches within twrp helped.
Step by step:
1. First you want to unlock the "developer options" in your settings.
To do this go into settings -> about this device and tap on "BuildNumber" 7 times.
After two taps, a small pop up notification should appear saying "you are now X steps away from being a developer" with a number that counts down with every additional tap.
unlocked developer options.
2. Now you can go into the developer options and activate both "USB debugging" and "OEM Unlock".
Both are needed for beeing able to flash anything onto your device in the first place.
3. Install Lenovos USB drivers & the 15 seconds ADB Installer v1.4.3
4. Boot your device into Recovery Mode. To do this, turn it on while holding both the On-Button as well as Volume-Up.
Inside the Recovery console select "boot into bootloader" with the volume keys and confirm with the on button.
See: https://forum.xda-developers.com/wiki/Lenovo_Yoga_Tab_3_-_8"-_YT3-850F
5. Connect your Tablet to your PC via USB.
Now open a console prompt on your PC and Type "fastboot oem unlock" (without the quotes of course).
This should unlock the bootloader for flashing.
6. Flash the twrp image supplied in the links section.
For Android 6 extract the "TWRP 3.0.2.7 (a)" folder from the downloaded archive, for Android 5 the "TWRP 2.8.7.7" folder.
Inside this folder, there should be a folder called "img", enter it.
Inside the img folder open a new console by “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” from the context menu.
Now type "fastboot twrp.img", this should install twrp onto your device.
Now type "fastboot reboot" to reboot your device.
See: http://rootmygalaxy.net/install-twrp-recovery-via-fastboot/
Note: I have done this step on Android 6, so noe guarantee for Android 5.
7. You can enter twrp the same way now like the original recovery menu.
It will boot up in russian language, but you can change it to english or some other choices:
8. It is advisable that you do a backup of your system files now with twrp, in case something goes wrong with SuperSU.
9. Copy the zip of Chainfires SuperSU onto your Device.
Within twrp you can now install SuperSU, which will root your device.
10. Done! Enjoy your newly rootet device!
Final words: To the moderators: Feel free to edit this thread for better understandability.
Click to expand...
Click to collapse

what about yt3-850m, anyone tried this on it?

thank you for this guide, but before we delve in, is there any custom rom we could flash?
my device is at 6.0.1 from telco, so unless there are nougat/oreo/pie roms out there, having a rooted device has little benefit?

ewong3 said:
thank you for this guide, but before we delve in, is there any custom rom we could flash?
my device is at 6.0.1 from telco, so unless there are nougat/oreo/pie roms out there, having a rooted device has little benefit?
Click to expand...
Click to collapse
It would facilitate the installation of Magisk though which in many ways is better than custom rom installation :good:

I did this same thing, but replaced supersu with magisk. Similar process, but rather than flashing supersu from twrp, just download magisk.apk from github, rename to magisk.zip, and flash with twrp.
Upon reboot I still had to install the magisk apk manually, as the magisk app didn't show up. Once installed, I had to go through one more step in the magisk app to reflash it properly, using the direct install method.
Instructions to install twrp (google translated from the thread linked above):
Original post (Translated)​
A month ago I bought this tablet and these are the things I did to it and that can help you
Before that, thanks to:
lenovo-forums.ru - Where I got everything from
SevenMaxs - User of that forum, who made the TWRP
baikal0912 and Steaven - From that forum too, for posting the Roms for the tablet (5.1 and 6.0 respectively)
Note 1 from OP: If you already updated to the latest version without touching anything, you only need to do the first 2 points (if you want to)
Note 2: In case you have touched and cannot update, continue from the point that you have not done (bootloader, twrp or update)
1. Unlock Bootloader​
Activate developer options
For this you have to go to "Settings -> About the tablet". Once here, you have to touch several times on "Compilation number", until it says "You are already a programmer"
Enable debugging and unlock permissions
Go to "Developer Options" and check the boxes for "OEM Unlocking" and "USB debugging"
Connect tablet to your computer
Download file and unzip it
01. Bootloader
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Run Unlock_Bootloader.bat
Note from Gramdalf: I was on linux, but was still able to do this - just look at the `.bat` file and enter the fastboot/adb commands as they are.
Review the tablet, as a code will appear and ask for permission to activate debugging, select 'Remember this computer's RSA key'
2. Install TWRP​
Connect tablet to PC
download file
02. TWRP
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Install
-If it comes with Android 5 from the factory, apply TWRP 2.8.7.7.
-If it comes with Android 6, install TWRP 3.0.2.7 (a)
You only have to open the .bat that is in each folder.
Note from Gramdalf: Same thing, just enter the commands as they are in the .bat script, making sure that you are in the correct directory. The only difference with this is that with the `tools\fastboot -i 0x17ef flash recovery img\twrp.img` command, `-i` wasn't an available option - I was able to run it just fine without it. The recovery flashed correctly, but just keep in mind that I'm not sure if there are any lasting side effects that I am unaware of.
-If you have Android 5 and then update to Android 6, you have to install TWRP 2.8.7.7 and then you can flash 3.0.2.7 which is in the "TWRP 3.0.2.7 (b)" folder from the same TWRP (it's a zip )
Note from OP: TWRP says 850M, but it is compatible with it. There is a version from someone on XDA who tweaked a few things for the 850F, but I haven't tested it.
Note from Gramdalf: I didn't do the following part in my case, but it's there just in case you want it
3. Firmware​
Android 5.1
YT3-850F_USR_S000025_1510160911_Q1241_ROW_factory_update
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Android 6
YT3-850F_000109_161226_ROW_otafull
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Just go into TWRP and flash.
Note from OP: When upgrading from 5 to 6, the bootloader is locked again and TWRP is removed, you need to do step 1 and 2 again.
Root and Xposed
Enter TWRP
Flash SuperSU
Restart
Check that it is rooted
Enter TWRP
Flash Xposed
Restart
Install the Xposed APK
Verify that it has been installed correctly
04. Programas
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

[Guide] Tired of EMUI ? Here's a full guide on how to install a Treble Rom

So I was tired of EMUI, the UI design isn't really that bad but it really clashed with Android's Material Design, so since our Mate 9 is Treble compatible, I decided to try a few Treble ROMs. After many fails and factory resets, I finally settled on Havoc-OS. Here I made a guide on how to switch to a Treble Rom.
So a few things to note :
There's no (fully) compatible TWRP recovery for Kirin devices. Either they work but cannot flash OpenGApps or they simply don't work with Treble ROMs.
Huawei's eRecovery seems to work. For me at least, it didn't work before. So as usual, BACKUP ALL OF YOUR DATA(Titanium Backup or HiSuite for apps if needed). You can also use TWRP with stock EMUI if you want to backup your partitions in case something goes really bad.
Make sure you're using stock kernel, ramdisk and recovery_ramdisk before starting anything.
A Micro SD card is optional but useful for restoring things or if you don't want to transfer all of your backup data to your PC
USB Debugging isn't really needed.
-------------------Requirements-------------------
- Your phone, obviously. Has to be a Mate 9 (Pro) updated to Android 8.0 Oreo.
- An unlocked bootloader (Since Huawei stopped giving unlock codes, I can't help you on that one. Sorry boys)
- A PC and a USB Type-C cable.
-------------------A. First things first-------------------
Enable OEM Unlocking
An easy thing to do, otherwise you won't be able to flash anything on your phone (FRP will be "Lock" on bootloader screen). You may think that this is kind of a mandatory thing to do since you've unlocked your bootloader, but you can get it back to disabled and greyed out anytime, so here's a reminder.
1. Enable developer options by going to Settings > System > About Phone and taping multiple times on Build Number
{
"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"
}
2. Once that's done, go to Developer Options and enable OEM Unlocking.
-------------------B. Downloads-------------------
1. Download and install Minimal ADB
Click here to download Minimal ADB
2. Download your ROM, right now there are two fully compatible ROMs :
- OpenKirin Builds : https://openkirin.net/download/
- Havoc-OS : https://forum.xda-developers.com/mate-9/development/rom-havoc-os-t3826470
You'll get an img file that you must put inside where you installed Minimal ADB.
3a. For later : Download Huawei Firmware Finder and Huawei Update Extractor
- Huawei Firmware Finder
- Huawei Update Extractor > If you're not running Windows (Mac, Linux) (Thanks to irony_delerium)
- Also download Magisk Manager (This is an APK)
--- OR ---
3b. Download this patched Ramdisk with Magisk included so that you don't have to download all of the above. CREATED WITH BUILD NUMBER MHA-L29 8.0.0.370(C432). USE AT YOUR OWN RISK IF IT DOESN'T EXACTLY MATCH YOUR PHONE BUILD.
Here (name is patched_boot.img)
-------------------C. Installation-------------------
Now that you've got your Rom img and Minimal ADB, we can start installing it.
1. Turn off your phone.
2. Plug your phone into your PC AND hold down the volume down button until you get a (terrible) white screen saying you're in fastboot&rescue mode.
3a. Open a command prompt (with admin rights if possible) on your PC and get to your Minimal ADB directory. By default, it should look like this :
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
3b. If you installed Minimal ADB on a different drive, then type this :
Code:
cd /d {DRIVELETTER}:/{MINIMAL ADB DIRECTORY/}
4. Make sure your phone is detected by typing :
Code:
fastboot devices
This should show up.
5. Now you can start flashing your ROM by typing :
Code:
fastboot flash system {IMGFILE}.img
Your ROM should start flashing with the message 'target reported max download size of 494927872 bytes'
It should take a minute.
Once you see 'finished. total time: times', that means your ROM has been flashed.
Don't reboot just yet. Things won't work
6. Reboot to recovery by turning off your phone (hold down power button for ~5 seconds) and holding volume up.
7. Now that you are in EMUI recovery, do the following :
- Wipe cache
- Wipe data/factory reset
You MUSTdo this otherwise you will have multiple issues.
8. You're done for the installation. Now reboot to system and start your phone first config (again).
-------------------D. Root-------------------
Your Treble Rom isn't rooted by default. But the Treble Rom itself triggers the SafetyNet flag, which means even if your phone is super clean, it is not certified. So it is obviously completely optional, by it is extremely recommended to install Magisk.
If you downloaded the patched_boot.img file in the attachment
The install process will be extremely easy. It will install Magisk 16.7 (only Beta works with Treble right now). So all you have to do is :
Get to fastboot mode by turning off your phone, plugging it to your PC while holding volume down button. Then, type the following command in the same command prompt window :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and download Magisk Manager. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
If you're not using the attachment
1. Check your phone Android version and build number. It is in Settings > About phone. Write it down, you'll need it.
2. (Install and) Open Huawei Firmware Finder. Get in the 'Common Base' tab and type in your phone build number.
3. Find the matching build number in the list. Make sure its type is 'FullOTA-MF' and its size is 2Go+. Then click on the blue link in the 'Filelist' column. Copy paste the first (ending with 'update.zip') in your browser to download the zip file. It should take some time.
4. Once it's downloaded, open it with 7Zip/WinRar and extract the file named 'UPDATE.APP'.
5. Open Huawei Update Extractor, go to the Settings tab and untick everything.
6. Now, go to the Extract tab and click on the dots on the right and select your extracted 'UPDATE.APP'. A ton of files should appear.
7. Right click on 'RAMDISK', and 'Extract selected'. Put it somewhere on your PC, you'll need it.
8. Plug your phone on your computer and put your RAMDISK.IMG in a folder on your phone.
9. On your phone, download and install Magisk Manager. If it prompts you to do so, do not install it. Then go to Settings tab and change 'Update Channel' to 'Beta'.
10. Now go back and tap 'Install', then choose 'Patch Boot Image File' and select your RAMDISK.IMG that you transferred to your phone. Then let Magisk do its thing.
11. Once it's done, on your PC, go to Your Phone/Internal Store/MagiskManager, and transfer the file 'patched_boot.img' to your Minimal ADB folder.
12. Turn off your phone and get to fastboot mode. You know how to do it now, don't you ?
13. In the same command prompt on your PC, type :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and BAM, you're rooted. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
-------------------E. SafetyNet-------------------
Magisk may be installed, but with a Treble Rom, SafetyNet should trigger anyway. So you'll have to do a few things.
1. In Magisk Manager, go to the Downloads tab and search for 'MagiskHide Props Config'. Install it, then reboot your phone.
2a. Once your phone is rebooted, download Terminal Emulator on the Play Store
--- OR ---
2b. Go to developer options and enable 'Local Terminal'.
3. Open your terminal, then type :
Code:
su
(Accept root request)
Code:
props
Things should appear. Woah.
4. Type 1 (Edit device fingerprint), then f, then choose a vendor and a model by typing the right number, then press y. Don't reboot yet (press n)
5. Type 6 (Script settings), then 1, then y. Now you can reboot (press y). Once it's done, make sure that 'boot stage' is 'currently post-fs-data'. Otherwise SafetyNet will still trigger.
THERE YOU GO ! Your phone should pass SafetyNet. You can check this by trying to search for the Netflix app on the Play Store or going into the Play Store settings and making sure your device is Certified'.
If you have any question/bug, do ask/report all of dem to me.

I haven't rooted or done anything with this device since I've bought it coming from all Samsung devices previously. This guide is awesome! Nice work!

About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".

i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages

irony_delerium said:
About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".
Click to expand...
Click to collapse
Yup, I'm aware of the Play Store app, but IMO, having everything directly on your PC is more convenient. Also what you said is useful for people not running Windows, so kudos to you for that.

aureliomilitao said:
i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages
Click to expand...
Click to collapse
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.

Deytron said:
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.
Click to expand...
Click to collapse
i extract system.img in update.app ...and lost Brazil language

aureliomilitao said:
i extract system.img in update.app ...and lost Brazil language
Click to expand...
Click to collapse
Well... I'm sorry, but I can't help you on that one. It just doesn't make sense. You can't "lose" a language. As I said, try to use Huawei eRecovery to completely restore your phone.

Solved

[Guide]Installing Lineage

Installing Lineage​
Few quick things.
Since the 8T does not have a single unified guide like FunkWizard did for other OnePlus devices, I'm adding some things that are likely important, but don't necessarily have to do with installing LOS.
This will be similar to my 6T installing Lineage guide. However the 8T is a newer device, and new to me. Expect it to change and get updated as things change. I'll add in pictures like the 6T guide soon.
I also want to address a common question, you can use Windows for this process. I prefer Linux, and Fastboot just works in Linux without driver issues. If you have Fastboot and ADB working in Windows already feel free to use that if you want. If you use Windows, remove "sudo" from the commands (this is for Linux).
I am using a Global 8T, and have only tested these methods on such.
Make Sure OOS is Updated​1. Start fresh, and make sure OOS is up to date.
This should be self explanatory. Go to settings, and system, check for updates. Download and install any system updates OOS has to make sure you have the latest firmware on your device.
Unlock the Bootloader​2. Unlock the Bootloader
sudo fastboot flashing unlock
For this step you will need fastboot. I use Linux, and honestly I feel like it's easier and more reliable for fastboot and ADB so that's what I'm including here in these steps. It's easy to boot from a USB.
To create a bootable Linux flash drive you can use Unetbootin, which you can download for free here (Your other option would be to burn the ISO straight to a DVD and skip the unetbootin step):
https://unetbootin.github.io/
For Linux, I'm using Linux Mint Cinnamon, You can download for free here:
https://www.linuxmint.com/download.php
Then run unetbootin (yours will look a little different, I'm running it in Linux):
{
"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"
}
Point it to the Linux ISO, and tell it where an empty flash drive is. It will erase everything on the flash drive. Afterwards you can load whatever you want on the flash drive. However be aware when booting Linux from this drive you can't access what is on the drive (at least not by normal methods).
After this has successfully completed, reboot the PC, and boot from the USB drive. Your PC will boot into Linux (turning off the PC and removing the USB drive will make it boot up like normal again).
Next we need to install fastboot and adb. You need to open up the "start menu" and open the "synaptic package manager". You can find this stuff in the menus, however the easiest way to get to these items is to just start typing the name of the item. See below:
Search fastboot, click the boxes, choose install. Then search for ADB, click the boxes, choose install and then click apply. That will install most of the stuff we need, but really old versions of fastboot and adb. You must update fastboot to install LOS. Time to open up a terminal:
In the terminal run these commands to update fastboot and adb (this is downloading them directly from Google).
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot
Next you need to make sure OEM unlocking is enabled. If you haven't tapped on the build number and enabled devloper options, do this now. enabling USB debugging for the moment, would also be helpful.
Now would be a good time to back everything up. The phone will get wiped.
Place the phone in fastboot mode. You can do this using the advanced reboot menu or ADB, or the key combinations (all key combos listed below for reference):
Volume Up + Power while turning on will boot to fastboot. (<-- Don't believe this works on the 8T)
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
If you enabled USB Debugging in the terminal window, type (the phone will pop up a warning asking you to allow USB debugging, make sure you allow this):
sudo adb reboot bootloader (<-- This command will make the phone restart to the bootloader / fastboot)
Once there type the command below. Your phone will be wiped. Make sure you backed up any important information. Use the volume buttons to select unlock, and press the power button.
sudo fastboot flashing unlock
Backing up Persist / EFS​3. Backing up the persist partition and EFS backup.
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.bin
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.bin
Hopefully you never need a backup of your persist paritition or EFS backup. However if anything ever happens you'll be glad you have it. The EFS contains the IMEI, so it is unique to every device. You can do this at any point as long as you have root. The easiest way, epsecially for those not want to root their device is to use the broken TWRP. I got this TWRP and a bunch of my initial rooting information from @Mpolo87 's Guide OnePlus 8T EasyRoot. It is an excellent guide. The TWRP is in step 4. This is not the way you need to root LOS though. Download this TWRP.
Once again from the terminal:
The image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo fastboot boot recovery.img * <-- Sends that TWRP image to the phone to be booted temporarily. Only boot this, never run the command "flash".
With this TWRP loaded it is normal that the screen will be blank and just briefly flash the TWRP logo screen. All we need to do is use the terminal window on the PC. Run these commands:
sudo adb shell
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.bin
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.bin
exit
sudo adb pull /sdcard/persist.img /home/mint/Desktop
sudo adb pull /sdcard/modemst1.bin /home/mint/Desktop
sudo adb pull /sdcard/modemst2.bin /home/mint/Desktop
It is important to use ADB to pull the files off of the device after creating them. They won't be accessible after you restart. Also if you are using a live Linux distro (USB) the files do not remain on the USB after you restart / power off. So you need to place these files on another hard drive or USB. The persist.img should be ~ 32MB the Modems should be ~ 2MB each. Once you have the files you can run
sudo adb reboot bootloader
Installing Lineage​4. LOS 18.1 Thread
Quick Common questions:
Gapps are not included, you must sideload them if you want them. Personally I use NikGapps, LOS Recommends MindtheGapps.
Official LOS 8T Download Link
Download the latest build, and the recovery image from the link above.
You must have a current version of fastboot / adb to successfully install this. (Update method mentioned previously in this guide) To install Lineage it is as simple as the instructions listed on the LOS site.
From the terminal:
sudo adb reboot bootloader
sudo fastboot flash recovery lineage-18.1-20210506-recovery-kebab.img
Now reboot in recovery. Doesn't matter how you get there. You can use the volume keys to change the options in the bootloader, you can use volume down and power, etc. Once in Lineage Recovery we need to run the copy partitions zip. The link for this is on the LOS install page. However here is a direct link. In LOS recovery choose:
- Apply Update
- Apply from ADB
From the terminal on the PC
- sudo adb sideload copy-partitions-20210323_1922.zip
LOS recovery will warn you about the zip not being signed, flash this anyways. Hit the back button, choose advanced, and then reboot to recovery. It is now time to actually install LOS. In LOS Recovery:
- Factory Reset. (You did backup everything right?)
- Press Format data / factory reset.
- From the main LOS Recovery menu, Apply Update
- Apply from ADB
From the terminal on the PC
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you want to install Gapps or Magisk, you must reboot to recovery. Go to advanced and choose reboot to recovery before install anything else. If you are only installing LOS you are ready to reboot to system now.
Optional, Gapps​5. Sideloading Gapps.
For Android 11 I've been using NikGapps:
NikGapps <-- For Lineage 18.1 (Use the R Folders for Android 11. I recommend the "Core" version. I also tested Basic though if you want that level of Gapps. I strongly recommend you grab setup wizard out of the R Addons Folder, I used the regular setup wizard, not the pixel one.)
Remember you need to reboot to recovery once after installing LOS (as mentioned above). This does not mean you need to let LOS boot, just reboot to recovery, so that it switches slots.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- Remember between each zip file you must again hit apply from ADB.
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
LOS recovery will warn you about the zip not being signed, flash this anyways.
If you get a warning about them not being signed, choose flash anyways. If you are going to flash Magisk, move to the next section. If you don't need Magisk, reboot to system.
Very Optional, Magisk​5. Sideloading Magisk.
All the devices I've tested with Android 11 have worked fine since Magisk 21.2. At this point I don't see a reason to still run the Canary builds unless you want to for some reason.
Download Magisk: [urlhttps://github.com/topjohnwu/Magisk/releases]Magisk GitHub Link[/url]
This will be flashed in LOS recovery. To get to recovery you can use the ADB (if you enable USB debugging), key combination, or the advanced restart menu, doesn't matter.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.
Very Optional, Passing Safety Net​6. Magisk Required.
These items are add-ons are flashed in Magisk after the first boot (Don't flash these in TWRP anymore):
MagiskHide Props Config
Busybox
To flash modules in Magisk press the puzzle piece icon. Then choose install from storage. Now just choose your addons. After flashing the icons it will have a reboot icon at the bottom. You can reboot or you can press back and flash another. After you are done reboot.
You will also need a Terminal Emulator. I personally use:
Terminal Emulator for Android
Once all these are installed the first step is setup Magisk. Under Magisk go to settings:
In version 20.4+ Magisk Hide is no longer on by default. So make sure the Magisk Hide, Hide Magisk from various forms of detection switch is flipped. Then press Hide Magisk Manager. This will bring up a box for you to choose a random name for the Magisk Manager, type whatever you want here. You can leave it Manager if you wish, but I typically change this.
Now open Magisk again. It will ask you to download it again, click ok, then manually open the app again as it says. Now we need to open Magisk hide. This is now under the shield icon, then click the arrow at the top:
These are the apps you don't want to know that you have root. Less is better. You can cause instability problems by just choosing everything. My general rule of thumb is, Google, steaming video, music, and payment apps get selected. In my experience if I come across an app that needs it and I didn't select it, I just clear cache and/or data and re-open the app and it works. There are some big multiplayer apps that ban hardware / people, so do your research (don't ask me, I don't play those games).
Next time to change the device fingerprint using MagiskHide Props Config Module. We do this using the terminal emulator. In the terminal emulator, type "su" to gain root privileges. Then type props to run the module:
Now it's just following the menus. Choose option 1 - Edit device finger print. (type 1, hit enter)
After this you will see a menu of devices. It doesn't matter what device you pick really. If you want apps / Google to think you have a OPPO or Samsung pick one of those Fingerprints. However there's a bit more to passing Safety-net than that. Since Google has changed how things work not all those fingerprints that used to work will work now. Also now you may get an error when you turn on the phone because of the security dates. My 8T passes saftey net, just choosing the 8T and Android 11 fingerprint. Also keep in mind some fingerprints will require Force basic key attestation to pass.
After choosing the fingerprint you want, it will ask you if you want to reboot. Choose yes. After rebooting, you may need to clear the cache from the play store for some apps to appear in it. You should now pass safety net. Check this in Magisk:
Very Optional, Ad Blocking​7. Root required.
You can block many things with a hosts file, most popular would be ads. I've been use StevenBlack's host file which is a compilation of several hosts files. This is located on Github:
https://github.com/StevenBlack/hosts (Scroll down you'll see the options of what you can block)
Direct link to the hosts file I use. This will block Adware / Malware.
First we have to make the hosts file. The hosts file must use Unix / Linux line endings. If you are using Linux, don't worry about this, just create the file. If you are using Windows, the easiest thing to do is use Notepad++ (Free).
Notepad++ Downloads
Next one other caveat. The hosts file is quite large. I've never had much luck copy and pasting it from any other browser than Firefox (Windows or Linux), but however you get it into Notepad++ is not a big deal.
Once in you have the hosts file into Notepad++ go to Edit, EOL Conversion, and Choose Unix (LF).
Now save the file as "hosts" no ending. This does mean under file type you will need to change it to All File types *.*. Move this hosts file to your phone.
You will need to use a root file explorer to copy this hosts file to /system/etc/ and replace the file that is there. I used Solid Explorer for this.
Updating Lineage​
Updating Lineage is pretty much the same as installing it, just without the reset or wipe. First reboot to Lineage recovery. Doesn't matter how you get there. You can use the advanced reboot menu, or the adb.
Couple things to remember:
You will need a PC for this.
Fastboot / ADB must be updated for this to work, otherwise you will have problems.
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you use Gapps or Magisk, you also need to sideload these. Once again you still need to reboot recovery. Hit the back button, choose advanced, and then reboot to recovery.
Apply Update -> Apply from ADB (This must be done between each zip file)
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways.
Then reboot to system. If you were using a hosts file for adblocking you will need to put that back as well when it boots. This gets replaced during the update.

Cliff Notes​
Hopefully you've backed up EFS and persist partition.
Fastboot and ADB must be current version. You will have issues if they are old.
If you are using Windows remove "sudo" from the commands. This is for Linux only.
Once you install Gapps you need to continuing installing Gapps. If you want to go without Gapps after installing them, do a clean install.
Installing Lineage​
sudo adb reboot bootloader
sudo fastboot flash recovery lineage-18.1-20210506-recovery-kebab.img
Apply Update --> Apply From ADB
- sudo adb sideload copy-partitions-20210323_1922.zip (assuming this is a new install) (you can skip wiping data if you are updating)
Reboot to Recovery (This option is in the Advanced Menu of LOS Recovery)
Choose factory reset, and format data (assuming this is a new install) (you can skip wiping data if you are updating)
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you want to sideload Gapps / Magisk you must reboot recovery now (This option is in the Advanced Menu of LOS Recovery). If you are only installing Lineage, you are ready to reboot to system.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.
Updating Lineage​
Using LOS Recovery:
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you use Gapps or Magisk, you also need to sideload these. Once again you still need to reboot recovery. Hit the back button, choose advanced, and then reboot to recovery.
Apply Update -> Apply from ADB (This must be done between each zip file)
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways.
Then reboot to system. If you were using a hosts file for adblocking you will need to put that back as well when it boots. This gets replaced during the update.

Woah, this is awesome, moving from my old Note 5 to a OP8T very soon (Currently in shipping, I'll have it in hand in a week or so if all goes well, very excited). This will be my first time poking around with Oneplus, or any new device for that matter (I've never dabbled in the AB system and stuff yet) and a guide like this is exactly what I need. Thank you so much!

Guide is updated, with update instructions, and cliff notes. I updated to the new build today. No issues.

For adblock you should add Adaway in there for an easier/safer option. You also get automatic host file updates then too

Very nice sir, very nice indeed!

Are these commands the same for windows?
I have been out of development for a long time. Last roms I built was Windows mobile 5. Probably around 2009. I must admit I'm a little lost in all the new terminology.
I have a T-mobile 8T+5G and SIM is unlocked and waiting on Boot loader unlock token to arrive tomorrow.
If anyone is interested in helping hold my hand through install, root etc I will gladly give a tip for your time. I have windows and and fastboot working. PM me for contact information.

bobsbbq said:
Are these commands the same for windows?
I have been out of development for a long time. Last roms I built was Windows mobile 5. Probably around 2009. I must admit I'm a little lost in all the new terminology.
I have a T-mobile 8T+5G and SIM is unlocked and waiting on Boot loader unlock token to arrive tomorrow.
If anyone is interested in helping hold my hand through install, root etc I will gladly give a tip for your time. I have windows and and fastboot working. PM me for contact information.
Click to expand...
Click to collapse
It is the same commands for windows. Just need to install the proper fastboot and adb binaries and drivers for windows (can easily be found by searching).

bobsbbq said:
Are these commands the same for windows
Click to expand...
Click to collapse
Just remove "sudo" from them. The distro I'm using requires fastboot / ADB to be run as root. Sudo obviously won't work and isn't needed in Windows. Everything else is the same.

Could you add "Revert Back to OOS from Lineage Guide" too ? Just in case people want to restore OOS !

rohanhole said:
Could you add "Revert Back to OOS from Lineage Guide" too ? Just in case people want to restore OOS !
Click to expand...
Click to collapse
This I should probably mention as this device doesn't really have an easy way to return back to stock at the moment. At least without using the MSM Tool, that I know of? At the moment you will need to use the MSM tool.
MSM / Unbrick Tool Thread <-- Instructions / Guide Included in that thread. * Remember using this tool will wipe your data, and it will relock your bootloader.
Also that is the regular 8T thread, TMobile users wanting the TMobile version would use the TMobile Thread.
jwarrior319 said:
For adblock you should add Adaway in there for an easier/safer option. You also get automatic host file updates then too
Click to expand...
Click to collapse
I'm not sure about safer? Again I'm making some assumptions I guess... I've never used Adaway, always used a hosts file. For what it's worth there is an adway add on in the NikGapps addon folder. At some point maybe I'll try and test this.

OhioYJ said:
This I should probably mention as this device doesn't really have an easy way to return back to stock at the moment. At least without using the MSM Tool, that I know of? At the moment you will need to use the MSM tool.
MSM / Unbrick Tool Thread <-- Instructions / Guide Included in that thread. * Remember using this tool will wipe your data, and it will relock your bootloader.
Also that is the regular 8T thread, TMobile users wanting the TMobile version would use the TMobile Thread.
I'm not sure about safer? Again I'm making some assumptions I guess... I've never used Adaway, always used a hosts file. For what it's worth there is an adway add on in the NikGapps addon folder. At some point maybe I'll try and test this.
Click to expand...
Click to collapse
Another way to revert back to OOS is to use the payload dumpster tool with a full ota zip and flash all the images. There's a thread already with instructions on that.
Edit: https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
Under manually in post 1

jwarrior319 said:
Another way to revert back to OOS is to use the payload dumpster tool with a full ota zip and flash all the images. There's a thread already with instructions on that.
Edit: https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
Under manually in post 1
Click to expand...
Click to collapse
I figured this might be possible, but I hadn't tried yet. Very helpful. MSM should always be a last resort.

I had already rooted and flashed the LOS ROM. I forgot to come back to this guide. I did not back up the persist and modem files. Is it too late for that now?

bobsbbq said:
I had already rooted and flashed the LOS ROM. I forgot to come back to this guide. I did not back up the persist and modem files. Is it too late for that now?
Click to expand...
Click to collapse
I don't think linage touch these paritions (at least not the persist one), but I might be wrong. In either case I would take a back up of persist and the modems now, as a backup from now is probably better than no backup if you get any problems later on.

Is there supposed to be F-Droid and Micro-G in the base LOS Rom? I don't have either. Sorry still trying to get use to this.

bobsbbq said:
Is there supposed to be F-Droid and Micro-G in the base LOS Rom? I don't have either. Sorry still trying to get use to this.
Click to expand...
Click to collapse
No it is not.

Got LOS installed, still does fastboot loop. Sideloaded Magisk 21.4, failed. Can't get past fastboot....hasn't booted to LOS even once
.

Anyone? No sense in trying it again until there's some feedback.
Device is NOT bricked. Can still reinstall the ROM, just will not boot to LOS...

Success!
You have to use r31.0.0 platform-tools
Linux users run commands as ROOT & add ./ before fastboot (./fastboot)

How To Guide [GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - via Recovery - via Local Update

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL
Installing an OTA.zip Update with ADB Sideload​
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine - ​
Click to expand...
Click to collapse
In this thread you will find different ways to install an OTA update :
Via ADB SIDELOAD (this post) - Via Recovery Mode - Via Local Upgrade
​I am writing this tutorial on ADB Sideload, one more on this topic, in order to be able to push an OTA Zip update, which for some reason could not be done properly.
Sometimes manufacturers allow users to make links or zip files of OTA updates available to other users. Once you have downloaded the OTA zip file, you will need this tutorial to proceed with the installation.
I borrowed the first two screenshots from the web so that I could explain clearly with pictures.
In the end it is very simple and requires little command line knowledge. But you will need to check some things:
- Firmware stock
- Unmodified system partition
- Third party apps like Magisk, Xposed Framework, and as a precaution TWRP Recovery should not be installed on your smartphone
Before starting, here is the list of prerequisites to perform the sideloading of the OTA package.
1. Have a backup of your data, even if theoretically performing a sideload will not erase your data,
2. Download the USB Drivers from the manufacturer, or the latest one from Google ( Link )
3. If you haven't already done so, you must download and install Android SDK Platform-tools (platform-tools_r33.0.2-windows.zip)
4. Don't forget to push on this folder "platform-tools" the file named "Global full Nothing OS 1.1.0.zip" - for example- that you need
4. And finally you will have to activate the USB debugging of your Phone(1) : to do so, you have to go to : Settings => System => Advanced => Type 7 times on the build number => once done, a pop-up will appear and will tell you that you have become a "Developer" => On some devices you will have to type in the Pin code.
5. Once you have become a developer => go back to System => Developer Options => Enable the USB Debug toggle
6. That's it if you are ready to do a Sideload, but also other operations!
{
"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"
}
​
These prerequisites are essential for this and a number of other operations.
You are ready, the tension is rising! You will succeed!
To do this, you must reboot your Phone(1) into the standard recovery system and you have 2 ways to reboot into Recovery.
1. You can use the hardware key combination specific to your smartphone.
2. Or use the ADB command
Booting into Recovery Stock mode with the ADB command
You go to the start screen of your PC and in the search bar you type:
Code:
cmd
and then press Enter. The command prompt starts.
Depending on where you have placed your "Platform-tools" folder you type:
Code:
C:\WINDOWS\system32>cd c:\platform-tools
and you should see on your command line screen
Code:
c:\platform-tools>
Once you are in your Platform-tools folder, connect your smartphone to your PC, making sure that USb debugging is effective.
Type the following command: adb devices and you should see the identification of your smartphone
When you run an ADB command, you should see an RSA key prompt on your smartphone screen asking you to allow USB debugging. Press OK to allow it.​
Type the following command: adb reboot recovery​
Then the command: adb sideload "file name".zip - For the example, I typed the full name of the file, but you can rename the file shorter like "nothing_ota".zip
That's it, normally the installation is started and you just have to wait for the update to be installed on your device. Once the installation is successful, you can restart your device.
I hope this tutorial has helped you to push an OTA.zip update.
Go ahead now

Installation via recovery mode​
The recovery mode of the Phone(1) is similar to that of the Google Pixel. This allows you to easily sideload the update packages via the recovery interface.
To perform this process, here are the steps and requirements:
Have downloaded the .zip file of the update to your computer
Your Phone(1) must be recognised by the ADB command on your computer
The Process:
Go to your Shell terminal, then run the recognition command:
Code:
adb devices
then the command :
Code:
adb reboot recovery
On your Phone(1) screen, you should see this "No command"
While pressing the Power button, press the Volume Up button then release both buttons quickly. The Android recovery menu should be visible.
Nothing Phone 1 recovery mode
On your Phone(1) screen, select the option: Apply update from ADB.
On your computer, run the command:
Code:
adb devices
This should return the serial number of the device with the 'sideload' next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:
Code:
adb sideload "filename".zip
The "filename" part should be replaced with the full path, followed by the name of the file downloaded in step 1.
The update will be installed on your phone.
Once the installation is complete, select "Reboot system now" on your phone to reboot into the new version.
Well done, you have installed the new update of Nothing OS to your Phone(1) with success
To date I still haven't received my phone(1). Once I have it in my hands, I will make screenshots about this tutorial.

Install OTA using Local Upgrade method​
Create a folder named “ota” (without the quotes) at the root of the internal storage. Meaning outside every folder.
Copy the OTA update ZIP file from above to that folder.
Open the phone app and Dial ##682##
This should launch an offline update tool.
The tool will scan for an OTA file from internal storage and install it.
If that fails, you can manually browse for the OTA package.
After selecting the OTA file, the wizard will apply the update.
Reboot the device and you are on the latest firmware.

Reserved 3

I think also after update, reboot, redo the step and sideload also Magisk for keep root

Pho3nX said:
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Click to expand...
Click to collapse
Yes I agree, but those tutos are for everyone, and everyone doesn't rooted his smartphone like us
So I won't confuse them

hello, thanks for the guide, when I do all the steps without any problems and reboot, it opens with the old version, where could I be doing wrong?

This will work to downgrade the phone also?

pankspoo said:
This will work to downgrade the phone also?
Click to expand...
Click to collapse
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone

sh4tteredd said:
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
Click to expand...
Click to collapse
So we can use your Windows tool to downgrade ?

pankspoo said:
So we can use your Windows tool to downgrade ?
Click to expand...
Click to collapse
I won't downgrade this phone at all. Btw maybe I'm wrong and it can work but I'm not sure and I don't suggest to do it

Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.

demiii said:
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
View attachment 5716899
Click to expand...
Click to collapse
Which version of ADB Sideload do you use ?
Post 1 or Post 2

Sib64 said:
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Click to expand...
Click to collapse
What I did was reboot to recovery, navigate to Apply Update via Sideload through the recovery interface and from there entered the command adb sideload filename.zip so i guess it is the method in post 2
UPDATE:
I have tried the method in Post 1 and this error shows up:
UPDATE 2:
I have tried revoking USB DEBUGGING authorization, adb kill-server, adb start-server and authorizing again
I have tried deleting adbkey and adbkey.pub files in C:Users/$Name/.android
I have tried following suggestions about solving this error both from this and this StackOverflow thread
Nothing worked for me.

You don't need to use ADB to sideload an OTA, the nothing phone contains an OTA updater In the phones os already, the only thing you need the computer for is to move the OTA to the phone

Here is what someone on the nothing discord said to do and it worked
dont sideload
Create a folder named “ota” (without the quotes) at the root of the internal storage of your phone. Then copy the update ZIP file to that folder.
Dial `*#*#682#*#* `to open up the offline update tool.
You can also use an activity launcher app to locate and execute the “OfflineOTAUpgrade” tool. The package name of the tool is com.nothing.OfflineOTAUpgradeApp.

Hi, I have just tried your method but an error window pops up:

Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?

Ky0sHiR0 said:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Click to expand...
Click to collapse
You can only upgrade not downgrade

demiii said:
Hi, I have just tried your method but an error window pops up:
View attachment 5717197
Click to expand...
Click to collapse
If you go on nothing discord and put that error maybe they can help