Related
Hi - I've read through almost every thread in this forum and, unless I am missing something - quite possible - I don't think that anybody has mentioned this problem.
I have a bootloader unlocked Boost Moto E4 and I can flash Squid's TWRP (I do get the "Image not signed or corrupt" message) and can boot from the bootloader after the flash into TWRP recovery. However, after I boot into the OS, the TWRP recovery gets overwritten with the stock recovery. Has anybody else bumped into this? Is there a step that I am missing somewhere to make TWRP permanent?
Thanks
D.
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
Your problem is the stock rom flashing the stock recovery when you reboot. If you flash twrp then reboot recovery once before booting the os, it should change a file in /system recovery-from-boot.p to recovery-from-boot.p.bak which will stop the stock recovery flash. You can also mount /system in twrp and use the file manager to change it manually.
D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Francesco Franz said:
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Click to expand...
Click to collapse
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Sent from my Moto E (4) using XDA Labs
amarc78 said:
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Click to expand...
Click to collapse
than do this flash over default recovery and do reboot. twrp recovery removed from recovery partition on next boot.
also do this flash twrp and do allow modifications. your device ain't gonna boot. if you didn't flash no verity thing.
rooting will make it permanent. it's the same case in both marshmallow and nougat too as OP states his problem in first post.
it will permanent by doing this
fastboot erase recovery (remove default recovery from recovery partition)
than install custom recovery. it will be there no matter if your device is rooted or not.
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
D97 said:
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
Click to expand...
Click to collapse
which step actually help you?
DE SEXIEST said:
which step actually help you?
Click to expand...
Click to collapse
Whatever you do don't run "fastbootboot erase" anything unless you know for sure what by you're doing or you can screw up your partitions. I have flashed twrp many times with only running "fastboot flash recovery...", then flashing one of numerous zips to disable dmverity and forced encryption. As long as you have the option in twrp under " mount" that says "mount system read only" not checked and you may need to reboot twrp afterwards, twrp should stick. Flashing Magisk directly after the stock rom should also solve your problem and disable dmverity.
I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?
+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)
+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?
GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
ledvedder said:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
Click to expand...
Click to collapse
Same happened to me a few days ago and had to reflash full rom. PC still recognized device so I placed os on root of device and flashed. Unfortunately it wiped the device but at least it worked.
PapaMag said:
Same happened to me a few days ago and had to reflash full rom. PC still recognized device so I placed os on root of device and flashed. Unfortunately it wiped the device but at least it worked.
Click to expand...
Click to collapse
So you had to wipe everything?
ledvedder said:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
Click to expand...
Click to collapse
I don't recommend updating that way. For me I flashed a patched boot.img from TWRP and it worked.
ledvedder said:
So you had to wipe everything?
Click to expand...
Click to collapse
When I flashed 9.0.11 again it wiped the device yes.
_Masked_ said:
I don't recommend updating that way. For me I flashed a patched boot.img from TWRP and it worked.
Click to expand...
Click to collapse
Obviously you are smarter than me. Thanks for the tip
PapaMag said:
Obviously you are smarter than me. Thanks for the tip
Click to expand...
Click to collapse
No problem, happy to help. By patched boot.img I mean the boot.img that was patched by Magisk.
_Masked_ said:
No problem, happy to help. By patched boot.img I mean the boot.img that was patched by Magisk.
Click to expand...
Click to collapse
Where can I get that boot.img file?
Sent from my ONEPLUS A6013 using Tapatalk
ledvedder said:
Where can I get that boot.img file?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
The stock boot.img file is extracted from OOS and the patched boot.img is after you patch it via Magisk.
_Masked_ said:
The stock boot.img file is extracted from OOS and the patched boot.img is after you patch it via Magisk.
Click to expand...
Click to collapse
How do I extract it?
Sent from my ONEPLUS A6013 using Tapatalk
Use this if you're on OOS 9.0.5/9.0.6/9.0.7, but if you are on a higher OOS then you need to grab your stock boot.img for 9.0.10 from here and 9.0.11 from here, and patch it yourself using the instructions below.
Connect your phone to your PC using the OnePlus Cable
Reboot to Bootloader using "adb reboot bootloader" on PC while your phone is in TWRP
Rename stock boot .img file to boot.img on PC
Use "fastboot boot boot.img" on PC while your phone is in Fastboot Mode / Bootloader
Follow this guide once you are done with the above steps to root your phone with Magisk and actually boot.
I am in the same situation.
1) Got the phone. Unlocked with out-of-the-box firmware. Put TWRP on it, Magisk. All worked like a dream.
2) Time passed, I tried to play Fortnite a bit, which kicked me out due to root. Had to use Magisk Canary. Still, NO issues, all superb!
3) New firmware. The December one. Kept postponing it, but after like 2 weeks, I was like, meh, why not. Big mistake.
From this point on, I cannot root no matter what I try. As soon as I flash Magisk, it will keep booting back to TWRP.
I have even tried to grab the Canary ZIP to flash. Nothing. Tried flashing back the full base update file from OnePlus, then root. Nothing.
It's like an endless loop.
To be fair, I only use root / magisk because I need call recording. Sadly, it's been killed in Android 9, but OnePlus has a hidden feature for this. Unfortunately you have to use either ADB on each boot, or use Magisk to enable it and save you time, hassle.
Anyone has any idea, shoot.
This is a 100% unbranded, OnePlus-store-bought 8GB/128GB 6T model.
Ps.: IF you ever get stuck in this loop - you can boot your phone by using the original "boot.img".
You can grab it here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
To boot it, simply:
1) Enter Bootloader where you can use fastboot (NOT TWRP!).
2) Use `fastboot boot boot.img`
3) Your phone now will boot up.
h8Aramex said:
I am in the same situation.
1) Got the phone. Unlocked with out-of-the-box firmware. Put TWRP on it, Magisk. All worked like a dream.
2) Time passed, I tried to play Fortnite a bit, which kicked me out due to root. Had to use Magisk Canary. Still, NO issues, all superb!
3) New firmware. The December one. Kept postponing it, but after like 2 weeks, I was like, meh, why not. Big mistake.
From this point on, I cannot root no matter what I try. As soon as I flash Magisk, it will keep booting back to TWRP.
I have even tried to grab the Canary ZIP to flash. Nothing. Tried flashing back the full base update file from OnePlus, then root. Nothing.
It's like an endless loop.
To be fair, I only use root / magisk because I need call recording. Sadly, it's been killed in Android 9, but OnePlus has a hidden feature for this. Unfortunately you have to use either ADB on each boot, or use Magisk to enable it and save you time, hassle.
Anyone has any idea, shoot.
This is a 100% unbranded, OnePlus-store-bought 8GB/128GB 6T model.
Ps.: IF you ever get stuck in this loop - you can boot your phone by using the original "boot.img".
You can grab it here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
To boot it, simply:
1) Enter Bootloader where you can use fastboot (NOT TWRP!).
2) Use `fastboot boot boot.img`
3) Your phone now will boot up.
Click to expand...
Click to collapse
Try this.
ledvedder said:
How do I extract it?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Plug your phone into your PC
Use this command in TWRP's Terminal and type this:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=boot.img
Copy it from your phone to your PC (in the directory your command prompt is in) and use the command:
Code:
fastboot boot boot.img
TWRP doesn't work
Hi there,
Just like you I have installed twrp-3.2.3-x_blu_spark_v9.86_op6 TWRP recovery on my phone to flash custom ROM (as recommneded by this ROMs list), however, it doesn't work. Like, no matter whether you I to flash unofficial or official custom ROM, it says that 'Something isn't right'. I think there's some problem within this recovery. Hoping for good.
dgdeepak000 said:
Hi there,
Just like you I have installed twrp-3.2.3-x_blu_spark_v9.86_op6 TWRP recovery on my phone to flash custom ROM (as recommneded by this ROMs list), however, it doesn't work. Like, no matter whether you I to flash unofficial or official custom ROM, it says that 'Something isn't right'. I think there's some problem within this recovery. Hoping for good.
Click to expand...
Click to collapse
Flash the CORRECT one, for the OnePlus 6T. Not for the OnePlus 6.
Anyone have a resolution for this? I have searched, but can't find an answer.
you could reset your network in settings/system
ecompton59 said:
you could reset your network in settings/system
Click to expand...
Click to collapse
Sorry I should have done a better job clarifying. It WiFi does not turn on, on my phone with Magisk installed. It does with it removed. The icon goes through the process but never turns on.
jivy26 said:
Sorry I should have done a better job clarifying. It WiFi does not turn on, on my phone with Magisk installed. It does with it removed. The icon goes through the process but never turns on.
Click to expand...
Click to collapse
TWRP is the culprit, reflash the factory rom and it will work.
qbanlinxx said:
TWRP is the culprit, reflash the factory rom and it will work.
Click to expand...
Click to collapse
Dirty flash of the rom fixed it thank you
jivy26 said:
Dirty flash of the rom fixed it thank you
Click to expand...
Click to collapse
Did you flash it through TWRP or stock installer?
Thanks
bigjailerman said:
Did you flash it through TWRP or sick installer?
Thanks
Click to expand...
Click to collapse
Twrp but what he recommends hear overwrites my rom removing magisk. When I reflash magisk it's the same issue.
I'll look into sick installer.
Dont know the exact reason but custom kernal installation fixing it.
I fixed it by running the update through the local upgrade again. It fixed it after one local upgrade with standard magisk upgrade steps.
jivy26 said:
Twrp but what he recommends hear overwrites my rom removing magisk. When I reflash magisk it's the same issue.
I'll look into sick installer.
Click to expand...
Click to collapse
What Magisk version you use?
look this https://forum.xda-developers.com/on...nofficial-twrp-touch-recovery-t3860815/page24
Flash you're boot img after twrp.
Mervingio said:
What Magisk version you use?
look this https://forum.xda-developers.com/on...nofficial-twrp-touch-recovery-t3860815/page24
Click to expand...
Click to collapse
10.1 flashing a custom kernel then Magisk and I have no WiFi issues. It is some conflict with standard OnePlus 6t kernel.
https://forum.xda-developers.com/oneplus-6t/how-to/ultimateguide-t4004367
Take a look at this...
Payload dumper
You have to use payload dumper. Extract Payload dumper after You downloaded it in a folder. Download the lastest 6t Stock Android zip file 10.0.1, extract it and take out the payload.bin file,
put it in the input folder of payload dumper and start payload dumper. Wait some time. Now in the Output folder take out the boot.img and send it trough Your phone, install Magisk in Your phone. It is still uninstalled now and it will remain unistalled now. Tap on install where Magisk is uninstalled and still Red, again tap on install and choose patch a file, it will open Your Filemanager on Your phone, choose the destination of Your boot.img. and tap on Your boot.img file.
Now magisk will flash it. After that look in Your download folder, there You will find the file magisk_patched.img, save it on Your PC. Start Your phone in to the fastboot mode and flash in minimal-adb-or-fastboot the magisk_patched.img.
You have to write fastboot flash boot. Now drag and drop the magisk_patched.img in to the window, so it will look like this:
fastboot flash boot "C:\Users\(Your Username)\Downloads\magisk_patched.img"
Hit enter, just some seconds and it is done. Now write fastboot reboot and hit enter. The phone reboots and Wifi also appears and the sound is working. You have to do it again when the next update appears. Maybe Android Oxygen OS 10.0.2
I am wondering about the next updates from android 11 (R), 12 (S), 13 (T). If it will work the same till Fuchsia OS is coming out and we will say good bye to Android and maybe goodbye to custom ROMs.
But PC Games on the Phone would be a tasty thing because Fuchsia OS is supporting APKs and EXEs too.
Have Fun.
KitsuneUK said:
I fixed it by running the update through the local upgrade again. It fixed it after one local upgrade with standard magisk upgrade steps.
Click to expand...
Click to collapse
Did you have to go all the steps again...?
full rom through local updater dont reboot
flash twrp installer dont reboot
flash magisk on inactive sloth through magisk manager
or did you just flash the rom through updater and reboot?
Thanks
bigjailerman said:
Did you have to go all the steps again...?
full rom through local updater dont reboot
flash twrp installer dont reboot
flash magisk on inactive sloth through magisk manager
or did you just flash the rom through updater and reboot?
Thanks
Click to expand...
Click to collapse
I ran through the standard upgrade process for root.
Uninstall Magisk and restore original images
update through settings > local upgrade with the full ota zip
install magisk to inactive slot. That keeps magisk installed and should let you reinstall the update.
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.
MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.
Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?
Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches
What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.
It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.
h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541