Related
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.
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
dantekb43 said:
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
Click to expand...
Click to collapse
try TWRP 3.0.2.. after that boot normally. then factory reset. boot again. go back to recovery flash su clear cache and dalvik cache.. boot. phone mat bootloop at logo few times don't interrupt it let it boot itself.
sukhwant717 said:
try TWRP 3.0.2.. after that boot normally. then factory reset. boot again. go back to recovery flash su clear cache and dalvik cache.. boot. phone mat bootloop at logo few times don't interrupt it let it boot itself.
Click to expand...
Click to collapse
Apparently.... my phone refuses to install TWRP 3.0.2......
I'm doing all the steps that I'm used to.... Enable Debugging on dev. options.... adb reboot fastboot.... fastboot flash recovery "TWRP 3.0.2" and it's sucessful....
However... when i try to boot into recovery, the phone goes back to fastboot (although, i can boot it to system normally).
I tried flashing 3.1.1 back again and it worked, it went back to 3.1.1 .... so I'm back at square one.
dantekb43 said:
Apparently.... my phone refuses to install TWRP 3.0.2......
I'm doing all the steps that I'm used to.... Enable Debugging on dev. options.... adb reboot fastboot.... fastboot flash recovery "TWRP 3.0.2" and it's sucessful....
However... when i try to boot into recovery, the phone goes back to fastboot (although, i can boot it to system normally).
I tried flashing 3.1.1 back again and it worked, it went back to 3.1.1 .... so I'm back at square one.
Click to expand...
Click to collapse
which version of super su you are flashing?
dantekb43 said:
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
Click to expand...
Click to collapse
Check the following topic and download VerifiedBootSigner-v8.zip
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Flash SuperSU and don't reboot yet.
Flash VerifiedBootSigner-v8.zip and then reboot.
Let me now if it worked. I had the same problem after installing Magisk. Resigning the bootimage fixed the problem for me.
Vorstedt said:
Check the following topic and download VerifiedBootSigner-v8.zip
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Flash SuperSU and don't reboot yet.
Flash VerifiedBootSigner-v8.zip and then reboot.
Let me now if it worked. I had the same problem after installing Magisk. Resigning the bootimage fixed the problem for me.
Click to expand...
Click to collapse
I've had the same problem and your solution fixed it!
Thank you very much, sir! :good:
I recently wanted to root my phone which I ended up doing but then I wanted to try a custom rom. After doing an adb backup I deleted all the files I then pushed the twrp zip and installed it and rebooted back into recovery. I then pushed the bootable zips for roms such as Invictrix, Lineage, and Dirty Unicorns. Everytime I tried to install a rom I get an error that reads:
Error applying update: 51 (ErrorCode:: kPayloadTimestampError)
Updater process ended with ERROR: 1
Error installing zip file 'romfilename.zip'
Updating partition details.....done
Each rom zipfile i made sure was for Nash.
Lorkald said:
I recently wanted to root my phone which I ended up doing but then I wanted to try a custom rom. After doing an adb backup I deleted all the files I then pushed the twrp zip and installed it and rebooted back into recovery. I then pushed the bootable zips for roms such as Invictrix, Lineage, and Dirty Unicorns. Everytime I tried to install a rom I get an error that reads:
Error applying update: 51 (ErrorCode:: kPayloadTimestampError)
Updater process ended with ERROR: 1
Error installing zip file 'romfilename.zip'
Updating partition details.....done
Each rom zipfile i made sure was for Nash.
Click to expand...
Click to collapse
Which version of twrp and which release of the rom are you trying?
Uzephi said:
Which version of twrp and which release of the rom are you trying?
Click to expand...
Click to collapse
twrp is version 3.2.2.2
Well the one I wanted the most and first tried was Dirty Unicorns which was the official release of 12.4 but I also tried 12.3 and most recent weekly. All giving the same error.
Try using TWRP version 3.2.1-1
Marcowe said:
Try using TWRP version 3.2.1-1
Click to expand...
Click to collapse
trying now
Lorkald said:
trying now
Click to expand...
Click to collapse
Flash the recent 07/27 weekly in 3.2.2. Ignore the error, go to reboot menu and swap slots then reboot and report back please.
Uzephi said:
Flash the recent 07/27 weekly in 3.2.2. Ignore the error, go to reboot menu and swap slots then reboot and report back please.
Click to expand...
Click to collapse
Did what you said and I got an Error 1 when trying to install the zip and the other slot didnt have an os. so it went into a boot loop and when I installed it again back on slot a and just tried booting up that one it went into a boot loop aswell. Didn't even have the dirty unicorns logo when boot looping.
Lorkald said:
Did what you said and I got an Error 1 when trying to install the zip and the other slot didnt have an os. so it went into a boot loop and when I installed it again back on slot a and just tried booting up that one it went into a boot loop aswell. Didn't even have the dirty unicorns logo when boot looping.
Click to expand...
Click to collapse
Format data and type "yes" then reboot
Uzephi said:
Format data and type "yes" then reboot
Click to expand...
Click to collapse
now what?
Lorkald said:
now what?
Click to expand...
Click to collapse
Does it boot? Formatting data should have fixed the bootloop
download the 27.1.3 but dont install twrp you have to enable oem unlock then adb devices so your pc sees it then reboot bootloader fastboot boot twrp.img i had issues decrypting data on new twrp when i was trying to help see whats up twrp oreo v6 you made works great that will fix issues
my oneplus 5t already unlocked bootloader, installed TWRP.
yesterday i saw the oneplus 5t open beta 19, so i downloaded it and click setting→system update→local, and click the downloaded update files...
it reboot into twrp and flashing, after flashed, my phone boot loop into twrp only, cannot boot into system. So i click wipe→advanced→ tick dalvik, cache, system and data. next i download the stock rom from official (oos 5.1.7 and open beta 19). after flashing, it also boot loop into twrp... i tried download and install the stock recovery from official, but it black screen when i boot into recovery, so flashed back to the TWRP...
Pls help me to solve the problem pls........... :crying: :crying:
ArlenCheng said:
my oneplus 5t already unlocked bootloader, installed TWRP.
yesterday i saw the oneplus 5t open beta 19, so i downloaded it and click setting→system update→local, and click the downloaded update files...
it reboot into twrp and flashing, after flashed, my phone boot loop into twrp only, cannot boot into system. So i click wipe→advanced→ tick dalvik, cache, system and data. next i download the stock rom from official (oos 5.1.7 and open beta 19). after flashing, it also boot loop into twrp... i tried download and install the stock recovery from official, but it black screen when i boot into recovery, so flashed back to the TWRP...
Pls help me to solve the problem pls........... :crying: :crying:
Click to expand...
Click to collapse
Format Data and then flash the rom. Formatting will wipe even your internal storage so once formatting is done, transfer the files to phone and then flash
Hello
I have big problem.
After patching img over Magisk and flash this new patched img, can not start system / boot loop to POCO logo, or boot loop to MIUI logo - here system starting, but every restart and boot loop
Help please
Thanks
Hi!
Which boot-img did you patch and where did it come from?
How did you flash it?
So:
I received an update 12.5.8.0.RKHEUXM
After the update, I always have to root the phone again.
So I took boot.img from the original 12.5.8.0.RKHEUXM and patched it via Magisk.
I flashed the patched boot.img via ADB.
Well, after the restart, my phone will boot only after the MIUI logo and a bit of a melody, and the phone will restart again. This restart is performed about 4 times and remains/stops in fastboot mode,or it will return to TWRP after clearing dalvik and cache and restarting.
He does what he wants
I've had a problem with that before, but it was enough to delete Dalvik and the cache via temporary TWRP.
Then the system booted up normally, but now it doesn't work even after deleting Dalvik and the cache.
Here is a link to the thread where I solved it. Nobody actually advised me there, I just tried to clear dalvik and cache via TWRP and it was after the problem. Unfortunately, now the problem persists.
Poco F3 - Boot Loop to POCO logo / Please help
Hello. I have a big problem after updating the firmware. Poco F3 root over magisk. After updating from 12.5.6.0 RKHEUXM, I updated to 12.5.7.0 RKHEUXM. After the restart, both the phone and the system booted up. I patched the original boot.img...
forum.xda-developers.com
Thats what I did also with 12.5.8.0.RKHEUXM and everything is working fine.
Updated to 12.5.8.0 via the MIUI updater, but downloading the full rom, as the updater told me that the incremental update (~58MB) wouldn't work.
Then downloaded the the recovery file here: https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.8.0.RKHEUXM/
Unzipped it and extracted the boot.img with payload-dumper-go on my Mac: https://github.com/ssut/payload-dumper-go
Patched the boot.img with Magisk on the phone.
Copied the patched_boot.img file back to the Mac.
Flashed the patched_boot.img from the mac with fastboot to both partitions:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Friend, I did exactly what you were writing, and unfortunately my system won't start
The only thing I did differently was to download the big rom 6gb update so I didn't have to extract boot.img. I didn't have to use a payload dumper.
Any other solution?
But I don't want to lose data and applications!
Did you try wiping data partition?
takichiman said:
Did you try wiping data partition?
Click to expand...
Click to collapse
Where should I do it?
But I don't want to lose data and applications!!!!!
I have bootloop to MIUI logo 4times - 5times and then stop in fastboot mode , It stops in fastboot mode and after pressing and holding the power button, the mobile starts only in fastboot mode, it no longer starts booting to the MIUI log
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
takichiman said:
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
Click to expand...
Click to collapse
You didn't give me much advice, my friend
I don't want to lose any data, or applications, pictures, just anything.
If it went after deleting the dalvik / cache last time, then why shouldn't it go now?
The system boots only to the miui logo, then the boot loop.
I don't understand why this is so.
And can't you somehow refresh the whole rom without losing data, applications and files?
Boot temp recovery, backup boot, patch backed boot and flash patched boot ... Just rename the boot backed image of twrp in boot.img, patch and flash ...
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Dark-Yox said:
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Click to expand...
Click to collapse
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
snx413 said:
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
When you boot, you have access normally
snx413 said:
When you boot, you have access normally
Click to expand...
Click to collapse
And how do I remove them? instructions please
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
You can remove them in TWRP
jkmaxfli said:
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Click to expand...
Click to collapse
Dirty flash the whole ROM then
Adb shell
then
magisk --remove-modules
Dark-Yox said:
You can remove them in TWRP
Dirty flash the whole ROM then
Click to expand...
Click to collapse
How it dirty flash ?
I used it over TWRP recovery ROM zip file, and not work flashing