Bootloop after flashing magisk_patched.img - OnePlus 7T Questions & Answers

I get into a bootloop after flashing magisk.
The only way out of the bootloop is to flash the original unpatched boot.img (after which everything works perfectly).
I am on 10.0.8. Anybody else have any idea how to troubleshoot this?

I don't think you have to flash Magisk patched boot image, you just have to boot from it. Don't know if its the same thing.
What I do is "fastboot boot magisk_patched.img", then when it boots on the Magisk Manager app, select install -> direct install. After installation is done reboot like normal and Magisk should be installed normally by then.

hectorviov said:
I don't think you have to flash Magisk patched boot image, you just have to boot from it. Don't know if its the same thing.
What I do is "fastboot boot magisk_patched.img", then when it boots on the Magisk Manager app, select install -> direct install. After installation is done reboot like normal and Magisk should be installed normally by then.
Click to expand...
Click to collapse
Hmm, I try your method and I think it's roughly the same.
When I do fastboot boot magisk_patched.img, my device goes into a bootloop. I waited 8 minutes (exactly) and figured it was never gonna boot, and so I killed it. When it booted again, it booted fine with no problems (except not rooted, obviously).

Then maybe you're using a wrong boot image, what's the Build number on Settings -> About phone? (It should be something like "Oxygen OS 10.0.8.HD65AA", that's what I'm currently on). Also, is your bootloader unlocked?

hectorviov said:
Then maybe you're using a wrong boot image, what's the Build number on Settings -> About phone? (It should be something like "Oxygen OS 10.0.8.HD65AA", that's what I'm currently on). Also, is your bootloader unlocked?
Click to expand...
Click to collapse
It's "Oxygen OS 10.0.8.HD65AA" under about phone. I'm also sure my phone is already unlocked because under developer options it says "bootloader is already unlocked" (and fastboot oem unlock gives me an error saying "device already unlocked")
I'm pretty sure it's the right boot image, since I used payload dumper and made the magisk image myself from the dumped boot.img. (both preserve force encryption and perserve AVB are checked)

I have the same, maybe the payload dumper did something wrong with the boot image, or magisk patcher. Try and use this one. Is the one I created and it worked perfectly.

hectorviov said:
I have the same, maybe the payload dumper did something wrong with the boot image, or magisk patcher. Try and use this one. Is the one I created and it worked perfectly.
Click to expand...
Click to collapse
I tried your file and it still gave me a bootloop =/
that said your fastboot boot boot.img trick is really handy since now I don't have to flash my old boot.img to fix the bootloop, haha
Edit: I solved it, all I needed to do was to do a system wipe (ugh) and everything worked...

ixrs said:
I tried your file and it still gave me a bootloop =/
that said your fastboot boot boot.img trick is really handy since now I don't have to flash my old boot.img to fix the bootloop, haha
Edit: I solved it, all I needed to do was to do a system wipe (ugh) and everything worked...
Click to expand...
Click to collapse
I'm having a similar issue, but when I flash the patched boot image I created, I'm only able to reboot into bootloader and it won't boot back into Oxygen OS for me to do the next steps with the Magisk Manager.
When did you do the system wipe, before you rebooted into Android, and did you do the system wipe using TWRP or stock recovery?

I flashed the original boot.img then booted up normally. I then wiped everything. Then I set up my phone again (ugh) and flashed the patched image and it worked.

ixrs said:
I flashed the original boot.img then booted up normally. I then wiped everything. Then I set up my phone again (ugh) and flashed the patched image and it worked.
Click to expand...
Click to collapse
Thanks, just to be clear (I've done this 30 times with no success, and I'm not new to xda or rom/kernel/gapps installation, so this has me scratching my head).
When you say wiped everything, was it:
1) With TWRP from this thread (https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961)?
1.1) If with this TWRP, was it a factory reset, dalivik/cache wipe or another wipe OR
2) With original recovery
2.1) If with original recovery, was it Reset system setting, Wipe cache or Erase everything (Music, pics, etc)
You are the only one I've seen with similar issues (you were in bootloop, I'm always rebooting into bootloader) with something I haven't tried yet, so this might get me over the hump (fingers crossed)

I actually did it from within the phone (settings, system, reset, erase all data). I believe it would be equivalent to reset system setting?

ixrs said:
I actually did it from within the phone (settings, system, reset, erase all data). I believe it would be equivalent to reset system setting?
Click to expand...
Click to collapse
Thanks, was going crazy. Tried so many times, will post this to the main root guide on xda in case it helps someone else. Yay. Vanced Youtube here I come

lockekey said:
Thanks, just to be clear (I've done this 30 times with no success, and I'm not new to xda or rom/kernel/gapps installation, so this has me scratching my head).
When you say wiped everything, was it:
1) With TWRP from this thread (https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961)?
1.1) If with this TWRP, was it a factory reset, dalivik/cache wipe or another wipe OR
2) With original recovery
2.1) If with original recovery, was it Reset system setting, Wipe cache or Erase everything (Music, pics, etc)
You are the only one I've seen with similar issues (you were in bootloop, I'm always rebooting into bootloader) with something I haven't tried yet, so this might get me over the hump (fingers crossed)
Click to expand...
Click to collapse
First the OP was in a bootloop cuz he flashed but not booted the magisk_pated.img so when he tried to boot from magisk_patched it didn't work.
So you can either simply go and download the OnePlus last 1.0.8.0 fastboot ROM and extract the boot.img then flash that using the command and so you will be out of the bootloop.
Don't use the twrp!... it's been stated plenty of times that there's no working android 10 twrp for our device yet.
*start from here...*
Instead all you need to do is to download magisk 20.3
-Extract last APK from the zip
-Install apk (magisk manager)
-Inside magisk manager choose install and then choose patch IMG
-Choose the image that you got from the fastboot official rom.
-You will get the magisk_patched.img in your downloads folder
-Take that file to the pc
-Put your phone In fastboot mode
-Then cmand fastboot boot magisk_patched.img
-Phone will boot
-Open magisk manager again.
-Choose install again and you will have a new option called direct install.
-Choose that and just reboot once and done...
Now you are rooted.
It's simple.

PriPhaze said:
First the OP was in a bootloop cuz he flashed but not booted the magisk_pated.img so when he tried to boot from magisk_patched it didn't work.
So you can either simply go and download the OnePlus last 1.0.8.0 fastboot ROM and extract the boot.img then flash that using the command and so you will be out of the bootloop.
Don't use the twrp!... it's been stated plenty of times that there's no working android 10 twrp for our device yet.
*start from here...*
Instead all you need to do is to download magisk 20.3
-Extract last APK from the zip
-Install apk (magisk manager)
-Inside magisk manager choose install and then choose patch IMG
-Choose the image that you got from the fastboot official rom.
-You will get the magisk_patched.img in your downloads folder
-Take that file to the pc
-Put your phone In fastboot mode
-Then cmand fastboot boot magisk_patched.img
-Phone will boot
-Open magisk manager again.
-Choose install again and you will have a new option called direct install.
-Choose that and just reboot once and done...
Now you are rooted.
It's simple.
Click to expand...
Click to collapse
Never used TWRP. Knew it wasn't working.
Tried all three methods from the main Root thread on xda and none worked (including payload dumper to extract my boot image,etc etc).
Please see my reply above yours. I've added those details to the main Root thread in case it helps someone else.
No idea why I could only reboot into bootloader as I only updated to 10.0.8 using oxygen updater and could never Root with all the methods I found on xda.
Erasing all data fixed my issue and I am Groot.
Sent from my HD1905 using Tapatalk

lockekey said:
Never used TWRP. Knew it wasn't working.
Tried all three methods from the main Root thread on xda and none worked (including payload dumper to extract my boot image,etc etc).
Please see my reply above yours. I've added those details to the main Root thread in case it helps someone else.
No idea why I could only reboot into bootloader as I only updated to 10.0.8 using oxygen updater and could never Root with all the methods I found on xda.
Erasing all data fixed my issue and I am Groot.
Click to expand...
Click to collapse
There's no need for payload dumper..
Also you must been using a wrong version of magisk cuz there's no way to fail if you do follow the steps correctly .
All you had to do it was too restore boot.img from fastboot ROM in case you made the mistake to flash the magisk_patched.img instead of booting on it.
And that's it then you just follow the steps.
Yea obviously doing factory reset helped because it restored the boot.img but is like you decided to take the long way instead of the quick and easy way.

PriPhaze said:
There's no need for payload dumper..
Also you must been using a wrong version of magisk cuz there's no way to fail if you do follow the steps correctly .
All you had to do it was too restore boot.img from fastboot ROM in case you made the mistake to flash the magisk_patched.img instead of booting on it.
And that's it then you just follow the steps.
Yea obviously doing factory reset helped because it restored the boot.img but is like you decided to take the long way instead of the quick and easy way.
Click to expand...
Click to collapse
I had no trouble flashing the boot.img without issue to restore my access to OOS. That wasn't the issue. I used the right magisk_patched boot. That wasn't the issue (confirmed this evening when I used the same image to root successfully after I erased my data). The payload dumper method was from this guide (https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307) and if the easier 1st 2 methods worked, I wouldn't have tried the 3rd payload dumper method (which got me another version of the same original boot image that I couldn't patch and get to work).
I could never reboot to OOS to install magisk manager and complete a direct install (either after a boot or flashing of the patched image), until I erased data.
Flashing the patched image works as well, it's just another method. I highly recommend reading the above thread.
A tip, you kind of need to know what a person has tried before making suggestions, let alone telling people what they must have done wrong or that they wasted time by using the wrong method.
I highly recommend reading the above thread to learn how to respond to people without coming off as condescending and overbearing. I lot of people tried to help me there and I was very appreciative of how they tried to assist.

lockekey said:
I had no trouble flashing the boot.img without issue to restore my access to OOS. That wasn't the issue. I used the right magisk_patched boot. That wasn't the issue (confirmed this evening when I used the same image to root successfully after I erased my data). The payload dumper method was from this guide (https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307) and if the easier 1st 2 methods worked, I wouldn't have tried the 3rd payload dumper method (which got me another version of the same original boot image that I couldn't patch and get to work).
I could never reboot to OOS to install magisk manager and complete a direct install (either after a boot or flashing of the patched image), until I erased data.
Flashing the patched image works as well, it's just another method. I highly recommend reading the above thread.
A tip, you kind of need to know what a person has tried before making suggestions, let alone telling people what they must have done wrong or that they wasted time by using the wrong method.
I highly recommend reading the above thread to learn how to respond to people without coming off as condescending and overbearing. I lot of people tried to help me there and I was very appreciative of how they tried to assist.
Click to expand...
Click to collapse
No one is trying to be condescending... just pointing out facts ..
Thanks for the advice I guess?
But it doesn't really matter; these days people get offended so easily that I'm starting to consider to don't post anymore..
I mean obviously as you can see I have been here for long and lately things have changed that I can't even say anything without being called rude.
And we'll I'm glad you managed to fix your problem although the solution was a bit weird.
Seeya

PriPhaze said:
No one is trying to be condescending... just pointing out facts ..
Thanks for the advice I guess?
But it doesn't really matter; these days people get offended so easily that I'm starting to consider to don't post anymore..
I mean obviously as you can see I have been here for long and lately things have changed that I can't even say anything without being called rude.
And we'll I'm glad you managed to fix your orientation although the solution was a bit weird.
Seeya
Click to expand...
Click to collapse
You may not be trying to be condescending but you are. And you continue by calling what you say facts and ignoring anything I say.
I've been on xda a long time (since nexus 4, 2012), installing kernels, Roms, etc. I'm not a noob and try and help when I can. I've never been called rude and noone ever seemed offended by any of my posts.
I don't think I have run into anyone as rude and condescending as you on xda.
But it's not you, it's everyone else.
I didn't need your help. It was clear I had the info I was looking for and a potential solution to my issue, if you bothered reading. Not sure what point you were trying to make.
Seeya.

lockekey said:
You may not be trying to be condescending but you are. And you continue by calling what you say facts and ignoring anything I say.
I've been on xda a long time (since nexus 4, 2012), installing kernels, Roms, etc. I'm not a noob and try and help when I can. I've never been called rude and noone ever seemed offended by any of my posts.
I don't think I have run into anyone as rude and condescending as you on xda.
But it's not you, it's everyone else.
I didn't need your help. It was clear I had the info I was looking for and a potential solution to my issue, if you bothered reading. Not sure what point you were trying to make.
Seeya.
Click to expand...
Click to collapse
And there we go.. you got triggered.
Sorry but this is a forum and well is open so everyone can come and comment.
Even if you dont need anyone's help anyone can come and quote you if they want.

PriPhaze said:
And there we go.. you got triggered.
Sorry but this is a forum and well is open so everyone can come and comment.
Even if you dont need anyone's help anyone can come and quote you if they want.
Click to expand...
Click to collapse
I thought you were considering not posting anymore because everyone is so triggered.
It was never a free speech issue. It was always you being a condescending know it all issue.
Just don't cry about people being triggered when people call you what you are.
You're amazing and you know it. Don't change a thing.

Related

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

[CLOSED] Delete Thread.

Due to the disrespect of certain members here I will no longer share the tutorials.
how long does it take to move past the N/A screen. also where in this do you flash the stock boot.img if you get error 1s? please be more specific.
I should've seen this first
So... I found this thread AFTER the fact. Phone's a day old, rooted, and softbricked. I have TWRP and fastboot but kernel's gone.
You have everything there except the what if...
How'd you un-softbricked your device?
quotrice said:
how long does it take to move past the N/A screen. also where in this do you flash the stock boot.img if you get error 1s? please be more specific.
Click to expand...
Click to collapse
Hi, sorry for the late reply. Been busy tinkering with the phone.
It can take up to 30 seconds (granted, I counted out loud on reboot just now) to move past the N/A screen and go to the chick saying "hello Moto" and then the Metro PCS flash screen.
If you get the error1s the original boot.img may have either been corrupted, deleted, or the phone is being a **** and has somehow altered it where its modified, and therefore cannot start up right. With me, that happened after flashing different TWRPs and then repetitively flashing the files for root. That is why I said this:
5. Installing any of the .zip files may mess with the boot.img. I personally think unlocking the bootloader did that because I followed directions on here to a T and had problems eith Error 1 off the bat. So, if you start seeing Error 1 messages when you attempt to flash the necessary files for root in TWRP, you will have to do this step below I did.
5. Go into the Stock Rom file and extract the boot.img file. Put it in the Minimal ADB file folder (the same as you did for the recovery.img file).
-In Minimal ADB type "fastboot erase boot "
-In Minimal ADB type "fastboot flash boot boot.img" That should restore your original boot image to stock and correct any error 1 problems. And the best part is you don't have to erase and re-flash all the original stock rom files to get it back in order, potentially messing up the bootloader unlock!
Click to expand...
Click to collapse
You do not have to flash the rom unless you want to, and trust it is a pain as you have to extract all the contents of the ROM and flash them via TWRP one by one. I've updated in my original post on how to go about that. So, if the boot.img is your prob, all you have to do is extract the boot.img file from the rom and follow the instructions above. However, if you've deleted or altered more than the boot.img, you will have to flash the rom, but at this step you shouldn't of. I too had the error1 thing, and after tinkering with it for 9 hours, just flashing that boot.img on a humbug solved the problem alone. Just open it in WinRar/WinZip and pull it out, and follow the instructions above.
HmonGrL123 said:
So... I found this thread AFTER the fact. Phone's a day old, rooted, and softbricked. I have TWRP and fastboot but kernel's gone.
You have everything there except the what if...
How'd you un-softbricked your device?
Click to expand...
Click to collapse
My softbrick was the corruption of the boot.img. I was unable to get the phone to load past the N/A after that. Flashing the boot.img from the stock solved it.
If your kernel is truly gone, which please mention what guide you used to try and get root, you will have to flash stock via TWRP. And let me just say, it isn't as easy as flashing it as a ROM. You will have to extract the entire Stock Rom files to Minimal ADB Fastboot folder and flash the files one by one (refer to my updates in my original post on how to restore the stock rom).
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
Articul8Madness said:
My softbrick was the corruption of the boot.img. I was unable to get the phone to load past the N/A after that. Flashing the boot.img from the stock solved it.
If your kernel is truly gone, which please mention what guide you used to try and get root, you will have to flash stock via TWRP. And let me just say, it isn't as easy as flashing it as a ROM. You will have to extract the entire Stock Rom files to Minimal ADB Fastboot folder and flash the files one by one (refer to my updates in my original post on how to restore the stock rom).
Click to expand...
Click to collapse
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
HmonGrL123 said:
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
Click to expand...
Click to collapse
Couldn't hurt
HmonGrL123 said:
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
Click to expand...
Click to collapse
PLEASE DO!!!! As you see we all are having different problems getting the E4 on the way to root. I encourage you to make a footnote of it in this thread, and I'll direct people to it on the original post. If we can't get this down, flashing a rom is going to be a *****. :good:
Articul8Madness said:
PLEASE DO!!!! As you see we all are having different problems getting the E4 on the way to root. I encourage you to make a footnote of it in this thread, and I'll direct people to it on the original post. If we can't get this down, flashing a rom is going to be a *****. :good:
Click to expand...
Click to collapse
So don't do this yet?
mookey1986 said:
So don't do this yet?
Click to expand...
Click to collapse
@HmonGrL123 had a specific issue when flashing, as a different guide was followed first. This guide is to simplify the process.
I just wanted to add:
At step
13. Hit Install and install Magisk.zip. Afterwards, go back to main menu.
Click to expand...
Click to collapse
I ran into the error 1 problem.
After that, I powered down the phone. Then I went into fastboot and flashed the boot.img
Then I used fastboot to get back into TWRP.
Then I went back to step 13.
And Rebooted.
And I finally got root. All working.
wktra said:
I just wanted to add:
At step
I ran into the error 1 problem.
After that, I powered down the phone. Then I went into fastboot and flashed the boot.img
Then I used fastboot to get back into TWRP.
Then I went back to step 13.
And Rebooted.
And I finally got root. All working.
Click to expand...
Click to collapse
Glad you got it working. Maybe no matter what step is taken is going to initially corrupt the boot.img, so reflashing that is probably going to be essential. I'll test it out on the significant other's phone and see if that is the case.
At the step after the wipe, no matter what I do and trying 2 different versions of twrp, I cannot get the data partition to mount. I can keep clicking it over and over but the box will not check.
Been searching and googling and I cannot figure it out.
nm after sever tries it mounted
Just wanted to thank the op for this awesome guide! Rooted, did a full back up and a nandroid back up, now I'm running resurrection remix to great effect.
Sent from my XT1765 using Tapatalk
Just so you know, the reason why you (and other people in the thread) keep getting error1 when installing Magisk is because of Step 12:
"12. Hit Install and install Superuser.zip. Afterwards, go back to main menu."
Installing the superuser.zip modifies the boot.img .... then the very next step, step 13, is when Magisk will complain about the boot.img being modified. You don't need the superuser.zip at all it's redundant, flashing magisk roots the phone as well. Skip step 12, I'm fully rooted without it and you will literally never get Magisk to say the boot.img is unmodified as long as you keep modifiying the boot.img right before it.
Rooted and bootloader unlock....roming now....wish me luck
So I have officially unlocked my motoE4 on metropcs and have installed superuser. Trying to custom rom and kill the stupid metro pcs bootloader. I deoxed it and removed bloat....but can we tweak? we'll c soon working on it all nite. ill keep you posted
InFamousD147 said:
So I have officially unlocked my motoE4 on metropcs and have installed superuser. Trying to custom rom and kill the stupid metro pcs bootloader. I deoxed it and removed bloat....but can we tweak? we'll c soon working on it all nite. ill keep you posted
Click to expand...
Click to collapse
Magisk works better for root (plus you get magisk modules) and can pass safetynet.
So how long does it take for it to flash each item in twrp? I flashed the first thing (no-verity), and it's just hanging out after it shows "Done Installing!" "Updating partition details...". How long is this suppose to take?
nekomancey said:
Just wanted to thank the op for this awesome guide! Rooted, did a full back up and a nandroid back up, now I'm running resurrection remix to great effect.
Sent from my XT1765 using Tapatalk
Click to expand...
Click to collapse
You're welcome! I went through a time getting this thing to root, so I just wrote what worked on my variant. How's the resurrection remix. Looking for a good rom.
Steel Froggy said:
Just so you know, the reason why you (and other people in the thread) keep getting error1 when installing Magisk is because of Step 12:
"12. Hit Install and install Superuser.zip. Afterwards, go back to main menu."
Installing the superuser.zip modifies the boot.img .... then the very next step, step 13, is when Magisk will complain about the boot.img being modified. You don't need the superuser.zip at all it's redundant, flashing magisk roots the phone as well. Skip step 12, I'm fully rooted without it and you will literally never get Magisk to say the boot.img is unmodified as long as you keep modifiying the boot.img right before it.
Click to expand...
Click to collapse
I am only going by what worked for me with the metropcs variant. I had tried other tutorials, but there was not a definitive one that dealt with the problems of the MetroPCS trying to get root. So I can't say it's redundant when it wasn't just as simple as flashing magisk on this version of the phone for me. And granted, I went by pieces of people's tutorials, trial, and error.

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance
So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.
jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app
SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.
i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.
so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

What is the CORRECT way to gain ROOT in PDP3?

I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
AndroidDevices said:
I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
Click to expand...
Click to collapse
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
EvilDobe said:
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
Click to expand...
Click to collapse
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Tulsadiver said:
If he wants recovery, he needs to flash twrp-3.2.1-2-taimen.zip before flashing magisk 16.4
Click to expand...
Click to collapse
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
He did mention that he would want to go back because he had root and recovery.....
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
I'll take TWRP as well, wasnt sure if there was an unofficial version for P or not...
Tulsadiver said:
He did mention that he would want to go back because he had root and recovery.....
Click to expand...
Click to collapse
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Tulsadiver said:
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Click to expand...
Click to collapse
After i flash the TWRP Installer, do i reboot and change slots, or no?
EvilDobe said:
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Click to expand...
Click to collapse
I appreciate BOTH of your help, no need to get all technical!
AndroidDevices said:
After i flash the TWRP Installer, do i reboot and change slots, or no?
Click to expand...
Click to collapse
No, flash Magisk unless you want to try a custom kernel. If so, flash it before Magisk, flash Magisk, then reboot.
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Jameswebb97 said:
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Click to expand...
Click to collapse
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
all43 said:
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
Click to expand...
Click to collapse
Hey,
I was installing from P (9.0 DP3)
I installed TWRP first by flashing the image and then installing the zip file on to the phone.
Next i installed magisk, the installation all went through absolutely fine.
When i hit reboot, it goes onto the white splash screen, then brings up a small progress bar that goes across. This lasts for a minute or two, then dumps me back into TWRP.
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Tulsadiver said:
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Click to expand...
Click to collapse
Thanks, i'll give it a try again with a Factory Reset 1st...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
EvilDobe said:
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
Click to expand...
Click to collapse
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
Don't reboot, TWRP installer installs to both slots.
Flash installer, hit back button, find magisk.zip, flash it.
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
What happens when you just do this:
Get DP flashed & configured. No passwords/patterns/security features.
fastboot boot TWRP3212.img
Flash your magisk 16.4 file.
Reboot.

Magisk version

I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
kenbo111 said:
I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
Click to expand...
Click to collapse
Yup, did both updates this morning. Working fine on 21.4
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Osprey00 said:
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Click to expand...
Click to collapse
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
schwinn8 said:
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
Click to expand...
Click to collapse
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
Anyone would know better than me, but I've done it checked and unchecked without issue. I lean toward checking it when updating, not really sure why.
ldeveraux said:
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
Click to expand...
Click to collapse
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Osprey00 said:
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Click to expand...
Click to collapse
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
ldeveraux said:
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
Click to expand...
Click to collapse
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Well, I went ahead and installed it with the option unchecked. It applied and booted with no issues. Looks like it worked.
I figured leaving it unchecked makes sense, since I believe we disable dm-verity during the WTF process anyway, so we shouldn't need to touch it. I wanted to be sure before I did it myself, but it seems I didn't have to worry. Unchecked worked for me.
Osprey00 said:
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Click to expand...
Click to collapse
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
ldeveraux said:
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
Click to expand...
Click to collapse
I know, and I did the opposite. I was just speaking it out loud for the sake of discussion.
Speaking of things that should've been clear earlier, it's occurred to me that that "Preserve AVB 2.0/dm-verity" probably does exactly what it says. Remember that, until about a year ago, it was recommended to flash a "dm-verity" zip in recovery when installing a ROM. I don't remember the order, but it could've been that we were supposed to flash Magisk first and then dm-verity because Magisk erased the latter. That "preserve" option, therefore, likely allows you to flash Magisk without erasing dm-verity and having to go into recovery after to re-flash it. Now, we haven't needed to flash dm-verity for a year, so the option may not matter if you're using a ROM version that's less than a year old, though there's probably no harm in being safe and checking it. Anyways, that's my guess.
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
There's more to this -
fastboot devices
list no devices.
Reinstallation of the LG drivers didn't help.
you
przemhb said:
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
Click to expand...
Click to collapse
You need to flash the original boot image from your stock or custom ROM via the flash boot using the command "flashboot flash boot <boot_file>
Then reflash TWRP and re-install magisk. Maybe the v21.4. The latest one broke my boot too. Good luck!
You need to flash the original boot image from your stock
Click to expand...
Click to collapse
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
przemhb said:
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
Click to expand...
Click to collapse
boot.img should be good. You can always flash the other boot image if it does not boot up.
Managed to flash "boot.img", TWRP and boot to TWRP, but... got "Mount Decrypt Data Enter Password".
I haven't encrypted purposely any partition.
Furthermore TWRP locked and doesn't unlock when I try to "swipe to unlock"...
Forced reboot. Android started. Phone works, but Magisk isn't installed. Rebooted once again into TWRP and installed Magisk ignoring data decrypt message. TWRP said it failed, but after reboot Magisk Manager sees Magisk installed and so TitaniumBackup
Seems it solved the prolem.

Categories

Resources