[ROOT] Teclast Master T8 - Android Q&A, Help & Troubleshooting

Hi everyone,
This is what I have done to root my Teclast T8 with Magisk (based on this chineese forum: http://tieba.baidu.com/p/5449087481)
1-First download the official firmware from Needrom.com (You need to register): https://www.needrom.com/download/teclast-t8-e8c1/
2-Go to the Firmware folder and copy the “boot.img” file to the root directory of your tablet
3-Download and install MagiskManager on the tablet, click on Install, then choose to patch the boot image file. Choose the boot.img you’ve just uploaded to your tablet and it will start to automatically patch it.
Then go into the File Manager and go to the MagiskManager folder and find the “patch_boot.img“ and copy it to the root directory (without copying it to the root directory, you can not find the file from your pc…), then sends the file from the tablet to your computer.
4-For me the method with SP Flash Tool don’t work, because it says the scatter file is wrong (don’t know why…)
So i have to do it with adb and unlock the bootloader first:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
-reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Your bootloader is now unlock.
-then copy the “patched_boot.img” in the adb folder and tap in command prompt “fastboot flash boot patched_boot.img”, then “fastboot reboot”.
Your tablet should be rooted.
I think you can relock bootloader after... don't try yet.
PS: This is my first thread, so be indulgent ?
Don’t ask me technical questions because I am not a developer , just a simple user …
Hope this will help.
If someone find a way to find and flash a TWRP or how to install Xposed, please tell me, thx.

Rooted using same method but SP Flash Tools worked in my tablet.
Waiting for a TWRP ....

Yes, can confirm that method works for root.
Also tried the T10 TWRP and it's not working on the T8, just a black screen.
Don't need TWRP yet, some bugs in the ROM are more annoying than that

hi all
somebody tried the new rom v1.10 on needrom ??

marinero57 said:
hi all
somebody tried the new rom v1.10 on needrom ??
Click to expand...
Click to collapse
Hi guys i jus download v1.10 rom but have no idea how to flash, everything in chinesse... even recovery, how do you flash? the tablet have a TelcastOTA apk installed, this have a local update option allow to load firmware from sd, anyone used this app? what files should i put in SD?
thanks in advance

HI quick question what rom have u installed in ur T8, mine came with 1.01, i see in needrom have 3 versions: 1.06. 1.08, 1.10, have u updated to any of these?
Thanks
Polo19 said:
Hi everyone,
This is what I have done to root my Teclast T8 with Magisk (based on this chineese forum: http://tieba.baidu.com/p/5449087481)
1-First download the official firmware from Needrom.com (You need to register): https://www.needrom.com/download/teclast-t8-e8c1/
2-Go to the Firmware folder and copy the “boot.img” file to the root directory of your tablet
3-Download and install MagiskManager on the tablet, click on Install, then choose to patch the boot image file. Choose the boot.img you’ve just uploaded to your tablet and it will start to automatically patch it.
Then go into the File Manager and go to the MagiskManager folder and find the “patch_boot.img“ and copy it to the root directory (without copying it to the root directory, you can not find the file from your pc…), then sends the file from the tablet to your computer.
4-For me the method with SP Flash Tool don’t work, because it says the scatter file is wrong (don’t know why…)
So i have to do it with adb and unlock the bootloader first:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
-reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Your bootloader is now unlock.
-then copy the “patched_boot.img” in the adb folder and tap in command prompt “fastboot flash boot patched_boot.img”, then “fastboot reboot”.
Your tablet should be rooted.
I think you can relock bootloader after... don't try yet.
PS: This is my first thread, so be indulgent
Don’t ask me technical questions because I am not a developer , just a simple user …
Hope this will help.
If someone find a way to find and flash a TWRP or how to install Xposed, please tell me, thx.
Click to expand...
Click to collapse

Flashing ROM with SP flashtool - Teclast Master T8 (E8C1)
Fossxp13 said:
Hi guys i jus download v1.10 rom but have no idea how to flash, everything in chinesse... even recovery, how do you flash? the tablet have a TelcastOTA apk installed, this have a local update option allow to load firmware from sd, anyone used this app? what files should i put in SD?
thanks in advance
Click to expand...
Click to collapse
Hi! I haven't used in built update app so I'll try to explain how to update using flashtool. Follow the steps with your device disconnected from the pc and take into account your files will be erased.
First of all, I recommend you to install ADB and fastboot drivers: 15 seconds ADB Installer
As OP said download the rom from NeedRom and unzip it: You will have three folders:
升级工具, which contains flashtool
固件程序, with the rom
驱动程序, with the drivers
Rename all of them as flashtool, rom and drivers, for example. If you don't, you may have troubles launching flashtool or loading the scatter file.
Launch flashtool as administrator (升级程序, you could rename it too), if you get the message "The scatter file cannot found, please make sure the file exist before download" ignore it. In flashtool make sure MTK_AllInOne_DA.bin is selected as Download-Agent and select the scatter file inside rom folder as Scatter-loading file. Choose firmware upgrade from the list and click the Download button (the one with the green arrow).
Finally, switch off your device and connect it to your pc. Flashtool should do the rest, wait untill "Download Ok" message is displayed. Close flashtool, disconnect your device and switch it on.
IF your computer doesn't load needed drivers automatically, flashtool won't start the process as expected. You will need to open device manager on windows, right click on your device - update driver - choose manually - browse "inf" folder inside drivers folder (choose x86 or x64 according to your OS).
Hope it works! Good luck.

Prevent Brick and Xposed for Teclast Master T8 (E8C1)
Polo19 said:
OP
Click to expand...
Click to collapse
Hi Polo19!
Thanks for your post, I rooted my tablet following it! But since I encountered some issues in the process I wanted to share my experience.
IMPORTANT: For a few hours I thought I hard bricked my device, so I hope I could help somebody.
When patching boot.img with MagiskManager IF the app automatically tics "Keep force encryption" choose "Keep dm-verify" aswell!
I don't know why but this was the only way to make it work on my device, I kept getting a encryption error after flashing the patched boot.img, despite the fact that I have never encrypted my device.
After getting that error I tried to flash the clean rom again, but flashtool gave an error and the tablet completely died! Well, it seemed so.
It's pretty stupid but the only way to make it work again was pushing the reset button on the top right corner of the tablet for a few seconds and flashing the rom again.
About Magisk: use the OFFICIAL MAGISK XDA THREAD to download it, as https://magiskmanager.com/ is NOT the official website.
In step 3, I couldn't find the patched_boot.img file even after moving it to the root directory. So I had to (let the patched_boot.img file in the default directory):
Install ADB drivers in the computer: https://forum.xda-developers.com/showthread.php?t=2588979
Enable USB debugging in developer options in the tablet, connect it to the computer and accept the connection.
Open command prompt / powershell: "shift + right click" wherever you want to copy the patched_boot.img and open cmd or power shell.
Run the command:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
In step 4: you won't encounter that problem if you rename downloaded folders and get rid of chinese characters. Simply open flashtool, choose the scatter file, untick all options except boot and change the default boot.img with the patched one (I renamed it to boot.img, I don't know if it's necessary)
Xposed: you can install xposed using MagiskManager.
Install Xposed Installer for Magisk, go to download tab in MagiskManager and install Xposed SDK24 (for android 7.0) and reboot
Sources:
15 SECONDS ADB INSTALLER
MAGISK
SYSTEMLESS XPOSED
CHINESE FORUM

Just need TWRP and I'm happy.
There's a chinese TWRP but it's not working decently.

Rotiaiso said:
Hi Polo19!
Thanks for your post, I rooted my tablet following it! But since I encountered some issues in the process I wanted to share my experience.
IMPORTANT: For a few hours I thought I hard bricked my device, so I hope I could help somebody.
When patching boot.img with MagiskManager IF the app automatically tics "Keep force encryption" choose "Keep dm-verify" aswell!
I don't know why but this was the only way to make it work on my device, I kept getting a encryption error after flashing the patched boot.img, despite the fact that I have never encrypted my device.
After getting that error I tried to flash the clean rom again, but flashtool gave an error and the tablet completely died! Well, it seemed so.
It's pretty stupid but the only way to make it work again was pushing the reset button on the top right corner of the tablet for a few seconds and flashing the rom again.
About Magisk: use the OFFICIAL MAGISK XDA THREAD to download it, as https://magiskmanager.com/ is NOT the official website.
In step 3, I couldn't find the patched_boot.img file even after moving it to the root directory. So I had to (let the patched_boot.img file in the default directory):
Install ADB drivers in the computer: https://forum.xda-developers.com/showthread.php?t=2588979
Enable USB debugging in developer options in the tablet, connect it to the computer and accept the connection.
Open command prompt / powershell: "shift + right click" wherever you want to copy the patched_boot.img and open cmd or power shell.
Run the command:
In step 4: you won't encounter that problem if you rename downloaded folders and get rid of chinese characters. Simply open flashtool, choose the scatter file, untick all options except boot and change the default boot.img with the patched one (I renamed it to boot.img, I don't know if it's necessary)
Xposed: you can install xposed using MagiskManager.
Install Xposed Installer for Magisk, go to download tab in MagiskManager and install Xposed SDK24 (for android 7.0) and reboot
Sources:
15 SECONDS ADB INSTALLER
MAGISK
SYSTEMLESS XPOSED
CHINESE FORUM
Click to expand...
Click to collapse
Yes, i also install Xposed using MagiskManager and it works. Now i am able to use all fonctions of Greenify, Amplify, Powernap and get a pretty decent standby batterylife.

marinero57 said:
hi all
somebody tried the new rom v1.10 on needrom ??
Click to expand...
Click to collapse
Hi, I tried to follow the procedure but in ROM 1.10 doesn't work
---------- Post added at 01:37 PM ---------- Previous post was at 12:44 PM ----------
With the news roms doesn't work...

What is the rom that was working this WA??
Thanks!

I just did this to a tablet that had OTA'd the 1.10 - using the 1.10's downloaded boot and latest Magisk Manager 5.5.4 / Magisk 15.3 beta
OEM Unlock, patching boot image and patched boot image flashing worked
BUT - the included Magisk Manager does not launch after installing upon reboot...
HOWEVER - V5.5.3 of the manager did work.
$ adb -s 0123456789ABCDEF install MagiskManager-v5.5.3.apk
Success
$ adb -s 0123456789ABCDEF shell
t8_e8c1:/ $ su
t8_e8c1:/ #
Notes
1. Tablet is wiped
2. Boot delay of 5 seconds is added with "can't be trusted" warning in white text
3. Fails safetynet
Letting MagiskManager update itself to 554 also worked - so I think my method of just installing the apk from the Magisk zip's common folder was wrong.

Kerrnel said:
I just did this to a tablet that had OTA'd the 1.10 - using the 1.10's downloaded boot and latest Magisk Manager 5.5.4 / Magisk 15.3 beta
OEM Unlock, patching boot image and patched boot image flashing worked
BUT - the included Magisk Manager does not launch after installing upon reboot...
HOWEVER - V5.5.3 of the manager did work.
$ adb -s 0123456789ABCDEF install *************-v5.5.3.apk
Success
$ adb -s 0123456789ABCDEF shell
t8_e8c1:/ $ su
t8_e8c1:/ #
Notes
1. Tablet is wiped
2. Boot delay of 5 seconds is added with "can't be trusted" warning in white text
3. Fails safetynet
Letting ************* update itself to 554 also worked - so I think my method of just installing the apk from the Magisk zip's common folder was wrong.
Click to expand...
Click to collapse
Hi,
My T8 arrived yesterday and I've used OTA to update to 1.10.
Is the sptools method working with 1.10 or do I need to use this process?
Also where to the numbers 0123456789ABCDEF come from in the instructions I've quoted?
Thank is advance

i have the ota 1.10 update and the rooting was successful. magisk and xposed working flawlessly.

another point:
i have closed the bootloader after flashing the patched boot.img with "fastboot oem lock".
the device boot up is faster and the warning "...5 seconds" is gone.
now, i wait for twrp.

You dont need to unlock bootloader.
Just flash patched_boot with flash tool.

Zaphodb69 said:
Hi,
My T8 arrived yesterday and I've used OTA to update to 1.10.
Is the sptools method working with 1.10 or do I need to use this process?
Also where to the numbers 0123456789ABCDEF come from in the instructions I've quoted?
Thank is advance
Click to expand...
Click to collapse
I had multiple devices attached to the PC.
No -s ABC... needed if you only have the one.
Sent from my T8(E8C1) using Tapatalk

The suggested worked for me. I will also mention that you must be connected to the internet to patch the boot.img file with magisk manager (otherwise, the option will not be presented in the magisk manager GUI).

Were there made any changes for the fingerprint? Soimebody mentioned, it isn´t that good. Maybe the last updates change something...

Related

[Guide] Root without Recovery for non-Verizon Asus ZenFone AR with Magisk Manager

I haven't had any luck building or finding TWRP yet for the ZenFone AR, but I found a way to get root access without needing the recovery.
To start, you will need:
The unlock APK from ASUS:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS571KL/SIGNED_UnlockTool-9.0.0.35.apk
The matching system image for your phone: BE SURE TO DOWNLOAD THE CORRECT VERSION BETWEEN JP (Japan) AND WW (WorldWide) or your wifi will break.
https://www.asus.com/us/Phone/ZenFone-AR-ZS571KL/HelpDesk_Download/
As of the time of writing, I downloaded:
ZS571KL Software Image: V14.1600.1711.36 for WW/TIM SKU only
The installation steps are pretty standard, but I'll summarize them here:
1) Get working copies of adb and fastboot
2) Push the Unlock APK to your phone and install and unlock on the device. THIS WILL ERASE ALL OF YOUR DATA.
3) Install Magisk Manager as described here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
A) Download this APK, copy to your phone, and install.
B) From your system image, uncompress and find the boot.img and copy to your SD Card.
C) Open MagiskManager and Press Install > Install > Patch Boot Image File, and select your stock boot image file (boot.img)
D) Magisk Manager will now download a file and patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img
E) Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB: adb pull /sdcard/MagiskManager/patched_boot.img
F) adb reboot bootloader
G) sudo fastboot flash boot patched_boot.img
H) Press the Power button to "Start"
You should now have MagiskManager installed, this is a program similar to SuperSU and it can enable and manage root for you.
Try look the TWRP of the Asus Zenfone 3 Deluxe if you can use it
Sent from my Asus ZenFone 3 Deluxe using XDA Labs
This is great!! Why isn't Verizon supported in this method? Is it because of the unlocking process?
Worked well for me with the installation via the magick.apk (non-recovery/non-rooted method) on the WW model.
Without this thread, i would not have known the unlock apk had been released nor that Majick worked with the AR.
thank you chadrockey
comomomo said:
This is great!! Why isn't Verizon supported in this method? Is it because of the unlocking process?
Click to expand...
Click to collapse
I would consider the Verizon version an almost different phone. I've been fortunate enough to have them side by side and they are very different. The builds and model numbers are different, as well as things you wouldn't expect like screen coloration or the scaling and menu options for the screens. There's also changes like the USB working much differently on the Verizon (much more locked down).
I haven't tried using the unlock tool on the Verizon model, but I don't expect it to work. As long as that's the case, I wouldn't expect root to come to Verizon.
Suspicious link
Why is the link to the apk redirected and hosted on an untrustworthy site? I would advise against using this app from this link.
Everything about the link screams malware.
huginnaesir said:
Why is the link to the apk redirected and hosted on an untrustworthy site? I would advise against using this app from this link.
Everything about the link screams malware.
Click to expand...
Click to collapse
It's a direct link from the ASUS download page. You can go to www.asus.com/us/Phone/ZenFone-AR-ZS571KL/HelpDesk_Download and click the same link there
For anyone who has got root install this and he will build your twrp.
https://www.mediafire.com/file/e5d1ojafoefcgbw/app-release-1.apk
Sent from my LEX727 using xda premium
Hi. Did just like this article explained, and now my wifi is gone. Any fix for this??
Has anyone tried to install the WW software on the Verizon Model?
chadrockey said:
I haven't had any luck building or finding TWRP yet for the ZenFone AR, but I found a way to get root access without needing the recovery.
To start, you will need:
The unlock APK from ASUS:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS571KL/SIGNED_UnlockTool-9.0.0.35.apk
The matching system image for your phone: BE SURE TO DOWNLOAD THE CORRECT VERSION BETWEEN JP (Japan) AND WW (WorldWide) or your wifi will break.
https://www.asus.com/us/Phone/ZenFone-AR-ZS571KL/HelpDesk_Download/
As of the time of writing, I downloaded:
ZS571KL Software Image: V14.1600.1711.36 for WW/TIM SKU only
The installation steps are pretty standard, but I'll summarize them here:
1) Get working copies of adb and fastboot
2) Push the Unlock APK to your phone and install and unlock on the device. THIS WILL ERASE ALL OF YOUR DATA.
3) Install Magisk Manager as described here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
A) Download this APK, copy to your phone, and install.
B) From your system image, uncompress and find the boot.img and copy to your SD Card.
C) Open MagiskManager and Press Install > Install > Patch Boot Image File, and select your stock boot image file (boot.img)
D) Magisk Manager will now download a file and patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img
E) Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB: adb pull /sdcard/MagiskManager/patched_boot.img
F) adb reboot bootloader
G) sudo fastboot flash boot patched_boot.img
H) Press the Power button to "Start"
You should now have MagiskManager installed, this is a program similar to SuperSU and it can enable and manage root for you.
Click to expand...
Click to collapse
Thanks as first for that thread. I did it, it has been patched and booted successfully but my device is it no rooted yet...
hello,please help for Verizon device
i want to root it as any device,also i want to install custom Rom as normal as any device !!
any help and co operate ??

[GUIDE] [EMUI 9] Magisk Root Honor view 10 BKL-09 for Android PIE

Requirements / Downloads
Honor 10 view BKL-09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk BKL
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager canary build to your phone and install.
2. Change in Magisk settings the update channel to "custom" inserting this URL. https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
3. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
4.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
ORIGINAL RECOVERY_RAMDISK BKL-09 PIE version 9.0.0.162 C432
5. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Thanks
Thanks a lot for this great guide!
Hello, will this also be on my bkl-l09c432? I have rom
blazios said:
Hello, will this also be on my bkl-l09c432? I have rom
Click to expand...
Click to collapse
If your device is on pie ?, yes
What should I use twrp?
blazios said:
What should I use twrp?
Click to expand...
Click to collapse
OP never mentioned anything about twrp. That is not needed
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
BlueMan_86 said:
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
Click to expand...
Click to collapse
Flash in bootloader mode. Not in twrp.
Android pie not work with twrp for now.
I am on ROOTED EMUI 8.0 (BKL-L09 8.0.0.130). How do I update to pie and then root? First unroot than update than root? or just update and root with the instructions in post#1?
Sadly it does not work for me. Tried it with your patches bootimage and with my own. Flashing the ramdisk works fine but after restart I don't have root.
I dont need Magisk installed if I use the pre patches bootimage right? Nevertheless I tried with Magisk installed and without. In the Huawei Mate Forum I read that one might need to shutdown the phone after flashing and then to start it with Volume Up and Power Button pressed. But this also does not work. Or any Idea how exactly to start with this Key combination?
Any other suggestions?
Today I updated from OREO with root to PIE same version as you have in pictures 9.0.0.162(C432E4R1P9). Tried both steps (with your patched file and me patching file) to root my phone but even I always got OK in fastboot mode I still have no root
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
I get the same error
any advise ?
Worked like a breeze for me. Shoutout to @ante0 and @shashank1320 who kept their calm in guiding me through and suggesting me this method.
@ante0 made things easier for me and it worked excellently for me. The steps are-
Download and install Magisk canary builds from the mentioned link. Change in Magisk settings the update channel to "custom" inserting*this*URL.*https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
Check "force encryption" and "AVB 2.0" boxes.
Transfer stock recovery ramdisk to phone, open Magisk Mnager and hit install - > patch boot image, select recovery_ramdisk.img. Take patched_boot.img from /sdcard/Download/ and transfer to computer, reboot to fastboot and flash patched_boot.img to recovery_ramdisk. Unplug USB, holv vol up + power to reboot to recovery, which will now boot phone with Magisk. If you reboot and don't hold vol up it will boot to system without root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Huge thanks @fabio84
Finally have root privileges on Pie.
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
davidsiv said:
I get the same error
any advise ?
Click to expand...
Click to collapse
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Not flash ramdisk. Need flash recovery_ramdisk!
worked, thanks
fabio84 said:
Not flash ramdisk. Need flash recovery_ramdisk!
Click to expand...
Click to collapse
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
ankan1993 said:
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
Click to expand...
Click to collapse
Update: @ante0 helped me yet again to figure it out. Apparently was because of pie's aggressive background restrictions. Root is now working full fledgedly. Thanks everyone. Big cheers to @ante0
Hello,
It finally worked for me. Thank you so much!
ante0 said:
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Click to expand...
Click to collapse

[ GUIDE ] [ ANDROID 10 ROOT ] [ HOW TO ] Patching Boot.img with Magisk

Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.

Oppo A5 2020 Root

Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
deadmeiker said:
Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
Click to expand...
Click to collapse
Me too
me three
deadmeiker said:
Hello
I bought a new Oppo A5 2020 and want to recovery my Titnaium Backups.
I search now 8-10 Hours to find a solution to root my phone, but no tutorial works.
I want to root my phone with Magisk and the right boot.img but i found only this file:
CPH1931_11_A.08_190905_cb4610de.ofp
I can not extract the ofp without some hardware parts.
Has anyone a idea how to root the Oppo A 2020 CPH1931
(CPH1931EX_11_A.08)
(CPH1931EX_11_A.13) <<- now aviable
Thank u so much
Click to expand...
Click to collapse
Me four. I want to root my A5 2020
Can you boot into bootloader? Cause i can't stay in bootloader mode.
Me 5..
Setting - about phone - tap "version" 7 times
Additional option - developer option - oem unlock bootloader
Tried download ota
Extracted from phone manager.. and got boot.img
But magisk say its corrupted.. maybe it cant read it.. some says to use its recovery.img but i cant find it.. im a noob in rooting so i cant opt to experiment
Tried these things (3rd might be a possiible solution)
1.)
I tried using the OTA update which is a .ozip file, and needs a certain key to be usable (Needs to be decrypted to zip), key differs depending on the device
as for reference:
filedesc.com/en/file/ozip
tried tools such as
github.com/bkerler/oppo_ozip_decrypt
(But with no luck, A5 2020 isn't supported)
2.)
I found something on the web which is the CPH1931_11_A.08_190905_cb4610de.ofp
which i cannot decrypt to get the boot.img file
3.)
If your willing to take the risk, i found this
forum.gsmdevelopers.com/oppo-android-unified/84350-oppo-a5-2020-cph1931-dead-boot-alive-akshay-bhandare.html
which leads to the boot.img here (Just extract then you'll find boot.bin, change the file extension to boot.img (Just replace/rename .bin to .img))
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
(If link doesn't work anymore, ill upload the one I've downloaded already)
I tried patching this using Magisk and it works, but i haven't tried flashing it to A5 2020
Thank u so much[/QUOTE]
---------- Post added at 04:43 PM ---------- Previous post was at 04:17 PM ----------
KrisAmaba said:
1.)
I tried using the OTA update which is a .ozip file, and needs a certain key to be usable (Needs to be decrypted to zip), key differs depending on the device
as for reference:
filedesc.com/en/file/ozip
tried tools such as
github.com/bkerler/oppo_ozip_decrypt
(But with no luck, A5 2020 isn't supported)
2.)
I found something on the web which is the CPH1931_11_A.08_190905_cb4610de.ofp
which i cannot decrypt to get the boot.img file
3.)
If your willing to take the risk, i found this
forum.gsmdevelopers.com/oppo-android-unified/84350-oppo-a5-2020-cph1931-dead-boot-alive-akshay-bhandare.html
which leads to the boot.img here (Just extract then you'll find boot.bin, change the file extension to boot.img (Just replace/rename .bin to .img))
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
(If link doesn't work anymore, ill upload the one I've downloaded already)
I tried patching this using Magisk and it works, but i haven't tried flashing it to A5 2020
Click to expand...
Click to collapse
If your going to try the 3rd possible solution in rooting Oppo A5 2020
DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards or thermonuclear war.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
Here's what you need
Download ADB and Fastboot files and extract them in the C:/drive. (Windows/MAC)
getdroidtips.com/how-to-install-adb-and-fastboot-on-windows
Download and Install Oppo USB Drivers.
getdroidtips.com/download-oppo-usb-drivers/
Oppo A5 2020 (Boot.img)
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
Here are the steps:
(Steps to do on your Phone)
1. Download the boot.img (Originally boot.bin in the link given)
2. Download Latest Magisk Manager
github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
3. Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
4. Tap on “Patch Boot Image File”
5. Navigate to internal storage and select your phone’s boot image that you've downloaded earlier.
6. Wait for a couple of seconds. Magisk will start patching the boot image.
7. Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the ADB fastboot extracted ROM folder on your PC.
(Steps to do on your PC)
1. We assume that you have already downloaded the ADB & Fastboot tool from the link given above.
2. Now, extract the ADB fastboot tool, then move the patched boot image to the same folder.
3. Hold the Shift key and right-click on the mouse to open the command window/PowerShell.
4. Next, enter the following command:
Flash the “patched_boot.img” to install Magisk and root your Android device:
fastboot flash boot patched_boot.img
The flashing process will begin. Once done, run
fastboot reboot
5. Done, Open Magisk to see if it's successful
---------- Post added at 04:52 PM ---------- Previous post was at 04:43 PM ----------
KrisAmaba said:
If your going to try the 3rd possible solution in rooting Oppo A5 2020
DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards or thermonuclear war.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
Here's what you need
Download ADB and Fastboot files and extract them in the C:/drive. (Windows/MAC)
getdroidtips.com/how-to-install-adb-and-fastboot-on-windows
Download and Install Oppo USB Drivers.
getdroidtips.com/download-oppo-usb-drivers/
Oppo A5 2020 (Boot.img)
mediafire.com/file/8kb8ilgz0mxaga3/OPPO_A5_2020%2528CPH1931_%2529DEAD_BOOT_ALIVE_BY_AKSHAY_BHANDARE.rar/file
Here are the steps:
(Steps to do on your Phone)
1. Download the boot.img (Originally boot.bin in the link given)
2. Download Latest Magisk Manager
github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
3. Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
4. Tap on “Patch Boot Image File”
5. Navigate to internal storage and select your phone’s boot image that you've downloaded earlier.
6. Wait for a couple of seconds. Magisk will start patching the boot image.
7. Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the ADB fastboot extracted ROM folder on your PC.
(Steps to do on your PC)
1. We assume that you have already downloaded the ADB & Fastboot tool from the link given above.
2. Now, extract the ADB fastboot tool, then move the patched boot image to the same folder.
3. Hold the Shift key and right-click on the mouse to open the command window/PowerShell.
4. Next, enter the following command:
Flash the “patched_boot.img” to install Magisk and root your Android device:
fastboot flash boot patched_boot.img
The flashing process will begin. Once done, run
fastboot reboot
5. Done, Open Magisk to see if it's successful
Click to expand...
Click to collapse
Forgot to Mention, that before proceeding to the steps to do on your PC
you need to do this.
1. Setting - about phone - tap "version" 7 times (To unlock Developer Option)
2. Additional option - developer option - oem unlock bootloader
3. Additional option - developer option - allow USB Debugging
4. turn off device
5. Volume up + power button if logo appears, stop pressing
6. Connect to PC (then proceed to the given steps)
Anyone try this method?
jayaduana said:
Anyone try this method?
Click to expand...
Click to collapse
I bought this phone 24-1-2020. I wanna know to if anyone tried this method.
yes!it works...
Can more people (mainly the ones who allrdy did comment in this thread) confirm method 3 is working?
I updated to CPH1931EX_11_A.28. Do i need a patched boot.img of CPH1931EX_11_A.28 or can i use any boot.img of all versions?
I wanted to know if the boot.img for all versions is the same.
i.daniyal said:
yes!it works...
Click to expand...
Click to collapse
i dont know how u've managed it. i can't boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Is your OPPO A5 2020 rooted now
jayaduana said:
i dont know how u've managed it. i can boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Click to expand...
Click to collapse
Do i understand, you did try method 3 using the boot.img provided in the link?
You were able to patch the boot.img with magisk?
Did you flash the patched boot.img to phone successfully? If so, its safe to use the boot.img provided in the link?
Are you rooted now?
I really need root in order to get boldbeast call recording working properly with pie 9.
jayaduana said:
i dont know how u've managed it. i can't boot into fastboot, using vol down + power buttons or using adb reboot bootloader. can u tell me how to boot into fastboot?
Click to expand...
Click to collapse
Read the instructions carefully it's vol up ?
Typo
hotcold65 said:
Read the instructions carefully it's vol up
Click to expand...
Click to collapse
That has to be a typo, because for the OPPO A5 2020 its powerbutton + volume down
ron23ny said:
That has to be a typo, because for the OPPO A5 2020 its powerbutton + volume down
Click to expand...
Click to collapse
Yes, when use volume up, its keep restarting. When use volume down, its login to coloros recovery mode,not fastboot mode.
jayaduana said:
Yes, when use volume up, its keep restarting. When use volume down, its login to coloros recovery mode,not fastboot mode.
Click to expand...
Click to collapse
Can you please answer my questions in post #12, i really need to know if you rooted successfully.
i.daniyal said:
yes!it works...
Click to expand...
Click to collapse
Some guidance please, or was your answer just a prank?
Ok, i tried to get in fastboot mode with command adb reboot bootloader. I do get the fastboot logo screen for a second, but then it just loading the OS pie 9, like someone stated here before. I read in some sources, OPPO company disabled the fastboot mode for this phone, so you will not able to flash files using adb. I also read power + volume down = recovery mode (working) and power + volume up = fastboot mode (not working because company disabled this).
I use firmware CPH1931EX_11_A.28. Now the big question: does somebody know, if some older version of firmware has fastboot not disabled by company?
Seems for now, you can only root this phone by using hardware tools like miracle box and easy jtag pro.
gffg
ron23ny said:
Can more people (mainly the ones who allrdy did comment in this thread) confirm method 3 is working?
I updated to CPH1931EX_11_A.28. Do i need a patched boot.img of CPH1931EX_11_A.28 or can i use any boot.img of all versions?
I wanted to know if the boot.img for all versions is the same.
Click to expand...
Click to collapse
I also using CPH1931EX_11_A.28 and have exact same bootloader problem.
I manage to extract boot.img from 11_A.13 and 11_A.28 firmwares using "ubuntu ozip to zip" and files appear identical and patched successfully using Magisk. The boot.img provided in the link is not the same, I wouldn't use it.
Did you find out if some older version of firmware has fastboot not disabled by company?
Many thanks for taking time to read reply.
Sotirious said:
I also using CPH1931EX_11_A.28 and have exact same bootloader problem.
I manage to extract boot.img from 11_A.13 and 11_A.28 firmwares using "ubuntu ozip to zip" and files appear identical and patched successfully using Magisk. The boot.img provided in the link is not the same, I wouldn't use it.
Did you find out if some older version of firmware has fastboot not disabled by company?
Many thanks for taking time to read reply.
Click to expand...
Click to collapse
Still no luck. Fastboot is disabled.

How to root with Magisk Lenovo M7 (TB-7305F) / Android 9

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

Categories

Resources