My phone, the LeEco Le Pro 3 LEX727 ZL1_NA US model is on the latest EUI 5.8.021S. I am able to open the adb tools in command prompt and get my computer to recognize my phone with "adb devices", but when I go to the stock fastboot with the Chinese and English writing and use "fastboot devices" nothing shows up. I'm using the latest adb tools and am clueless as to what to do.
Unlock Bootloader - Le Eco Pro 3
If you are not seeing your phone ID in ADB
Did you enable enable Developer options, or chosen MTP?
Its possible that the Android driver driver is outdated, or just try another usb port, preferably in the back of the machine.
Go here to check a whole list of possible causes: https://appuals.com/android-phone-not-showing-up-on-pc/
More than you asked for:
Since you seem to be new to your Leeco phone and new to using custom roms, I am going to go ahead and answer your current question and provide you steps needed to move forward. No big deal, I just copy pasted my notes ( with a few edits)
First steps that you need to take:
1. You will first need to unlock the bootloader :
PHP:
https://forum.xda-developers.com/showpost.php?p=71566961&postcount=203
2. Install Twrp :
PHP:
https://twrp.me/leeco/leecolepro3.html
****** Scroll down to see: Fastboot Install Method (
3. Right now just use ADB. But for the future, I highly recommend that you buy an OTG drive: it makes the whole process a thousand times easier: They are cheap somewhere near $5 and worth ten times that
Unlocking the Bootloader
You can save your self alot of time by looking up how to give ADB system wide privileges: this will allow you to flash files without tying the directory path.
Mauronofrio created a tool called: "TOOL ALL IN ONE"" it's great, install it and check for updates.
PHP:
https://toolaio.tk
The all is one tool is excellent and you can use it to install everything if wanted.
I usually recommend it for novices that can use it to help with unlocking the bootloader and installing TWRP.
The tool will also update your copy of ADB, android Drivers and provide system wide privileges for ADB
LETS RECAP : Choose using the All in One Tool or the ADB Method
**********BEFORE DOING ANYTHING*******************
Make sure you have enabled the developer tools,
Turned on USB debugging
Authorized your computer on your device I.E: “MTP”
Make sure the All in One Tool can see your device
(*) Select your device from the drop down menu, then click check
(*) Choose to install drivers, and set ADB and fastboot privileges from advanced menu.
(*) First attempt to unlock, then check bootloader status
If you have a X727 you will need to flash : emmc_appsboot.mbn from this zip :
PHP:
https://androidfilehost.com/?fid=313042859668275431
Next, choose Recovery flasher and manually select your copy of TWRP
After you have received the success message, I recommend doing the rest of the install manually within Twrp Recovery.
(*) Reboot into TWRP and begin installation of your Rom, Gapps and Magisk.
Using the ADB Method
Install ADB/Fastboot tools on your computer
PHP:
https://wiki.lineageos.org/adb_fastboot_guide.html
1. Make sure you have enabled the developer tools,
2. Turned on USB debugging, and authorized your computer on your device “MTP”
3. Enter fastboot mode on phone (hold power and VOL -)
4. Make sure adb can see your device when you run "adb devices"
5. type: fastboot devices
6. fastboot flash aboot emmc_appsboot.mbn
7. Run { adb reboot bootloader } - No spaces (before/after)
8. Run { fastboot devices } to make sure you see your device
9. Run { fastboot oem unlock-go } to unlock your device temporarily
10. Run { fastboot oem device-info } to verify unlock status
11. Run { fastboot boot recovery_twrp-3.2.1-0-zl1.img }
12. 5. Reboot back to TWRP and begin installation of your Rom, Gapps and Magisk.
13. 6. If you wiped data, your device will now proceed to re-initialize itself as if from the factory
Concerning your device's storage,
When you boot into twrp you will see a message that states that the storage is encrypted.
*****************Important************************ ******************
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
To remove encryption you will need to format the storage
(Anyone who says otherwise has the X720 and not the X727)
You could also try to skip the formatting step. But you will very likely have permissions issues and get errors and you will eventually have to come back and format ( Again as long as Twrp recovery is install there is very slim chance of ever bricking your phone.
To format the storage
Go to Wipe, choose Format Data and follow the instructions.
This will erase all of photos , music, etc
If you wiped your data partition, you'll need to push the zip file to the newly formatted storage. - This is one BIG reason why using OTG is better. You can use Mauronofrio's "TOOL ALL IN ONE"" for pushing the ROM, Gapps, and Magisk to storage.
Root: You absolutely should root!
NOTE: If you have unlocked the bootloader and flashed TWRP to the recovery partition. But have not yet flashed a Custom Rom the OS will likely reset back to the factory recovery UNLESS YOU ROOT THE SYSTEM. Your device is still unlocked. But the recovery can be overwritten by the stock EUI system, so beware.
Installation of Rom, Gapps, Magisk
Boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to system.
Finished!
If you need help or have a question message me, I would much rather help you with a successful install versus helping you unbrick your phone.
Thank you for your reply. I figured out the issue. Windows 10 updater wasn't auto installing the driver for some reason even though I have auto update ticked.
simpbrackets said:
Thank you for your reply. I figured out the issue. Windows 10 updater wasn't auto installing the driver for some reason even though I have auto update ticked.
Click to expand...
Click to collapse
You have manually install those drivers usually.
Sent from my LEX720 using xda premium
I have the same issue in Windows 10. All In One Tool sees my x720 in adb mode, but when I switch to bootloader, the phone is gone. Device manager then shows unrecognized android device. I have LTSB version of Windows, so maybe that's why it won't auto install the needed driver. Could anyone point out what kind of driver exactly do I need, so that I can install it manually?
Related
[Guide] Pixel XL Android 7.1.2 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2017 Security Patch
Intro
This thread is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel/Pixel XL'.
It also works for Pixel owners: If, they download the correct files for their Pixel.
This Guide is not for use with the Second Generation Pixel 2 or Pixel 2 XL devices.
Update(s):
Other - Added 'Other' after 'Prerequisites'
Disclaimers:
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Google Pixel XL or Verizon Pixel XL phone with an unlockable Bootloader, ([How-to] Unlock bootloader on Verizon Pixel/XL by burduli) - The unlock method was discovered by: Qu3ntin0), and the latest 7.1.2 August 2017, Factory Image (NHG47Q - Verizon; NKG47S - T-Mobile, Fi carriers, and Rogers; NZH54D - Deutsche Telekom; NJH47F - all other carriers).
Note: If you want the latest OTA or Binaries. Tap the Menu icon (upper left corner) then tap Full OTA Images or Driver Binaries
PC - With the latest Android SDK or SDK Platform tools installed.
Important: Update Android SDK or Platform Tools, regularly, for optimal performance.
Need help installing Android SDK or SDK Platform Tools
How to Install ADB & Fastboot on Mac, Linux & Windows-(Method 1)
Easiest-way-to-install-androids-adb-and-fastboot
Other
Pixel XL Guides: Android 9.0.0 (Pie)Android 8.1.0 (Oreo), Android 8.0.0 (Oreo)
Pixel 3 XL Guide: Android 9.0.0 (Pie)
Credit/Thanks/Recognitions
TWRP
TWRP for Google Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone
SuperSU
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
Magisk/MagiskManager
[Unofficial] Google Pixel family support by goodwin_c
Custom Kernels
ElementalX kernel
Franco's Kernel
Busybox/Busybox Checker
[MODS] Android Oreo Aroma installer misc. Mods by Tulsadiver
UPDATE-Busybox.Installer.v1.26.2-ALL-signed.zip
meekfik, download from PlayStore
Busybox Free (Stericson), download from PlayStore
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] by osm0sis
UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip
Busybox Checker, download from PlayStore
Other
pcriz -Fastboot Slot Commands, Custom ROM installion help, Magisk help, and help on many many other subjects.
Those I may have inadvertently forgotten.
Index
Open Command Prompt/ Boot Bootloader/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type 'cmd' and press enter.
Note: If your computer only has 'open powershell here' in the context menu and you do not want to change it or add open 'command prompt here' use use option 2.
Boot Bootloader:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Press volume Up/Down button until you see Recovery Mode > Press Power button.
Testing ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt and press enter to test ADB.
Code:
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot bootloader.
Connect your phone to your computer with a USB cable.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Your Bootloader
Backup your data and Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Build Number. Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect your phone to your computer via USB cable.
Open a Command Prompt on your computer.
Type the following at the prompt and press enter:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to make your selection.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll be greeted with a warning that says Your device software can't be checked for corruption. Please lock the bootloader everytime you reboot. It's ok, as long as your bootloader is unlocked it will stay there.
Important: do not repeat do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see 9 of this guide for instructions on how to return to stock and lock the boot loader.
Install Factory Image and wipe data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install Factory Image and keep data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Edit flash-all.bat: Remove -w
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install A Custom Recovery and Root with SuperSU
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Backup your data and Internal storage
Download files:
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone.
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release to your phone.
Copy the following file to the platform-tools folder: twrp-3.0.2-0-RC1-fastboot-marlin.img rename it twrp.img
Boot Bootloader
Connect device/phone to computer
Open a Command Prompt on your computer.
Type the following at the Prompt.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
Tap Add more ZIPs button, select SuperSU-v2.82-201705271822.zip
Swipe the slider to install.
Reboot system
Install A Custom Recovery and Root with Magisk (Clean Install)
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Note:[Substratum] theme Spectrum does not work with Magisk root.
Backup your data and Internal storage
Download the following files:
ElementalX-P-1.14.zip for Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img
twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Magisk-v13.3-Pixel-b4.zip
MagiskManager-5_1_1.apk
Magisk-uninstaller-20170720.zip
Flash Boot.img - If you have TWRP, SuperSU, or a custom kernel installed.
Extract the contents of your factory image and open the folder it creates. From there, extract the second archive (image-marlin-aaa99a.zip)
Then open that folder and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the phone to your computer
Open a Command Prompt on your computer.
Type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
When it finishes, leave the command prompt window open, your phone in bootloader mode and connected to your computer.
Install TWRP
Place twrp-3.0.2-0-RC1-fastboot-marlin.img in your platform-tools folder and Rename it twrp.img
Type the following command at the prompt:
Code:
fastboot boot twrp.img
When TWRP boots, tap the Install button and select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe the slider to install
Press the back button until you are on TWRP's main menu select Reboot > Recovery.
Flash the ZIPs
Disconnect your phone from your Computer.
Tap the Install button, then navigate to the files you downloaded.
Select the Magisk Uninstaller.zip, tap the Add more ZIPs button.
Select the twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install
Reboot Recovery
Tap the Install button select a Custom Kernel: ElementalX-P-1.1x.zip or Franco's Kernel-r1x.zip.
Tap Add more ZIPs button select Magisk-v13.3-Pixel-b4.zip, tap the Add more ZIPs button and select: twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe to install
Note: During the Installation of ElementalX, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and press Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and Finish. After, the other ZIPs are installed.
Reboot System
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Install MagiskManager
Install Magisk Manager (5.1.1.apk)
Wipe data on Magisk Manager
Enable Magisk Hide
Enable Core Only Mode
Toggle on and off systemless hosts
Reboot system
Check for Latest Version, Root, and Saftey Net.
Update Magisk Dirty Flash
Download file:
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip
Flash the ZIPs
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip, tap the Add more ZIPs button.
Select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install.
Reboot system
Check for Latest Version, Root, and Saftey Net.
Custom ROMs for Pixel/Pixel XL
[ROM][Pixel-XL][7.1.2_r24]★ Pure Nexus ★ Substratum | Fi | WiFi Calling ★[07/25/17] by BeansTown106
[ROM][Pixel-XL][7.1.2_r33][OMS] Pixel Dust for marlin [FINAL][2017/08/22] by spezi77
[ROM][Resurrection Remix v5.8.3][Android Nougat 7.1.2][OMS][07/24/17] by BDogg718
[ROM][UNOFFICIAL] LineageOS 14.1 Nightlies for the Google Pixel (marlin/sailfish) by invisiblek
Paranoid Android 7.2.1 - AOSPA - Pixel XL by freak_97
ROM][7/21/17][Marlin][7.1.2][WEEKLY]Team OctOs Oct-N by cjkacz
SCREW'D ROM
Install Custom Kernel
Franco's Kernel - SuperSu
Download file:
The latest Franco's kernel for Pixel/Pixel XL
Boot into TWRP
Press Install button select the file you downloaded
Swipe slider to install
Reboot System
ElementalX-PXL-1.xx by flar2 Kernel - SuperSU
Download files:
ElementalX kernel
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release
Flash ElementalX zip in TWRP recovery (do not flash SuperSU-v2.82-201705271822.zip again if you're already rooted).
During the Installation, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and tap Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and then Finish.
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Franco's Kernel or ElementalX-PXL-1.xx by flar2 Kernel - Magisk
See [Unofficial] Google Pixel family support by goodwin_c for Installation Instructions.
Install Substratum Theme
SuperSU Root
Install Substratum Theme Engine from the play store.
Install [Substratum] Spectrum theme from the play store. Note: I used Substratum theme Spectrum to test the installation of Substratum with SuperSU root..
Magisk Root
Researching Information
Return to Stock and Lock Bootloader
Return to Stock
Backup your data and Internal storage
Download the appropriate factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the platform-tools folder on your Computer
flash-all.bat
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following command at the prompt.
Code:
flash-all
Lock Bootloader
Phone
Boot Bootloader
Connect your phone to your Computer with USB cable.
Computer
Open a Command Prompt on your computer.
Type the following at the prompt:
Code:
fastboot flashing lock
When it finishes the bootloader is locked.
The next step won't be needed if your Pixel XL reboots into system after bootloader relock.
You need to boot into system now, either press Power button to reboot OR issue the following command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Audio Mod
Weta Audio Mod
we already have guides though
flex360 said:
we already have guides though
Click to expand...
Click to collapse
can't hurt to have an updated guide for those too lazy to read.. so many posts about "this guide is out of date" or "i dont have time to read 6 pages about other people's experiences"
Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.
jrhatfield said:
Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.
Click to expand...
Click to collapse
It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.
JimSmith94 said:
It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.
Click to expand...
Click to collapse
I'll research it and make changes if needed.
Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.
iamjimmy said:
Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
¯\_(ツ)_/¯
About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?
Avasta said:
About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?
Click to expand...
Click to collapse
2. Install Factory Image and wipe Data
Code:
fastboot -w update image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
fastboot update image-marlin-aaa99a.zip
Homeboy76 said:
2. Install Factory Image and wipe Data
Code:
update -w image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
update image-marlin-aaa99a.zip
Click to expand...
Click to collapse
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.
Avasta said:
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.
Click to expand...
Click to collapse
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?
Homeboy76 said:
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?
Click to expand...
Click to collapse
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
When you flash a factory image, flash it in both slots.
Flash all once
Boot into the bootloader again
Swap slots in bootloader
Flash all again
(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)
pcriz said:
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.
Click to expand...
Click to collapse
Ok.
parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
If you follow the instructions above you should not have to worry about slot a/b. The firmware will put it in the correct slot.
If you are installing Custom ROM this thread is not for you. You, should follow the installation instructions of the Custom ROM you want to install.
parano666 said:
(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)
Click to expand...
Click to collapse
You're welcome!
I wanted to create a guide which is as simple as rooting a OnePlus 3T. I don’t know if it will work with the OnePlus 3. I’m not responsible for anything. You’re doing it on your own risk, so only do it if you know what you will do, now! It may brick your device.
This is the way it worked for me. I do not guarantee it will work for you!
READ THE WHOLE INSTRUCTIONS FIRST BEFORE YOU DO ANYTHING
What we do:
- Flash TWRP
- Flash an old version of OOS
- Enable dm verity
- Relock the bootloader
- Flash the latest stock rom
What you need:
- Computer (Windows 7 or 10)
- USB Cable
- about 1 hour of your lifetime
YOU WILL LOOSE ALL YOUR DATA - ALSO THE INTERNAL STORAGE WILL BE DELETED (pics, music and all the stuff stored there)
Download to your computer:
Latest TWRP for OnePlus 3T
https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
and
latest OOS from OnePlus for your 3T
http://downloads.oneplus.net/
THE USB DRIVERS MUST BE INSTALLED ON YOUR COMPUTER
Download to the phone:
4.0.2 OOS Stock rom (post #2)
https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
Flash TWRP:
1. Start your phone in fastboot mode (don’t connect to your PC yet!)
2. Open CMD as Admin (Windows start-menu - type “cmd”, right-click, run as administrator)
3. connect your phone
4. rename the file to “recovery” (don’t type “recovery.img” manually, only “recovery”)
5. type command “fastboot devices” -> device will be listed
6. command “fastboot flash recovery C:\Users\...\recovery.img” (the path where it’s stored)
7. done -> boot to recovery
8. disconnect your phone - leave CMD open
Flash OOS 4.0.2
1. Go into TWRP
2. wipe “System, Data, Cache, Dalvik”
3. Install OOS 4.0.2
4. reboot into fastboot
Enable dm-verity:
1. connect your 3T when it’s back in fastboot
2. type in CMD “enable dm-verity”
3. done - keep CMD open and the phone connected
Relock the bootloader:
1. type in CMD “fastboot OEM lock”
2. Warning message on your phone will pop up -> choose “yes” on your phone by using the volume buttons to lock the bootloader (keep CMD open)
Update to the newest OOS via “sideload”:
1. VOL down to boot into recovery
2. choose “Install from ADB”
3. “Upgrade Android from USB?” -> “Ok”
4. rename the OOS zip file to "update"
5. type in CMD “adb sideload C:\Users\...update.zip”
6. done
7. reboot the device - it will take about 10 minutes, DO NOT INTERRUPT THE PROCESS
Finish
Take your time! Don't do it if you're in a rush.
Please give me feedback if it worked for you or if I have to change something.
enable dm-verity doesnt work
"enable is not recognised..."
chowchillacharlie said:
enable dm-verity doesnt work
"enable is not recognised..."
Click to expand...
Click to collapse
Did you check if the device is listed in fastboot?
You can also try the command "disable" and then "enable"
Sometimes you may need to do it first, even if it's disabled
Thanks for your threat. I tried this but had to do a couple things differently.
I think enabling/disabling dm-verity works only with old firmware.
What I used:
* 4.0.2 firmware from this threat https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
* latest oneplus recovery and rom https://downloads.oneplus.com/
* the recovery can be downloaded from a link on the bottom of the rom download site.
I started with twrp and a custom rom.
You need usb debuging enabled and adb and fastboot installed
What I did:
* I did a Nandroid backup, and copied the sdcards content to my computer, because the following completely wiped my phone
"adb pull /sdcard /path/to/my/drive/"
* flash 4.0.2 firmware, with trp
enter adb sideload mode in twrp and
"adb sideload firmware.zip"
* fastboot flash oneplus recovery
"fastboot flash recovery recovery.img"
* using onplus recovery and sideloading installed latest oneplus rom
enter adb sideload and
"adb sideload oneplusrom.zip"
* did a factory reset in oneplus recovery and cheked if my phone would boot
* entered fastboot mode
"fastboot oem disable_dm_verity", then "fastboot oem enable_dm_verity"
"fastboot oem lock"
after that my phone got wiped again, and the next boot took a long time
Then the phone was completely stock
Wanted to post to say thanks to roor7 and WhataHulk - had a rooted 3T I wanted to sell following an upgrade (best price requires the phone to have no sign of root!), and this was the only method that worked for me to enable dm-verity.
As a quick note, I followed roor7's guide, but got the same error message as chowchillacharlie. After sme playing about I found the simplest soultion was using the CMD line provided towards the end of WhataHulk's guide, i.e. - "fastboot oem disable_dm_verity", then "fastboot oem enable_dm_verity". For me, roor7's guide swapping the type "enable dm-verity" in CMD with "fastboot oem enable_dm_verity" worked a treat.
Sorry if that is all incredibly obvious to most people!
Thanks again gents.
Hi, folks, how you doing?
Today, I'm gonna help you to update your MIUI without losing your installed apps and stuff.
First of all, you have to download the MIUI rom image here. Choose wisely, because there's just one version compatible with MI A2 and it is called MI 6X - WAYNE.
----------------------------------------------------------------
A few things before you get into this:
[!]This process worked to me and can work to you, however, I can not give any garantee of how you will understand it, so, if you follow these steps, do it at your own risk.
[!]You must have USB debugging enabled, an unlocked bootloader, a converted MI A2 to MI 6X andTWRP recovery installed.
[!]CAMERA2API: If you have had edited build.prop and renamed wayne.xml to whyred.xml, you'll have to do it again. I recommend this guide.
Requirements:
1) TWRP Wayne
2) ADB
3) MI 6X Wayne rom
4) USB Debugging, unlocked bootloader enabled in Developer options
5) Platform-tools
6) Compatible USB Cable
----------------------------------------------------------------
A few explanations:
The update process has two methods: one is known as "clean update". On clean update, all data in your phone will be wiped on the process and the update will give you a fresh clean device.
The other one process is known as "dirty update". On this process, only the OS files will be replaced, keeping all that garbage (apps, pictures, music, videos, cache, etc) we love in our phones.
Today, I'll teach you how to do a dirty update.
----------------------------------------------------------------
From here, I'll assume you already have ADB installed and working in your computer and TWRP boot image placed in ADB Folder.
1) Download MIUI rom and place it in your phone's internal memory
2) Restart your phone with Power button + Volume down until you see the Fastboot bunny
3) Connect your phone in your computer using the provided USB cable
4) In your computer (Windows), open file manager in ADB folder, hold SHIFT key and right click mouse and select "Open Command prompt here"
5) In Command Prompt, type
Code:
fastboot devices
and Enter - you shall see your devices ID
6) Type
Code:
fastboot boot twrp-[version here]-wayne.img
and Enter, your phone your will restart and load TWRP Recovery.
7) In TWRP, tap "Install", it will open file manager to you choose the desired file. Select it it and slide "swipe to confirm flash".
8) The installation process will start. Take a coffee because it may take a while.
9) In the end of the update process, tap "wipe Dalvik/Cache".
10) Tap "Restart".
Your phone will restart. The first boot is a little longer than the normal (+-3 minutes), but it is normal.
will it break magisk?
Guide to install Lineage OS 16.0 with root, recovery and unlocked bootloader on Lenovo Vibe K5 A6020I36 by lexiyuri
0. Download and uncompress all the essential included files (TWRP recovery, minimal adb and fastboot, lenovo drivers) included in my androidifilehost link:
https://androidfilehost.com/?w=files&flid=303569
Download the Lineage OS 16 from here (thanks to harry8242):
https://androidfilehost.com/?w=files&flid=282516
dont forget to choose latest Lineage OS 16 compilation
Download the Gapps from
https://opengapps.org/
(choose Android 9.0, arm64 and stock options)
Download the latest SuperSU version (flashable zip package) from here:
http://supersuroot.org/downloads/SuperSU-v2.82-201705271822.zip
Important: dont forget to copy the Gapps, supersu and ROM inside a micro sd card before start!!
1. Make a entire backup of your device, syncing Google and WhatsApp accounts before doing something.
Remember: you are going to erase your Stock Lollipop version in your k5!!
2. Install the inclued Lenovo Drivers
from the folder named latest_usb_driver_windows_2
and the drivers in the executable file named LenovoUsbDriver_autorun_1.1.15_user.exe
For Windows xp to 8.1: proceed to follow on screen instructions
Note for Windows 10 users: this OS enforces driver signatures by default. This can be disabled to install drivers that are not digitally signed. Use the following steps to disable driver signature enforcement in Windows 10.
Click the Start Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement. Your computer will restart and you will be able to install non-digitally signed Lenovo drivers.
3. Install Minimal ADB and Fastboot: double click on the adb setup file included and follow on screen instructions
Alternatively you can download Minimal ADB tool from https://androidmtk.com/download-minimal-adb-and-fastboot-tool or choose the included in compressed
Also you can install Android Studio SDK from its official source in order to use the ADB and fastboot tools
https://developer.android.com/studio/?gclid=EAIaIQobChMIpdiIlpfh5QIVks13Ch2bUw8REAAYASAAEgJW9PD_BwE
4. To ease things, copy the Recovery file (twrp3230.img) into Minimal ADB Program files folder (check before if your program files folder are 32 or 64 bits).
5. Unlock bootloader for lenovo Vibe k5
Enable the Developer Options. To enable the Developer Options, go to settings => About => Software Information => More => Tap on the Build Number around 7-8 times until you see a message telling you "developer options enabled"
Go back to settings and now enable the OEM Unlock by going to Settings => Developer Options and tap "Enable/allow OEM Unlock" and after tap in the "Enable/ Allow usb debugging" option.
I want to clarify in this point: Lenovo doesn't offer an official way to unlock bootloader. Now, connect your phone to the PC.
In your Minimal ADB fastboot program files folder open a command prompt (cmd window) by pressing Shift Key + Right Mouse Click, now type the following command line in your command window
Code:
adb devices
(This is to verify your device is being recognized and shows a code or identifier)
Note: if you see a pop up to allow USB Debugging on your phone, Click OK
After that, type the following command below to reboot your phone to bootloader
Code:
adb reboot bootloader
Your phone will reboot into bootloader and enter to the fastboot at the same time.
Fastboot screen shows green lenovo logo, a white background and a tiny message saying if you press longer the on/off button you will restart the phone.
Please, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers are installed properly.
Code:
fastboot devices
(This command will list the connected devices. If your phone serial number shows up you can continue, but if the phone is not listed, your drivers are not installed correctly. Fix that issue and then continue.
Now, unlock the bootloader with this command line
Code:
fastboot oem unlock
Important: this command returns an error code saying that remote oem is not allowed, just like the following one
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.002s
For some reason I did all the entire process without problems. May be Lenovo Vibe K5 is unlocked by default, so, it doesn't matter if the message says you can't do the unlocking. Continue to the Step 6
6. Install the TWRP recovery 3.2.3-0
Type the following command in order to install the recovery and press enter
Code:
fastboot flash recovery twrp3230.img
(this line installs the twrp permanently)
Optional: you can just run the recovery temporarly using this line
Code:
fastboot boot twrp3230.img
The fastboot boot command line lets you inside the twrp recovery mode window. Also, you can enter to the recovery mode pulling out the battery, pressing vol +, vol - and power all that at the same time.
7. Installing Lineage OS 16.0 -Android Pie 9.0-, Gapps and SuperSu (make root) flashable packages.
First then all, make the reglamentary wipes (one by one) without restart/reboot the phone
Code:
wipe system (this will erase the Stock Lollipop)
wipe data (this will erase pictures, WhatsApp folder, Download folder, data apps, wifi passwords, configurations and so on)
wipe cache
wipe dalvik / art cache
In the main twrp window, tap the Install option, locate your microSD tapping in the select storage to activate the external SD.
Now search the files into the SD, pressing in the "up a level" zone and after you reach it, install the following things in the exact order:
Choose the Lineage OS 16 Rom zip file (swipe to confirm) and wait. Dont restart the phone.
After that, choose the Gapps zip file, swipe again to confirm and wait.
Finally, choose the SuperSu zip file you downloaded, do a swipe, wait.
If you want, its possible install all the zip files as a bunch using the "add more zip option" that twrp offers to you, but I prefer do it each one by one.
8. Do a final wipe choosing "wipe Dalvik and Cache".
9. Now choose the restart/reboot option. Wait for the phone initial setup (around a couple of minutes)
10. Configure the phone with your android account preferences. install your favorite apps, sync your info, etc.
Important: during the configuration, the Pixel launcher can fail. So, choose trebuchet as the default launcher.
11. Configure the SuperSU, install it, and verify the root with the Root checker app (you can found it in the Play store) and you are done!! Enjoy!!
== Special tip to enable the TWRP recovery option in the on/off/restart menu===
12. Once you have finished the set-up in your phone enable the Developer options into Lineage OS following this route:
tap in the drawer little configuation wheel ==> System ==> about phone, go to the last option and tap around 7-8 times in the Rom compilation number until you receive the toast message telling you "developer options enabled".
Return to the main system screen options, tap in System, then tap in advanced, and finally tap in the developer or programmer options, activate them and enable Advanced Power/reboot Menu
13. Finally, hold power button, choose restart, then you will see all restart options including the restart to the recovery .
READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down) Recommended to use Command Prompt commands instead of powershell (type cmd in platform-tools directory) https://developer.android.com/studio/releases/platform-tools
Unlock oem bootloader
Enable developer options (click build number several times)(make sure you’re connected to internet)
Enable oem unlocking, advanced reboot, usb debugging
Reboot to bootloader/fastboot
fastboot oem unlock
Unlock bootloader
Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding volume down while
booting)
Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
fastboot flash boot (path to boot.img)
fastboot flash dtbo (path to dtbo.img)
fastboot flash recovery (path to recovery.img)
Download firmware (https://kremowka.xyz/files/8fw/)
Enter recovery mode, enter fastbootd
Advanced > enter fastboot
Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload
LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in
there somewhere
Open notepad, copy commands from lineage, save as (file name).bat, drag into powershell from file explorer
(flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
adb devices (to confirm phone is connected properly and device drivers are configured properly)
adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are
too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
Reboot recovery?
adb sideload (path to copy partitions .zip)
Back > Reboot system now
It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have
data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done
that before this step (do it in fastboot, search up adb shell pull)
If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something
happened.
OPTIONAL (if you want magisk/root)
Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
Search in settings for “advanced”, click “advanced restart” and enable
Hold power button, restart, recovery
Apply update > apply from adb
adb devices
adb sideload (path to magisk .apk)
Signature verification failed, install anyway
Volume up to go to back arrow, reboot system now
Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file
transfer is on
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
What I use: Safetynet universal fix and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
Install from storage
Order I did it in was safetynet then raven, rebooting between each one but I'm not sure if it matters
Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click
google play services, google play store, and carrier services (the square check box next to the name, make sure
every check below when you open it as a dropdown menu is checked
Reboot phone
Now you can download whatever you want
If you install twrp, make sure you are using android 12 version and not android 11, android 11 twrp will destroy
your recovery if you try to use it on android 12.
Add on: If your phone is not detected by your pc, or is detected as “MTP” with an exclamation mark, you do not
have the right drivers. There are plenty of resources online to fix this, but one that I had trouble with was that I
was on windows 10 N instead of whatever the other version is, which doesn’t come with “mediafeaturepack.”
You need to install that on your own from https://www.microsoft.com/en-us/software
download/mediafeaturepack, or, if your device isn’t listed, go to windows application “optional features” and
add it from there.
If your computer won’t download qdloader 9008 qualcomm drivers through device manager, there are a few
things i’ve tried to fix it. Make sure you have correct drivers
from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
“The system cannot find the file specified”
Open command prompt as administrator
Type DISM /Online /Add-Package /PackagePath:"Full path of .cab file"
I put mine in C: drive folder but I'm not sure it matters
Also I'm not sure which one of the three I downloaded from the website. Did not cause any issue downloading
and trying to install all three, let me know if you figure out which one works. Maybe you need all three, I don’t
know.
If that doesn’t work, do sfc /scannow
Open windows update, make sure all updates are applied and restart windows (make sure you go to optional
updates and select qualcomm drivers)
Fastboot won’t connect
Make sure you’re using a usb 2.0 port instead of a usb 3.0 port, and make sure your usb cable is a data cable.
Google the difference if you don’t know what it is. Download usb drivers
from https://developer.android.com/studio/run/win-usb, open device manager, see if anything is there, if it
shows something in “other devices” click on it, click update drivers, browse my computer, let me pick, have disk,
and then browse to android_winusb.inf and click update, click bootloader interface. If you get “error 10 device
won’t start” when installing bootloader interface, one possible solution is to disable driver signing.
Open command prompt as an administrator (doesn’t have to be in platform tools directory)
bcedit /set testsigning on
Reboot, try to install driver again.
If your device is bootlooping, and you enter fastboot after updating to a12 firmware AND you have magisk\
modules downloaded AND you have twrp installed, do not press the up volume button, only cycle through
options with volume down, because it may enter an option cycle and you won’t be able to do anything unless
you fastboot flash boot twrp.img.
It’s recommended that as soon as you root, you backup persist.img, which contains imei info (you don’t want
that to get destroyed) I am unsure if there’s anything else device specific you need to backup, I've heard
vendor_image may be but it’d not as important as persist.
To backup persist.img, put phone in recovery, type in command prompt or powershell
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
This should save persist.img to your computer. Back it up somewhere you keep important things. Also don’t
give it out at random as it contains your imei number, not sure what the consequences of that could be but
nothing good is likely to come of it.
Important shortcuts:
Power + vol up – boot into system
Power + vol down – boot into fastboot
Power + vol up + vol down – boot into edl
IF DEVICE IS BOOTLOOPING AND YOU CAN’T ENTER ANY DIFFERENT MODES, CONTINUE HOLDING POWER +
VOL DOWN IN RANDOM PATTERNS. IT HAS TAKEN ME 20 MINUTES OF RANDOM BUTTON COMBINATIONS TO
GET INTO FASTBOOT FROM A BOOTLOOP. YOU WILL ALWAYS BE ABLE TO EXIT A BOOTLOOP IF YOUR PHONE
IS PHYSICALLY UNDAMAGED.
If VoWifi doesn’t work, pixelify dialer can get it working. Probably also just any custom dialer, but I like Google
dialer. Wait for the interface to change slightly, don’t clear data until you’ve waited at least a minute or two and
closed and reopened it a few times, but if it doesn’t change after installing pixelify then force close, clear data,
and wait a minute or two, reopen, and then wait. If it continuously doesn’t change you can reflash pixelify.
Note – If using pixelify module, disable auto update for android system intelligence, it will break gboard
translate and possibly slow down device.
You can also use magisk module “mindetach” to detach com.google.android.as from play store, which will fix
any auto update bugs. Credit to vewu for showing me that
https://github.com/j-hc/mindetach-magisk
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community.
Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for formatting, this is copied from a word doc. Please feel free to indent and number list yourself and
send me a better version
Does the third option work?
INTseed said:
Does the third option work?
Click to expand...
Click to collapse
did you configure the denylist? try clearing cache and data for google play services, google play store, and carrier services and rebooting
Mrmcfeffers said:
READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down)
a. Unlock oem bootloader
i. Enable developer options (click build number several times)(make sure you’re connected to internet)
ii. Enable oem unlocking, advanced reboot, usb debugging
iii. Reboot to bootloader/fastboot
iv. .\fastboot oem unlock
v. Unlock bootloader
b. Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding
volume down while booting)
2. Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
a. .\fastboot flash boot (path to boot.img)
b. .\fastboot flash dtbo (path to dtbo.img)
c. .\fastboot flash recovery (path to recovery.img)
3. Download firmware (https://kremowka.xyz/files/8fw/)
4. Enter recovery mode, enter fastbootd
a. Advanced > enter fastboot
5. Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in there somewhere
a. Open notepad, copy commands from lineage, add .\ before each line, save as (file name).bat, drag into powershell from file explorer (flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
b. Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
c. Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
i. .\adb devices (to confirm phone is connected properly and device drivers are configured properly)
ii. .\adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
d. Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
i. .\adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
e. Reboot recovery?
i. .\adb sideload (path to copy partitions .zip)
6. Back > Reboot system now
a. It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done that before this step (do it in fastboot, search up adb shell pull)
7. If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something happened.
8. OPTIONAL (if you want magisk/root)
9. Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
a. Search in settings for “advanced”, click “advanced restart” and enable
b. Hold power button, restart, recovery
10. Apply update > apply from adb
a. .\adb devices
b. .\adb sideload (path to magisk .apk)
i. Signature verification failed, install anyway
ii. Volume up to go to back arrow, reboot system now
11. Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
a. Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file transfer is on
12. DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
a. What I use: Safetynet universal fix, disableflagsecure (lets you screenshot netflix lol), and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
i. Install from storage
ii. Order I did it in was safetynet, then raven, then flag secure rebooting between each one but I'm not sure if it matters
b. Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click google play services, google play store, and carrier services (the square check box next to the name, make sure every check below when you open it as a dropdown menu is checked
c. Reboot phone
13. Now you can download whatever you want
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
https://forum.xda-developers.com/t/disable-flag-secure-magisk-module-v3-0-by-mehedi-hjoy.4490475/
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community. Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for the ****ty formatting, i copied this from a word document. I don't know how to paste the indents.
Click to expand...
Click to collapse
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.
optimumpro said:
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.
Click to expand...
Click to collapse
modded msm tool allows bootloader unlocking
Mrmcfeffers said:
modded msm tool allows bootloader unlocking
Click to expand...
Click to collapse
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.
optimumpro said:
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.
Click to expand...
Click to collapse
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.
Mrmcfeffers said:
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.
Click to expand...
Click to collapse
It's just a decription in thread name that is a bit misleading.
At first it appears like it can be done on locked bootloader.
And it's obviously not, as stated in your instruction point #2.
Otherwise, nice tutorial.
Mrmcfeffers said:
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
Click to expand...
Click to collapse
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?
jinncarry said:
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?
Click to expand...
Click to collapse
Don't use acca from f-droid. Acc from the official GitHub (https://github.com/VR-25/acc) is fine and works perfectly