First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Reserved !!
hamooz92 said:
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Click to expand...
Click to collapse
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
Exactly.
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
I don't understand
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
They are saying rename magisk from apk to zip and flash it in TWRP
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
Just rename the APK to .zip extention and install through zip installer in twrp
iam almost ready to root my device i have both zip files from adreas tutorial on how root it.
where those zips files need to be in order to flash it?
cmd can be used, sorry iam new to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3lgato said:
View attachment 5485447
Click to expand...
Click to collapse
You need to get the unlock token first
Here is the instructions:
https://www.oneplus.com/support/answer/detail/op588
raginhomosapien said:
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
Click to expand...
Click to collapse
Glad it worked for you. You're welcome
Why it wait forever for attached device, even removing and reconnecting phone?
Rulesless said:
View attachment 5568509
Why it wait forever for attached device, even removing and reconnecting phone?
Click to expand...
Click to collapse
You have to be in fastboot mode before you can flash the recovery. Reboot into fastboot by typing "adb reboot fastboot" (without the quotes). Your phone should then reboot into fastboot mode. NOW, assuming you have already unlocked your bootloader, you can flash the recovery.
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
wcoolj said:
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
Click to expand...
Click to collapse
Just to add to this.....If you are unable to use device unlock because you have not met your carrier's requirements to do so yet you can use the script at this thread and it will open up oem unlock even if your phone is not eligible yet.
I have the N20. No twrp. Flashed a patched boot.img and lost radios. No wifi Bluetooth or sim)mobile data. Hoping that the platform is similar enough that someone could help me recover my device. Phone was sim locked, not sure if that's the issue. I forgot to run the command from the debloat script after flashing the unlock token, shouldn't have rushed this. I don't have a backup of anything though. Was trying to get root to back up everything. Factory resetting did nothing to fix the issue
PsYk0n4uT said:
Factory resetting did nothing to fix the issue
Click to expand...
Click to collapse
LOL never does at this level, just wipes cache and user partition, but nothing of value where we play- the assumption is you (or the bad guys) can't figure out how to write to the system, boot, etc partitions. (snicker).
So the good news is if you can find the EDL image, and follow the procedure to reflash the phone... it should restore everything for you.
(To be clear @PsYk0n4uT I linked you to the N10 EDL thread, not the N20...)
Thanks. So my issue so far. I don't think there is even a stock firmware posted anywhere. Though there is a backup of another device posted. How would I go about finding the EDL files for mine? Can one be created? Or would I need to source that from OnePlus or wait on someone to do that? I actually wasn't aware that I could boot the boot omg without flashing it to test it out first
Related
Hi! Could you please explain if this ROM will be compatible with my smartphone? I'm not sure, I don't found it on the list on LineageOS website.
Well, someone need to compile it for our bv9600 - i also would appreciate it, but i don't have thoose skills...
Also, lenovo vibe c2
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
giannhs_n said:
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
Click to expand...
Click to collapse
jup, runs root - magisk
AMDFenics said:
jup, runs root - magisk
Click to expand...
Click to collapse
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
giannhs_n said:
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
Click to expand...
Click to collapse
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
AMDFenics said:
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
Click to expand...
Click to collapse
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
giannhs_n said:
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
View attachment 4705498
Click to expand...
Click to collapse
exact same version.
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
First u need to go to fastboot mode, to unlock "OEM UNLOCK"
This is easy via adb
-> reboot fastboot
Did u install the correct driver? (ADB driver) is ur device listed?
i tried repacking it myself but with no luck so far, also tried various treble GSI, all booting on my BV9600Pro and basically working but mobile data and phone are broken so that's not an option for now
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Root with sp Flash tool
Hi please Anyone could explain this procedure with Sp Flash Tool and post it?
serg2327 said:
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Click to expand...
Click to collapse
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
AMDFenics said:
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
Click to expand...
Click to collapse
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
serg2327 said:
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
Click to expand...
Click to collapse
I'm glad to hear that it works that way to you. But that doesn't worked for me. So i wrote the way i took, to root. Let the others choose, wich way works for them. :fingers-crossed::good:
I am using another MTK device and SP FlashTool is great it lets you recover from any software brick. So I will advice people to use this method.
I am planning on buying bv9600 pro and having twrp ported and root is a good start to custom roms.
The touch driver issue on twrp should be easily solved with the good kernel module for the twrp. And official twrp support would be nice.
Subscribed to the thread will see where it goes.
hi guys, can you share a clean system twrp backup of bv9600? because my USB is damaged and i can not use sp flash tool to clean restore. thanks!
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
dark-wulf said:
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
Click to expand...
Click to collapse
Maybe there is a way, but i don't know him. It is a common way for many manufacturer, to say, "here u did something you are not supposed too"
https://www.mediafire.com/file/0j0bx6cb0cb58f5/BV9600Pro_30042019_full.zip/file
Latest Firmware (04.2019) Clean SP Flash tool Backup
This is the OnePlus 8 Pro's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
mauronofrio said:
This is the OnePlus 8 Pro's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Click to expand...
Click to collapse
Awesome thanks for the support.
Guys with this tool you can finally root your device without have to flash the specified patched boot.img. I hope it will help you and i hope you will not break anymore the fingerprint sensor. Enjoy it.
mauronofrio said:
Guys with this tool you can finally root your device without have to flash the specified patched boot.img. I hope it will help you and i hope you will not break anymore the fingerprint sensor. Enjoy it.
Click to expand...
Click to collapse
Would you be so kind to elaborate on that? I broke my fingerprint sensor by using a already patched img.. Kind of lazy mistake. But had the phone for just a day so I send it back and I'll be getting a new one tomorrow.
I would love to root it and retain my FP.
mauronofrio said:
Guys with this tool you can finally root your device without have to flash the specified patched boot.img. I hope it will help you and i hope you will not break anymore the fingerprint sensor. Enjoy it.
Click to expand...
Click to collapse
I would also like to know the steps. I'm looking at the tool and when selecting "Only Root" I can choose Magisk 20.4 from the list. The note in the tool says "or you can use 'Only Root' to root your phone you are already in TWRP mode." But as far as I understand there is no legitimate TWRP for our device yet.
Balthazard said:
Would you be so kind to elaborate on that? I broke my fingerprint sensor by using a already patched img.. Kind of lazy mistake. But had the phone for just a day so I send it back and I'll be getting a new one tomorrow.
I would love to root it and retain my FP.
Click to expand...
Click to collapse
letum00 said:
I would also like to know the steps. I'm looking at the tool and when selecting "Only Root" I can choose Magisk 20.4 from the list. The note in the tool says "or you can use 'Only Root' to root your phone you are already in TWRP mode." But as far as I understand there is no legitimate TWRP for our device yet.
Click to expand...
Click to collapse
So you should go in "recovery flasher and rooter" option, there you have to select the only TWRP available, check if "only boot" is checked, check "root after boot", select magisk 20.4 and click on the button at the bottom of the page. The TWRP will be booted and magisk flashed, and then from TWRP you can manually reboot to system and your device will be correctly rooted.
mauronofrio said:
So you should go in "recovery flasher and rooter" option, there you have to select the only TWRP available, check if "only boot" is checked, check "root after boot", select magisk 20.4 and click on the button at the bottom of the page. The TWRP will be booted and magisk flashed, and then from TWRP you can manually reboot to system and your device will be correctly rooted.
Click to expand...
Click to collapse
Thank you! I will be doing that when I get my phone.
It's actually just using your twrp build but instead of installing it, booting it and using twrp to flash the stable build of Magisk.
Thank you for your hard work!
Is it possible to restore fingerprint with this tool and appropriate files?
t-mizzle said:
Is it possible to restore fingerprint with this tool and appropriate files?
Click to expand...
Click to collapse
If you lost fingerprint, due to Canary Magisk, just switch to stable Magisk, and reinstall the latest update. If you did a local upgrade the file is still in your download folder. Worked fine for me.
spotmark said:
If you lost fingerprint, due to Canary Magisk, just switch to stable Magisk, and reinstall the latest update. If you did a local upgrade the file is still in your download folder. Worked fine for me.
Click to expand...
Click to collapse
I've tried that, it doesn't work for me.
t-mizzle said:
Is it possible to restore fingerprint with this tool and appropriate files?
Click to expand...
Click to collapse
actually no
Gordietm said:
I've tried that, it doesn't work for me.
Click to expand...
Click to collapse
Restore your persist img ..
If you have a backup...
cultofluna said:
Restore your persist img ..
If you have a backup...
Click to expand...
Click to collapse
I don't have one.
This will work on any version of OOS?
Sent from my IN2025 using Tapatalk
czerdrill said:
This will work on any version of OOS?
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
Yes sure
Thank you mauronofrio..!!!!
Has anyone used this tool yet to unlock the bootloader and root their 8 pro?
I just can't be the first one. Lmao!!!!
Is there a Tool to install on a Chromebook/Linux?
mauronofrio said:
So you should go in "recovery flasher and rooter" option, there you have to select the only TWRP available, check if "only boot" is checked, check "root after boot", select magisk 20.4 and click on the button at the bottom of the page. The TWRP will be booted and magisk flashed, and then from TWRP you can manually reboot to system and your device will be correctly rooted.
Click to expand...
Click to collapse
I'm having some trouble, any guidance would be appreciated. I have "only boot" checked and "root after boot" checked, and the phone just boots into TWRP and then hangs there. I've tried closing the command prompt and selecting "root only" but my device isn't showing up in the device list.
Konfuzion said:
I'm having some trouble, any guidance would be appreciated. I have "only boot" checked and "root after boot" checked, and the phone just boots into TWRP and then hangs there. I've tried closing the command prompt and selecting "root only" but my device isn't showing up in the device list.
Click to expand...
Click to collapse
You have some problems with adb
1 . unlock BootLoader AND Root https://forum.xda-developers.com/v50-thinq/development/lg-v50-temp-root-exploit-via-cve-2020-t4098077
2. Download the required files ( twrp-installer-v3.3.1-V50_ab.zip )
View attachment twrp-installer-v3.3.1-V50_ab.zip
3.Install the corresponding TWRP flash module in Magisk Manager, remember not to restart
The module is one-time, and it will be deleted automatically after TWRP is successfully brushed in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4.Re-swipe the Magisk 20.4 card package in Magisk Manager
5.Verify that TWRP is successfully installed
adb reboot recovery
6.Wait for the phone to restart to the TWRP interface, I believe everyone knows what this thing looks like
7.Disable_Dm-Verity can solve the problem of decryption failure after booting
Does this still have the touchscreen issue if you boot from OS to Recovery?
5dprince said:
1 . unlock BootLoader AND Root https://forum.xda-developers.com/v5...g-v50-temp-root-exploit-via-cve-2020-t4098077
2. Download the required files ( twrp-installer-v3.3.1-V50_ab.zip )
3.Install the corresponding TWRP flash module in Magisk Manager, remember not to restart
The module is one-time, and it will be deleted automatically after TWRP is successfully brushed in
4.Re-swipe the Magisk 20.4 card package in Magisk Manager
5.Verify that TWRP is successfully installed
adb reboot recovery
6.Wait for the phone to restart to the TWRP interface, I believe everyone knows what this thing looks like
7.Disable_Dm-Verity can solve the problem of decryption failure after booting
Click to expand...
Click to collapse
Dude. You didn't say to flash magisk again, nor did you credit the author of the twrp. And touchscreen does not work with the adb command, so I do not know why you said to do that instead of the key combo...
Indeed, there are some problems with the touch screen in this TWRP version. Can anyone elaborate on how do I even boot into it with key combination? I've been fiddling with them for about half an hour before I dropped it on the carpet and it booted, and I had exactly one chance to flash everything before a reboot, I'd rather know what I pressed if I ever want to do that again.
UPD: getting into TWRP is almost like on v30: power+volUp, when logo appears you let go of power button and immediately press it again, then proceed to factory reset option which will boot you to TWRP. I'll leave it here in case somebody will google it later.
https://youtu.be/b1lnYdNxVMg
The issue with touch not always working in TWRP is that the stock kernel disables the touch driver when the boot reason is recovery (aka from adb reboot recovery), while via button combo, the reason isnt "recovery", so touch works in TWRP
Is there a way to get twrp image somewhere? If I now have unlocked bootloader, won't I be able to just flash it from fastboot?
Installed it but can't mount my internal storage in TWRP. Anyone else have this issue?
SGCMarkus said:
The issue with touch not always working in TWRP is that the stock kernel disables the touch driver when the boot reason is recovery (aka from adb reboot recovery), while via button combo, the reason isnt "recovery", so touch works in TWRP
Click to expand...
Click to collapse
And what would be the combination of buttons to start the TWRP with active touch functionality? If I install TWRP from fastboot is it different than if I install it from QFIL?
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
That would be great.
smitra420 said:
Installed it but can't mount my internal storage in TWRP. Anyone else have this issue?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/twrp_3-3-1-for-usa.4304847/.
GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
is this available yet, for the LM-V500EM?
Didn't work for me 500N problem of decryption failure after booting, how to disable it?
didn't work for me LM-V500EM after boot twrp asks for decryption password ?
GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
I don't think that's possible since this device does not have a separate recovery partition so this patch unpacks the boot ramdisk and injects twrp code there - not doable via fastboot.
antintin said:
Dude. You didn't say to flash magisk again, nor did you credit the author of the twrp. And touchscreen does not work with the adb command, so I do not know why you said to do that instead of the key combo...
Click to expand...
Click to collapse
Exactly. The pictures no longer display and this magisk is different than the latest. Do we leave dmverity checked in magisk?
I rebooted before re flashing magisk again because I've never done this and its mind boggling to have to flash magisk twice (why couldn't it stick the first time or have an obvious option?). Anyway. Anyone know how to reverse the softbootloop these instructions result in!?!
How do I get root back after magisk flashed twrp and lied? When I go to recovery, its stock. Now when I replace boot_a with magisk patched in edl mode bootloop! This worked the first time why doesn't it any longer?
q-killer said:
How do I get root back after magisk flashed twrp and lied? When I go to recovery, its stock. Now when I replace boot_a with magisk patched in edl mode bootloop! This worked the first time why doesn't it any longer?
Click to expand...
Click to collapse
Why would you want TWRP if you weren't going to replace the OS? Go into TWRP and flash something else, with Magisk as well.
For anyone reading, the button combo to get into TWRP is Vold down + power. As soon as LG Logo starts up, you release power for a second then go back to pressing it. Phone will ask if you want to erase data. Select yes, and yes. Phone will boot TWRP.
TPMJB said:
Why would you want TWRP if you weren't going to replace the OS? Go into TWRP and flash something else, with Magisk as well.
For anyone reading, the button combo to get into TWRP is Vold down + power. As soon as LG Logo starts up, you release power for a second then go back to pressing it. Phone will ask if you want to erase data. Select yes, and yes. Phone will boot TWRP.
Click to expand...
Click to collapse
Thanks for this question, and advice on getting to recovery with keys, it's the only way to get touchscreen support in recovery, and it's a good question... unfortunately my phone no longer asks if I want to erase data for some odd reason when accessing recovery... this really tripped me up. I was trying to flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, but it was too late in this instance as system was already encrypted. so the mistake made was that I didn't disable dmverity, which needs to be done either before setup, or directly after first restart. Otherwise system starts encrypting and it seems boot_a is encrypted and can't be directly replaced via qfil, since it causes a bootloop at that point. I wasn't able to access and therefore fix NT-Code issue errors (observed after cross flashing) at this point either, so the key is to first backup or get a copy of vmeta_a and boot_a along with other key files, then flash engineering (eng_abl) in qfil so that fastboot can be accessed and then fastboot --disable-verity --disable-verification flash vbmeta vbmeta_a-v50original.bin, place backed up boot_a on phone, patch with Majisk, copy back to pc, then flash patched boot with qfil or fastboot, Then fastboot flash abl_a abl_a(orig-nonENG).bin, also then restore ftm-original and modem_a/b-original with same method in fastboot or using qfil, rebot then *#*#4636#*#* choose automatic and NR/LTE/CDMA/EcDO/GSM/WCDMA , then append NT errors to /Product/OP/cust_path_mapptings.cfg following format there, and then finally flash twrp via magisk but don't reboot, and then reflash magisk.zip, and reboot. Finally, following guides for adaway, revanced, and wallet hiding should work. There are a ton of steps to this phone, especially sprint version.
i have lg v50 450 verizon model number lm-g850 android version 10 g85020j
does not read sim cards.
How to unlock the bootloader on it and flash it. Thank you !!!
Hi everyone
My phone model is xt2075-3,I want to root
Can I directly flash the latest magisk(20.4) to get root permission after unlocking BL?
I've succeeded in getting root.The steps are as follows
1.Download the twrp for your mobile phone,and magisk20.4.zip,magisk 7.5.1.apk
2.Visit Motorola official unlock website to unlock BL
3.You have 2 choice,A.boot on twrp one time;B.flash twrp;I choose A
4.Whatever your choose,in the twrp,install magisk zip,after done,reboot system
Enjoy root!
If you use the Magisk Manager to patch the boot image manually, and then flash that through fastboot - will that work also?
(My phone has yet to arrive so can't test this just yet...)
Update : i got the 8gb ram 128gb varient and i could boot into twrp from fastboot but i cannot flash replacing stock recovery nor i can see the internal or external memory due to decryption error
However, i basically unlocked boot loader and booted in fast boot then i flashed the patched boot.img ( installed magisk apk and added the stock boot.img inside the phone to patch it) then copy it back to pc and flashed it in fastboot mode and now i got root access
NOTE : if you happen to do something wrong you cannot use rescue and backup software to restore your phone to stock again ... flash stock boot.img in fastboot first so the software will recognize the phone back again
sniper9911 said:
Update : i got the 8gb ram 128gb varient and i could boot into twrp from fastboot but i cannot flash replacing stock recovery nor i can see the internal or external memory due to decryption error
However, i basically unlocked boot loader and booted in fast boot then i flashed the patched boot.img ( installed magisk apk and added the stock boot.img inside the phone to patch it) then copy it back to pc and flashed it in fastboot mode and now i got root access
NOTE : if you happen to do something wrong you cannot use rescue and backup software to restore your phone to stock again ... flash stock boot.img in fastboot first so the software will recognize the phone back again
Click to expand...
Click to collapse
where did you find the boot.img and the patched one?
Thanks
Mr.Krulez said:
where did you find the boot.img and the patched one?
Thanks
Click to expand...
Click to collapse
Get the full stock image by downloading rescue and smart assistant app from lenovo which supports moto phones ... Do login and get the fastboot rescue option while plugging your phone in the pc in fastboot mode .. then it will download it full firmware for your varient
Becareful that continue to flash the firmware will wipe your phone completely
After that get a copy of the boot.img file ... Copy it to the internal memory and install magisk manager apk from its official github site ... Now patch the boot.img you copied in your phone inside the magisk app then copy it back to your pc
Lear how to flash it from fastboot
Flash it
Done .. you are now rooted by patched boot.img with stock recovery !
Sent from my moto g 5G plus using Tapatalk
View attachment 5143479View attachment 5143477View attachment 5143481
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Hi Guys,
my device is a/b device, bootloader unlocked, could you please kindly advise to flash twrp
what is the fastboot command, i use fastboot flash recovery twrp.img and i get a bootloop . the command fastboot boot twrp.img runs twrp onece and its fine, but how do i flash it please?
thanks and kind regards
emanuel said:
what is the fastboot command, i use fastboot flash recovery twrp.img and i get a bootloop . the command fastboot boot twrp.img runs twrp onece and its fine, but how do i flash it please?
Click to expand...
Click to collapse
I think the flash method fails because there is no partition called "recovery" - as an A/B device it looks like there are two:
Code:
nairo:/ $ ls -l /dev/block/by-name/ | grep recovery
lrwxrwxrwx 1 root root 16 1970-05-20 07:34 recovery_a -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 1970-05-20 07:34 recovery_b -> /dev/block/sdf20
if you have the Magisk zip file on the internal storage you can use the "fastboot boot twrp.img" method to flash it from there (for some reason TWRP can't see the SD card on my device)
Now for my question... my rooted (UK Retail) device has indicated that there is an OTA update:
I've tried using the method described here to restore the boot partition to stock so that it doesn't interfere with the process, but it fails (see attached images).
Does anyone know of a working method? I have downloaded the full (2+GB) update so am prepared to flash that (and restore everything else from backups) if necessary - but would rather not if it can be avoided...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xth88312 said:
I've succeeded in getting root.The steps are as follows
1.Download the twrp for your mobile phone,and magisk20.4.zip,magisk 7.5.1.apk
2.Visit Motorola official unlock website to unlock BL
3.You have 2 choice,A.boot on twrp one time;B.flash twrp;I choose A
4.Whatever your choose,in the twrp,install magisk zip,after done,reboot system
Enjoy root!
Click to expand...
Click to collapse
Hi @xth88312 ,
can you give the link you used to download TWRP for Moto XT2075-3?
I unlocked my phone through the official Motorola site:
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I downloaded the latest Magisk and MagiskManager in the same directory from
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I downloaded the original firmware from https://mirrors.lolinet.com/ and extracted the boot.img in the same directory, then issued, through the ADB connection:
Code:
adb install ./MagiskManager-*.apk
adb push ./boot.img /sdcard/Download/
(Replace the star as needed)
I opened MagiskManager app (you need to be connected to the Internet) and in the Magisk card I tapped Install > "Select and Patch a File". I browsed for and selected /sdcard/Download/boot.img and tapped "Let's go". A patched image /sdcard/Download/magisk_patched_*.img is created. Then, through the ADB connection, I issued:
Code:
adb pull /sdcard/Download/magisk_patched_*.img
adb reboot bootloader
fastboot devices
fastboot flash boot magisk_patched_*.img
fastboot reboot
At reboot, the phone was rooted.
boringtech said:
Hi @xth88312 ,
can you give the link you used to download TWRP for Moto XT2075-3?
Click to expand...
Click to collapse
[RECOVERY][UNOFFICIAL] TWRP 3.5.0.0
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
thats the link for twrp for moto g 5g plus..
use at own risk as i havent tried it myself so im not responsible for bricked devices etc...FLASH AT OWN RISK....
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
youll have to patch bo
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
you need to
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
youll need the patched boot.img to gain root, thats how ive had to root all my moto phones ive had, never been able to just flash supersu etc, someone will jump in if im wrong but as far as i know you need to patch the boot.img....
Remember everything you do is at your own risk i take no responsibility for.what you do with your device
Good afternoon XDA
Well like the title says, I need help rooting my LE2127 with T-Mobile's release of A13. Made several attempts which all failed.
With A13 installed and the Bootloader unlocked, I then shut off the phone, booted into EDL mode, used the MSMTool to readback the boot.img, transferred that image to the device and patched it with Magisk. From there the device was put into Bootloader mode, and via pc flashed with the command "Fastboot flash boot_ a (img) followed by "Fastboot flash boot_b (img) then reboot into system. This procedure has worked without issue for A11 and A12, but doesn't seem to work on 13. It flashes, then just hangs. With this procedure failing, I then temporarily booted TWRP (since T-Mobile variant is known to have issues with installing it) and attempted to install the Magisk.zip, which also fails. It doesn't seem like TWRP has file system access. I have tried both procedures several times now. I made sure Windows 11 is in test mode, since 11 doesn't play nice with fastboot and Qualcom EDL drivers. I have a known good USB cable, plugged into a USB 2.0 port, and once again the first method mentioned above has worked without issue for T-Mobile's A11 & A12 releases.
Can somebody please help a dumb redneck figure this out? Thanks
DaveImagery said:
Good afternoon XDA
Well like the title says, I need help rooting my LE2127 with T-Mobile's release of A13. Made several attempts which all failed.
With A13 installed and the Bootloader unlocked, I then shut off the phone, booted into EDL mode, used the MSMTool to readback the boot.img, transferred that image to the device and patched it with Magisk. From there the device was put into Bootloader mode, and via pc flashed with the command "Fastboot flash boot_ a (img) followed by "Fastboot flash boot_b (img) then reboot into system. This procedure has worked without issue for A11 and A12, but doesn't seem to work on 13. It flashes, then just hangs. With this procedure failing, I then temporarily booted TWRP (since T-Mobile variant is known to have issues with installing it) and attempted to install the Magisk.zip, which also fails. It doesn't seem like TWRP has file system access. I have tried both procedures several times now. I made sure Windows 11 is in test mode, since 11 doesn't play nice with fastboot and Qualcom EDL drivers. I have a known good USB cable, plugged into a USB 2.0 port, and once again the first method mentioned above has worked without issue for T-Mobile's A11 & A12 releases.
Can somebody please help a dumb redneck figure this out? Thanks
Click to expand...
Click to collapse
Have you tried temp booting the magisk patched image instead of flashing it? fastboot boot boot magiskpatched.img rather than fastboot flash boot_[n] magiskpatched.img
Appreciative said:
Have you tried temp booting the magisk patched image instead of flashing it? fastboot boot boot magiskpatched.img rather than fastboot flash boot_[n] magiskpatched.img
Click to expand...
Click to collapse
Actually I have (forgot to mention that) and same result, just hangs on fastboot logo. Thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't tell you what exactly is wrong on your end but I can tell you that now that I finally found the time, I've rooted mine on the TMO OOS13 with (almost) no trouble. Here's what I did.
Entries in brackets [ ] are commands
Enable developer options
Enable OEM Unlocking
Enable USB debugging
Reboot bootloader
Flash unlock token
Unlock Bootloader
Boot into Android
Skip setup and turn on USB debugging
Reboot bootloader again
Temp boot TWRP
Tap reboot button to see which slot is active (slot A)
Go back to main screen without rebooting
Open ADB shell while booted in TWRP
[dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img]
Reboot system
Install magisk app
Patch /storage/emulated/0/boot_a.img
Copy magisk_patched_boot_a.img to computer hard drive
Reboot bootloader
[fastboot flash boot_a magisk_patched_boot_a.img]
reboot and open magisk
Finish installation via direct install method and reboot
Profit
Verify root is present
Reboot to fastboot
Flash stock boot image to unroot
Verify root is gone
Reboot bootloader again
Temp boot TWRP
Flash magisk-v26.1.apk
Reboot system
Open magisk
Finish installation via direct install method and reboot
Profit
Both methods worked for me. The one hiccup I had was that one of the times I temp booted TWRP it couldn't read my USB stick so I had to reboot back into fastboot mode then temp boot TWRP again, and then it worked fine.
First I rooted by backing up the stock unmodified boot image, patching it with magisk, then flashing the patched boot image via fastboot. Once I verified that this method worked and that magisk was installed properly I unrooted by flashing the stock unmodified boot image, then I checked and verified that magisk was no longer installed and that root access was in fact gone. Next I rooted again by temp booting TWRP and flashing the newest magisk apk, then I verified that this method worked as well and that magisk once again was properly installed.
TWRP never had any problems reading my internal storage but if it did here's what I'd do. Temp boot TWRP again and retry. If TWRP still won't read internal storage after multiple attempts format data, reboot to fastboot, temp boot TWRP again, and retry. If that doesn't work I'd format data again, reboot into Android, reboot to fastboot, temp boot TWRP again and retry. Like I said in my other thread, TWRP is a bit wonky on this phone. I don't know why, but eventually it works. It reminds me of an old worn out doorknob that won't unlock unless you jiggle it while you turn the key.
TheGhost1951 said:
View attachment 5909849
Click to expand...
Click to collapse
Masterchief87 said:
I can't tell you what exactly is wrong on your end but I can tell you that now that I finally found the time, I've rooted mine on the TMO OOS13 with (almost) no trouble. Here's what I did.
Entries in brackets [ ] are commands
Enable developer options
Enable OEM Unlocking
Enable USB debugging
Reboot bootloader
Flash unlock token
Unlock Bootloader
Boot into Android
Skip setup and turn on USB debugging
Reboot bootloader again
Temp boot TWRP
Tap reboot button to see which slot is active (slot A)
Go back to main screen without rebooting
Open ADB shell while booted in TWRP
[dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img]
Reboot system
Install magisk app
Patch /storage/emulated/0/boot_a.img
Copy magisk_patched_boot_a.img to computer hard drive
Reboot bootloader
[fastboot flash boot_a magisk_patched_boot_a.img]
reboot and open magisk
Finish installation via direct install method and reboot
Profit
Verify root is present
Reboot to fastboot
Flash stock boot image to unroot
Verify root is gone
Reboot bootloader again
Temp boot TWRP
Flash magisk-v26.1.apk
Reboot system
Open magisk
Finish installation via direct install method and reboot
Profit
Both methods worked for me. The one hiccup I had was that one of the times I temp booted TWRP it couldn't read my USB stick so I had to reboot back into fastboot mode then temp boot TWRP again, and then it worked fine.
First I rooted by backing up the stock unmodified boot image, patching it with magisk, then flashing the patched boot image via fastboot. Once I verified that this method worked and that magisk was installed properly I unrooted by flashing the stock unmodified boot image, then I checked and verified that magisk was no longer installed and that root access was in fact gone. Next I rooted again by temp booting TWRP and flashing the newest magisk apk, then I verified that this method worked as well and that magisk once again was properly installed.
TWRP never had any problems reading my internal storage but if it did here's what I'd do. Temp boot TWRP again and retry. If TWRP still won't read internal storage after multiple attempts format data, reboot to fastboot, temp boot TWRP again, and retry. If that doesn't work I'd format data again, reboot into Android, reboot to fastboot, temp boot TWRP again and retry. Like I said in my other thread, TWRP is a bit wonky on this phone. I don't know why, but eventually it works. It reminds me of an old worn out doorknob that won't unlock unless you jiggle it while you turn the key.
Click to expand...
Click to collapse
Hello, and many thanks for your comprehensive reply. Aside from how you extracted the boot.img (I did it via MSMTool) that's pretty much the procedure I used as well. Curiously, I had no issues getting TWRP to read from my USB thumb drive, the flashing just failed. In your list you have "Flash magisk 26.1.apk" You mean the zip file right? Also, after you flashed, did it just sit on the Fastboot screen a while, then boot into system, or did it boot into system pretty much immediately? Just curious if perhaps I didn't give it long enough. It just appeared to be hanging.
DaveImagery said:
Hello, and many thanks for your comprehensive reply. Aside from how you extracted the boot.img (I did it via MSMTool) that's pretty much the procedure I used as well. Curiously, I had no issues getting TWRP to read from my USB thumb drive, the flashing just failed. In your list you have "Flash magisk 26.1.apk" You mean the zip file right? Also, after you flashed, did it just sit on the Fastboot screen a while, then boot into system, or did it boot into system pretty much immediately? Just curious if perhaps I didn't give it long enough. It just appeared to be hanging.
Click to expand...
Click to collapse
Normally I'd just flash magisk through TWRP then be done with it but since you were having issues I decided to try patching the boot image as well. As for flashing the Magisk apk, this is a bit of an oversimplification but an apk is basically a zip archive with a different extension. If you want to see for yourself, just rename any apk file to .zip and you'll see that you can view and extract the contents with any file manager that supports zip archives.
With this in mind, it's pretty easy for a developer to make a dual purpose apk file that can be installed like any other app but can also be flashed through recovery like a flashable zip. TWRP just has to be made in a way that allows it to treat an apk the same as a zip, and apparently this is something that TWRP now supports. There's no need to look for a magisk zip file or even rename it from magisk.apk to magisk.zip because TWRP doesn't care about the .apk file extension. Also, official Magisk releases are only uploaded to GitHub and don't come in the form of zip files anymore, so if you go looking somewhere else for a zip file it could be tampered with.
If I remember correctly, the only time it sat at the fastboot screen was when I temp booted TWRP and that only lasted 5 or 10 seconds before TWRP booted up normally. After flashing the patched boot image and giving the reboot command it just showed the orange state warning about the bootloader being unlocked, then booted up normally. The same goes for when I just flashed the magisk apk through TWRP. It just showed the annoying warning about unverified software then booted normally.
After two more failed attempts. Thought I would try another USB cable. EUREKA!!!
flashed the patched magisk boot img and it crashed my phone. Stuck on orange state boot screen...... back to drawing board....starting from scratch with msm tool....ugg I guess I should have tried different cables to do the fastboot boot patched img to see if it would have worked. Lessons learned.. although I had been using the same cable in the past. I guess for A13 it may need to be different.
tried a different cable but still freezes at OnePlus logo with Fastboot Mode printed below the logo......
finally got it done by sideloading the unified twrp recovery and then installing magisk 26.1 done I used twrp for A12 and the the sideload of the unified twrp.
Damn, lol rooting this phone sounds nerve racking.
Not really!
TheGhost1951 said:
Not really!
Click to expand...
Click to collapse
I'm just worried that my banking apps and google wallet will be non-stop issues. I've gotten so used to using those everyday.
SkOrPn said:
I'm just worried that my banking apps and google wallet will be non-stop issues. I've gotten so used to using those everyday.
Click to expand...
Click to collapse
Add to magisk deny list..