Related
Hello, I'm still a noob trying to learn, so far with help of this forum I've learned to unlock and root my first android phone, now I'm trying to learn how to properly keep my device updated!
Can someone please give a little rundown to what are the correct steps to update OTA on a rooted twrp device?
I've been browsing the forums a lot but I seem to find a lot of different approaches, or too vague instructions.
It would be greatly appreciated if someone could help me out, step by step, and explain the steps with the commands I need to put in, if there are any.
Thank you
download the ota from here
place it on your phone
go to update on you phone then hit the cog and hit local update
let it up date
reboot to boot loader
fastboot twrp img again
then flash the installer
reboot recovery
then it will boot back in to recovery again
flash root
job done
Hello,
To save you having to fastboot boot TWRP, do the following:
Save the following files to your SDCard:
OTA.zip
Magisk.zip
TWRP.zip
Boot into TWRP
Flash OTA.zip first, then TWRP.zip straight after, then Magisk.zip straight after that, reboot.
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
Sorry yes, put the installer zip on the sdcard
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
i just download and install the OTA through system updates. Then boot to Trwp recovery and flash magisk . Profit
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide
to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You can flash the installer zip for TWRP through TWRP itself.
Doesn't installing OTA through system settings wipe TWRP? That's why I perform all my updates from TWRP directly.
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You have to do twrp/root again after updates. Unlock sticks, but twrp and root don't.
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Ajaykumar21066 said:
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Click to expand...
Click to collapse
It prob doesn't overwrite until u reboot so twrp may not have been overwritten on that partition yet, so would make sense, I need to try it out sometime
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Swatto is correct. The risk when using twrp is that you must reboot to recovery immediately after flashing the twrp installer zip, or you will boot to the old slot and things will be broken. Rebooting to recovery gets you onto the active, updated slot.
When you reboot to recovery and flash an OTA, you are flashing it to the other slot. The current slot is untouched, while the new active one is completely stock. The twrp installer zip flashes twrp to both slots.
This is the procedure to follow if you want to update via twrp. Personally, I prefer taking the OTA and reinstalling via fastboot just to make sure everything is clean.
lollyjay said:
I have personally tested the following with TWRP already installed and twrp-installer-enchilada-3.2.1-0.zip on your phone:
Download full (not incremental) OOS ROM to your phone and check MD5
Reboot to your installed TWRP
Install the OOS ROM
Do not reboot instead stay in TWRP
Install twrp-installer-enchilada-3.2.1-0.zip
Reboot Recovery
Wipe cache
Reboot System
Click to expand...
Click to collapse
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Thank you
DampDeceiver said:
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Click to expand...
Click to collapse
I have not tried that method as I want twrp, but that is the recommended approach.
I know things have changed with twrp, but it's not that hard once you get used to it. You just have to remember that your phone will switch active slots every time it gets an update or you flash an ota (for example, to go back to stock), so twrp, etc, have to be installed on the other slot before you boot to it. Once you get comfortable with that idea, the rest of it is pretty easy.
Well, I am glad to read this post. Its always interesting how things can be slightly different in every phone manufacturer's setup.
After my lady Huawei device (Honor 6x), I did not want to have to deal with their style of... Control over their devices.
And things seem much easier here, while also being a little confusing right now. I don't fully get the slot a/b stuff yet but it sounds like it's a system to ensure stability on the phone in cases where the newest update could install incorrectly the alternative slot has a backup to ensure the device will function.
Sorta sounds like the dual bios setup on some motherboards. It's good!
Right, so to summarise to ensure I got it right:
1) Downloaded large (1gb+) ota zip from one of these threads, official twrp recovery installing zip, new version of magisk recovery installing zip
2) in recovery install all 3 of those zips in that listed order
3) reboot to recovery again to ensure twrp is still installed
4) profit
Which twrp thread should I take the zip from? There are a few different threads. I shouldn't care about the fastboot version when I already have twrp installed, right?
Either way, it can be much easier than what I had to do on Huawei phones. (currently the easiest phone I used for customisation like this was Nexus 4, but gladly OP6 is getting pretty close to that same level).
Sent from my OnePlus 6 using XDA Labs
You're best off downloading from the official twrp site. If you already have it installed, no need to use the fastboot boot method. You should to reboot to recovery in between flashing twrp and magisk to be sure magisk gets installed on the active slot.
Swatto86 said:
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Click to expand...
Click to collapse
Question, more of a scenario really. So if I'm on slot A and have TWRP and Magisk installed, would it be alright to just do a local update and reboot, giving me a perfectly clean install in slot B? Does it work that way? Thanks!
I'm actually using a 6t, but worst case scenario I just use the MSM Download tool, still I wanna get the hang of these confusing A/B devices.
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
raptax said:
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
Click to expand...
Click to collapse
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
Exactly! I'm glad to had help you sometimes if something is done wrong TWRP is dangerous
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
If you wipe system, then flash oos ROM, TWRP will think there is no os. You can just ignore and boot.
Wiping system then flashing any time will make twrp display "no os installed" it does this because it hasn't created files for twrp to check if you have a ton installed. Flashing twrp then rebooting to twrp fixes it.
Reboot to stock recovery?
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
5xonlineage said:
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
Click to expand...
Click to collapse
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Fastboot method?
°Washy said:
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Click to expand...
Click to collapse
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
Do you solve, man?
Fastboot ROM
°Washy said:
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
Click to expand...
Click to collapse
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
5xonlineage said:
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
Click to expand...
Click to collapse
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Magisk, boot img?
°Washy said:
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Click to expand...
Click to collapse
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
5xonlineage said:
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
Click to expand...
Click to collapse
No. Just flash stock boot image if magisk broke something.
Rooted
°Washy said:
No. Just flash stock boot image if magisk broke something.
Click to expand...
Click to collapse
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
5xonlineage said:
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
Click to expand...
Click to collapse
I followed that thread for the first A10 release cause there wasn't a worked twrp yet. You are welcome man, when I feel myself usefull I always try to help.
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
madhattr999 said:
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
Click to expand...
Click to collapse
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
For your other questions, if you extract the factory image you'll find another zip file in there. That's were the image files are and you need to extract that zip. And, ota's are cumulative so you don't need install previous ones. But specifically to the boot image, a previous months boot image may or may not be the same as the current one, etc.
jd1639 said:
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
Click to expand...
Click to collapse
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Devices with A/B Partitions
Due to the fact that these devices have two separate partitions, it is possible to have the OTA installed to the inactive slot and have Magisk Manager to install Magisk onto the updated partition. The out-of-the-box OTA installation works seamlessly and Magisk can be preserved after the installation.
After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Update).
Wait for the installation to be fully done (both step 1 and step 2 of the OTA), do not press the restart button!! Instead, go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk to the slot that the OTA engine just updated.
After installation is done, press the reboot button in Magisk Manager. Under-the-hood Magisk Manager forces your device to switch to the updated slot, bypassing any possible post-OTA verifications.
After the reboot, your device should be fully updated, and most importantly, Magisk is still installed to the updated system!
Click to expand...
Click to collapse
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
jd1639 said:
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
Click to expand...
Click to collapse
Thanks, I'll back up my files and try that.
Well, as far as I know twrp backups only work for data (with verity and all that). Always bootloop on a vendor or system restore. Back up your data a million times and go for it. Worse thing that happens is back to zero. Wait, you said no computer? Well, put it on a free cloud saving service, have your data backed up out there. Not advertizing for any service in particular, but backing up data is something everyone should be thinking about.
I am about to go for broke on this device for the 4th time. Non boot several times, flashing, flashing, building, flashing. I have the added benefit of figuring out if cell service works as the vendor.img always breaks it. Good times mate.
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
fronten said:
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
Click to expand...
Click to collapse
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Badger50 said:
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Click to expand...
Click to collapse
But the person above you said he was able to do it on both recent updates...
madhattr999 said:
But the person above you said he was able to do it on both recent updates...
Click to expand...
Click to collapse
He doesn't have twrp and if you do have twrp the ota won't work for sure. So you're welcome to try if you're only rooted, no twrp. But patching the boot image and installing it from magisk hasn't worked, but maybe it does now. Let us know.
dracushor87 said:
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
Click to expand...
Click to collapse
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
madhattr999 said:
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
Click to expand...
Click to collapse
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
timg11 said:
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
Click to expand...
Click to collapse
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
dracushor87 said:
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
Click to expand...
Click to collapse
Used this method after the May update finally arrived for me yesterday. Backed up everything just in case, but it worked flawlessly.
Hi all,
last week I received my new OnePlus 7 and I started playing with it and I'm having a problem. I unlocked it straight away, I installed TWRP and Magisk and all was great.
Then I noticed I coulnd't enter TWRP anymore to take a full backup. I tried everything I found on the net, Volume Up+Pwr, Volume Down+Pwr, Adb and so on but nothing. So I ran TWRP from fastboot and... I f****ed my partition. Some more reasearch and I managed to have the phone back but lost the data of the past week. Why TWRP doesn't start anymore but I only see the stock recovery?
Playing some more I made that happen again and here is what I discovered:
Phone: OnePlus 7 GM1903
OS: Oxygen 9.5.8.GM57AA
TWRP: twrp-3.3.1-1-guacamoleb.img (from https://twrp.me/oneplus/oneplus7.html)
Magisk: problem started with v19.1 but repeated itself with v20.0
UPDATE: I've found someone else with the same problem https://github.com/topjohnwu/Magisk/issues/1920
1) Start with factory defaults
2) Install TWRP via adb
3) Install Magisk via TWRP
4) Try to enter TWRP from recovery but boots to stock recovery
Can anyone help me? The feature I need the most is a full system backup
ColOfAbRiX said:
Hi all,
last week I received my new OnePlus 7 and I started playing with it and I'm having a problem. I unlocked it straight away, I installed TWRP and Magisk and all was great.
Then I noticed I coulnd't enter TWRP anymore to take a full backup. I tried everything I found on the net, Volume Up+Pwr, Volume Down+Pwr, Adb and so on but nothing. So I ran TWRP from fastboot and... I f****ed my partition. Some more reasearch and I managed to have the phone back but lost the data of the past week. Why TWRP doesn't start anymore but I only see the stock recovery?
Playing some more I made that happen again and here is what I discovered:
Phone: OnePlus 7 GM1903
OS: Oxygen 9.5.8.GM57AA
TWRP: 3.3.1-1-guacamoleb
Magisk: 20.0
1) Start with factory defaults
2) Install TWRP via adb
3) Install Magisk via TWRP
4) Install MagiskHide
5) Try to enter TWRP from recovery. Doesn't work.
Can anyone help me? The feature I need the most is a full system backup
Click to expand...
Click to collapse
Hello,
did you follow this guide https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800 ?
Please use Magisk 19.3 on your pie rom.
Is this "3.3.1-1-guacamole" your whole twrp file name? Please use the ones from mauronofrio, you'll find them here(also linked in the guide)
Hi!
strongst said:
did you follow this guide https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800 ?
Click to expand...
Click to collapse
For TWRP I followed another guide and used the official website. The only thing that differs seems to be the twrp file. For Magisk I followed the XDA thread.
strongst said:
Is this "3.3.1-1-guacamole" your whole twrp file name? Please use the ones from mauronofrio, you'll find them here(also linked in the guide)
Click to expand...
Click to collapse
It's almost the entire file name: twrp-3.3.1-1-guacamoleb.img I've downloaded the images following the links in https://twrp.me/oneplus/oneplus7.html. And I've updated my original request
Should I use this file "TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio"? The download page says it's for "Oneplus 7 Pro" but I have "Oneplus 7"
strongst said:
Please use Magisk 19.3 on your pie rom.
Click to expand...
Click to collapse
The problem first started with 19.3 and the second time I tried with 20.0
What I will do now is I'll try to follow step-by-step the TWRP guide on XDA first making sure I'm using the right twrp image, then using Magisk 19.3 and I'll post an update here.
ColOfAbRiX said:
Hi!
For TWRP I followed another guide and used the official website. The only thing that differs seems to be the twrp file. For Magisk I followed the XDA thread.
It's almost the entire file name: twrp-3.3.1-1-guacamoleb.img I've downloaded the images following the links in https://twrp.me/oneplus/oneplus7.html. And I've updated my original request
Should I use this file "TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio"? The download page says it's for "Oneplus 7 Pro" but I have "Oneplus 7"
The problem first started with 19.3 and the second time I tried with 20.0
What I will do now is I'll try to follow step-by-step the TWRP guide on XDA first making sure I'm using the right twrp image, then using Magisk 19.3 and I'll post an update here.
Click to expand...
Click to collapse
Thanks for the update!
Yes, please use the twrp from mauronofrio, it's unified for OP7 and OP7 Pro (check file name like twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip)and and 19.3 magisk.
Done. The partitions didn't break like it happened the first time but I still can't access TWRP. I can only access the stock recovery.
This time I have:
TWRP: twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
Magisk: Magisk-v19.3.zip
It's exactly like these guys https://github.com/topjohnwu/Magisk/issues/1920
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
ColOfAbRiX said:
Done. The partitions didn't break like it happened the first time but I still can't access TWRP. I can only access the stock recovery.
This time I have:
TWRP: twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
Magisk: Magisk-v19.3.zip
It's exactly like these guys https://github.com/topjohnwu/Magisk/issues/1920
Click to expand...
Click to collapse
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
lvints said:
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
Click to expand...
Click to collapse
That's known, that on pie( 9.5.8 for example) magisk 20 has issues, so my recommendation was to use 19.3 Instead.
lvints said:
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
Click to expand...
Click to collapse
Really? I have the problem with Magisk version 19.3
strongst said:
That's known, that on pie( 9.5.8 for example) magisk 20 has issues, so my recommendation was to use 19.3 Instead.
Click to expand...
Click to collapse
I tried to use 19.3 and nothing.
ColOfAbRiX said:
Really? I have the problem with Magisk version 19.3
Click to expand...
Click to collapse
Hmm, really strange, with 19.4?
lvints said:
I tried to use 19.3 and nothing.
Click to expand...
Click to collapse
Something prevents twrp to stick from magisk side
strongst said:
Hmm, really strange, with 19.4?
Something prevents twrp to stick from magisk side
Click to expand...
Click to collapse
Any idea what it might be or what I did to cause it? No TWRP, no party :crying:
lvints said:
Any idea what it might be or what I did to cause it? No TWRP, no party :crying:
Click to expand...
Click to collapse
Sorry, I'm out of ideas at the moment...
And I've just realized that the Oneplus Switch application "moves" the files, it doesn't copy them. I've just lost 5 years of pictures... And still no TWRP
ColOfAbRiX said:
And I've just realized that the Oneplus Switch application "moves" the files, it doesn't copy them. I've just lost 5 years of pictures... And still no TWRP
Click to expand...
Click to collapse
I'm sad about what happened to you, friend
If you can find a solution put the topic.
I think somehow I "broke" slot A. When I put in to reboot through this slot it is the phone for TWRP, but I can't access my files.
When I select B, I lose TWRP and can access my files
That makes sense? Is there a way to fix the slots?
lvints said:
I think somehow I "broke" slot A. When I put in to reboot through this slot it is the phone for TWRP, but I can't access my files.
When I select B, I lose TWRP and can access my files
That makes sense? Is there a way to fix the slots?
Click to expand...
Click to collapse
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
ColOfAbRiX said:
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
Click to expand...
Click to collapse
See other thread(cross posting) https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
@strongst
Do you think it's best to answer this topic or the other?
lvints said:
@strongst
Do you think it's best to answer this topic or the other?
Click to expand...
Click to collapse
Where the discussion starts
Otherwise you'll lost the line when switching between threads.
ColOfAbRiX said:
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
Click to expand...
Click to collapse
I have the same problem as yours. I've tried countless scenarios, followed tutorials on XDA and Youtoube but can't make TWRP work.
Out of curiosity I restarted the device through slot A after flash zip from magisk. My phone has accessed TWRP, but I cannot access my files. When I restart from slot B I have the opposite. Twrp doesn't work, but my files are accessible.
So I believe I somehow "broke" slot A. I just don't know how I did it or how to fix it.
Guys, I upgraded my POCO F2 PRO to MIUI V12.5.1.0.RJKMIXM (Android 11). Unfortunately TWRP and Magisk versions are not compatible with Android 11 and has problems.
Before upgrading I was on MIUI 12.0.4 Android 10 and both TWRP and magisk was working without problem.
Now, I tried both ManuelBlanco's and LR Team's TWRP versions and the problems is the same. When I click select storage, internal Storage (0.00 MB) seems 0 MB. Data can't be mounted.
Also, Magisk Root does't work on that ROM. I tried to root the phone with several versions of magisk both by patching or flashing zip files but the phone bootloops every time with patched boot.img
As a result now I can't use TWRP and root functions. Are there any one who succeed to make them work on that last update without wiping data or formatting data? I have lots of settings and data on the phone so I don't want to try other options of wiping or formatting.
Thanks,
Any news magisk for latest miui rjomixm v12.0.5.1
Bogazicili90 said:
Guys, I upgraded my POCO F2 PRO to MIUI V12.5.1.0.RJKMIXM (Android 11). Unfortunately TWRP and Magisk versions are not compatible with Android 11 and has problems.
Before upgrading I was on MIUI 12.0.4 Android 10 and both TWRP and magisk was working without problem.
Now, I tried both ManuelBlanco's and LR Team's TWRP versions and the problems is the same. When I click select storage, internal Storage (0.00 MB) seems 0 MB. Data can't be mounted.
Also, Magisk Root does't work on that ROM. I tried to root the phone with several versions of magisk both by patching or flashing zip files but the phone bootloops every time with patched boot.img
As a result now I can't use TWRP and root functions. Are there any one who succeed to make them work on that last update without wiping data or formatting data? I have lots of settings and data on the phone so I don't want to try other options of wiping or formatting.
Thanks,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...y-net-pass-without-twrp.4223939/post-85443839
NOSS8 said:
https://forum.xda-developers.com/t/...y-net-pass-without-twrp.4223939/post-85443839
Click to expand...
Click to collapse
This method DOES NOT work. I tried this option before opening this thread. Magisk manager doesn't patch the boot. img correctly. After flashing new boot.img the phone doesn't boot and it drops into bootloop. It only boots after reflashing the original boot.img
It seems, still, there is no way to root Android 11 with Miui 12.5.1 on POCO F2 PRO
Bogazicili90 said:
This method DOES NOT work. I tried this option before opening this thread. Magisk manager doesn't patch the boot. img correctly. After flashing new boot.img the phone doesn't boot and it drops into bootloop. It only boots after reflashing the original boot.img
It seems, still, there is no way to root Android 11 with Miui 12.5.1 on POCO F2 PRO
Click to expand...
Click to collapse
Patched boot.img and working normally like before
Dadovvv said:
Patched boot.img and working normally like before
Click to expand...
Click to collapse
Did you formatted data or the internal storage after flashing the patched boot.img?
I read some suggestions to format data after rooting. I didn't try this since I don't want to lose all my settings and internal data.
Bogazicili90 said:
Did you formatted data or the internal storage after flashing the patched boot.img?
I read some suggestions to format data after rooting. I didn't try this since I don't want to lose all my settings and internal data.
Click to expand...
Click to collapse
I did clean flash new 12.5.1 fastboot rom, after first boot i flashed patched boot.img.
Dadovvv said:
I did clean flash new 12.5.1 fastboot rom, after first boot i flashed patched boot.img.
Click to expand...
Click to collapse
This is why I say it DOES NOT work. I don't have to format my data to only just root. I don't want to lose all my data. And I declared this on the starting thread. It doesn't work just with upgrading the MIUI. Before Android 11 it was working without formatting data.
Any news on this search yet?
HValenti said:
Any news on this search yet?
Click to expand...
Click to collapse
No solution. There is not a new version of Magisk that solves this bootloop issue. You have to format all the data after rooting with magisk to make it work. I'm using without root and TWRP.
Bogazicili90 said:
No solution. There is not a new version of Magisk that solves this bootloop issue. You have to format all the data after rooting with magisk to make it work. I'm using without root and TWRP.
Click to expand...
Click to collapse
Are you sure about formating data? I mean, are you sure that if you format the data (after flashing the patched boot) the phone will boot? Myself, I am not sure actually, as I have not seen it anywhere explicitly.
Unfortunately, according to Magisk news, any new version when eventually is published (maybe long enough), will have ditched the Magisk hide feature... So, maybe it is not worth to wait for newer version...
HValenti said:
Are you sure about formating data? I mean, are you sure that if you format the data (after flashing the patched boot) the phone will boot? Myself, I am not sure actually, as I have not seen it anywhere explicitly.
Unfortunately, according to Magisk news, any new version when eventually is published (maybe long enough), will have ditched the Magisk hide feature... So, maybe it is not worth to wait for newer version...
Click to expand...
Click to collapse
I'm not sure, I haven't tried it and won't try. I just read it on some comments. They claim that after formatting Data the phone boots normally.
Bogazicili90 said:
I'm not sure, I haven't tried it and won't try. I just read it on some comments. They claim that after formatting Data the phone boots normally.
Click to expand...
Click to collapse
I can understand you, I am in the same place.
HValenti said:
I can understand you, I am in the same place.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...-global-for-poco-f2-pro.4303453/post-85449319
Clean flash before not after.
I'm currently on 12.5.2.0 (RJKEUXM), what I did was :
1) Installed the rom via LM recovery an dpatched boot img via magisk app
2) Installed magisk v22.1.zip (with adb to install recovery (fasboot flash recovery NAMETWRP.img)
3) boot recovery with adb (fastboot boot NAMETWRP.img)
4) In recovery, I installed magisk v22.1.zip). I didn't installed "no verify opt encrypt" as it bootlooped me in fastboot.
Now it is working great ( I didn't factory reset my phone or wiped any data).
harisdu95 said:
I'm currently on 12.5.2.0 (RJKEUXM), what I did was :
1) Installed the rom via LM recovery an dpatched boot img via magisk app
2) Installed magisk v22.1.zip (with adb to install recovery (fasboot flash recovery NAMETWRP.img)
3) boot recovery with adb (fastboot boot NAMETWRP.img)
4) In recovery, I installed magisk v22.1.zip). I didn't installed "no verify opt encrypt" as it bootlooped me in fastboot.
Now it is working great ( I didn't factory reset my phone or wiped any data).
Click to expand...
Click to collapse
thanks for the tips but:
what's LM recovery? link please
which rom is better for daily use?
what is a Dpatched you mean a magisk patched boot image?