Hi. Sorry was that reply to my question or someone else?
Thanks
Hi. Sorry was that reply to my question or someone else?
What's weird is that I can successfully flash it (both from recovery and fastboot), but I can't boot into it. I get the Ofox splash screen, it sits there for ~15 seconds, then reboots back to system.I had this issue too, install unofficial orange fox and it should be fixed. I'm pretty sure Joey linked it a couple pages back.
Edit:
Here is the link - http://androidfilehost.com/?fid=4279422670115710816
Have you tried flashing it again? Or maybe try going back to previous version then back to it.What's weird is that I can successfully flash it (both from recovery and fastboot), but I can't boot into it. I get the Ofox splash screen, it sits there for ~15 seconds, then reboots back to system.
Anyone got any ideas as to why that might be?
Thanks in advance.
Yeah, I reflashed it. That didn't work, so I re-downloaded and re-flashed it.Have you tried flashing it again? Or maybe try going back to previous version then back to it.
Damn, I'm sure someone on here with more experience will be able to help you out. I'm not the most experienced sorry.Yeah, I reflashed it. That didn't work, so I re-downloaded and re-flashed it.
I can flash back to the official Orangefox build, and that loads as expected. I then flashed forward again and back to the bootloop. I'm baffled tbh.
What? I shared the problem and the solution for others to help
It's because your refresh rate is higher than 60hz. Try lower the apps frequencies to 60 hz.System just hangs when using camera and some apps such as Google Maps, and magically unhangs when pressing and holding my finger in the area below the fingerprint sensor. Any idea what's causing this?
After you flash the ROM, use the wipe (dalvik and something else) option that's on that page - go back to the main wipe tab - do a full format - then reboot. It worked for me today.What's weird is that I can successfully flash it (both from recovery and fastboot), but I can't boot into it. I get the Ofox splash screen, it sits there for ~15 seconds, then reboots back to system.
Anyone got any ideas as to why that might be?
Thanks in advance.
I tried yesterday to dirty flash the latest build (using the latest TWRP official) but without success.I cant boot my system with root, only if i update without magisk system is up. Any ideas?
On the build from 22.01.2023 "evolution_raphael-ota-tq1a.230105.001.a2-01220928-unsigned.zip" everything with root works fine. But on rom from 25.01.2023 after installing root device return to recovery.I tried yesterday to dirty flash the latest build (using the latest TWRP official) but without success.
I flashed using the same steps (ROM, Magisk, DFE) as I always did but this time something has changed that prevented the update - phone booted back to recovery.
I have root with Magisk 25.2, different modules that never interfered with dirty flashing. System build is "13 TD1A.221105.001". The firmware is the latest A11 file for Global device.
Maybe my OS it's too old?...
Is clean flash mandatory for the latest build? Or clean flash AND data format mandatory? Maybe, I don't know, but I really don't have the time to configure everything again from scratch.
So, it's a fact. Thanks for confirming it.On the build from 22.01.2023 "evolution_raphael-ota-tq1a.230105.001.a2-01220928-unsigned.zip" everything with root works fine. But on rom from 25.01.2023 after installing root device return to recovery.
Hey, was this reply for me? Sorry it's just you didn't mention any names.I'm used to install updates by wiping caches/system/vendor and flashing latest update, but with the latest one I lost fast charging.
The fix if someone is experiencing it is wiping caches/system/vendor as mentioned above then flashing the correct firmware for your phone then flashing the update. I though this could help someone else.
I couldn't get into the recovery to do that, the problem being that recovery was broken.After you flash the ROM, use the wipe (dalvik and something else) option that's on that page - go back to the main wipe tab - do a full format - then reboot. It worked for me today.
Thank you!
You'd think it's a bug until you realize fingerprint won't unlock when night light is active on the lockscreen itself. It's the intended behavior as our fingerprint sensor isn't the same with the Pixels.Bug description: There is a bug with the "On screen fingerprint". Whenever I turn of my screen the night mode (the one that make screen yellow) also stops. But after unlocking it the device, the night mode turns back on.
/*
* Your warranty is void. Or valid, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/