Related
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
hw-schrauber said:
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
Click to expand...
Click to collapse
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Thank you Augustoandro, but unfortunately I can't use an older version. Since I want to run my device with magic, I only have to install the apk. If I take an older one here, I will only get to the patch buttons when the app is updated.
So this proposal does not help.
Perhaps it is also because the 7305F does not seem to have the partitions set up as usual. If I want to make a BackUp using the tool "MTKdroidTools 2.5.3" (screenshot), it means that the partition structure does not fit and no backup is possible. A root with the tool is also not possible.
Is there another idea?
For more information:
CPU MT8321 (32bit), Memory 1/16GB, kernel 4.9.117+ (#25.10.2019)
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
macgajos said:
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
Click to expand...
Click to collapse
You have to root by means of Magisk: Magisk itself doesn't root the Android.
jwoegerbauer said:
You have to root by means of Magisk: Magisk itself doesn't root the Android.
Click to expand...
Click to collapse
Thank you for your reply. Sorry for not being clear here: I get "Magisk is not installed" info in magisk manager after flashing the magisk patched boot img in fastboot mode.
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
hw-schrauber said:
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
Click to expand...
Click to collapse
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
macgajos said:
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
Click to expand...
Click to collapse
What do you mean with reset? When MAGISK is in recovery, the only way to start is in the recovery-mode. Then you have ever MAGISK working when it is installed!?!
Today I have seen, that there is a new version for the "F" model. TB_7305F_S100055_200703_ROW. I will test and report!
How do I pull the Recovery.img from this tablet in the first place? Please help. Thanks.
Hi. I am trying to manage root without twrp for a couple of days. I picked up the solution with recovery.
I've tried to flash root to recovery with magisk patched recovery.img via fastboot. But the .img size is to large (is texted in fastboot). By the way i was curious after magisk patching cause the patched .img file has the same size as the original .img file. I downloaded twrp port tool and ported recovery.img and got a recovery.img with a smaller size so i was able to flash it via fastboot. Fastboot flash recovery recovery.img
Fastboot reboot.
Device is booting to Lenovo splash screen with the warning that the device is unlocked and boot in 5s. Could wait forever. After 2min pushed vol+, Lenovo Banner starts to flip and it booted to system.
But no root.
Reboot.
Boot with key combo
Hold Vol+ and power, released as lenovo splash with the warning appears. Nothing happend.
Pushed vol+. Nothing happened. It stuck at splash.
After that i could not boot the device with power key anymore. It stays at splash every time i rebooted.I had to reboot to recovery and do rebooting to system from recovery.
From bootloader i was able to boot to system also.
I like to flash magisk patched boot.img via fastboot but magisk doesn't make the .img file smaller.
I tried with sp flash tool but after patching the img is not signed anymore soflash tool doesn't flash it.
So that is my state for now.
_
_
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
PART HO said:
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
Click to expand...
Click to collapse
.....Install twrp and root rights, it's not difficult. You can then do whatever is needed
I rooted my Lenovo M7 (TB-7305X) the folling way
On a PC Get and Install LMSA "Lenovo Rescue and Smart Assistan"
* Using LMSA do a recovery, this way you are sure you have al the drivers working and that you have a correct rom
On the Tabled enabled developer mode
* enable remote debugging
* enable oem unlocking
Unlock the bootloader using fastboot
(you will find adb and fastboot in the location where LMSA was installed)
P.S. this will erase of data on your tablet
* adb reboot-bootloader
* fastboot flashing unlock
* fastboot reboot
PS tablet well be in orange state (because the bootloader is unlocked)
* android boots
On the tablet create a rooted boot.img using magisk
* download and install the latest magisk.apk
* look for boot.img (boot.img_verified) the ROW downloaded by LMSA (some where in c:\programdata)
* uplad the boot.img to the tablet
* start magisk and patch the boot.img file
* download the patched boot.img
On the PC start MTK_Flash tool
P.S. this will erase of data on your tablet
* open the download tab
* the download agent should be set by default (MTK_AllInOne_DA.bin)
* select the scater file (from the LMSA rom directory)
* deselct all files except BOOTIMG
* change the location of the BOOTIMG and select the pached boot.img
Flash boot.img by clicking download
Rooting instructions for TB_7305X (Should be the same for TB_7305F using TB-7305X_S100043_200223_ROW)
Install Rescue and Smart Assistant from Lenovo
Start Rescue and download latest ROM
Replace the latest ROM files from C:\ProgramData\RSA\Download\RomFiles\TB_7305X_S1000xx_xxxxxx_ROW with the ones from TB-7305X_S100043_200224_ROW
Can be downloaded from:
https://mirrors.lolinet.com/firmware/lenovo/Tab_M7/TB-7305X/
Rescue the device as per the RSA instructions
Install latest Magisk
Upload recovery-verified.img from the TB-7305X_S100043_200224_ROW ROM to the Internal Shared Storage of the device in Download directory
Run Magisk Manager
Patch the recovery-verified.img with magisk
Copy the newly created magisk_patched-xxxxxxxx.img file in Downloads to C:\Program Files (x86)\Rescue and Smart Assistant and rename to magisk_patched.img
It will later be used to flash the device after unlocking
Enable developer mode on the device
From developer options enable:
OEM Unlocking (needs Internet connection)
USB Debugging
Start cmd and navigate to C:\Program Files (x86)\Rescue and Smart Assistant directory
adb reboot bootloader
Wait for reboot. You will see “=> FASTBOOT mode …” message when ready
fastboot.exe flashing unlock
Press volume up key to confirm
fastboot flash recovery magisk_patched.img
disconnect USB cable
press volume-up+volume-down+power buttons to switch off the tablet
press volume-up+volume-down+power buttons to switch on the tablet in Recovery mode
When Lenovo logo appears release the buttons.
Wait several minutes. Do not give up, do not restart. It takes time.
Reconfigure device
Enable USB Debugging
Disable System updates
Reinstall Magisk
Your device is rooted.
Whenever you want to use it in rooted mode you have to switch to recovery mode
The normal mode calls boot.img where magisk is not installed and the device will not be rooted.
You may proceed with removing Orange mode 5 sec wait message. Instructions available on the Internet.
If at some point the device writs back the original Recovery mode just reflash with magisk patch recovery-verified.
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Skylon5000 said:
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Click to expand...
Click to collapse
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Lenovo 7 tb-7305f
Root and TWRP
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
So i was searching for some guides but none were really complete so here is my take on a Guide regarding Root and flashing from WW to CN or CN to WW and Downgrading if your FW is to high.
Requirements:
A computer
Your ROG Phone 3 (Duh)
The Bootloader Unlock Tool (can be found here)
TWRP (can be found here)
ADB+Drivers (can be found here and here)
The newst Firmware from Asus (can be found here) To cross flash you need both CN and WW Version with the same Build Number. Newest one with matching Number should be the .2009.98 as the time of writing this. CN WW
Magisk Manager (can be found here)
IMPORTANT!
After you cross flash you will loose the ability to update via OTA. So you have to update your Phone yourself.
Also you WILL loose your Data by following this guide and unlocking your Bootloader!
Follow this Guide at your own Risk! I do NOT take any responsibilty for problems or bricks.
Also if you have a PIN, Fingerprint or anything installed on your Phone aside from the PIN for your Cards disable them.
Preparations:
First download or copy the Bootloader Unlock file to your phone and install it. After that run it. If it is successfull your Bootloader will be unlocked and your device will be wiped.
Now install adb and the drivers provided from the Links above.
After you installed adb download and copy the twrp image to the Adb folder and rename it to twrp.img
Then open a cmd and cd to the directory where adb is installed. Easiest folder for accessing + location would be C:\adb
Now enable the Developer Settings on your Rog Phone. For that open the Settings go to System / About the Phone / Softwareinformation / Then tap on Build-Number till it says you are a Developer.
Now go to Developer Options. Its also under System and then Developer Options. Enable USB-Debugging.
Connect your Rog Phone via usb to your pc and enable the ADB Debug Connection from the prompt on your phone.
Type in adb reboot bootloader and your phone will reboot to fastboot.
After that use
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
to install TWRP on your Phone. After that reboot your phone to recovery through the menu. With TWRP installed you can now fully Backup your system + install/downgrade new Versions of Android. This also works if you want to install WW on a CN Version of the Rog Phone.
Downgrade:
To Downgrade just download the Firmware Version you want to downgrade to from the Asus Homepage and copy it to your ROG Phone.
Then boot to TWRP. To be safe create a backup. After that you can install the ZIP file with TWRP. If the Downgrade is successfull you can remove the backup to save some space.
Reboot your phone and check the installed Version.
Switching Rom WW/CN or CN/WW:
To Switch your Rom you need the Firmware Version which matches for both Region. Currently this would be build .2009.98 There are newer ones available with 2009.99 for WW and 2009.100 for CN but the later one is not available for Download only through OTA and 99 is not available as download for CN devices.
If your Firmware is higher then the .98 or newest matching Version available Downgrade to that Version. Create a Backup before doing so.
If successfull you can then install the same Version for the other Region. For me this did work fine. If it does not work you can always restore your backup via TWRP.
There are also RAW Zip Files available for some Versions but those are hard to find and can brick your phone while trying to downgrade.
Rooting:
Download and install Magisk Manager from the link provided above.
After installing it open the App and download Magisk.
Boot to TWRP and install the Zip File for Magisk.
After that reboot to System. You can check if root is working by using root checker or any other software.
If you plan on using Magisk together with for example Pokemon Go you need to Hide Magisk in the Settings.
Like Bugs Bunny said. "This should be all folks."
If you need further help or something is missing feel free to post below.
Seriously? What a waste of bandwidth.
Invisan said:
So i was searching for some guides but none were really complete so here is my take on a Guide regarding Root and flashing from WW to CN or CN to WW and Downgrading if your FW is to high.
Requirements:
A computer
Your ROG Phone 3 (Duh)
The Bootloader Unlock Tool (can be found here)
TWRP (can be found here)
ADB+Drivers (can be found here and here)
The newst Firmware from Asus (can be found here) To cross flash you need both CN and WW Version with the same Build Number. Newest one with matching Number should be the .2009.98 as the time of writing this. CN WW
Magisk Manager (can be found here)
IMPORTANT!
After you cross flash you will loose the ability to update via OTA. So you have to update your Phone yourself.
Also you WILL loose your Data by following this guide and unlocking your Bootloader!
Follow this Guide at your own Risk! I do NOT take any responsibilty for problems or bricks.
Also if you have a PIN, Fingerprint or anything installed on your Phone aside from the PIN for your Cards disable them.
Preparations:
First download or copy the Bootloader Unlock file to your phone and install it. After that run it. If it is successfull your Bootloader will be unlocked and your device will be wiped.
Now install adb and the drivers provided from the Links above.
After you installed adb download and copy the twrp image to the Adb folder and rename it to twrp.img
Then open a cmd and cd to the directory where adb is installed. Easiest folder for accessing + location would be C:\adb
Now enable the Developer Settings on your Rog Phone. For that open the Settings go to System / About the Phone / Softwareinformation / Then tap on Build-Number till it says you are a Developer.
Now go to Developer Options. Its also under System and then Developer Options. Enable USB-Debugging.
Connect your Rog Phone via usb to your pc and enable the ADB Debug Connection from the prompt on your phone.
Type in adb reboot bootloader and your phone will reboot to fastboot.
After that use
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
to install TWRP on your Phone. After that reboot your phone to recovery through the menu. With TWRP installed you can now fully Backup your system + install/downgrade new Versions of Android. This also works if you want to install WW on a CN Version of the Rog Phone.
Downgrade:
To Downgrade just download the Firmware Version you want to downgrade to from the Asus Homepage and copy it to your ROG Phone.
Then boot to TWRP. To be safe create a backup. After that you can install the ZIP file with TWRP. If the Downgrade is successfull you can remove the backup to save some space.
Reboot your phone and check the installed Version.
Switching Rom WW/CN or CN/WW:
To Switch your Rom you need the Firmware Version which matches for both Region. Currently this would be build .2009.98 There are newer ones available with 2009.99 for WW and 2009.100 for CN but the later one is not available for Download only through OTA and 99 is not available as download for CN devices.
If your Firmware is higher then the .98 or newest matching Version available Downgrade to that Version. Create a Backup before doing so.
If successfull you can then install the same Version for the other Region. For me this did work fine. If it does not work you can always restore your backup via TWRP.
There are also RAW Zip Files available for some Versions but those are hard to find and can brick your phone while trying to downgrade.
Rooting:
Download and install Magisk Manager from the link provided above.
After installing it open the App and download Magisk.
Boot to TWRP and install the Zip File for Magisk.
After that reboot to System. You can check if root is working by using root checker or any other software.
If you plan on using Magisk together with for example Pokemon Go you need to Hide Magisk in the Settings.
Like Bugs Bunny said. "This should be all folks."
If you need further help or something is missing feel free to post below.
Click to expand...
Click to collapse
I wish someone would make a video tutorial on this. For dummies who are afraid to brick their phone like me.
Invisan said:
So i was searching for some guides but none were really complete so here is my take on a Guide regarding Root and flashing from WW to CN or CN to WW and Downgrading if your FW is to high.
Requirements:
A computer
Your ROG Phone 3 (Duh)
The Bootloader Unlock Tool (can be found here)
TWRP (can be found here)
ADB+Drivers (can be found here and here)
The newst Firmware from Asus (can be found here) To cross flash you need both CN and WW Version with the same Build Number. Newest one with matching Number should be the .2009.98 as the time of writing this. CN WW
Magisk Manager (can be found here)
IMPORTANT!
After you cross flash you will loose the ability to update via OTA. So you have to update your Phone yourself.
Also you WILL loose your Data by following this guide and unlocking your Bootloader!
Follow this Guide at your own Risk! I do NOT take any responsibilty for problems or bricks.
Also if you have a PIN, Fingerprint or anything installed on your Phone aside from the PIN for your Cards disable them.
Preparations:
First download or copy the Bootloader Unlock file to your phone and install it. After that run it. If it is successfull your Bootloader will be unlocked and your device will be wiped.
Now install adb and the drivers provided from the Links above.
After you installed adb download and copy the twrp image to the Adb folder and rename it to twrp.img
Then open a cmd and cd to the directory where adb is installed. Easiest folder for accessing + location would be C:\adb
Now enable the Developer Settings on your Rog Phone. For that open the Settings go to System / About the Phone / Softwareinformation / Then tap on Build-Number till it says you are a Developer.
Now go to Developer Options. Its also under System and then Developer Options. Enable USB-Debugging.
Connect your Rog Phone via usb to your pc and enable the ADB Debug Connection from the prompt on your phone.
Type in adb reboot bootloader and your phone will reboot to fastboot.
After that use
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
to install TWRP on your Phone. After that reboot your phone to recovery through the menu. With TWRP installed you can now fully Backup your system + install/downgrade new Versions of Android. This also works if you want to install WW on a CN Version of the Rog Phone.
Downgrade:
To Downgrade just download the Firmware Version you want to downgrade to from the Asus Homepage and copy it to your ROG Phone.
Then boot to TWRP. To be safe create a backup. After that you can install the ZIP file with TWRP. If the Downgrade is successfull you can remove the backup to save some space.
Reboot your phone and check the installed Version.
Switching Rom WW/CN or CN/WW:
To Switch your Rom you need the Firmware Version which matches for both Region. Currently this would be build .2009.98 There are newer ones available with 2009.99 for WW and 2009.100 for CN but the later one is not available for Download only through OTA and 99 is not available as download for CN devices.
If your Firmware is higher then the .98 or newest matching Version available Downgrade to that Version. Create a Backup before doing so.
If successfull you can then install the same Version for the other Region. For me this did work fine. If it does not work you can always restore your backup via TWRP.
There are also RAW Zip Files available for some Versions but those are hard to find and can brick your phone while trying to downgrade.
Rooting:
Download and install Magisk Manager from the link provided above.
After installing it open the App and download Magisk.
Boot to TWRP and install the Zip File for Magisk.
After that reboot to System. You can check if root is working by using root checker or any other software.
If you plan on using Magisk together with for example Pokemon Go you need to Hide Magisk in the Settings.
Like Bugs Bunny said. "This should be all folks."
If you need further help or something is missing feel free to post below.
Click to expand...
Click to collapse
Sir? sorry noob here. how do you install the adb drivers?
Is there a way to pass CTS Profile? I tried many steps but none worked.
Magisk.zip v20.4 is working , but latest 21.* causing boot loop.
I have a question. I rooted my ROG 3 and installed Adaway program , but it says that it unable to copy host file to /system partition. System partition is read only. Is there any way to make it rw ?
kepetrov said:
Magisk.zip v20.4 is working , but latest 21.* causing boot loop.
I have a question. I rooted my ROG 3 and installed Adaway program , but it says that it unable to copy host file to /system partition. System partition is read only. Is there any way to make it rw ?
Click to expand...
Click to collapse
Defeats the whole purpose of systemless root. Moreover, the /system partition now resides inside the new dynamic super partition which is always mounted ready-only.
It would be better to go for a systemless solution. I believe there's a module, but don't remember. So try searching for that.
EDIT: As for the bootloop, try Magisk v21.4, it should fix the bootloop.
Ttt
mcbodinho said:
Ttt
Click to expand...
Click to collapse
Xi me root
Gabda
Ok
FF
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?
Please read this guide fully before attempting to follow it. It requires some knowledge of how to use a Terminal and basic ADB/Fastboot operation. I don't think this guide is thorough enough for a person who's modifying their phone for the very first time. Feel free to ask for help though!
I am not reliable for any adverse effects this guide might have on your phone. If something breaks, that's your responsibility. However: if your phone doesn't boot anymore, but you can still get into fastboot, you should be able to flash the Stock Firmware OFP using the Realme Flash Tool. To get into fastboot, power off your phone, wait a few seconds, and hold power and volume down until you see the fastboot logo.
This guide was cobbled together using various other tutorials and my own attempts. I've used it on my RMX2075. It should also work for the RMX2076. The files Realme provides for the RMX2075 are named "RMX2076", so I assume they're the same device. I have no idea how the RMX2071 fits into this. Curiously, the TWRP version used here is intended for the RMX2071, although it works flawlessly on my RMX2075. However: if you're using it on an RMX2075/2076 TWRP thinks you're using an RMX2071, so it won't flash packages intended for the RMX2075/2076. Hence the following warning:
!!! YOU WON'T BE ABLE TO INSTALL OTA UPDATES AFTER INSTALLING TWRP !!!
If you attempt to install an OTA Update downloaded from within the Settings.app, the phone will reboot, TWRP will attempt to install the OTA Update and fail with an error. This does not break anything, it just doesn't update.
DOWNLOADS:
- Realme Flash Tool
- Stock Firmware OFP
- OTA Update OZIP
- TWRP 3.4.1b for RMX2071 by wzsx150 and LR. Team
Spoiler: further details
The licensing of this TWRP is pretty unclear, so I can't provide a download link. If you search for it Online, make sure to find a version that includes both "recovery.img" and "misc.bin"
- Realme DeepTesting App
- Magisk Manager by topjohnwu
- oppo ozip decrypt
PREPARATION:
- install ADB & Fastboot on your computer
- enable "USB debugging" on your phone
- install the oppo ozip decryption tool by following the instruction on the GitHub page
UNLOCKING
- follow the unlock instructions provided by the official Realme Tutorial
RESTORING AND UPDATING - if you're on firmware A42, skip this step
- follow the restore instructions provided by the official Realme Tutorial
- go to the Realme Software Update page, click on "How to update?" and follow the instructions
FLASH TWRP
- open a Terminal window and cd into the folder that holds recovery.img and misc.bin
cd /path/to/folder
- enter the following commands and hit enter after each
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash misc misc.bin
fastboot reboot recovery
- your phone should now reboot into TWRP
- enter your phones unlock code if you have one
- go to "Advanced" -> "Disable Replace TWRP"
- reboot phone
ROOTING
DO NOT use "Install Root" in TWRP, it'll "destroy" the bootloader and you'll have to flash the stock firmware
Follow this instead:
- decrypt the OTA .ozip using the oppo ozip decrypt tool (instructions on its GitHub page)
- unzip the resulting decrypted file
- copy "boot.img" onto your phone
- copy "/firmware-update/vbmeta.img" into a folder of your choice
- install Magisk Manager on your phone
- open Magisk Manager, tap on "Install" followed by "Select and Patch a File"
- select the "boot.img" you've previously copied onto your phone and let Magisk do its thing
- the patched "boot.img" is called "magisk_patched_XXXX.img" or something similar. Make note of the resulting file name which is specific to you.
- copy the patched "magisk_patched_XXXX.img" into the same folder that holds your "vbmeta.img"
- open a terminal and cd into the folder that holds the patched "boot.img" and "vbmeta.img"
- enter the following commands and hit enter after each
adb reboot bootloader
in the following step, replace "magisk_patched_XXXX.img" with whatever your patched "boot.img" is called
fastboot flash boot magisk_patched_XXXX.img/ICODE]
[ICODE]fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
- your phone should now be rooted
I have also uploaded the stock boot.img along with the rooted version as well as vbmeta.img here. They were created using the method described above with OTA update A42. I would recommend creating your own though, since this has a higher chance of success.
Another method to get the stock boot.img and vbmeta.img is creating a TWRP backup, renaming "boot.emmc.win" to "boot.img", and "vbmeta.emmc.win" to "vbmeta.img". I have NOT TESTED this method.
I don't know if this will work for Android 11 / ColorOS 2.0. My theory is that if you can get the RMX2076PU_11.C.16.ozip somewhere, you could just follow this guide using it instead of the A42 one. Again, I have NOT TESTED this method.
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
corneo said:
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
Click to expand...
Click to collapse
Android 11twrp brush Android 10, and then brush Android 10twrp, you can boot
can u using volte with stock ofp eu version?
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?