[GUIDE][Video/Text] How to Remove Unlocked Bootloader Warning on Moto X4 - Moto X4 Guides, News, & Discussion

How to Remove Unlocked Bootloader Warning on Moto X4​
Shoutout/Credits to xda member @AvenidaDelGato for the modified logo bin file.
​Text Guide.
Make sure adb and fastboot are setup and working.
Donwload and Unzip the modified logo file. Place logo3.bin in platform-tools folders, or whereever you have fastboot and adb.
Navigate to adb/fastboot folder
Windows
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash logo_a logo3.bin
Code:
fastboot flash logo_b logo3.bin
Code:
fastboot reboot
Mac/Linux
Code:
./adb devices
Code:
./adb reboot bootloader
Code:
./fastboot devices
Code:
./fastboot flash logo_a logo3.bin
Code:
./fastboot flash logo_b logo3.bin
Code:
./fastboot reboot
Downloads
Modified Logo.bin zip file - https://forum.xda-developers.com/showpost.php?p=77013516&postcount=4
Mirror of Modified logo.bin zip file - https://mega.nz/#!eYFiVaxT!mpt4RhJDToEcJG4TSpw-CBePLIhd_hm8OjRGTu3egoU
ADB and Fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Motorola Drivers - https://support.motorola.com/us/en/drivers

Thanks, that worked to remove the bootloader unlocked warning screen!
One other thing though is when the phone is first turned on while the Moto M logo is still on the screen (just before the Moto startup animation), a line of yellow console text appears over the Moto M logo that says "Verity mode is set to logging." Is there a way to turn that off? Aside from unlocking the bootloader, flashing the logo3.bin file and installing Magisk Manager from TWRP, my phone/ROM is a completely stock retail XT1900-1 (I didn't even flash TWRP to the recovery partition, I just booted it with fastboot to backup my device and install Magisk).
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.

kofruge said:
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
I think verity is set to logging is not part of the logo. It's a text message which is coming up for a reason i do not know.

Be careful with this method, when you receive updates via OTA, you will not be able to update them since they will get an error ...

Oh yeah, didn't think of that... Any way to fix OTA installation after flashing this?

kofruge said:
Thanks, that worked to remove the bootloader unlocked warning screen!
One other thing though is when the phone is first turned on while the Moto M logo is still on the screen (just before the Moto startup animation), a line of yellow console text appears over the Moto M logo that says "Verity mode is set to logging." Is there a way to turn that off? Aside from unlocking the bootloader, flashing the logo3.bin file and installing Magisk Manager from TWRP, my phone/ROM is a completely stock retail XT1900-1 (I didn't even flash TWRP to the recovery partition, I just booted it with fastboot to backup my device and install Magisk).
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
It worked for me as well on LOS 16, except for the Verity Logging Text, would be nice if we could turn that of too?

Just installed this and it works fine, but is there an Android One version/can one be made? Thanks!

MeowDotEXE said:
Just installed this and it works fine, but is there an Android One version/can one be made? Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x4/themes/bootlogo-custom-bootlogos-dark-variant-t3832118

is there a way to restore the old logo?

vidra said:
is there a way to restore the old logo?
Click to expand...
Click to collapse
Just fastboot flash the boot logo file part of the factory firmware.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

munchy_cool said:
How to Remove Unlocked Bootloader Warning on Moto X4​
Shoutout/Credits to xda member @AvenidaDelGato for the modified logo bin file.
Text Guide.
Make sure adb and fastboot are setup and working.
Donwload and Unzip the modified logo file. Place logo3.bin in platform-tools folders, or whereever you have fastboot and adb.
Navigate to adb/fastboot folder
Windows
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash logo_a logo3.bin
Code:
fastboot flash logo_b logo3.bin
Code:
fastboot reboot
Mac/Linux
Code:
./adb devices
Code:
./adb reboot bootloader
Code:
./fastboot devices
Code:
./fastboot flash logo_a logo3.bin
Code:
./fastboot flash logo_b logo3.bin
Code:
./fastboot reboot
Downloads
Modified Logo.bin zip file - https://forum.xda-developers.com/showpost.php?p=77013516&postcount=4
Mirror of Modified logo.bin zip file - https://mega.nz/#!eYFiVaxT!mpt4RhJDToEcJG4TSpw-CBePLIhd_hm8OjRGTu3egoU
ADB and Fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Motorola Drivers - https://support.motorola.com/us/en/drivers
Click to expand...
Click to collapse
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?

HACK3DANDR0ID said:
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
Click to expand...
Click to collapse
No need to quote the OP.

HACK3DANDR0ID said:
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
Click to expand...
Click to collapse
i dont make bootlogos
download android one firmware, and flash logo.bin from there

munchy_cool said:
i dont make bootlogos
download android one firmware, and flash logo.bin from there
Click to expand...
Click to collapse
Found what i was looking for thanks

kofruge said:
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
wanb1i said:
It worked for me as well on LOS 16, except for the Verity Logging Text, would be nice if we could turn that of too?
Click to expand...
Click to collapse
Flash the attached modified bootloader (unzip first).
Code:
fastboot flash bootloader no-verity-warning-bootloader.img
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Code:
SHA256SUMs:
b2efd37d2bef4e2de5bcbd7ca3e643a1e1e246d597e6ed4389679d321bebd2f0 no-verity-warning-bootloader.img
fcf3391a13f757d3f998c9b14c5ef40e6084d65b2d0162273d3842e75f972281 no-verity-warning-bootloader.zip

gleenfield97 said:
Flash the attached modified bootloader (unzip first).
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Click to expand...
Click to collapse
It worked for me, thank you heaps!

gleenfield97 said:
Flash the attached modified bootloader (unzip first).
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Click to expand...
Click to collapse
I tried this, and bootlooped. I am on stock 9.0 Retail US. Perhaps this is not the right one for my device.

jhedfors said:
I tried this, and bootlooped. I am on stock 9.0 Retail US. Perhaps this is not the right one for my device.
Click to expand...
Click to collapse
Maybe it's not compatible with stock. I'm using Havoc.

The AndroidOne logo.bin if anyone else needs it.
Extracted from stock XT1900-1_PAYTON_FI_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
Md5: e306b8ea948a10ec304ca62ebcd60495

Just a warning: after flash the bootlogo file, it seems this change prevent OTA updates. Some hours ago, i receive the 2019 july security patch update and it fails at 90-95 percent. I make a factory reset and it didn't help. Then I flashed the stock rom and the update install very well.

Related

GUIDE: How to make backups and restore stock. || stock + patched images here

If you are not able to boot a patched boot image or a twrp image on Android 10, here is a workadound.
Machi007 said:
Boot TWRP and images is possible also on Android 10, but it needs some workaround...
1) Turn phone into Download Mode
2) Use command fastboot flash recovery twrp.img where twrp.img is your TWRP image you want to boot up
It shows this error (it is OKAY):
Code:
FAILED (remote: '(recovery_a) No such partition') //This is because an A/B Device does not have a recovery partition. It's located in the boot partition itself.
3) Now you can boot your TWRP recovery image, for example: fastboot boot twrp.img
Click to expand...
Click to collapse
Hay Guys!
One of the most important things on Android is to make backups. Every time you want to root or flash something, make backups!
I saw many people struggling with OTA because they didn't make backups to restore there images.
=========================================================================
If you DONT have any backup, but you want to restore stock, I'll upload all my stock backups as well as all patched boot images in this mega:
https://mega.nz/#F!52B0HCID!A1k8PiGn9OQbiEa_IJ3_EQ
This is just in case something went wrong with you backup. You should still make your own backups!!!
=========================================================================
In this post I will show you how to create a backup and how to restore it.
There are 2 ways to backup your Phone images.
TWRP:
Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Boot into TWRP. you can use the TWRP image from my mega. DO NOT FLASH IT!!!
Code:
fastboot boot twrp.img
Hit the Backup button and backup boot image, system image and vendor image.
If you want to restore this images, you can restore them with TWRP. Just hit the restore button.
This may not work for all Devices. But you can flash the images via fastboot too.
The fastboot files looks like boot.emmc.win. Dont worry, this is img file. So you can rename it to boot.img or something.
ADB:
1Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Find out your current slot
Code:
fastboot getvar current-slot
Boot into a patched boot image.
Code:
fastboot boot patched.img
Your phone shoud boot up. If it does,
then open ADB.
In ADB type there commands to dump the images.
Get root access by typing the "su"
Dump your boot, system and vendor from your current slot you found out on step 2
(The commands for dumping an image are below)
If you want to restore this images, you can restore them via fastboot.
Code:
fastboot flash [boot_{current-slot}/system_{current-slot}/vendor_{current-slot}] <image file>
Replace the {current-slot} with your current slot.
Example:
Current slot is a and you want to restore the boot image.
Code:
fastboot flash boot_a boot_a.img
If you still have Questions or need help, feel free to pm me.
Also you can leave a comment under this post.
Commands for dumping images:
#Backup A boot:
Code:
dd if=/dev/block/mmcblk0p52 of=/sdcard/boot_a.img
#Backup B boot:
Code:
dd if=/dev/block/mmcblk0p53 of=/sdcard/boot_b.img
#Backup A vendor:
Code:
dd if=/dev/block/mmcblk0p83 of=/sdcard/vendor_a.img
#Backup B vendor:
Code:
dd if=/dev/block/mmcblk0p84 of=/sdcard/vendor_b.img
#Backup A system:
Code:
dd if=/dev/block/mmcblk0p81 of=/sdcard/system_a.img
#Backup B system:
Code:
dd if=/dev/block/mmcblk0p82 of=/sdcard/system_b.img
Great tutorial and much appreciated. On the first sentence... There is a typo on the word "thinks".. it should be "things".
Danny1976 said:
Great tutorial and much appreciated. On the first sentence... There is a typo on the word "thinks".. it should be "things".
Click to expand...
Click to collapse
Thanks. fixed it :good:
Hail brother! Tnx!
might have shot the capability of OTA on experimenting with TWRP and it's possibilites of taking backups.
thought, I was careful, but wasn't enough.
so THANKS a lot for providing all the information and (of course) : the sp1 images.
January stock and patched images is now uploaded.
Hi! I have a Problem with the wifi not working after flashing back stock boot.img on slot a & b....if anyone could help I'll be grateful.
emicloud91 said:
Hi! I have a Problem with the wifi not working after flashing back stock boot.img on slot a & b....if anyone could help I'll be grateful.
Click to expand...
Click to collapse
Did you flash your own backups?
Do you have global 6.1?
Also, why did you flash A AND B?
¥sBielefeld said:
Hay Guys!
One of the most important things on Android is to make backups. Every time you want to root or flash something, make backups!
I saw many people struggling with OTA because they didn't make backups to restore there images.
=========================================================================
If you DONT have any backup, but you want to restore stock, I'll upload all my stock backups as well as all patched boot images in this mega:
https://mega.nz/#F!52B0HCID!A1k8PiGn9OQbiEa_IJ3_EQ
This is just in case something went wrong with you backup. You should still make your own backups!!!
=========================================================================
In this post I will show you how to create a backup and how to restore it.
There are 2 ways to backup your Phone images.
TWRP:
Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Boot into TWRP. you can use the TWRP image from my mega. DO NOT FLASH IT!!!
Code:
fastboot boot twrp.img
Hit the Backup button and backup boot image, system image and vendor image.
If you want to restore this images, you can restore them with TWRP. Just hit the restore button.
This may not work for all Devices. But you can flash the images via fastboot too.
The fastboot files looks like boot.emmc.win. Dont worry, this is img file. So you can rename it to boot.img or something.
ADB:
1Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Find out your current slot
Code:
fastboot getvar current-slot
Boot into a patched boot image.
Code:
fastboot boot patched.img
Your phone shoud boot up. If it does,
then open ADB.
In ADB type there commands to dump the images.
Get root access by typing the "su"
Dump your boot, system and vendor from your current slot you found out on step 2
(The commands for dumping an image are below)
If you want to restore this images, you can restore them via fastboot.
Code:
fastboot flash [boot_{current-slot}/system_{current-slot}/vendor_{current-slot}] <image file>
Replace the {current-slot} with your current slot.
Example:
Current slot is a and you want to restore the boot image.
Code:
fastboot flash boot_a boot_a.img
If you still have Questions or need help, feel free to pm me.
Also you can leave a comment under this post.
Commands for dumping images:
#Backup A boot:
Code:
dd if=/dev/block/mmcblk0p52 of=/sdcard/boot_a.img
#Backup B boot:
Code:
dd if=/dev/block/mmcblk0p53 of=/sdcard/boot_b.img
#Backup A vendor:
Code:
dd if=/dev/block/mmcblk0p83 of=/sdcard/vendor_a.img
#Backup B vendor:
Code:
dd if=/dev/block/mmcblk0p84 of=/sdcard/vendor_b.img
#Backup A system:
Code:
dd if=/dev/block/mmcblk0p81 of=/sdcard/system_a.img
#Backup B system:
Code:
dd if=/dev/block/mmcblk0p82 of=/sdcard/system_b.img
Click to expand...
Click to collapse
Can these images be used for downgrade to oreo? I am on pie (ta1068), unrooted and loocked bootloader.
Windoors said:
Can these images be used for downgrade to oreo? I am on pie (ta1068), unrooted and loocked bootloader.
Click to expand...
Click to collapse
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
¥sBielefeld said:
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
Click to expand...
Click to collapse
How to do it with NTool?
JurreTas said:
How to do it with NTool?
Click to expand...
Click to collapse
You need to buy Ntool credits. Just google it
¥sBielefeld said:
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
Click to expand...
Click to collapse
I heard in nokia 6.1 u don't need to downgrade to unlock bootloader (just change slot a to b).
Anyways, if I have already unlocked my bootloader can i downgrade to oreo without ntool? Thanks
Windoors said:
I heard in nokia 6.1 u don't need to downgrade to unlock bootloader (just change slot a to b).
Click to expand...
Click to collapse
Nokia changed the Bootloader unlock algorithm with the August patch. So you need to be pre August patch.
A B slots work work like this:
Start: A(June)B(June) Currentslot A -> OTA UPDATE -> A(June)B(July) Currentslot B -> OTA -> A(August)B(July) current slot A and so forth.
So. If you are on Slot A and you have Januar installed, you B slot is on December. This means, switching the Slot does not help you with the bootloader unlock.
You have to downgrade.
Windoors said:
Anyways, if I have already unlocked my bootloader can i downgrade to oreo without ntool? Thanks
Click to expand...
Click to collapse
Yes you can use OST LA for downgrade if you are unlocked. Make sure you are critical unlocked too.
Thanks for clarifying. I unfortunately updated to January patch.
March update just released (V3.51F) with 530 MegaByte...
This is not just a security update but a complete software update.
Waiting for your files @MEGA.
Do we have to flash more than boot, system and vendor?
Last time (with pie october patch) radio and some other files were updated!
Updated to march security patch.
klauer said:
March update just released (V3.51F) with 530 MegaByte...
This is not just a security update but a complete software update.
Waiting for your files @MEGA.
Do we have to flash more than boot, system and vendor?
Last time (with pie october patch) radio and some other files were updated!
Click to expand...
Click to collapse
Why do you want to flash more?`If you are rooted, flash stock boot image. If ur modified ur system, flash stock system.
If you are complete stock, install OTA
Btw. Stock images for march are online
Are your images from Global version ? I had issues updating to March OTA (said that some partitions were modified) so I flashed your boot.img and system.img, but I still cannot update.
Solannae said:
Are your images from Global version ? I had issues updating to March OTA (said that some partitions were modified) so I flashed your boot.img and system.img, but I still cannot update.
Click to expand...
Click to collapse
Yes, they are global. I hade this issue a few weeks ago too. I had to reflash my phone for some reason...

Help with root access for Nokia 3 running Android Pie

Could anyone please help with a guide for rooting Nokia 3 and flashing TWRP that works for Android 9.0?
Thanks.
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
Thank you for your answer.
What if you don't have your bootloader unlocked ? Do you just need to check the "Unlock Bootloader" switch in the developers options ? Thank you
Soupape50 said:
Thank you for your answer.
What if you don't have your bootloader unlocked ? Do you just need to check the "Unlock Bootloader" switch in the developers options ? Thank you
Click to expand...
Click to collapse
The only way Is unlocking the bootloader
Just follow this steps and it's done
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
Zhowlx said:
The only way Is unlocking the bootloader
Just follow this steps and it's done
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
Click to expand...
Click to collapse
Thank you really much for your answer, but I don't think this tutorial works on android Pie :/
unfortunately not, I downgrade the android version to nougat and from there I did the whole process, then updated to oreo and then to android p
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
have tried it?
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
Can you give more details like what zip ? what apk ( magisk or magisk manager)? How to boot into recovery? (Samsung is easier to boot than nokia so i dont know how to)
Zhowlx said:
unfortunately not, I downgrade the android version to nougat and from there I did the whole process, then updated to oreo and then to android p
Click to expand...
Click to collapse
Hey. How to downgrade nokia 3 from pie to nogaut ? I want to root my device
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
Click to expand...
Click to collapse
How can I remove the orange state?
I mean, currently, if I lock the bootloader again, I get a red state.
and I can only skip it, if I connect it to the usb.
and start normally, without any status warning, if it is connected to the usb
djxpro said:
How can I remove the orange state?
I mean, currently, if I lock the bootloader again, I get a red state.
and I can only skip it, if I connect it to the usb.
and start normally, without any status warning, if it is connected to the usb
Click to expand...
Click to collapse
perhaps flash an unmodified boot image?
NulledRoot said:
perhaps flash an unmodified boot image?
Click to expand...
Click to collapse
that implies then that I could not root it.
****
I guess I'll keep the orange state.
NulledRoot said:
fastboot -i 0x2e04 oem key [MD5-key]
Click to expand...
Click to collapse
>>>>fastboot: unknown option -- i
TA-1032, android 9 (00W_5_120_SP02), OEM unlocking in dev.opt. enabled.
NOWAY!
ORANGE STATE (^_^)
fastboot oem key [md5 KEY]
fastboot flashing unlock
fastboot reboot
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked[/QUOTE
How to get MD5-key ?
Click to expand...
Click to collapse
Hasnain77 said:
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked[/QUOTE
How to get MD5-key ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
you need your SN from your phone and put it on the web that is in the thread
Click to expand...
Click to collapse
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
Click to expand...
Click to collapse
I am in very trouble to rooting my Nokia 3 ta-1032 pie... Pls help me how to unlock bootloader and flash twrp and root on nokia 3 pie security patch 5 October 2019:crying::crying:help me plz
aditya#777 said:
I am in very trouble to rooting my Nokia 3 ta-1032 pie... Pls help me how to unlock bootloader and flash twrp and root on nokia 3 pie security patch 5 October 2019:crying::crying:help me plz
Click to expand...
Click to collapse
get the twrp recovery image file from unofficialtwrp.com/nokia-3-root-twrp-3-2-3 ....
rename the file to recovery.img and put the file in adb directory.....also put the magisk.zip file in the sd card (don't put it in the internal memory)
then get into fastboot mode....then enter the following commands....
fastboot oem key [md5 hash]
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
while rebooting, instantly press vol up+power to go into recovery mode( dont let the phone to boot normally or you will have to flash twrp again and your phone might be in orange state but ignore that)....if it shows "no command" press the same buttons at the same time to get into recovery mode.....then install the magisk.zip and reboot....then install magisk.apk and you are done.... tried and tested on nokia 3 ta- 1032 android pie just today and it worked...
mech59 said:
get the twrp recovery image file from unofficialtwrp.com/nokia-3-root-twrp-3-2-3 ....
rename the file to recovery.img and put the file in adb directory.....also put the magisk.zip file in the sd card (don't put it in the internal memory)
then get into fastboot mode....then enter the following commands....
fastboot oem key [md5 hash]
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
while rebooting, instantly press vol up+power to go into recovery mode( dont let the phone to boot normally or you will have to flash twrp again and your phone might be in orange state but ignore that)....if it shows "no command" press the same buttons at the same time to get into recovery mode.....then install the magisk.zip and reboot....then install magisk.apk and you are done.... tried and tested on nokia 3 ta- 1032 android pie just today and it worked...
Click to expand...
Click to collapse
can you confirm that this method to root the phone is still working right now with the latest updates of nokia 3?
freaks211 said:
can you confirm that this method to root the phone is still working right now with the latest updates of nokia 3?
Click to expand...
Click to collapse
Don't do it !!! After rooting TA-1032 Pie 9, camera does not work !!!
Hier is what I did:
$ adb devices
$ adb reboot bootloader
$ fastboot devices
$ echo -n "NE1GXXXXXXXXXXXX" | md5sum | tr a-z A-Z | awk '{print $1}'
$ fastboot oem key YOUR-KEY
# the first time did not accepted
$ fastboot -i 0x2e04 oem key YOUR-KEY
$ fastboot oem key YOUR-KEY
$ fastboot flashing unlock
$ fastboot reboot
# Installed magisk v23.apk
$ fastboot flash boot magisk_patched-23000_7R099.img
$ fastboot reboot
I can confirm that this works on Nokia3 TA-1032, but the problem is the camera.
All you get is green background, if anyone knows hot to fix the green
background, please let me/us know.
Thank you,

Road to the unlock Verizon device.

how to flash patched kernel on google pixel 3 via ADB?
Myoko150 said:
how to flash patched kernel on google pixel 3 via ADB?
Click to expand...
Click to collapse
If you are referring to a Magisk patched kernel, do the following. The name of the img file now has some random letters appended to it.
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
dcarvil said:
If you are referring to a Magisk patched kernel, do the following. The name of the img file now has some random letters appended to it.
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
I have a locked bootloader, I cannot use the "fastboot" commands
it would be so simple...

General [TWRP] Xiaomi 12

This TWRP works with Xiaomi 12
📌 [Shared] TWRP by skkk
⚡⚡A12/A13⚡⚡ ----------------------- BOOT VERSION Installation: Phone in fastboot mode Cmd: fastboot boot twrp.img or Power shell ./fastboot boot twrp.img then in Twrp go to Advanced -> flash current TWRP...
forum.xda-developers.com
Command to install:
1. boot your device in Fastboot mode
2. fastboot boot recovery_finename.img
This will temporary boot your device to TWRP
3. From TWRP go to Advanced and choose "Flash curent TWRP" - this will permanently install TWRP but will overwrite magisk scripts, so root will be lost.
4. Flash magisk from TWRP - this will fix root.
Thanks bro.
will this lost data or need to clear any caches after done installation TWRP?
you loose nothing and no caches to clear
geraldine said:
you loose nothing and no caches to clear
Click to expand...
Click to collapse
Well noted that.
I've tried and success!
Thanks again!
3.8.4
skkk/TWRP/A12/v3.8.4_A12 • AKR DL
dl.akr-developers.com
update 3.9
skkk/TWRP/A12/v3.9_A12 • AKR DL
dl.akr-developers.com
What does "boot" or "REC" mean? I always thought twrp is just a one file?
REC it's for direct flash the recovery with "fastboot flash recovery.img" (doesn't work for me)
BOOT it's for boot to the recovery "fastboot boot recovery.img" to flash permently go to advanced and "flash current twrp" (work great)
geraldine said:
update 3.9
skkk/TWRP/A12/v3.9_A12 • AKR DL
dl.akr-developers.com
Click to expand...
Click to collapse
Can I update from 3.8?
What is the changelog?
Yes, but you lose root. if there is.
double post, sorrry**
mmm, dont work for me, idk if im doing something wrong, when i put the command (fastboot boot recovery_name.img) it restarts, but the screen stays black and need the force the start.
I download this [BOOT]3.6.2_12-Mi12_v3.9_A12-cupid-skkk_632fca0d.img maybe im wrong with the version =/
darkevangelion said:
mmm, dont work for me, idk if im doing something wrong, when i put the command (fastboot boot recovery_name.img) it restarts, but the screen stays black and need the force the start.
I download this [BOOT]3.6.2_12-Mi12_v3.9_A12-cupid-skkk_632fca0d.img maybe im wrong with the version =/
Click to expand...
Click to collapse
There is a newer:
Downloading • AKR DL
immerzu2 said:
There is a newer:
Downloading • AKR DL
Click to expand...
Click to collapse
Thank you!! this version work, is it reccommended to make it permanent? i dont use root or magisk.
Hello. I have the latest TWRP installed on my Xiaomi 12. A friend of mine installed it. I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me. I don't know what I'm doing wrong, but the phone still won't boot into TWRP. I'm using ADB minimal and I renamed the downloaded file to twrp.img and put it in ADB minimal, then I used the command mentioned above, but still nothing happens, the phone won't enter TWRP. Once it enters TWRP, I use the command: "flash current twrp", I already know the next procedure. I welcome help. Thanks
Benoni1 said:
Hello. I have the latest TWRP installed on my Xiaomi 12. A friend of mine installed it. I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me. I don't know what I'm doing wrong, but the phone still won't boot into TWRP. I'm using ADB minimal and I renamed the downloaded file to twrp.img and put it in ADB minimal, then I used the command mentioned above, but still nothing happens, the phone won't enter TWRP. Once it enters TWRP, I use the command: "flash current twrp", I already know the next procedure. I welcome help. Thanks
Click to expand...
Click to collapse
" I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me"
Check with"fastboot devices"CMD or "./fastboot devices"Powershell before
the phone must be in fastboot mode.
CMD=fastboot boot recovery twrp.img
Powershell=./fastboot boot recovery twrp.img
Then use the twrp
go to Advanced > Flash Current TWRP
The Twrp .img must be in the same folder as the command.
Possibly post the screenshot of the result of the command
Flash TWRP-I still can't do it, I'm sending pictures
Benoni1 said:
Flash TWRP-I still can't do it, I'm sending pictures
Click to expand...
Click to collapse
Already said in the post above.
1/You wrote "fasboot" instead of fastboot.
2/Download SDK platform-tool extract the folder and put the twrp in it.
https://developer.android.com/studio/releases/platform-tools
3/ use the command from the folder where the twrp is.
NOSS8 said:
Already said in the post above.
1/You wrote "fasboot" instead of fastboot.
2/Download SDK platform-tool extract the folder and put the twrp in it.
https://developer.android.com/studio/releases/platform-tools
3/ use the command from the folder where the twrp is.
View attachment 5688077​
Click to expand...
Click to collapse
Hello, I already know it was successful. Thank you for your help. Best regards, Josef
fastboot flash recovery xxx.img is not correct.
the command is: fastboot flash recovery_ab xxx.img
A question: why the twrp version jumped from from 3.x directly to 5.x?

Question I do everything correctly to root but it keep booting in to the bootloader

My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
What device are you talking about ?
f1tm0t said:
What device are you talking about ?
Click to expand...
Click to collapse
Tab p11 4gig
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
f1tm0t said:
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
Click to expand...
Click to collapse
Threr is no twrp sadly
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
mingkee said:
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
Click to expand...
Click to collapse
I tried it i flashed patched boot.img only in fastbootd still boots me in to the bootloader
LSS4181 said:
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
blocky3321 said:
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
Click to expand...
Click to collapse
Which Magisk version did you use? From what I can tell any official Magisk version should work.
I haven't really tested the recent builds of vvb2060's Alpha or huskydg's Delta... so if you're using these versions I can't really help you much...
Additionally, you need to check which slot you are now, and through fastbootd check which slot actually has system, vendor and such. Normally the super partition only has enough size for one slot. You may have entered a wrong slot that doesn't have usable system.
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
Getting Started: What's Your Device ?
Tab p11 4gig
Device->settings->About : Model & Hardware -> Lenovo ??? (Tb-j606f,TB-J616F...) In your case stiker on box or on back.
mingkee said:
who told you to flash vbmeta.img?
Click to expand...
Click to collapse
???

Categories

Resources