Related
I just got an N7 32GB tablet, very nice. I plan on rooting this device. Mine still on 4.2.1. What guide you guys recommend, both seem good so I'm undecided.
Thanks
Aut0botK1lla said:
I just got an N7 32GB tablet, very nice. I plan on rooting this device. Mine still on 4.2.1. What guide you guys recommend, both seem good so I'm undecided.
Thanks
Click to expand...
Click to collapse
Do you know how to use adb/fastboot ? if you know you can use that to easily root the N7.
Here's the link on how to use adb/fastboot to unlock and root the Nexus 7.
If not, then use this toolkit by following the link below:
http://forum.xda-developers.com/showthread.php?t=1766475
Download the program and install it.
After that, watch this tutorial first once and then start rooting with the toolkit.
http://www.youtube.com/results?sear...0.219.737.0j3j1.4.0...0.0...1ac.1.NbcxhPx0ZLs
IMPORTANT NOTE: You must unlock your Nexus 7's bootloader in order to proceed with the rooting process. As a result, everything in your tablet will be erased. So backup what you can and put it back later.
I would recommend using adb fast boot method, it is very simple if you follows it correctly, I will give you full instructions on how to unlock boot loader and root
ALL DATA WILL BE LOST , BACKUP EVERYTHING
I RECOMMEND USING TWRP CUSTOM RECOVERY
Getting started
In order to root Android 4.2 the following three requirements must be satisfied beforehand:
The Android SDK, which you can download from Google Developers
A custom recovery like ClockworkMod (CWM) or Team Win Recovery Project (TWRP)
SuperSU, which you can download from CF-Root
There are no major differences between the two, but TWRP is more touch-oriented thanks to larger buttons. CWM is also available in a touch-compatible variant, but it has much smaller buttons. It's a matter of personal preference between the two though, but you have to choose one.
Before starting the process I urge you to perform a backup, as all data might be lost afterwards. You can copy the contents of the SD card to a safe external location such as cloud storage service or computer hard drive.
Setting the Stage
The first step that needs to be performed after all the files are downloaded is to install the Android SDK. Afterwards open the Android SDK Manager and select the following two items:
Android SDK Platform-tools -- it contains the required programs to install Android 4.2 Jelly Bean
Google USB Driver -- it contains the necessary drivers for the Nexus device
Then you should create a folder in an easily accessible location within the command line. In this example I will use a folder named "Root" in my C:\ drive in Windows. The path name will therefore be: "C:\Root".
From the folder where Android SDK Platform-tools is installed (in my case it is "C:\Program Files x86)\Android\android-sdk\platform-tools") copy the following files to the previously created "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
The following files must also be copied to the "Root" folder:
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery that you previously downloaded for your specific device (please see below)
For my 8 GB nexus 7 wifi(codename "grouper") I will use TWRP with the name "openrecovery-twrp-2.3.1.0-grouper.img".
You can easily find the codename for your devoice by looking into Google
The custom recovery file differs for each device, please make sure you download the correct file
In order to make the process smoother for instance the SuperSU file can be renamed to "root.zip" and the custom recovery to "customrecovery.zip". It's a matter of convenience, but for accuracy I will stick to the original naming for this guide.
If the previous steps are completed you must have the following six files in your "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery. In my case it is "openrecovery-twrp-2.3.1.0-grouper.img"
From there, you can proceed to install the drivers for "fastboot mode". To install them, follow these steps:
Power off your Nexus device.
Press and hold Volume Up and Volume Down then press and hold the Power button; the device will now enter "fastboot mode".
Go to Device Manager (Computer -> Properties -> Device Manager in Windows 7/8) and identify the device; for me it shows up as Android 1.0.
Right click Android 1.0 and select "Update Driver Software," then select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer," then click "Next".
From "Have Disk..." option go to the folder where you have Google USB Driver installed (for me it's "C:\Program Files .(x86)\Android\android-sdk\extras\google\usb_driver") and select "android_winusb.inf".
Out of the three options select "Android ADB Interface" and validate any future warning window to install the driver.
Final preparations
Everything is prepared in order to start the installation process, but in order to do so a command window must be opened. Windows Key + R opens "Run"; type in "cmd" and the command window appears. Typing "cd C:\Root" and pressing Enter sets the "Root" folder as the working directory. Pressing the Shift key and right clicking inside the "Root" folder will also deliver the same result.
The device must be turned on in "fastboot mode" which I have explained at step no.2 during the driver installation process, and obviously plugged-in to the computer. You then have to type in the following commands while in "fastboot mode":
fastboot devices -- this is just for verification purposes; if there is no listed device then the drivers have been improperly installed and steps 1 through 7 must be redone.
fastboot oem unlock -> you have to accept the prompt in order to continue -- this command will unlock the bootloader, but it will also erase the data on the device which is why a backup is necessary.
fastboot reboot-bootloader -- this will reboot the bootloader.
fastboot flash recovery openrecovery-twrp-2.3.1.0-grouper.img -- this will flash the custom recovery --please use the specific file and name for your particular Nexus device!
fastboot erase cache -- this will erase the cache -- might not be necessary but it's just as a precaution.
fastboot reboot -- this will reboot the device.
After Android 4.2 is loaded and running the SuperSU file must be copied from the "Root" folder to the internal storage (shows up in Windows Explorer as a Nexus device). A simple copy and paste will do the trick here.
Then you have to power off the Nexus device and enter "fastboot mode" again. Use the Volume Up and Volume Down keys to navigate until you can select "Recovery Mode". After the power button is pressed the device will reboot in the new custom recovery.
Rooting your Nexus device
If you have ClockworkMod installed, you have to perform the following steps:
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "0" (zero) folder
Select "CWM-SuperSU-v0.97.zip"
Select "Yes - Install CWM-SuperSU-v0.97.zip"
Select "Go Back"
Select "reboot system now"
If you have Team Win Recovery Project installed, you have to perform the following steps:
Press "Install".\
Select "CWM-SuperSU-v0.97.zip" -- for me it's in the "0" (zero) folder
Swipe to confirm flash
Press "Wipe cache/dalvik" (just as a precaution)
Swipe to wipe
Press "Reboot System"
After Android 4.2 loads your device can run apps with elevated privileges (meaning it's rooted). A SuperSU app is installed in order to allow root requests, so please use your judgement on which apps you grant access.
If you experiences any problem, please reply and I will look into it.
Sent from my Nexus 7 using xda app-developers app
+ Above.
Way to wordy and not easy to follow
Basically:
Boot into recovery (yes i know you don't properly have one)
Get Android SDK from HERE
Once downloaded/installed.
Navigate to the "Platform-tools" folder, where you should see ADB/FASTBOOT
Hold shift, right click and "open command prompt here"
type fastboot devices
(if your device is listed, move on)
Unlock your bootloader
type fastboot oem unlock
Download THIS(supersu)
Download TWRP from HERE
Place the SuperSU download file on your SD CARD (Nexus has a virtual SD, place it there)
Place the recovery in the "Platform-tools" folder with your ADB/FASTBOOT files.
Reboot to fastboot again (Power and volume down)
fastboot devices
if listed continue:
fastboot flash recovery openrecovery-twrp-2.4.1.0-grouper.img
Reboot back into recovery (which should now be twrp) (POWER AND VOLUME DOWN)
Then from TWRP menu choose "Install"
Find the 2 files you downloaded and placed on SD card
Install them using TWRP.
Reboot
Profit.
Wilks3y said:
+ Above.
Way to wordy and not easy to follow
Click to expand...
Click to collapse
Well... I liked it... for a guy with only 2 posts to his/her name to explain (perhaps in TOO much detail) how to root takes b**ls:!
Keep it up, naman14... but be a little more judicious in what you include (and choose to exclude) in your walkthrou's.
Writing instructions is art in itself... and requires practice. Succinct and pithy is the way to go.
Rgrds,
Ged.
Thank you all, the last thing i ever rooted was my sprint htc hero a yr or so ago
IT WORKED FOR ME, BUT IT MIGHT NOT FOR YOU. TRY AT YOUR OWN RISK.
I unlocked and rooted my N7 4.2.2 wifi using this tool kit http://forum.xda-developers.com/showthread.php?t=1809195 .
I then updated to 4.3 OTA and lost root but the bootloader was still unlocked. If yours hasn't been unlocked then this isn't for you.
Download CWM 6.0.3.5 from their website and superSU v 1.51 from the superSU site.
Down load and install the Nexus7 tool kit. (Link above)
Put the CWM .img in a folder which is inside the Nexus7 tool kits main folder in C: , the folder is easy to find as there are a few together which are used to add you own files to the phone and not the kit's built in ones, so look for the add an .img file (or something similar) and there is only one folder for adding .img files.
Put the superSU zip on your phone(if you don't know how to do this, then do not go any further and wait for a one click tool kit solution.)
I donated so I have the newest V5.0.0 but I don't think it needs to be this version as an older one should do it, because you are adding the newest files yourself.
Start the tool kit and go to main option, you need to type in 99 when you get the pick a build version screen. You will then get a big list of options.
Select 1 to add the drivers!
Then after the drivers have been installed, select option 11 and then you should have two options 1 for a non permanent flash and 2 for a permanent flash: select 1, then type the name of the file(the CWM .img which if you put it in the right folder will be shown above where you have to type the name) in and follow the instructions.
Your phone will boot into fast boot, if it wasn't already, after you followed the instructions then navigate to the zip on your phone (install from sd card?) then /0 scroll down and install the superSU zip. Then ''go back' untill it gives you the option to select no or yes connected with recovery mode, I selected yes, because most tool kit instructions seem to recommend it. Go to the superSU program and see if it opens OK and if it does, like mine did, then that's it! Rooted with no problems.
If you have used CWM before then this will be very easy for you(I've used it before). I found how to do this just by reading the instructions in the tool kit and trying it, with my fingers crossed, so READ THE INSTRUCTION IN THAT PART OF THE TOOL KIT (option 11).
This was very easy and very fast (I had been trying lots of other 4.3 toolkits but couldn't get CWM to install 'no erro'?)
I did this this morning and have since uninstalled the tool kit, because I won't use it again for a while, so this is why some of the folder names aren't exact, but you will know which ones I am talking about when you look.
If someone, who is experienced at this, wants to clarify some parts in a comment, then feel free.
Thanks!
I just did this, and wanted to revise the instructions slightly based on my experience.
Download CWM 6.0.3.5 from their website and superSU v 1.51 from the superSU site.
Download and install the Nexus7 tool kit. (Link above)
Put the CWM .img in a folder which is inside the Nexus7 tool kits main folder in C: , the folder is easy to find as there are a few together which are used to add you own files to the phone and not the kit's built in ones, so look for the add an .img file (or something similar) and there is only one folder for adding .img files.
Put the superSU zip on your phone(if you don't know how to do this, then do not go any further and wait for a one click tool kit solution.)
I donated so I have the newest V5.0.0 but I don't think it needs to be this version as an older one should do it, because you are adding the newest files yourself.
Start the tool kit and go to main option, you need to type in 99 when you get the pick a build version screen. You will then get a big list of options.
Select 1 to add the drivers!
Then after the drivers have been installed, select option 11 and enter the file name. If there's only one file listed (the CWM .img which if you put it in the right folder will be shown above where you have to type the name), you can enter *
You should have two options 1 for Boot (non permanent flash) and 2 for a permanent flash: select 1
If your tablet is booted, enter 'no' to reboot to fastboot mode.
Your phone will boot into fast boot, if it wasn't already, after you followed the instructions then navigate to the zip on your phone (install from sd card?) then /0 scroll down and install the superSU zip.
Select ''go back' thren boot into recovery mode. Select yes.
Boot and run the superSU program and see if it opens OK and if it does, like mine did, then that's it! Rooted with no problems.
Reboot recovery then choose yes.
I could no longer boot to recovery, so I re-flashed recovery and was fine.
"...put the superSU zip on your phone (if you don't know how to do this, then do not go any further and wait for a one click tool kit solution.)..."
Hi, nevereven...
You don't need to wait for a one click tool kit solution.
Easiest way to "put the superSU zip on your phone" is to download it directly to the Nexus 7 first, using Chrome (or whatever browser you're using) - from the link below. (Chrome will download it to the /download folder, as will most other browsers).
http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Once CWM is flashed, navigate to the /download folder and install the SuperSU .zip.
Anyway... it's the way I'd do it (if I was a using a toolkit)
Rgrds,
Ged.
DISCLAIMER: I will not be responsible of any issues you could face following this how-to. You do it at your own risk!
Here is a guide to root Honor 8 B521 Oreo. I did this on FRD-L09C432B521. Even if i think the "easy method" should work with other iteration of the phone (L02, L19, ...), I am not sure ramdisk is the same for all so test it if you feel lucky and please report if it works or not.
Requirements:
- Honor 8 running Oreo
- Unlocked Bootloader
- adb and fastboot installed on your computer (https://forum.xda-developers.com/android/software-hacking/alpha-adb-fastboot-installer-windows-t3637255 (Hit the thanks button)
Long method: (should work for all honor 8)
1 -- Visit http://pro-teammt.ru/firmware-database/ and search your exact build (FRD-L09C432B521 for me). If you have several phones listed for your build, click the name of the build on the left. This will open an xml file on the first line of which you will see the exact model it is for.
2 -- Once you know which firmware is yours, click on "filelist". This will list the files for this build and theirs url. Copy the link pointing to "update.zip" (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3109/g1699/v159456/f1/full/update.zip for me). Decompress it wherever you want.
3 -- Download and run Huawei Update Extractor (Hit the thanks button) . Untick "verify header checksum" in "settings" tab.
4 -- In the "extract" tab, click on "..." and select "update.app" in the previously "update.zip" decompressed folder.
5 -- Files from "update.app" should now be listed. Find "ramdisk" and right click on it. Choose "extract" and you will be able to save the file wherever you want. Copy this file on your phone.
6 -- On your phone: Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. Grant permission to the manager to access your storage in phone settings > applications.
7 -- Run Magisk Manager, it will ask you if you want to install the zip. Select "Yes". It will now ask if you want to flash the zip or to patch a boot image, choose this last one. Point to the ramdisk img you previously copied on your phone. Magisk manager will now patch it and create a new "patched_boot.img" file. Copy this on your computer.
8 -- On your computer: Open a command prompt where you copied "patched_boot.img". Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_boot.img
fastboot reboot
9 -- Your phone will now reboot and be rooted. To unroot, repeat the process (8) with your stock ramdisk (the one extracted with Huawei Update Extractor)
Easy method
If your build is FRD-L09C432B521, FRD-L02C432B521, FRD-L04C567B520 or FRD-L09C432B562, you can use these already patched ramdisk.img.
patched_RAMDISKL09B521.img
stock_RAMDISKL09B521.img
patched_RAMDISKL02B521.img thanks to @Sharath007for the file
patched_RAMDISKL04B520.img thanks to @macbuggo for the file
stock_RAMDISKL04B520.img thanks to @macbuggo for the file
patched_RAMDISKL09B562.img thanks to @topscorer for the file
stock_RAMDISKL09B562.img thanks to @topscorer for the file
On your computer: Open a command prompt where you downloaded "patched_RAMDISKL09B521.img" (or L02/L04 ramdisk) .
Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_RAMDISKLXXBXXX.img (the exact name depends of the ramdisk you downloaded)
fastboot reboot
Your phone will now reboot
Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it.
You now got root. To unroot, repeat the process with stock ramdisk.
Worked in the first attempt.. Safety net passes..
Sharath007 said:
Worked in the first attempt.. Safety net passes..
Click to expand...
Click to collapse
Did you do this on L09? Otherwise, could you share the patched ramdisk so I can add it in OP?
stephtban said:
Did you do this on L09? Otherwise, could you share the patched ramdisk so I can add it in OP?
Click to expand...
Click to collapse
Thanks for your guide. I did it on my FRD-L02 Variant.
FRD_L02_patched_boot
Sharath007 said:
Thanks for your guide. I did it on my FRD-L02 Variant.
FRD_L02_patched_boot
Click to expand...
Click to collapse
Thanks! I added your ramdisk to OP. Do you still have unpatched version of it for easy unrooting?
delete
PremiumBlaze said:
Can't guys flash Magisk using twrp? It worked for me in android oreo.
Click to expand...
Click to collapse
You can indeed use twrp but as it is not completely functional yet, some people don't use it. Besides, Open Kirin suggest to flash their rom with fastboot so it limits the interest of having twrp.
stephtban said:
DISCLAIMER: I will not be responsible of any issues you could face following this how-to. You do it at your own risk!
Here is a guide to root Honor 8 B521 Oreo. I did this on FRD-L09C432B521. Even if i think the "easy method" should work with other iteration of the phone (L02, L19, ...), I am not sure ramdisk is the same for all so test it if you feel lucky and please report if it works or not.
Requirements:
- Honor 8 running Oreo
- Unlocked Bootloader
- adb and fastboot installed on your computer (https://forum.xda-developers.com/android/software-hacking/alpha-adb-fastboot-installer-windows-t3637255 (Hit the thanks button)
Long method: (should work for all honor 8)
1 -- Visit http://pro-teammt.ru/firmware-database/ and search your exact build (FRD-L09C432B521 for me). If you have several phones listed for your build, click the name of the build on the left. This will open an xml file on the first line of which you will see the exact model it is for.
2 -- Once you know which firmware is yours, click on "filelist". This will list the files for this build and theirs url. Copy the link pointing to "update.zip" (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3109/g1699/v159456/f1/full/update.zip for me). Decompress it wherever you want.
3 -- Download and run Huawei Update Extractor (Hit the thanks button) . Untick "verify header checksum" in "settings" tab.
4 -- In the "extract" tab, click on "..." and select "update.app" in the previously "update.zip" decompressed folder.
5 -- Files from "update.app" should now be listed. Find "ramdisk" and right click on it. Choose "extract" and you will be able to save the file wherever you want. Copy this file on your phone.
6 -- On your phone: Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. Grant permission to the manager to access your storage in phone settings > applications.
7 -- Run Magisk Manager, it will ask you if you want to install the zip. Select "Yes". It will now ask if you want to flash the zip or to patch a boot image, choose this last one. Point to the ramdisk img you previously copied on your phone. Magisk manager will now patch it and create a new "patched_boot.img" file. Copy this on your computer.
8 -- On your computer: Open a command prompt where you copied "patched_boot.img". Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_boot.img
fastboot reboot
9 -- Your phone will now reboot and be rooted. To unroot, repeat the process (8) with your stock ramdisk (the one extracted with Huawei Update Extractor)
Easy method
If your build is FRD-L09C432B521 or FRD-L02C432B521, you can use these already patched ramdisk.img.
patched_RAMDISKL09B521.img
stock_RAMDISKL09B521.img
patched_RAMDISKL02B521.img thanks to @Sharath007for the file
On your computer: Open a command prompt where you downloaded "patched_RAMDISKL09B521.img" (or L02 ramdisk) .
Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_RAMDISKL09B521.img OR fastboot flash ramdisk patched_RAMDISKL02B521.img
fastboot reboot
Your phone will now reboot and be rooted
To unroot, repeat the process with stock ramdisk.
Click to expand...
Click to collapse
Thanks! work perfectly
freewind29 said:
Thanks! work perfectly
Click to expand...
Click to collapse
Don't quote entire op please.
Did not work on my phone (L09C432) with the "easy way".
Flashed patched ramdisk, no root, but at least still running.
daFlox said:
Did not work on my phone (L09C432) with the "easy way".
Flashed patched ramdisk, no root, but at least still running.
Click to expand...
Click to collapse
Sorry, I forgot a step. After you flashed the patched ramdisk, go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. This should work then. Please tell me if it helped.
OP edited with this new step.
Worked great here for FRD-04, one thing to add
You may have to restart your phone to be able to see the patched file via MTP in order to copy it to your PC.
macbuggo said:
Worked great here for FRD-04, one thing to add
You may have to restart your phone to be able to see the patched file via MTP in order to copy it to your PC.
Click to expand...
Click to collapse
Happy this works. Could you share the stock ramdisk and the patched ramdisk so I can add it in OP.
stephtban said:
Sorry, I forgot a step. After you flashed the patched ramdisk, go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. This should work then. Please tell me if it helped.
OP edited with this new step.
Click to expand...
Click to collapse
Ahhh, okay!
Will try it this evening and report tomorrow.
daFlox said:
Will try it this evening and report tomorrow.
Click to expand...
Click to collapse
Works, thanks a lot!! (additional thanks in the original post )
stephtban said:
Happy this works. Could you share the stock ramdisk and the patched ramdisk so I can add it in OP.
Click to expand...
Click to collapse
I couldn't upload to XDA directly due to 8MB limit unfortunately, here it is if you want to put it up on your google drive or something
http://s000.tinyupload.com/index.php?file_id=10562650897614852938
This is a patched image of FRD-04C567 8.0.0.520 with Magisk 17.1
macbuggo said:
I couldn't upload to XDA directly due to 8MB limit unfortunately, here it is if you want to put it up on your google drive or something
http://s000.tinyupload.com/index.php?file_id=10562650897614852938
This is a patched image of FRD-04C567 8.0.0.520 with Magisk 17.1
Click to expand...
Click to collapse
Thanks. File and credit added to OP. Do you still have stock ramdisk for easy unrooting?
Tinyupload appears to be down, these links will last for 30 days
FRD-L04C567 8.0.0.520 ramdisk patched Magisk 17.1
https://ufile.io/nsa1h
Stock L04 520 ramdisk
https://ufile.io/34eq5
macbuggo said:
Tinyupload appears to be down, these links will last for 30 days
FRD-L04C567 8.0.0.520 ramdisk patched Magisk 17.1
https://ufile.io/nsa1h
Stock L04 520 ramdisk
https://ufile.io/34eq5
Click to expand...
Click to collapse
File added. Thx.
Hallo! Is it possible to root my FRD-L09 Honor 8 Oreo this way too? And after then can I flash/install a Stock Version with Emui 5 Android 7 Nougat and then un-root again? I need my device unrooted, because of SkyGo App (Germany) doesnt work with rootet Devices ...
If theres another way to downgrade without these operations, please let me know and maybe show me the steps for that?! Thank you so much!
YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
ISSUE: FASTBOOT Might not work on windows 10 version 2004, a solution is to use a Linux virtual machine to use fastboot commands. Test it out first as you might be lucky and it could work for you.
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port, as USB 3.0 might give you issues with the fastboot commands)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Usyless said:
YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Click to expand...
Click to collapse
Thank you excellent post just what I needed.
eedwin101 said:
Thank you excellent post just what I needed.
Click to expand...
Click to collapse
I'm glad it helped you
Usyless said:
I'm glad it helped you
Click to expand...
Click to collapse
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
eedwin101 said:
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
Click to expand...
Click to collapse
I know that phhussons AOSP works on this phone with no issues aswell, you might have to use securize to get safety net to pass tho.
android 11 will boot on this phone however iirc you won't be able to hear and other people won't hear you in phone calls.
havoc gsis I believe works but I haven't tested it and I have only heard of one person using it.
BLISS/LOSQ/CAOS don't work on this phone at all.
and after that I don't think there really is many more GSIs that work as they just won't boot for bizarre reasons
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
_Sherrif said:
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
Click to expand...
Click to collapse
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Usyless said:
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Click to expand...
Click to collapse
No AT&T.
_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
or you could try this: https://t.me/razer_phone/12949
install instructions shown in the message
Usyless said:
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
Click to expand...
Click to collapse
Aight! Definitely worth a try. Tried everything else.
Thank you!
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
frannet said:
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
Click to expand...
Click to collapse
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Usyless said:
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Click to expand...
Click to collapse
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
frannet said:
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
Click to expand...
Click to collapse
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Usyless said:
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Click to expand...
Click to collapse
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
frannet said:
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
Click to expand...
Click to collapse
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Usyless said:
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Click to expand...
Click to collapse
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ??
frannet said:
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ?
Click to expand...
Click to collapse
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
i
Usyless said:
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
Click to expand...
Click to collapse
Hahaha, yeah, If I'm honest, dark mode in iOS work fine, very fine, normally I use my iPhone 11 and I play with android devices for.. for play with the OS and develoment OS, and as second andriods phone for maybe.... I go to check the gsi mode, thanks guy!!
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 Updated1. 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 Bootloader2. 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 / EFS3. 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 Lineage4. 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, Gapps5. 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, Magisk5. 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 Net6. 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 Blocking7. 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)