Related
Custom ROMs are one of the best things about Android. One of the best things about the openness of the Android platform is that if you're unhappy with the stock OS, you can install one of many modified versions of Android (called ROMs) on your device. A new ROM can bring you the latest version of Android before your manufacturer does, or it can replace your manufacturer-modded version of Android with a clean, stock version. But with the introduction of the dynamic partition flashing Custom ROMs are a bit tricky. In this post, I will run you through the steps of flashing Custom ROMs on your Poco X3.
Pre-requisites:
Unlocked Bootloader
Custom Recovery
Note:- Always create a backup of your important files before flashing.
Steps:-
From MIUI to Custom ROM
Encrypted
Copy the Custom ROMs zip to your sdcard or your OTG flash drive.
Boot to the recovery.
Flash the required firmware mentioned for the ROM.
Reboot your recovery.
Flash the Custom ROM.
And then format data [**This will wipe your internal storage**]
Reboot (Flash magisk if you want root after the first boot)
Decrypted
Flash this decrypted vendor
Flash the custom rom
Format data and reboot
From Custom ROMs to Another Custom ROM
Encrypted
**Backup your internal storage, incase something gets wrong**
Remove your lockscreen password
Boot to the recovery
Wipe Data, Cache and Dalvik Cache
Flash Custom ROM
Reboot
** If the device bootloops Format Data **
Decrypted
*If your device is encrypted*
Flash the decrypted vendor
Flash the custom rom
Format data and reboot
*If your device is already decrypted*
Wipe data and cache
Flash rom
Reboot
Notes:-
For encrypted people
Always create a backup of your internal storage.
Format data while upgrading from one android version to another.
Downgrading firmware may also require data format
Moving from Gapps build to non-gapps build or vice versa also requires fata format
For decrypted people
You don't need to flash the decrypted vendor everytime unless you come from miui
The vendor will not work on miui
All credits to POCO X3 Developers & Custom ROM Community.
Regards,
Polvolt
You saved me. I had properly unlocked bootloader, flashed OrangeFox but then I did the wipes and also mistakely formated data, so I couldn't send files from PC to phone to flash the custom rom.
Guess I could've just used the usb otg at this point, but I reflashed MIUI with a script, and reflashed OrangeFox and now I'm good to go.
I thought current custom recoveries don't check for rollback protection (yet)?
It's probably safe to be flashing stock firmwares via custom recovery if you are sure you know what you're doing. But this guide seem to appeal to new comers. Should we suggest they stick to using Mi Flash tool for flashing stock firmwares as it has rollback protection checks?
Or am I just out of the loop and this is no longer the case with custom recoveries for surya/karna?
Thanks for the guide btw. Greatly appreciated.
I miss manually flashing each partition files via fastboot like when I was on my Nexus devices and my Essential PH-1. I have not seen a guide that recommends or even teaches us to flash partitions manually.
payas0 said:
I thought current custom recoveries don't check for rollback protection (yet)?
It's probably safe to be flashing stock firmwares via custom recovery if you are sure you know what you're doing. But this guide seem to appeal to new comers. Should we suggest they stick to using Mi Flash tool for flashing stock firmwares as it has rollback protection checks?
Or am I just out of the loop and this is no longer the case with custom recoveries for surya/karna?
Thanks for the guide btw. Greatly appreciated.
I miss manually flashing each partition files via fastboot like when I was on my Nexus devices and my Essential PH-1. I have not seen a guide that recommends or even teaches us to flash partitions manually.
Click to expand...
Click to collapse
Yes it is safe to flash stock fw via custom recovery. ARB hasn't been implemented on surya yet.
Well manual flashing each partition using fastboot on surya is much more complicated. Dynamic partition work differently. In short one have to boot to fastboot than boot to fastbootd than you can flash rom
Are you sure it's not enabled? After running fastboot getvar anti, I get anti: 2 and I just bought the phone without doing any upgrades. Unless this alone doesn't mean that ARB is enabled?
Mckol said:
Are you sure it's not enabled? After running fastboot getvar anti, I get anti: 2 and I just bought the phone without doing any upgrades. Unless this alone doesn't mean that ARB is enabled?
Click to expand...
Click to collapse
No only if you get "anti:4" itmeans ARB is enabled, otherwise feel free to downgrade via fastboot.
Kineceleran said:
No only if you get "anti:4" itmeans ARB is enabled, otherwise feel free to downgrade via fastboot.
Click to expand...
Click to collapse
Seems you're wrong. This XDA article states other way:
"
How to find current rollback index
Reboot to fastboot mode
Enter the following command: fastboot getvar anti
If the output is blank, then anti-rollback has not yet been enabled. If you get a number in the output, then that’s your current rollback index."
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
How about from MIUI Global to MIUI EU ? I've found a 12.0.7.0, not sure but it seems to be EU rom, right?
Hello
I'm new to Xiaomi phones! For the love of God someone tell me how do I flash roms on my poco x3 nfc Note ( I've been flashing roms for years but not Xiaomi phones ). What ever I flash it works but after I attempt to flash another rom files in sd card get corrupt and I format data that doesn't gonna do anything! So please someone tell me how do I flash roms on this phone. My phone is encrypted I was on MIUI global
ayad.phonex said:
Hello
I'm new to Xiaomi phones! For the love of God someone tell me how do I flash roms on my poco x3 nfc Note ( I've been flashing roms for years but not Xiaomi phones ). What ever I flash it works but after I attempt to flash another rom files in sd card get corrupt and I format data that doesn't gonna do anything! So please someone tell me how do I flash roms on this phone. My phone is encrypted I was on MIUI global
Click to expand...
Click to collapse
I suppose you do have already unlocked bootloader and installed recovery? if no, please do, if yes try this guide or read this post
I'm having trouble because I flashed the vendor and it does not work in my version (QJGMIXM) and 4g internet does not work. I need help to fix because I can't find original vendor file or return to MIUI. HELP!!!!!
biliterror said:
I'm having trouble because I flashed the vendor and it does not work in my version (QJGMIXM) and 4g internet does not work. I need help to fix because I can't find original vendor file or return to MIUI. HELP!!!!!
Click to expand...
Click to collapse
Use any fastboot stock ROM and MiFlash tool to restore your phone...or flash any custom recovery and use it to flash any recovery stock ROM to restore your phone.
I have 6 days to wait for unlocking the device. I can't wait to get rid of the Mi UI mess and bloat. I haven't had to do a complicated (for me) phone flash process like this since a Motorola phone in 2014. I have a a few questions:
1- Do I need to add/install adb drivers to my WIN10 PC? I came across win adb drivers for the POCO in my search for Windows PC drivers. Which version of adb is needed for Win10? I currently have abd my laptop, but I can't determine the version.
2- Installing the recovery - I see the steps some have posted with TWRP versions, but I'm not really clear on this. Do I go to the folder with TWRP in it and then use a command prompt from there? TWRP or Orange Fox and what version? The posts are confusing.
3- I'd like to have the easiest rom flash for my first go at this phone. I would appreciate a recommendation for which rom might be the best one to start with. I will be want gapps as part of the process, but could flash afterwards if its better that way. Is Arrow OS or Havoc a good choice?
Sorry for all the questions.
Thanks
If i flash a newer Firmware (.7) over the decrypted vendor (.5), is my phone encrypted again?
Grusel said:
If i flash a newer Firmware (.7) over the decrypted vendor (.5), is my phone encrypted again?
Click to expand...
Click to collapse
if you'll flash 12.0.7 vendor from this thread, then no
Is this the right way?
Flash the CustomRom and after flash format Data?
Not first format Data and than flash Customrom?
My plan after bootloader Wait time is flash the Miui Eu Rom.
What ist the right way?
trutta said:
Is this the right way?
Flash the CustomRom and after flash format Data?
Not first format Data and than flash Customrom?
My plan after bootloader Wait time is flash the Miui Eu Rom.
What ist the right way?
Click to expand...
Click to collapse
Flashing ROM and Format data is the usual way....
I now. But the chronologie was another. First Format data, then flash Rom.
Usually in all my old device while flashing roms I have to wipe system data cache then I just flashed the rom, it's my first Xiaomi device I am confused as hell , should i never have to wipe system partition ? , Is flashing firmware necessary everytime ? Are there any risks associated with decrypted vendor ?please guide me I am not noob but these things are completely new to me
Device storage partition schemes have changed and are now dynamic, so previous procedures don't apply anymore. Closely follow your ROM developer instructions in order to avoid bricking your device.
Dynamic Partitions | Android Open Source Project
source.android.com
Brother, i have Karna (Indian) one with me. I got update to latest MIUI 12.0.8, after updating i unlocked the bootloader and flashed twrp, but it dint wrok, then had to flash OFox. RN i am on latest lineageOS 17.1. I am having network issues. Someone at the telegram group told me to flash the firmware along with the vendor of 12.0.5 MiUi as he also suffered the same kind of network issue i am having.
but the problem is i am unable to find the Vendor n firmware of 12.0.5. Can you please help me ?
I want to access /data/system/users//settings_ssaid.xml to know what my game unique id is.
But after some research i learned that i have to root to able to get there but i have almost zero knowledge about it.
Are there any guide to root Redmi Note 10 from the scratch? Thanks.
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm on official global ROM 12.5.3.0 RKGMIXM
And i turned on OEM Unlocking in developer mode yesterday (Which is confuse me a little a guide said i have to wait for 7 days for this but mine is nothing it's just switched to on)
OEM Unlocking is only one of the steps, but it does not unlock the bootloader. File a request with Xiaomi.
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
inn0ichi said:
...
i recommend only booting to twrp, not flashing it
...
Click to expand...
Click to collapse
Why do you recommend to only booting to TWRP instead of flashing it?
Pasarireng said:
Why do you recommend to only booting to TWRP instead of flashing it?
Click to expand...
Click to collapse
because the twrp developer instruction is to booting , not flashing
alonsoj636 said:
because the twrp developer instruction is to booting , not flashing
Click to expand...
Click to collapse
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Risk of bootloop
Pasarireng said:
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Click to expand...
Click to collapse
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Y
alonsoj636 said:
Risk of bootloop
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Click to expand...
Click to collapse
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Pasarireng said:
Y
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Click to expand...
Click to collapse
Yes , is the correct way
inn0ichi said:
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
Click to expand...
Click to collapse
Please confirm these;
*So we can:
Use TWRP only temporarily, only to root the phone (by flashing Magisk v23),
and then,
back to using the stock recovery on our RN10 afterward,
even if the RN10 is already rooted?
**If the answer for my question above is yes, then (in RN10 condition of Unlocked Boot Loader, Rooted, Stock MIUI & Stock Recovery) ;
Would we still get official OTA Update from Xiaomi (and can download and install the update- as how it's like before rooting the phone)?
Thank you in advance
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
StaryMuz said:
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
Click to expand...
Click to collapse
Thanks again, (and maybe I will try your suggestion later).. but (sorry)... your reply doesn't answer my questions.
(I think my questions are very clear and probably very easy to be answered by someone who has experience/knowledge about it (like you?).. no?)
Forgive my nooby questions.
But I really want to know as much as I can (especially about the answer for some questions I have inside my head about the matter, like I asked above),.. before executing doing something about my phone.
oops... I'm sorry for double send
In the past I rooted Miui and then continued to get OTA updates. However, this cannot be confirmed for all versions of Miui. Each new update changes the phone software and so what worked before may not work today.
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
First of all, I would like to point out that Magisk (root) is a security risk. Without understanding the issues, the phone is more easily exploitable.
To install, just download the magisk file with the ZIP extension. In recovery, select the install option and select this file. Once installed, exit recovery and boot the system. Once the system boots, use magisk and complete the installation it requests.
Lolitary said:
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
Click to expand...
Click to collapse
the answer above is right ... but i would suggest to flash Orange Fox zip and then Magisk zip... to avoid problems
isn't there decrypt.zip for RN10?
How to decrypt this phone?
I usually did that along with rooting with my android phones before this.
Edit:
Update:
It's ok now I understand how, after watching this video.
I don't understand the need to build a custom recovery? Can't someone just flash using just fastboot?
Does anyone know any instructions on how to flash A/B devices with custom rom using fastboot? Also I see now there is a fastbootd?
nexuspb said:
I don't understand the need to build a custom recovery? Can't someone just flash using just fastboot?
Does anyone know any instructions on how to flash A/B devices with custom rom using fastboot? Also I see now there is a fastbootd?
Click to expand...
Click to collapse
Unless ive been living under a rock or something has radically changed, fastboot will only ever flash ROM's in img format, not ROM's in zip format like most custom ROM's....that said custom GSI's (based off Google GSI's) come in .img format (sometimes zipped first)
Your best bet is to find your devices home section on XDA and work from there....as usually if youve thought it, someone else has before you, and so checking to see if its already been done before in the much more focused section where your device is discussed is a faster resolve than post in a general Q&A thread...
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do
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?