Related
By this you will be able to Unlock bootloader, Flash TWRP, and Root while maintaining possibility of applying future OTA's
I've researched many topics and forums for this and compiled all those things in this single step by step topic.
WARNING
Follow if you understand every word written in the topic name only and at your own risk.
I am not responsible for your doing. Follow every step as mentioned, you can skip parts if you understand what you are doing. Read it again to understand clearly, don't do it if you have any doubt and ask before rather asking later.
Credits to xda miui forums and all their ops for this kind info. Thank You.
Divided in 5 parts:
Main Topic-Introduction, Download links
Post two-Short Instructions-Rooting and Flashing OTA's
Post three-Unlocking bootloader, Flashing TWRP, Flashing 7.2.3 OTA, Rooting
Post four-How to flash Future OTA and Root after that
Post five-Troubleshooting- Drivers installation, Patching boot.img, Re-locking Bootloader, Fixing error 0x80070002 in MI Tool, VOLTE fix for marshmallow roms, Debloat MIUI 8, Under Test Methods
Things needed:
1. Redmi Note 3
2. PC with windows x64 (I did it on Windows 10 x64)
3. MiFlash_2016.03.30.exe
4. Fastboot 7.1.8 rom
Note: Fastboot 7.2.5 Rom is now available, you can use that and skip ota modifying and flashing part:Fastboot 7.2.5 rom
5. i) Miui 7.2.3 OTA
ii) Miui 7.2.5 OTA
6. twrp-3.0.2-2-kenzo.img
Twrp-3.0.2-2 Complete backup version
7. unlocked_emmc_appsboot.mbn Recovery flashable
8. Boot.img patcher (extracted from alka recovery, credits to the dev)
Patching method on pc is also given in the guide
9. Volte Fix for Marshmallow Roms: Here
10. MIUI 8 Debloating:Here
Some patched boot.img:
i) 7.2.3 patched boot.img
ii) 7.2.5 patched boot.img
iii) 7.3.2 patched boot.img
9. Android Image Kitchen OP-Android Image Kitchen - Unpack/Repack Kernel Ramdisk
10. Minimal adb and fastboot OP-[TOOL]Minimal ADB and Fastboot
11. SuperSU zip OP-SuperSU v2.65
12. i) Edited updater-script for OTA 7.2.3
ii) Edited updater-script for OTA 7.2.5
Now follow post 3 if you are not clear about this 'thing' or try looking at post 2 for simple and short instructions.
Short Instructions-Rooting and Flashing OTA's
Divided in two parts:
PART 1
How to root?
1. Falsh complete 7.1.8 with unlocked emmc_appsboot.mbn instead of the one in the rom .tgz and unlock using fastboot- After this our bootloader is unlocked.
2. We will now flash the twrp recovery using fastboot (with help of minimal adb and fastboot)- we have a custom recovery to apply modified ota zip (all future ota zips need to be modify before flashing) and also to flash supersu and patched boot.img
3. We will make a backup of 7.1.8 system+boot in TWRP.
4. We will now modify the ota zip (replace emmc_appsboot.mbn and updater-script) and flash in the recovery (system mounted as read only on first TWRP boot) but will NOT flash supersu.- updated to 7.2.5 now
5. We will now make a backup of 7.2.5 system+boot with NO compression in TWRP.- we got 7.2.5 boot.img (boot.emmc.win is the name )to patch it (#8 in things needed)
6. We will take this backed up boot.emmc.win in Android Image Kitchen in pc and patch it.- we now have patched 7.2.5 boot.img and a way to patch all future boot.img's
7. We will now mount system as read/write and flash supersu and this patched boot.img in twrp.- we have successfully rooted the phone.
PART 2
Future OTA's will fail as they will verify system and boot too before flashing. We have altered both here. But we have a recovery and a backup to restore before flashing ota.
So, how to apply future updates?
1. Download the ota but DO NOT flash it.
2. Modify the OTA zip as we did for 7.2.3 and 7.2.5
3. Restore unrooted system and not patched boot.img (the 7.2.5 TWRP backup)
4. Mount system and read only
5. Patch the OTA zip by replacing emmc_appsboot.mbn and updater-script. Flash the OTA
6. Make a new boot+system backup.
7. Patch the new boot.img.
8. Mount system as read/write
9. Flash patched boot.img along with supersu.
Follow up post three for detailed Rooting guide if things are not clear for you.
Unlocking bootloader, Flashing TWRP, Flashing 7.2.5 OTA, Rooting
It is particularly focused on rooting latest (at writing this) version of Miui i.e. 7.2.3
How to Root?
For rooting we have to flash SuperSu from custom recovery i.e. TWRP. So, obviously we need to flash TWRP first in Redmi Note 3.
But, to flash TWRP we need to unlock bootloader first
Unlocking Bootloader:
Downloads from post one:
1. Download and Install Mi Flash Tool
2. Download and Extract 7.1.8 Fastboot Rom (You can also use latest fastboot rom, just skip OTA part from this guide)
3. Download, Extract and Replace unlocked_emmc_appsboot.mbn in the extracted rom folder
4. Download and Install Minimal ADB and Fasboot Tools
Instructions:
1. Turn Your Phone On and Connect USB Cable to the phone and the Computer
2. Go to settings-about phone and tap Miui versoin five times.
3. Go back and go to Additional settings-Developer Options and enable USB debugging (if disabled) and Enable OEM Unlock (if disabled)
4. Open Device Manager in PC and check to find your phone Installed as ADB Device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. See if there is any pop up in phone asking to Authorization (Allow USB debugging). Check Always allow from this Computer and tap ok.
6. Run the Minimal ADB and Fastboot From the Start Menu
7. Check if your Device is Detected in ADB by typing this command
Code:
adb devices
You should see the output like this
If not, then you have to install drivers. Go to topic #5. Then try again.
8. Type the following command to Reboot the Phone to EDL mode
Code:
adb reboot edl
9. Check the Device Manager you should see the Phone as shown in the Screenshot below
NOTE: The Driver can be Either the one Shown in the Image (which is a default driver loaded by windows)
or
can be from Qualcomm which will read as
Qualccomm HS-USB QLoader 9008
Click to expand...
Click to collapse
Note that there is a possibility that You might End up in
Qualcomm HS-USB Diagnostics 900E
Click to expand...
Click to collapse
But Don't Panic and Follow the Steps from Step No. 1 again
10. Now Start the MI Flash Tool and Browse to the Location Where you have Extracted the Fastboot ROM
11. Go to Advanced (arrow in front of browse) and Select:
Flash Programmer, Raw XML File and Patch XML File
from the Fastboot ROM\Images folder and press enter on keyboard
12. Press Refresh in MI tool and You should see you phone in the MI Flash tool With the same COM# as in the Device Manager
13. Press Flash and wait. It would take some time to flash about 170-250 seconds or more ( if Miflash shows a error on clicking Flash , please restart Miflash and try again)
14. After the Miflash fastboot is completed successfully, hard boot phone to Fastboot mode by pressing and holding Volume Down+Power On. You will see mi bunny on screen.
15. Again run Minimal ADB and Fastboot from start menu (as Administrator)
16. Type:
Code:
fastboot oem device-info
It will show you the current Bootloader Status .
17. Now again Type:
Code:
fastboot oem unlock-go
Optional: Type in the previous command again to check if the status of Bootloader had changed or not.
18. Type:
Code:
fastboot reboot
to reboot the phone.
Bootloader is unlocked now but do not disconnect the phone from pc yet.
Credits:
http://en.miui.com/thread-253680-1-1.html
http://en.miui.com/thread-261019-1-1.html
Flashing TWRP:
Downloads from post one:
1. TWRP recovery
Instructions:
1. Once done with bootloader unlock guide, without disconnecting the phone, restart phone in fastboot mode (use steps 1-8 from unlocking guide and replace edl command with fastboot, i.e. write fastboot instead of edl in cmd) or Press and hold volume down+power to hard boot it to fastboot.
2. Go to Minimal ADB and Fastboot directory
C:\Program Files (x86)\Minimal ADB and Fastboot
Click to expand...
Click to collapse
and copy/move downloaded twrp-3.0.2-2-kenzo.img here.
3. Type following in cmd once the phone is in fastboot mode.
fastboot flash recovery twrp-3.0.2-2-kenzo.img
4. Once done, hard boot phone to recovery by Pressing and holding Volume Up+Power On. TWRP should boot.
Note: When asked to mount system as read only or as read/write select read only in TWRP. This step is important otherwise you will face bootloop after flashing ota.
Flashing 7.2.3 OTA and then 7.2.5 OTA:
Downloads from post one:
1. Miui 7.2.3 OTA and Miui 7.2.5 OTA
2. unlocked_emmc_appsboot.mbn
Downloads from internet
1. 7zip Or WinRAR
Instructions:
1. Download the OTA in your PC or move it in your pc from phone after downloading.
2. Open the OTA file in Windows with Winrar/7zip
3. Locate the emmc_appsboot.mbn in firmware-update folder and delete from the zip (it will take a while for the deletion please be patient)
4. Drag and drop the (unlocked)emmc_appsboot.mbn to the firmware-update folder of the OTA
5. Navigate to "META_INF/com/google/android/" and extract the updater-script file and then delete it from the zip.(make sure to keep a backup of the zip)
6. Open the file in a text editor, (I prefer Notepad++) and delete the following lines and save the file
ui_print("Verifying current system...");
getprop("ro.build.fingerprint") == "Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.1.8.0.LHOMICL:user/release-keys" ||
getprop("ro.build.fingerprint") == "Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.2.3.0.LHOMIDA:user/release-keys" ||
abort("Package expects build fingerprint of Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.1.8.0.LHOMICL:user/release-keys or Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.2.3.0.LHOMIDA:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:33721674:bf5d61ecd25d0026e768f6258f320640385976fd:34037066:22a19fe883c5fe4b25852702a1bd25bcaeedd9a0") || abort(""EMMC:/dev/block/bootdevice/by-name/boot:33721674:bf5d61ecd25d0026e768f6258f320640385976fd:34037066:22a19fe883c5fe4b25852702a1bd25bcaeedd9a0" has unexpected contents.");
if block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") then
ui_print("Verified system image...");
else
(range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "e04e9788c17630b4088243d8b3ee29509568b793") || (range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "3b8aeee76a291f2b1647c9bbcbece5be948a83fc") || abort("/dev/block/bootdevice/by-name/system has been remounted R/W; reflash device to reenable OTA updates");
(range_sha1("/dev/block/bootdevice/by-name/system", "80,0,32770,32929,32931,33439,65535,65536,65538,66046,98303,98304,98306,98465,98467,98975,131071,131072,131074,131582,163839,163840,163842,164001,164003,164511,196607,196608,196610,197118,229375,229376,229378,229537,229539,230047,262143,262144,262146,262654,294911,294912,294914,295073,295075,295583,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,476353,491520,491522,524288,524290,557056,557058,589824,589826,622592,622594,623102,650190,650191,655320") == "a75d23fa6067c58c166603cfac0b3d0df9b81919") ||
abort("system partition has unexpected contents");
endif;
Click to expand...
Click to collapse
(Edit the 7.2.5 OTA the same way or use updater-scripts provided for both OTA's from post 1)
7. Now again navigate to "META_INF/com/google/android/" and drag and drop the modified updater-script file inside the folder
8. Move this modified OTA zip to your (internal/external sd) and flash using TWRP.
9. Once done, make a system+boot bakcup in twrp, name it "7.1.8 stock"
10. Apply future updates like this and make backup with naming. Delete old backups.
Example: Make a backup named "7.2.5 stock" just after flashing 7.2.3 and 7.2.5 updates. Then root it and flash patched boot.img. If the phone starts up normal, reboot to recovery and delete 7.1.8 stock backup and keep 7.2.5 stock backup to use it for flashing future OTA.
Rooting:
Downloads from post one:
1. SuperSU zip
2. 7.2.5 boot patched.img
Instructions:
Note: Now change the mode to read/write for system partition from mount option in TWRP. Otherwise these zips will not flash.
1. Copy/Move/Download SuperSU zip and patched boot.img in your phone.
2. Extract the .rar containing the patched boot.img.
3. Reboot to recovery and Tap on Install in the TWRP main screen.
4. Select SuperSu.zip
5. To flash boot.img, the default mode is to flash zip files, you will need to toggle the mode to images.
6. To do so, tap on the Images… button on the bottom-right of the screen
7. The recovery will now only see the image files, select the patched boot.img
8. Once you select, you will be prompted to select the type of image it is, select Boot or Recovery. Select Boot.
9. Finally, swipe the button on the bottom of the screen to start the flashing process.
10. Once complete, you can go to Reboot > System.
How to flash Future OTA and Root after that
You got a Unlocked, Rooted phone with custom TWRP recovery. The OTA will check the system and will fail to flash as you have flashed SuperSu and Boot.img.
What you may do when a new OTA arrives??
Flashing any OTA and rooting it
Downloads from post one:
1. SuperSU zip
2. Unlocked boot img (will be updated when ota will arrive)
3. Unlocked_emmc_appsboot.mbn
Downloads from internet:
1. WinRAR/7zip
Preparing OTA:
1. Download the OTA in your PC or move it in your pc from phone after downloading.
2. Open the OTA file in Windows with Winrar/7zip
3. Locate the emmc_appsboot.mbn in firmware-update folder and delete from the zip (it will take a while for the deletion please be patient)
4. Drag and drop the (unlocked)emmc_appsboot.mbn to the firmware-update folder of the OTA
5. Navigate to "META_INF/com/google/android/" and extract the updater-script file and then delete it from the zip.(make sure to keep a backup of the zip)
6. Open the file in a text editor, (I prefer Notepad++) and delete the following lines and save the file
ui_print("Verifying current system...");
getprop("ro.build.fingerprint") == "Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.1.8.0.LHOMICL:user/release-keys" ||
getprop("ro.build.fingerprint") == "Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.2.3.0.LHOMIDA:user/release-keys" ||
abort("Package expects build fingerprint of Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.1.8.0.LHOMICL:user/release-keys or Xiaomi/kenzo/kenzo:5.1.1/LMY47V/V7.2.3.0.LHOMIDA:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:33721674:bf5d61ecd25d0026e768f6258f3206403859 76fd:34037066:22a19fe883c5fe4b25852702a1bd25bcaeed d9a0") || abort(""EMMC:/dev/block/bootdevice/by-name/boot:33721674:bf5d61ecd25d0026e768f6258f3206403859 76fd:34037066:22a19fe883c5fe4b25852702a1bd25bcaeed d9a0" has unexpected contents.");
if block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") then
ui_print("Verified system image...");
else
(range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "e04e9788c17630b4088243d8b3ee29509568b793") || (range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "3b8aeee76a291f2b1647c9bbcbece5be948a83fc") || abort("/dev/block/bootdevice/by-name/system has been remounted R/W; reflash device to reenable OTA updates");
(range_sha1("/dev/block/bootdevice/by-name/system", "80,0,32770,32929,32931,33439,65535,65536,65538,66 046,98303,98304,98306,98465,98467,98975,131071,131 072,131074,131582,163839,163840,163842,164001,1640 03,164511,196607,196608,196610,197118,229375,22937 6,229378,229537,229539,230047,262143,262144,262146 ,262654,294911,294912,294914,295073,295075,295583, 327679,327680,327682,328190,360447,360448,360450,3 60958,393215,393216,393218,393726,425983,425984,42 5986,426494,458751,458752,458754,459262,476353,491 520,491522,524288,524290,557056,557058,589824,5898 26,622592,622594,623102,650190,650191,655320") == "a75d23fa6067c58c166603cfac0b3d0df9b81919") ||
abort("system partition has unexpected contents");
endif;
Click to expand...
Click to collapse
NOTES:
a. If this is not working for you, getting error while flashing, then use the updater script added in post one, i have edited that my self for my use and worked perfectly.
b. Allow TWRP to read/write system (asked on first time when recovery boots) as flashing ota to system is a write process.
7. Now again navigate to "META_INF/com/google/android/" and drag and drop the modified updater-script file inside the folder
8. Move this modified OTA zip to your (internal/external sd) and flash using TWRP.
9. Once done, make a system+boot bakcup in twrp, name it "7.2.3 stock"
Flashing and making new Backup:
1. Reboot to TWRP (Volume Up+Power on)
2. Restore 7.2.3 stock backup from backup and restore options
3. Flash the modified OTA.
4. Make a new backup of system+boot and name it "version" stock. Like "7.2.3 stock"
Rooting:
1. Copy/Move/Download SuperSU zip and patched boot.img in your phone.
2. Extract the .rar containing the patched boot.img.
3. Reboot to recovery and Tap on Install in the TWRP main screen.
4. Select SuperSu.zip
5. To flash boot.img, the default mode is to flash zip files, you will need to toggle the mode to images.
6. To do so, tap on the Images… button on the bottom-right of the screen
7. The recovery will now only see the image files, select the patched boot.img
8. Once you select, you will be prompted to select the type of image it is, select Boot or Recovery. Select Boot.
9. Finally, swipe the button on the bottom of the screen to start the flashing process.
10. Once complete, you can go to Reboot > System.
Troubleshooting
Installing Drivers
1. Disable Windows Drivers Signature on your computer: you can do that by pressing Windows button + i on keyboard to reveal the Settings page. From there you can choose Update & Security >> Recovery >> Advanced startup >> Restart now. Wait a moment for your computer to restart. Next, go to Troubleshoot >> Advanced options >> Startup settings >> Restart. Once your computer restarts, now choose Disable driver signature enforcement which is option number 7. See the video below:
Disable Windows Drivers Signature
:credits to the owner i have not made it.
2. Hold Vol - and Vol + and plug Usb , you will enter adb Mode.
3. Now Phone is Connected as ADB. Check Device Manager for Below:-
4. Run Minimal adb (search adb in start)
5. Type these Commands:
Code:
adb devices
adb reboot edl
Phone will enter in download Mode with Red Led.
6. Open Device Manager and Phone will be detected as QHUSB_BULK.
Right Click and choose Update Drivers.
7. Choose Browse My Computer for Driver Software
8. Choose the Path of Xiaomi Folder. Most of users will find it like this.
Note:- If Folder does not exist , Install MI Flash (post #1) first.
Win 64 bit C: \ Program Files (x86) \ Xiaomi \ MiPhone \ Qualcomm \ Driver
Win 32 bit C: \ Program Files \ Xiaomi \ MiPhone \ Qualcomm \ Driver
9. Choose Install this Driver Software anyway.
10. The driver will be installed Sucessfully and you can see added in Ports as Qualcomm HS-USB.
Credits:http://en.miui.com/thread-235865-1-1.html
Patching Boot.img
1. Download the Android Image Kitchen Tool from post #1 and extract it.
2. Download the fastboot room and extract to locate the boot.img (or any other source you would like) and move it to the Android Image Kitchen folder, as shown below:-
3. Right click & hold, on the "Boot.img" file and move & place it onto unpackimg.bat file and proceed with the on-screen message to "Run", as shown below:-
4. Next go to ramdisk directory and locate fstab.qcom file, as shown below:-
5. Use any text editor (notepad++ preferred) to open fstab.qcom file, then use the Find function to find any value containing "Verify" and delete with care, and save it accordingly, as shown below:-
Code:
,verify
:delete verify also the , in from of it.
6. Now we need to repack the modded boot.img file, double-click to execute "repackimg.bat" hence it will generate a new boot file as "image-new.img" as shown below:-
7. Done..
Credits:http://en.miui.com/thread-249666-1-1.html
Relocking Bootloader: (DO AT YOUR OWN RISK AND ONLY IF YOU KNOW WHAT YOU ARE DOING)
1. Get the fastboot rom image from topic #1 or the locked emmc_appsboot.mbn from post #1 (version 7.1.8)
2. Download (from post #1) and Install Minimal adb and fastboot
3. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and copy/move the downloaded emmc_appsboot.mbn here.
4. Run MAF32.exe (it is in this folder too)
5. Type following commands
Code:
fastboot Flash aboot emmc_appsboot.mbn
fastboot Flash abootbak emmc_appsboot.mbn
fastboot Reboot
6. Done.
Fixing The system cannot find the file specified.(0x80070002):
* Make sure you have downloaded correct rom.
* Make sure there is no space in you path of images.
Eg:
NOT E:\MI TOOLS\rn3\kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global_9706e12561UNLOCK\kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global\images
BUT E:\MI_TOOLS\rn3\kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global_9706e12561UNLOCK\kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global\images
IF STILL THE ERROR IS THERE (ONLY TRY IF ALL ABOVE METHODS FAIL)
1. Download this Rar and replace both files in your fastboot rom. (flash_all.bat in rom folder and rawpragram0.xml in images folder)
2. Try to flash now.
What about the fingerprint error while flashing OTA?
OP, you need to really give detailed steps... Else this thread is gonna be filled with more questions than answers....
For example the ota zip does not contain the boot.img file but contains a patch file boot.img.p , so do we need to replace modded full boot.img in ota- will it get flashed or will the flashing fail as the instructions in ota will be for patch boot file...
Dropbox link for patched bot image of 7.2.3 is not working... gives error
7.2.3.0 boot.img
use this link to downloadwww.dropbox.com/s/k5w16gotzz7zge0/7.2.3 boot patched.rar?dl=0
Sudeep Duhoon said:
reserved 4
Click to expand...
Click to collapse
I am on miui 7.2.3.0(locked boot loader), can I flash modified 7.2.3.0 boot.IMG and twrp through adb?
pvp16 said:
I am on miui 7.2.3.0(locked boot loader), can I flash modified 7.2.3.0 boot.IMG and twrp through adb?
Click to expand...
Click to collapse
to flash modified boot.img you have to do all the steps till that part first.
Error from dropbox
Downloaded file of boot .rar has been corrupted
root 7.2.3.0
if i am on 7.2.3.0 (bootloader locked) is it neccessary to flash 7.1.8 ie downgrade to unlock bootloader... or i can skip some of ur steps plzzz help
---------- Post added at 09:29 AM ---------- Previous post was at 09:15 AM ----------
what we are doing (deleting) in script..... it is for to get rid from finger print error
Deevit said:
Downloaded file of boot .rar has been corrupted
Click to expand...
Click to collapse
Downloading in phone? Try uc browser.
vivekjha said:
if i am on 7.2.3.0 (bootloader locked) is it neccessary to flash 7.1.8 ie downgrade to unlock bootloader... or i can skip some of ur steps plzzz help
---------- Post added at 09:29 AM ---------- Previous post was at 09:15 AM ----------
what we are doing (deleting) in script..... it is for to get rid from finger print error
Click to expand...
Click to collapse
Yes necessary.
I was following the process to install the OTA after making changes to the zip file with the emmcxx and update-script.
TWRP threw me this error
Failed to apply patch " patch/boot.img.p"
Updater process ended with ERROR:7
Pls help. Thanks
Tried
Sudeep Duhoon said:
Downloading in phone? Try uc browser.
Click to expand...
Click to collapse
In UC I had tried but it has been corrupted
Unlocking Bootloader Error
When I try to flash fastboot oem unlock-go it returns: FAILED (remote: Token verification failed, reboot the device)
.HOW TO FIX
pvp16 said:
I am on miui 7.2.3.0(locked boot loader), can I flash modified 7.2.3.0 boot.IMG and twrp through adb?
Click to expand...
Click to collapse
Not without unlocking the bootloader, you cant
---------- Post added at 06:07 AM ---------- Previous post was at 06:04 AM ----------
fylim said:
I was following the process to install the OTA after making changes to the zip file with the emmcxx and update-script.
TWRP threw me this error
Failed to apply patch " patch/boot.img.p"
Updater process ended with ERROR:7
Pls help. Thanks
Click to expand...
Click to collapse
I guess you need to remove the patch boot file and replace it with modified boot image file.
Deevit said:
Downloaded file of boot .rar has been corrupted
Click to expand...
Click to collapse
link has been updated but file working fine. it is 10.64mb
[SIZE=+3]How-To Guide For Beginners[/SIZE]
[SIZE=+2]Pixel XL (Marlin)[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+3]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Pixel XL (Marlin). I'm going to start off with a couple of the more obvious ones and go from there.
[size=+3]Prerequisites[/size]:
If you are on Verizon, please follow dePixel8 guidelines prior to using this thread
Always update your phone to the latest build available before starting the unlocking/rooting process.
You'll need a working adb/fastboot environment on your PC to get through some of these guides.
You must have Java installed and up to date in order to use the SDK Manager, please ensure that this is taken care of before installing the SDK.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C: called SDK (C:SDK). Once you've downloaded the zip you can extract it into your C:SDK folder. Navigate to C:SDKandroid-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library, Google USB Driver
Once you have installed those, inside C:SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
[SIZE=+3]Quick Tips[/SIZE]
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
[SIZE=+3]Index[/SIZE]
Post #1
1. How To Unlock Your Bootloader
2. How To Install A Custom Recovery On Your Device
3. How To Root with TWRP Recovery
4. How To Root with via Fastboot (No Recovery)
Post #2
5. How To Install A ROM with TWRP Recovery
6. How To Install A Custom Kernel With TWRP Recovery
7. How To Install A Custom Kernel Using Fasboot
8. How To Flash The Factory Images (Return To Stock)
9. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
[SIZE=+3]1. How To Unlock Your Bootloader[/SIZE]
Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue the unlock command:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Note: After unlocking your bootloader, each time your phone boots up you'll be greeted with a warning that says "Your device software can't be checked for corruption. Please lock the bootloader". This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is unlocked it will stay there.
Important: 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 section 10 of this guide for full instructions on how to return to stock.
[SIZE=+3]2. How To Install TWRP On Your Device[/SIZE]
Prerequisites: unlocked bootloader (section 1).
Warning: TWRP is currently in RC1 phase and is not fully stable, flash at your own risk.
This guide assumes you have just unlocked your bootloader and are otherwise stock, NO root yet.
Download the necessary files (IMG and Zip) from the TWRP website and add the TWRP zip to your internal storage: https://dl.twrp.me/marlin/
Place the IMG file in your fastboot folder (this is where fastboot.exe is located on your PC)
Boot into the bootloader. Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot boot path/to/twrp.img
(The TWRP filename in the command will change depending on which recovery you're flashing)
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your password, reboot to the bootloader and try again. Go to install and browse to the zip and install the TWRP zip
[SIZE=+3]3. How To Root[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest SuperSU of your choosing to your phone:
https://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
Boot into TWRP recovery and enter the install menu.
Navigate to where you have SuperSU stored on your internal storage and select it.
Swipe to install.
Thats it, reboot and you should have TWRP and SuperSU installed
[SIZE=+3]4. How To Root via Fastboot[/SIZE]
Prerequisites: unlocked bootloader (section 1)
Special Note: This is for users who do not have or want TWRP installed and want to run stock root
Download Chainfire's root-marlin-pixelxl.zip located here: https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Extract Chainfire's zip and follow the instructions in the read me
Code:
***** The short guide *****
*BOOT* (do not flash!) the supplied image, and wait a few minutes:
fastboot boot boot-to-root.img
***** The long guide *****
Before you root your device, you need to unlock your bootloader, if you haven't done so yet.
If you are using a Verizon device, you need a special tool for that. Go find that first.
- Boot into Android
- Enable developer options
--- Settings -> About phone -> Build number: tap 7 times
- Enable OEM unlocking
--- Settings -> Developer Options -> OEM unlocking
- Go into bootloader mode
--- Turn off device
--- Hold volume down and power
- Run "fastboot flashing unlock" and follow the on-screen instructions
--- This will wipe your device
To root your device:
- Go into bootloader mode, if not there already
--- Turn off device
--- Hold volume down and power
- Run "fastboot boot boot-to-root.img"
--- Wait for a few minutes. The device will reboot at least twice
- You should be rooted once Android is fully booted up
*****
Enjoy!
- Chainfire
XDA:DevDB Information
Guide: How To Unlock/Root/Flash for Pixel XL (Marlin), Tool/Utility for the Google Pixel XL
Contributors
bajasur, The Flash, beanstown106, @micmars
Version Information
Status: Testing
Created 2016-11-27
Last Updated 2016-11-26
[SIZE=+3]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Pending......
[SIZE=+3]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+3]7. How To Install A Custom Kernel via Fastboot[/SIZE]
Prerequisites: unlocked bootloader (section 1)
This guide is for users who DO NOT have TWRP installed, and want to Fastboot flash custom kernels.
Check the md5 to verify its integrity.
Download the kernel file you want to flash from whichever kernel developer you'd like
Place the file in your fastboot folder
Open a command prompt within that folder and run
Code:
fastboot flash kernel kernel_binary
kernel_binary will be replaced with whatever the file name (ie fk-r5.gz for Franco's Kernel)
Reboot your device.
Special Note: You may lose root if you had SuperSU pre-installed, you will need to re root following Section 4 (How to Root via Fastboot)
[SIZE=+1]8. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Download the appropriate factory images for your model https://developers.google.com/android/images
Unzip the marlin-xxxxxx-factory-xxxxxxxx (marlin-nmf26o-factory-4f68765c) into a directory on your PC (for this guide we'll use C:\marlin\).
Once unzipped you should have a folder named marlin-xxxxxx (marlin-nmf26o).
Move the contents of this folder into your Fastboot/ADB environment so that you can run fastboot and adb commands. (Note: I do the opposite and move the most current fastboot and ADB from the Android SDK into this folder)
Look for the windows batch file named "flash-all.bat" and double click on it. This should begin the proper full clean flash of all images back to stock. This should take a few minutes, but eventually your phone should reboot on its own and take you to the Android set up screen.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
[size=+4]Frequently Asked Questions[/size]
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
2. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.
3. After unlocking the bootloader I get a message that says "Your device software can't be checked for corruption. Please lock the bootloader". What's going on? Can I get rid of it?
This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is locked it will stay there.
4. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot.
5. Does taking an OTA update wipe my user data?
No, it doesn't.
6. Do I need to flash the userdata.img from the factory images?
You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
fastboot format userdata
More to come, special thanks to @Heisenberg for his excellent guide format
Reservation
Don't forget to pin this
Dude, awesome
Looking good @bajasur!
Nice! Great job...should definitely be pinned
Thanks so much @bajasur! I always used the one by the famous @Heisenberg for the 6P and its great to have one for the Pixel XL.
Any plans to also include the step-by-step for restoring back to stock?
MinimalistChris said:
Thanks so much @bajasur! I always used the one by the famous @Heisenberg for the 6P and its great to have one for the Pixel XL.
Any plans to also include the step-by-step for restoring back to stock?
Click to expand...
Click to collapse
Yes, there is a lot more to come. For now to restore to stock I recommend running the flash-all.bat file that comes within the factory image folder.
A detailed step by step image flashing guide will be linked in the next few days.
Sent from my Pixel XL using XDA-Developers mobile app
Thanks @bajasur! We can still use this to unlock and root from NDE63X correct?
oneandroidnut said:
Thanks @bajasur! We can still use this to unlock and root from NDE63X correct?
Click to expand...
Click to collapse
Negative
For Verizon you need to follow the unlock method provided by DePixel Devs. Once you have unlocked the rooting and twrp methods should work.
Sent from my Pixel XL using XDA-Developers mobile app
bajasur said:
Negative
For Verizon you need to follow the unlock method provided by DePixel Devs. Once you have unlocked the rooting and twrp methods should work.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry I should have clarified it is a Google Store edition just with verizon sim and X software. I can just unlock it like normal correct?
oneandroidnut said:
Sorry I should have clarified it is a Google Store edition just with verizon sim and X software. I can just unlock it like normal correct?
Click to expand...
Click to collapse
Yep! That should work fine ☺
Sent from my Pixel XL using XDA-Developers mobile app
bajasur said:
Yep! That should work fine
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Awesome I am trying to wait until TWRP is stable but im inpatient lol
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
aholeinthewor1d said:
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
Click to expand...
Click to collapse
Other than flashing dePixel8 to allow bootloader unlocking, all other steps are identical.
aholeinthewor1d said:
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
Click to expand...
Click to collapse
I'll clarify in the OP regarding Verizon devices but yes that should be the case
Sent from my Pixel XL using XDA-Developers mobile app
Does rooting without TWRP cause bootloops on NDE63V? I tried it with the all-in-one tool and couldn't get my Pixel to boot past the 4 dots when I was on NDE63V.
I have since flashed the Npf26j update. Would it be safe to root via chainfire's method? Wanted to avoid TWRP for now incase I get the data drain bug.
Thanks!
[Guide] Pixel XL Android 8.0.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + November Security Patch
Other Pixel XL Guides:
Android 9.0.0 (Pie), Android 8.1.0 (Oreo), Android 7.1.2 (Nougat)
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'.
This Guide also works for the Pixel: If, you download the correct files for the Pixel.
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
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 Android8/Oreo Factory Image
Pixel XL (Fi/Canada) - marlin-opr1.170623.032-factory-990d8d51.zip
Pixel XL (other carriers) - marlin-opr3.170623.013-factory-af0b6564.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 Android SDK or Platform tools installed.
Important: Update Android SDK or Platform Tools, regularly, for optimal performance.
Need help installing Android SDK or using SDK Platform tools:
How to Install ADB & Fastboot on Mac, Linux & Windows-(Method 1)
Using the SDK Platform-Tools
Credits/Thanks/Recognitions
TWRP
TEAM TWRP - TWRP 3.2.0-0 for Google Pixel XL
Special thanks to @gubacsek - for [MOD][RECOVERY] Working TWRP recovery for Pixel/Pixel XL on Android O
SuperSU/suhide/Flashfire
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
[Android 4.2+][ROOT][2017.09.21] FlashFire v0.73 by Chainfire
FlashFire Documentation
Magisk/MagiskManager
[BETA][2017.11.24] Magisk v14.5 (1456) by*topjohnwu
[DEV] [Magisk] Official Pixel (XL) Support is Here! by topjohnwu
Magisk Manager Releases topjohnwu
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
Special thanks to @goodwin_c - for [Unofficial] Google Pixel family support
Custom Kernels
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
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
Custom ROMs
[ROM][Pixel-XL][8.0.0_r17] Pixel Dust OREO for marlin [ALPHA] by spezi77
Other
spaceman860 - TWRP 3.1.1-1 Backup
Special Thanks to LeMoise - for the Root with Magisk remain Stock - Pass SafetyNet and Receive OTA Updates. It was nice while it lasted. Sorry, it stopped working with the November Security Patch.
Those I may have, inadvertently, forgotten.
Index
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 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.
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 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 USB cable.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock 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:
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 reads 'Your device software can't be checked for corruption. Please lock the bootloader' You will receive this warning until, you relock the bootloader.
Important: do not repeat do not relock your bootloader unless your phone is fully stock. You must flash the factory image 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 #13 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 appropriate Factory/System 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-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following and press enter.
Code:
flash-all
Install Factory Image and keep data
Important: If upgrading to Android8/Oreo from Android7/Nougat 7.x.x. Do #4 - Install Factory Image and wipe data
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
Edit flash-all.bat: remove -w
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following and press enter.
Code:
flash-all
Install Custom Kernel
Flash with TWRP
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Download files:
Factory Image for Nexus/Pixel Devices to your Computer
TWRP 3.2.0-0 for Google Pixel XL
Custom Kernel - to your Phone
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
SuperSU - to your Phone
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Fastboot the boot.img.
Use a File Explorer to extract the contents of your factory image.Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the device/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, and leave your phone in bootloader mode, and connected to your Computer.
Install TWRP
Place twrp-3.2.0-0-marlin.img in your platform-tools folder and Rename it twrp.img
Type the following command at the prompt:
Code:
fastboot boot twrp.img
Flash Zips.
When TWRP boots on your phone, Tap the Install button, and select twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, and select a Custom Kernel
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Swipe the slider to install.
Reboot System
Boot Recovery
Tap the Install button, and select SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Note: The sequence of flashing the zips is important
Reboot System
Install BusyBox to/sbin/supersu/xbin.
Flash with Flashfire
Warning: "FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and this thread before doing anything potentially destructive."
Backup your data and Internal storage
Install Application:
Install Flashfire Application from Google's Play Store
Open Flashfire Grant Root
Tap Plus Sign (+)
Tap Flash ZIP or OTA
Locate/Navigate to ZIP File location
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Tap file
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Check the Restore boot and recovery images box
Tap Checkmark (Top right corner)
Verify before you Flash
Flash ZIP or OTA - Has the file you want to flash and ✓ Restore boot and recovery images is present.
If not repeat 2. Flash with Flashfire d through h above.
EverRoot - ✓ Inject SuperSU is present.
If not, Tap EverRoot Select Inject SuperSU
Reboot should default to ✓ Normal.
Tap Flashfire symbol to Flash file
Root with SuperSU
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire to your Phone
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Boot Bootloader
Connect device/phone to Computer
Open a Command Prompt on your computer.
Type the following command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, and select
twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, and select
SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Reboot System.
Note: Install BusyBox to/sbin/supersu/xbin.
Root with SuperSU - Pass Safetynet
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Note: If you did #6 - Install Custom Kernel or #7 - Root with SuperSU, above you already have root. Start at m..
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SR5-SuperSU-v2.82-SR5-20171001224502.zip to your Phone
UPDATE-suhide-v1.09-20171001222116.zip to your Phone
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Busybox
There are several different versions (Free and Pro, see Credits/Thanks/Recognitions above) find one that works for you.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Boot Bootloader
Connect device/phone to Computer
Open a Command Prompt on your computer.
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, select SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Reboot System.
Boot Recovery
When TWRP boots on your phone, tap the Install button, Select
UPDATE-suhide-v1.09-20171001222116.zip
Swipe the slider to install.
Reboot System
Note: Install BusyBox to /sbin/supersu/xbin.
Root with Magisk - Pass SafetyNet
Important: I haven't tested Magisk 14.5 or Magisk Manager 5.4.3. If you have problems redo #9 substitute Magisk 14.3 for Magisk 14.5 and Magisk Manager 5.4.0 for Magisk Manager 5.4.3.
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Install TWRP, Custom Kernel, Magisk, and Busybox.
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
twrp-3.2.0-0-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.2.0-0.zip to your Phone.
Custom Kernel (Optional) - to your Phone
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
Magisk
[BETA][2017.11.24] Magisk v14.5 (1456) by*topjohnwu
Magisk-v14.5 (1456).zip to your Phone.
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Magisk-uninstaller-20170928.zip to your Phone
Flash boot.img.
Use a File Explorer to extract the contents of your factory image. Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the device/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, leave your phone in bootloader mode and connected to the Computer.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select
twrp-pixel-installer-marlin-3.2.0-0.zip
Swipe the slider to install
Reboot Recovery
Tap Install, select Custom kernel (Optional)
Note: If you do not want to install a Custom Kernel go to n below.
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Swipe slider to install
Reboot System
Boot Recovery
Tap Install, select Magisk-v14.5 (1456).zip
Swipe slider to install.
Reboot System
Install BusyBox (Optional)
Open Magisk Manager, tap Menu, tap Modules, verify Busybox for Android NDK is checked.
Root with Magisk - Pass SafetyNet without installing TWRP
thanks stryker09
Important: Set Pin before using TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Read/Do (as applicable) #1 - Command Prompt/Boot Bootloader/Boot Recovery; #2 - Testing ADB (Android Debug Bridge)/fastboot; #3 - Unlock Bootloader; #5 - Install Factory Image and keep data; and Tips and Tricks -OTA Installation Tips
Download files:
TWRP 3.2.0-0 for Google Pixel XL to your Computer.
[BETA] Magisk v14.5 (1456) by topjohnwu
Magisk-v14.5 (1456).zip to your Phone.
Flash boot.img.
Use a File Explorer to extract the contents of your factory image. Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the phone to your Computer via USB cable.
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, leave your phone in bootloader mode and connected to the Computer.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots up, tap Install, select Magisk-v14.5 (1456).zip
Swipe Slider to Install
Reboot System
Install BusyBox (Optional)
Open Magisk Manager, tap Menu, tap Modules, verify Busybox for Android NDK is checked.
Custom ROMs for Pixel XL
[ROM][Pixel-XL][8.0.0_r17] Pixel Dust OREO for marlin [ALPHA] by spezi77
Other - TWRP Backup
Boot Recovery.
Tap Backup and select Partitions to backup
Boot
System Image
Vendor Image
Data (Optional)
Swipe Slider to backup
Reboot System
Your backup will be stored in /Storage/Emulated/0/TWRP/...
Return to Stock and Lock Bootloader
Return to Stock
Backup 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-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.:
Type the following command at the prompt, and press enter.
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 command 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
Audio Mod
[GUIDE] How to install ARISE sound on 8.0 Magisk by kingbri
[GUIDE] ARISE magnum OPUS on magisk android 8.0 by kingbri
getting viper4android to work would be great.
busybox refused to install
TheUndertaker21 said:
getting viper4android to work would be great.
busybox refused to install
Click to expand...
Click to collapse
Arise works perfectly.
jaxenroth said:
Arise works perfectly.
Click to expand...
Click to collapse
which one did you flash ?
jaxenroth said:
Arise works perfectly.
Click to expand...
Click to collapse
Please more info about version and install settings!
I am trying at the moment v4a get to work with bootable twrp..... Would appreciate further info a lot.
Hi, step 3, first code should be fastboot flash bootloader bootloader.img and not fastboot flashbootloader bootloader.img
(i.e there is a gap between flash and bootloader)
To root mine all I did was chainfires boot-to-root. Then you can install and substratum theme with O support. I'm using the Swift black theme. You have to install only 5 at a time or it won't work. It says in the description for the app. My Android O is blacked out now and I'm happy.
Why is it claiming it must be a Google purchased phone? Many Verizon users have an unlocked bootloader.
TheUndertaker21 said:
which one did you flash ?
Click to expand...
Click to collapse
ARISE+Deuteronomy+2.94+Modular Aroma Installer
jaxenroth said:
ARISE+Deuteronomy+2.94+Modular Aroma Installer
Click to expand...
Click to collapse
getting abnormal when i flashed that
it worked when i use supersuconfig in permissive mode but i lost root when i do
do you still have root ? and how did you manage to get it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I flashed SU from TWRP, booted into system, from there adb'd back to BL and booted TWRP again and flashed aroma installer.
Is the aroma installer necessary for just being stock rooted with adaway? Or would I just fastboot boot twrp then flash latest SuperSU and reboot?
Sent from my Nexus 6P using Tapatalk
waiting for nexus 6p
TheUndertaker21 said:
getting viper4android to work would be great.
busybox refused to install
Click to expand...
Click to collapse
Updated OP with BusyBox path information.
grifforama said:
Hi, step 3, first code should be fastboot flash bootloader bootloader.img and not fastboot flashbootloader bootloader.img
(i.e there is a gap between flash and bootloader)
Click to expand...
Click to collapse
Thanks for the 'editing' help.
encephalon9986 said:
To root mine all I did was chainfires boot-to-root. Then you can install and substratum theme with O support. I'm using the Swift black theme. You have to install only 5 at a time or it won't work. It says in the description for the app. My Android O is blacked out now and I'm happy.
Click to expand...
Click to collapse
Yeah, there's more than one way to root, I prefer Chainfire's SuperSU. Thanks for the Substratum information.
Which Substratum theme engine and version did you use?
Mike02z said:
Why is it claiming it must be a Google purchased phone? Many Verizon users have an unlocked bootloader.
Click to expand...
Click to collapse
A case of CRS (can't remember s#*t) Lol. I just forgot to change it. Thanks for the reminder.
jaxenroth said:
View attachment 4249400 I flashed SU from TWRP, booted into system, from there adb'd back to BL and booted TWRP again and flashed aroma installer.
Click to expand...
Click to collapse
Great!
Neverendingxsin said:
Is the aroma installer necessary for just being stock rooted with adaway? Or would I just fastboot boot twrp then flash latest SuperSU and reboot?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, "just fastboot boot twrp then flash latest SuperSU and reboot"
This is a Pixel XL thread.
Chouiyekh said:
waiting for nexus 6p
Click to expand...
Click to collapse
This is a Pixel XP thread.
[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT
Security Patch - December 2019
Introduction
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 Pixel, Pixel 2, Pixel 2 XL, Pixel 3a, or Pixel 3a XL phones.
NEW
Android 11 (R) ROM
Update(s)
Factory/OTA Images - 12/02
Magisk Stable - Magisk-25.2
Magisk Beta - Magisk-25.3
Magisk Canary - Magisk-25205
T.W.R.P - twrp-3.4.0-0-marlin.img/zip[/URL]
SDK Platform-tools - r33.0.3
Custom Kernels
No Updated Custom Kernels
Custom ROMs Android 10 (Q)
Pixel Experience 10/25
Custom ROMs Android 11 (R)
[UNOFFICIAL][ROM][11][Marlin/Sailfish] LineageOS 18.0 [06/10/2020] by*Lunarixus
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.
The latest Android 9.0.0 (Pie) Factory or OTA Image: "marlin" for Pixel XL
Factory Image
10.0.0 (QP1A.191005.007.A3, Dec 2019)
OTA Image
10.0.0 (QP1A.191005.007.A3, Dec 2019)
Computer - With the latest SDK Platform-Tools: r30.0.5 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
Pixel XL Android 10 (Q)
Credits/Thanks/Recognitions
Heisenberg RETIRED FORUM MODERATOR - He set the standard for creating, detailed, Guides.
Those I may have, inadvertently, forgotten.
Index
(NOTE: These are not steps 1-13, they are individual sets of information/instructions).
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.
Notes:
If your computer only has 'open powershell here' in the context menu. Use option 2.
If you do not want to open a Command Prompt every time you want to use fastboot, add the path to the Platform-tools folder to Windows environment variables.
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.
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 the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
fastboot devices
It should return your device serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader (Google Pixel XL)
Backup your data/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 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 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/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader (Google Pixel XL)
'B' must be completed before performing this step!
Boot bootloader
Open a Command Prompt and type this at the Prompt: 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: 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 Unlock off.
Install Factory Image keep or wipe data
When doing a major upgrade, Android 8.1.0 (Oreo) to Android 9.0.0 (Pie). I suggest wiping data/Clean Install.
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 flash-all at the Command Prompt and press enter.
Reboot
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 flash-all at the Command Prompt and press enter.
Reboot
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: 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:
fastboot flash boot boot.img --slot all
Reboot
Install T.W.R.P./Root/Reroot with Magisk and 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.3.1-3 for Google Pixel XL
twrp-3.4.0-0-marlin.img - Download to your computer
twrp-pixel-installer-marlin-3.4.0-0.zip - Download to your phone
Magisk - Download to your phone
The latest Stable/Beta Magisk Manager from Magisk by topjohnwu
[DEV] Magisk Canary Channel - Bleeding Edge Builds by topjohnwu
Custom kernels - Download to your phone
No Updated Custom Kernels
Kernel Managers - Download to your phone
EX Kernel Manager
FK Kernel Manager
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.5.0-0-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: fastboot boot twrp.img and press enter.
When TWRP boots, disconnect phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.4.0-0.zip
Swipe the slider to install
Reboot Recovery
If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, and Swipe the Slider to Install.
Note: If you have Modules installed, please read these posts by @jcmm11 'RC' before flashing/installing Magisk's Uninstaller.zip: Post 329 and Post 333
Install Custom Kernel and Root/Reroot (Optional)
Note(s):
Some Custom Kernels can be updated by flashing via twrp or Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
Some Custom Kernels can also be Flashed with a Kernel Manager.
If you want to flash the kernel via the Kernel Manager instead of twrp skip #7 L1 do #7 L2 then install kernel via Kernel Manager.
Yes
No Updated Custom Kernels
No
Tap Install, select Magisk-20.4.zip - Stable/Beta
Swipe Slider to Install
Save Log
Reboot System
Boot T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.
Important: Remove Pin before booting TWRP:
Settings > Security & location >Screen lock > None
Backup your data and Internal storage
Download files:
See #7 - Skip the twrp-pixel-installer-marlin-3.4.0-0.zip
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.
Copy twrp-3.4.0-0-marlin.img to the platform-tools folder or the folder that fastboot is in and rename it twrp.img
Type fastboot boot twrp.img at the Command Prompt and press enter.
When TWRP boots, disconnect phone from computer.
If requested Swipe to allow modifications.
If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, and Swipe the Slider to Install.
Note: If you have Modules installed, please read these posts by @jcmm11 'RC' before flashing/installing Magisk's Uninstaller.zip: Post 329 and Post 333
Install Custom Kernel and Root/Reroot (Optional)
Note(s):
Some Custom Kernels can be updated by flashing via twrp or Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
Some Custom Kernels can also be Flashed with a Kernel Manager.
If you want to flash the kernel via the Kernel Manager instead of twrp skip #8 I1 do #8 I2 then install kernel via Kernel Manager.
Yes
No Updated Custom Kernels
No
Tap Install, select Magisk-20.4.zip - Stable/Beta
Swipe Slider to Install
Save Log
Reboot System
Set Magisk Manager's Update Chanel/Update Magisk
Set Magisk Manager's Update Channel - Stable/Beta/Custom
Open Magisk Manager > Tap menu icon > Settings > Update Channel > Select Stable, Beta or Custom.
Custom is used to switch to Canary. Paste the URL below in the Custom Channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json
Update Magisk
When Magisk Manager notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Tap, Reboot
Done!
Custom ROMs for Pixel XL
Need help with a Custom ROM?
First, follow the Installation Instructions in the OP of the Custom ROM you are trying 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.
Alpha/Beta
None
Official
None
Unofficial
[ROM][10.0][marlin] Pixel Experience [AOSP][2020/10/25] by*PixelBoot
Audio Mod
ViPER4Android FX/XHiFI, [MOD]Audio Modification Library , and Audio Compatibility Patch.
Note: These Mods can be installed via Magisk Manager: Tap Magisk Manager > Tap Menu > Tap Downloads > Select Mod > Tap Install.
Other: TWRP Backup/TWRP Update
TWRP Backup
To Internal Storage
Boot bootloader
fastboot boot twrp-3.4.0-0.img
[*]When twrp-3.4.0-0 boots, tap Backup and select Partitions to backup
[LIST="(1)"]
[*]Boot
[*]System Image
[*]Data
[/LIST]
[*]Tap Select Storage ==> internal storage
[*]Tap ok
[*]Swipe Slider to backup
[*][B]Your backup will be stored in /Storage/TWRP/...[/B]
[/LIST]
[/HIDE]
[*]To OTG-USB Storage
[HIDE]
[LIST="a"]
[*]Boot fastboot mode (#1B)
[*][ICODE]fastboot boot twrp-3.4.0-0.img
[*]When twrp-3.3.1-3 boots, tap Backup and select Partitions to backup
[LIST="(1)"]
[*]Boot
[*]System Image
[*]Data
[/LIST]
[*]Insert USB-OTG
[*]Tap Select Storage ==> OTG-USB
[*]Tap ok
[*]Swipe Slider to backup
[*][B]Your backup will be stored in /Storage/TWRP/...[/B]
[/LIST]
[/HIDE]
[/LIST]
[/HIDE]
[*][B]Update[URL="https://twrp.me/google/googlepixelxl.html"]TWRP[/URL][/B]
[/LIST]
[/HIDE]
[/LIST]
Reserved
Reserved
Once again, fantastic guide Big thanks :highfive:
Way to be on top of things @Homeboy76, Job Well Done, once again :good:
Do OG Pixels need magisk 1671 or 1674?
Pixel 2 and 2 xl have some troubles, so there is a specific magisk version for them in the flash kernel thread, before flash I just wanna make sure 1671 won't cause issues, thank you.
Hi.
Can anyone tell me?
I want to flash Android Pie.
Now I'm on official Lineage OS 15.1 + twrp 3.2.2 + Magisk
I need to do step 3 (and flash all to both slots)?
Return Phone to Stock
Or I need to do step 4 (and flash all only once)?
Install Factory Image
Thanks in advance.
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
I did, but I was running FireHound v4.7 (July Security), so I got a lot of different FCs, lol (Hey, I had to try). If you're on stock, you'll probably be fine.
I just installed TWRP 3.2.3, did a factory reset and setup fresh. No issues after that.
I had to use Magisk beta 16.7 to root. I did a restore with TiBu and all my previous apps are working fine.
Hi, i followed this (already 9 with OTA) :
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.2.2-0-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 phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.2.2-0.zip
Swipe the slider to install
After TWRP is installed
Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
then
flash Magisk-v16.7(1671).zip - (BETA)
Swipe Slider to Install
Save Log
Reboot System
did not install custom recovery tho
it stuck at google logo. do i need to flash custom kernel?
I have this same problem, using 3.2.3. Not installing TWRP, I installed Elemental X alone and it works fine. It's when I try to install Magisk 16.7 that it bootloops on the Google Logo
lesp4ul said:
Hi, i followed this (already 9 with OTA) :
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.2.2-0-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 phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.2.2-0.zip
Swipe the slider to install
After TWRP is installed
Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
then
flash Magisk-v16.7(1671).zip - (BETA)
Swipe Slider to Install
Save Log
Reboot System
did not install custom recovery tho
it stuck at google logo. do i need to flash custom kernel?
Click to expand...
Click to collapse
jeremyafrank said:
I have this same problem, using 3.2.3. I installed Elemental X alone and it works fine. It's when I try to install Magisk 16.7 that is bootloops on the Google Logo
Click to expand...
Click to collapse
found this , magisk 16.7 1674
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view
didn't work either lol
I'm going to have to go back to 8.1 (had done a dirty flash, but I'm only running stock) until this is sorted. Some nice things I'd like to play with in Pie, but not at the expense of root.
lesp4ul said:
found this , magisk 16.7 1674
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view
didn't work either lol
Click to expand...
Click to collapse
TENN3R said:
Do OG Pixels need magisk 1671 or 1674?
Pixel 2 and 2 xl have some troubles, so there is a specific magisk version for them in the flash kernel thread, before flash I just wanna make sure 1671 won't cause issues, thank you.
Click to expand...
Click to collapse
1674 is for Pixel2/Pixel2XL
[TAIMEN/WALLEYE] [9.0.0] [4.4.146] [CLANG 7.… - Pg. 284 | Google Pixel 2 XL
Where is my mistake?
I flashed Pie image marlin-ppr1.180610.009-factory-90a4fa8b
(flash all.bat)
And had a lot of errors (Screenshot attached).
After reboot to system I have Lineage OS 15.1 that I had before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance.
djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
Yes, this is how I updated.
- I was on stable Magisk 16.0 so I flashed the most recent Magisk uninstall ZIP in TWRP to be safe, since 9.0 requires the Magisk 16.7 beta
- boot to bootloader
- flash-all.bat removing -w
- fully boot to system
- turn off, boot to bootloader
- fastboot boot new TWRP 3.2.3-0
- install TWRP 3.2.3-0 ZIP
- install Magisk 16.7 ZIP
- boot to system
- I had to reauthorize root access for all root apps and enable systemless hosts in Magisk
Device passes SafetyNet and is certified in Play Store.
jeremyafrank said:
I'm going to have to go back to 8.1 (had done a dirty flash, but I'm only running stock) until this is sorted. Some nice things I'd like to play with in Pie, but not at the expense of root.
Click to expand...
Click to collapse
1674 is for Pixel2/Pixel2XL: [TAIMEN/WALLEYE] [9.0.0] [4.4.146] [CLANG 7.… - Pg. 284 | Google Pixel 2 XL
Anyone try going from 8.0.0 directly to 9? I haven't done updates in forever. Don't want to just try and end up messing things up for myself.
djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
I did with no problem.
I did a dirty install from Stock 8.1 with only Magisk.
Installed TWRP, Elemental and Magisk in that order rebooting to system in-between each one. It seems as soon as Magisk 16.7 is installed, many apps fail to launch or break, i.e. the Google Play Store can no longer open without force closing, Titanium Backup errors because it can't read the TB Pro key, going into settings and trying to change some things causes the UI to freeze up. But some apps like Twitch does work. Though Magisk is broken as well, i.e. Magisk Hide doesn't work but root access is detected. Safety, however, fails both on the inbuilt test in Magisk Manager and the SafetyNet app.
If I open Magisk Manager and install 16.0 apps goe back to working fine, but Magisk is still broken in the same way and SafetyNet still won't pass.
Reading back through the thread, I see that some get boot loops due to Magisk, but for others, it works fine and SafetyNet passes which I find odd... Either way, I guess we'll all have to wait for the next Magisk update!
EDIT:
Turns out, running the Magisk Uninstaller zip, then flashing the Magisk 16.7 zip seems to solve the issue!
Can confirm Magisk Hide now works and SafetyNet passes. Seems like running the uninstaller is a good step to add into this guide if the user was previously running Magisk.
ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL
Hey everyone,
It's been a few days since the Phone(1) went on sale. And already, Nothing is doing things right by making the Phone(1) Kernel available. The next step was to unlock the bootloader and root it. Both are already available and ready to use.
So don't deprive yourself and here is the process of the two operations.
You've already unlocked the bootloader and rooted a carrierless variant of either a Google Pixel or OnePlus, you should have no problem unlocking your Nothing Phone (1) and installing Magisk. For those of you with a memory lapse, here is a tutorial to guide you through the process.
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Click to expand...
Click to collapse
How to bootloader unlock and root the Nothing Phone 1After unlocking the bootloader, you can use Magisk to root the device.
You must first unlock the bootloader in order to be able to start third-party software. Here's how to do it:
Step 1: Unlock the Nothing Phone 1’s bootloader
Open the Settings app on your Nothing Phone 1.
Tap on About phone.
Locate the section named Software info and tap on it.
On the next screen, tap on the Build number 7 times until it says you’re now a developer.
Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
Scroll down a bit until you see USB debugging. Enable it as well.
Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the Latest version of ADB and Fastboot (33.0.3) binaries installed.
Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
[NOT A MANDATORY TO UNLOCK CRITICAL, IT'S FOR ME BETTER TO NOT USE THIS COMMAND, THIS COMMAND COULD BE THE REASON SOME PEOPLE HAVE BRICK OR NOT WHEN GO BACK STOCK NOS]
You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.
Step 2 - Rooting your Nothing Phone 1 with MagiskWith an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
Depending of your model, you have Global or EEA (European) firmware availables.
You can download the latest full OTA firmware package here.
Extract the stock boot image from the OTA package. For more information, take a look the “You have access to the recovery-flashable ZIP file” section our “How to Install Magisk on your Android Phone” tutorial.
In case you don’t want to download the whole OTA file, you can separately download the boot image just to the post #2 or from this post. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
Download and install the Magisk app on the Nothing Phone 1.
Open the Magisk app and tap on the Install button.
Choose Select and Patch a File. A file manager will pop up.
Select the boot image that you pushed earlier and let Magisk patch it.
Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
Reboot the Phone 1 into the bootloader: adb reboot bootloader
Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
Reboot the phone: fastboot reboot
Open the Magisk app and your Nothing Phone 1 should be rooted.
Keep in mind that unlocking the bootloader and rooting your Nothing Phone 1 will impact how you take advantage of updates. You'll have to learn to manually load monthly security patch updates. But don't worry, it's easy enough to do.
-=o#0#o=-
WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.
Spoiler: Relock the bootloader of your Phone(1)
menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
[*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
[*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1
#root #nothingphone
Unbricking Nothing phone 1: Flash Stock Firmware with Fastboot
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Click to expand...
Click to collapse
Warning : The process below will erase all the data on your device. So, I invite you to make a full backup of the device beforehand.
Unfortunately, as I don't own the Phone(1) yet, I am unable to take screenshots with the Phone(1) at the moment. As soon as I can, I will put them online to finalize the tutorial. Thank you for your understanding
STEP 1: What you need and read before the process.
It’s really important for a process without problems
Install Android SDK and the Platform-tools folder
Download the Nothing OS version you need (see this post)
Extract the "payload bin" file from the rom
Extract the Firmware Stock "boot.img" from the rom (see this tutorial)
Unlock the bootloader of your Phone(1) (see this tutorial)
STEP 2: Boot the bricked phone 1 into Fastboot mode
Very often, a soft-bricked or boot-looped device may already be in Fastboot mode. However, if you are stuck in a boot-loop, long press the Power key to turn it off.
Then press and hold the Power and Volume Down keys (or Power and Volume Up keys on some devices) simultaneously to boot your device into Fastboot mode.
In case you are unable to turn off your device, let the battery discharge. Once it is drained, connect it to the charger. Then, as soon as it is about to start, use the Power and Volume Up/Down keys and it will start directly in Fastboot mode.
STEP 3: Format the device via Fastboot
1.Go to the platform-tools folder where the extracted ROM is located.
2.Then go to its address bar, type CMD in its address, and press Enter. This will launch the CMD window.
3.Now run the following command to perform a factory reset (optional but recommended)
Code:
fastboot -w
STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands
Run the commands below in the CMD window [which is open in the platform-tools folder] to flash the partition file.
Very Important: Only run one command at a time. If you get an error, however, do not exit the process halfway, but go on to the next flashing command instead.
Don't forget to check your command line before validating it, because often a small error blocks you!
Spoiler: Command Lines
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
flash fastboot dsp dsp.img
flash fastboot dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img fastboot
fastboot flash product product.img
fastboot flash qupfw qupfw.img
flash fastboot shrm shrm.img
flash fastboot system system.img
flash fastboot system_ext system_ext.img
flash fastboot tz tz.img
flash fastboot uefisecapp uefisecapp.img
flash fastboot vbmeta vbmeta.img
flash fastboot vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash vendor_boot vendor_boot.img
flash fastboot xbl xbl.img
fastboot flash xbl_config xbl_config.img
Step 5: If you have not had any errors, then you can run the command below to boot your device onto the operating system.
Code:
fastboot reboot
Well done , you have just debricked your Nothing Phone 1 by flashing the stock firmware via the fastboot commands.
I hope this tutorial has helped you find your Phone(1).
Thanks
Reserved
FILES FOR NOTHING OS - (stock-boot, etc. )
UPDATE 15/12/2022
Stock_Boot for Nothing OS here
Be carefull, be sure to select the good Stock Boot "Global" or "EEA" for your device.
Extract Payload.bin via Payload Dumper Go
To start, download the payload-dumper-go 1.0.0 from Github [Credits: XDA Member @ssssut].
Then extract it to any convenient location on your PC. The file name will be something like payload-dumper-go_1.0.0_windows_amd64.
Rename it to payload-dumper-go.
Next, download the liblzma-5.dll file and transfer it to the same folder where the payload-dumper-go.exe file is located.
After that, transfer the payload.bin file to this folder as well.
So, from now on, you should have the 3 files payload-dumper-go.exe, payload.bin and liblzma-5.dll in one folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to the address bar of that folder, type "cmd" and press Enter. This will launch the command prompt window.
Type the command below to extract the payload.bin file:
Code:
payload-dumper-go payload.bin
The extraction process will now begin and will only take a few seconds.
Once this is done, all extracted files will be placed in a folder named extract_date_time which is created in this directory like this name : extracted_20220731_145751
The process is very simple and very fast. Anyone can do it. So don't hesitate, you have everything you need to do this yourself.
it's up to you now
If this has helped you, and if you appreciate my help.
Thanks
Is it possible to relock the bootloader?
Is it possible to relock the bootloader on an third party ROM?
@Sib64 does the device keep Widevine L1 when the bootloader has been unlocked?
Krullendhaar said:
Is it possible to relock the bootloader?
Click to expand...
Click to collapse
Yes.
Krullendhaar said:
Is it possible to relock the bootloader on an third party ROM?
Click to expand...
Click to collapse
No.
Could you also do a tutorial on how to update the OS when you're rooted?
I hope to find an EDL QPST full rom... better to stay safe and restore It in any case...
Mod is coming...
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Is rooting success with 1.1.0 Rom?
Naveenakash said:
Is rooting success with 1.1.0 Rom?
Click to expand...
Click to collapse
I didn't try it with an actual app, but it was showing properly in Magisk. But bootloader needs to stay unlocked.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Did you fix that issue?
Naveenakash said:
Did you fix that issue?
Click to expand...
Click to collapse
I didn't. I'm trying to factory reset the phone, but I can't seem to flash the ROM from bootloader.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
No matter from which partition (A/B)
lba810701 said:
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
Click to expand...
Click to collapse
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
And what if you flash back the original bootloader to over the unlocked one, and after it you close it, not the modded one?
ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
Also, doing a factory reset from recovery doesn't relock the bootloader either.
I've tried now to sideload the .zip but it seems that even the supposed 1.1.0 full OTA zip available in the other post is older than my current ROM, so it can't be flashed like that. I'll have to wait for the next update.