My Moto G5 plus keeps booting to TWRP. No matter what ROM I install. What do I do?
What did you do to get here? Were you on stock before? Did you we Data? You haven't really given any information...
Mikeandrd2292 said:
My Moto G5 plus keeps booting to TWRP. No matter what ROM I install. What do I do?
Click to expand...
Click to collapse
Booting into TWRP or into the bootloader?
If the Bootloader, that's a simple fix... If TWRP you probably flashed it to the boot partition instead of recovery partition, but flashing a ROM should fix it as it over-writes that partition anyway.
Guess if that doesn't help we need more info...
Mikeandrd2292 said:
My Moto G5 plus keeps booting to TWRP. No matter what ROM I install. What do I do?
Click to expand...
Click to collapse
1) never be in a hurry here... we help when we can...
2) search the forum: other people reported this problem an found a solution.
Sorry. I posted this right before I fell asleep. I updated my phone and it booted into TWRP. Now it just keeps booting into TWRP. Every ROM I flash, it does the same thing.
Updated from what to what?
Karlinski said:
Updated from what to what?
Click to expand...
Click to collapse
I restored my backup and there was a security update so I updated it and that's when all this happened.
So, you took a stock OTA Update on a rooted build, it sounds like. I believe you need to follow the steps to root again, and you should be good.
Karlinski said:
So, you took a stock OTA Update on a rooted build, it sounds like. I believe you need to follow the steps to root again, and you should be good.
Click to expand...
Click to collapse
The backup I restored was already rooted though :/
EDIT: I misread what you said. Yeah, I flashed a stock OTA update. But the problem is, I can't get into the system to root it again. It just keeps going to TWRP.
Mikeandrd2292 said:
The backup I restored was already rooted though :/
EDIT: I misread what you said. Yeah, I flashed a stock OTA update. But the problem is, I can't get into the system to root it again. It just keeps going to TWRP.
Click to expand...
Click to collapse
This procedure is for the G4, but the Factory ROM structure is the same for both the G4 and G5+:
https://forum.xda-developers.com/showpost.php?p=68948997&postcount=1
You can get the factory ROM here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Read through everything, and make sure it makes sense. I used this to remove TWRP from a G4.
Mikeandrd2292 said:
The backup I restored was already rooted though :/
EDIT: I misread what you said. Yeah, I flashed a stock OTA update. But the problem is, I can't get into the system to root it again. It just keeps going to TWRP.
Click to expand...
Click to collapse
In TWRP wipe caches and reboot... Should be fine.
acejavelin said:
In TWRP wipe caches and reboot... Should be fine.
Click to expand...
Click to collapse
That did nothing. I tried installing a new ROM and it restarted TWRP in the middle of installing.
Mikeandrd2292 said:
That did nothing. I tried installing a new ROM and it restarted TWRP in the middle of installing.
Click to expand...
Click to collapse
Wiping caches was only to get rid of the OTA file... the OTA zip file is stored in cache, removing it should have allowed the phone to boot normally, if not there is a bigger problem.
Start fresh... Flash latest TWRP, copy a new ROM and Gapps to device, wipe everything except internal/external storage, and flash clean... If it fails, or restarts in the middle of installing, you have more serious problems... likely a partition or hardware issue.
same thing happened to me, I just started over and flashed a stock image, install twrp, update to latest ota, then rooted with magisk. pretty easy with drtechie's moto g5 plus toolkit v1.1.0
Related
My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app
My OP2 is currently 100% stock, never rooted, and is running Oxygen OS 2.2.1. I have tried OTAing, flashing dirty and clean but the phone itself keeps getting the boot loop logo (Powered by Android screen with the capacity buttons off). I have enabled google apps so I'm not sure what is causing the bootloop. A history of my phone is that on 2.1.0, I tried updating the phone via OTA and I would get "Installation failed" once the entire bar finishes in Recovery. The same thing happened for 2.2.0 > 2.2.1 so I had to dirty flash the phone, otherwise I would get "Installation failed".
I keep a spare file of 2.2.1 off of Oneplus' download site so whenever this boot loop occurs, I turn the phone off and go into recovery > install from downloads > and flash the 2.2.1.
Try this ? http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Djarenga said:
Try this ? http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Click to expand...
Click to collapse
My phone isn't bricked
bump
willy156 said:
My phone isn't bricked
Click to expand...
Click to collapse
Is it, if you can't boot it up.
serkka8 said:
Is it, if you can't boot it up.
Click to expand...
Click to collapse
Hi, my phone is on 2.2.1 fine. but every time i try to update (ota shows me 3.1.0) i get a boot loop
I just tried the 3.1.0 OTA and my phone got stuck on the Powered by android screen. I had to turn the phone off and go into recovery and flashed my 2.2.1 file to unbrick myphone.
try the full rom zip intead of the OTA.
NickRuler said:
try the full rom zip intead of the OTA.
Click to expand...
Click to collapse
with or without wiping data/cache first? I'll try the 3.1.0 full zip file flashing next. think ill try to factory reset after
willy156 said:
with or without wiping data/cache first? I'll try the 3.1.0 full zip file flashing next. think ill try to factory reset after
Click to expand...
Click to collapse
Try it without wiping first. If it works , you wont lose your data.
Edit: If you dont mind losing your data, I would suggest that you use this
http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
This will flash OxygenOS 3.0.2 and restore all partitions to stock.
This should also solve your OTA problems.
I tried installing Lineage 14.1 last night, and cannot get past recovery screen now. Not sure what else to do, as I've formatted data and cache both to ext4, and have updated back to TWRP 3.0.3. Any help would be greatly appreciated.
I can still get adb and fastboot to recognize the phone, so that seems to be a good thing. But every time I reboot, I just see the ZTE logo, and then it boots into TWRP.
Format system as ext4 and make sure to be on twrp 3.0.3-1
Just to be sure, but did you flash the Nougat bootstack that was in the release topic?
Twiggy000b said:
Format system as ext4 and make sure to be on twrp 3.0.3-1
Click to expand...
Click to collapse
Thank you. Will I need to completely reinstall the rom and gapps again after updating TWRP? I'll have to get to a computer again and give it a shot.
P.S. Would have quoted your post in the Lineage forum, but lost my old account information and couldn't post under Development. So, out of curiousuty, how much trouble did you have with this?
xtermmin said:
Just to be sure, but did you flash the Nougat bootstack that was in the release topic?
Click to expand...
Click to collapse
I did. But am scared that I may have panicked and reinstalled it again. Hoping that won't cause any more trouble for me. Have had to revert to a backup iPhone, and am hating it. Lol.
Updating TWRP worked.
Setting the ROM up now, just had to get back to a computer and try updating recovery. Thanks for the help.
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..
Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.
Ebeninyo said:
Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.
Click to expand...
Click to collapse
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda
strongst said:
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda
Click to expand...
Click to collapse
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.
Ebeninyo said:
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.
Click to expand...
Click to collapse
With which recovery and rom are you able to access your internal storage?
strongst said:
With which recovery and rom are you able to access your internal storage?
Click to expand...
Click to collapse
I've only tried using TWRP as my recovery, Pixel experience rom and oxygen os rom. The thing is because upon entering the phone after flashing a rom you can't access the internal storage of the phone with TWRP because phone encrypts itself. That means I can't dirty flash it and need to wipe everything out with TWRP then reboot TWRP again and install new rom after that flash magisk and reboot to system and set everything up from the scratch.
When I started this thread I didn't knew how to dirty flash a rom. Now I know and realize the problem I'm having is phone's encryption.
UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.
Ebeninyo said:
UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.
Click to expand...
Click to collapse
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.
strongst said:
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.
Click to expand...
Click to collapse
Can you be able link me that patch and instructions?
Ebeninyo said:
Can you be able link me that patch and instructions?
Click to expand...
Click to collapse
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.
strongst said:
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.
Click to expand...
Click to collapse
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.
Ebeninyo said:
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.
Click to expand...
Click to collapse
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.
strongst said:
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.
Click to expand...
Click to collapse
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.
Ebeninyo said:
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.
Click to expand...
Click to collapse
Cool:good: