Develop Bugs

[Q] ADB sideload with TWRP fails for 4.4.3 OTA (Nexus 7 LTE)

Hi All,
My Nexus 7 LTE is rooted with TWRP.
I've downloaded the OTA for 4.4.3 from one of the posts in the forums. It updates my razorg from KOT49H to KTU84L.
After using adb sideload, the update zip file is transferred successfully to my device, but it fails with the error message
Code:
"/system/bin/surfaceflinger" has unexpected contents.
error excuting updater binary in zip '/data/media/0/sideload.zip
Does anyone have any idea what could be causing the update to fail?
I've already restored to a stock kernel (from franco kernel) as well as uninstalled xposed framework.
Thanks!

Install stock recovery and take ota as normal. Then reinstall twrp and reroot.
If you fail update I have a backup I made with twrp you can use. Just need to extract it to your twrp backup folder and restore. It's 100% stock and was made after wiping data. Can't post a link to my Dropbox right now because of my post count but if you need it I an send it to you by other means.

Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.

endlesstrail said:
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
Click to expand...
Click to collapse
To get the OTA to work with either a stock or custom recovery the unexpected contents error will have to be fixed first. Somehow the surfaceflinger file was changed, that's a new one for me so I have no idea what could have changed it. I could upload a copy of mine if you want to try it but I do have the wifi version and don't know if they are the same. Otherwise you will need to fastboot flash the system image for the version you are running now for the update to work. Instead of doing that I would download the 4.4.3 factory image and extract the radio, system, and boot images and fastboot flash those. The bootloader did not change so that does not need to be flashed. Before flashing the images I would download the newest supersu zip and put it in your device storage, then flash the images, once that is done do not reboot, boot into recovery instead and flash the supersu zip then wipe cache and dalvik then reboot. Should take less than 15 minutes. ; )
You could also flash the factory image but that will install the stock recovery, lose root and completely wipe your device. If you are using windows you can open the flash-all.bat with a text editor like notepad and remove the -w from the text, that will prevent the userdata image from being flashed which wipes your device.

Thanks for your reply, wantabe.
I guessed as much, that if I couldn't figure out what changed the surfaceflinger, I might as well do a complete flash back to stock, which was what I did. Now it's just a matter of flashing back TWRP, restoring all the apps and waiting for 4.4.4 :good:

How to update OTA with Magisk (can I just sideload without risk of bootloops)?

So I can't remove Magisk ("stock boot.img backup does not exist") so I was wondering if it was safe to sideload the November OTA (the whole 1GB file, not sure how to do just the 60MB delta update) and I assume that removes Magisk but keeps userdata, but does that cause any issues e.g bricks or bootloops?
I'm on 8.0 October Security Patch. My main aim isn't to remove Magisk, but I guess I have to to update to the Nov patch, and then reinstall it

brpqzme said:
So I can't remove Magisk ("stock boot.img backup does not exist") so I was wondering if it was safe to sideload the November OTA (the whole 1GB file, not sure how to do just the 60MB delta update) and I assume that removes Magisk but keeps userdata, but does that cause any issues e.g bricks or bootloops?
Click to expand...
Click to collapse
First, try the
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
If that doesn't work download the appropriate Factory Image for your phone.
Go to Android 8/Oreo and do #5 to save data.

I'll give this a shot now!
Do I need to disable any Modules before flashing the ZIP? Couldn't find a definite answer searching online
Homeboy76 said:
First, try the
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
If that doesn't work down the appropriate Factory Image for your phone.
Go to Android 8/Oreo and do #5 to save data.
Click to expand...
Click to collapse

brpqzme said:
I'll give this a shot now!
Do I need to disable any Modules before flashing the ZIP? Couldn't find a definite answer searching online
Click to expand...
Click to collapse
I don't know, but I don't think it would hurt to disable the modules.
Just don't lock the bootloader.

So in case anyone else reads this -
For some reason, flashing the MAGISK UNINSTALLER ZIP caused a soft brick (device would boot only into fastboot and then "NO COMMAND", not boot into OS).
I'd already downloading the factory images from your links, so I flashed BOOT.IMG onto both slots, A and B.
Device then booted back into the OS, no data lost etc. But Magisk w
Still wouldn't accept OTA.
Flashed OTA as per the link you gave with flashall, worked fine. Will flash Magisk through TWRP next.
Thanks

brpqzme said:
So in case anyone else reads this -
For some reason, flashing the MAGISK UNINSTALLER ZIP caused a soft brick (device would boot only into fastboot and then "NO COMMAND", not boot into OS).
I'd already downloading the factory images from your links, so I flashed BOOT.IMG onto both slots, A and B.
Device then booted back into the OS, no data lost etc. But Magisk w
Still wouldn't accept OTA.
Flashed OTA as per the link you gave with flashall, worked fine. Will flash Magisk through TWRP next.
Thanks
Click to expand...
Click to collapse
Please go to the link below and post the information about the problem Magisk-uninstaller-20171123.zip caused:
[2017.11.23] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Why? So, topjohnwu can fix it or tell you why it didn't work. The link above is where I got the 'Latest Uninstaller (Support v1+)' from.
Also it would help if you add the make and model of your phone, Magisk- version you were trying to uninstall.
Flashed OTA as per the link you gave with flashall

Posting here instead of creating a new thread.
Same issue as OP except i have TWRP installed as well, so SYS.img is altered as well so i can't take OTAs. Does the factory image also contain system flash?
On the OTA page, it says make sure your device is up to date, but im on October's image and cannot move to November's. Should i flash October and let it OTA to current or safe to flash November. Thinking of just going to 8.1 beta but one step at a time.

AlPoo said:
Posting here instead of creating a new thread.
Same issue as OP except i have TWRP installed as well, so SYS.img is altered as well so i can't take OTAs. Does the factory image also contain system flash?
On the OTA page, it says make sure your device is up to date, but im on October's image and cannot move to November's. Should i flash October and let it OTA to current or safe to flash November. Thinking of just going to 8.1 beta but one step at a time.
Click to expand...
Click to collapse
When you go to settings System Updates can you update?
If not Download the appropriate (October 2017) Factory Image for your phone.
Go to Android 8/Oreo and do #5 to SAVE data or #4 to WIPE data.
This will remove root and you should get the OTA.

how to update without losing root?

I'm using stock oos and root with magisk
Everytime I get an ota it removes root.
Does anyone have any ideas

It happens because if you choose to update over System Settings it somehow knows that your phone is rooted / has an unlocked BL.
Therefore, Oneplus only offers the full Image. There is a way to inspect this full Image.
The way I'm doing it whenever I'm updating is:
download the newest FW over PC, inspect zip... delete something that says "recovery" on it.
Because that is the one, that will return you to stock recovery, instead of keeping TWRP installed.
After flashing that zip; TWRP should still be available for you, from there you can re-flash the magisk zip and you should all be rooted then.

moeq123 said:
It happens because if you choose to update over System Settings it somehow knows that your phone is rooted / has an unlocked BL.
Therefore, Oneplus only offers the full Image. There is a way to inspect this full Image.
The way I'm doing it whenever I'm updating is:
download the newest FW over PC, inspect zip... delete something that says "recovery" on it.
Because that is the one, that will return you to stock recovery, instead of keeping TWRP installed.
After flashing that zip; TWRP should still be available for you, from there you can re-flash the magisk zip and you should all be rooted then.
Click to expand...
Click to collapse
After that do you only loose root? Is your data, apps, customizations still there? Other than magisk root what else got deleted? Please answer i wanna do it your way.
Also where do you download FW file?

nadiration said:
After that do you only loose root? Is your data, apps, customizations still there? Other than magisk root what else got deleted? Please answer i wanna do it your way.
Also where do you download FW file?
Click to expand...
Click to collapse
Firmwares should be available on manufactures site.
For Oneplus 5T it should be that link: https://downloads.oneplus.com/devices/oneplus-5t/
Honestly, I can't tell what's inside These files; as I don't have one of them at Hand; and I'm not allowed to download and open such files here at work.
If you want I can expect them later after work (4 hours or something) or you download one and post me the Folder tree as a text here.
I know, that if you remove this one recovery file/Folder/entry that it passes the flashing of the recovery Partition.
If I recall correctly (from my Knowledge of devices and roms other than op5t) inside of These downloaded firmwares there should be a file called "Image.zip"
inside that Image.zip there should be Folders or files like "boot", "recovery" "system Images", and "userdata".
Delete recovery and userdata, repack it to "Image.zip" and repack that zip to the previously downloaded zip...
flashing that pack should prevent you from your data being wiped.
I don't know if magisk will work without flashing magisk.zip over.
Before you do all that stuff, back up your data, try it, and please - let us know if that has worked.
[Edit]: TL;DR - In the end, it just wipes your data and installs another recovery because it has been told to do so inside of these Firmware Images.
Download that Firmware, inspect everything, and delete stuff that tells him to do stuff that you don't like.

[ROM/FW][STOCK]LG V30 (Joan) T-Mobile H932 20r TWRP flashable firmware (incl. ROM)

LG V30 T-Mobile H932 20r ROM​
For U.S. T-mobile H932 ONLY. Do NOT install this on any other V30/V30+/V30S except U.S. T-mobile H932. You will brick your phone.
DISCLAIMER : I do not hold responsiblity for any of the following but not limited to : Bricks due to not reading, nuclear war, cat dying. I will not be held responsible for any damage of any kind due to the result of this zip. It is held under your own risk. This does not mean that i wont help in any way shape or form to recover from anything that may happen at the result of flashing this zip. PLEASE FLASH RESPONSIBLY! PS. This zip has NOT been tested by me!​
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20r firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Added DTS build prop
Added all lockscreen weather animations build prop
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
H93220r.zip [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20r firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20r zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)​
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2019-1-1
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...

#RESERVED
Please to anyone who had issues with the zip.....
We have a fix!
Flash this zip
https://www.androidfilehost.com/?fid=1395089523397908552
Then flash a rom from your SD CARD
ONLY FLASH THIS OF YOU HAD A BRICK FROM 20R!!

Zip is live! Enjoy!

your zip name is wrong.. should be h93220r* ( it doesnt matter but i was confused at first)
also, i flashed it and nothing happened. my system is still the same as i was before (20p)
and in the script, i think it says 'model=VS996' or something. since it just words, it may not matter.
but maybe you used the wrong script for h932
In any case, the zip did nothing for me. flashing only took about 10 secs in total, and flashing system barely took a second.

So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work

JohnFawkes said:
So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work
Click to expand...
Click to collapse
Did you remove the file?
Sent from my LG-H932 using XDA Labs

BROKEN1981 said:
Did you remove the file?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour

JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
Ahh ok, thought I was missing something.
Sent from my LG-H932 using XDA Labs

JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
looking forward to the fix.

I figured people might want these files.
Root-System-Media

Uploading new zip now! figured out all issues

JohnFawkes said:
Uploading new zip now! figured out all issues
Click to expand...
Click to collapse
Awesome thank you!
Sent from my LG-H932 using XDA Labs

BROKEN1981 said:
Awesome thank you!
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
no problem. should be live in about 15 minutes

zip is live!

Awesome. Woke up this morning to the system update notification. Glad there are still T-Mobile users around here that works to get this stuff out. Downloading now. Will report back after I flash it.
---------- Post added at 07:43 AM ---------- Previous post was at 07:19 AM ----------
BROKEN1981 said:
I figured people might want these files.
Root-System-Media
Click to expand...
Click to collapse
Are these new in this update?

JohnFawkes said:
zip is live!
Click to expand...
Click to collapse
At the end of the flash it looks like it flashed fine but then it tells me it failed to mount everything. When I go to reboot into the system it tells me there is no OS. I was just going to flash the 20p zip I had but then it restarted and now I can't get into TWRP again. Now it just restarts into fastboot mode
UPDATE: I was able to get back into TWRP by going through the factory reset option (Volume down + Power, etc.) I'm now flashing the 20p zip I have.
UPDATE 2: Didn't work. Got into a bootloop. Restoring an old Lineage backup I have. Should have made a backup of my current state before flashing but I wasn't thinking
UPDATE 3: That didn't work either. Everything I flash it tells me failed to mount '/persist-lg' and just boot loops. I guess the next thing to do is try and use LGUP to restore

Same here as above. Doesnt mount system persist cache.

sunmybun said:
Same here as above. Doesnt mount system persist cache.
Click to expand...
Click to collapse
Flashing anything else doesn't fix it either. My phone is chillin' in recovery mode until I can figure it out

im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on

JohnFawkes said:
im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on
Click to expand...
Click to collapse
Thanks. Searching around, I see there have been people having issues like this before with other devices. Something to do with the persist.img. Did the last zip include one? Also, I hope whatever it is can be fixed with a new zip. I don't know why restoring a backup or flashing an old full stock zip wouldn't fix anything.
This is basically what I'm getting
http://en.miui.com/thread-467490-1-1.html

Bootloop after flashing magisk_patched.img

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.