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?
Related
Has anyone been able to figure out how to root the Alcatel idealXTRA (5059r)? I have been able to make a modded boot image with Magisk but I can not flash it to my phone because I need a DA file for SP Flash Tool specifically for this phone
I've been able to unlock the bootloader with Android "Tool all in one" which i found on here sometime ago. Actually have gotten a "successful" flash thru adb bootloader but with no effect on the device. I've tried a variety of tools, you'll need MtkDroidTools (Mediatek specific tool) and a host of other things and pherhaps you'll have some luck. I however did not. It appears that this specific device and its hardware are simply beyond my skills in rooting which are extensive so I question the viability of the exercise all together. That being said I still devote multiple hours a month attempting.
SUCCESS!!
The DA file your speaking of is actually located in the SP Tool folders : \SP_Flash_Tool_v5.1904_Win\\MTK_AllInOne_DA.bin
Disclaimer this method is finicky at best but on my device has worked, I take no responsibility for bricked/destroyed devices nor voided warranties. This simply resembles the method I used to successfully root my Alcatel 5059r Device nothing more
Alright I'm going to do a small write up with links for you. I'm assuming you have your bootloader unlocked and Magisk rooting is sufficient bc if its not well your not going to be able to root this device. First we need stock firmware, magisk manager 7.0, and the flashing tool that works with this phones MediaTek CPU.
HTML:
https://alcatelfirmware.com/alcatel-onetouch-ideal-xtra-5059r
Here you'll find both the stock firmware and the SP Flash Tool for this particular hardware.
You'll also need the latest Magisk Manager app on your phone(great idea for after you root if you've saved it on your SD as well as its the first thing you want to install after). You can find that on XDA or Github or a simple google search.
In short you need to patch the stock firmwares boot.img with Magisk Manager in order to gain root.
Once you've downloaded your Firmware, Tool, and .apk of Magisk Manager extract the boot.img from the stock firmware .zip/.rar then move it a storage path somewhere you can find it on your device. THEN DELETE THE BOOT.IMG THAT REMAINS IN THE .ZIP FOLDER
Start magisk manager and you'll probably get a big red X on Magisk 18.1, press it and install > patch boot image, select the stock boot.img we extracted to your pc then moved to your device.
With the Patch_boot.img move it off your devices storage back onto windows. Then add it back into the .zip/.rar Stock Firmware folder. Now we have a complete set of stock firmware flashed with Magisk 18.1 and ready to go!
Now you have a properly rooted boot.img now onto the flash
SP Flash Tool is a finicky tool at best, I always got error codes but was successful. Start off by shutting off your phone and unplugging the USB if your connected.
Extract the patched stock firmware .zip/.rar
Extract SP Flash tool, and run the flashtool.exe
From here you can follow the basic instructions on the website I posted
If you need an Auth file run a search here in XDA and you'll find a nice little .zip with an Auth file in it that works.
Your Scatter file is in the stock firmware, Auth file above.
With your phone still off & disconnected and your 3 drop boxes on the SP Flash Tool full and looking like the guide on the website. Press download. Attach your phone to USB and hit Volume up or down. Here is kind of the tricky part and trust me error codes don't necessarily mean there was any error. I ended up using the windows chimes to tell when the device was picked up, it disconnects pretty quickly but in between connection/disconnect chimes you have enough time to hit download again and you should get a Red Line on the bottom of SP tool saying 100% Completed, although probably with an error code. I did this routine of flashing in between chimes probably 10 times.
Reboot and yes your phone has been wiped, first thing you'll want to do is reinstall magisk manager and with any luck you should have green checks beside both boxes.
Proofs
https://forum.xda-developers.com/picture.php?albumid=15313&pictureid=58444
https://forum.xda-developers.com/picture.php?albumid=15313&pictureid=58445
Rooted with magisk and built twrp
deleted
Well in case anyone wants to work on this I'm uploading TWRP
deleted
deleted
Deleted
deleted
Can't seem to get root to work on gsi
deleted
Here's some good stuff and how I got recovery and LOS 16 on alcatel idealxtra 5059r
https://forum.xda-developers.com/an...16-alcatel-t3933004/post79586479#post79586479
LgPWN'd said:
Here's some good stuff and how I got recovery and LOS 16 on alcatel idealxtra 5059r
https://forum.xda-developers.com/an...16-alcatel-t3933004/post79586479#post79586479
Click to expand...
Click to collapse
EVEN BETTER LOOK AT OUR TELEGRAM GROUP
https://t.me/Android_General_Chat
ROMS
TOOLS
RECOVERIES
ROOT LIVES THERE
come join in the fun
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?
Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.
Does anyone have a guide on how to root a Xiaomi Redmi Note 10? I’m a novice Android user so any help will be appreciated. Thanks
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
Thanks mate. Will wait for the phone to be unlocked then will try these steps.
hello, I followed the whole procedure and the phone only reboots in bootloop or after several reboots it brings me back to Fastboot
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
what about vbmeta?
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
I do not understand the question
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
titifayls said:
I do not understand the question
Click to expand...
Click to collapse
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
precisely I did not take magisk v22 but v21, moreover I have exactly the same version as the first poster is 12.0.1 RKGEUXM.
To root I took the boot.img from version 12.0.2, was it an error?
I tried to reflash the original boot.img file from v12.0.2 but still in bootloop
I can not find anywhere where to take my original version yet up to date v12.0.1
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Slim K said:
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Click to expand...
Click to collapse
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
titifayls said:
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
Click to expand...
Click to collapse
I asked if you're using windows or linux to connect to your phone. About losing data, maybe a clean flash could be required, but trying first won't hurt.
Here is how you do it: (you can use the downloaded fastboot firmware, because your device is unlocked, so region differences won't matter that much when flashing full firmware):
Inside that .tgz archive (that you unarchived) you'll find a script called flash_all_except_data_storage.bat for windows or flash_all_except_data_storage.sh for linux. (Do not use the flash_all_lock.bat/.sh script or risk a hard brick, so read carefully this time!!!!)
Connect your device in fastboot mode and open a CMD/Terminal where those scripts and the rest of the firmware files are. Use fastboot devices to make sure device is recognized.
If it is, then type in fastboot followed by dragging and dropping the flash_all_except _data_storage.bat to your CMD/terminal and press Enter. The process should begin automatically. If you get an error, make sure to have typed a space after the fastboot command and before the dropped script.
If it takes a long time during flash of super, don't panic!! Super.img is a very big file
Done!
If it still bootloops after that, then use the flash_all.bat script (will factory reset your phone and delete data)
It doesn't matter, it gives me the list of commands but doesn't launch anything
Wouldn't it be better to put fastboot flash?
don't bother, I'll take miflash, it'll be easier
I delivered an eea_global_images_V12.0.2.0.RKGEUXM rom with miflash by putting flash_all_except_data_storage.
I recovered everything at startup, my applications everything, so I redid the manipulation for the root and now everything works, perfect
thank you
I did the above process successfully.
Also if new update comes out, the process must be done again (not including the unlocking part of course).
The ROMs are posted here
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
pihpih95 said:
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
Click to expand...
Click to collapse
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
pihpih95 said:
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
Click to expand...
Click to collapse
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Slim K said:
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Click to expand...
Click to collapse
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
pihpih95 said:
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
Click to expand...
Click to collapse
I used the latest as well. Most of the time, it errors out and I can't see the time left, but sometimes it works. Don't forget, you're giving them your imei for the freedom of your phone. Those imei's must be stored on Chinese servers and the tool must query those servers to get any info, depending on your country it may not work at all.
My experience with using an older tool has been very bad, the time was extended to 2 weeks instead of one on an another Xiaomi device. Avoid doing that and wait the requested time first.
After following the instruction my phone keeps rebooting.
I tried the flash_all.bat without success. What could I do?
Received the tablet in the mail, and now looking to root via Magisk (and ideally a custom recovery like TWRP).
I found this video describing a way to download the stock ROM from Teclast:
Has anyone achieved root on this device? Can anyone confirm Treble ROM compatability for GSI A/B?
On the russian forum 4pda somebody posted the patched boot.img and vbmeta.img files required for rooting.
If anyone is registered on the forum he might try to grab the files, for me it gives 404 error when trying to download, though im not registered..
Teclast T40 Plus - Обсуждение - 4PDA
Teclast T40 Plus - Обсуждение, Планшет, 10,4
4pda.to
NightLord said:
On the russian forum 4pda somebody posted the patched boot.img and vbmeta.img files required for rooting.
If anyone is registered on the forum he might try to grab the files, for me it gives 404 error when trying to download, though im not registered..
Teclast T40 Plus - Обсуждение - 4PDA
Teclast T40 Plus - Обсуждение, Планшет, 10,4
4pda.to
Click to expand...
Click to collapse
Good find, but the link no longer works. It gives me a 404: https://4pda.to/forum/dl/post/24458874/T40_Plus_root.7z
My guess is it would work if we were logged in, its just that i cant create an account since i cannot get past rhe russian captcha
Yeah, I also can't register without knowing the Russian keyboard layout and how to identify the characters. Perhaps someone with this knowledge can register and attach the required images to root here?
Slightly off topic while someone manages to grab the files from 4pda
Do you actually get 50000+ gpu score in antutu with the t40? I have the maxpad i11 which is in theory the same hardware, and I only get 42000. I even flashed the t40 firmware on the device, but gpu score didnt budge.
To be on topic: if you want root, you may also flash phhuson's treble GSI rom-s. I tried his version of android 12, and it works, and has root.
NightLord said:
Slightly off topic while someone manages to grab the files from 4pda
Do you actually get 50000+ gpu score in antutu with the t40? I have the maxpad i11 which is in theory the same hardware, and I only get 42000. I even flashed the t40 firmware on the device, but gpu score didnt budge.
To be on topic: if you want root, you may also flash phhuson's treble GSI rom-s. I tried his version of android 12, and it works, and has root.
Click to expand...
Click to collapse
These ROMs? https://github.com/phhusson/treble_experimentations/releases
ForgottenSolstace said:
These ROMs? https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Yes.
You can either install them via DSU as dual-boot OS beside your stock rom, or just flash system partition (inside super) via fastbootd (you are going to have to delete product partition to have enough space inside super for the system image) and use them as primary OS.
Gotcha:
Just ordered a T40 Plus, did you manage to get root?
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
NightLord said:
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
Click to expand...
Click to collapse
Hi NightLord, can you explain easily the root steps for this device? do we need the software that we see in the video at the beginning or is ADB enough?
Marynboy78 said:
Hi NightLord, can you explain easily the root steps for this device? do we need the software that we see in the video at the beginning or is ADB enough?
Click to expand...
Click to collapse
Hey,
You need to use the spreadtrum research download tool (RDT), not the one seen in tthe video in the first post.
See this guide on how to use the RDT.
The basic concept is that you need to download the official firmware from the teclast homepage, load it into RDT, uncheck all partitions (save for those that are compulsory and cannot be unchecked), select only boot and vbmeta partitions, and as images to be flashed you need to browse the ones found in the archive I posted, instead of those found in the original firmware package.
Begin flashing, your device will perform a hard reset, and then you should boot into rooted firmware.
Theoretically you should be able to flash both partitions (boot and vbmeta) via fastboot too, but when I tried, i got an error message saying boot.img was too large or something. Flashing via RDT went without problem. The only caveat is that flashing via RDT will always hard reset your device.
NightLord said:
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
Click to expand...
Click to collapse
How to install android 12 gsi on this device?
marinzrncic said:
How to install android 12 gsi on this device?
Click to expand...
Click to collapse
First you need to unlock the bootloader. You need to be patient when you are flashing the unlock, my device took some 10 mins to complete, but in the end it succeeded (on the 2nd try, mind you.)
Here is a guide for unlocking in windows, though it is in russian (Im attaching the required modified fastboot in case you cannot download it from 4pda).
When you're done unlocking the bootloader, you've already done the hard part.
Next, download your preferred GSI image from Google, from phhusson's, or whatever else you find (Pixel Experience for eg.). Mind you, that the image from Google contains the Android 12L version.
Next you will flash your active system partition with the GSI image. To do that, initate ADB connection to your tablet, then enter fastbootd, by issuing the command:
fastboot reboot fastboot
you can check your active system slot by:
fastboot getvar all (but it will be slot "a" unless you have received an OTA update previously)
you need to free up some space by deleting the logical partition product otherwise you wont be able to flash your gsi:
fastboot delete-logical-partition product_a
(in case your active slot is "a")
then you can move forward to actually flashing your GSI:
fastboot flash system_a whateverisyourimagefilename.img
Lastly, you will need to wipe userdata, which can be done on the tablet by switching to recovery from fastbootd, and then selecting wipe userdata, or maybe the fastboot -w command does the same.
Reboot, and enjoy your GSI.
I'm using the Google 12L GSI, and it is perfectly stable for daily usage. For bluetooth audio to work, you will have to disable bluetooth a2dp hardware offload in developer options.
NightLord said:
First you need to unlock the bootloader. You need to be patient when you are flashing the unlock, my device took some 10 mins to complete, but in the end it succeeded (on the 2nd try, mind you.)
Here is a guide for unlocking in windows, though it is in russian (Im attaching the required modified fastboot in case you cannot download it from 4pda).
When you're done unlocking the bootloader, you've already done the hard part.
Next, download your preferred GSI image from Google, from phhusson's, or whatever else you find (Pixel Experience for eg.). Mind you, that the image from Google contains the Android 12L version.
Next you will flash your active system partition with the GSI image. To do that, initate ADB connection to your tablet, then enter fastbootd, by issuing the command:
fastboot reboot fastboot
you can check your active system slot by:
fastboot getvar all (but it will be slot "a" unless you have received an OTA update previously)
you need to free up some space by deleting the logical partition product otherwise you wont be able to flash your gsi:
fastboot delete-logical-partition product_a
(in case your active slot is "a")
then you can move forward to actually flashing your GSI:
fastboot flash system_a whateverisyourimagefilename.img
Lastly, you will need to wipe userdata, which can be done on the tablet by switching to recovery from fastbootd, and then selecting wipe userdata, or maybe the fastboot -w command does the same.
Reboot, and enjoy your GSI.
I'm using the Google 12L GSI, and it is perfectly stable for daily usage. For bluetooth audio to work, you will have to disable bluetooth a2dp hardware offload in developer options.
Click to expand...
Click to collapse
thank you very much
NightLord said:
Hey,
You need to use the spreadtrum research download tool (RDT), not the one seen in tthe video in the first post.
See this guide on how to use the RDT.
The basic concept is that you need to download the official firmware from the teclast homepage, load it into RDT, uncheck all partitions (save for those that are compulsory and cannot be unchecked), select only boot and vbmeta partitions, and as images to be flashed you need to browse the ones found in the archive I posted, instead of those found in the original firmware package.
Begin flashing, your device will perform a hard reset, and then you should boot into rooted firmware.
Click to expand...
Click to collapse
Did we need unlock bootloader first or we can flash root without unlock bootloader?
Thx
ardianz said:
Did we need unlock bootloader first or we can flash root without unlock bootloader?
Thx
Click to expand...
Click to collapse
I have no idea because I havent tried yet. But I would guess it might be possible that you can flash the patched boot.img along with vbmeta.img with RDT, and it might work, if they do pass Android Verified Boot check.
NightLord said:
Gotcha:
Click to expand...
Click to collapse
will these files work on android 10 or android 11? I have a unisoc T618 and unisoc T310. I was hoping to flash both tablets to get root access.
and also do you have a twrp for T40_plus or any unisoc generic twrp?