Pixel 4 boot looping issue - Google Pixel 4 Questions & Answers

I have updated to the latest version of Android 13. After that the phone keeps boot looping on startup. It gets stuck on the white screen with the G and the loading never ends.
After a while it doesn't restart anymore and got stuck on the fasboot view.
I tried these solutions but none solved my problem:
- Wipe data / Factory reset
- Google online flash tool
- Sideload
All the above options are successful but then the phone freezes on loading.
Do you have other solutions on how to fix the problem?
The Bootloader is unlocked

I had the exact same issue after the latest update, any luck on what can be done?

Related

'System UI isn't responding' and 'Process system isn't responding' w/ restarts

(Moved from general discussion)
Hey all,
I've run into a bit of a pickle..
I replaced the screen on my S8 (SM-G950U) and after booting, it immediately gives 'System UI isn't responding' and/or 'Process system isn't responding'.
Shortly after (1-3 minutes) the phone will reboot. The errors may appear 1-2 more times before rebooting.
A bit of info:
Model: SM-G950U
OS: G950USQU4CRE9
Steps taken:
Clearing cache does nothing.
Factory reset via recovery mode has no change.
Flashing stock ROM (same version) with ODIN does nothing either.
Before restoring I was able to go in and see the RAM was reporting what I assume is normal (~30% usage)
Also the front camera was no longer working, but I've replaced that as well and haven't had the phone on for long enough to get through the initial setup to test.
Anyone have a potential solution / suggestion? Any and all help is appreciated. Thanks!
Edit:
It might also be worth noting that the shutdowns only happen after booting. There's no issue when entering recovery / download mode.
Havr you tried safe mode?
I know this is an old thread but hoping to get some guidance. I am facing the exact same issue on my at&t s8+ snapdragon as mentioned above. The device is unrooted and was with stock oreo rom. suddenly started showing either "system iu isn't responding" or "process system isn't responding". Later the device started hanging and kept restarting. It restarts from samsung logo instead of the device model name unless force restarted. This cycle keeps happening. I am able to access download mode and recovery without any problem. recovery initially shows "installing update" followed by "no command" but then works normally. The device doesn't power off even from recovery, it keeps rebooting. I have tried (1) cache wipe (2) factory reset from recovery (3) safe mode (4) installed stock rom without problem (5) installed latest stock s8+ unlocked xas pie rom without problem (6) installed latest stock s8+ sprint version pie rom without problem but i am unable to even end the initial device setup as the device keeps hanging with these errors and restarts. Any ideas would be appreciated.

Stuck on "Starting Android..."

Hi Guys
I used Odin to reflash my Galaxy S10+ dual sim (duos) as it was experiencing some slowness. I used the Singapore firmware as it uses the same "G975FXXU1ASBA" model name.
The process completed successfully but when the phone boots, it gets past the Samsung logo screen and then gets stuck on a blank black screen with "Starting Android..." showing in the middle. I can swipe down from the top to show the toolbar, but it is limited in what I can select from it and the phone doesn't get to the point where the home screen boots.
I'm guessing this could be an app optimization process but after 4 hours, it was still on this screen.
I've tried re-flashing (redownloading the firmware files), clearing the cache and rebooting the phone.
Does anyone have any ideas?
In case you do want to start clean anyway, have you tried doing a reset in the recovery menu (where you are wiping the cache)? This will wipe all data.
I may have to try the full wipe, which is something I wanted to avoid but seems I have no choice.
Hopefully that at least solves the problem.
I have the same problem but I cannot get it to boot into recovery or download mode. I was flashing Magisk at the time. Odin said it worked but now it wont pass the initial stating android... Odin detects the phone but can talk to it. ADB does not even detect the phone. Phone power and reset come on. if i hold both volume the assistant comes on and if i hold bixby the safemode tag appears in the bottom corner but it still wont boot past Starting Android or boot into download mode

S4 stuck in bootloop on stock android

My Galaxy S4 VE (GT-I9515) crashed. (the screen went black) It was not rooted and ran the latest Andoid 5.0.1 ROM.
When I turned it on, it went into a bootloop, randomly crashed during booting, or turned on normally. I removed sd and sim card and tried a different battery. Furthermore I tried to boot into recovery mode and wiped the system data and the cache. It did not help.
Sometimes it was not possible to get into recovery mode because the phone's screen went black and it rebooted.
Then I tried flashing multiple stock ROM files using Odin, but it did not solve the problem.
After that i tried rooting the device and installed a custom recovery (TWRP), but i still got random crashes during booting and sometimes it got stuck showing the samsung boot animation. The only things that work reliably are the Download Mode and the charging animation.
Now, what can I do to fix my phone?
I read a bit about flashing a .pit file but I don't think that will help?
Is this a hardware or a software issue?
How can I find out, what caused the problem?

Stuck on startup android

Recenty i got a phone that was stuck in a boot loop. when you boot up the phone in the top right is said [ this binary is old , update to latest binary]. After getting issue resolved trying to flash the phone with multiple different firmwares for Samsung galaxy s7 AT&T, G930AUCUACSF1 was the one that i was able to flash but whe the phone was booting up it got stuck on the startup android screen, as in it was frozen. the boot animation wasnt even working. And yes i wipe the cache and did a factory wipe and still nothing.

Pixel 4 stuck in bootloop after last automatic attempt to update | Updating manually through ADB does not work

Hello,
Looked into the boot loop issue quite heavily over last couple of days after facing it myself and it seems for majority manually pushing the update via ADB would solve it, but not in my case unfortunately.
As mentioned in the title, boot loop began after I rebooted the phone and it had a pending update to 12.1.0 (SQ3A.220605.009.A1, Jun 2022), however it did not complete. It displays Google upon start, shows the animation, then onto G logo, progress bar comes up below it and freezes in couple of seconds. Then it restarts and does this all over again. Left it charging and in this loop overnight, for at least 12h, but there was no change.
Details:
It's a stock build, bootloader is locked
Bootloader version: c2f2-0.4-8048765
Current version: 12/SP2A.220505.002/8353555
What I tried so far:
Various reboot attempts in different intervals e.g. manual reboots while holding power button ; Manual reboots through recovery mode (some have reported positive outcomes when doing it this way couple of times in a row)
Applied updates from ADB:
12.1.0 (SP2A.220505.002, May 2022)
12.1.0 (SQ3A.220605.009.A1, Jun 2022)
flame-ota-tpb3.220513.017.b1-853b2f95.zip (The Android 13 beta, tried it as a last resort)
All updates are verified and get installed successfully according to output on the phone and ADB (complete with status 0), however version displayed in recovery mode never changes, it always remains as 12/SP2A.220505.002/8353555, hence I am assuming, that update gets stuck/corrupted
Tried flash.android[.]com - would not work as device bootloader is locked, but as per above, pushed update manually from ADB with little luck
Tried pixelrepair.withgoogle[.]com, but it throws an error, that device version is newer than that of the tool
As bootloader is locked, don't have the option to try some custom recovery tools out there, e.g. TWRP
Has anyone come across with such or similar issue in the past, where update cannot be pushed manually from ADB, accompanied with a boot loop? Any thoughts on how to resolve this? Would it be possible to at least clone the device into emulator and accessing it that way to get to non-backed up pieces of data I need?
I have not tried factory reset, as I am trying to avoid it and have it as a last resort, since while majority of data is backed up, there are some critical items and apps which are not, such as Google Authenticator, which would get me into a tricky situation with some of the 2FA services, so I am trying to resolve this without factory reset for now.
Thanks!

Categories

Resources