Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse
Related
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
MColbath said:
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
Click to expand...
Click to collapse
Do you still have root? What was the error?
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
MColbath said:
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you outline the exact steps you are doing to flash?
mdamaged said:
Can you outline the exact steps you are doing to flash?
Click to expand...
Click to collapse
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
MColbath said:
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
Click to expand...
Click to collapse
In the process of resetting back to factory, did it relock your bootloader? I ask only because some tools do this automatically. I had to ask.
mdamaged said:
In the process of resetting back to factory, did it relock you bootloader? I ask only because some tools do this automatically. I had to ask.
Click to expand...
Click to collapse
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
MColbath said:
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
Click to expand...
Click to collapse
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it (a suggestion to use goo was here, but forget that).
If you can boot into twrp using the above suggestion, you can at least root and get some stuff done while waiting for a fix or update or someone more knowledgeable than I to solve your issue.
The only thing I can think of is that the bootloader changed and we are back to where you started, waiting for them to update it for your bootloader.
mdamaged said:
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it and try using...goo manager (never used this myself heard some good, some bad things, about it YMMV etc etc).
Click to expand...
Click to collapse
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
MColbath said:
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
Click to expand...
Click to collapse
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Okay seems good.
mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
MColbath said:
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
Click to expand...
Click to collapse
No problem, thanks for the update.
mdamaged said:
No problem, thanks for the update.
Click to expand...
Click to collapse
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
MColbath said:
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
Click to expand...
Click to collapse
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or location or added a new one (with a diff name) or did something with the permissions so it could not be renamed, and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
mdamaged said:
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or added a new one (with a diff name), and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
Click to expand...
Click to collapse
Yeah there are new backup files all over the place in System partition.
MColbath said:
Yeah there are new backup files all over the place in System partition.
Click to expand...
Click to collapse
Stupid providers.
mdamaged said:
Stupid providers.
Click to expand...
Click to collapse
I'm checking the developer block section of recovery right now.
I'll upload the log for the recovery too. Hold on.
Here it is.
MColbath said:
Here it is.
Click to expand...
Click to collapse
Is there a file in /system named recovery-from-boot.p?
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
You need to decrypt the phone for it to work.
Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.
pkadavid said:
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.
Click to expand...
Click to collapse
I had no issues obtaining root with the new twrp on an encrypted phone.
Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.
legendarren said:
Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.
Click to expand...
Click to collapse
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks, man. But still TWRP still doesn't stick after system reboot.
legendarren said:
Thanks, man. But still TWRP still doesn't stick after system reboot.
Click to expand...
Click to collapse
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?
Vanschtezla said:
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?
Click to expand...
Click to collapse
Yes, I forgot about decrypting. It works fine now, thanks!!
legendarren said:
Yes, I forgot about decrypting. It works fine now, thanks!!
Click to expand...
Click to collapse
No problem mate ??
Vanschtezla said:
No problem mate ??
Click to expand...
Click to collapse
Which boot IMG did you use to decrypt the final release of n?
kevtrysmoddin said:
Which boot IMG did you use to decrypt the final release of n?
Click to expand...
Click to collapse
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.
Vanschtezla said:
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.
Click to expand...
Click to collapse
No probs
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Just installed twrp and seeing if flashign super su stuck or not... Have to wait for modified boot images to decrypt, though
---------- Post added at 10:25 AM ---------- Previous post was at 10:14 AM ----------
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Update-phone is decrypted after installing twrp, wiping userdate, rebooting twrp, flashing latest super su, rebooting
eggman618 said:
Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.
Click to expand...
Click to collapse
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.
eggman618 said:
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.
Click to expand...
Click to collapse
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.
pkadavid said:
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.
Click to expand...
Click to collapse
If you root using phh's superuser and magisk, TWRP will stick. His solution also allows you to use Android Pay with root, albeit with a little hoop-jumping
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I had the twrp not sticking issue in the past. What has worked is to boot twrp, not flash it, then flash SU. Then boot back into the bootloader and flash twrp.
Sent from my Nexus 9 using XDA-Developers mobile app
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
rendez2k said:
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
Click to expand...
Click to collapse
If your phone boots back to bootloader on reboot, you did something wrong. Reflash system imgs and start over.
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
rendez2k said:
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
Click to expand...
Click to collapse
Yes. If you don't want your data wiped, open the install.bat file and take off the -w.
Did you unlock your bootloader correctly? Unlock critical? I believe the pixel 2 xl is the only phone where that has to be done.
Boot into bootloader and fastboot flash recovery.img again, once your in recovery, flash the recovery.zip from your storage again, then reboot recovery.... its happened to me, usually when I switch slots, all I have to do is reflash recovery.
Also note, If I am trying to boot at that point (rather than flash a ROM), I usually just flash the kernel and magisk and I'm good to go.
Thanks all! I flashed the patched boot.img again and it seems to be working OK
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
rendez2k said:
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
Click to expand...
Click to collapse
Yes you do loose twrp after flashing the boot.img. the reason being that stock recovery resides in the boot.img. So when you flash it, bye..bye twrp! Why not just fastboot twrp, then once in twrp, flash the twrp installer zip, then flash your custom kernel(if used) then flash the magisk zip for root. :good:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
rendez2k said:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
Click to expand...
Click to collapse
No. Flash kernel is just the kernel, the boot.img is from the factory image. Flash the zip version of Flash kernel in twrp, then flash magisk.zip :good:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
DON'T DO THAT! You'll bootloop for sure!! Do what the post below says, and what I told you earlier!
Pyr0x64 said:
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
Click to expand...
Click to collapse
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
rendez2k said:
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
Click to expand...
Click to collapse
There is no solution for that. Xposed always fails SafetyNet.
Is Xposed worth having these days? Are people still actively developing useful mods?
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I think it's worth it, for the following apps:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Fuse8499 said:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Click to expand...
Click to collapse
No problems with TWRP here. Maybe you are flashing to the wrong slot.
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I keep hoping Xposed will go die in a fire. It causes more problems than it solves, to the point ROM developers will tell you not to bother reporting issues with it installed. Rovo knows his stuff, but his creation has caused more damage to custom ROM development than Cyanogenmod did in its last three years.
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
From what I understand you can not do ADB in TWRP to install an update. What I did was download the factory images, remove -w from the flash all.bat. flashed the images and let the phone boot normally. Once I knew it was running I went to the bootloader and booted TWRP temporarily. Once that was up I flashed Magisk and then my kernel
I don't install TWRP anymore.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
DarkPhoenix said:
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
Click to expand...
Click to collapse
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
cmh714 said:
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
Click to expand...
Click to collapse
Doesn't installing TWRP remove Android Recovery?
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
hmm, since I dont install TWRP anymore, you may be correct....still cant hurt to try
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
Yes it does. TWRP replaces the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
v12xke said:
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
Click to expand...
Click to collapse
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
DarkPhoenix said:
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
Click to expand...
Click to collapse
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
v12xke said:
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
Click to expand...
Click to collapse
I was updating so I could install Bootleggers rom so updating should be a lot easier lol.
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!
Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?
posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.
thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.
thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.
Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you