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
Related
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...
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
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.
I just got one of these bad boys and i about rooted it and flashed an older models ROM before i realized i had the 2021 model
I imagine we will have to wait for stock firmware to show up before we can root
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
If you loaded Magisk and are having problems with banking app look at this post and he has another setting in Magisk that you can change to fix this. It is under the heading "a note about mobile banking apps".
Rooting with Magisk
Just a heads up to anyone who is wondering about root for this phone - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus...
forum.xda-developers.com
kbwojo said:
I imagine we will have to wait for stock firmware to show up before we can root
Click to expand...
Click to collapse
Stock firmware maybe available with LMSA' s Flash rescue option
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Fun... I made my first brick using that panda build box link.
kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
Is there a way to root the xt2117-1 version without a pc?
Knox-jack said:
Is there a way to root the xt2117-1 version without a pc?
Click to expand...
Click to collapse
No
Rooting these phones is dead simple. If you boot into bootloader mode, you can find your device's codename. Look for your codename on the lolinet site, select your varient, and download your firmware. Be sure to share the codename here so links can be updated.
Then you unlock your bootloader, patch boot.img you got from the firmware archive with Magisk, and flash the patched image through fastboot.
Seen any Roms for this floating around?
pontifier said:
Fun... I made my first brick using that panda build box link.
Click to expand...
Click to collapse
Did you FLASH recovery.img, instead of BOOT recovery.img?
It's pretty hard to perma brick phones these days. You can probably reflash device with LMSA -
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
I have tried this method on a linux system and a windows version and yhe twrp program always goes to straight to a lockscreen and doesnt stay
kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
Hello. I just got one of these on accident. Meant to get a G9 Power. Oh well. I will still love it. Having rooted countless phones and a great many Motos, I went to root mine without looking for instructions. I fastboot flashed the entire RETUS from lolinet, magisk patched and flashed the new kernel, and then booted to a phone without a working digitizer. Not only that, but when I flashed the original back on it, it didn't fix it. Still no digitizer. I then flashed the entire RETUS again, including the same kernel, and it fixed, but of course I had to set everything up again. I made a fastboot command list though, for flashing firmware from lolinet, if anyone could use it. It's on my computer though. I'll have to share it later. I just made this post to warn others of possible problems with a magisk-patched boot.img.
And also to thank @kbwojo . I've many times wished we could use twrp from a command line. Where did you learn that? Is there a manual?
Oh, BTW, the codename for xt2117-4 is borneo.
arkansawdave74 said:
Hello. I just got one of these on accident. Meant to get a G9 Power. Oh well. I will still love it. Having rooted countless phones and a great many Motos, I went to root mine without looking for instructions. I fastboot flashed the entire RETUS from lolinet, magisk patched and flashed the new kernel, and then booted to a phone without a working digitizer. Not only that, but when I flashed the original back on it, it didn't fix it. Still no digitizer. I then flashed the entire RETUS again, including the same kernel, and it fixed, but of course I had to set everything up again. I made a fastboot command list though, for flashing firmware from lolinet, if anyone could use it. It's on my computer though. I'll have to share it later. I just made this post to warn others of possible problems with a magisk-patched boot.img.
And also to thank @kbwojo . I've many times wished we could use twrp from a command line. Where did you learn that? Is there a manual?
Oh, BTW, the codename for xt2117-4 is borneo.
Click to expand...
Click to collapse
I did try a few things that didn't work. What I ended up doing was just flash boot the original boot.img and that basically reset magisk
Just giving an update and a thanks again to @kbwojo . I finally booted a patched kernel by patching a kernel extracted with twrp in the command line. All the kernels from lolinet caused me to lose touch support after patching, even if I was running the same version the kernel was from. But when I patched it after pulling the kernel with twrp, all is good. Whew. That was different.
Well i have done it. I have rooted my phone .
moto g power (2021)
model XT117-4
Android version 10
basebrand version : HA10_18.534.0273R BORNEO_NA_CUST
Kernel version 4.19.95-perf + #1 Wed Mar 31 12:08:54 CDT 2021
After extensive reading multiple threads i found one and followed the attemt using magisk and no twrp installed.
1st Magisk installed on phone
2nd Install magisk and then patch using the boot.img from a mirror site for Borneo
3rd (not sure yet) Install magisk and then patch file recovery.img (originaly TWRP 3.4 renamed)
renamed the 2 magisk files accordingly to boot and recovery
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
restarted phone directly back into fastboot mode
selected recovery option and started the phone
Sucessful Root!!!!
slickmojo said:
Well i have done it. I have rooted my phone .
moto g power (2021)
model XT117-4
Android version 10
basebrand version : HA10_18.534.0273R BORNEO_NA_CUST
Kernel version 4.19.95-perf + #1 Wed Mar 31 12:08:54 CDT 2021
After extensive reading multiple threads i found one and followed the attemt using magisk and no twrp installed.
1st Magisk installed on phone
2nd Install magisk and then patch using the boot.img from a mirror site for Borneo
3rd (not sure yet) Install magisk and then patch file recovery.img (originaly TWRP 3.4 renamed)
renamed the 2 magisk files accordingly to boot and recovery
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
restarted phone directly back into fastboot mode
selected recovery option and started the phone
Sucessful Root!!!!
Click to expand...
Click to collapse
Can anyone confirm this works?
Just bought a G Power 2021 after thinking it was supported for custom roms already. It should just be arriving today and if i can't unlock the bootloader and root it I'm going to be returning it and getting the 2020, which I'm already considering even if i can be rooted.
Thank you
MyNameIsEarlB said:
Can anyone confirm this works?
Just bought a G Power 2021 after thinking it was supported for custom roms already. It should just be arriving today and if i can't unlock the bootloader and root it I'm going to be returning it and getting the 2020, which I'm already considering even if i can be rooted.
Thank you
Click to expand...
Click to collapse
the 2021 can be rooted, that is what I use with root, and heavily modified UI. You can even change things so system is writable (but will need a computer with linux, or a VM to complete the process), after bootloader unlocked and rooted. But does not presently have any custom ROMs for the device, however some in this branch of the forums have cited they are working on one. If I had the time to, I'd tinker and try my hand at porting LineageOS, or similar fairly easy to port, since TWRP is mostly done or doable for 99% of these devices, there are some that still have touch issues, and that seems to be all digitizer and screen related like mentioned in this thread. As long as you restore yours from the Motorola software and grab your stock files, when they are restored, it has touch, you know you can always fix it back even if a test flash of TWRP has no touch. But then it is not that hard to build from those files the TWRP, even in Android Image Kitchen. I made mine have touch support the hackish way before the compiled way.
So it can absolutely be done, just play things smart with it is all keeping backups of vital files and so on so you have stock even with data loss as the worst that would happen from messing about.
Edit: You will need to keep the device online, wifi and cell data for at least a day if not two before bootloader unlock option in settings will usually permit being toggled on. I know in my experience I got mine on a Friday, and it was not till Sunday about mid-day that it popped, and I'd check it every few hours that I was awake otherwise in that time.
Onoitsu2 said:
the 2021 can be rooted, that is what I use with root, and heavily modified UI. You can even change things so system is writable (but will need a computer with linux, or a VM to complete the process), after bootloader unlocked and rooted. But does not presently have any custom ROMs for the device, however some in this branch of the forums have cited they are working on one. If I had the time to, I'd tinker and try my hand at porting LineageOS, or similar fairly easy to port, since TWRP is mostly done or doable for 99% of these devices, there are some that still have touch issues, and that seems to be all digitizer and screen related like mentioned in this thread. As long as you restore yours from the Motorola software and grab your stock files, when they are restored, it has touch, you know you can always fix it back even if a test flash of TWRP has no touch. But then it is not that hard to build from those files the TWRP, even in Android Image Kitchen. I made mine have touch support the hackish way before the compiled way.
So it can absolutely be done, just play things smart with it is all keeping backups of vital files and so on so you have stock even with data loss as the worst that would happen from messing about.
Edit: You will need to keep the device online, wifi and cell data for at least a day if not two before bootloader unlock option in settings will usually permit being toggled on. I know in my experience I got mine on a Friday, and it was not till Sunday about mid-day that it popped, and I'd check it every few hours that I was awake otherwise in that time.
Click to expand...
Click to collapse
Thank you very much!
I'm perfectly happy with needing to make my own custom ROM. I've never done it, but I've been wanting to for quite some time. At least a few years.
The last 2 android phones I've been using couldn't even be rooted. Long story short, i bought a redmi 5, got it all setup great, then moved and the only service around my new area is Verizon so i sold that, bought a note 5, couldn't root it, bought a pinephone which i do love, but the battery life is really bad. So I've been using my note 5 that's close to a decade old so I'm just looking for a phone with root and a good battery life.
Look forward to getting mine rooted!
Quick question, hopefully doesn't derail too much. Wondering if there is any work being done on the XT2165-5 model? Can't seem to find anything on it?
Hello everyone hope you are all keeping well.
Since I believe that many of you don't know about this, I've decided to share the steps I've done in order to root the OP 11R ( ACE 2 )
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
adb devices
adb reboot bootloader
(so your phone will reboot into fastboot mode)
fastboot flashing unlock
(device should now unlock)
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
2 - Download OP 11R stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Indian Boot.img A_0.8 - download
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
6 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
7 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
8 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
Why title says NORD 2T?
firoz3321 said:
Why title says NORD 2T?
Click to expand...
Click to collapse
MB ... typo
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
firoz3321 said:
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
Click to expand...
Click to collapse
Sorry but there is no msm tool available for new OnePlus devices. + You can use Fastboot enhance tool from github to recover softbrick , magisk is always recommended for rooting because of ease of steps and simple to use
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
saifsohel said:
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
Click to expand...
Click to collapse
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
shiki_senpai said:
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
Click to expand...
Click to collapse
Then remember to take a backup of the boot before rebooting. I messed up big time.
Thanks for the detailed information man. Can I know if bootloader unlock decreases widevine L1 to L3? As this was case with my OP6