Related
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Root Doogee BL12000
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck ?
Root Bl12000
Since the SuperSu method took me nowhere I decided to try Magisk. And.......HURRAY !!!!!!.......it worked.....for a moment. Booted the patched boot.img and got superuser. But with the first reboot I got stuck in bootloop. Tried again, in case I missed something, but same ****.
IT WORKS !!!!! My mistake was to assume, that Magisk works the same way as rooting with SuperSu does. So after rooting with Magisk I tried to install root apps as I was used to, but Magisk does not work that way.
Well, it'll take me awhile to figure this out ?
Why does an app keep coming back on my phone after I have done factory reset?
Christian1968.Bolz said:
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Lucky Patcher 9Apps VidMate
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck
Click to expand...
Click to collapse
This Recovery is only supported for Doogee BL12000
You should have either PC or Laptop.
Make sure to charge your phone for at least 50%.
Download and install latest Doogee USB Drivers on your PC/Laptop [All Android USB Drivers]
Download the SP Flash Tool Software
VCOM driver: Download – Instal the VCOM Driver on your computer (still compatible with MT67xx phones)
Before flashing a custom recovery, you need to unlock the bootloader on Doogee BL12000
Take a full backup just in case if you need it later
TWRP+root bl 12000
joachim97 said:
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Click to expand...
Click to collapse
On the forum 4pda can be found for bl 12000
TWRP+ROOT
when you install twrp formatting you can not do it, but immediately install magisk and reboot ...
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com
I just got one of these bad boys and i about rooted it and flashed an older models ROM before i realized i had the 2021 model
I imagine we will have to wait for stock firmware to show up before we can root
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
If you loaded Magisk and are having problems with banking app look at this post and he has another setting in Magisk that you can change to fix this. It is under the heading "a note about mobile banking apps".
Rooting with Magisk
Just a heads up to anyone who is wondering about root for this phone - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus...
forum.xda-developers.com
kbwojo said:
I imagine we will have to wait for stock firmware to show up before we can root
Click to expand...
Click to collapse
Stock firmware maybe available with LMSA' s Flash rescue option
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Fun... I made my first brick using that panda build box link.
kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
Is there a way to root the xt2117-1 version without a pc?
Knox-jack said:
Is there a way to root the xt2117-1 version without a pc?
Click to expand...
Click to collapse
No
Rooting these phones is dead simple. If you boot into bootloader mode, you can find your device's codename. Look for your codename on the lolinet site, select your varient, and download your firmware. Be sure to share the codename here so links can be updated.
Then you unlock your bootloader, patch boot.img you got from the firmware archive with Magisk, and flash the patched image through fastboot.
Seen any Roms for this floating around?
pontifier said:
Fun... I made my first brick using that panda build box link.
Click to expand...
Click to collapse
Did you FLASH recovery.img, instead of BOOT recovery.img?
It's pretty hard to perma brick phones these days. You can probably reflash device with LMSA -
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
I have tried this method on a linux system and a windows version and yhe twrp program always goes to straight to a lockscreen and doesnt stay
kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
Hello. I just got one of these on accident. Meant to get a G9 Power. Oh well. I will still love it. Having rooted countless phones and a great many Motos, I went to root mine without looking for instructions. I fastboot flashed the entire RETUS from lolinet, magisk patched and flashed the new kernel, and then booted to a phone without a working digitizer. Not only that, but when I flashed the original back on it, it didn't fix it. Still no digitizer. I then flashed the entire RETUS again, including the same kernel, and it fixed, but of course I had to set everything up again. I made a fastboot command list though, for flashing firmware from lolinet, if anyone could use it. It's on my computer though. I'll have to share it later. I just made this post to warn others of possible problems with a magisk-patched boot.img.
And also to thank @kbwojo . I've many times wished we could use twrp from a command line. Where did you learn that? Is there a manual?
Oh, BTW, the codename for xt2117-4 is borneo.
arkansawdave74 said:
Hello. I just got one of these on accident. Meant to get a G9 Power. Oh well. I will still love it. Having rooted countless phones and a great many Motos, I went to root mine without looking for instructions. I fastboot flashed the entire RETUS from lolinet, magisk patched and flashed the new kernel, and then booted to a phone without a working digitizer. Not only that, but when I flashed the original back on it, it didn't fix it. Still no digitizer. I then flashed the entire RETUS again, including the same kernel, and it fixed, but of course I had to set everything up again. I made a fastboot command list though, for flashing firmware from lolinet, if anyone could use it. It's on my computer though. I'll have to share it later. I just made this post to warn others of possible problems with a magisk-patched boot.img.
And also to thank @kbwojo . I've many times wished we could use twrp from a command line. Where did you learn that? Is there a manual?
Oh, BTW, the codename for xt2117-4 is borneo.
Click to expand...
Click to collapse
I did try a few things that didn't work. What I ended up doing was just flash boot the original boot.img and that basically reset magisk
Just giving an update and a thanks again to @kbwojo . I finally booted a patched kernel by patching a kernel extracted with twrp in the command line. All the kernels from lolinet caused me to lose touch support after patching, even if I was running the same version the kernel was from. But when I patched it after pulling the kernel with twrp, all is good. Whew. That was different.
Well i have done it. I have rooted my phone .
moto g power (2021)
model XT117-4
Android version 10
basebrand version : HA10_18.534.0273R BORNEO_NA_CUST
Kernel version 4.19.95-perf + #1 Wed Mar 31 12:08:54 CDT 2021
After extensive reading multiple threads i found one and followed the attemt using magisk and no twrp installed.
1st Magisk installed on phone
2nd Install magisk and then patch using the boot.img from a mirror site for Borneo
3rd (not sure yet) Install magisk and then patch file recovery.img (originaly TWRP 3.4 renamed)
renamed the 2 magisk files accordingly to boot and recovery
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
restarted phone directly back into fastboot mode
selected recovery option and started the phone
Sucessful Root!!!!
slickmojo said:
Well i have done it. I have rooted my phone .
moto g power (2021)
model XT117-4
Android version 10
basebrand version : HA10_18.534.0273R BORNEO_NA_CUST
Kernel version 4.19.95-perf + #1 Wed Mar 31 12:08:54 CDT 2021
After extensive reading multiple threads i found one and followed the attemt using magisk and no twrp installed.
1st Magisk installed on phone
2nd Install magisk and then patch using the boot.img from a mirror site for Borneo
3rd (not sure yet) Install magisk and then patch file recovery.img (originaly TWRP 3.4 renamed)
renamed the 2 magisk files accordingly to boot and recovery
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
restarted phone directly back into fastboot mode
selected recovery option and started the phone
Sucessful Root!!!!
Click to expand...
Click to collapse
Can anyone confirm this works?
Just bought a G Power 2021 after thinking it was supported for custom roms already. It should just be arriving today and if i can't unlock the bootloader and root it I'm going to be returning it and getting the 2020, which I'm already considering even if i can be rooted.
Thank you
MyNameIsEarlB said:
Can anyone confirm this works?
Just bought a G Power 2021 after thinking it was supported for custom roms already. It should just be arriving today and if i can't unlock the bootloader and root it I'm going to be returning it and getting the 2020, which I'm already considering even if i can be rooted.
Thank you
Click to expand...
Click to collapse
the 2021 can be rooted, that is what I use with root, and heavily modified UI. You can even change things so system is writable (but will need a computer with linux, or a VM to complete the process), after bootloader unlocked and rooted. But does not presently have any custom ROMs for the device, however some in this branch of the forums have cited they are working on one. If I had the time to, I'd tinker and try my hand at porting LineageOS, or similar fairly easy to port, since TWRP is mostly done or doable for 99% of these devices, there are some that still have touch issues, and that seems to be all digitizer and screen related like mentioned in this thread. As long as you restore yours from the Motorola software and grab your stock files, when they are restored, it has touch, you know you can always fix it back even if a test flash of TWRP has no touch. But then it is not that hard to build from those files the TWRP, even in Android Image Kitchen. I made mine have touch support the hackish way before the compiled way.
So it can absolutely be done, just play things smart with it is all keeping backups of vital files and so on so you have stock even with data loss as the worst that would happen from messing about.
Edit: You will need to keep the device online, wifi and cell data for at least a day if not two before bootloader unlock option in settings will usually permit being toggled on. I know in my experience I got mine on a Friday, and it was not till Sunday about mid-day that it popped, and I'd check it every few hours that I was awake otherwise in that time.
Onoitsu2 said:
the 2021 can be rooted, that is what I use with root, and heavily modified UI. You can even change things so system is writable (but will need a computer with linux, or a VM to complete the process), after bootloader unlocked and rooted. But does not presently have any custom ROMs for the device, however some in this branch of the forums have cited they are working on one. If I had the time to, I'd tinker and try my hand at porting LineageOS, or similar fairly easy to port, since TWRP is mostly done or doable for 99% of these devices, there are some that still have touch issues, and that seems to be all digitizer and screen related like mentioned in this thread. As long as you restore yours from the Motorola software and grab your stock files, when they are restored, it has touch, you know you can always fix it back even if a test flash of TWRP has no touch. But then it is not that hard to build from those files the TWRP, even in Android Image Kitchen. I made mine have touch support the hackish way before the compiled way.
So it can absolutely be done, just play things smart with it is all keeping backups of vital files and so on so you have stock even with data loss as the worst that would happen from messing about.
Edit: You will need to keep the device online, wifi and cell data for at least a day if not two before bootloader unlock option in settings will usually permit being toggled on. I know in my experience I got mine on a Friday, and it was not till Sunday about mid-day that it popped, and I'd check it every few hours that I was awake otherwise in that time.
Click to expand...
Click to collapse
Thank you very much!
I'm perfectly happy with needing to make my own custom ROM. I've never done it, but I've been wanting to for quite some time. At least a few years.
The last 2 android phones I've been using couldn't even be rooted. Long story short, i bought a redmi 5, got it all setup great, then moved and the only service around my new area is Verizon so i sold that, bought a note 5, couldn't root it, bought a pinephone which i do love, but the battery life is really bad. So I've been using my note 5 that's close to a decade old so I'm just looking for a phone with root and a good battery life.
Look forward to getting mine rooted!
Quick question, hopefully doesn't derail too much. Wondering if there is any work being done on the XT2165-5 model? Can't seem to find anything on it?
Hi, I've just bought a Cubot P50, it's a Chinese brand and seems more than decent for the price, I've rooted it with Magisk and I want to install TWRP on it but can't find anything for that brand. Has anyone came across a TWRP that might work on it?
Marko Lyno said:
Hi, I've just bought a Cubot P50, it's a Chinese brand and seems more than decent for the price, I've rooted it with Magisk and I want to install TWRP on it but can't find anything for that brand. Has anyone came across a TWRP that might work on it?
Click to expand...
Click to collapse
I have the same phone how did you root it ? If there a guide that is safe to use ? Thank you
Unlock the bootloader first, this step will factory reset your phone https://romprovider.com/unlock-bootloader-android/
On your PC:
1. Install Fastboot driver
2. Install MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed
3. Extract platform-tools
4. On your phone, Enable Developer Options, USB debugging and OEM Unlocking
5. Unlock bootloader (this step will factory reset your phone): Phone in fastboot mode, open command prompt on PC > fastboot devices > fastboot flashing unlock. Note this will cause the phone to show the "Orange State" warning on boot up. You can ignore this or remove it later.
(If device is unauthorised in ADB or Fastboot, go to Developer Options on phone, revoke USB debugging authorisation, disable then enable USB debugging. You should now get an authorisation confirmation dialogue when you try to connect with ADB/Fastboot. If not, type "adb kill-server", then "adb devices" or "adb start-server" in the command prompt).
6. Place boot.img on phone with USB file transfer (either from stock ROM, or read from phone using SP_Flash_Tool_v5.1924_Win) and patch it with Magisk v5.2. NO need to patch vbmeta.img
7. Transfer patched boot.img back to PC
8. Flash the patched boot.img to phone either with SP Flash Tool or Fastboot command in ADB (fastboot flash boot boot.img). Take care here, make sure it's the right image going to the right location and that ALL other files are de-selected, especially the preloader file, always de-select this when flashing any firmware unless you know what you're doing!
Phone is now rooted.
How to remove orange state warning on this device:
How to remove Orange, Yellow & Red state warnings on MTK
This guide will explain how to hide or remove Yellow, Red and Orange state warnings on a Mediatek Android device. Its ideal for those who feel irritated by constantly seeing these warnings on reboot.
www.hovatek.com
Edit: If you need a stock ROM for the phone it's here https://www.cubot.net/Support/id/78/cid/19.html#hh
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom?
Thank you have a nice day.
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom on the Cubot p50?
Thank you have a nice day.
Mark8:9 said:
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom on the Cubot p50?
Thank you have a nice day.
Click to expand...
Click to collapse
It is possible that in the future, developers may create custom ROMs and TWRP recoveries for the device, especially if it becomes popular among the Android community.
If a custom ROM and TWRP recovery becomes available for your device in the future, you will be able to flash it by following the instructions provided by the developer. Keep in mind that installing custom ROMs and recoveries comes with some risks, and it is important to backup your data and follow the instructions carefully to avoid damaging your device.
Good evening, can you tell me the correct procedure for how to Root the Cubot p50 smartphone? Thank you.
Mark8:9 said:
Good evening, can you tell me the correct procedure for how to Root the Cubot p50 smartphone? Thank you.
Click to expand...
Click to collapse
Well if you really want to know that, surely you would have read the entire thread? It's not that long. I gave complete instructions 5 posts up
Marko Lyno said:
Well if you really want to know that, surely you would have read the entire thread? It's not that long. I gave complete instructions 5 posts up
Click to expand...
Click to collapse
Good evening, be patient ... but where do I find Magisk 5.2 to download and how do I install it? Thanks good evening.
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Just get the latest version and follow the instructions I posted.
Thanks for your work on the Cubot phone .Im a fan of them also. I found that twrp recovery 3.40 works on the Note 20/20Pro you just have to flash vbmeta BEFORE and AFTER you flash twrp to the device. Im also seeing separate websites claiming twrp 3.40 is also used with the Cubot P40 model. I dont see why it wouldnt work with the P50. Its worth a shot. Also theres alot more "familiars" with Mediatek phones like these in Hovatek forum. Since you already have information on how to root maybe consider starting your own P50 thread over there.
My references: https://www.hovatek.com/forum/thread-44810-post-233457.html#pid233457
elimoviebuff said:
Thanks for your work on the Cubot phone .Im a fan of them also. I found that twrp recovery 3.40 works on the Note 20/20Pro you just have to flash vbmeta BEFORE and AFTER you flash twrp to the device. Im also seeing separate websites claiming twrp 3.40 is also used with the Cubot P40 model. I dont see why it wouldnt work with the P50. Its worth a shot. Also theres alot more "familiars" with Mediatek phones like these in Hovatek forum. Since you already have information on how to root maybe consider starting your own P50 thread over there.
My references: https://www.hovatek.com/forum/thread-44810-post-233457.html#pid233457
Click to expand...
Click to collapse
Thanks for that. Is there a specific vbmeta to patch it with?
Good evening, can you give me the link to download a compatible cust recovery for the cubot p50? Thank you
The link is on the page just posted above. Here's the direct link to the file:
Hovatek
Download files
www.hovatek.com
Let us know if it works please, and what steps you took.
Good evening, how will I flash the lk file? Thanks.
Hi, you will have, or should have, downloaded a zip file containing a recovery.img. The recovery.img is the file you need to flash. Then follow the instructions here:
How to Install TWRP Recovery on Any Android 2022 [100% Working]
In this article, I will be showing you how you can install TWRP recovery on any Android smartphone. By following this guide you will be able to install
magiskapp.com
The TWRP Recovery file it refers to is the one you (hopefully) downloaded from this link:
Hovatek
Download files
www.hovatek.com
BUT, you also need to flash a vbmeta file BEFORE and AFTER the recovery.img, and I'm still unsure which vbmeta file it is, as elimoviebuff hasn't replied to my question regarding that.
Marko Lyno said:
Hi, you will have, or should have, downloaded a zip file containing a recovery.img. The recovery.img is the file you need to flash. Then follow the instructions here:
How to Install TWRP Recovery on Any Android 2022 [100% Working]
In this article, I will be showing you how you can install TWRP recovery on any Android smartphone. By following this guide you will be able to install
magiskapp.com
The TWRP Recovery file it refers to is the one you (hopefully) downloaded from this link:
Hovatek
Download files
www.hovatek.com
BUT, you also need to flash a vbmeta file BEFORE and AFTER the recovery.img, and I'm still unsure which vbmeta file it is, as elimoviebuff hasn't replied to my question regarding that.
Click to expand...
Click to collapse
I get it, but I have to flash the .bin to remove the yellow/red state on boot. I don't know how to install the lk.bin file. If you can help me. Thank you.
Ah I see, you're rooting the phone first. Ok I've just checked my own notes on this, so, if you have edited the lk.img file as described in that Hovatek thread, then do as follows:
When flashing with SP Flash Tool, make sure the correct lk.img file is chosen as SP Flash Tool chooses lk-verified.img by default (click along to the right of the file list under "Location" and choose your edited lk.img file here).
OR, flash with ADB (fastboot flash lk lk.img).
Then install Magisk on your phone if you haven't already.
boot.img is for rooting the phone, lk.img is only to remove the orange state message and the 5 second delay when the phone boots, it does not actually remove it's orange state and is not needed for the phone to be rooted.
To un-root, you should just flash the original boot.img and lk-verified.img from the stock firmware ROM file.
Marko Lyno said:
Ah I see, you're rooting the phone first. Ok I've just checked my own notes on this, so, if you have edited the lk.img file as described in that Hovatek thread, then do as follows:
When flashing with SP Flash Tool, make sure the correct lk.img file is chosen as SP Flash Tool chooses lk-verified.img by default (click along to the right of the file list under "Location" and choose your edited lk.img file here).
OR, flash with ADB (fastboot flash lk lk.img).
Then install Magisk on your phone if you haven't already.
boot.img is for rooting the phone, lk.img is only to remove the orange state message and the 5 second delay when the phone boots, it does not actually remove it's orange state and is not needed for the phone to be rooted.
To un-root, you should just flash the original boot.img and lk-verified.img from the stock firmware ROM file.
Click to expand...
Click to collapse
Good morning. Thank you for the information given.
I wanted to ask: is it necessary or useful to install an antivirus on your smartphone now that it's been rooted? Thank you.
I haven't but that's just down to personal choice really. It's certainly useful if you like to try stuff from unknown sources, although personally I've rarely encountered viruses on Android. I'm not saying they don't exist though.
Have you successfully rooted your phone then? What about TWRP, have you tried that yet?