Related
Follow the Instructions
1. Download OOS 4.0.2.Zip and OOS 4.1.0.zip
OOS 4.1.0
https://drive.google.com/open?id=0Bzko1towAti5WW1rUThrb3lHUWs
OOS 4.0.2
https://drive.google.com/open?id=0Bzko1towAti5NGVsTUtfd2VUY2M
2. Copy both files inside device internal memory
3. Unlock Bootloader and Flash latest TWRP
https://dl.twrp.me/oneplus3t/
4. Reboot into recovery and wipe-advance wipe
caech, data, system (without internal storage)
5. Flash Rom OOS 4.0.2.zip first and reboot device
6. Flash stock recovery using cmd prompt & fastboot
7. Reboot Fastboot mode and enter this commands
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
8. After success and finished
9. Go-to stock recovery without reboot
10. Flash Rom OOS 4.1.0.zip from stock recovery
11. Reboot device
12. lock Bootloader using fastboot
13. Reboot into stock recovery again
14. Reset and wipe everything from stock recovery
15. That's all now you feel free from dm-verity warning
and your device fully official.
Moderator Information.
Thread closed, we have a thread already here: [FIX][OP3/OP3T] DM-Verity warning fix. Works on 4.1.0!!
Hello Friends,
I have seen several Youtube videos and read the thread of xda senior member the rooter to unroot and revert the oneplus 3t to stock. The senior member guided very beautifully to have the stock ROM with or without the bootloader unlocked and fix DM-verity issue.
The following guide is not my invention, I have taken the sources from internet and xda site. The difference is that I used TWRP to flash official oxygenOS zip file of 4.1.6 and I am surprised that this file also flash stock recovery, therefore I did not flash stock recovery and proceeded further for full wipe and lock bootloader. In the middle of thread, I also alerted and said that if stock recovery is not flashed after installing zip of 4.1.6, then it is mandatory to flash stock recovery from fastboot before locking bootloader, otherwise your devices will be bricked.
1) Flash Oxygen OS 4.1.6 through latest TWRP 3.1.1.2 and remember to wipe system, cache, data and delvic cache excluding internal storage before flashing. Do not wipe completely otherwise you will have TWRP installed again and you will have to flash stock recovery through fastboot method.
Link for official TWRP for oneplus 3t: https://dl.twrp.me/oneplus3t/twrp-3.1.1-2-oneplus3t.img.html
Link for official stock recovery for oneplus 3t: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/ , here go down the page and click on "Download Oxygen Recovey (Optional)"
After booting successfully, go to setting and tap the build number 7 times to enable advanced reboot and usb debugging and connect your mobile with your PC and make sure that you have adb drivers installed on your PC.
Now, extract the folder of fastboot and press the right click of mouse while pressing shift button. Basically you have to open command prompts. Now type: adb reboot recovery and hit enter.
2) Your phone should boot into oxygen stock recovery and if it does not boot to stock recovery then flash stock recovery from fastboot.
2) Now your oneplus 3t is having Oxygen OS 4.1.6 with stock recovery but having DM verity issue. Now, full wipe ( select erase everything) in stock recovery and reboot. This wiping through stock recovery may be extra step (locking the bootloader will erase your data completely) but I did this to avoid any problem.
3) Now, sideloaded the same file i.e. oxygen OS 4.1.6 or OOS 4.1.7 through the following command:
adb sideload OTA.zip
where OTA is zip file downloaded from oneplus site for oneplus 3t and renamed it as OTA
(For this, you will have to go to stock recovery and select the option of "install from ADB" then a pop up screen will show you that you are in sideload mode. But remember that sideloading the OS is a slow process; so keep patience and do not remove cable in the middle of installation otherwise your device will be bricked.)
4) Now, lock the bootloader from the command in fastboot mode:
fastboot oem lock
after entering the command in fastboot mode, a confirmation will be asked to lock the bootloader for Yes or No, confirm from the volume keys and let boot the phone automatically and wait to finish.
5) If you sideloaded the OOS 4.1.6 in step 3 then you will see the update notification of OOS 4.1.7 which is about 450MB, download it ,install it and reboot.
6) Enjoy............the stock
Thanks to guides on youtubes and xda site.
Please note that if you follow these steps, you will not have any issues because I have done again and again without any issues but I do not take any responsibility of bricked devices if you perform wrong method or skip any thing.
Please hit the like if find this useful, it is absolutely freeeeee.............
What if I currently have no OS installed? Does that matter?
sandeep_kumar said:
Hello Friends,
I have seen several Youtube videos and read the thread of xda senior member the rooter to unroot and revert the oneplus 3t to stock. The senior member guided very beautifully to have the stock ROM with or without the bootloader unlocked and fix DM-verity issue.
The following guide is not my invention, I have taken the sources from internet and xda site. The difference is that I used TWRP to flash official oxygenOS zip file of 4.1.6 and I am surprised that this file also flash stock recovery, therefore I did not flash stock recovery and proceeded further for full wipe and lock bootloader. In the middle of thread, I also alerted and said that if stock recovery is not flashed after installing zip of 4.1.6, then it is mandatory to flash stock recovery from fastboot before locking bootloader, otherwise your devices will be bricked.
1) Flash Oxygen OS 4.1.6 through latest TWRP 3.1.1.2 and remember to wipe system, cache, data and delvic cache excluding internal storage before flashing. Do not wipe completely otherwise you will have TWRP installed again and you will have to flash stock recovery through fastboot method.
Link for official TWRP for oneplus 3t: https://dl.twrp.me/oneplus3t/twrp-3.1.1-2-oneplus3t.img.html
Link for official stock recovery for oneplus 3t: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/ , here go down the page and click on "Download Oxygen Recovey (Optional)"
After booting successfully, go to setting and tap the build number 7 times to enable advanced reboot and usb debugging and connect your mobile with your PC and make sure that you have adb drivers installed on your PC.
Now, extract the folder of fastboot and press the right click of mouse while pressing shift button. Basically you have to open command prompts. Now type: adb reboot recovery and hit enter.
2) Your phone should boot into oxygen stock recovery and if it does not boot to stock recovery then flash stock recovery from fastboot.
2) Now your oneplus 3t is having Oxygen OS 4.1.6 with stock recovery but having DM verity issue. Now, full wipe ( select erase everything) in stock recovery and reboot. This wiping through stock recovery may be extra step (locking the bootloader will erase your data completely) but I did this to avoid any problem.
3) Now, sideloaded the same file i.e. oxygen OS 4.1.6 or OOS 4.1.7 through the following command:
adb sideload OTA.zip
where OTA is zip file downloaded from oneplus site for oneplus 3t and renamed it as OTA
(For this, you will have to go to stock recovery and select the option of "install from ADB" then a pop up screen will show you that you are in sideload mode. But remember that sideloading the OS is a slow process; so keep patience and do not remove cable in the middle of installation otherwise your device will be bricked.)
4) Now, lock the bootloader from the command in fastboot mode:
fastboot oem lock
after entering the command in fastboot mode, a confirmation will be asked to lock the bootloader for Yes or No, confirm from the volume keys and let boot the phone automatically and wait to finish.
5) If you sideloaded the OOS 4.1.6 in step 3 then you will see the update notification of OOS 4.1.7 which is about 450MB, download it ,install it and reboot.
6) Enjoy............the stock
Thanks to guides on youtubes and xda site.
Please note that if you follow these steps, you will not have any issues because I have done again and again without any issues but I do not take any responsibility of bricked devices if you perform wrong method or skip any thing.
Please hit the like if find this useful, it is absolutely freeeeee.............
Click to expand...
Click to collapse
How can i find one plus 3t recovery I cant find both twrp and one plus official recovery.
[Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + July 2018 Security Patch​
Intro
This Guide 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 XL'.
This Guide also works for the Pixel owners: If, they download the correct files for their phone.
This Guide is not for use with the Second Generation Pixel 2 or Pixel 2 XL devices.
Update(s):
Custom ROM - crDroid v4.7
Note: Some Custom ROM's have the latest Security Patch.
Install Custom Kernel: - See #7, or #8
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 unlocked bootloader. ([How-to] Unlock bootloader on Verizon Pixel/XL by burduli - The unlock method was discovered by: Qu3ntin0) , and the latest Android 8.1.0 (Oreo) Factory Image: "marlin" for Pixel XL
marlin-opm4.171019.021.p1-factory-d5fc023e.zip
marlin-ota-opm4.171019.021.p1-f0709550.zip
Note: If you want the latest OTA or Binaries. Tap the Menu icon (upper left corner) then tap Full OTA Images or Driver Binaries
Computer - With the latest SDK Platform-Tools installed.
Important: Update Platform Tools, regularly, for optimal performance.
Need help installing or using SDK Platform tools: Easiest-way-to-install-androids-adb-and-fastboot
Other
Pixel XL Guides: Android 9.0.0 (Pie), Android 8.0.0 (Oreo), Android 7.1.2 (Nougat)
Pixel 3 XL Guide: Android 9.0.0 (Pie)
Credits/Thanks/Recognitions
Heisenberg RETIRED FORUM MODERATOR - He set the standard for creating, detailed, Guides.
Those I may have, inadvertently, forgotten.
Index
Open a 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 the 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. 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. Use volume up/down button until you see Recovery mode. Press power button.
Test 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 to test ADB.
Code:
adb version
It should return a version number for ADB.
Note: If it does not return a version number type
Code:
adb reboot bootloader
and try
Code:
adb devices
again.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Note: If it does not return a version number type
Code:
adb reboot bootloader
and try
Code:
fastboot devices
again.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Backup your data and Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type
Code:
fastboot flashing unlock
and press enter.
This will erase all user data from the device!
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type
Code:
fastboot reboot
at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll see a warning: Your device software can't be checked for corruption. Please lock the bootloader. You will see this warning until, you relock the bootloader.
Important: Do not relock your bootloader until you have returned the device to Stock..
Return Phone to Stock
Backup your data and Internal storage
Download the latest Factory Image
Extract factory Image to the platform-tools folder, or the folder that has fastboot in it.
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: This will erase all your Data and Internal Storage
Boot bootloader
Connect your phone to your Computer with a USB cable.
Open a Command Prompt:
Flash the Stock Factory Image on Both Slots
Type this at the Command Prompt:
Code:
flash-all
Let the phone boot.
Boot bootloader
Open Command Prompt:
Switch to the other slot.
Type this at the Command Prompt:
Code:
fastboot --set-active=other
Then type this at the Command Prompt:
Code:
flash-all
Let the phone boot.
Lock Bootloader
'B' must be completed before performing this step!
Boot bootloader
Open a Command Prompt and type this at the Prompt:
Code:
fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt:
Code:
fastboot reboot
Set up your phone.
Enable Developer Options: Settings > System > About phone > Tap Build number 7 times.
Tap Back > Developer options and toggle OEM unlocking to off.
Install Factory Image keep or wipe data
Important: When doing a major upgrade i.e., Android 7.x.x to Android 8.0.0/Android 8.1.0. I recommend wiping data.
Backup your data and Internal storage
Download the appropriate Factory Image: "marlin" for Pixel XL to your Computer.
Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file to remove -w from this command: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: If you do not remove the -w not only will your data be erased but also your internal storage will be erased.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.:
Type
Code:
flash-all
at the Command Prompt and press enter.
Do #7 or #8 to root/reroot
Wipe Data
Open the folder you extracted the Factory Image to and Verify the flash-all.bat file has the -w in this command: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: This will erase your data and internal storage.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.:
Type
Code:
flash-all
at the Command Prompt and press enter.
Do #7 or #8 to root/reroot
ADB Sideload
Boot Recovery
-- On the Computer
Connect the phone to the Computer.
Open a Command Prompt.
-- On the Phone
Boot recovery
Tap Advanced > ADB Sideload.
Swipe the slider to start the ADB connection.
-- Sideload the ZIP
Copy and paste the Zip file you want sideload to the Platform-tools folder or the folder that 'adb.exe' is in.
At the Command Prompt type:
Code:
adb sideload <space> <file name>
Example: adb sideload example.zip
Press enter to begin the sideloading process.
When, you see a Reboot System button, tap it.
Extract/Flash boot.img
Extract boot.img
Use a File Explorer to extract the boot.img from the Factory Image.
Extract the Factory Image file (marlin-opm-9.999999.999-99a-factory-a9a9999.zip) to a folder.
Open the folder and, extract the Image file (image-marlin-aaa9.999999.999.99a.zip).
Flash boot.img
Note: Flashing this file removes root.
Open the folder you extracted the 'image file' to and copy the boot.img file to the platform-tools or to the folder that has fastboot in it.
Boot Bootloader
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
Reboot
Root/Reroot with Magisk - Pass SafetyNet
Important: Set Pin before installing TWRP:
Settings > Security & location >Screen lock > Pin
Backup your data and Internal storage
Download files:
The files listed below are used with 7 and 8.
TWRP
TWRP 3.2.2-0 for Google Pixel XL
twrp-3.2.3-1-marlin.img - Download to your computer
twrp-pixel-installer-marlin-3.2.3-1.zip - Download to your phone
Magisk - Download to your phone
[2018.9.1] Magisk v17.1 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Magisk-uninstaller-20180901.zip - Post 1, Downloads
topjohnwu / Magisk
Custom kernels - Download to your phone
[KERNEL] [29 July] Pixel XL ElementalX 3.09 (8.1.0) 4.06 (P) by flar2
exNoShadez:. nine7nine/Apps
[*][MARLIN/SAILFISH] [8.1.0/9.0.0] [3.18.117] [CLANG 7.0] Flash Kernel 1.19 by nathanchance
[*][KERNEL][8.1.0][3.18.115] PureZ-Kernel-1.9 for Google Pixel XL [17/07/2018] by ZawZaw
[*]Boot Bootloader
[*]Connect the phone to the Computer with USB cord.
[*]Copy twrp-3.2.3-2-marlin.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
[*]Open a Command Prompt on your computer.
[*]At the Command Prompt type:
Code:
fastboot boot twrp.img
and press enter.
[*]When TWRP boots, disconnect the phone from the computer.
[*]Tap Install select
twrp-pixel-installer-marlin-3.2.3-1.zip
[*]Swipe the slider to install
[*]After TWRP is installed
[*]Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
[*]Install Custom Kernel and Root/Reroot (Optional)
Tap Install, select Custom Kernel:
ElementalX
ElementalX-P-3.09.zip
EX Kernel Manager by flar2
flashkernel-marlin-v1.19.zip
PureZ-Kernel-marlin-1.9.zip
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
[*]Root/Reroot with Magisk
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
[*]Install Modules - BusyBox, etc. (Optional)
Open Magisk Manager, tap Menu, tap downloads.
[*]Root/Reroot with Magisk - Pass SafetyNet without installing TWRP
Important: Set Pin before booting TWRP:
Settings > Security & location >Screen lock > Pin
Note: You might have noticed in the 'Install Custom kernel' section that some Custom kernels are installed before Magisk while others are installed after Magisk. The best answer I could find for when to flash a Custom Kernel when using Magisk for root is, if the Custom Kernel modifies/patches the boot image you install Magisk then the Custom Kernel otherwise you install the Custom Kernel then Magisk.
Backup your data and Internal storage
Download files:
See 'Download files' in #7 above - Do not download TWRP zip file.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.
Copy twrp-3.2.3-1-marlin.img to the platform-tools folder or the folder that fastboot is in and rename it twrp.img
Type
Code:
fastboot boot twrp.img
at the Command Prompt and press enter.
When TWRP boots, disconnect the phone from the computer.
Install Custom Kernel (Optional)
Yes
exNoShadez:. nine7nine/Apps
Tap Install, select Magisk-v17.1.zip - (Official)
Tap Add more Zips, select:
exns_eas_v3.8.1p_bca050b.zip
Or
(Stable) exNoShadez_eas_v2.8.2_f94351f.zip
Swipe Slider to Install
Save Log
Reboot System
ElementalX / Flash /PureZ
Tap Install, select Custom Kernel:
ElementalX-P-3.09.zip
EX Kernel Manager by flar2
flashkernel-marlin-v1.19.zip
PureZ-Kernel-marlin-1.9.zip
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
No
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
Install Modules - BusyBox, etc. (Optional)
Open Magisk Manager, tap Menu, tap downloads.
[*]Update Magisk
Important: "If you had the stable version or the official beta installed, you must first un-install the Magisk Manager, only, before you can install the unofficial version, because they are signed with different keys".
"The same holds true if, for example, you have @kantjer 's build installed and want to try @ianmacd 's builds". See kantjer and martyfender post: [UNOFFICIAL] next version Magisk and MagiskManager snapshots by stangri
Magisk Notification is on.
Turn on Magisk Manager update notification: Open MagiskManager > Tap menu icon > Settings > Update Channel > Select: Stable, Beta or Custom
Custom is used to get updates for Unofficial Magisk Builds.
When Magisk Manager notifies you of update availibility.
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Magisk Notification is off.
Open Magisk Manager
When asked 'Do you want to install Magisk-vxx.x.zip now?
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Unofficial Magisk Links and Channels
To set the Magisk Notification Update Channel for Unofficial Magisk Builds: Open MagiskManager > Tap menu icon > Settings > Update Channel > Select: Custom > Copy the link address below and paste it on the line:
ianmacd
Code:
https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
kantjer
Code:
https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json
topjohnwu has a new channel:
[DEV] Magisk Canary Channel - Bleeding Edge Builds by topjohnwu Please, read the OP for the URL.
When Magisk Manager notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
[*][Magisk] Systemless Xposed v89.3/v90.1-beta3 (SDK 21-27)
Information only, see thread for instruction/use.
[2018.5.6][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27) by*topjohnwu
[*]Custom ROMs for Pixel XL
Need help with a Custom ROM?
First, follow the Installation Instructions in the OP (Post 1) of the Custom ROM you want to install.
Second, if you have a problem Installing it, Search the thread of the Custom ROM you want to install for solutions to problem before posting a request for help on their thread.
Official
[ROM][Pixel-XL][8.1.0_r43] [OMS] Pixel Dust OREO for marlin [R8] by spezi77
pixeldust_marlin-oreo-release-eight-20180810.zip
[ROM][OPM4.171019.021.P1][07/21] Benzo Rom 8.1.0 OMS by xanaxdroid
benzorom-8.1.0-20180721-2013-marlin.zip
[ROM] [marlin] [8.1] [LOS-based] **crDroid**OMS**v4.7 (10/12/18) by hokiealumnus
crDroidAndroid-8.1-20181012-marlin-v4.7.zip
[ROM][OFFICIAL][8.1.0]FireHound-v4.8.1 For Google Pixel XL [Marlin] by NepoRood
FireHound-4.8.1-OFFICIAL-20180907-marlin.zip
[ROM][OFFICIAL]Resurrection Remix v6.0 [Android 8.1][05/20/18] by BDogg718
RR-O-v6.0.0-20180520-marlin-Official.zip
[8.1.x][OFFICIAL][WEEKLIES] CarbonROM | cr-6.1 [marlin] by shagbag913
CARBON-CR-6.1-NOCT-WEEKLY-marlin-20180529-1130.zip
[ROM]-[Official]-[10.07.18]-Havoc-OS-[8.1.0] by SKULSHADY
Havoc-OS-20180710-marlin-Official.zip
[ROM][OFFICIAL] lineage-15.1 for Pixels (sailfish/marlin) by razorloves.)
lineage-15.1-20180731-nightly-marlin-signed.zip
Unofficial
[ROM][UNOFFICIAL][7/29/18] AICP 13.1 by stebomurkn420
aicp_marlin_o-13.1-UNOFFICIAL-20180729.zip
[ROM] [8.1.0] BootleggersROM 2.3-STABLE [Unshishufied] by stebomurkn420
BootleggersROM-Oreo4marlin.2.3-Stable-Unshishufied-20180710.zip
AOSiP 8.1 *Flash Kernel* (Unofficial) by stebomurkn420
AOSiP-8.1-Derp-marlin-20180722.zip
[ROM][Unofficial][8.1.0] Resurrection Remix 6.1.0 by dylanneve1
RR-O-v6.1.0-20180818-marlin-Unofficial.zip
Android Devs
[*]Audio Mod
ViPER4Android, [MOD]Audio Modification Library , and Audio Compatibility Patch.
Note: Some, of there can be installed via 'Magisk Downloads'.
[*]Other: TWRP Backup/TWRP Update
TWRP Backup
Boot Recovery.
Tap Backup and select Partitions to backup
Boot
System Image
Vendor Image
Data (Optional)
EFS (Once per major upgrade)
Swipe Slider to backup
Your backup will be stored in /Storage/Emulated/0/TWRP/...
Note: If you are unable to make a backup to internal storage with trwp 3.2.2-0 try backing up to USB-OTG
Update TWRP
TWRP Installation Instructions:
"If you already have TWRP installed: Download the latest zip and install the zip using TWRP".
at #5 why do I need to wipe data if coming from 8.0.0? or is it just a precaution?
Papote3 said:
at #5 why do I need to wipe data if coming from 8.0.0? or is it just a precaution?
Click to expand...
Click to collapse
FWIW, I am on 8.1 from 8.0 Nov patch and did not factory reset, just flash-all with -w removed (actually I run each command in that file myself). Everything works fine and no data/app loss...
jk8260 said:
FWIW, I am on 8.1 from 8.0 Nov patch and did not factory reset, just flash-all with -w removed (actually I run each command in that file myself). Everything works fine and no data/app loss...
Click to expand...
Click to collapse
Yeah that's what I thought. I think he just writes it just as a precaution, in case anything goes wrong on 8.1, first factory reset and then write the problem if it still persist
Supersu or Magisk
Which rooting method is best for the Pixel XL. Supersu or Magisk
Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work
Juhler said:
Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work
Click to expand...
Click to collapse
Password Encryption isnt working on the new TWRP3.2.0 gotta wait for an update or remove passwords all together...
Juhler said:
Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work
Click to expand...
Click to collapse
Supersu wasn't even in my app drawer after flashing the zip so after rebooting I just went into the zip and installed the apk manually
Thank you for this thread....it worked. I did #9
Can confirm #10 works like a charm. Thanks for the separate thread. Both your guide threads should be stickies.
Just use adb sideload...
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo
ekowwillis said:
Which rooting method is best for the Pixel XL. Supersu or Magisk
Click to expand...
Click to collapse
In my opinion Magisk.
NepoRood said:
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo
Click to expand...
Click to collapse
Good Information!
Did you flash a Custom Kernel (ElementalX-P-3.00.zip) or UPDATE-suhide-v1.09-20171001222116.zip to pass SafetyNet?
Papote3 said:
Yeah that's what I thought. I think he just writes it just as a precaution, in case anything goes wrong on 8.1, first factory reset and then write the problem if it still persist
Click to expand...
Click to collapse
There are three reasons I recommend #4 - 'Wipe Data' prior to rooting:
a. I write all my guides with step by step instructions for noobs.
b. Some have reported data corruption when not doing #4 - 'Wipe Data'.
c. When upgrading the OS, I always start with a clean install.
If you want to upgrade without a clean installation that's ok too, but it is much easier to trouble shoot problems if you start with a clean installation.
Homeboy76 said:
Good Information!
Did you flash a Custom Kernel (ElementalX-P-3.00.zip) or UPDATE-suhide-v1.09-20171001222116.zip to pass SafetyNet?
Click to expand...
Click to collapse
I did not flash those, I have no real need for either...
Sent from my Pixel XL using XDA Labs
Everything went well up to "erasing userdata"..... its been stuck there for 5 min... any advice?
Cancel that....Just finished...
NepoRood said:
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo
Click to expand...
Click to collapse
Thanks
Don't you need stock recovery to be able to apply OTA?
I don't see a step doing that, and I suppose you're on TWRP, or were you already on stock recovery?
If so, then better make that a clear step.
badabing2003 said:
Thanks
Don't you need stock recovery to be able to apply OTA?
I don't see a step doing that, and I suppose you're on TWRP, or were you already on stock recovery?
If so, then better make that a clear step.
Click to expand...
Click to collapse
That's covered with Step #1, friend
NepoRood said:
1) Flash stock boot.img (November for me, I used TWRP)
Click to expand...
Click to collapse
Since boot and recovery are on the same partition, flashing stock boot will give you stock recovery. I flashed my stock boot using TWRP, however, it can be flashed via fastboot as well.
AFAIK, this can be done for all updates (I've used this method since Oreo came out), it's just like taking the OTA from Gooble, you just download it yourself :good:
Regards,
Nepo
PS, I did flash full factory image when upgrading from Nougat to Oreo, just FYI
NepoRood said:
That's covered with Step #1, friend
Since boot and recovery are on the same partition, flashing stock boot will give you stock recovery. I flashed my stock boot using TWRP, however, it can be flashed via fastboot as well.
AFAIK, this can be done for all updates (I've used this method since Oreo came out), it's just like taking the OTA from Gooble, you just download it yourself :good:
Regards,
Nepo
PS, I did flash full factory image when upgrading from Nougat to Oreo, just FYI
Click to expand...
Click to collapse
Thanks for the clarification, didn't know that was the case.
I never flashed boot using twrp, would it do it for all slots, I guess it would.
Sent from my Pixel XL using Tapatalk
Is anyone getting this error?
Code:
wiping userdata...
/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
I'm using the wipe option, but haven't ran into this one before.
WHO IS THIS GUIDE FOR:
Anyone updating factory images within the same OS version (10 to 10)
Anyone upgrading from one OS to another (9x to Android 10)
Below is a QUICK REFERENCE guide for those who have done this before, and a DETAILED STEP BY STEP guide for the first or second timer who needs each and every step outlined. Links to all required files are also provided (make sure you are selecting the latest version)
UPDATE TO THE LATEST FACTORY IMAGE . . . UPGRADE TO THE NEXT OS. . .
PREP WORK:
* Unlocked bootloader. (*performing critical_unlock only required with bootloader versions PRIOR to TMZ20a) read it here.
* Latest SDK Platform Tools found here.
* USB 2.0 & 3.0 cables available (trust me)
* Remove screen lock security before starting
* Remove all substratum overlays
*Download and extract the latest Taimen factory image (place the second extracted folder in Platform Tools folder)
CLEAN FLASH (wipe everything) or DIRTY FLASH (keep data)
Decide now whether you want a fresh OS that will restore your device to factory setup OR if you want to flash the latest factory image but keep your data.
For a clean flash: leave the FLASH-ALL file intact, change nothing.
To retain your data: EDIT the FLASH-ALL file and REMOVE the -w near the end of the script. Save the file and reopen it to ensure the -w has been removed,
When UPGRADING from one OS to another I reco a CLEAN FLASH (leave the -w intact)
Place these files on your sdcard (either before dirty flash or from PC after clean install):
* Latest TWRP.ZIP
* Your preferred customer kernel zip, I use ElementalX kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing :good:
QUICK REFERENCE GUIDE for updating/upgrading Pixel 2 XL:
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash custom kernel, I use flar2's ElementalX Kernel. SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
DETAILED STEP BY STEP GUIDE for updating monthly factory images, or upgrading to the next OS (ie: 9x to 10x)
I reco a CLEAN FLASH (leave the -w intact) when jumping from one OS to a new one (not necessary when doing monthly factory updates within the same OS version)
Requirements:
*Unlocked bootloader and Critical_unlock* completed. (*critical_unlock required with bootloader versions PRIOR to TMZ20a) read it here.
*Latest SDK PlatformTools found here
*USB 2.0 & 3.0 cables available (trust me)
These files on your sdcard:
* Latest TWRP.ZIP
* Your preferred Custom Kernel, I use Elemental X Kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK
These files in your Platform Tools Folder:
* Latest factory image (MAKE SURE YOU DL THE CORRECT DEVICE IMAGE :good: )
* Latest TWRP.IMG
1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Connect device to PC, verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot latest factory image (To KEEP internal storage intact, edit and remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
Type: FLASH-ALL (hit enter) Allow the OS to reboot and settle for a minute *REMEMBER LEAVING THE -W INTACT WILL WIPE YOUR DEVICE*
6. Reboot into BOOTLOADER, in CMD screen Type: fastboot boot <twrpxxx.img name> to boot into Latest TWRP.IMG
7. Once in TWRP, install Latest TWRP.ZIP from sdcard
8. Reboot back into Recovery
9. Install compatible custom kernel, I use flar2's ElementalX Kernel.
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Boot into Recovery
13. Install Latest Magisk.zip
14. Reboot into System
15. Profit
Troubleshooting Tips & Other Information
Click here for * * * BASIC FASTBOOT/ADB TROUBLE SHOOTING FOR THE 2XL * * *
If you get stuck at the G screen, or bootloop into TWRP, try these steps:
-Perform a hard reboot (long press the power button) or
-Get back to TWRP (whether by booting into it from fastboot, or rebooting into bootloader -long press power & vol down- then boot into recovery) and reinstall the Magisk Uninstaller in TWRP a few times.
- If you are bootlooping into TWRP with Magisk installed, READ THIS!
- Safety Net message in Magisk "The Response Is Invalid" is a known issue[/URL] ... Be patient
View attachment 4572738
Make sure you have all the correct and/or latest versions of SDK Tools, factory image, TWRP.img and TWRP.zip, and Magisk
Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, but it works
Again, HUGE thanks to @Badger50 for his invaluable input
Az Biker said:
A lot of users have had success upgrading from Oreo to Pie and there are several tutorial / guide posts located in different threads, so I figured I'd centralize instructions in a Quick Reference Thread, that includes all needed file links and an easy to follow step by step.
Please feel free to make any suggestions to simplify or make this more accurate.
Requirements:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
These files on your sdcard:
* TWRP 3.2.2-0.ZIP
*Flash kernel 3.0
* magisk uninstaller
*magisk zip 1674
* MM 5.8.3 APK
These files in your Platform Tools Folder:
* 9.0 factory image
*TWRP 3.2.2-0.IMG
1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot 9.0 factory image(To KEEP internal storage intact, remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
6. Type: fastboot boot <twrpxxx.img name> to boot into TWRP 3.2.2-0.IMG
7. Once in TWRP, install TWRP.ZIP on sdcard
8. Reboot back into Recovery, and install the magisk uninstaller in twrp,
9. Reboot back into Recovery and install Flash kernel 3.0
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Install MM 5.8.3 APK
13. Reboot into Recovery
14. Install magisk zip 1674,
15. Reboot back into Recovery
16. Reboot into System
17. Profit
Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, but it works
Thanks to @Badger50 for figuring out the right steps in this process!
Click to expand...
Click to collapse
Well done my brother!! :good::good:
Badger50 said:
Well done my brother!! :good::good:
Click to expand...
Click to collapse
I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).
newyesor said:
I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).
Click to expand...
Click to collapse
Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.
You use unlock bootloader normal??
Badger50 said:
Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.
You use unlock bootloader normal??
Click to expand...
Click to collapse
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
newyesor said:
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
Click to expand...
Click to collapse
So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.
Badger50 said:
So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.
Click to expand...
Click to collapse
I use this command for flash unlock bootloader.
fastboot flashing unlock
newyesor said:
I use this command for flash unlock bootloader.
fastboot flashing unlock
Click to expand...
Click to collapse
Have you ever ran fastboot flashing unlock_critical..?
Have you actually booted into the 9.0.OS yet?
Badger50 said:
Have you ever ran fastboot flashing unlock_critical..?
Have you actually booted into the 9.0.OS yet?
Click to expand...
Click to collapse
I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.
newyesor said:
I use this command for flash unlock bootloader.
fastboot flashing unlock
Click to expand...
Click to collapse
If you flashed the factory image with no issues, then you must have completed critical_unlock as well, otherwise the new bootloader shouldn't have taken (as far as I understand).
I'd start from scratch again, and make sure you follow the process exactly. Many users have used this with no issue, so maybe you missed something? The first time I flashed the factory image to my 6P (my backup) I totally skipped flashing the boot.img, and wondered why it wouldn't boot
Kudos, just what I needed to update!
newyesor said:
I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.
Click to expand...
Click to collapse
Have you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?
Badger50 said:
Have you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?
Click to expand...
Click to collapse
Yes,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I try to flash patch boot for root without twrp but it's not work.
I try to flash magisk follow you but it's not work.
Is flashing the kernel mandatory?
newyesor said:
Yes,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I try to flash patch boot for root without twrp but it's not work.
I try to flash magisk follow you but it's not work.
Click to expand...
Click to collapse
Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory image. However, it seems that you have somehow. All I can suggest is to fastboot the 9.0 again to both slots, and let it boot up each time.
Then fastboot into twrp, flash the installer zip, and let it boot up. Then go back to twrp, flash magisk uninstaller zip, then flash custom kernel, and let it boot up. Then go back to twrp, and flash magisk 1674 again.
If none of that works, I'd unlock _critical, which will wipe your phone, and then start over.
aznriceballman said:
Is flashing the kernel mandatory?
Click to expand...
Click to collapse
Not mandatory, but it keeps TWRP touch screen working among other things...
Just wanted to say thanks for this!
I didn't have time to update from DP5 yesterday, but I guess that was a good thing because now there's this guide, and it worked perfectly. Upgraded from DP5/flash 2.44 and who knows what Magisk version to all the latest and greatest in no time at all.
Thanks!
Badger50 said:
Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory image. However, it seems that you have somehow. All I can suggest is to fastboot the 9.0 again to both slots, and let it boot up each time.
Then fastboot into twrp, flash the installer zip, and let it boot up. Then go back to twrp, flash magisk uninstaller zip, then flash custom kernel, and let it boot up. Then go back to twrp, and flash magisk 1674 again.
If none of that works, I'd unlock _critical, which will wipe your phone, and then start over.
Click to expand...
Click to collapse
im having an issue, i followed all instructions and got booted up an everything but when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no go. Any suggestions?
shooterlgk said:
im having an issue, i followed all instructions and got booted up an everything but when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no go. Any suggestions?
Click to expand...
Click to collapse
Do you have screen lock disabled?
Badger50 said:
Do you have screen lock disabled?
Click to expand...
Click to collapse
Yes sir
Firstly, I would like to thank @karthick mostwanted for his work and a thumbs up for keeping Lineage OS updated.
I have an Indian Unit of X2 Pro with 128 Gigs of RAM and I got the ROM working with FP and the payment apps at once. Everything works good here. Only thing which I did not like is the camera, so I'm using PixelPlus GCAM on this ROM.
Coming to the steps (assuming ADB & Fastboot drivers installed) -
1. Unlock the Bootloader. For the same Install the In Depth Test app (pm if you do not get the links for the app on Google) and apply. After a successful review message on the app, use the following commands.
adb reboot bootloader (For reboot into fastboot mode)
fastboot flashing unlock
Select the confirmation dialog on the screen and its done. Then type fastboot reboot for the phone OS to boot. It will erase all your data too.
2. Next step is to install TWRP img file by Mauronofrio (Google it). Download vbmeta.img also, you will get in LOS thread downloads section. Copy the recovery file and vbmeta into the ADB folder where the powershell/cmd is running so the you can fetch it. Reboot into the fastboot mode and give the following command.
fastboot flash recovery recoveryfilename.img
DO NOT REBOOT YET. Immediately type fastboot flash --disable-verification vbmeta vbmeta.img and enter. Don't reboot, with help of Volume and power button combination, boot directly into recovery. Remember, do not reboot phone in any other mode or even the present OS because it will wipe the recovery installed.
3. Format Data. (Don't Wipe, Use FORMAT DATA Option). Wipe Cache & Dalvik.
4. Keep the Files in a USB Storage such as Lineage OS, Magisk 20.3, Open Gapps Nano ARM 64.
5. Insert the USB drive through an OTG and go to TWRP mount option and mount external storage. It will start showing files. Now go to install and select OS. Wait, don't run now. Add Gapps to the same queue and then run.
6. After successful installation, wipe cache and dalvik and reboot your phone.
7. After you setup everything, again boot into TWRP recovery and install magisk 20.3.
You are done and all set !
Note - Do not remove/uninstall system apps using root access in LOS, it may break. Happened with me when I tried to uninstall DuckDuckGo, it went into bootloops.
Will be happy to answer any doubts for this installation. Comment below if you need further help !
oreopie said:
Note - Do not remove/uninstall system apps using root access in LOS
Click to expand...
Click to collapse
Do you mean by using apps like titanium backup, systemapp remover or similar?
Did you rooted with new lineage OS 18 ?