Develop Bugs

Stuck at Logo after flashing rom [fixed] > solution!

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.

Cannot install 4.0.2 update

I was using 4.0.0 stock with twrp and root. Tried to install the 4.0.2 update but every boot just took me back to recovery. Tried wiping clean, no change. Tried installing stock recovery v2.0, recovery would hang. Tried using new twrp 3.0.3 and I could get back in, but any ROM, stock or not I installed, would not stick.. Even twrp would warn me "no os installed. reboot anyway?" even when I had just installed a ROM. So in the end I flashed OOS 3.2.8 with twrp and then flashed stock recovery. At this point I'm pretty much at factory stock at v3.2.8 with stock recovery v1.0. Now I'm trying to update to 4.0.2 via OTA and for the 3rd time already I have received a installation failed message and rebooted to system. The first time I thought it was because I disconnected VPN after starting the download, so I downloaded a second and a third time. I don't want to resort to sideloading again because I fear I might get the same no OS installed problem I got when I tried to install 4.0.2 in the first place. Does anyone have any insight on what is wrong?

Steps:
1. Install latest Official or Modified TWRP ( 3.0.3/ 3.0.3 version 14 by eng.stk)
2. Enter into recovery. Connect phone to PC and copy downloaded ROM file.
3. Wipe everything in the recovery- Data, System, cache and Dalvic. It will erase everything.
4. Flash ROM zip after completing, don't reboot phone. Reboot to recovery again, and then reboot phone.
If u reboot phone directly after flashing ROM, u will loose TWRP.

Even twrp would warn me "no os installed. reboot anyway?" even when I had just installed a ROM.
Click to expand...
Click to collapse
This is pretty normal for nougat OOS. I've faced it for all 3 ROMs i flashed. Don't worry, your ROM was flashed successfully. You can mount and check the /system partition, you can see your ROM files there.
So here's what worked for me. (considering you are on ext4 /data)
1. Flash latest official twrp recovert ext4 version or use the file system swapper zip if it doesn't decrypt your data in recovery. TWRP has some issues as of now and mounts f2fs as default, so you just need to flash the file system swapper zip in order to swap it to ext4 by default.
2. Wipe /system /cache and dalvik cache.
3. Flash full 4.0.2 ROM zip, should be 1.4 GB in size.
4. Flash TWRP image again just in case.
5. Reboot to recovery, not to system.
6. Flash stable 2.79 Super Su and you are good to go.

Thanks for the tip, however I don't mind losing twrp, I only want to get stock unaltered update and this procedure does not help in this

IonAphis said:
Thanks for the tip, however I don't mind losing twrp, I only want to get stock unaltered update and this procedure does not help in this
Click to expand...
Click to collapse
Have you tried this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
P.S. I think you did, but I'm just asking.

Thanks for the tip, but I fixed it. Ended up flashing v3.2.8 via twrp and installed OTA to 4.0.1 via sideload. Recovery would not boot unless first fully booted into the system. After that sideloaded 4.0.2 via OTA and now back to complete stock.
Thanks guys!

Strange issue with mi5s not booting flashed rom

Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.

goatlad said:
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
Click to expand...
Click to collapse
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer

crzykiller said:
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
Click to expand...
Click to collapse
tried official twrp 3.1.1-0, did these steps only, maybe I've missed something:
installed twrp 3.1.1-0 then went into fastboot and typed fastboot format userdata
rebooted into TWRP, i was promted whether to keep system read only, I tried first swiping to allow mods, and also keep read only then proceeded:
changed data to F2FS (didn't wipe or factory reset anything else)
rebooted system
copied lineage and gapps zip files to phone
installed latest lineage then gapps 7.1 arm64
rebooted system, back into twrp

TWRP cannot mount /data or /system

I finally got unlocked, installed ADB/Fastboot on my computer, and flashed TWRP. (Followed this guide)
TWRP starts up with no problem, and flashed Magisk 'successfully', however I don't have root and I can't install any ROMs.
The problem appears to be TWRP cannot mount /system or /data. I've tried reflashing it to no avail. What am I doing wrong?
Edit: Since the reflash attempt it won't boot into anything other than TWRP. That's inconvenient.
Edit Edit: After letting the phone sit for ~5 minutes doing nothing, I was suddenly able to mount /data and flash a ROM. Unfortunately, my device still only boots to TWRP, and once again I can't mount /data or /system.

zurginator said:
i finally got unlocked, installed adb/fastboot on my computer, and flashed twrp. (followed this guide)
twrp starts up with no problem, and flashed magisk 'successfully', however i don't have root and i can't install any roms.
The problem appears to be twrp cannot mount /system or /data. I've tried reflashing it to no avail. What am i doing wrong?
Edit: Since the reflash attempt it won't boot into anything other than twrp. That's inconvenient.
Edit edit: After letting the phone sit for ~5 minutes doing nothing, i was suddenly able to mount /data and flash a rom. Unfortunately, my device still only boots to twrp, and once again i can't mount /data or /system.
Click to expand...
Click to collapse
format data

Mackay53 said:
format data
Click to expand...
Click to collapse
Data has been formatted, problem persists.

Zurginator said:
Data has been formatted, problem persists.
Click to expand...
Click to collapse
If it doesn't work after typing yes to format, then flash another twrp

Zurginator said:
Data has been formatted, problem persists.
Click to expand...
Click to collapse
Are you sure you formatted data? That's different than a wipe. Try rebooting into fastboot mode, connecting your phone to a computer and typing the command "fastboot format userdata" (fastboot is 1word) and then rebooting (unless you have already tried this). If you have make sure you are using the latest official TWRP for this device (not a modded one) and try flashing your ROM again. Also, some custom ROMs won't boot up if you flash Magisk at the same time. You need to flash the ROM and Gapps (if desired) and then fully boot into the system. After you have successfully booted into the ROM you can go back into recovery and flash Magisk.

Sir, I believe you can benefit from this:
https://forum.xda-developers.com/mi-mix-2/how-to/mix-pack-simple-user-twrp-adaway-supersu-t3792753
Even if you are not intending on using MIUI, this should bring your phone to stock (with unlocked bootloader).

jhs39 said:
Are you sure you formatted data? That's different than a wipe. Try rebooting into fastboot mode, connecting your phone to a computer and typing the command "fastboot format userdata" (fastboot is 1word) and then rebooting (unless you have already tried this). If you have make sure you are using the latest official TWRP for this device (not a modded one) and try flashing your ROM again. Also, some custom ROMs won't boot up if you flash Magisk at the same time. You need to flash the ROM and Gapps (if desired) and then fully boot into the system. After you have successfully booted into the ROM you can go back into recovery and flash Magisk.
Click to expand...
Click to collapse
That did the trick. I am 100% sure I was formatting data though. I'm up and booting custom ROMs now. Problems abound, of course, but that's what makes it fun.
Thanks everyone for helping out!

Try flashing the official TWRP from https://dl.twrp.me/chiron/twrp-3.2.1-0-chiron.img

I had the same problem. Just download the latest version from web or play store to fix the issue.

Unable to Install any custom rom.

So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?

So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?

JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?

SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.

JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.

SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.

JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.

SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.

hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good: