Related
Hello,
I recently got a new Nexus 5X, I enabled USB Debugging and I tried using the CMD and it worked fin with commands like:
adb devices
adb reboot bootloader
However, once I boot into bootloader, I can't use any of the commands such as:
fastboot boot "C:\USERS\Path\To\TWRP.img"
it just gives this error:
downloading 'boot.img'...
OKAY [ 0.612s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.627s
I installed the drivers so USB Debugging works on my PC. However USB Debugging doesn't work when I am in bootloader.
The only reason I want to do this is because I want to be able to enable "Multi Window" mode with out having a rooted device as I want to play games that don't allow a device to be rooted.
Thanks.
Your boot loader is locked by default that's why you get the rather helpful error output: "(remote: unlock device to use this command)" Always read error outputs and try to understand them .
What you'll have to do is to unlock your device , the great thing is that you have a Nexus phone so it will be easy.
Step 1: Go to settings -->> Developers options -->> OEM unlocking toggle it to ON.
Step 2: Reboot your device to fastboot mode
Step 3: Use the command
Code:
fastboot oem unlock
(This will wipe your device so back up your important files)
Step 4: Fastboot command will work now all of them be careful this freedom comes with responsibilities! You can easily soft brick your device.
A small consideration all the information I just gave you is easy to find! The search function on XDA is great and the pinned threads are gold :good:. It will also increase your understanding of the methods used and your device :highfive:
Xacky said:
Your boot loader is locked by default that's why you get the rather helpful error output: "(remote: unlock device to use this command)" Always read error outputs and try to understand them .
What you'll have to do is to unlock your device , the great thing is that you have a Nexus phone so it will be easy.
Step 1: Go to settings -->> Developers options -->> OEM unlocking toggle it to ON.
Step 2: Reboot your device to fastboot mode
Step 3: Use the command
Code:
fastboot oem unlock
(This will wipe your device so back up your important files)
Step 4: Fastboot command will work now all of them be careful this freedom comes with responsibilities! You can easily soft brick your device.
A small consideration all the information I just gave you is easy to find! The search function on XDA is great and the pinned threads are gold :good:. It will also increase your understanding of the methods used and your device :highfive:
Click to expand...
Click to collapse
Is this basically making the device rooted?
No, you are simply unlocking the bootloader so changes can be made. You won't be rooted until you have installed SuperSU. This is a good guide that will tell you everything: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Disclaimer :
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Warranty will be VOID
UNLOCK BOOTLOADER AND ROOT ASUS ZENFONE MAX PRO M2 (Unofficial)
<Device will be formatted, so keep a backup >
Requirements :
Asus Zenfone Max Pro M2
Windows / Linux
Instructions :
//unlocking
Phone:
- Go to Setting > System > About Phone and tap on the build number until developer option appears
- Go back to Settings > System > Developer options and enable usb debugging ( If you had already enabled usb debugging, ignore this step)
Windows:
- Download "unlocker" and extract the files
- Go to "adb + asus drivers" folder and install ADB and necessary drivers ( Linux users install adb, fastboot from their respective repositories )
- Connect the device to PC on a USB 2.0 port
- Go to "unlock" folder and open an Elevated command promt there and enter :
Code:
adb devices
( Allow usb debugging box will appear, check "always allow debugging from this computer" and click OK ) and again enter
Code:
adb devices
(Device should be listed)
Code:
adb reboot bootloader
(Device will now enter fastboot )
Code:
fastboot devices
(Device should be listed )
Now execute unlock.cmd (windows) or ./unlock.sh (linux)
Device will show unlocked bootloader warning, encrypt and reboot
Thats it, Bootloader is unlocked (Don't close the command prompt)
//rooting
- Download the recovery [ TWRP recommended ] and decrypt.zip from the links provided ( If you are on stock pie rom, use decrypt_pie.zip instead )
- Go to "Root" folder of unlocker and copy magisk.apk to phone
- Install magisk (update if available) > open > install > install > Download Zip only
- Note the location of the downloaded zip file and move it from there to sd card
- Move the decrypt.zip to sd card
- Go to sec. //unlocking > Phone to enable usb debugging again
- Copy the recovery image to "unlock" folder, go back to cmd and enter :
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery "name-of-the-recovery".img
- power off the device by pressing power button and go to recovery by pressing volume down + power button
- Device will boot into recovery
- If it asks for password, just cancel it
- Wipe > Format data
- Install > Flash decrypt.zip and magisk.zip that we copied to sdcard and reboot
[ IF THE DEVICE STILL ENCRYPTS ITSELF, FLASH THE RECOVERY AGAIN AND FLASH OREO FIRMWARE AND REPEAT THE ABOVE STEP ]
- Finally, go to magisk manager > install > install > direct install
- If you want to move to other recoveries, flash the respective recovery zip provided
- Reboot and You are done !
To unroot and relock the bootloader, Go HERE
Credits
@Sudeep Duhoon
@legacy07
Downloads:
Unlocker
Recoveries : TWRP / PBRP / OFRP / PERP / SHRP / Batik
Data Decryption
Data Decryption (Pie)
Piece of advice :
If there comes any problem with this unlock process, NEVER try to unlock by official unlock tool, as you will not be able to install custom recovery and finally end up in an unlocked bootloader device with no warranty and no custom recovery to proceed further!!!
in such cases fix the communication between phone and pc, instead of directly jumping to official tool
Wow..
Anyone try this??
what is the firmware version that is being used in this Indian root image? mine start with ww_xxxxx.....
Will the unofficial way of unlocking void warranty?
Dhairy said:
Will the unofficial way of unlocking void warranty?
Click to expand...
Click to collapse
Yes. Warranty will be void. But there is always a possibility of relocking bootloader to obtain warranty.
Was someone able to root successfully?
Yes. I confirm this works.
Which method did u use
Did u unlocked the bootloader and then flashed masgisk via twrp or via patched boot image method.
Free Radical said:
Yes. I confirm this works.
Click to expand...
Click to collapse
what is your firmware version that you root on?
learnyee said:
what is your firmware version that you root on?
Click to expand...
Click to collapse
Magisk method will work on the firmware released out of the box and also the update.
I am on stock firmware (without the first ota) and it works, nice bro
kickyvivi said:
Magisk method will work on the firmware released out of the box and also the update.
Click to expand...
Click to collapse
looked through the unock.cmd file, just hate to format the phone and reset up everything....
Which TWRP is being used in this??
#ArtFuL said:
Disclaimer :
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Warranty will be VOID
UNLOCK BOOTLOADER AND ROOT MAX PRO M2 (Unofficial)
<Device will be formatted, so keep a backup >
Requirements :
Asus Zenfone Max Pro M2
Windows OS
Instructions :
//unlocking
Phone:
- Go to Setting > System > About Phone and tap on the build number until developer option appears
- Go back to System > Developer options and enable usb debugging ( If you had already enabled usb debugging, "revoke USB debugging authorisations" and lets start new)
Windows:
- Download "unlocker" and extract the files
- Go to "adb + asus drivers" folder and install ADB and necessary drivers
- Go to "unlock" folder
- Open an Elevated command promt there and type :
adb devices ( Allow usb debugging box will appear, check "always allow debugging from this computer" and click OK and again enter :
adb devices (Device should be listed)
adb reboot bootloader (Device will now enter fastboot )
fastboot devices (Device should be listed )
Now execute unlock.cmd
Device will show unlooked bootloader warning, encrypt and reboot
Thats it, Bootloader is unlocked
//rooting
- Download the twrp recovery and Disable Forced Encryption/Data zip (decrypt.zip) from the links provided
- Go to "Root" folder of unlocker and copy magisk.apk to phone
- Install magisk (update if available) > open > install > install > Download Zip only
- Note the location of the downloaded zip file and move it from there to sd card
- Move the decrypt.zip to sd card
- Extract twrp, open an elevated command prompt and type :
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
- power off the device and go to recovery by pressing volume down + power button
- Device will boot into TWRP
- If it asks for decryption key, just cancel it
- Wipe > Format data
- Install > Flash decrypt.zip and magisk.zip that we copied to sdcard and reboot
- Finally, go to magisk manager > install > install > direct install
- Reboot and You are done !
You will receive OTA as usual
To unroot and relock the bootloader, Go HERE
Credits
@Sudeep Duhoon
@Shivam Kumar Jha
@#ArtFuL
Downloads:
Unlocker
TWRP
Data Decryption
Click to expand...
Click to collapse
What type of firmware/sku that u unlocked n install twrp?
X10MINISTER said:
What type of firmware/sku that u unlocked n install twrp?
Click to expand...
Click to collapse
ASUS ZenFone Max Pro (M2) Software Image Version: WW-15.2016.1811.177 For India SKU only
Not working as soon as I run the unlock.cmd file a prompt comes on the screen of the phone to press any key to shut down, after pressing any physical button it reboots to system again with no warning as bootloader unlocked
Dhairy said:
Not working as soon as I run the unlock.cmd file a prompt comes on the screen of the phone to press any key to shut down, after pressing any physical button it reboots to system again with no warning as bootloader unlocked
Click to expand...
Click to collapse
Edit the post with the method that worked for you
Dhairy said:
Not working as soon as I run the unlock.cmd file a prompt comes on the screen of the phone to press any key to shut down, after pressing any physical button it reboots to system again with no warning as bootloader unlocked
Click to expand...
Click to collapse
Got it working the problem is with adb it was installed and then I reinstalled it as given in steps, which might have broken the adb so if I performed the steps in ubuntu and everything worked perfectly. I am attaching the error images. If anyone else getting issue try uninstalling adb and drivers and then reinstalling adb and drivers.
Official way?
will there be official way?
prOzs said:
will there be official way?
Click to expand...
Click to collapse
There is official method available on asus support page for max pro m2.
Note: doing the official way there is no chance for relocking the bootloader and claiming warranty
Hey buddies,
Is there anything to do if my phone isnt working exept the fastboot mode, and I want to open the Bootloader, but I didnt allowed the OEM to be unlocked on the developer settings and I cant do it now because the phone cant turn on normally so I cant allow it from the settings?
If it matters, the model is "Nexus 5X".
Thanks alot!
You can check this topic Oem bootloader locked with no os installed!!! How can i flash phone to stock?!
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
Click to expand...
Click to collapse
But I have no access to the OEM (Or bootloader, I dont know if it is the same) too
I found this guide : guide-fix-bootloop-locked-bootloader-t3608679
I've refreshed the links:
You will need:
ADB + drivers installed: platform-tools
Nexus toolkit: Nexus Root Toolkit
STOCK image archive, older than you have now - Factory Images for Nexus
Latest OTA image archive : https://developers.google.com/android/ota#bullhead
-------------------
Extract stock image (NOT OTA)
install Nexus toolkit and restart your phone in Bootloader mode
connect phone to pc.
In nexus toolkit click on : advanced utilities > launch
look at: fastboot flash
click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache.
Copy downloaded OTA ROM archive in ADB folder.
reboot in recovery
now select apply update from adb.
open ADB
flash latest OTA package via command : adb sideload <packagename>.zip
I hope this works
Step 1 – Unlock the bootloaderIt is important to note the steps described below are intended for the unlocked carrier variant of the Pixel 4a 5g. Most U.S. carriers like to disallow bootloader unlocking, making it impossible to root your phone.
Go to System settings -> About phone -> tap on ‘Build number’ several times until Developer options are enabled
Back out into settings and go to System -> Advanced -> Developer Options -> Enabled ‘OEM Unlocking’
Unplug your phone if it’s plugged into anything and power it off
Boot into the Fastboot interface by holding Power + Vol Down or open Terminal/Shell/Command Prompt/PowerShell (depends on the OS) and type adb reboot fastboot
Plug the phone into your PC and open Terminal/Shell/Command Prompt/PowerShell (depends on the OS)
Type fastboot flashing unlock on the terminal and follow the prompt on your device to unlock the bootloader (Note that this step will factory reset the device)
The bootloader is now unlocked!
Step 2 – Patch the stock boot image using Magisk ManagerWhile you can find a pre-patched boot image for the Pixel 4a 5g here on xda, make sure to verify its origin. Any pre-patched boot image you download should match the installed software build version, otherwise, you may face severe anomalies. So in case they don't match(for instance the boot image here is for only Android 12 in case you have a higher or lower version as when you found this thread) recommend you patch the boot image yourself.
Download the factory firmware corresponding to the installed version of the stock ROM and extract the boot image from the archive
Copy the boot. img to your device
Install Magisk Manager (grab it from the release section of the project’s GitHub repo)
Open Magisk manager -> select ‘Install’ -> ‘Select and Patch File’ -> select your boot.img file
The patched boot image should be found inside your Download folder
Step 3 – Flash the patched boot image
Copy the magisk_patched.img to your PC you patched or for Android 12 download this on your PC
Reboot your device back into fastboot (see Unlock section above) or Boot into the Fastboot interface by holding Power + Vol Down or open Terminal/Shell/Command Prompt/PowerShell (depends on the OS) and type adb reboot fastboot
Open a terminal in the directory your patched boot img file is and type fastboot flash boot magisk_patched.image in Android 12 case will be fastboot flash boot magisk_patched-24200_x1HXn.img
You’re now rooted!
Have a look here for in-depth knowledge
Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin)
Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first try
PREPARATION
==========
Update zip file were from the 3.18 firmware on the redmagic.gg site https://help.redmagic.gg/hc/en-us/sections/360005986031-Global-ROMs-and-Updates
Extracted the payload.bin from the update zip file
All img files were dumped from payload.bin using Payload-Dumper-Go https://github.com/ssut/payload-dumper-go/releases
STEP ONE
==========
- Booted up my new device and updated to latest firmware (3.18) - SKIPPED all pin and fingerprint setups
- Rebooted
- Enabled developer settings
- Enabled bootloader unlocking in developer settings
- Powered off again
STEP TWO
==========
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced program (https://github.com/libxzr/FastbootEnhance/releases)
- Selected device by double clicking it and press "fastbootd" mode button
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)
STEP THREE
==========
- unlocked with command line in terminal:
- fastboot flashing unlock
- toggled to unlock with phone vol button
- fastboot flashing unlock_critical
- toggled to turn off device
STEP FOUR
==========
- Turned on and booted system to confirm it still loads
- Powered off again
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced
- Selected device and press "fastbootd" mode
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)
STEP FIVE
==========
- Flashed magisk patched init_boot with:
- fastboot flash init_boot FILENAME.img
- Flashed system partition with:
- fastboot system system.img
- Flashed vendor partition with:
- fastboot vendor vendor.img
- Selected power off
STEP FIVE
==========
- Started phone and booted to system
- Did basic setup SKIPPED all pin and fingerprint setups
- Once setup completed entered Phone Settings - Password and Security
- Proceeded to set pin AND fingerprint for lockscreen
STEP SIX
==========
- Run the magisk stub app to complete Magisk installation
I suspect a reflash of the Vendor partition (and maybe also system parititon) AFTER flashing the patched init_boot image is what fixed this.
Mine is eu version, started the phone and didn't set up any password, root the phone, then set fingerprint, so far so good, no need to flash the system or vendor img
ugene1980 said:
STEP THREE
==========
- unlocked with command line in terminal:
- fastboot flashing unlock
Click to expand...
Click to collapse
After this command does your phone reboot and wipe data?
edzchen said:
After this command does your phone reboot and wipe data?
Click to expand...
Click to collapse
Yup it does,
ugene1980 said:
STEP ONE
==========
- Booted up my new device and updated to latest firmware (3.18) - SKIPPED all pin and fingerprint setups
Click to expand...
Click to collapse
Can anyone confirm if this works for them if they previously set a screen lock after first boot?
edzchen said:
Can anyone confirm if this works for them if they previously set a screen lock after first boot?
Click to expand...
Click to collapse
as far as i can see, you need to factory reset the phone (to wipe out all data and settings), then root the phone.
magicsword123 said:
as far as i can see, you need to factory reset the phone (to wipe out all data and settings), then root the phone.
Click to expand...
Click to collapse
Did you fastboot unlock through the bootloader or do it after rebooting to fastboot?
I suspect this phone may be similar to the OnePlus 11. Many people have struggled to get screen-lock setup after unlocking the bootloader. The solution seems to be to NOT setup a screen lock when the bootloader is locked, and then it'll let you set one once you unlock. However, if you have a screen lock with the bootloader unlocked, and then re-lock your bootloader, you won't be able to set a screen lock in that state.
In short; Don't setup your lock screen until you get to the bootloader state you wish to remain in. I could be wrong, but I wonder.
jfsat said:
I suspect this phone may be similar to the OnePlus 11. Many people have struggled to get screen-lock setup after unlocking the bootloader. The solution seems to be to NOT setup a screen lock when the bootloader is locked, and then it'll let you set one once you unlock. However, if you have a screen lock with the bootloader unlocked, and then re-lock your bootloader, you won't be able to set a screen lock in that state.
In short; Don't setup your lock screen until you get to the bootloader state you wish to remain in. I could be wrong, but I wonder.
Click to expand...
Click to collapse
I see, will look into those forums.
For me unlocked BL screen lock never works
Locked BL screen lock always works
edzchen said:
Can anyone confirm if this works for them if they previously set a screen lock after first boot?
Click to expand...
Click to collapse
yes i can. i manually updated my UN rom to 3.18 and used it two days with fingerprint lock. I cleared it and reset my phone then done the instruction and fingerprint works. So can i use OTA in this case?
ugene1980 said:
Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin)
Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first try
PREPARATION
==========
Update zip file were from the 3.18 firmware on the redmagic.gg site https://help.redmagic.gg/hc/en-us/sections/360005986031-Global-ROMs-and-Updates
Extracted the payload.bin from the update zip file
All img files were dumped from payload.bin using Payload-Dumper-Go https://github.com/ssut/payload-dumper-go/releases
STEP ONE
==========
- Booted up my new device and updated to latest firmware (3.18) - SKIPPED all pin and fingerprint setups
- Rebooted
- Enabled developer settings
- Enabled bootloader unlocking in developer settings
- Powered off again
STEP TWO
==========
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced program (https://github.com/libxzr/FastbootEnhance/releases)
- Selected device by double clicking it and press "fastbootd" mode button
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)
STEP THREE
==========
- unlocked with command line in terminal:
- fastboot flashing unlock
- toggled to unlock with phone vol button
- fastboot flashing unlock_critical
- toggled to turn off device
STEP FOUR
==========
- Turned on and booted system to confirm it still loads
- Powered off again
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced
- Selected device and press "fastbootd" mode
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)
STEP FIVE
==========
- Flashed magisk patched init_boot with:
- fastboot flash init_boot FILENAME.img
- Flashed system partition with:
- fastboot system system.img
- Flashed vendor partition with:
- fastboot vendor vendor.img
- Selected power off
STEP FIVE
==========
- Started phone and booted to system
- Did basic setup SKIPPED all pin and fingerprint setups
- Once setup completed entered Phone Settings - Password and Security
- Proceeded to set pin AND fingerprint for lockscreen
STEP SIX
==========
- Run the magisk stub app to complete Magisk installation
I suspect a reflash of the Vendor partition (and maybe also system parititon) AFTER flashing the patched init_boot image is what fixed this.
Click to expand...
Click to collapse
Can confirm this worked for me too. I removed my screen lock and factory reset. Then followed these instructions exactly. Only difference was fastboot flashing unlock didnt work in fastbootd mode and only in bootloader.
I would like to greatly thank you @ugene1980 for your advice
vadizzi said:
yes i can. i manually updated my UN rom to 3.18 and used it two days with fingerprint lock. I cleared it and reset my phone then done the instruction and fingerprint works. So can i use OTA in this case?
Click to expand...
Click to collapse
Nope, ota won't work if you are rooted (patched init_boot.img)
All partitions must be stock for ota to work (bootloader can remain unlocked)
edzchen said:
Can confirm this worked for me too. I removed my screen lock and factory reset. Then followed these instructions exactly. Only difference was fastboot flashing unlock didnt work in fastbootd mode and only in bootloader.
I would like to greatly thank you @ugene1980 for your advice
Click to expand...
Click to collapse
Glad my experience was of use!
This phone is so gorgeous it's all worth the effort
i've unlock both, already at 3.18 non eu with root. try wipe everything and try do from step 4 but still not work :| trying to update 3.18 again and redo step
UPD: reupdate 3.18 again, relock, unlock and did everything like @ugene1980 and work like a charm!!!
ugene1980 said:
Nope, ota won't work if you are rooted (patched init_boot.img)
All partitions must be stock for ota to work (bootloader can remain unlocked)
Click to expand...
Click to collapse
Thank you very much. But how i can lock bootloader and use lockscreen? Also i didnt recieve any incremental ota for my 3.12-->3.18 UNCommon rom with locked loader
vadizzi said:
Thank you very much. But how i can lock bootloader and use lockscreen? Also i didnt recieve any incremental ota for my 3.12-->3.18 UNCommon rom with locked loader
Click to expand...
Click to collapse
To go back to stock/update you can boot to recovery then hold volume down for a few seconds to enable sideload. Then sideload update.zip. Then you can use
fastboot flashing lock
To relock bootloader
edzchen said:
To go back to stock/update you can boot to recovery then hold volume down for a few seconds to enable sideload. Then sideload update.zip. Then you can use
fastboot flashing lock
To relock bootloader
Click to expand...
Click to collapse
thanks. I needed to go to the fastbootD choose reboot to recovery and only then i have opportunity to use sideload
How can I update to version manually? Should I flash stock boot image, flash full OTA and then flash new rooted boot.img?
Yeah i did what you did except i had to unlock critical and bootloader in regular fastboot and held down volume button so that it wouldnt boot up afterwards. Then i flashed init boot in fastboot d
ugene1980 said:
Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin)
Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first try
PREPARATION
==========
Update zip file were from the 3.18 firmware on the redmagic.gg site https://help.redmagic.gg/hc/en-us/sections/360005986031-Global-ROMs-and-Updates
Extracted the payload.bin from the update zip file
All img files were dumped from payload.bin using Payload-Dumper-Go https://github.com/ssut/payload-dumper-go/releases
STEP ONE
==========
- Booted up my new device and updated to latest firmware (3.18) - SKIPPED all pin and fingerprint setups
- Rebooted
- Enabled developer settings
- Enabled bootloader unlocking in developer settings
- Powered off again
STEP TWO
==========
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced program (https://github.com/libxzr/FastbootEnhance/releases)
- Selected device by double clicking it and press "fastbootd" mode button
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)
STEP THREE
==========
- unlocked with command line in terminal:
- fastboot flashing unlock
- toggled to unlock with phone vol button
- fastboot flashing unlock_critical
- toggled to turn off device
STEP FOUR
==========
- Turned on and booted system to confirm it still loads
- Powered off again
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced
- Selected device and press "fastbootd" mode
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)
STEP FIVE
==========
- Flashed magisk patched init_boot with:
- fastboot flash init_boot FILENAME.img
- Flashed system partition with:
- fastboot system system.img
- Flashed vendor partition with:
- fastboot vendor vendor.img
- Selected power off
STEP FIVE
==========
- Started phone and booted to system
- Did basic setup SKIPPED all pin and fingerprint setups
- Once setup completed entered Phone Settings - Password and Security
- Proceeded to set pin AND fingerprint for lockscreen
STEP SIX
==========
- Run the magisk stub app to complete Magisk installation
I suspect a reflash of the Vendor partition (and maybe also system parititon) AFTER flashing the patched init_boot image is what fixed this.
Click to expand...
Click to collapse
Have you used any modules? I used safteynet and lsposwd so far