Guys warning dont install official twrp on existing unofficial one it softbbricks the device i flashed fastboot rom and updated to 5.1.6 and followed the tutorial on official twrp to get it working
I just flashed the zip. I'm sure things go south of you flash the original .IMG by itself. I think you also have to reroot after flashing or you boot loop.
Ascertion said:
I just flashed the zip. I'm sure things go south of you flash the original .IMG by itself. I think you also have to reroot after flashing or you boot loop.
Click to expand...
Click to collapse
You were on unofficial TWRP and just flashed the zip and it worked?
ddominikt said:
You were on unofficial TWRP and just flashed the zip and it worked?
Click to expand...
Click to collapse
No, I did that and didn't worked. Just flash img. from twrp on fastboot and then flash permanent twrp from that temporary twrp
Manivannan9444 said:
Guys warning dont install official twrp on existing unofficial one it softbbricks the device i flashed fastboot rom and updated to 5.1.6 and followed the tutorial on official twrp to get it working
Click to expand...
Click to collapse
I literally just did. And it's totally fine. Just flashed the zip then rebooted recovery then reflashed magisk v16.0 zip then rebooted system. Zero issues whatsoever.
Where do you get oos 5.1.6?
BTW, you can flash official OTA in TWRP then just flash TWRP & magisk again afterwards.
Sent from my OnePlus 6 using XDA Labs
brossovitch said:
I literally just did. And it's totally fine. Just flashed the zip then rebooted recovery then reflashed magisk v16.0 zip then rebooted system. Zero issues whatsoever.
Where do you get oos 5.1.6?
BTW, you can flash official OTA in TWRP then just flash TWRP & magisk again afterwards.
Click to expand...
Click to collapse
You just flashed the installer zip what about twrp img
Key is flashing magisk. It's in every tutorial
Manivannan9444 said:
You just flashed the installer zip what about twrp img
Click to expand...
Click to collapse
No. I already had unofficial TWRP installed so I simply flashed the installer.
Here's exactly what I did:
1. Downloaded the official TWRP installer package
2. Hold power button, selected reboot, select recovery, tap to reboot.
3. In TWRP, confirm Lockscreen code. Select install & selected installer package swipe to flash.
4. Press home button, select reboot, select recovery, reboot.
5. In TWRP again (now official version) confirm Lockscreen code again, select install, select Magisk 16.0, swipe to flash.
6. Select reboot system. System reboots.
7. Go on XDA find this thread and say it worked fine.
8. This is where we are now. LOL
FYI... I used the unofficial TWRP provided by Zedomax (Max Lee from HighOnAndroid) originally. I didn't do all those other crazy versions.
Sent from my OnePlus 6 using XDA Labs
brossovitch said:
No. I already had unofficial TWRP installed so I simply flashed the installer.
Here's exactly what I did:
1. Downloaded the official TWRP installer package
2. Hold power button, selected reboot, select recovery, tap to reboot.
3. In TWRP, confirm Lockscreen code. Select install & selected installer package swipe to flash.
4. Press home button, select reboot, select recovery, reboot.
5. In TWRP again (now official version) confirm Lockscreen code again, select install, select Magisk 16.0, swipe to flash.
6. Select reboot system. System reboots.
7. Go on XDA find this thread and say it worked fine.
8. This is where we are now. LOL
FYI... I used the unofficial TWRP provided by Zedomax (Max Lee from HighOnAndroid) originally. I didn't do all those other crazy versions.
Click to expand...
Click to collapse
Ok
intruda119 said:
Key is flashing magisk. It's in every tutorial
Click to expand...
Click to collapse
Spot on. Most people make this mistake then moan about it not working.
Sent from my ONEPLUS A6003 using Tapatalk
I flashed official twrp on stock recovery and now I can't exit twrp in both slots
Confirmed working fine on official twrp
Reboot recovery
Flash twrp installer zip (official)
Reboot recovery
Flash magisk 16.0
Wipe cache/davlik
Reboot system
*** DO NOT INSTALL TWRP when printed just reboot system
Profit
Rooted running official TWRP 3.2.1 enchilada ??
Alright, this is a bit confusing.
Can someone tell me if I can update to official TWRP from unofficial, without losing my data/settings? The method OP describes (via fastboot) resets all my data I guess? Wish I had never installed the unofficial version....
I have this unofficial version...
I had the unofficial twrp from the very same link you posted. No problem in updating to official TWRP. Just boot into recovery, install, select the official TWRP installer (forget the img file). Reboot in recovery again, install Magisk. Reboot to system. I did not lose any data or settings (keep always a backup of your important files, you'll never know).
Thanks for the quick reply! I dared to try it and I can confirm unofficial TWRP can indeed succesfull be overflashed with the official one. No bootloops, no errors!
Phew... I had a full nandroid backup, but I do not like the hassle of going through unbricking and such....
I had uninstalle Magisk beforehand, could be the trick?
I do not know why OP was not succesful, but it seems not a problem for everyone.
This thread really should be closed because the OP is 100% not true. If you get a softbrick, it's because you didn't install the official twrp correctly. The instructions are bit involved and I see many people skipping steps because they didn't read or don't see why they need to do anything different from previous phones.
Question I updated from an unofficial version. i followed instruction someone posted on here. But since the unofficial and official look exactly same how do I know I have official?
It does work, u just didn't do it right, u can install official TWRP over unofficial.
Well, depends on which unofficial one you use(d) .
The unofficial one I used was quite laggy on first start, I had to flash some additional zips to get it working right (see the link for install process). So concerning that one: when it works fine from start, you have the new one.
Blackout said:
Question I updated from an unofficial version. i followed instruction someone posted on here. But since the unofficial and official look exactly same how do I know I have official?
Click to expand...
Click to collapse
Related
Hello folks,
I have a Pixel sailfish and I am on Nougat 7.1.2. I would like to just root it via Magisk. Bootloader is unlocked and i tried the latest version of TWRP 3.2.1.2 and latest Magisk 16.0, Magisk Manager is 5.7. Heres the problem, if I tried to flash TWRP and then reboot into recovery (to check if TWRP sticks) I could not access my files because they are all encrypted. I did removed all pass codes, fingerprint etc. Is there a specific version of TWRP, Magisk that I need to install on Nougat 7.1.2? My process is as follow (assume fresh Nougat is onboard):
1. Boot into bootloader
2. Fastboot twrp zip
3. In twrp, flash twrp .zip
4. Reboot into recovery to see if twrp sticks
5. If 4 passes, then flash Magisk zip (version 16)
6. Reboot into system
7. Install Magisk manager apk file
8. Open Magisk manager.
Please let me know,
Thank you very much
I would like to point out that my main goals are: run stock 7.1.2 and root. That's it, no fancy kernels or anything. 8.1 and 8.0 stock are killing my battery so i would like to do some tests on 7.1.2.
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Thanks for this but i still have the same problem. Setting pin in Nougat, then reboot into bootloader, fastboot the .img file works. When in TWRP, it asks for my pin, i enter and manage to decrypt my data. Then I proceed to flash install tpwrp.zip. Process ends well but then when I reboot the phone, then reboot into TWRP (already installed). TWRP is there which means that the installation process is ok. However, this time, it does not ask for my PIN, there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted. Obviously, I cannot flash install Magisk.zip here. So I tried the following:
1. Fastboot the twrp.img to get into TWRP
2. Do not install TWRP but go to file manager and flash the Magisk.zip
3. The process ended well. I rebooted
4. Phone booted fine. I then installed Magisk Manager v5.7 (latest from XDA) via apk.
5. Installation ended ok.
6. I opened up Magisk Manager and got stuck at the Boot Logo.
I hope these are detailed, please let me know if you can help me.
Thank you very much
TENN3R said:
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Click to expand...
Click to collapse
maxwell0312 said:
... there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted...
Click to expand...
Click to collapse
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
TENN3R said:
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
Click to expand...
Click to collapse
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
maxwell0312 said:
...
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
...
Click to expand...
Click to collapse
I think for this you better ask in magisk forums. Stable version of magisk also installs the manager apk, I noticed that beta versions don't.
You can find better support in official magisk thread :good:
Hey
maxwell0312 said:
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
Click to expand...
Click to collapse
What version of TWRP did you use..More like what did you do..I am having the same problem.
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Fixed (update)
hardhead808 said:
What version of TWRP did you use..More like what did you do..I am having the same problem.
Click to expand...
Click to collapse
I flashed TWRP 3.1.1-1 then of course went in a recovery bootloop...Just flash SU..... PROFIT
maxwell0312 said:
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Click to expand...
Click to collapse
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
fiverings said:
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
Click to expand...
Click to collapse
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
maxwell0312 said:
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
Click to expand...
Click to collapse
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
fiverings said:
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
Click to expand...
Click to collapse
Thanks. I am on the smaller OG Pixel with 2770 mAh battery. I got 6h15 mins of SOT with 5% left. Not sure if this is normal
Was this problem ever resolved? I've been having problems that seem similar. I'm trying to use TWRP with Magisk and the stock google 9.0 for my Pixel, but I keep getting stuck. Wonder if someone has complete set of steps with specific versions of each of the necessary components.
bad post
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.
I went to reload 5.1.11 ..I think it might be because I forgot to remove my security features now keeps rebooting to TWPR
do I have to do a compete wipe now....or is there a simple method ?? Thanks for the help!
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
ImSpiderman said:
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
Click to expand...
Click to collapse
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
double post
skyeking69 said:
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
Click to expand...
Click to collapse
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
ImSpiderman said:
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
Click to expand...
Click to collapse
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
skyeking69 said:
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
Click to expand...
Click to collapse
No you don't have to
ImSpiderman said:
No you don't have to
Click to expand...
Click to collapse
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
skyeking69 said:
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
Click to expand...
Click to collapse
That didn't work? Really strange tho
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Gradusr said:
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Click to expand...
Click to collapse
Thanks but I really don't understand this....first I don't know if encryption is on ? Don't think I have turned it off...2nd 3.2.2.0 worked fine for me before..I installed 5.1.9 and 5.1.11 with no problems.....it was when I tried to reinstall 5.1.11 and forgot to remove security features this happened now?
How old is this thread about TWRP 3.2.2.0 ?
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
WOS17 said:
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
Click to expand...
Click to collapse
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
skyeking69 said:
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
Click to expand...
Click to collapse
No, any security just double tap to wake.
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Thanks..I'll try that first....the TWRP I have is 3.2.2.0 from official page ( I think ?) I'll try 16.7 and see what happens..
WOS17 said:
No, any security just double tap to wake.
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Click to expand...
Click to collapse
I'm using 3.2.2.0 which was working fine.....the guy below tells me to use 16.7 Magisk???? Geez not sure now ?
Gradusr said:
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Click to expand...
Click to collapse
The thing is TWRP 3.2.2.0 does ask me to enter my pin code then goes to the options page...install, wipe, backup,restore...etc...
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Geez ...now when I go to reboot to recovery it gives me a warning " No OS installed, are you sure you want to reboot?? " what do I do now ??
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
UPDATE (09/12) : Issues fixed by installing the uninstaller first then install the magisk 17.1 zip. thx to exelinguy.
Try to do the whole flash procedure again.
Boot into recovery
Flash beta2
Flash twrp
Reboot to twrp
Flash magisk
Boot to system
That way it will be installed on both partitions, could/should do the trick.
Azhar_Fahry said:
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
Click to expand...
Click to collapse
Flash the Magisk uninstaller first to remove any old files, and then flash 17.1 zip again.
Azhar_Fahry said:
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
Click to expand...
Click to collapse
Will upgrading reset the phone or will just upgrade with the same data?
sanu26661 said:
Will upgrading reset the phone or will just upgrade with the same data?
Click to expand...
Click to collapse
it depends on the situation. If you're on the Open beta updating to a newer build, the data will still be there, but if you're on the open beta downgrading a build or downgrading to oreo, your data will be lost.
whizeguy said:
Try to do the whole flash procedure again.
Boot into recovery
Flash beta2
Flash twrp
Reboot to twrp
Flash magisk
Boot to system
That way it will be installed on both partitions, could/should do the trick.
Click to expand...
Click to collapse
I already tried, still nothing
try to change slot A / B
dum143 said:
try to change slot A / B
Click to expand...
Click to collapse
When you install rom, install twrp and reboot to twrp it changes slot. If he has done it 2 times both slots are tested.
exelinguy said:
Flash the Magisk uninstaller first to remove any old files, and then flash 17.1 zip again.
Click to expand...
Click to collapse
I tried to wipe the system and flash the rom, thought that will remove all the Magisk files that already installed before. but then I flash magisk again, it still nothing. just bootloop
Azhar_Fahry said:
I tried to wipe the system and flash the rom, thought that will remove all the Magisk files that already installed before. but then I flash magisk again, it still nothing. just bootloop
Click to expand...
Click to collapse
Nonetheless, just try flashing the magisk uninstaller from here and reflashing magisk 17.1 zip
Refer to section Hotfix v17.1 in topjohnwu's update post
exelinguy said:
Nonetheless, just try flashing the magisk uninstaller from here and reflashing magisk 17.1 zip
Refer to section Hotfix v17.1 in topjohnwu's update post
Click to expand...
Click to collapse
Issues fixed by installing the uninstaller first then install the magisk 17.1 zip. thx for helping me bro. appreciate it.
I'm having the same issue but now twrp won't even show my files although I haven't wiped it. Its only showing like 9gb of storage.
whymista said:
I'm having the same issue but now twrp won't even show my files although I haven't wiped it. Its only showing like 9gb of storage.
Click to expand...
Click to collapse
have u tried to flash the open beta rom zip? I got that problem too, it's shows random folder and it contains nothing. but after I flashed the open beta rom and re flash the twrp from fastboot, it's fixed.
Hi,
I recently installed kosp on my device and rooted my device. I tried to install twrp (without any success), but after multiple tries, it seems I broke something.
I can't update anything, it seems the a partition of my device is broken :
if I try to install the update, my phone boots on the a partition and jumps immediately to the bootloader (no recovery nor system).
I tried to hard brick retore my phone twice with no luck yet.
If you have any idea on how to fix this issue, it would be much appreciated.
If not, I'll try to hardbrick restore this device once more....
Thanks !
Please read the thread before posting:
Upgrading:
It is recommended to update using updater
Via recovery:
Reboot to recovery
Sideload with ADB (preferred)
Reboot to recovery
Reboot
Via updater app:
Open Settings -> System -> KOSP Updater
Download the ota if available or if you have already downloaded the zip then use it for local upgrade
Install the update
Flash magisk to inactive slot (optional)
(optional) Reboot to recovery if you have anything else to flash
Reboot
Just use MSMTool and do a clean/fresh install.
After that. Read the OP in KOSP thread how to update. And i think u cant use TWRP with KOSP.
spinoza23 said:
Please read the thread before posting:
Upgrading:
It is recommended to update using updater
Via recovery:
Reboot to recovery
Sideload with ADB (preferred)
Reboot to recovery
Reboot
Via updater app:
Open Settings -> System -> KOSP Updater
Download the ota if available or if you have already downloaded the zip then use it for local upgrade
Install the update
Flash magisk to inactive slot (optional)
(optional) Reboot to recovery if you have anything else to flash
Reboot
Click to expand...
Click to collapse
Thanks, tried that already, sorry if I wasn't clear, but that's not working.
Dan3ll1 said:
Just use MSMTool and do a clean/fresh install.
After that. Read the OP in KOSP thread how to update. And i think u cant use TWRP with KOSP.
Click to expand...
Click to collapse
That's what I'm trying to avoid if possible...
But why? This will take you 30-60 min and u have a fresh 7 Pro with KOSP on it.
Dan3ll1 said:
But why? This will take you 30-60 min and u have a fresh 7 Pro with KOSP on it.
Click to expand...
Click to collapse
Ok, so I ended up doing that, but I'm still facing the same issue : when the device tries to boot on the a partition, I'm just immediately sent to the bootloader and have to run "fastboot --set-active=b" to reboot into my system...
KK...Don´t know were the error is. I did install KOSP and ArrowOS both 2 times to test wich rom is the best for me.
I did not having any issue with the install on both of them.
But as spinoza23 said.
Do it like the OP post and you should not have any issue.
Maybe make a post in KOSP thread if u think it is a general Rom issue.
Have you tried flashing the recovery to both slots in fastboot screen? In your case, fastboot flash boot boot.img --slot all
Ensure you're using the kosp recovery boot.img. After that, cycle the volume key to recovery then factory reset. Then adb sideload the kosp zip
I use this method all the time and avoid using twrp. Then since you already did the effort of getting the boot img, just patch it. If you really want to use twrp, just use the fbev2 version to flash things like magisk or kernels. Just boot the twrp.img though not flash. I hope this helps. Currently on derp12. I was daily driving kosp12 for a while with the patched boot and using gpay with no issues.
If you can boot to bootloader than you should be fine. A reliable way of installing roms is using the payload dumper and flashing boot.img, dtbo.img, odm.img, system.img, vbmeta.img, and vendor.img.
Thanks, I tried what you propose, unfortunately, still the same result : can't boot to a partition, which means no update possible...
lost boy said:
Thanks, I tried what you propose, unfortunately, still the same result : can't boot to a partition, which means no update possible...
Click to expand...
Click to collapse
maybe use the msm tool take it down to 9 and ota back up to 11 if you havent tried already, just a thought
Solved :
What I had to do :
use msmtool to go back to android 9
update to android 10's latest official build through the updater
update to android 11's latest beta build using oxygenos updater
update to kosp 2.2 using the provided fastboot sequence
update to kosp 2.3 using kosp updater
Took me the afternoon but seems to be working fine now !
My guess is, the device was not ready for a jump from android 9/10 to 12 directly or something...
Thanks for the help
So yeah you actually never said that u are on A9 or A10 release. I mean it is in the KOSP thread that you need 11.0.4 or the lastest A11.
Do you know that there are "newer" MSMTool builds than A9? Makes things easy.