Database Info

Yota 3+ root,twrp, updates - YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev

Please put in this thread all the news about our yota3+ so we can update and custom safely together.

This is the first update that i know, still not tested by me:
Originally Posted by Allleeexxx5
Who can try this files on his Y3+ ? It is a test version. It can break your phone.
Better ask to Allleeexxx5
Quote:
fastboot flash boot boot.img
https://drive.google.com/file/d/1Rez...RGc9WOKna/view

I have not still download the 2 OTA update.
Anyone has tested, any issues?

paolinger said:
This is the first update that i know, still not tested by me:
Originally Posted by Allleeexxx5
Who can try this files on his Y3+ ? It is a test version. It can break your phone.
Better ask to Allleeexxx5
Quote:
fastboot flash boot boot.img
https://drive.google.com/file/d/1Rez...RGc9WOKna/view
Click to expand...
Click to collapse
Ok How do I get this installed on my YotaPhone 3+ 64 Gb?
Please give me some instructions, I have updated from the YotaPhone 3 Chinees to the YotaPhone 3+ but after this update the IMEI's are empty and I need to add them it looks now I need to root to be able to add the IMEI from the box it came with.
If you have a tool to re-enter the IMEI without rooting is the best, but it look the only way to do this is to root the YotaPhone 3+

HvMES said:
Ok How do I get this installed on my YotaPhone 3+ 64 Gb?
Please give me some instructions, I have updated from the YotaPhone 3 Chinees to the YotaPhone 3+ but after this update the IMEI's are empty and I need to add them it looks now I need to root to be able to add the IMEI from the box it came with.
If you have a tool to re-enter the IMEI without rooting is the best, but it look the only way to do this is to root the YotaPhone 3+
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2317790

fastboot oem unlock-go
to unlock

Yota 3+ Root
Instruction 1: Magisk system-less root (ref: https://www.xda-developers.com/what-is-magisk/), which is less invasive as it doesn't have to remove user data, but more fragile if something goes wrong on your system (e.g you will attempt to modify your storage outside of booted OS), you will have to fully re-install your OS. But is less detectable by apps and playstore that your device is rooted, which is good.
Instruction 2: Full root which includes TWRP, Magisk and disabled storage encryption, meaning you can freely modify your storage outside of booted OS and if something goes wrong your will be able to boot into TWRP and potentially fix the issues / make or restore backups . But this method has to remove and fully re-install your system to work.
Note: leaving your device unencrypted is not secure as if your device is lost then your personal data can be retrieved from it. Hence, once you've done installation of all rooted apps and ensured that everything is working fine in long term (e.g couple of days) it is recommended to do following:
- Encrypt your device (Settings > Security & location > Encryption & credentials > Encrypt phone)
- Lock boootloader (Settings > System > Developer options > OEM unlocking > OFF)
This will make your device secure again, but note that you will not be able to modify / access user data from TWRP anymore. Moreover, you won't be able to successfully modify system partitions unless you re-apply Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip (https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389)
Instruction 1 - System-less root method
Note: this is a system-less root method, meaning that if you attempt to modify your system partition from custom recovery, then it will fail to boot again!
Pre-reqs (important!):
All you personal data is backed up
Developer options is enabled:
{
"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"
}
USBdebugging is on:
OEM unlocking is on:
adb, fastboot tools are installed on PC
Device pin is enabled (Settings > Security & location > Screen lock > PIN)
Steps:
Get new9008-0112.zip from: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
Extract new9008-0112.zip > copy boot.img to your phone
Boot image is copied to phone:
Install Magisk. : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Open Magisk > Install > Patch Boot Image File > direct to copied boot.img > It will generate a file > Close
Copy created patched_boot.img from device Downloads to your PC:
Run cmd on pc from place where you copied file > adb reboot bootloader > fastboot boot patched_boot.img
Device will boot > Open Magisk app > It will ask you to grant root permission > grant it > Click Install button again > Direct Install (Recommended) > Reboot
Grant permissions:
Click on install button:
Click on install in dialog:
Click on direct install in dialog:
It will patch your boot partition, click reboot:
Observe two green tick boxes are still green after reboot:
Congratulations, your device is now rooted!
Instruction 2 - Yota 3+ 8.1 System Root with TWRP recovery, Magisk and storage encryption disabled
I've managed to create a TWRP specific for Y3+ and wrote .bat script which automatically re-installs OS 8.1 with latest ota 54 update, magisk and root and disables storage encryption.
Pre-recs (Important!):
Your phone is charged to at least 50%
adb, fastboot installed on your pc and accessible through home path system environment variable
adb debugging enabled
Developer options > OEM unlocking > ON
backup all your personal data
Steps:
Download: mega.nz/#F!yMBGBYIY!24gGnv0DXNhqBvE7IbrEmA
Double click on install.bat
Follow on-screen instructions
Important! As soon as you are on home screen browse your e-ink screen at least once, otherwise the OS might crash after ~ 5-10 minutes due to inability to properly access its launcher. Once done, Reboot your device.
References:
The work is done based on:
- TWRP repacking using Android.Image.Kitchen.v3.4-Win32.zip from: https://forum.xda-developers.com/showthread.php?t=2073775 thanks to @osm0sis
- TWRP for Y3 from: https://forum.xda-developers.com/yotaphone-3/development/yota3-firmware-root-magisk-t3830405 thanks to @gor516don
- new9008-0112.zip from: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999 thanks to @paolinger
- Disabling storage encryption using Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip from: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 thanks to @Zackptg5

vvinjj said:
Pre-reqs (important!):
All you personal data is backed up
Developer options is enabled
adb debugging is on
OEM unlocking is on
adb, fastboot tools are installed on PC
Steps:
Get new9008-0112.zip from: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
Extract new9008-0112.zip > copy boot.img to your phone
Install Magisk: https://******************/downloading-magisk-manager
Open Magisk > Install > Path Boot Image File > direct to copied boot.img > It will generate a file > Close
Copy created patched_boot.img from device Downloads to your PC
Run cmd on pc > adb reboot bootloader > fastboot boot patched_boot.img
Device will boot > Open Magisk app > Install > Direct Install (Recommended) > Reboot
Congratulations, your device is now rooted!
Click to expand...
Click to collapse
Hi I have tried all but it is not clear to me I'm not able to root the YotaPhone 3+.
If it possible to give me a more clear instruction step by step. Also how to test if it is rooted?
It was a YotaPhone 3 and I updated it successful to the YotaPhone 3+ only I lost the IMEI 1 and 2. To add them I need to rood the Phone to add the EMEI or is there a option to add them NOT rooted.
Please help!!

vvinjj said:
Pre-reqs (important!):
All you personal data is backed up
Developer options is enabled
adb debugging is on
OEM unlocking is on
adb, fastboot tools are installed on PC
Steps:
Get new9008-0112.zip from: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
Extract new9008-0112.zip > copy boot.img to your phone
Install Magisk: https://******************/downloading-magisk-manager
Open Magisk > Install > Path Boot Image File > direct to copied boot.img > It will generate a file > Close
Copy created patched_boot.img from device Downloads to your PC
Run cmd on pc > adb reboot bootloader > fastboot boot patched_boot.img
Device will boot > Open Magisk app > Install > Direct Install (Recommended) > Reboot
Congratulations, your device is now rooted!
Click to expand...
Click to collapse
All nice but if I do so on point 7. and it reboot it ask me for a pincode.
What is the pincode? or code I have to enter?

HvMES said:
All nice but if I do so on point 7. and it reboot it ask me for a pincode.
What is the pincode? or code I have to enter?
Click to expand...
Click to collapse
Before attempting to root the device I already had fingerprint / pin setup, hence just simply needed to re-enter the pin in that case. But, I was not sure if it is a must. Unfortunately, to fix it you will need to reset your os, using same steps as in https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999. Then ensure your device has pin installed, and then re-try rooting steps. I've updated my post with pin pre-req step.
---------- Post added at 04:12 PM ---------- Previous post was at 04:06 PM ----------
HvMES said:
Hi I have tried all but it is not clear to me I'm not able to root the YotaPhone 3+.
If it possible to give me a more clear instruction step by step. Also how to test if it is rooted?
It was a YotaPhone 3 and I updated it successful to the YotaPhone 3+ only I lost the IMEI 1 and 2. To add them I need to rood the Phone to add the EMEI or is there a option to add them NOT rooted.
Please help!!
Click to expand...
Click to collapse
To determine if you're device is rooted you will see in Magisk app two green tickboxes (Latest Version: v18.0; Installed Version: v18.0) even after you reboot your device.
Please specify what steps you're unclear about, but before doing that please read through comments in: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999 or google the step you're unclear about (especially pre-req ones)

vvinjj said:
Before attempting to root the device I already had fingerprint / pin setup, hence just simply needed to re-enter the pin in that case. But, I was not sure if it is a must. Unfortunately, to fix it you will need to reset your os, using same steps as in https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999. Then ensure your device has pin installed, and then re-try rooting steps. I've updated my post with pin pre-req step.
---------- Post added at 04:12 PM ---------- Previous post was at 04:06 PM ----------
To determine if you're device is rooted you will see in Magisk app two green tickboxes (Latest Version: v18.0; Installed Version: v18.0) even after you reboot your device.
Please specify what steps you're unclear about, but before doing that please read through comments in: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999 or google the step you're unclear about (especially pre-req ones)
Click to expand...
Click to collapse
Well I did now with a password and it looked OK but still it is not rooted.

has root been yota phone 3+ yet?
I have followed the instructions many times but still cannot succeed

Yota 3+ Stock Recovery access
1. On the phone off, press and hold the "Volume up" and "Power" keys
2. A robot will be lying with an open belly and an error on the lack of a command.
3. Lock the "Volume Down" and "Power" buttons, briefly pressing the "Volume Up" button

Yota 3+ 8.1 System Root with TWRP recovery, Magisk and storage encryption disabled
Merged 2nd instruction into 1st post.

I've tried the latest instruction; failed in cmd as following :
"Ensuring the bootloader is unlocked..."
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
Anyone?

nnlife82 said:
I've tried the latest instruction; failed in cmd as following :
"Ensuring the bootloader is unlocked..."
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
Anyone?
Click to expand...
Click to collapse
Can you check if in developer options OEM unlocking is ON (as in first instruction > pre-recs > step 4).

vvinjj said:
Can you check if in developer options OEM unlocking is ON (as in first instruction > pre-recs > step 4).
Click to expand...
Click to collapse
Yes, it's on.
So technically I don't have to unlock bootloader first right?

nnlife82 said:
Yes, it's on.
So technically I don't have to unlock bootloader first right?
Click to expand...
Click to collapse
If it was ON, the expected message in script should've been "Already unlocked" instead of message you've seen ("Need wipe userdata. Do 'fastboot oem unlock-go"). Maybe because in my case I had already unencrypted userdata at point of re-testing the script, it was working for me. Hence, I will fix the script by replacing "fastboot flashing unlock" to "fastboot oem unlock-go" to see if it fixes the issue for you.
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
vvinjj said:
If it was ON, the expected message in script should've been "Already unlocked" instead of message you've seen ("Need wipe userdata. Do 'fastboot oem unlock-go"). Maybe because in my case I had already unencrypted userdata at point of re-testing the script, it was working for me. Hence, I will fix the script by replacing "fastboot flashing unlock" to "fastboot oem unlock-go" to see if it fixes the issue for you.
Click to expand...
Click to collapse
I've updated the script, please re-download install.bat

vvinjj said:
If it was ON, the expected message in script should've been "Already unlocked" instead of message you've seen ("Need wipe userdata. Do 'fastboot oem unlock-go"). Maybe because in my case I had already unencrypted userdata at point of re-testing the script, it was working for me. Hence, I will fix the script by replacing "fastboot flashing unlock" to "fastboot oem unlock-go" to see if it fixes the issue for you.
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
I've updated the script, please re-download install.bat
Click to expand...
Click to collapse
Thx dude, trying it.:fingers-crossed:
ps I just tried instruction 1 . When it told me to enter the pin after reboot, I did, but it says it's wrong. Can't boot, so reflashing now:silly: My phone is absurd lol

nnlife82 said:
Thx dude, trying it.:fingers-crossed:
ps I just tried instruction 1 . When it told me to enter the pin after reboot, I did, but it says it's wrong. Can't boot, so reflashing now:silly: My phone is absurd lol
Click to expand...
Click to collapse
Before you did the instruction 1 attempt, one of pre-recs was that your device had already pin setup (Settings > Security > Screen lock > PIN), did you have it? As the only use case I am aware of this situation is if you didn't have pin setup before. It would still ask you for pin, but it does't exist, hence wrong.

Related

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/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=+2]Moto X Pure[/SIZE]​
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. 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:\SDK\android-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
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'll find Motorla drivers here, download it and install, then reboot your PC.
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 fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (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 this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)​
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
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. Wipe the cache/dalvik, hit the back button, and 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=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me

This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk

Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes

This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.

Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?

You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?

Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery

elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.

Oops

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588

Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/

I flashed SU and it didn't give me root, any suggestions?

mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?

Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.

mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.

Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.

mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?

Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.

mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.

Hi,
i want to share a rooting method for Android 6.0 with SuperSu 2.78.
It's tested on my XT1642 and on XT1622, XT1625, XT1640, XT1643, XT1644 from other users.
I am not responsible for any damage or failure on your smartphone.
Requirements:
Unmodified System
Unlocked Bootloader
Minimal ADB & Fastboot
Motorola Drivers
TWRP - Custom Recovery
SuperSU-v2.78-SR1
Optional:
Guide to remove "unlocked bootloaderwarning" - use the "V2" version.
You want to install a OTA-Update after Rooting? -> [GUIDE] Sucsessful OTA-Update after Rooting
1. Unlock your Bootloader:
Follow this Link
2a. Connect your phone to your computer and boot into TWRP:
Code:
adb reboot-bootloader
Code:
fastboot boot twrp-3.0.2-0-athene.img
2b. If you want to flash TWRP you can use the follow code. But then you can't install OTA-Updates without flashing stock recovery again.
For rooting your Moto G it is not necessary to flash TWRP!
Code:
fastboot flash recovery twrp-3.0.2-0-athene.img
3. Make a backup of your unmodified system:
TWRP -> Backup -> Select all Partitions -> Swipe to Backup
{
"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"
}
4. Save your Backup on your computer or somewhere else
5. Write a ".supersu" file for systemless rooting:
TWRP -> Advanced -> Terminal -> Type the follow code:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
6. Make sure the .supersu file is in /data.
TWRP -> Advanced -> File Manager -> /data
7. Install SuperSU.zip
TWRP -> Install -> SuperSU-v2.78.zip
8. Reboot your Moto G4
If something went wrong while flashing SuperSU, you can always restore your backup with booting into TWRP.
I hope someone can confirm this method on other versions of the G4 (Plus).
Updating SuperSU without TWRP (or a PC) via FlashFire
For updating SuperSU you can wait till the new versions hits the Play Store or you can flash it via FlashFire when you didn't flash TWRP permanetly.
1. Install FlashFire:
Play Store: FlashFire by Chainfire
2. Download lastest SuperSU.zip:
http://download.chainfire.eu/supersu
3. Start FlashFire and add "Flash ZIP or OTA":
4. Disable "Mount /system read/write" checkbox:
5. Disable all "Ever Root" options and hit the "Flash" Button:
Changelog:
1. You can update the SuperSU app via Play Store to 2.76 and let it update the binary's.
2. The first step is now "Unlock your Bootloader", for everyone that are unable to follow instructions properly and stuck on booting up into TWRP with an locked Bootloader.
3. Updated to SuperSU 2.78.
4. New guide for removing "unlocked bootloaderwarning", without the visable "N/A:" in the logo.
5. Added guide for Updating SuperSU via FlashFire without TWRP.
6. Updated pictures in the thread.
7. New GUIDE for install OTA-Updates after rooting.

Great news.. any side effects?
Sent from my Moto G (4) using Tapatalk

Nope, everything works perfect.

Just to say.... i've just done this on a XT1622 and i've got root access....
i've noticed that you only did
fastboot boot twrp-3.0.2-0-athene.img
and not flash it permanently... is there a reason for this..? Allows for official updates etc?
fastboot flash recovery twrp-3.0.2-0-athene.img
thanks

Nice to hear that
When the unroot option in the SuperSU app is working correctly, there is a high chance to get a OTA-update and install it.
With custom recovery there is no chance to install an update.

Does Android Pay work after the systemless root? Thx

Is android pay working without NFC?
I can't use it here in germany, so I don't know if it is working after rooting.

Bender1987 said:
Is android pay working without NFC?
I can't use it here in germany, so I don't know if it is working after rooting.
Click to expand...
Click to collapse
Android Pay needs NFC to work as it's classed as contactless payment no NFC it can't communicate with the device

Very nice guide
---------- Post added at 01:57 PM ---------- Previous post was at 01:51 PM ----------
Very nice guide

Apologies if my question is out of place, but what do I need to do to make this work on an XT1640?
Do I have to modify any files, or anything like that?
Thanks!

minidude2012 said:
Android Pay needs NFC to work as it's classed as contactless payment no NFC it can't communicate with the device
Click to expand...
Click to collapse
Argh. Could have sworn up/down that NFC was included in the XT1644. Checked. You are right! (of course). Foo.

bishteca said:
Apologies if my question is out of place, but what do I need to do to make this work on an XT1640?
Do I have to modify any files, or anything like that?
Thanks!
Click to expand...
Click to collapse
Read the steps in OP.
Boot into TWRP -> make a backup -> write a file with "systemless=true" -> flash SuperSU 2.74-2.zip -> reboot -> done
There are no need to modify any file on your own. SuperSU modify the boot.img.

Cannot boot into TWRP
I have a Motorola Moto G4 (2016 model) on Talkmobile.
I have enabled "Developer Options", enabled USB Debugging, and set "Allow Bootloader to be Unlocked" to "Yes".
When I try to follow your rooting instructions, I get as far as "fastboot boot twrp-3.0.2-0-athene.img", and I get the error message:
C:\Program Files\Minimal ADB and fastboot>fastboot boot twrp-3.0.2-0-athene.img
downloading 'boot.image'...
OK [0.398s]
booting...
FAILED (remote failure)
finished. total time: 0.403s
Any ideas what causes this (and how to overecome it).
Please keep solution as simple as possible, with full detailed instructions. I am a total novice regarding Android rooting (although very familiar with PCs and Windows).
I tried Kingo Root, but that failed also

Have you actually unlocked your bootloader? I.e gone to the Motorola website etc.. see other sections on this forum for details
See here for details
(Fixed url)
http://forum.xda-developers.com/showthread.php?p=67031801
Sent from my Moto G (4) using Tapatalk

Cannot Boot into TWERP
Thanks Stehaworth.
That was my error - I hadn't unlocked the bootloader. I thought that by setting the "Enable Bootloader to be Unlocked" key to "Yes" in Developer Options that the phone would unlock itself.
I've now managed to root the phone using the instructions, but now have an annoying message on bootup:
"Your Device has been unlocked and can't be trusted
To Learn More Visit: motorola.com/unlockbootloader"
Any ideas on how to get rid of this message?
The phone itself seems to be working OK.

will this method wipe the entire data of the phone? is there any method to root it without losing any data?

yash1331 said:
will this method wipe the entire data of the phone? is there any method to root it without losing any data?
Click to expand...
Click to collapse
Nope, not yet.
Make a backup from your data and then unlock the bootloader.

Hmmm, just tested with the xt1622 and the installation of twrp doesn't seem permanent. Can't reboot into recovery. Also the 'unlock' message isn't what I expect (and Motorola indicates) Instead of the white background with the regular message I get a black background with in yellow 'your device can't be trusted, will boot in 5 seconds'.
BTW I found it, "fastboot flash recovery <img>" flashes, boot just boots.

T_I said:
Hmmm, just tested with the xt1622 and the installation of twrp doesn't seem permanent. Can't reboot into recovery. Also the 'unlock' message isn't what I expect (and Motorola indicates) Instead of the white background with the regular message I get a black background with in yellow 'your device can't be trusted, will boot in 5 seconds'.
BTW I found it, "fastboot flash recovery <img>" flashes, boot just boots.
Click to expand...
Click to collapse
Yeah, it is not necessary to flash TWRP when you only want to root your G4.
I updated the OP with a link to guide to remove the unlocked warning.

Bender1987 said:
Yeah, it is not necessary to flash TWRP when you only want to root your G4.
I updated the OP with a link to guide to remove the unlocked warning.
Click to expand...
Click to collapse
Thanks, works nicely, from the "ID: n/a" text only the is a is barely visible in the M from moto. Looks a lot better though.

!!! YOUR WARRANTY IS NOW VOID !!!​
THIS TOOL IS FOR CUBOT NOTE PLUS ONLY.
neither I nor the XDA Forum is responsible for your phone brick or your cat triggers an atomic apocalypse. YOU has been responsible for your phone and you are doing everything at your own risk.​
This is a tool for rooting the CUBOT NOTE PLUS ONLY.
NOTE: THIS TOOL IS IN ALPHA STAGE
RoCuNo+_v0.3 is online.
Downloads see post 2
This tool can root your Cubot Note Plus and patch your boot.img for working with Magisk.
this tool can make this in seperate steps or All-In-One. For now the bootloader must stay UNLOCKED for root to work.
A guide to doing this by yourself with adb is also in this post.
NOTE: ALL YOUR DATA GET LOST. SAVE YOUR IMPORTANT DATA FIRST. (Videos, Pictures, Music and all you can save.)
What this tool can do:
Unlock/Relock your Bootloader
Root/Unroot your Cubot Note Plus (Unroot dont work for now)
[*]Make a Dump of your Boot Partition as boot.img
Install MagiskManager-v5.4.3 and Magisk-v14.0
Please download the attached zip and unzip it somewhere and rightclick on RoCuNo+_V*.bat and start as Administrator.
Read all carefully and choose your option. Follow the instructions on screen STEP BY STEP!!!
Better way is to choose the AIO because that makes all for you except a few steps.
Downloads see post 2
GUIDE
OEM UNLOCK + ROOT + MAGISKMANAGER APP
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. go in RoCuNo+ Directory on PC
08. press Shift + Right Mouse Click
09. Open Command Prompt here
10. type
Code:
adb reboot-bootloader
11. type [ODE]fastboot oem unlock[/CODE]NOTE: ALL YOUR DATA WILL BE DELETED
12. press VOL+ Button on phone to oem unlock
13. type
Code:
fastboot flash boot patched_boot.img
14. type
Code:
fastboot reboot
15. if you have unlocked your bootloader, make your setup
16. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
17. enable "USB DEBUGGING" (Go to "Menu --> Settings --> Developer Options")
18. type
Code:
adb install -r -d -g MagiskManager-v*.*.*.apk (set the Version numbers for *)
OEM LOCK
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. go in RoCuNo+ Directory on PC
08. press Shift + Right Mouse Click
09. Open Command Prompt here
10. type "adb reboot-bootloader"
11. type "fastboot oem lock"
12. press VOL+ Button on phone to oem lock
13. type "fastboot reboot"
UNROOT
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. Download SP Flashtool and Firmware for Cubot Note Plus
08. Start SP Flashtool and choose the MT6737T_Android_scatter.txt from the Cubot Note Plus Firmware Folder.
09. Turn off the Cubot Note Plus.
10. Click on Downloadbutton and connect the Cubot Note Plus to PC.
NOTE: ALL YOUR DATA WILL BE ERASED. MAKE A BACKUP IF YOU NEED.
11. After Flashing is complete, reboot Phone.
Old Guide
Save your data.
Connect your phone to PC and make sure all drivers are installed. (Boot up to normal system, recovery and fastboot to get sure.)
Open a CMD Prompt on your PC and switch to Directory where you have unzipped the RoCuNo+. (e.g. C:\Users\YourName\Desktop\RoCuNo+ or You can go to RoCuNo+ folder and Shift+Rightclick on empty space and click "open Command Prompt here".)
Type:
Code:
adb reboot-bootloader
Than:
Code:
fastboot oem unlock
NOTE: ALL YOUR DATA WILL BE DELETED
Press VOL+ on Phone if asked
wait for device for unlock
Type:
Code:
fastboot reboot
Setup your phone until you come to system.
Enable "Developer Options" Menu. Go to Menu --> Settings --> About Phone and tap Built Number 7 times until a message appears that you are now an Developer.
Enable USB DEBUGGING and OEM UNLOCKING in Menu --> Settings --> Developer Options.
Enable UNKNOWN SOURCES in Menu --> Settings --> Security
Copy MTK-Engineering-Mode.apk and MagiskManager-v5.4.0.apk on your and install this to apps.
open the MTK-Engineering-Mode app tap on MTK Settings and swipe to Log and Debugging.
Tap on User2Root and than the Root button.
NOTE: UNPLUG AND RECONNECT YOUR PHONE. DONT CLOSE THIS APP OR DO SOMETHING ON THE PHONE. YOU LOSE YOUR ROOT IF YOU DO SOMETHING.
Go back to CMD Prompt on PC and type:
Code:
adb root
adb shell dd if=/dev/block/mmcblk07p of=/sdcard/boot.img
Now open MagiskManager app and tap the Install button.
Choose to inject in boot.img
Point Magisk to the boot.img.
after Magisk has succssesfully patched the boot.img it will copy it to /sdcard/MagiskManager/patched_boot.img.
Copy your boot.img from sdcard AND the patched_boot.img from sdcard/MagiskManager to the RoCuNo+ folder on your PC.
Go to CMD Prompt and type:
Code:
adb reboot-bootloader
than type:
Code:
fastboot flash boot patched_boot.img
when flashing is ready, type:
Code:
fastboot reboot.
on phone go to MagiskManager app and check if Magisk and Root are on green state.
You succssesfully have rooted your Cube Note Plus.
Take care of the boot.img and the patche_boot.img in case we need them on some day.
DONT RELOCK YOUR PHONE BECAUSE YOU CANT WRITE ON /SYSTEM PARTITION WITH LOCKED BOOTLOADER. (for now.)
I hope that helps many people with his/her phone and maybe someone can make TWRP or a Custom Rom for our phone. Now the Door is Open.
if someone found better solution for some tasks here please let us know.
Changelog
RoCuNo+ v0.3
Delet the Unroot Section because it doesent work for now.
update Magisk Manager App to 5.4.3.
Update Guide.
Update patched_boot.img.
RoCuNo+ v0.2
complete rework.
all should now work.
now the original verified-boot.img from Cubot is implemented. so root and unroot works now.
ive patched the original verified-bood.img with magisk so no boot.img dump has to be made.
the tool now detects what state you are and boots the state needed for his job.
only magisk manager app has to be installed on device and the tool do this for you.
the tool detects if you are already oem unlocked or not. so if you already unlocked you dont
need to do that again. it also detects in witch state your phone and boots the right mode.
Credits to XDA-Developer Schwester_Gabi (https://forum.xda-developers.com/member.php?u=5264039) and the Flampinko.IT Team ([email protected])
you can use this tool on your own risk but its not allowed to share this tool in other forums or blogs or something. but you can write about this tool and link
than over to the XDA-Developer Forum under (https://forum.xda-developers.com/android/general/guide-cubot-note-plus-mtk6737t-root-t3695272)
it is also not allowed to copy the code or change anything in this programm. Only Schwester_Gabi or the Flampinko.IT Team is allowed to change the code.
If you have any Ideas to implement in this tool than post it over to XDA-Developers Forum (https://forum.xda-developers.com/android/general/guide-cubot-note-plus-mtk6737t-root-t3695272)
or send us an Email ([email protected]). If you like our work please make a donation to help us.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZXVV3MZX2NVK6
please respect the developers work and stick to the rules.
Credits and special thanks to:
topjohnwu for the awesome Magisk
themonsterit for MTK-Engineering-Mode App
Schwester_Gabi for finding the way and coding the RoCuNo+ programm
all the people who write solutions for problems that i read to find the way too root.
XDA-Developer Team to giving us such a great Platform to share our stuff with the world.

Cubot Note Plus Stock Rom:
V8:
Mirror 1
V7:
Mirror 1 / Mirror 2
SP Flash Tool for Cubot Note Plus Stock Rom:
Mirror 1 / Mirror 2
Cubot Note Plus Stock Scatter File for flashing:
Mirror 1 / Mirror 2
RoCuNo+_v0.1(Alpha):
Mirror 1 / Mirror 2
RoCuNo+_v0.2:
Mirror 1 / Mirror 2
RoCuNo+_v0.3:
Mirror 1

Problems:
i got some problems with dumping boot.img. the partiton size is 16M and the dd dump is also 16M but if i try to flash it back fastboot says the file is to large for partition. thats why unroot doesent work for now. Magisk patch the boot.img and resize them to 8M. than flashing works fine and all works. if someone can point me in the right direction would be very nice. if you have some questions please write here or pm me.
if someone can make a scatter file for this phone or had the scatter file it would be nice to share so we can try to backup the phone with SP Flash Tool. thanks.
if you found some bugs please tell it here so i can fix it.

Nice

Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)

Matthius said:
Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)
Click to expand...
Click to collapse
not now. i hope that someone can make an TWRP or CWM for the Cubot and share it with us.

Matthius said:
Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)
Click to expand...
Click to collapse
did you use the RoCuNo+ Programm or have you done all by yourself ? what do you use ? step by step or the AIO routine ?

Schwester_Gabi said:
did you use the RoCuNo+ Programm or have you done all by yourself ? what do you use ? step by step or the AIO routine ?
Click to expand...
Click to collapse
I had already unlocked the bootloader myself prior to this, looking for a way to root it before I saw this article (I gather this is the first available root method for this device), and also manually installed MagiskManager and the MTK-Engineering-Mode apk's and from then on I used the ruCuNo+ bat to complete it.
I followed stage 6, then 7, then 3. Pointed the Magisk to the original boot img, got it patched, sent it to PC and flashed the boot image with ADB. After turning on the phone, Magisk ended up with two green ticks so everything was good to go.
{
"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"
}

Matthius said:
I had already unlocked the bootloader myself prior to this, looking for a way to root it before I saw this article (I gather this is the first available root method for this device),
Click to expand...
Click to collapse
yes it is. i searched over a week to find a root solution but nothing found. so i make it by my self and want to share this with the world :highfive:
Matthius said:
and also manually installed MagiskManager and the MTK-Engineering-Mode apk's and from then on I used the ruCuNo+ bat to complete it. I followed stage 6, then 7, then 3. Pointed the Magisk to the original boot img, got it patched, sent it to PC and flashed the boot image with ADB. After turning on the phone, Magisk ended up with two green ticks so everything was good to go.
Click to expand...
Click to collapse
thats also a way :good: maybe i implement this for users who already unlockt the bootloader. then the the phone must not be factory reset again. :good: thanks for telling me this way i dont think of bevor

Schwester_Gabi said:
yes it is. i searched over a week to find a root solution but nothing found. so i make it by my self and want to share this with the world :highfive:
thats also a way :good: maybe i implement this for users who already unlockt the bootloader. then the the phone must not be factory reset again. :good: thanks for telling me this way i dont think of bevor
Click to expand...
Click to collapse
No worries, great work - hopefully, we may see some custom recovery to come in the future from someone. Wish this phone actually had its own page on XDA, but I doubt it has enough widespread support for that, who knows.

Matthius said:
No worries, great work - hopefully, we may see some custom recovery to come in the future from someone. Wish this phone actually had its own page on XDA, but I doubt it has enough widespread support for that, who knows.
Click to expand...
Click to collapse
Yes. custom recovery for the phone would be great. if I knew better, I would make one myself. but I've read a lot. maybe I'll try it in future to make one.
i think this phone dont get his own page. but maybe the Cubot vendor get his own where we can put all related Cubot threads together in his own sub section. :good:

i got a error after "fastboot oem unlock" -> "FAILED (remote:Unlock operation is not allowed)". i think, bootloader is not unlocked, what can i do?
oops: had forget "OEM UNLOCKING in DevMenu"

spunky1a said:
i got a error after "fastboot oem unlock" -> "FAILED (remote:Unlock operation is not allowed)". i think, bootloader is not unlocked, what can i do?
oops: had forget "OEM UNLOCKING in DevMenu"
Click to expand...
Click to collapse
yes. that was the point. :good:

I think the sequence in the Guide is a bit wrong. In the Guide I read:
Schwester_Gabi said:
...
Type:
Code:
adb reboot-bootloader
Than:
Code:
fastboot oem unlock
NOTE: ALL YOUR DATA WILL BE DELETED Press VOL+ on Phone if asked wait for device for unlock...
... (this comes now after)
Enable USB DEBUGGING and OEM UNLOCKING in Menu --> Settings --> Developer Options
...
Click to expand...
Click to collapse
If I follow this I get (in very small fonts) as another user here in this thread:
Unlock failed...return to fastboot in 3s
Click to expand...
Click to collapse
And no unlock of the bootloader seems possible.
Because first I need to do OEM UNLOCKING in the Dev. Options, which seems very clear. Only after I can fastboot oem unlock
What I further not quite understand in this post, is it either the Guide or the Batchfile I have to follow? Or is it a mixture of both what I need to do?
As I think the Batchfile cannot enable the Developer Tools in the System, or?
Lastly and most important: on my phone I don't see a mmcblk07p only a mmcblk0p7, so this throws an error:
Schwester_Gabi said:
...
adb shell dd if=/dev/block/mmcblk07p of=/sdcard/boot.img
...
Click to expand...
Click to collapse
I guess that mmcblk0p7 is ment, so I did a dd with mmcblk0p7, and I let patch this file with Magisk to the file: patched_boot.img
But here I am very not sure and if I flash now a wrong img-file with this:
Schwester_Gabi said:
...
fastboot flash boot patched_boot.img
...
Click to expand...
Click to collapse
I strongly guess that is it with my new phone
So could you please confirm that it was just a typo in the first post here?
How can I know which of these files in /dev/block is the boot.img?
Thank!!!

francwalter said:
I think the sequence in the Guide is a bit wrong. In the Guide I read:
...
Type: Than:
If I follow this I get (in very small fonts) as another user here in this thread:
And no unlock of the bootloader seems possible.
Because first I need to do OEM UNLOCKING in the Dev. Options, which seems very clear. Only after I can fastboot oem unlock
Click to expand...
Click to collapse
For this Problem the batch says first enable dev options and OEM unlock and than go to next step.
francwalter said:
What I further not quite understand in this post, is it either the Guide or the Batchfile I have to follow? Or is it a mixture of both what I need to do?
As I think the Batchfile cannot enable the Developer Tools in the System, or?
Lastly and most important: on my phone I don't see a mmcblk07p only a mmcblk0p7, so this throws an error:
I guess that mmcblk0p7 is ment, so I did a dd with mmcblk0p7, and I let patch this file with Magisk to the file: patched_boot.img
But here I am very not sure and if I flash now a wrong img-file with this:
I strongly guess that is it with my new phone
So could you pleas confirm that it was just a typo in the first post here?
How can I know which of these files in /dev/block is the boot.img?
Thank!!!
Click to expand...
Click to collapse
Yes. Its a typo. You can flash it.
Btw i am on the way to rework the whole Programm for better use and better instructions. Give me some time because iam very busy at the moment. But I will update it soon.
And remember its an 0.1ALPHA for now. So its not perfect :angel:

Oh Great! It works
Thank a lot for your work!!!

As a noob, I did not get what to do after installing the Magisk manager. So I have it installed, but it shows no root. How can I then install the root?
I used the "RoCuNo+_v0.2.bat" in admin mode and although I got through the unlock and root, I am stuck on what to do on Magisk in the phone.
I was able to root my galaxy tab, but perhaps I am too noob for these instructions?
(Btw while booting I get the "this phone is unlocked and cannot be trusted" text)

Ran into a bit of an issue here, I received an official OTA so I uninstalled Magisk by clicking uninstall within the APK, now my phone is stuck on the boot logo. I've tried to flash the original boot img, but I can't get into the system to confirm flashing it on the device. It displays under <adb devices> but when issuing the <fastboot flash boot> command it says <waiting for any device> and nothing occurs.
Not sure how to proceed without wiping the whole thing. Anything I can try?

So I did a factory reset and used the "RoCuNo+_v0.2.bat" again as follows:
First enabled developer mode, USB Debugging unknown sources, OEM unlock
Then ran the tool:
1 - unlock bootloader - success
3 - root - success
5 - install magisk - here the phone first boots, then it erases data, then does again all the "setup your phone, wifi, accounts etc"
"Orange state - this device is unlocked..." appears in the boot
Magisk is not installed in the apps.
OEM unlock is greyed out (but enabled)
So the tool worked differently, or I am missing something.
Perhaps there are new versions of this phone?

...aaaand it's rooted.
I did everything again using the adb -command instructions.
So did not use the .bat tool.
Used the step-by-step instructions.
Thanks a lot! Finally I can use macrodroid properly.

OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!
{
"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"
}
Before you start, OTA up to the latest System Update available.
Settings > System Updates > Download & Install the latest available
Thank You all for your support :highfive:
Never Settle :fingers-crossed:​

Introduction​​
Rooting OnePlus 6 would give you additional benefits like you can install special apps, Flash Custom ROMs & Custom Mods, you can streamline your phone performance and many extra features. The real performance of an Android smartphone can only be unlocked once it is rooted.
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: ​
1. Unlocking the Bootloader
2. Installing a Custom Recovery
3. Gaining Root Access
Each new step relies on the previous step so please follow the entire process and a basic summary of each part is described as below:
Unlocking Bootloader​​Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.​
Installing a Custom Recovery​​A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your device (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Gaining Root Access​​You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries or by Flashing Magisk Zip for a system less root. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed and an unlocked bootloader. This, in my opinion, is the a practical and beneficial method for rooting your phone. It will give you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of the entire process. This method will work regardless of any android version on the phone.
If you are confused by anything in this guide, I highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also we would suggest that you read over the whole thread a few times before actually doing anything to the phone.​

Setup, Preparation & Prerequisites​​
Basic tasks that may be referred to throughout this guide:​​Open Command Prompt: Press Shift + Right Click anywhere on the screen and select Open Command Window here
Enter Fastboot/Bootloader Mode: Turn the phone off. Hold volume up + power until the "fastboot" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot > Bootloader from the power menu.]
Enter Recovery Mode: Turn the phone off. Hold volume down + power until the "OnePlus Logo" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot -> Recovery from the power menu.]
ADB and Fastboot Drivers Installation​1. Download & Update OnePlus 6 Drivers From Here
2. Download & Update Fastboot and ADB Binaries/Drivers from Here
3. Run the .exe file downloaded from above as Administrator.
4. Press 'Y' every time the installer asks for.
5. Continue Driver Installation.
Now, ADB and Fastboot have been installed on your PC and should be Working as desired.
Things To Remember​Show File Extensions
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery
Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long , but its best to have enough charge in case something goes wrong.
Backup (Optional)
Unlocking the bootloader will/should completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
USB Debugging
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Enable Advanced Reboot
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.

Unlocking Bootloader​
Turn the phone off. Then boot it into fastboot mode by holding volume up + power or select reboot to bootloader if advanced reboot is activated via developer options. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember this Step will WIPE EVERYTHING off the phone so Backup all your Data
Code:
fastboot oem unlock
You would be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection
Your device will reboot, show you a Secure boot warning, reboot into stock recovery and wipe all data. Once done, your phone will reboot into the OS.
Please continue and follow the next post to install Custom Recovery

Flashing TWRP Recovery​
Downloads:
Official TWRP Image & Installer Zip
Blu_Spark TWRP
Root
Magisk​
Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation.
Download all the files, place Magisk & TWRP installer zip on Device Internal Memory and TWRP img on your PC
Then boot it into fastboot/bootloader mode by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the same location and run the following commands:
Code:
fastboot boot twrp-3.2.2-0-enchilada.img
You will temporarily boot into TWRP
Now in TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed.
PS: DO NOT BOOT IN OS JUST YET & CONTINUE TO THE ROOTING POST

Gaining Root Access​
This is a continued post from the above post...
1. Boot into TWRP Recovery
2. If you want to stay systemless continue without swiping right else Swipe and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk to root.
5. Swipe to confirm the flash
6. Reboot System
Keep in mind that the first boot after wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot and might reboot a few times.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Congrats! Your Device now has an unlocked bootloader, a custom recovery installed and is rooted !!
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Enjoy :fingers-crossed:

Making a Nandroid Backup​
Warning: before you make a backup with TWRP you must remove all Lockscreen Security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin/pattern/password will result in an "incorrect pin/pattern/password" message), you'll be forced to perform a factory reset to boot into Android.
To remove lockscreen security go to
Settings > Security > Screen Lock and set it to Swipe/None.
A Nandroid Backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back.
You can also use Nandroid Bckup to create a backup of your favorite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
To Create Nandroid Backup:
1. Boot into TWRP Recovery .
2. Go to Backup Menu and select all the listed partitions.
3. Name the Backup if needed (Optional)
4. Swipe to take Backup.
This proces should take 5 to 7 minutes depending upon the size of data.
5. Reboot System when done.
Your Nandroid will be stored in the Backup Folder inside TWRP Folder /sdcard/TWRP/BACKUPS

Restoring a Nandroid Backup​
1. Boot into TWRP Recovery
2. Go to Restore Menu and select the backup you want to restore.
3. Select the partitions you want to restore.
4. Swipe to Restore. The process will take 5 to 7 minutes.
5. Reboot system once done
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Password) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue.
Boot into TWRP
Use the TWRP File Manager and Navigate to /data/sytem/ and delete the following files:
locksettings.db
locksettings.db-shm
locksettings.db-wal.
gatekeeper.password.key
gatekeeper.pattern.key
You may or may not have all the above files so delete the ones you have.
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Upon Boot > Go into Settings > Security > set your preferred unlock method
Android will ask you if you want to set a boot-time code too so select as per convenience.

Making an EFS Backup​All too often, we've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Download & Open up Terminal Emulator on your phone from here
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
Code:
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
This will place two files (modemst1.bin & modemst2.bin) on your internal storage.
Make sure you copy them to your PC and Cloud immediately so that you have a backup there to use if you need to restore it in future.
That's it !! In case you ever need to restore Nanroid or EFS Backups, please continue and follow the next post...

Restoring an EFS Backup​If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Keep modemst1.bin and modemst2.bin (backed up earlier) on your desktop and open command window there.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device.
Code:
fastboot reboot
Now disconnect phone from PC. Your IMEI should be back.
That's it for this guide, Enjoy :highfive:

Full Stock Rom:
OOS 5.1.3:
AFH
Changelog:
* Updated Android Security Patch To May
* Preloaded OnePlus Switch Application
* Added Configuration for Notch Show/Hide
* Camera - Support Super Slow Motion (720p at 480fps and 1080p at 240fps)
* Camera - Support Quick Capture in Portrait Mode
* Gallery - Support more actions for recently deleted files

Thread Opened for Users to Unlock the device for now, TWRP will be updated as soon as its available.
Thank you for your consideration.

Funk Wizard said:
2. If you want to stay systemless continue without swiping right else Swipe and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
Click to expand...
Click to collapse
These two steps seem a bit conflicting when it comes to enabling system modifications in TWRP. Am I right in that if you don't allow system modifications, you can still flash Magisk and get root access but you won't be able to flash custom ROMs?
---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------
Is there a difference between backing up EFS via a terminal emulator rather than just doing it via TWRP?

KnifeFed said:
These two steps seem a bit conflicting when it comes to enabling system modifications in TWRP. Am I right in that if you don't allow system modifications, you can still flash Magisk and get root access but you won't be able to flash custom ROMs?
---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------
Is there a difference between backing up EFS via a terminal emulator rather than just doing it via TWRP?
Click to expand...
Click to collapse
Yes you are right, you can still flash Magisk and get root access if you don't allow modifications. Also there should be no difference between the TWRP EFS backup or the Terminal Emulator EFS backup.
I would still recommend both as backup if you mess up TWRP/OS due to encryption issues, besides that the official twrp for the 6 would still take time so for just wanted to keep both options at your disposal :good:

Funk Wizard said:
Flashing TWRP Recovery​
Click to expand...
Click to collapse
Good to see you here.
Being a device with A/B partitioning, there is no separate /recovery partition as it is fused with /boot. Besides, you've to fiddle with active slots to make it installed. I know the guide is work in progress, but the current state may arise confusions.
Regarding this post, what was the OOS version of the initial build?

Titokhan said:
Good to see you here.
Being a device with A/B partitioning, there is no separate /recovery partition as it is fused with /boot. Besides, you've to fiddle with active slots to make it installed. I know the guide is work in progress, but the current state may arise confusions.
Regarding this post, what was the OOS version of the initial build?
Click to expand...
Click to collapse
The initial build was 5.1.0 which was a test build

Funk Wizard said:
The initial build was 5.1.0 which was a test build
Click to expand...
Click to collapse
Thanks for the confirming my initial speculation.
:highfive:

Funk Wizard said:
Gaining Root Access​
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Click to expand...
Click to collapse
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!

jordanlaa said:
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!
Click to expand...
Click to collapse
You can just take the partial OTAs with unlocked bootloader..
But if you install custom recovery ( twrp) ..then you have to flash the full rom zip anytime that you want to upgrade..

jordanlaa said:
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!
Click to expand...
Click to collapse
As and when you get the device follow the below:
1. Boot up the device and check for system updates
2. Update to the latest available 5.1.3 as of today or whatever latest at the time you have the device.
3. Unlock the bootloader
4. Continue with TWRP flash & Root (Magisk) as by next week TWRP will be available
4. Set up the device the way you want now like installing you preferred apps and setup your device.
5. There on whenever an update comes download the full zip and flash it via twrp instead of partial OTA's
I will make a separate thread for instruction on how to update just like my threads on 5T & 5, links on my signature.
Those will be self explanatory and tested instructions as I happen to have the device with me.
For anything else you are free to discuss here, I may not be available all the time due to work schedule however I will answer all your concerns once I have access to xda.
Thank you for your patience :highfive:

[Guide] Root Pixel 3 XL Android 12 Unlock/Lock Bootloader + Install/Flash Custom ROMs​
Introduction
This Guide is for Pixel 3 XL owners that want to Instal a Custom ROM, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
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 Pixel 3 XL phone with an unlocked bootloader.
The latest Custom ROM.
A Computer with the latest SDK Platform-Tools: r33.0.3 installed.
Important Notes:
Update Platform Tools, regularly, for optimal performance.
Need Google's USB Drivers for your Pixel Phone?
NEW
Waiting . . .
Update(s)
Magisk Alpha - app-release_555a54ec-alpha.apk 2 Sep
Magisk Beta - 25.2 21Jul
Magisk Canary - app-release_a468fd94-25205.apk 11Oct
Magisk Delta - app-release
Magisk Stable - 25.2 21Jul
TWRP - Waiting for Android 12 T.W.R.P
SafetyNet - SafetyNetFix v2.3.1 (Zygisk) 27Jun
SDK Platform-tools - r33.0.3 11Aug
Custom Kernels
Note: If you want to use a Custom Kernel, please follow the Installation instruction in the OP of the Custom Kernel you want to install.[[/I][/U]​a. [Kernel][10.06.2022][4.9.317][Android 12]Kirisakura_S 5.1.1 for Pixel 3/XL aka Bluecross by Freak
​b. Elemental X - check the Elemental X Kernel Manager for updates​
Custom Android 12.x ROMs
[ROM] [UNOFFICIAL] [blueline/crosshatch] [Android12] LineageOS 19.1 Nightly by razorloves​
Custom Android 13 ROMs
a. [ROM] [Android 13] [blueline/crosshatch] ArrowOS 13.0 | UNOFFICIAL | BETA by ReallySnow​b. [ROM][13 BETA][blueline/crosshatch] PixelExperience [AOSP][OFFICIAL] Nightly by ReallySnow​
My Other Guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 1 XL
Credits/Thanks/Recognitions
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (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 fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone (#1)
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
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.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
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
Do not lock the bootloader until you have returned the phone to stock. Failure to do so causes bricked phones.
This will erase all user data from the device!
Boot fastboot mode
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
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Flash Custom ROM with @badabing2003 PixelFlasher
PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones. by badabing2003
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery - TWRP
Waiting for Android 12 TWRP
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap menu icon > Settings > Update Channel > Select Stable, Beta Canary or Custom.
Update Magisk
When Magisk App 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
Install/Update Magisk Modules
Download Modules
Fox Magisk Module Manager Releases
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Fox2Code/Fox Magisk Module Manager
Open Fox2Code/Fox Magisk Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Fox2Code/Fox Magisk Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Alpha/Beta
[ROM] [Android 13] [blueline/crosshatch] ArrowOS 13.0 | UNOFFICIAL | BETA by ReallySnow
Official
[ROM][12][blueline/crosshatch] PixelExperience [AOSP][OFFICIAL] by ReallySnow
[ROM] [OFFICIAL] [blueline/crosshatch] [Android12.1] LineageOS 19.1 by razorloves
Unofficial
None
Mods
Tulsadiver's Mods
None . . .
Others
[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.1 by Didgeridoohan
T.W.R.P. Backup/T.W.R.P Update
Waiting for Android 12 T.W.R.P

Reserved 1

Reserved 2

Reserved 3

Nice guide. It will be very resourceful. I am going to wait to root my 3XL. I tried to follow a couple of guides, but I end up in a boot loop.

Worked great and thanks for the detailed guide
Sent from my [device_name] using XDA-Developers Legacy app

Nice. Root up and running w/o issues. Even got rid of the gesture navigation.
{
"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"
}

can you update the OS via OTA with once you root the phone?

jaxenroth said:
Nice. Root up and running w/o issues. Even got rid of the gesture navigation. View attachment 4624655
Click to expand...
Click to collapse
How do you get past "No Valid Slot To Boot"

State.of.mind said:
How do you get past "No Valid Slot To Boot"
Click to expand...
Click to collapse
Read Section 9.A.3. Need to switch your Magisk Manager over to Canary in order to install Magisk 17.4. Stable channel is v17.2 which is what is causing you to see that error.

JeromeLeung said:
Read Section 9.A.3. Need to switch your Magisk Manager over to Canary in order to install Magisk 17.4. Stable channel is v17.2 which is what is causing you to see that error.
Click to expand...
Click to collapse
Thanks. I tried that method. I'm not sure what's causing it. Could it be that I am not typing "fastboot reboot" at the end of the flash? I normally just press start.

Verify the URL you typed in settings for Canary setup, a typo could have that result maybe. I followed the same instructions and it went right through
Sent from my [device_name] using XDA-Developers Legacy app

Updated from 17.3 to 17.3 hotfix. Direct install method. No problems

State.of.mind said:
How do you get past "No Valid Slot To Boot"
Click to expand...
Click to collapse
Set magisk to custom, add this url https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json
than you should have option to update magisk. patch boot.img and flash.

Anyone already rooted here? If so pm me pls, I have some questions regarding audio that requires root.

I rooted fine this morning, but am getting a "couldn't install a system update" error message. I know otas won't work on a rooted phone, but I do not see any factory images for a new patch or any discussion of a new ota. Anyone not rooted get an update?

lawtalking said:
I rooted fine this morning, but am getting a "couldn't install a system update" error message. I know otas won't work on a rooted phone, but I do not see any factory images for a new patch or any discussion of a new ota. Anyone not rooted get an update?
Click to expand...
Click to collapse
It happened to me right after unlocking the bootloader. I let it update because I was curious. I have a Verizon sim in the unlocked variant. It updated the build number to the Verizon version. I pulled the sim, flashed back to Google factory image. Rooted the phone, got some things set up, put the Sim back in, update failed. Screw Verizon!

flash-all bat gives me errors that it cannot find system.img and other files, despite the fact that it's there?

masri1987 said:
flash-all bat gives me errors that it cannot find system.img and other files, despite the fact that it's there?
Click to expand...
Click to collapse
Show me a picture of your folder where you are launching the flash-all.
Sent from my crosshatch using XDA Labs

ridobe said:
Show me a picture of your folder where you are launching the flash-all.
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
It has the nerve to tell me that "image-crosshatch-pd1a.180720.030.zip" could not be found in the directory despite it being right there.
This is a common trend for me trying to execute this.
---------- Post added at 08:22 PM ---------- Previous post was at 08:11 PM ----------
ridobe said:
Show me a picture of your folder where you are launching the flash-all.
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
and then when i do get it to recognize the image.zip file
I get this result instead
Update:
So I updated my platform tools and it's working now.
Now to try to root again :|
Final Update:
Updated my entire ADB setup despite it being setup in July, ran the factory image flash-all file, wiped everything, rerooted and i'm back up and running successfully.
Something was missing from my ADB\platform tools setup that the pixels depend on.