Database Info

[Root][Sony Xperia Z2][MM][23.5.A.0.575] unlock bootloader, root and ROM flashing

SONY Xperia phones have unlocked bootloader which adds to the difficulty of rooting on top of MM.
#######All the works posted here are not mine but of various authors to whom I am gratful for helping me achieve root############
Requirements
Locked Bootloader Xperia z2
Stock SONY ROM
no root
Battery above 70(just to be safe)
Good internet connection
Now, we have lots to download because Flashtool dosen't work so, I had to download android sdk entirely.
#1
Obtaining the Bootloader Unlock Code
Note:Unlocking the bootloader on a Sony device may automatically wipe internal storage; a backup of the sdcard is suggested. It will also irreversibly erase the DRM keys stored in the TA partition of some devices, which will result in the loss of certain proprietary features that may have been included. Check your specific device forum on XDA to learn more.
In order to unlock the bootloader on your Xperia Z2 you will need to obtain a code from Sony. The following process will help you acquire this code so that you can flash a custom recovery.
Open the Phone application on the Xperia Z2 and enter *#06# to obtain the device's IMEI, IDID or MEID. Save this for later use.
Optional: if you do not have a phone app, the IMEI, IDID or MEID can be found on the box or on the device in Settings -> About Device -> Status.
Put the device into fastboot mode:
Insert one end of the Micro-USB cable into your PC. Turn off the device and wait at least 5 seconds. Press and hold the Volume Up button and plug the other end of the Micro-USB cable in to your device.
Open a terminal on the PC and enter fastboot getvar version
If you receive the message <waiting for device> fastboot is not configured properly, please see fastboot for more details.
Navigate a browser here
Select your device and click the 'continue' button at the bottom of the page.
Enter your email address, agree to the terms and select 'Submit'
Click the link from your email, enter your IMEI, IDID or MEID and continue
The unlock code should now appear, write this down for the next step.
In the PC's terminal, enter the following command: fastboot oem unlock 0xKEY
KEY corresponds to the unlock code you were given.
The Xperia Z2's bootloader should now be unlocked.
This should factory reset the phone, you may have to wait a while before reboot.
Source:https://wiki.cyanogenmod.org/w/Install_CM_for_sirius
How to check if your bootloader is locked or unlocked?
This tutorial is suitable for all versions of Android. We are provoding two different methods to check the status of your bootloader, use the one that works for you.
Method 1 :
This one is the easiest method and works with many device out there, you don’t require any use of PC, you just need to enter a spacial block of numbers in your keypad to check your bootloader’s status.
Step 1 : Open your device’s dialer (App where you enter telephone numbers to call someone).
Step 2 : Dial the below code, it will automatically open a new windows. (if it doesn’t opens anything then use the second method).
1
*#*#7378423#*#*
Step 3 : Now in that window go to Service Info >> Configuration, and see if there is :
1
2
Bootloader unlock allowed - Yes >> This means that your Bootloader is Locked
Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
Method 2 :
Step 1 : Download and install adb & fastboot package & drivers in your system (Google it for your device).
Step 2 : After successful installation of adb & fastboot, connect your device to your PC via USB cable in fastboot mode.
Step 3 : Now open the folder where your adb & fastboot package is extracted, press Shift key on your keyboard and right click in the folder and select “Open command prompt here“.
Step 4 : It will open a Command Prompt window.
Step 5 : Type the following command to check if the device was detected in fastboot mode.
1
fastboot devices
Step 6 : if you don’t get device it or anything it means that the drivers weren’t correctly installed or the device wasn’t connected properly, if this happens try reinstalling your drivers.
Step 7 : Next run the following command to check the status of your device’s bootloader.
1
fastboot oem device-info
Source:https://thebroodle.com/android/how-to-check-your-bootloader-is-locked-or-unlocked/
#2
After unlocking the device, rooting is done using Kingroot (easier), you can use either the windows app or android app.
Success rate of rooting however is very less, so you may need to do it more than a few time.
The rooting lasts only 2 restarts(for me), so you have to root again using king root.
android: http://forum.xda-developers.com/devdb/project/dl/?id=19156
windows: https://kingroot.net/
Any problems with kingroot check the link : http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
#3
How to Install CWM 6.0.4.7 Recovery on Xperia Z2 D6503, D6502, D6543
Download Doomlord’s Z2_DooMLoRD_AdvStkKernel_FW-167-v07.zip
http://doomlord.xperia-files.com/download.php?dlid=WjJfRG9vTUxvUkRfQWR2U3RrS2VybmVsX0ZXLTE2Ny12MDc=
Copy the downloaded Advanced Stock Kernel.zip file to your phone’s SD card.
Extract the downloaded .zip folder on your PC, you will get a Boot.img file.
Place the extracted Boot.img file in the Minimal ADB & Fastboot folder that you created using our ADB & Fastboot Quick Setup Guide.
If you are using Android ADB & Fastboot full package, you can place the downloaded Recovery.img file in the Fastboot folder or in the Platform-tools folder.
Open the folder where you placed the Boot.img file. E.g Minimal ADB & Fastboot or Fastboot or Platform Tools.
Press and hold the shift key and right click on an empty area within the folder, and click on “Open Command Window Here”.
Turn off your Xperia Z2 completely.
Now press the Volume Up Key and while keeping it pressed plug in the USB cable.
You should see a blue light in the notification light of your phone, that means your device is now connected in Fastboot mode.
Now type the following command: fastboot flash boot boot.img
Hit Enter and it will quickly flash CWM 6.0.4.7 recovery in your Xperia Z2.
Once recovery is flashed, now issue this command “Fastboot reboot”
Your device will reboot now, as soon as you see the Sony logo, and the pink LED, press Volume Up key to enter recovery.
Once you’re in recovery, select “Install Zip > Choose Zip from SD Card > Advanced Stock Kernel with CWM.zip > Yes”. [Important]
This will flash the Kernel in your phone now. Once flashed, reboot your device.
Congrats! You should now see the custom recovery.
Source: http://techbeasts.com/install-cwm-recovery-root-xperia-z2-2301a0167-d6502-d6503-d6543/
Now, you have custom recovery, you can use this to flash ROMS. Caution to be taken when you flash a ROM you might loose your Kernel and recovery so use ROMs with inbuilt kernels or just flash after installing depending on ROM
For D6502 phone you will need to flash a fix zip after the ROM for getting network.
#4
http://www.xda-developers.com/how-to-install-twrp/
For installing TWRP follow the above guide.
Can't upload screenshots yet(don't have them, did this in a hurry)
(My internet connection is very slow)
CREDITS
All the authors of my sources
#########@@@@@@@Press that small little Thank You button:good@@@@@@@@############
-------------------------------------------------------------->>>>>>>>>>>>>>>>>>>>>>>Should be here

Thread closed as per OP's Request.

Unlocking Bootloader [Incomplete]

Note: It would be great to keep this page open while following through on your PC instead of your phone as you'll be rebooting and resetting your phone by following this procedure.
Click to expand...
Click to collapse
Prerequisites:
ADB (Android Debugging Bridge) tools for your OS (Windows/Linux/Mac)
Windows
Mac
Linux
Custom Recovery Image (TWRP or some other that you prefer):
(Official TWRP web hosted version) Nokia 6.1 (2018)
Download from American Mirrors
Download from EU Mirrors
USB Cable to Connect the phone to the computer
The Phone: Nokia 6.1 (2018) (preferably Fully Charged)
The device drivers (for Windows and Mac)
A good and active Internet Connection
An active Email address and client to quickly view it.
In this tutorial I'll be referring to Linux terminal, Mac Terminal & Windows Command prompt/Powershell simply as terminal.
Click to expand...
Click to collapse
Installing adb and fastboot
Google hosts zips including only adb and fastboot. You can set these up for use with the instructions below.
On Windows
Download the (Windows.zip) from Google.
Extract it somewhere - for example, %USERPROFILE%\adb-fastboot
• On Windows 7/8:
1. From the desktop, right-click My Computer and select Properties
2. In the System Properties window, click on the Advanced tab
3. In the Advanced section, click the Environment Variables button
4. In the Environment Variables window, highlight the Path variable in the Systems Variable section and click the Edit button
5. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• On Windows 10:
1. Open the Start menu, and type “advanced system settings”
2. Select “View advanced system settings”
3. Click on the Advanced tab
4. Open the “Environment Variables” window
5. Select the Path variable under “System Variables” and click the “Edit” button
6. Click the “Edit Text” button
7. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• Install the device drivers linked in prerequisites (or from Nokia support site), and reboot.
On MacOS
Download the MacOS (Darwin.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.bash_profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
On Linux
Download the (Linux.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
You may also need to set up udev rules: see (this repository) for more info.
Setting up adb
To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.
2. Tap on “Build number” seven times.
3. Go back, and select “Developer options”.
4. Scroll down, and check the “Android debugging” entry under “Debugging”.
5. Plug your device into your computer.
6. On the computer, open up a terminal/command prompt and type adb devices.
7. A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”.
Congratulations! adb is now ready to use with your device.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at (Nokia Support) to unlock your bootloader, you will need to register at this site with a working/active email to proceed. They'll verify your device using an app to issue a validation code.
Note: If your device is not supported by the Nokia Bootloader Unlock
website, you will need to use an alternative bootloader unlock method.
Installing a custom recovery using fastboot
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. In case you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone. This needs to be done again due to resetting of your phone.
3. Download recovery - visit twrp.me to obtain the latest version of Team Win
Recovery Project for your device. Nokia 6.1 (2018) does have an official TWRP recovery that you can find here: Nokia 6.1 (2018) [PL2] respectively.
4. Connect your device to your PC via USB.
5. Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>" , try running
Code:
fastboot
as root/Administrator.
7. Boot into TWRP temporarily:
Code:
fastboot boot twrp.img
8. Use adb to push the zip onto your device:
Code:
adb push twrp.zip /
9. Go to `Install` option on the TWRP menu and browse to the zip (Scrolling to the bottom should have the zip) and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidentally flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
This command assumes the recovery image is present in your current working directory (Check using `DIR` on command prompt or `ls` command on terminal)
If it isn't you can change your current directory to the directory containing the recovery image or copy/move the recovery image to your current working directory.
10. Now reboot into recovery to verify the installation:
That's all folks. You may now root your phone, or even flash a custom ROM. I suggest getting openGapps for the custom ROM if you wish to use Google play services on the custom ROM.
Popular adb commands
Code:
adb shell
Launches a shell on the device accessed through the terminal on your computer.
Code:
adb push <local> <remote>
Pushes the file <local> to <remote>
Code:
adb pull <remote> [<local>]
Pulls the file <remote> to <local>. If <local> isn’t specified, it will pull to the current folder.
Code:
adb logcat
Allows you to view the device log in real-time. You can use adb logcat -b radio to view radio logs, and adb logcat -C to view logs in colour
Code:
adb install <file>
Installs the given .apk file to your device
<local> refers to location on your computer (like c:\\Users\%USERPROFILE%\adb-fastboot on windows or ~/adb-fastboot on unix based OS), while <remote> refers to location on your android device (like "/sdcard/", without quotes)

Reserved

What do you do if oem unlocking in developer is greyed out? TA-1045

@toxicmender The official bootloader unlock was only released to the Nokia 8. So, what is the point posting it here?
Or have they silently added the 6.1?

singhnsk said:
@toxicmender The official bootloader unlock was only released to the Nokia 8. So, what is the point posting it here?
Or have they silently added the 6.1?
Click to expand...
Click to collapse
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones

toxicmender said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones
Click to expand...
Click to collapse
Why would you make start this thread then? It is completely pointless and misleading.
It is like making a post saying that there are flying cars and marking it [Incomplete]. It is just ****ing stupid.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.

cmaxwe said:
.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.
Click to expand...
Click to collapse
Hey now, there is really no need for that level of hostility. He knew they were doing unlocks for at least one Nokia phone, and me may not have known that they didn't have it for the 6.1.
Please don't talk to peope like that if they make a simple mistake when trying to provide info and help out the community. We're all human.

toxicmender said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones
Click to expand...
Click to collapse
Honestly if there was a good amount of roms available for this phone I would gladly pay the $5 to unlock bootloader, although that method leaves me with questions. does that method survive ota? Does it actually work? Can it relock and unlock without paying again?
Is there really not that many people on here willing to try unlocking and flashing the many gsi roms available?

cmaxwe said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Why would you make start this thread then? It is completely pointless and misleading.
It is like making a post saying that there are flying cars and marking it [Incomplete]. It is just ****ing stupid.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.
Click to expand...
Click to collapse
It's not like there isn't a way, there is, just not a transparent method. Somehow those (refer to link in reply) are able to generate and send the signature file allowing you to unlock the phone, how it works or if your bootloader be locked again after updating is unknown to me ATM

mymeatb18 said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Honestly if there was a good amount of roms available for this phone I would gladly pay the $5 to unlock bootloader, although that method leaves me with questions. does that method survive ota? Does it actually work? Can it relock and unlock without paying again?
Is there really not that many people on here willing to try unlocking and flashing the many gsi roms available?
Click to expand...
Click to collapse
Well the ROM development begins after an Official TWRP recovery, so the chances are there might be some. I'm not clear on the the OTA being able to relock the bootloader either since I was running Pie update when I got to know about it.

thread closed as per OP request

Fastboot Issues with Nokia 3

Hey guys, I’ve been trying to turn my old Nokia 3 into a LineageOS device for the last week, mainly as a test before I try it on my main device (a Nokia 8), but I’m not having any luck. I’m trying to follow the steps as described on the board here. While I did have great success installing LOS on an old Samsung Galaxy S5 Neo following the guide on the wiki (wiki.lineageos.org/devices/s5neolte/install), the Nokia 3 is just not having it and I’m running out of ideas. So much for an introduction, let’s get into it …
The device:
Nokia 3—“TA-1020”
Android Version: 8.1.0
USB Debugging is turned on and my laptop has permission.
OEM Unlocking is not available/greyed out in the Dev. Options.
My Laptop:
OS: Windows 10
Nokia USB Drivers are installed.
The Nokia 3 is recognized by the Device Manager, Explorer, and adb.exe.
All commands are used via cmd as administrator from within the adb directory.
The Issues:
“adb devices” finds the device and lists it as “NE… device”—so far so good, I guess, but …
“adb reboot-bootloader” reboots the device, but it does not boot into fastboot mode and instead just reboots normally
“adb devices” after “adb reboot-bootloader” just lists it as “device” again
going into fastboot mode manually by using Power+Volume Up to get into recovery mode works; I then get a black screen with a little “=> FASTBOOT mode…” on the bottom
“adb devices” does no longer find the device, once this black fastboot screen is on
Windows finds the device and lists it in the Device Manager under “ADB Interface” » “Fastboot Device”
“fastboot devices” via cmd does not find the device, however
“fastboot oem unlock” returns “<waiting for device>” and is stuck there until I quit (I tried waiting for about 45 minutes once, but to no avail)
So here I am—stuck. Forget installing LineageOS, it seems like I can’t even unlock the OEM because the device is “invisible.” Does anyone have any suggestions? I would really appreciate the help.

blarkh said:
Hey guys, I’ve been trying to turn my old Nokia 3 into a LineageOS device for the last week, mainly as a test before I try it on my main device (a Nokia 8), but I’m not having any luck. I’m trying to follow the steps as described on the board here. While I did have great success installing LOS on an old Samsung Galaxy S5 Neo following the guide on the wiki (wiki.lineageos.org/devices/s5neolte/install), the Nokia 3 is just not having it and I’m running out of ideas. So much for an introduction, let’s get into it …
The device:
Nokia 3—“TA-1020”
Android Version: 8.1.0
USB Debugging is turned on and my laptop has permission.
OEM Unlocking is not available/greyed out in the Dev. Options.
My Laptop:
OS: Windows 10
Nokia USB Drivers are installed.
The Nokia 3 is recognized by the Device Manager, Explorer, and adb.exe.
All commands are used via cmd as administrator from within the adb directory.
The Issues:
“adb devices” finds the device and lists it as “NE… device”—so far so good, I guess, but …
“adb reboot-bootloader” reboots the device, but it does not boot into fastboot mode and instead just reboots normally
“adb devices” after “adb reboot-bootloader” just lists it as “device” again
going into fastboot mode manually by using Power+Volume Up to get into recovery mode works; I then get a black screen with a little “=> FASTBOOT mode…” on the bottom
“adb devices” does no longer find the device, once this black fastboot screen is on
Windows finds the device and lists it in the Device Manager under “ADB Interface” » “Fastboot Device”
“fastboot devices” via cmd does not find the device, however
“fastboot oem unlock” returns “<waiting for device>” and is stuck there until I quit (I tried waiting for about 45 minutes once, but to no avail)
So here I am—stuck. Forget installing LineageOS, it seems like I can’t even unlock the OEM because the device is “invisible.” Does anyone have any suggestions? I would really appreciate the help.
Click to expand...
Click to collapse
You need to have fatboot drivers to be able to see your device in fastboot. I had the same problem with it connecting to adb devices but not to fastboot devices. I downloaded the driver on this thread https://forum.xda-developers.com/no...-bootloader-nokia-3-pie-t4012285#post82382141 which also shows how to unlock the bootloader. You will not be allowed to flash lineage without unlocking the bootloader first.

Forget fingerprint password

I forget fingerprint password so I would like set another one

Do you mean the screen lock PIN? What's your Android device?

FRP Remove via ADB Command All Android Phone - PAKFONES.COM
How to Remove FRP via ADB Command: ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and Fastboot are a must for any Android...
pakfones.com

You have google account add to your mobile.
Then go to find android on google services. Now it will give you location of mobile.
You have lock/ unlock , erase and ring option.
Now tap on unlock. This will unlock mobile screen without password.
You can start mobile in recovery mode. And wipe cache partition.

How to root android device with factory disabled fastboot

Howdy! I got a gionee a1 lite device recently and I cannot manually reboot the phone to bootloader through recovery mode or fastboot via adb pc tools. Someone here enlightened me that the device's fastboot is disabled which is a bummer.
I'm aware now that some manufacturers disable their devices' bootloaders for reasons unknown. Has anyone been able to root a device with a disabled fastboot? Please help me out.

Trunks614 said:
Howdy! I got a gionee a1 lite device recently and I cannot manually reboot the phone to bootloader through recovery mode or fastboot via adb pc tools. Someone here enlightened me that the device's fastboot is disabled which is a bummer.
I'm aware now that some manufacturers disable their devices' bootloaders for reasons unknown. Has anyone been able to root a device with a disabled fastboot? Please help me out.
Click to expand...
Click to collapse
Methods that involve flashing the device won't do you any good. You'll have to try methods that involve using an app to root the device for you, which have not been useful to root android since android Lollipop/Marshmallow was released.

Droidriven said:
Methods that involve flashing the device won't do you any good. You'll have to try methods that involve using an app to root the device for you, which have not been useful to root android since android Lollipop/Marshmallow was released.
Click to expand...
Click to collapse
Is there possibly any app or other method that doesn't involve unlocking bootloader to root android nougat? Kingroot and kingoroot have been ineffective so far.

It's a misconception to think that device's bootloader must get unlocked before device's Android can get rooted.
Rooting Android simply means a suitable SU binary - by whatever method - gets installed. IMO the easiest method to do this is by means of ADB.

jwoegerbauer said:
It's a misconception to think that device's bootloader must get unlocked before device's Android can get rooted.
Rooting Android simply means a suitable SU binary - by whatever method - gets installed. IMO the easiest method to do this is by means of ADB.
Click to expand...
Click to collapse
I have a ported twrp ready to flash but I'm hesitant because I heard flashing a recovery while bootloader is locked could bork the device. Flashing twrp seems to be the only step now to root the phone, should I give it a try or avoid the risk?

My POV: TWRP isn't needed at all to root a device's Android.

jwoegerbauer said:
My POV: TWRP isn't needed at all to root a device's Android.
Click to expand...
Click to collapse
I needed the twrp to flash magisk. Is there some other method to root an android 7 device that doesn't involve twrp or unlocking bootloader?

I already told you a method: no more to say by me ...

jwoegerbauer said:
I told a method: no more to say by me ...
Click to expand...
Click to collapse
Please put me through or post the link to the method.

1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot

jwoegerbauer said:
My POV: TWRP isn't needed at all to root a device's Android.
Click to expand...
Click to collapse
My POV: it isn't exactly as simple as connect to adb and issue a few commands, that is just a fact. I'm speaking from experience, just isn't that simple in all cases. If you can get the device to accept temp root via adb, then, yes, it "can" be that simple, the problem is, temp root via adb isn't an option on ALL android devices.

jwoegerbauer said:
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
Click to expand...
Click to collapse
Thank you. I tried this, unfortunately I got a "device not found" error even though "adb devices" did.

Droidriven said:
My POV: it isn't exactly as simple as connect to adb and issue a few commands, that is just a fact. I'm speaking from experience, just isn't that simple in all cases. If you can get the device to accept temp root via adb, then, yes, it "can" be that simple, the problem is, temp root via adb isn't an option on ALL android devices.
Click to expand...
Click to collapse
I'm really confused ...
With no line in this thread it was mentioned / suggested / recommended to install a temporary root.
I kindly ask you to stop hopping into a thread and post off-topic content. TIA

@Trunks614
When ADB triggers "no devices found" then it's mostly caused by wrong ADB-driver used.

jwoegerbauer said:
@Trunks614
When ADB triggers "no devices found" then it's mostly caused by wrong ADB-driver used.
Click to expand...
Click to collapse
Will "apply update from SD card" work the same way?

jwoegerbauer said:
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
Click to expand...
Click to collapse
SuperSU is a deprecated project, that is why and how Magisk came to prominence. Anyone still using SuperSU is taking a real chance of compromising the security of their device at the system level. If SuperSU is used to gain root, it is highly recommended to convert to Magisk root after gaining root via SuperSU.

i have the same problem, zte A5 2019 fastboot disabled, by the way you can try mtk easy-su