Hi,
My OP5 worked like a charm with Resurrection Remix 5.8.5, but recently my pin was randomly unrecognised, and I solved it with lock key files suppression. I ended up to restore a backup but got a bootloop, that occured with every rom I tried.
I had bootloader unlocked and magisk flashed.
I finally managed to flash and boot Resurrection Remix 6.0 (after wiping every partition), but at every reboot, when in twrp 3.2.1.0 (also tried on 3.1.1), I'm unable to mount data partition. Also it doesn't ask for my pin as it did before all those reflashing. The rom seems to have no issue (except some bugs).
I tried reflashing twrp without result and deleting internal storage is working so far as long as I don't reboot. I found some threads with similar problems about Oreo's related roms but I don't know if they are related to my issue.
I'm currently on RR6.0, bootloader unlocked, twrp 3.2.1.0 and no root, and encrypted by default.
Do you have any idea on this ?
Thanks for your help.
nonnaryplayer said:
Hi,
My OP5 worked like a charm with Resurrection Remix 5.8.5, but recently my pin was randomly unrecognised, and I solved it with lock key files suppression. I ended up to restore a backup but got a bootloop, that occured with every rom I tried.
I had bootloader unlocked and magisk flashed.
I finally managed to flash and boot Resurrection Remix 6.0 (after wiping every partition), but at every reboot, when in twrp 3.2.1.0 (also tried on 3.1.1), I'm unable to mount data partition. Also it doesn't ask for my pin as it did before all those reflashing. The rom seems to have no issue (except some bugs).
I tried reflashing twrp without result and deleting internal storage is working so far as long as I don't reboot. I found some threads with similar problems about Oreo's related roms but I don't know if they are related to my issue.
I'm currently on RR6.0, bootloader unlocked, twrp 3.2.1.0 and no root, and encrypted by default.
Do you have any idea on this ?
Thanks for your help.
Click to expand...
Click to collapse
Are you using the twrp from twrp.me or a modded recovery like codeworkx or blu spark? The original recoveries from twrp.me don't work on oreo.
Try using these recoveries:
Codeworkx: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Blue spark: https://forum.xda-developers.com/devdb/project/dl/?id=28224
Zohair.ul.hasan said:
Are you using the twrp from twrp.me or a modded recovery like codeworkx or blu spark? The original recoveries from twrp.me don't work on oreo.
Try using these recoveries:
Codeworkx: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Blue spark: https://forum.xda-developers.com/devdb/project/dl/?id=28224
Click to expand...
Click to collapse
It worked Thanks ! I flashed codeworkx and all went fine : data is mounted at every boot, encryption unlock in recovery, flashing and restore.
I should have waited to flash oreo but this rom is the first to get me out of my bootloop hell so I'll stick with it for now.
Thanks again !
No problem Glad to see your issue got fixed.
I flashed MIUI Pro... Used it for a month or so.. then I flashed Mokee rom... Everything seemed to work well until I rebooted phone into twrp to flash magisk. I saw that data partition is not accessible at all. Unable to mount error came. So I flashed global dev miui rom using Fastboot mode. and after successful first boot i went into fastboot.. flashed Mokee Nougat instead of oreo. everything seemed good.. Until I rebooted into twrp to flash magisk but could not get into twrp cause now data encrypted and non of my mi account pass or phone pin is working... I again flashed global dev miui rom using fastboot... and again flashed twrp then new rom.... and after a successful boot into system again booted to recovery to check if i can access data partition or not... BUt still no luck.. Unable to mount data partition. HOw to fix this??????? Anyone got any Idea thanks.
killeradi said:
I flashed MIUI Pro... Used it for a month or so.. then I flashed Mokee rom... Everything seemed to work well until I rebooted phone into twrp to flash magisk. I saw that data partition is not accessible at all. Unable to mount error came. So I flashed global dev miui rom using Fastboot mode. and after successful first boot i went into fastboot.. flashed Mokee Nougat instead of oreo. everything seemed good.. Until I rebooted into twrp to flash magisk but could not get into twrp cause now data encrypted and non of my mi account pass or phone pin is working... I again flashed global dev miui rom using fastboot... and again flashed twrp then new rom.... and after a successful boot into system again booted to recovery to check if i can access data partition or not... BUt still no luck.. Unable to mount data partition. HOw to fix this??????? Anyone got any Idea thanks.
Click to expand...
Click to collapse
Just reflash your device with deep flash cable or just use pin point method
Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)
BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!
PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter
Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!
I am sick of this encryption thingy everytime I want to flash a rom on 6t, sometimes it works sometimes it's triggered even if I follow twrp tutorial.
Lately I flashed omnirom, but it encrypted slot B, I rebooted to slot A in recovery and Oos booted.
So it looks like slot B is still encrypted while A is running great and rooted with magisk.
Should I decrypt slot B or it's useless as long as I won't flash a new rom?
So did you managed to flash omnirom or not?
cultofluna said:
So did you managed to flash omnirom or not?
Click to expand...
Click to collapse
Nop
Tried a second time but it will trigger encryption again following twrp first post tutorial. It's weird because it worked in the past with other aosp roms. Perhaps Omnirom dev forgot to add A6010 as compatible 6t?
vegetaleb said:
Nop
Tried a second time but it will trigger encryption again following twrp first post tutorial. It's weird because it worked in the past with other aosp roms. Perhaps Omnirom dev forgot to add A6010 as compatible 6t?
Click to expand...
Click to collapse
Try to install without rebooting on twrp in between..
Flash rom
Flash twrp installer (DON'T reboot on twrp)
Wipe data
Flash gapps
Flash magisk
Reboot
cultofluna said:
Try to install without rebooting on twrp in between..
Flash rom
Flash twrp installer (DON'T reboot on twrp)
Wipe data
Flash gapps
Flash magisk
Reboot
Click to expand...
Click to collapse
Ok I will try.
And what is the way back? Last time I went back to oos from aosp it encrypted both slots, I had to use unbriking tool that wipes the whole phone
vegetaleb said:
Ok I will try.
And what is the way back? Last time I went back to oos from aosp it encrypted both slots, I had to use unbriking tool that wipes the whole phone
Click to expand...
Click to collapse
If both slots are encrypted you can maybe put the oos rom and a magisk zip on a otg storage to flash it via twrp
Let me know if it works also. I had same problem, the only way I was able to recover was to fastboot flash ops to phone.
adeptustech said:
Let me know if it works also. I had same problem, the only way I was able to recover was to fastboot flash ops to phone.
Click to expand...
Click to collapse
Do you have 6010 variant?
So my problem is the encryption every time i try to install a pie rom my phone ask me for a password in the recovery they say "encrytion sucesfull" so i try to wipe the rom and the same problem, i flashed the rom with a clean flash but all the pie roms for me are having the same problem, i know theres an option to remove encryption on the TWRP but when i type yes my phone automatically says me unable to mount storage unable to mount anything and basicly is dead i tryed to fix that changing the phone file contexts but nothing and to recover i need to reflash the stock firmware ands its likea a loop i revive my phone later install the recovery next install a pie rom then the pie rom not working (All the new pie roms) and later come back to the stock firmware, so im really frustated for that problem so im asking for a solution please help me:crying: . (Sorry for my bad english)
RealDogeMx said:
So my problem is the encryption every time i try to install a pie rom my phone ask me for a password in the recovery they say "encrytion sucesfull" so i try to wipe the rom and the same problem, i flashed the rom with a clean flash but all the pie roms for me are having the same problem, i know theres an option to remove encryption on the TWRP but when i type yes my phone automatically says me unable to mount storage unable to mount anything and basicly is dead i tryed to fix that changing the phone file contexts but nothing and to recover i need to reflash the stock firmware ands its likea a loop i revive my phone later install the recovery next install a pie rom then the pie rom not working (All the new pie roms) and later come back to the stock firmware, so im really frustated for that problem so im asking for a solution please help me:crying: . (Sorry for my bad english)
Click to expand...
Click to collapse
Go to recovery, DON'T decrypt data (click in cancel when the dots shows up), go to wipe and format data. You shouldn't see any errors formating data if you don't deprypt it first.
As far as I know the only roms that support encryption is Bootleggers and Havoc, but with Havoc I lose mobile internet after some time and with Bootleggers gcam doesn't work for me.