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 !!!
Related
Hi Guys - I installed this twrp via fastboot flash recovery, I am on china dev version MIUI 10 8.8.3 Beta, rebooted to system, powered down, and then volume up & power button to go to recovery - I am greeted by china recovery 3.0 in chinese. It appears twrp does not stick. Device is unlocked bootloader (from vendor), Just flashed over from the fake ROM, this is the 128 GB / 6 GB version phone. What am I doing wrong
Lol, dont understand why you typed "revocery" in your pic but it still understood
badrsj said:
Hi Guys - I installed this twrp via fastboot flash recovery, I am on china dev version MIUI 10 8.8.3 Beta, rebooted to system, powered down, and then volume up & power button to go to recovery - I am greeted by china recovery 3.0 in chinese. It appears twrp does not stick. Device is unlocked bootloader (from vendor), Just flashed over from the fake ROM, this is the 128 GB / 6 GB version phone. What am I doing wrong
Click to expand...
Click to collapse
After flashing china rom, need to boot to fastboot then execute the following commands in adb:
1. fastboot format userdata
2. fastboot flash recovery twrp.......
3. fasboot boot recovery twrp...... so the phone can boot into recovery then follow the rest of the guide if you want to flash xiaomi.eu rom
That's strange, but Orange recovery also reverted
You're right it shouldn't have installed but it did. The Orange recovery also installed, neither stuck tho
Awesome
martin.burgas said:
After flashing china rom, need to boot to fastboot then execute the following commands in adb:
1. fastboot format userdata
2. fastboot flash recovery twrp.......
3. fasboot boot recovery twrp...... so the phone can boot into recovery then follow the rest of the guide if you want to flash xiaomi.eu rom
Click to expand...
Click to collapse
Will try
Thanks
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights out
{
"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"
}
Sent from my SM-N950U1 using Tapatalk
badrsj said:
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights outView attachment 4591035
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
I'm straggling with Chinese like most of us here. There is an android app you can install on your other phone which would use your cam to translate Chinese. Try that see if it helps...
What I am getting from this (cannot read chinese) but phone goes into fastboot - So I have formated, deleted the eu rom I had on the internal - so start again install the fastboot rom, twrp into it reboot twrp, have eu rom on SD Card and go from there.
badrsj said:
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights out
Click to expand...
Click to collapse
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
martin.burgas said:
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
Click to expand...
Click to collapse
Change phone file system
How?
Currently it states reset device and loops off and on.
It's a mess
Sent from my SM-N950U1 using Tapatalk
badrsj said:
Change phone file system
How?
Currently it states reset device and loops off and on.
It's a mess
Click to expand...
Click to collapse
From TWRP Wipe->Advanced wipe->Repair or change file system. Reboot TWRP from within TWRP -> Reboot recovery.
Can I flash this instead
Hi, I'd also flashed miui_MIMAX3Global_V9.6.6.0.OEDMIFD_091e94a919_8.1
Can I flash this rom on top of the above?
Fastboot ROM: http://bigota.d.miui.com/V9.6.7.0.O...EDCNFD_20180705.0000.00_8.1_cn_7c9a1a57f8.tgz
Located here
https://xiaomi.eu/community/threads...-and-recovery-rom-9-6-7-0-for-mi-max-3.45198/
Thanks, I'm afraid I'll brick the device?
Also struggled with twrp, switched back to miui's.
Look the twrp official site, find your device and follow step by step the fastboot method till the end. Worked.
I have solved the TWRP issue, the problem now is that when I flash a ROM it does not seem to work and crashes.
I am worried this is going to get bricked in this process. Maybe just wait for the official Global to come out
Which Partitions Change to F2FS
martin.burgas said:
From TWRP Wipe->Advanced wipe->Repair or change file system. Reboot TWRP from within TWRP -> Reboot recovery.
Click to expand...
Click to collapse
Hi, Which partitions to change to F2FS, If we change the Data Partition that would need to reflash Miui Chinese again?
Many Many Thanks - I am up and running
martin.burgas said:
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
Click to expand...
Click to collapse
Thanks Martin you're very helpful I am now up and running. I am going to list a list of mistakes
1. I should have used CMD, not Powershell (type CMD in the address bar of the folder where your recovery is)
2. I did not know the sequence of flashing (change to F2FS, reboot recovery from within, Wipe Dalvic, Cache, Data) Then flash
3. I did not know how to boot recovery from fastboot (fastboot boot "recovery.img" "name of your recovery")
4. I did not know to change file system for data, (From TWRP Wipe->Advanced wipe->Repair or change file system. Select Data partition, select F2FS) change it then reboot recovery = see step 2 above.
Thanks Very Much
I am listing these for reference, and for those who help others to know what other errors may be committed.
Twrp supposedly installed -- twice -- but i got nothin'
Hi all,
I love this forum -- despite having a bunch of learning disabilities, I've managed to root a half dozen devices over the years thanks to your patience. This time I'm stumped.
Can't install TWRP. It says it is installed successfully with ADB (see screenshot). I used
twrp-3.3.1-0-nitrogen.img and I'm on I'm on Miui Global 10.3.5 Stable (Android 9PKQ1.181007.001).
Command line confirms installation. MM3 reboots when I enter the fastboot reboot to recovery command but it boots into the main system. I can boot into recovery using power/volume up method but it boots to the stock Mi recovery.
Should I try OrangeFox? Does this have anything to do with dm-verity? Is there anything else I can try to get root?
Originally, I wanted to install LineageOS, but what with locked bootloaders, anti-rollback, DM Verity, etc. , I'm guessing that's over my head and would happily settle for rooted stock.
Best,
Amy
Twrp supposedly installed -- twice -- but i got nothin'
EUREKA!!! I found a simple solution to install TWRP no worries about verity etc and I am rooted!
Genius idea came from Youtuber. Here is the link but I will still describe it in case the video gets removed for some reason.
You do it the regular stuff:
adb reboot bootloader
fastboot flash recovery "twrp filename"
But then while you're still in fastboot enter "fastboot recovery" into the command line and before you hit enter, press and hold volume up on the phone.
It boots into TWRP!
Note that you will keep getting Mi Recovery using volume down/power combo until after you use TWRP install (accessing TWRP with above method) to flash magisk.
Then, TWRP seems to stick. (Although just in case it gets unstuck, I installed the official twrp app from the Play store, since it has a 'boot into recovery' option.
Firstly, when plugging my 7t in to my windows 10 PC, I am asked to choose which mode to go in within usb preferences, as I did previously in order to achieve and ADB driver connection I chose file transfer.......
this didn't work for some reason, only when in MIDI did I get a confirmation with adb devices.....even though there is still no sign of adb interface in device manager.....
any ideas? I can get adb connection with MIDI but is this good enough to flash recoveries/boot images etc....?
I tried to flash twrp and I could successfully boot into twrp directly via fastboot but twrp couldn't seen any of my storage, despite having all security methods turned off...
all i want to do is gain root access but I am having no joy....
ever since android 10 rooting anything for me has been a pain in the ass......truly fed up....it shouldn't be this hard......
I also flashed a patched boot image in an attempt to gain root access but it all did was break my wifi........which i fixed by copying over the latest image and installing locally......
please HELP....
Everything about this issues is already said in this forum.
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
sweet, ill check it out.....
ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
mediaman123 said:
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
Click to expand...
Click to collapse
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Josh McGrath said:
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Click to expand...
Click to collapse
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
mediaman123 said:
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
Click to expand...
Click to collapse
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
{
"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"
}
fawazahmed0 said:
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
Click to expand...
Click to collapse
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
mediaman123 said:
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
Click to expand...
Click to collapse
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
fawazahmed0 said:
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
Click to expand...
Click to collapse
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
mediaman123 said:
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
Click to expand...
Click to collapse
it wipe's the data
mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
TWRP is not functional at the moment, so stay away from it.
The only way to root right now is to use the patch boot image method.
Lossyx said:
No don't do this.... This is not about encryption at all. It's about the major partitioning changes that has happened in Android 10. Wiping the system will just make everything worse.
Avoid using TWRP at all.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Oh, I didn't know this phone was on Android 10, Thanks for letting me know.
TWRP doesn't support Android 10 yet.
You can see it here
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Actually there is a twrp compiled for this phone, but that doesn't work , you can see the messages in thread:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
The steps I told, was for Android 9 and earlier devices, I assumed, this is an old device.
@mediaman123, So please wait, until twrp starts supporting the Android 10.
And for rooting, I am not sure, whether magisk supports this new phone or not.
Maybe @Lossyx can help you on that.
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
mediaman123 said:
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
Click to expand...
Click to collapse
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
So if it boots an older image successfully I can move it over to the phone to patch to then flash it or use the already patched one and flash that...?..
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
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
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..