Edit: solution added
problem:
after flashing a rom (in my case OP3lite or FreedomOS) you can't get past the boot logo
you have access to TWRP, so you can restore nandroid or flash flashable stock OxygenOS packages (tutorial here)
solution:
wipe: Dalvik /ART Cache, Cache, Data, System
flash your rom
try to boot (most likely will get stuck at boot logo)
boot into TWRP > Advanced > Fix Contexts, and swipe to Fix Contexts
Reboot
(wait a while, it might take a few minutes till it boots)
___________________________________________
original post:
hi,
I'm running official OxygenOS 3.1.3.
Rooted (systemless) , TWRP installed.
I don't have any problems on my rom, but everytime I flash a rom I get stuck at the boot logo.
I can just force reboot, goto twrp and restore my nandroid backup, and my phone works fine again.
But I can't flash any rom.
tried this:
Dirty flash OP3Lite rom - stuck at boot logo
wipe and install OP3Lite rom - stuck at boot logo
Restored nandroid backup, factory format, wipe and install OP3Lite rom - stuck at boot logo
wipe and install FreedomOS - stuck at boot logo
Restored nandroid backup, factory format, wipe and install FreedomOS - stuck at boot logo
wipe, Format userdata throught fastboot, install FreedomOS - stuck at boot logo
update to OxygenOS 3.2.1 (flashable zip throught twrp)
wipe and install FreedomOS - stuck at boot logo
Both roms I tried are OxygenOS 3.2.1 stock based, my problem is most likely not due to the rom I want to flash.
Anyone knows a solution for this?
is it possible that systemless root causes this problem?
are you encrypted? that might be the issue.
backup your internal sd data then go to fastboot and fastboot format userdata then flash the rom you want
Abaddon said:
are you encrypted? that might be the issue.
backup your internal sd data then go to fastboot and fastboot format userdata then flash the rom you want
Click to expand...
Click to collapse
I never did format my userdata throught fastboot, so I might be encrypted.
I'll try tomorrow and let you know if that was the solution.
@Abaddon I format my userdata throught fastboot (fastboot format userdata), but still roms wont go past the Logo . any other idea?
did you full wipe?
wiped /system too before flashing a rom then u go and flash the rom + gapps if needed
how long was it at the boot logo? no animation correct?
did u advance wipe - data, caches, system instead of factory wipe, try it 3 times
I did a few wipe 3 times, still stuck at logo.
I get stuck on this logo, never reboot, just get stuck there.
I noticed that it does flash the rom, cause if I restore my nanodroid backup layers and adblock is added.
I also get zero error while flashing in twrp.
I fixed it .
did a fill whipe, then flashed feedomOS, then tried to boot, didnt get past the logo, booted into recovery, selected "fix Contexts" and then rebooted, started without any problem .
doesent work for me..!! any help
Same here this issue keeps occuring again and again. then i always have to follow mega unbrick guide
Resurrection ROM 7.1.1 stuck at logo after every restore
nikhilsnigam said:
Same here this issue keeps occuring again and again. then i always have to follow mega unbrick guide
Click to expand...
Click to collapse
Faced this issue every time I restore any nandroid on one plus 3. It stucks at rotating resurrection logot . Even tried fix contents from TWRP, no output. Please help without a functional TWRP backup and restore - phone is useless. Only everytime mega unbrick guide needs to be repeated with painful reinstall of apps
hello guys. sorry if I'm a bit slow on this topic. I'm using the the op3t A3010 version (not dure whether I'm at the right forum or not lol) Recently I updated my phone to the new 4.1.7, in which I had already rooted the phone before with magisk v12. But right after the update, as usual, the phone will unroot and yes I did root the phone back by using the magisk v13.0 version. But it failed the safety net. So after a few 'research', I installed the superuser just in case that the safety net will work this time. But this is when it all went wrong. The phone did restart back to factory settings, but the phone is not rooted (checked by using the rootchecker app) So again, I'm back to the twrp recovery, clean wipe all the data, with hope that I can start from scratch which is from installing the magisk all over again. But after this step, it stuck at the boot logo for like more than half an hour. Than at this moment, I restart my phone back to recovery mode by long pressing the power button, and when I try to install both the magisk 12 and 13 version, there is a line of error code on the screen. There's a site that says simply go to the advance setting on the twrp interface, check fix contents and ur phone will be as good as new. After done doing that, I'm now stuck with a phone with no os installed and about 38% battery left. Can anyone help me here? This is the only phone that I had :crying: Urgent help needed here guys
Unless your original installation is without storage encryption (no dm-verity) this will happen. So next time install custom rom after flashing OB22 firmware+modem, then boot patch for dm-verity followed with custom rom and gapps then boot without wipe
i have the same problem but with p9 lite : when i tried a flash lineageOS or ResurrectionRemix my phone stucks at boot logo and when i flash the original os my phone works perfectly
sorry for my english
washichi said:
I fixed it .
did a fill whipe, then flashed feedomOS, then tried to boot, didnt get past the logo, booted into recovery, selected "fix Contexts" and then rebooted, started without any problem .
Click to expand...
Click to collapse
How long did you wait?
washichi said:
Edit: solution added
boot into TWRP > Advanced > Fix Contexts, and swipe to Fix Contexts
Reboot
(wait a while, it might take a few minutes till it boots)
Click to expand...
Click to collapse
What is the work around for CWM v6.0.5.1 Philz Touch6; it does not have Fix contexts under Advanced Functions
My issue: Tecno Spark K7 stuck at boot logo after flashing with ported ROM from Infinix XOS Chameleon . Both kernels match
This is EXACTLY my issue with the galaxy s9 plus. Gonna try the solution you wrote tommorow.
i have the same problem with galaxy s5 and the solution mentioned in the thread did not work with me.
im having the same issue but in lenovo z5 pro gt
PauloVillaflor said:
im having the same issue but in lenovo z5 pro gt
Click to expand...
Click to collapse
Search for answers HERE and if not successful, create a thread in the Q&A forum there.
You may not get any help here since this is the OP 3 forum.
I haven't had any software update for about 1.5 months. I was on Resurrect Remix ROM Nougat, firmware 3.2.6, and on TWRP 3.0.1 (or 3.0.0 I'm not too sure). Today I tried updating. Things went wrong. Here are my steps:
1. Wiped everything except internal storage.
2. Updated recovery to twrp-3.0.2-1.28 within recovery itself. Used the file given on the ROM thread https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-m-t3399960?nocache=1.
3. TWRP couldn't decrypt my phone even with the right password.
4. Downgraded TWRP back to 3.0.1. Decryption worked.
5. Updated firmware & modem to version 4 within recovery. Used the files given on the same ROM thread.
6. Updated recovery again to twrp-3.0.2-1.28, this time via fastboot.
7. TWRP couldn't decrypt. Tried trwp 3.0.3 from the official twrp site as well. Same problem.
8. Downgraded TWRP back to 3.0.1. Recovery didn't even start. Phone freezes.
I have two questions. What is causing this problem? And second, any way I can use fastboot to downgrade firmware 3.2.6, so that I can at least access my internal storage and back it up. I got loads of data in there.
Djalaal said:
I haven't had any software update for about 1.5 months. I was on Resurrect Remix ROM Nougat, firmware 3.2.6, and on TWRP 3.0.1 (or 3.0.0 I'm not too sure). Today I tried updating. Things went wrong. Here are my steps:
1. Wiped everything except internal storage.
2. Updated recovery to twrp-3.0.2-1.28 within recovery itself. Used the file given on the ROM thread https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-m-t3399960?nocache=1.
3. TWRP couldn't decrypt my phone even with the right password.
4. Downgraded TWRP back to 3.0.1. Decryption worked.
5. Updated firmware & modem to version 4 within recovery. Used the files given on the same ROM thread.
6. Updated recovery again to twrp-3.0.2-1.28, this time via fastboot.
7. TWRP couldn't decrypt. Tried trwp 3.0.3 from the official twrp site as well. Same problem.
8. Downgraded TWRP back to 3.0.1. Recovery didn't even start. Phone freezes.
Hi I made that too with this rom! (https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-5-8-0-oms-t3527344) I think it is that 3.0.3 TWRP that did it! I hawe to wipe everything but i got it working! with these instruction https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ Method 2 worked for me but it wipes all! there seemed to be instructions for not loosing all but i cant test it
Click to expand...
Click to collapse
I have found a solution. Even without decrypting /data, you can still get into recovery (except you can't read your data partition). This is key. What I did is simply use recovery sideload to flash the old 3.2.6 firmware (apparently flashing works even without decryption), use fastboot to flash twrp 3.0.1, and backup all my data to the computer via mtp. Then I completely wiped everything, flashed the new firmware and recovery, and decryption worked.
Today I wanted to upgrade to OOS 5.1.1. But after flashing and reboot, my 5t went into recovery mode again. Then after that, the phone always reboot into recovery mode.
I tried flash stock recovery, blue spark recovery, tried to flash oos 5.0.4, none works.
What can I do to save my 5T? TIA.
I noticed that I have this error in my twrp codeworkx recovery:
failed to mount /vendor (invalid argument)
This happened to mine as well. I did a full wipe and flashed the stock recovery and then flashed the most recent Stock OOS.
What do you mean by a full wipe?
cache+davlink+system+data? I did.
Internal storage needs to be wiped too?
Floss0324 said:
This happened to mine as well. I did a full wipe and flashed the stock recovery and then flashed the most recent Stock OOS.
Click to expand...
Click to collapse
lyrebird said:
Today I wanted to upgrade to OOS 5.1.1. But after flashing and reboot, my 5t went into recovery mode again. Then after that, the phone always reboot into recovery mode.
I tried flash stock recovery, blue spark recovery, tried to flash oos 5.0.4, none works.
What can I do to save my 5T? TIA.
I noticed that I have this error in my twrp codeworkx recovery:
failed to mount /vendor (invalid argument)
Click to expand...
Click to collapse
First thing, the error about /vendor in TWRP can be ignored because you will not have that partition if you have not installed a trebelized ROM (MOKEE treble rom).
Next is your issue:
There are two approaches I can Think of:
Approach 1) - Download official full rom from this thread
- Boot into TWRP and copy this ROM to your phone
- Wipe Clean (standard TWRP clean flash step) keeping internal storage intact
- Install ROM and try to boot.
- Sometimes it will boot back into recovery, you can try to install again.
- If it boots up fine, then follow this guide to install TWRP correctly again.
- If it didnt boot up and you are ok to wipe everything, Boot into TWRP
- Wipe Everything (you will lose all data, photos everything)
- Boot back into twrp
- Now follow install steps again.
Approach 2) if 1 didnt work:
- use this guide to unbrick your device
- You can then ROOT, install recovery etc by following this thread
I have recently experienced this problem, there was little help and finally I have to wipe all data on the phone. It was a pain in the ass and i hope you wont have to go through it !
Did many rounds of flashing of recovery and rom, tried many combinations. It eventually worked.
While I am not 100% sure, i think what makes it work is to use compatible recovery (8.0 or 8.1) with rom, and wipe both cache, system, and data after (?) flashing.
Thanks!
krispuniq said:
First thing, the error about /vendor in TWRP can be ignored because you will not have that partition if you have not installed a trebelized ROM (MOKEE treble rom).
Next is your issue:
There are two approaches I can Think of:
Approach 1) - Download official full rom from this thread
- Boot into TWRP and copy this ROM to your phone
- Wipe Clean (standard TWRP clean flash step) keeping internal storage intact
- Install ROM and try to boot.
- Sometimes it will boot back into recovery, you can try to install again.
- If it boots up fine, then follow this guide to install TWRP correctly again.
- If it didnt boot up and you are ok to wipe everything, Boot into TWRP
- Wipe Everything (you will lose all data, photos everything)
- Boot back into twrp
- Now follow install steps again.
Approach 2) if 1 didnt work:
- use this guide to unbrick your device
- You can then ROOT, install recovery etc by following this thread
I have recently experienced this problem, there was little help and finally I have to wipe all data on the phone. It was a pain in the ass and i hope you wont have to go through it !
Click to expand...
Click to collapse
What TWRP were you using? Had basically the same problem with "twrp-3.2.1-x_blu_spark_v8.74_treble-op5_op5t.img", flashed an older version and it worked fine.
Seeing "failed to mount /vendor (invalid argument)" as you mentioned happened to me too. I think it means it's only for treble compatible ROMs.
if you were rooted with magisk, you have to flash the magisk uninstaller before flash the rom.
I had the same problem after flashing XXXnolimits rom (bluespark recovery 8.73). I just power off the phone pressing the power button for a while (10-20 seconds). It worked for me and the rom was succesfully flashed. Hope this help for the future.
i will keep this in mind and will try it next time when we have an update! Thanks.
caluz78 said:
if you were rooted with magisk, you have to flash the magisk uninstaller before flash the rom.
Click to expand...
Click to collapse
Hello Everyone
I felt this section will be more appropriate for this query as it can also help many others who might be seeking an answer to the same question after Pie OOS (Community Beta) came out. This can also act as a guide for all future queries regarding force encryption. So, I have a really simple query, for which I have searched before posting but no concrete information came up.
Query:
How to prevent OOS from force-encrypting my internal data on first boot after a fresh ROM flash? I have tried flashing Magisk before first boot but that doesn't prevent force encryption. I am also using a custom kernel so patching stock boot image and flashing it won't be a viable option too.
Does anyone know of any zip or method which would prevent OOS from triggering force encryption (both Pie open beta and Oreo 5.0.8)?
I have tried to flash Oreo on an decrypted partition as follows but it still encrypted it.
1. Factory Reset
2. Flash OOS 5.0.8 zip on decrypted storage
3. Flash TWRP
4. Reboot to recovery
5. Flash Magisk
6. Flash custom kernel
7. Reboot
8. Rom takes 10 minutes to boot and storage is encrypted when booted up.
Look at this thread:
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
jeffrey268 said:
Look at this thread:
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Click to expand...
Click to collapse
The doubt i have is for the patched boot image. I always flash a custom kernel and i assume it will replace the bootimage as well.
I hope that someone here can help me rescue to rescue my data.
I was on the AOSiP build from september and than decided to encrypt my device. That worked perfectly. Now I wanted to install the latest update. The internal updater didn't work (just booted into TWRP recovery without further action, so I moved the update file to microsd and than updated manually by flashing the zip file via TWRP). Prior to the whole action, I updated TWRP through the app to the latest version.
Now my phone doesn't boot anymore, it is stuck in the AOSiP boot animation. Reverting to a previous TWRP version (3.2.3.2) didn't help, also flashing the september build again didn't help.
In TWRP I was unable to decrypt data, because TWRP keeps asking me for a password (but I don't remember putting a password in the first place). Therefor I switched from TWRP to OrangeFox recovery. Here decryption worked, put still after flashing the phone doesn't boot.
Anyone that has further ideas how to fix this without loosing all my data? Any help appreciated!
Have you tried installing another kernel?
kotobodj said:
Have you tried installing another kernel?
Click to expand...
Click to collapse
No, but as my system was running before without problems I don't expect the kernel to be the problem .. Or why would that make sense?
SOLVED: I noticed that flashing the update manually didn't automatically flash Gapps right afterwards. So flashing the Gapps helped and the phone now boots normally!