Database Info

[GUIDE] How to unlock bootloader on Nokia 3

*Unlocking bootloader will remove all your data!*
I'm using Windows 7, and that's the steps i did. (it should be simmilar for other systems too)
Getting code:
Code will look simmilar to this: DB1ED223C5537BA756FB0671E425D650
Method 1 (no root):
Go to
https://passwordsgenerator.net/md5-hash-generator/ copy paste serial number and click generate. Then you should see code in "MD5 Hash of your string". You can also go to simmilar md5 hash generator sites, but this site automatically converts small letters to big letters.
Method 2 (root):
Okay, this is new method that is much easier and you don't need to send IMEI and wait for @the_laser to give you code. Go to terminal emulator, type su and execute it. Then type this and execute it:
redweaver said:
Actually the command is
echo -n NE1GAM4770133666 |md5sum |tr [:lower:] [:upper:]
If you don't use the -n flag, the newline character is also passed and you get a different result
Click to expand...
Click to collapse
Unlocking bootloader:
Download platform-tools which activates adb and fastboot commands (first you need Nokia 3 driver installed if you didn't)
Nokia 3 driver: http://www.devfiles.co/download/3iK0k7Sv/Nokia_3_USB_Drivers.zip
platform-tools Windows: http://www.devfiles.co/download/KtLsN6fX/platform-tools-latest-windows.zip
platform-tools Mac: http://www.devfiles.co/download/OkrfluP0/platform-tools-latest-darwin.zip
platform-tools Linux: http://www.devfiles.co/download/vk5DudZX/platform-tools-latest-linux.zip
Enable usb debugging in Developer options before running adb. To get Developer options, go to settings, about phone and press build number 7 times. Also enable OEM unlock.
Now Connect phone to computer via usb and enable usb file transfer, run cmd as administrator, then type this command which runs adb:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
then type this command to check is your device connected to adb, it will show serial number of your device, if it hangs at waiting device, then you need to reinstall drivers (if you're doing this first time, then it will ask to allow usb debugging on your computer, just tick always allow from this computer and click OK)
adb devices
then type this command to reboot to recovery (you can boot to recovery by holding power on + volume up (only with usb connected) if this command doesn't works)
adb reboot recovery
when booted to recovery, choose reboot to bootloader option with volume sliders (this will boot to fastboot)
when booted to fastboot, it will show text 'FASTBOOT MODE' in down-left corner
now type this command to check is your device connected properly to fastboot.
fastboot devices
if it show characters like 0123456789ABCDEF or simmilar then it is connected properly, if it hangs on waiting device, then you need to reinstall drivers like mentioned above.
Android Nougat (7.0 & 7.1.1):
Now type these commands to unlock bootloader
fastboot.exe -i 0x2e04 oem key (type your key after oem key)
fastboot.exe -i 0x2e04 oem unlock
then press volume up, when asked
Android Oreo (8.0 & 8.1):
First download NE1-0-215H.lk.bin:
https://my.pcloud.com/publink/show?code=XZaLMs7ZclQ2wvKwSb0ofUraMmrsiHh6uk1X
Now type these commands to unlock bootloader
fastboot oem dm-verity <your_unlock_key>
fastboot flash lk NE1-0-215H.lk.bin
fastboot reboot-bootloader
Proceed your unlock procedure.
If you have problem on flashing the lk partition, you can use MTK Smart Phone Flash Tool to flash lk partition manually.
After lk partition flashed, you may encounter "Red State" when booting the phone. Ignore that and boot your phone to Fastboot mode directly with OST LA.
That is it, i tried to explain for you to understand everything i did to unlock bootloader.
Credits:
@the_laser for codes, some additional steps and corrections. Also thanks for new method. @redweaver for new method.
@Hikari_kalyx for Android Oreo method. @bigrammy for NE1-0-215H.lk.bin link.

way to enter recovery without adb -
power off phone
press and hold volume up + power on buttons, insert cable immediately
countdown will start on phone, hold both keys until countdown ends, then IMMEDIATELY release power on key, still holding volume up
you will enter recovery shortly
after installing TWRP it is very important - DO NOT allow /system modification until supersu package installation ! ( or you will require reflashing phone with OST )
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
one man reported, that even he successfully flashed TWRP image with "fastboot flash recovery <twrp image>", he still got original recovery.
workaround is to use "fastboot boot <twrp image>" - as we need to have USB cable connected to enter TWRP recovery anyway, not big problem.

the_laser said:
way to enter recovery without adb -
power off phone
press and hold volume up + power on buttons, insert cable immediately
countdown will start on phone, hold both keys until countdown ends, then IMMEDIATELY release power on key, still holding volume up
you will enter recovery shortly
after installing TWRP it is very important - DO NOT allow /system modification until supersu package installation ! ( or you will require reflashing phone with OST )
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
one man reported, that even he successfully flashed TWRP image with "fastboot flash recovery <twrp image>", he still got original recovery.
workaround is to use "fastboot boot <twrp image>" - as we need to have USB cable connected to enter TWRP recovery anyway, not big problem.
Click to expand...
Click to collapse
Someone told me that if you flashed twrp, that it automatically removes data encryption. Is that true?
EDIT: i find out that is not true, it asks for some password to decrypt data, but the problem is that idk what is the password

DON'T install xposed! It bootlops.
EDIT: My fault, it actually work but you need to wait more than usual to boot.

That is great guys.
Do we have a working recovery yet?

nafnist said:
That is great guys.
Do we have a working recovery yet?
Click to expand...
Click to collapse
I use this twrp https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
I have stock recovery, but I use fastboot command 'fastboot boot recoveryname.img' when I need TWRP, and that's awesome because I don't lose stock recovery which is useful to flash OTAs and Nokia zips. I flashed SuperSu 2.79 just fine, but expect some crashes like software update, device monitor crash, but actually everything works, software update works just fine.

SkaboXD said:
Someone told me that if you flashed twrp, that it automatically removes data encryption. Is that true?
EDIT: i find out that is not true, it asks for some password to decrypt data, but the problem is that idk what is the password
Click to expand...
Click to collapse
TWRP can't handle Android 7.x default disk encryption, just press "cancel" and we need to use sdcard as storage for backups and packages because of this

Can I return the bootstrapper lock?

Where are you getting the codes from @the_laser?

abetterlie said:
Where are you getting the codes from @the_laser?
Click to expand...
Click to collapse
Yes

shokohiw said:
Yes
Click to expand...
Click to collapse
you mean to get bootloader locked again?
yes you can just instead of oem unlock type oem lock

I mean where are you getting the OEM unlock keys from?
SkaboXD said:
you mean to get bootloader locked again?
yes you can just instead of oem unlock type oem lock
Click to expand...
Click to collapse

abetterlie said:
I mean where are you getting the OEM unlock keys from?
Click to expand...
Click to collapse
idk, ask @the_laser

the bootloader I unlocked how to install root and twrp

shokohiw said:
the bootloader I unlocked how to install root and twrp
Click to expand...
Click to collapse
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
reboot to fastboot, then type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.

Thank you!

Is it possible after unlocking, installing twrp and root, to return the device to factory settings for ota updates? If so, how?

shokohiw said:
Is it possible after unlocking, installing twrp and root, to return the device to factory settings for ota updates? If so, how?
Click to expand...
Click to collapse
on twrp, there is a option wipe, click on it, then you will see option swipe to factory reset. then wait and reboot.
And you can now enable system modification if you want (it is recommended to enable it because some zips fails to flash because this option is disabled)

After installing TWRP and rebooting, does not want to boot Android, weighs in on the initial splash screen what to do
Your device has failed verification and may not work properly

shokohiw said:
After installing TWRP and rebooting, does not want to boot Android, weighs in on the initial splash screen what to do
Your device has failed verification and may not work properly
Click to expand...
Click to collapse
Weird, when it says your device has failed verification?
For me reboot works fine

[Recovery][3.0.2] Unofficial TWRP for the Huawei Y3 2017 CRO-U00

TeamWin Recovery Project 3.0.2​
WARNING #1: Unlocking BL and flashing a custom recovery voids your warranty. Please make sure to contact your carrier/seller if your phone is still under warranty after unlocking the bootloader.
WARNING #2: Make sure you have enabled OEM unlock and unlocked bootloader before trying to flash this. How you can successful root and install TWRP will be described below.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
HOW-TO UNLOCK BOOTLOADER
1. Get bootloader Unlock code here
2. Install minimal adb and fastboot
3. Plug in your phone and make sure all huawei drivers got installed
4. Enable developer options in settings as described above.
5. Enable OEM unlock, enable USB debugging (both in developer options)
6. Open the adb tool you installed recently
7. Type fastboot devices (now a device number should show up)
8. Type fastboot reboot-bootloader (your phone will now boot into bootloader, if not, you haven't set up drivers or adb/fastboot correctly)
9. This step will wipe all your data! Type:
Code:
Code:
fastboot oem unlock xxxxxxxxxxxxxxxx
(xx is for your unlock code)
10. Ones it's done type:
Code:
Code:
fastboot reboot
Your phone will reboot and you have an unlocked bootloader!
11. You can now go on installing TWRP on your device
HOW-TO INSTALL
Make sure you enabled OEM unlock in settings, if you haven't please do that now by tipping 10 times on build number (to activate developer options), than open developer options and go to OEM unlock, enable it
Have an unlocked bootloader is required! (In my case, I login the unlocker website at provide necessary information and get the unlock code so try yourself !!!)
Download the TWRP recovery from the download section below
Make sure you got fastboot drivers installed (I will describe this below in how to unlock your bootloader)
Open the adb/fastboot application on your pc and go to the directory where your TWRP img file is downloaded
Boot your phone into download mode (First method: fastboot reboot-bootloader while connected to pc. Second method: power off your phone, hit power on and volume down until it boots to download mode)
Check again if there is written: unlocked phone!
If yes type now into your adb/fastboot terminal:
Code:
fastboot flash recovery Twrp_CRO_U00_recovery.img
Click to expand...
Click to collapse
Type:
Code:
Code:
fastboot reboot
Now boot into recovery by pressing: power+volume up+volume down at the same time
Enjoy twrp
HOW-TO ROOT
Backup, just in case
Have an unlocked bootloader and TWRP installed from above (take one from december)
We will use this root method: Phh's superuser
Download latest official phh superuser zip here.
Put the zip on your external sd card of your phone (since we can't access /data in twrp)
Boot into twrp and flash the downloaded file
Install latest Material phh apk: Release post
Now you are rooted, congrats!
SUPPORTED DEVICES
CRO-U00
HWCRO-U6580M
(Test your Device, if you want to take the risk )
DOWNLOAD
Updated Link Shared In Next Post.
Contributors
CM13 Minimal Twrp Source
BBQlinux
Google
HWDEV
****
More Information Given Later

Dualboot Patcher Supported
TWRP
Downloads

is the source for this device support available somewhere?

fgallina said:
is the source for this device support available somewhere?
Click to expand...
Click to collapse
YES.
The sources of Y3 2017 available in Git-Hub.

TWRP Sources Of Y3 2017
Source:
https://github.com/docs007/device_Huawei_Cairo_U00

The Ultimate guide to flash and root Xperia L (aka, taoshan)

This thread will guide you to flash a custom recovery, Root the device, flash custom ROMs. Firstly, read the entire post and then start your work.
I am a noob. But I have a little experience of rooting and flashing. This device gave me nightmares which are less than as compared to the Xperia Sola which I bricked some years back.
My device has a problem. It does not help install twrp with the traditional ways we know like we can see in the Official TWRP website using "dd" method, the Cyanogenmod link using fastboot commands, the Flashify method, the RecoveryApp method whose apk I never found and the Recovery Installer Utility.
I came to know that either my phone don't have the recovery partition or the phone is overriding all the commands.
Using fastboot commands would give the error like in this post.
Using Flashify would tell me there's no recovery partition found. Rashr would complete the flash process but after booting to recovery, there was no TWRP, just the stock Android recovery.
If you read carefully on the twrp page of XL, there's a line which caught my attention late enough.
It means that TWRP may not work on your device unless you install other custom software as well.
Click to expand...
Click to collapse
Flashing custom kernels with flashtool is easy and they come with recovery pre-installed and lots of amazing stuff, but they won't do any good with the stock ROM. I've tried the Extended stock kernel, the Phantom Kernel and the Thunderzap 4.15.
After surfing the web and forums of other devices, I found that there is a chance I can fix things by updating/repairing software via PC Companion. But something happened and repair also failed.
I can't tell the reason why this happened. And I didn't store the logs. But with trial and error I found some workarounds.
Actual Methods start here
Rooting the device
If you only want to root your device for various reasons, then you will need nothing but a Rootkit. Check out this post about Rooting Xperia L.
But if you are planning to install custom ROMs for your device, then skip this rooting step. It won't be necessary for this condition.
Flashing custom recovery
*Try this method only if above-mentioned method fails*
1. Download TWRP 3.2.1 img. The 3.2.2 and 3.2.3 versions work perfectly but they caused the screen to flicker like hell on my device. Rename the file to 'twrp.img'
2. Download and install adb and fastboot drivers system-wide.
3. Connect your device to PC via USB cable and enabling USB-debugging mode.
4. Open Windows Powershell/Command Prompt in the twrp download directory by pressing Shift and clicking right mouse button.
5. Use fastboot command on stock ROM without root and Unlocked Bootloader. Instead of flashing twrp image to recovery, flash to boot. Use the code:
Code:
adb devices
adb reboot fastboot
Wait for device to boot into fastboot mode. A blue LED will flash when connected.​
Code:
fastboot flash boot twrp.img
fastboot reboot
After reboot, don't boot to system. Boot to recovery by pressing volume up repeatedly when pink LED glows. Stop when device vibrates and LED color changes
Flashing custom ROMs
Once the recovery is installed, everything becomes easy. you can find different custom ROMs on the device page here on XDA.
My favorite one is The resurrection Remix Nougat. It is stable enough to be your daily driver. You can head to that page and follow their instructions. But I will also provide steps here.
When in TWRP after the last step, move the downloaded zip file of the ROM and GApps you want to install to the storage of the device by simply connecting via USB.
After that, in TWRP click on Wipe->Advanced->Tick on System, Cache, Dalvik cache. Then Do swipe to begin wipe.
After wipe, go back to main menu. Tap on install, select from the list the ROM zip. then tap on Add more zips and select the GApps zip and then Swipe to start flashing.
After flashing, reboot to system. The first boot takes time. Don't panic if it won't boot.
Install TWRP to FOTAKernel
After booting to your new ROM, you can install the TWRP to your FOTAKernel.
This can be done as following:
Get the downloaded TWRP img file and push it to the device using command line. Open command prompt in the TWRP directory and type,
Code:
adb root
adb wait-for-device
adb push twrp.img /tmp/twrp.img
Now extract the TWRP image to the FOTA partition code,
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now reboot to recovery
Code:
adb reboot recovery
Note that custom ROMs often come with Root access inbuilt. If your ROM happened to be not, and your ROM is based on Lollipop or later version of Android, you can root with Magisk. Just read carefully before proceeding.
Comments are welcome!

Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devices​adb reboot fastboot "​
I think my Sony Xperia L C2105 does not have the fastboot mode.
Here's what I did:
Drivers for Xpleria L are installed.
The bootloader is unlocked (I think!)
1 - installed 15-second ADB
2 - open Windows power shell
3 - Command: adb devices
Response is: "List of devices attached: ZH8001ADB3 device"​
4 - Command: adb reboot fastboot
Response is: long pause, phone booted but in normal mode, and light is red ...!​
5 - Command: fastboot flash boot twrp.img;
Response is: "<waiting for device>";
- phone still running in normal mode and the light is red.
- few minutes later, the phone is charging with green light present.​
I think the phone is rooted.
I used the code provided by the Sony website to unlock the bootloader.
Using the Root Checker Basic app, I get the info: "Congratulations! Root access is properly installed on this device!"
But if I type in the dialer *#*#7378423#*#*, and go to Service info > Configuration > Rooting status is "Boootloader unlock allowed" !!
Is that why it does not work?
I tried switching it off and doing Boot into Xperia L Fastboot Mode Using HARDWARE BUTTONS, but the phone is dark, with no picture, and the led turns blue.
Using the command:
PS C: \ adb> adb devices
List of devices attached
PS C: \ adb>
I've been trying to do that for a few days now and I still have not managed it, even using other advice.
Can someone tell me what to do?
Thank you in advance.

Everterra said:
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devices​adb reboot fastboot "​
I think my Sony Xperia L C2105 does not have the fastboot mode.
.......
Click to expand...
Click to collapse
1. When in fastboot mode, you should type in cmd "fastboot devices" to check the device connectivity. If you can't, then connect using hardware keys.
2. Blue light indicates that you are in fastboot mode. If list of attached devices are blank, that means drivers are not installed (properly). Connect your phone again in fastboot mode and check your drivers page, Win+X > M (I am assuming you must be on windows). There must be a tiny yellow triangle on your device's name. Right click on it and uninstall it and remove device. Try again installing drivers from the flashtool's folder. Disable driver signature enforcement if you are having trouble going the straight way.
3. Your bootloader is still locked because if it had unlocked then the message displayed would have been, "Bootloader Unlocked: Yes" or something like that. Try flashing your stock ROM via Flashtool. Wipe cache and data while flashing. After flashing stock Rom, try unlocking bootloader again. I believe you are using Flashtool.
4. If you are rooted, then you must have any SuperSU app installed on your device. And it's all good even if you are rooted.

The Complete Pixel 3 How-To Guide (newbie friendly!)

There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623
Download: https://dl.twrp.me/crosshatch/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone

Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules

I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?

Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?

farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april

farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
1.) If you somehow have an unlocked bootloader, yes, it would work for the Verizon Pixel 3 XL. However, I was under the impression that Google will not unlock the BL for the Verizon variant and there is currently no way to "hack" it.
2.) It should work the same whether you're on P or Q, though if you want to remain with Q, make sure you download the beta files directly from Google (rather than the P images) and use Magisk 19.0 instead of 18.1.
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
You can force it to check for updates; when you unlocked the BL shouldn't matter if you're using a patched boot image.

HACK3DANDR0ID said:
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
Click to expand...
Click to collapse
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.

farfegnugen said:
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
Click to expand...
Click to collapse
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz

Homeboy76 said:
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Click to expand...
Click to collapse
Thanks so much for the info! Its difficult trying to find the current status of all the diff devices' root statuses.

Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?

CadTechBGMC said:
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
Click to expand...
Click to collapse
yes, if you are flashing with wipe all option (without removing -w) it does flash to both slots.

Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.

EMJI79 said:
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
Click to expand...
Click to collapse
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
what i do normally is to power off the device first wait for few seconds then then use key combination to get it to fastboot from power-off state. Booting from fastboot to twrp never had any issues unless i had messed up the twrp installation due to some mess i did.

SacredDeviL666 said:
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
Click to expand...
Click to collapse
I have to press the keys 40 seconds even from power off.

EMJI79 said:
I have to press the keys 40 seconds even from power off.
Click to expand...
Click to collapse
definitely not 40seconds from power off state for me. not sure whats happening there

Maybe a short video would be a help to some of us newbies

Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!

Drashnar said:
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Click to expand...
Click to collapse
That is correct. I made the same switch from an OG Pixel and Pixel XL to P3 and P3XL right after release. Unlock the bootloader before you mess around a lot since it will do a factory reset.

How about backups? Does anyone backup and restore, or not?
If so, how do you do it with this 2 partition system?

installed and I like it. I cant get the clock off the lock screen. all settings says it is off.
wished it had MicroG installed instead of gapps

Infinix Hot 9 TWRP Recovery,Other & Root

[AIO Guide] Bootloader unlocking, Root ,Twrp , Custom Rom & Stock Firmware]​ NOTE :unlocking bootloader wipe your data
Root at your own risk
I am not responsible for any data loss or brick
# Twrp recovery for hot 9
Device- Infinix Hot 9
Model & Variant :
1: X655C-H6211ABKG-Q-OP
1.Bootloader Unlocking Guide:
1. Download & install ADB driver
2.Enable devloper mode by taping on Build verson(setting->my phone) then enable Oem Unlock & usb debugging from (settings->System->Devloper option)
3.Now connect device & open ADB path & run cmd
command: ADB devices
then reboot to bootloader
command: ADB reboot bootloader
4. unlock bootloader
command: fastboot flashing unlock the phone will ask to confirm
5. now reboot to system
command:fastboot reboot
If you are stuck waiting for the device screen
2. TWRP [Official]
https://forum.xda-developers.com/t/recovery-for-infinix-hot-9.4472895/
3. Root:
## Root zip link: Magisk-v21.0.zip
## Unroot link : Magisk-uninstaller-20201003.zip
4. Orange state disabler:
Flashing guide & zip file
Click Wipe →Format Data → Yes → Press Enter.
Then Click Reboot → Recovery (Reboot to Recovery ).
After this, TWRP Recovery Mode will be installed on your phone
Link::Orange disabler.zip
5. Gsi Rom / Custom Rom Install guide & link:
https://forum.xda-developers.com/t/custom-rom-dynamic-partition-arm64-ab.4379341/
6. Phone Hard Brick fix / Flashing guide & tools :
https://forum.xda-developers.com/t/phone-soft-brick-phone-on-off-poblem-tecno-device.4378501/
6.1. Stock Firmware Files / Flash file
## Download link :
1.X655C-H6211ABKG-Q-OP-210704V303
Hit Thanks If You Liked My Work

Hey, the recovery just stuck at the TWRP logo screen.

I'm stuck with < waiting for any device > when I enter fastboot flashing unlock command

Dkwbsn said:
I'm stuck with < waiting for any device > when I enter fastboot flashing unlock command
Click to expand...
Click to collapse
if you are using windows OS check your USB drivers
enable USB Debugging from developers options and make sure your device is listed in results of CLI command USB devices otherwise may the problem is the USB Cable