Database Users

[Q] Recovering... recovery, after Lollipop official image installation

Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?

I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179

common issue at this point. It appears recovery isnt sticking for some reason.

kokotron said:
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
Click to expand...
Click to collapse
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.

sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Click to expand...
Click to collapse
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274

kokotron said:
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
A solution for auto swpan defualt recovery, the file is there only rename it

DJBhardwaj said:
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
Click to expand...
Click to collapse
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!

sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
Click to expand...
Click to collapse
Just Install a Custom Kernel with modified ramdisk. Install Hellscore kernel and then install SuperSU. You will be able to experience Root.
I think unleashed kernel has also been updated with the same, but I can only confirm it with Hellscore.

It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.

kokotron said:
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
Click to expand...
Click to collapse
It is weird. I am pretty much sure you're either missing something or using a corrupted img file. Confirm that the file has been downloaded completely by verifying the md5 checksum and I am sure it will mismatch

hp420 said:
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
Click to expand...
Click to collapse
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?

kokotron said:
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
Click to expand...
Click to collapse
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.

sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?

sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
Ok thank you, this seems to have worked. When I booted back into Android though root didn't work any more. I re-rooted using your link (which was what I used the first time as well), and I guess I'll know how it goes the next time I reboot the phone.

hp420 said:
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
Click to expand...
Click to collapse
Not the boot loader because I have the new bootloader that came with L and TWRP working perfectly, so both can coexist.
The problem comes from within the rom as I said, the file is in /system/etc/install-recovery.sh is responsible to clear the custom recovery and return to default android recovery. The solution is to remove (or rename) that file, what I saw is that the TWRP and SuperSU (both try to) can not rename it, and the solution was to rename it manually from the file manager included in the TWRP (mounting /system as explained before).
The same problem to can not overwrite files (should be modified in any command in library ) prevents install from a flashable zip SuperSU, so the solution http://forum.xda-developers.com/nexu...- root-t2025274 initiating its own operating system booting own image solves the problem that can not be overwritten (or modified) files from the TWRP (at least until a specified version for L see the light).
Probably whoever the new bootloader prevents TWRP modify files in /system, but bootloader not erases the custom recovery. Surely people of TWRP is working to fix this issue (or sleeping sometimes you have to sleep) but the problem can be solved by keeping the new booloader.
Conclucion, I have stock L Last bootloader, root and TWRP everything working perfectly and hellsCore Kernel

sidVici0us said:
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?

you installed via the SuperSU binaries from flashable zip in TWRP or use the method http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274 ?
With the CF-auto-root you should have no problems, I did so and I read that many people do so, use this method to root.
On the other hand, I was thinking that having a recovery that can not flash zip is not something useful
---------- Post added at 03:16 PM ---------- Previous post was at 02:52 PM ----------
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
You can not use the superSU flasheable zip, the recovery is not working to modify /system partition, use the other method.

samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
CF autoroot works perfectly!! http://www.xda-developers.com/android/chainfire-releases-cf-auto-roots-for-nexus-line/

[Q] Custom Recovery Doesn't Work Anymore

Hello,
I've rooted my own note 3 and flashed Temaseks unofficial cm 12 rom. Everything works perfect so I decided to do the same thing for my father. It all went well, first I rooted his phone, then I flashed CWM and flashed cm 12 by temasek. The rom works fine but I forget to install the Gapps. So I tried to install Gapps but I got an error "Failure Status 6". I googled on that error and someone told it has to do something with CWM. I tried to flash a different version of CWM but now I can't reboot into recovery mode anymore. So I can't flash anything.
I flashed another version of CWM but this one also doesn't work. Whenever I try to boot the phone into recovery mode, the blue line shows up. Rebooting into recovery mode, but after a few secs, the phone just boots the normal way. Is there anyone that can help me to get CWM back to work? In the mean time I'll try to flash TWRP by Odin.
Thanks in advance!

So I flashed latest version of CWM: Buildversion; 6.13.0, CWM Base Version V6.0.4.7. I can reboot into recovery now but still can't install Google Apps due to failure status 6. On my own Phone I run a different version of CWM, but when I try to flash it, the phone won't boot into recovery mode anymore. It only boots into recovery when I flash this V6.0.4.7 . How can I get rid of this version and flash an older version of CWM?

You'll probably have to Odin back to stock and start over...

Morningstar said:
You'll probably have to Odin back to stock and start over...
Click to expand...
Click to collapse
You mean If there is no other way to get the Google Apps on the phone, I have to go back to stock. I did make a backup with CWM on the while it was running custom firmware. Now I have 4 files on my comuter, 3.tar and 1.md5 . If I recover them, I will still have this not working CWM version on my phone right? Isn't there a easier way to delete CWM, can I flash TWRP over CWM and see if it will install these Gapps?

Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.

Morningstar said:
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Click to expand...
Click to collapse
I appreciate your effort, thank you. The recovery issue is solved. I flashed Chainfires Root script and that installed the stock recovery. However, when I tried to install and older CWM version I got back in the recovery reboot cycle. But once I installed the latest CWM it booted in recovery. So I flashed Chainfires Root once again and had the stock recovery back. From there on I tried to install TWRP but got the recovery boot cycle again. My phone is now running android 5.0.2 and I think that's the problem.... :S I'll try again to flash Chainfires Root script to get the stock recovery back. From there on I will try to flash the link you gave to me with Odin and hope that will fix it. Do you have any ideas on what I'm doing wrong?

Your version of TWRP works so far. It reboots into RecoveryMode. Now I'll wipe and try to install Temaseks Cm 12 followed by Gapps! Thanks so far!
Okay, it's solved. Can't thank you enough for you help. Bless you!!

No problem. Glad you got it figured out!
[emoji106]

S4 I9505 - Ressurection Remix - Can't Access TWRP 3.0.0

I'm running ResurrectionRemix-M-v5.6.5-20160316 with the latest TWRP recovery and Xposed.
The last time I used the recovery was on 22/03 to make a backup of my ROM (I've entered the recovery more than a dozen times before this backup with no issues).
Today I wanted to switch from Ressurrection Remix to crDroid (Ressurrection for some reason becomes laggy after use and only a reboot resolves this issue).
I downloaded all of the zips I required (ROM, GAPPS, SU etc.)
I selected to reboot to recovery using the advanced reboot option.
The phone rebooted and displayed recovery booting in blue as per the norm.
The TWRP splash screen showed for around 10 sec or so then the phone rebooted (this never happened before).
Thinking that this was a bug with the recovery, I tried turned off the phone via the power menu once my I got into MM and then removed the battery and used the power + up button combo to enter recovery however still no go.
Next I tried flashing the TWRP 3.0.0.tar file via odin, still no luck.
The question I have is how do I resolve the issue?

Try flashing a different version of TWRP.
Or flash an twrp.img file via the app Flashify.

Ok to downgrade?
GDReaper said:
Try flashing a different version of TWRP.
Or flash an twrp.img file via the app Flashify.
Click to expand...
Click to collapse
So it's ok to downgrade to say 2.8.60 with F2FS support?

Fixed!!!
jdhot2 said:
So it's ok to downgrade to say 2.8.60 with F2FS support?
Click to expand...
Click to collapse
I found a custom version of the recovery made by the JDC team http://forum.xda-developers.com/gal.../jdcteam-twrp-touch-recovery-3-0-0-0-t3312115.
I flashed the recovery using flashify.
All fixed now

HELP! SM -G901F, TWRP can't find storage partition to mount

Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:

Pobi123 said:
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Click to expand...
Click to collapse
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?

BlueCyclone said:
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
Click to expand...
Click to collapse
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping

Pobi123 said:
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Click to expand...
Click to collapse
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.

BlueCyclone said:
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
Click to expand...
Click to collapse
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!

Pobi123 said:
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Click to expand...
Click to collapse
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again

BlueCyclone said:
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
Click to expand...
Click to collapse
Good News! Phone is back in full working order after flashing stock firmware. It was kinda scary though, I had to fix an error in Odin and then the phone wouldn't even boot up! Left it over night, booted it again and it worked fine Thanks a lot for your help, I'll try not to soft brick my device again

Need some help - Strange OP6T storage issues after flash

Hello, I have a T-Mobile 6T which thanks to the XDA thread about bypassing T-mobile, is running the international firmware so I didn't have to kiss their butt trying to unlock the bootloader. Yesterday I decided to try the Resurrection Remix rom since it is unclear whether the Lineage 16 rom supports the in-display fingerprint reader, and I am too busy at work and too lazy to read the entire thread to see if it does.
I followed the instructions and updated my OxyOS to the latest .15 release via TWRP which I also updated to the latest version via OTG using a USB drive because I was unable to unencrypt using the older Blu-Spark TWRP version I had installed. After the OxyOS update (on both partitions) I flashed TWRP again, rebooted to recovery and installed Pico Gapps.
I found the Resurrection Remix rom to be very buggy and I hate the way the in-display biometric works (very slow and I don't like the paw print used as fingerprint placement). Anyway I started installing apps and after 4 apps installed, it says there is no space left in storage.
Nothing will update, and when I try to check storage with any file explorer it says "access denied" or just won't load. I've tried everything. Wiped the data and did factory reset, then flashed stock rom again and same issue. What am I doing wrong?

That looks like a messed up flash. And is pretty common. Considering that A/B is still new and everyone has his own method of flashing. So assuming you can make it back to latest Stock OOS (9.0.15 right now). If you dunno how to then simple reboot to recovery, flash OOS ZIP and then TWRP. Again Reboot to Recovery from within TWRP (Reboot -> Recovery) and again flash OOS ZIP and TWRP Installer. For TWRP I recommend you to grab the latest one (3.3.1-6 as of now). Once flashed, Format Data (Wipe -> Format Data -> YES) and Reboot. Wait for it to boot up. Now you should be on Stable Stock OOS with TWRP Installed.
Now Download ROM of your Choice (RR, LOS, Bootleggers, whatever). You will also need the latest TWRP Installer (same as above) and Gapps (Nano/ Stock Recommended) and Magisk if you want to Root. Reboot to Recovery, flash ROM ZIP and TWRP Installer ZIP. Wait for it to Finish. Reboot to Recovery. Once in TWRP, again flash ROM and TWRP Installer. Once done, again. Reboot to Recovery from Within TWRP. (Read above on how to). Now, flash Gapps. Magisk if you want to Root. Once done, again do a Format Data. Reboot and be patient for ROM to boot. And then tell me wether this works or Not. Good Luck.