Related
i'm on the OTA lollipop, and this is what happens:
you unlock the phone by swiping upwards, and you see the homescreen. however, it takes around 1 to 2 seconds until the phone reacts to input!
so i unlock the phone and instantly start swiping left to right or tap on the screen(to change the desktops or start an app), and nothing happens up until 1-2 seconds after the homescreen is visible.
this lag makes me crazy! anyone else has this problem?
murfi said:
i'm on the OTA lollipop, and this is what happens:
you unlock the phone by swiping upwards, and you see the homescreen. however, it takes around 1 to 2 seconds until the phone reacts to input!
so i unlock the phone and instantly start swiping left to right or tap on the screen(to change the desktops or start an app), and nothing happens up until 1-2 seconds after the homescreen is visible.
this lag makes me crazy! anyone else has this problem?
Click to expand...
Click to collapse
Could be the mem leak reported in other threads. I got it on occasion that when exiting apps, the homescreen has some redraw/loading of all app icons etc for a few seconds, usually a restart fixes it for a few days.
Did you do a clean install?
chrismast said:
Could be the mem leak reported in other threads. I got it on occasion that when exiting apps, the homescreen has some redraw/loading of all app icons etc for a few seconds, usually a restart fixes it for a few days.
Did you do a clean install?
Click to expand...
Click to collapse
no, it was OTA, not a clean install.
but other than that the phone works fine, no sign of mem leak i'd say
its the same after a restart. even after unlocking the device for the first time after a restart, this lag exists on my device
I had the same problem after I flashed the OTA - fixed it with a clean flash.
If nothing else helps ( wipe cache , check for memleaks and so on ) try flashing the latest factory image.
Niflheimer said:
I had the same problem after I flashed the OTA - fixed it with a clean flash.
If nothing else helps ( wipe cache , check for memleaks and so on ) try flashing the latest factory image.
Click to expand...
Click to collapse
unfortunately i didnt root when i got the phone... now a clean flash is kinda problematic because i would loose a lot of data. i will try to wipe the cache.
/edit: ok i just wiped the cache, and the lag is still there... looks like a clean flash is my last hope
As long as your bootloader is unlocked you can do it without losing anything - just do a backup from recovery . If needed manually backup your sdcard as well .
Edit : Is your device encrypted by any chance ?
Niflheimer said:
As long as your bootloader is unlocked you can do it without losing anything - just do a backup from recovery . If needed manually backup your sdcard as well .
Edit : Is your device encrypted by any chance ?
Click to expand...
Click to collapse
my bootloader isnt unlocked
seriously, i dont know why this wasnt the first thing i did when i got the phone.
and no, my phone is not encrypted!
murfi said:
my bootloader isnt unlocked
seriously, i dont know why this wasnt the first thing i did when i got the phone.
and no, my phone is not encrypted!
Click to expand...
Click to collapse
You can at the very least save your settings and apps with an adb backup + google account backup ( or helium if you dont want to do it manually) , followed by a backup of your sdcard.
Backups are one of the main reason why I unlocked and rooted my Nexus from the day I bought it ( actually I unlocked , flashed factory and rooted on the bus on my way from work )
Edit : Can you try rebooting into debug mode (search for how you can do that , I believe it was by holding the power button at the power off dialog ) and see if you still have lag ? It might very well be a rogue app.
Niflheimer said:
Edit : Can you try rebooting into debug mode (search for how you can do that , I believe it was by holding the power button at the power off dialog ) and see if you still have lag ? It might very well be a rogue app.
Click to expand...
Click to collapse
after googling, i couldnt find a single site that refers to a debug mode. all results lead to the usb debugging or the developer options.
please elaborate
and btw, holding the powerbutton while the power-off dialog is present makes the phone vibrate with the poweroff-dialog disappearing and reappearing quickly. couldnt find anything else though.
murfi said:
after googling, i couldnt find a single site that refers to a debug mode. all results lead to the usb debugging or the developer options.
please elaborate
and btw, holding the powerbutton while the power-off dialog is present makes the phone vibrate with the poweroff-dialog disappearing and reappearing quickly. couldnt find anything else though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2397282
Niflheimer said:
http://forum.xda-developers.com/showthread.php?t=2397282
Click to expand...
Click to collapse
thank you very much!
the lag still exists in safe mode... well, looks like a clean install is inevitable
Afraid that's the only thing left to do - thankfully you can backup pretty much everything so no big deal.
Make sure you have everything ready though , check stickies and the rest.
First time when phone went on bootloop I sent it on fixing , apparently when they tried to boot it up for backup it went on security error loop, and now I cannot enter to download mode nor the phone is visible on pc , is there any way I can enter download mode without key combination and get phone visible again , and how to wipe everything and reinstall stock rom (watched tutorials , cant do since no download/vis. port on pc / need more "brutal" way).
Phone wasnt previously rooted , dont know if it was done when they tried the recovery.
Thanks for reading and hopefully answering , cheers
shad0wseek3r said:
First time when phone went on bootloop I sent it on fixing , apparently when they tried to boot it up for backup it went on security error loop, and now I cannot enter to download mode nor the phone is visible on pc , is there any way I can enter download mode without key combination and get phone visible again , and how to wipe everything and reinstall stock rom (watched tutorials , cant do since no download/vis. port on pc / need more "brutal" way).
Phone wasnt previously rooted , dont know if it was done when they tried the recovery.
Thanks for reading and hopefully answering , cheers
Click to expand...
Click to collapse
That's hardware failure.. flashing the stock rom won't fix your problem. Only fix is a board or phone replacement.
Google LG G4 bootloop, it's extremely common. Never store anything important on a G4, always use an SD Card.
There are some methods of baking it or taking it apart and using a heat gun/blow dryer in places but it's not a permanent fix and sometimes never really works.
Sent from my iPhone using Tapatalk
hyelton said:
That's hardware failure.. flashing the stock rom won't fix your problem. Only fix is a board or phone replacement.
Google LG G4 bootloop, it's extremely common. Never store anything important on a G4, always use an SD Card.
There are some methods of baking it or taking it apart and using a heat gun/blow dryer in places but it's not a permanent fix and sometimes never really works.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
You can reduce the cores that are being used when you root the phone, but i cannot do that cause of the problems stated above. Im perfectly aware of the hardware failure , what i need is possibly the solution to get phone recognizable to pc again.
This ROM is outdated, please look here.
Code:
/*
* This rom is for infocus m560.
* I am not responsible for any damage
* that may be caused to your phone.
*/
This ROM was port since that of mohancm and A.M.T, thank to them.
What's working:
Boot
RIL
Wifi
Bluetooth
Camera
Flash
GPS
Audio (only with call or with external audio source, I don't know why)
Internal and External Storage
Sensors
What's not working:
SIM card information is not detected
Download:
TWRP : https://androidfilehost.com/?fid=890278863836283189 or https://mega.nz/#!2QZxxCiL!Cj6C5TTJD5sjcmzN3EKla5D_gGD9Cdt_7ZHBs2EkraA thanks bigrammy
ROM : https://androidfilehost.com/?fid=818070582850490153
root : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (the official root of lineageos don't working with this rom)
GAPPS : http://opengapps.org/?arch=arm64&variant=pico&api=7.1
How to install:
download all
BACKUP your contacts on .VCF file on your SD card
install TWRP
MAKE A BACKUP OF ALL
format all (except SDcard)
install lineage-14.1-20170117-UNOFFICIAL-ZM1-fix-sensors.zip
install magisk (optinal)
install gapps (optinal)
reboot
Information:
kernel : 3.18.19+
android : 7.1.1
Created : 2018-01-28
Last Updated : 2018-02-03
Sorry for my english, if anyone could solve the problem of his thank you for telling me.
First of all thanks for your effort.
Alpha_lin said:
[*]Audio (only with call or with external audio source, I don't know why)
Click to expand...
Click to collapse
Is ringtone, notification or alarm audio not working as well directly on the device?
Salut Alpha_lin!
I have tried to flash your modified lineageOS 14.1 rom to my Infocus M560, but did not work. I have erased all partitions, except SD card.
First I have tried to use the TWRP that you linked in your post, but that did not showed anything on the screen, so I've used TWRP for Infocus M560 that can be found on needrom.
I have not flashed neither the root, nor the gapps to the device.
After successful ROM flash, the device starts, I can see the lineageos boot logo for a couple of minutes, then it pops up a white screen with two buttons, Emergency Call and Next. On the top notification area the clock, battery and cellular icon is shown.
But the touch screen does not respond, so I could not perform any action on the screen.
The power button functions, when I press the screen turns off, but when I press again it does not lit, only I can hear a tick sound that it performs some action.
The volume down button works, it decreases the volume, but the volume up does nothing.
And after a while it reboots itself and this repeats infinitely.
Do you have an idea what could be the problem? Maybe different hardver? But I don't think they made different versions...
Thanks,
Regards,
Tamas
sprengo said:
First of all thanks for your effort.
Click to expand...
Click to collapse
Thank you
sprengo said:
Is ringtone, notification or alarm audio not working as well directly on the device?
Click to expand...
Click to collapse
I'm sorry but the all sound don't work without external source except the sound of call, I don't know why.
mogyoros said:
Salut Alpha_lin!
I have tried to flash your modified lineageOS 14.1 rom to my Infocus M560, but did not work. I have erased all partitions, except SD card.
First I have tried to use the TWRP that you linked in your post, but that did not showed anything on the screen, so I've used TWRP for Infocus M560 that can be found on needrom.
I have not flashed neither the root, nor the gapps to the device.
After successful ROM flash, the device starts, I can see the lineageos boot logo for a couple of minutes, then it pops up a white screen with two buttons, Emergency Call and Next. On the top notification area the clock, battery and cellular icon is shown.
But the touch screen does not respond, so I could not perform any action on the screen.
The power button functions, when I press the screen turns off, but when I press again it does not lit, only I can hear a tick sound that it performs some action.
The volume down button works, it decreases the volume, but the volume up does nothing.
And after a while it reboots itself and this repeats infinitely.
Do you have an idea what could be the problem? Maybe different hardver? But I don't think they made different versions...
Thanks,
Regards,
Tamas
Click to expand...
Click to collapse
Salut mogyoros!
Do you have tried another time ? Maybe your download was corrupt.
If this not work I can try to fix this bug but it's strange that it happen only to you.
Alpha_lin said:
Do you have tried another time ? Maybe your download was corrupt.
Click to expand...
Click to collapse
Salut Alpha_lin!
I will try to download once more the image and try to flash it.
Will let you know the outcome.
mogyoros said:
Salut Alpha_lin!
I will try to download once more the image and try to flash it.
Will let you know the outcome.
Click to expand...
Click to collapse
Downloaded once again the ROM image, run a CRC check, that was ok.
The flashed the ROM, but saw the same issue, touch screen does not respond and after a while the phone resets.
That is also strange, that the above TWRP does not show anything on the screen when entering to recovery...
I think this is due to different hw version.
I will give up, since this is my daily used phone and need to be operational.
Thank you anyway!
mogyoros said:
Downloaded once again the ROM image, run a CRC check, that was ok.
The flashed the ROM, but saw the same issue, touch screen does not respond and after a while the phone resets.
That is also strange, that the above TWRP does not show anything on the screen when entering to recovery...
I think this is due to different hw version.
I will give up, since this is my daily used phone and need to be operational.
Thank you anyway!
Click to expand...
Click to collapse
That was a big problem for me too with the TWRP, in the end this posting helped me a lot, especially that part:
6. When you see a Black Screen release the Volume button and wait until you see TWRP.
Note: First time use can take up to 2 minutes so do not touch the screen until 2 mins has passed then press the power button briefly to wake the screen if you missed the brief screen lock notification shown by TWRP.
Click to expand...
Click to collapse
So basically when you enter the TWRP and you get a black screen wait for two minutes or so.
Flashing Alpha_lin's LineageOS worked well for me and i didnt get the touchscreen problems you mentioned but i got an infinite boot loop as well after a while. It wasn't actually a boot loop but the screen was black and it vibrated every few seconds like when you turn it on.
watch this video to know how to bypass frp lock
Hello !
One day, after a nice sleep, I switch on my phone and it boot loops! The day before, I didn't do anything special.
It's the last firmware (so under Android 10), it's a stock rom, developper mode not active.
Before flashing, I would like to take my pictures if possible my sms.
With a nice person, I tried to flash (except userdata) with Newflasher https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/ but my phone is still boot looping.
You can watch a video of this wonderful boot loop in attachment
Any suggestion is very welcome
Your browser is not able to display this video.
With regards to retrieve data from your Sony take note that when being in a boot-loop device's filesystem can't get accessed from outside, also not by USB-OTG even if device supports USB-OTG.
jwoegerbauer said:
With regards to retrieve data from your Sony take note that when being in a boot-loop device's filesystem can't get accessed from outside, also not by USB-OTG even if device supports USB-OTG.
Click to expand...
Click to collapse
thank you. So, is there any way I can make it boot? I tried fastboot set_active b but, fastboot doesn't recognise the command. I'm under windows 10 64
1. To run Fastboot commands your phone's bootloader must got unlocked, and phone must get successfully booted into Fastboot mode before.
2. Slot B on a A/B layouted Android is reserved to temporarily hold OTAs: it doesn't contain a runable Android OS.
jwoegerbauer said:
1. To run Fastboot commands your phone's bootloader must got unlocked, and phone must get booted into Fastboot mode before.
2. Slot B on a A/B layouted Android is reserved to temporarily hold OTAs: it doesn't contain a runable Android OS.
Click to expand...
Click to collapse
1. I read somewhere that if I unlock bootloader, userdata is wiped, is it correct?
2. Ok, so is there a solution to make my phone booting without deleting my pictures?
1. Correct.
2. IDK. Take it to authorized service center and let them try to fix it.
PURJUJU said:
Hello !
One day, after a nice sleep, I switch on my phone and it boot loops! The day before, I didn't do anything special.
It's the last firmware (so under Android 10), it's a stock rom, developper mode not active.
Before flashing, I would like to take my pictures if possible my sms.
With a nice person, I tried to flash (except userdata) with Newflasher https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/ but my phone is still boot looping.
You can watch a video of this wonderful boot loop in attachment
Any suggestion is very welcome
View attachment 5476663
Click to expand...
Click to collapse
Just leave it to loop for 20/30 times... It will turn on eventually.
Then enable developer options and disable automatic updates on boot/startup in developer options.
This is caused by Google Play Security trying to update itself.
You know what ? I just put it in charge and... it starts!!!
cronozrev said:
Just leave it to loop for 20/30 times... It will turn on eventually.
Click to expand...
Click to collapse
yes, this is what I was about to do. Thank you for the advice.
cronozrev said:
Then enable developer options and disable automatic updates on boot/startup in developer options.
This is caused by Google Play Security trying to update itself.
Click to expand...
Click to collapse
I'm tired by Google and it's unsolicited/corrupted updates... Does Google pays in case of bricked phone, data loss because of their updates?
An /e/OS version for XZ2C should be available by the end of this year. I can't wait to switch to this rom...
Strange thing, same thing happened to me today. Don't know it's coincidence about I have faced the same problem the same date?
OK, so I have got bootloop, so I was trying VOL UP + Power to turn off. Turned it off. Then tried VOL DOWN + Power = bootloop. Tried to plugin the original wall charger, then power ON = bootloop. Tried eject sim cards = bootloop. Tried to connect via data transfer usb cable to computer = bootloop. Unplugged cable and ejected sim cards = bootloop, but I went away for few minutes and when I back the phone it started to OS successfully. Instered SIM cards, phone did autoreboot and it works now. I am not sure these actions made the phone back, but I hope it will help someone, who came XDA with that problem.
EDIT: Just read it's due Google Play Security auto update as @cronozrev mentioned. Thank you.
The update is on Google Play System update in security setting. I guess the only option so far is disabling automatic system updates in developer options to prevent this error.
Still waiting for the real solution to this bootloop....
As mentionned tuesday, my phone could boot when I plugged it to charge. So I did full backup and used Sony Companion to "repair" (reflash) software.
All ran nicely. I put my datas back in my smartphone, download, reconfigure my apps and so on...
After a couple of day (so, yesterday) : bootloop again !!!
So here is my solution, easy and simple: I let it bootloop... and after 10 to 15 minutes, the phone started!
Lol. But that does not solve the bootloop right?
Every time Google Play System tries to update in security, phone bootloops....
cronozrev said:
Lol. But that does not solve the bootloop right?
Every time Google Play System tries to update in security, phone bootloops....
Click to expand...
Click to collapse
Well, at least, it takes you out of the sh**t...
About google forced defective updates managements, shall we create a group of people and sue this company which ruins time and energy to all the people facing this problem?
Second option: switch to another ROM
So hmm what's supposed to be the latest security update for XZ2c ?
On a previous install i had something like 2021.
But after a recent reinstall from scratch it says :
Security update: july 1, 2020
Play System update : May 1, 2020
Any way to update these manually since Sony dropped support for the device ?
Hi all,
I recently imported a used Japanese Pixel 4a (I wanted the jp-exclusive "Barely Blue" model), and immediately upon receiving it, installed LineageOS 19 on it.
The phone originally came in with some form of android 12 (I didn't check that very precisely unfortunately, could have been 12.0 and not 12.1)
Installing LineageOS went mostly fine, the phone managed to boot and I was able to use it for a few hours ... then wifi and mobile data stopped working. I thought rebooting would fix that, so I tried rebooting, but the phone never rebooted completely.
I've tried a lot of things to get it back to a working state :
Flash LineageOS again
Flash Google's Factory Image for the last 12.1
both via the online tool AND the flash-all.sh script
both on slot A and B
also tried the very old 10.0.0 JP-carrier-specific image
with a different USB cable
on a different USB2 port on my computer
on a USB3 port on my computer
Flash Google's Full OTA Image for the last 12.1
by using fastboot to boot into lineageos's recovery image
At one point in my attempts at making it work it even displayed the "Your device is corrupt" error message (it's now gone btw).
My phone is now in a state where I can reach fastboot, but everytime I try booting up any ROM (Google or LineageOS), it shows the boot animation for something like 2 seconds then shuts down.
Any help you guys could provide would be awesome
Stepland said:
Hi all,
I recently imported a used Japanese Pixel 4a (I wanted the jp-exclusive "Barely Blue" model), and immediately upon receiving it, installed LineageOS 19 on it.
The phone originally came in with some form of android 12 (I didn't check that very precisely unfortunately, could have been 12.0 and not 12.1)
Installing LineageOS went mostly fine, the phone managed to boot and I was able to use it for a few hours ... then wifi and mobile data stopped working. I thought rebooting would fix that, so I tried rebooting, but the phone never rebooted completely.
I've tried a lot of things to get it back to a working state :
Flash LineageOS again
Flash Google's Factory Image for the last 12.1
both via the online tool AND the flash-all.sh script
both on slot A and B
also tried the very old 10.0.0 JP-carrier-specific image
with a different USB cable
on a different USB2 port on my computer
on a USB3 port on my computer
Flash Google's Full OTA Image for the last 12.1
by using fastboot to boot into lineageos's recovery image
At one point in my attempts at making it work it even displayed the "Your device is corrupt" error message (it's now gone btw).
My phone is now in a state where I can reach fastboot, but everytime I try booting up any ROM (Google or LineageOS), it shows the boot animation for something like 2 seconds then shuts down.
Any help you guys could provide would be awesome
Click to expand...
Click to collapse
Could you walk us through the steps you took to initially flash LOS?
Also, have you tried flashing versions other than 12.1 of Google's factory images?
Can you boot into recovery? Did you root LOS?
How did you import the device? Are you sure it was a trusty site/seller? Could they have tinkered something with the device to not make it work?
Could you walk us through the steps you took to initially flash LOS?
Click to expand...
Click to collapse
The very first time I flashed LineageOS I just followed these "official" installation instructions from the LineageOS website. The only mistakes I remember making were :
I forgot to really check that the phone actually was on the latest stock 12.1, the phone may have been on 12.0 or an older 12.1 prior to flashing LOS
I forgot to reboot between flashing LineageOS and GApps (MindTheGapps in my case), noticed my mistake, rebooted then flashed GApps again
After I saw things weren't working, I double checked the version numbers and the sha256 hashes of everything I had downloaded and they were all correct
Also, have you tried flashing versions other than 12.1 of Google's factory images?
Click to expand...
Click to collapse
Yes,
I tried flashing factory images of
10.0.0 (Android 10) QD4A.200805.001 (6583866) (JP carriers and Verizon)
12.1.0 (SP2A.220405.003, Apr 2022)
12.1.0 (SP2A.220505.002, May 2022)
12.1.0 (SQ3A.220605.009.A1, Jun 2022)
12.1.0 (SQ3A.220705.003.A1, Jul 2022)
13.0.0 (TP1A.220624.014, Aug 2022)
Can you boot into recovery?
Click to expand...
Click to collapse
Yes
Did you root LOS?
Click to expand...
Click to collapse
No
How did you import the device? Are you sure it was a trusty site/seller? Could they have tinkered something with the device to not make it work?
Click to expand...
Click to collapse
By asking a person who's used to proxying things, this phone was from a listing on rakuten, it came from this seller. Since it came in with stock 12 (or 12.1, don't remember), I think it's unlikely they tinkered with it
Stepland said:
I forgot to really check that the phone actually was on the latest stock 12.1, the phone may have been on 12.0 or an older 12.1 prior to flashing LOS
I forgot to reboot between flashing LineageOS and GApps (MindTheGapps in my case), noticed my mistake, rebooted then flashed GApps again
Click to expand...
Click to collapse
These likely have nothing to do with the issue you're facing.
Since you're able to boot into recovery, would you be open to try to flash literally any custom ROM (with the provided custom recovery), and see if that works?
You can flash whatever you like, since you said you wanted to go for LOS, I'd recommend you flash PixelExperience, since it's the closest to that (I think). You can download the regular or the plus edition, doesn't really matter. Make sure you not only download the build (flashable zip), but also the recovery image.
I assume you're familiar with the process of flashing custom ROMs. Should you be unfamiliar, I followed this guide when I first flashed a custom ROM on my 4a.
(If you don't feel like watching a video made for newbies, here are some notes I took a while back, just so I can know I never skip a step):
Spoiler: Flashing steps
adb reboot bootloader
fastboot devices
fastboot flash --slot all boot <img_name>.img (i think this can be skipped?)
use power buttons to enter recovery mode
apply update
apply update over adb
adb sideload <zip_name>.zip
*/ if you don't want to root, you can skip everything below /*
reboot recovery (to change to active slot so that magisk flash goes to correct slot)
apply update over adb
adb sideload <magisk_name>.zip
Oh my GOD thank you SO much I'm finally getting somewhere !
I tried flashing PixelExperience, both recovery and the ROM itself, the flashing part went well.
Then I rebooted and the following things happened in order :
static google screen
phone reboots (before the animated G even appeared)
PixelExperience screen that warns "your data may be corrupt you may need to perform a factory reset"
I chose the factory reset / wipe data option
phone reboots
boot animation that lasts WAY longer than in any of my previous attempts, goes as far as 3/4 of the progress bar
phone reboots before reaching the welcome screen
PHONE SUCCESFULLY REACHES THE SETUP/WELCOME SCREEN ON THE NEXT BOOT
phone seems to freeze for a moment
"Bluetooth keeps stopping" message pops up
phone reboots + reaches welcome screen a few times
phone reboots, reaches welcome screen, then plays the "charging" chime (didn't hear it before even though it was plugged in the whole time)
It has now been a solid 10 minutes and my phone is showing the welcome screen and hasn't crashed !?!
What should I do to troubleshoot what caused the crashes ?
Thank you SOOOOOO much for your help so far !
Stepland said:
PixelExperience screen that warns "your data may be corrupt you may need to perform a factory reset"
I chose the factory reset / wipe data option
Click to expand...
Click to collapse
Ah, yeah, my mistake. You are supposed to perform a factory reset whenever you flash a different ROM. Step can only be skipped when performing a dirty flash.
Stepland said:
It has now been a solid 10 minutes and my phone is showing the welcome screen and hasn't crashed !?!
Click to expand...
Click to collapse
What do you mean by "showing the welcome screen"? Can you use your device? Can you log in to your Google account and set it up? If we don't take Bluetooth crashing into account, would you be able to use your device regularly?
Stepland said:
"Bluetooth keeps stopping" message pops up
Click to expand...
Click to collapse
Stepland said:
[...]the phone managed to boot and I was able to use it for a few hours ... then wifi and mobile data stopped working.
Click to expand...
Click to collapse
See, these malfunctions you get regardless of the OS makes me think somebody tinkered with your phone/gave you a faulty unit to begin with.
You could try to flash any / of / these kernels to see if they stop the "bluetooth crashed" notification. If you do flash a new kernel, I'd suggest you do another factory reset after the kernel has been flashed (and before you boot your device up). Just to make sure nothing stays in cache and no configurations remain that could cause this error again.
If that doesn't help, for starters, I would suggest you flash radio.img provided by Google on this site. Make sure you download the one corresponding to your build number (which you can find out by going to Settings -> About phone -> Build number (it will be at the very bottom of the page)).
You can flash this downloaded radio.img using "fastboot flash radio radio.img"
If that doesn't help either, I would try to use the Android Flash Tool. I assume the PixelExperience you downloaded is A12.1, so I would choose the latest 12.1 version in the Flash Tool. Be sure you have the "Wipe Device" and "Force Flash all Partitions" boxes ticked!!
Lada333 said:
What do you mean by "showing the welcome screen"?
Click to expand...
Click to collapse
It reached the setup assistant you are presented with the first time you power on a phone, without crashing
Lada333 said:
Can you use your device? Can you log in to your Google account and set it up? If we don't take Bluetooth crashing into account, would you be able to use your device regularly?
Click to expand...
Click to collapse
Unfortunately no :
Wi-Fi doesn't work
I can access the Wi-Fi menu in the settings, I can "turn it on" but it never finds any network. My other phone is doing just fine on my home wi-fi so it's not just that there's no network reachable
my SIM card is not recognized
Not much to say, I placed it in and the phone says it has no SIM card inserted, even after I reboot
it takes many attempts to successfully boot the phone
Last reboot took 8 tries
Surprisingly, Bluetooth seems to be working just fine ? I was able to connect to a bluetooth speaker and play some sounds
Lada333 said:
You could try to flash any / of / these kernels to see if they stop the "bluetooth crashed" notification. If you do flash a new kernel, I'd suggest you do another factory reset after the kernel has been flashed (and before you boot your device up). Just to make sure nothing stays in cache and no configurations remain that could cause this error again.
Click to expand...
Click to collapse
Tried blu_spark, exact same problems :
Takes many attempts before a "successful" boot
Wi-Fi broken
Can't detect my SIM card
Lada333 said:
If that doesn't help, for starters, I would suggest you flash radio.img provided by Google on this site. Make sure you download the one corresponding to your build number (which you can find out by going to Settings -> About phone -> Build number (it will be at the very bottom of the page)).
You can flash this downloaded radio.img using "fastboot flash radio radio.img"
Click to expand...
Click to collapse
That worked almost perfectly !
fastboot was refusing to flash radio when the phone was on fastbootd, regular fastboot worked just fine, I also flashed with --slot all because ... why not ?
After that the phone booted just fine on the FIRST TRY ! Wifi and mobile data both work !
Unfortunately it's still a bit unstable, after the first boot the phone shut down after about 10 minutes (while I was playing back a youtube video, if that's of any importance ?). It rebooted just fine without crashing even once, and it's now been running for half an hour without a problem.
If that doesn't help either, I would try to use the Android Flash Tool. I assume the PixelExperience you downloaded is A12.1, so I would choose the latest 12.1 version in the Flash Tool. Be sure you have the "Wipe Device" and "Force Flash all Partitions" boxes ticked!!
Click to expand...
Click to collapse
Well actually it was 13, so I tried flashing 13. it all went fine ! The phone rebooted fine on the first try, wifi and mobile data both work ... I'm speechless, I don't even understand what I did that made it work ... but it works !
I'll try using the phone for a few days and report back any problems if I don't forget about it.
Thank you so much for your help ! I owe you big time
Well uh, the joy was short-lived. The phone lasted a couple hours before shuting down and going back into a short series of failed boot attemps, but now every failed boot attempt gets noticeably "further" in the boot animation than they did at the time of my initial post.
The phone managed to boot yet again, wifi + data + bluetooth still work.
Keeping an eye on it for now
Stepland said:
Well uh, the joy was short-lived. The phone lasted a couple hours before shuting down and going back into a short series of failed boot attemps, but now every failed boot attempt gets noticeably "further" in the boot animation than they did at the time of my initial post.
The phone managed to boot yet again, wifi + data + bluetooth still work.
Keeping an eye on it for now
Click to expand...
Click to collapse
I honestly don't have any experience with custom ROMs on Pixels, but if you want to return to bone stock, you can use the Android Flash Tool. Since you've been using custom firmware, make sure you check the Force flash all partitions option.
Otherwise, you can refer to my guide to flash the factory firmware and root using Magisk.
Yup, that's what I did to get it to its current state.
The phone is still unstable, it rebooted itself twice just this morning.
If this is a hardware issue, how do I diagnose it ?
Stepland said:
Yup, that's what I did to get it to its current state.
The phone is still unstable, it rebooted itself twice just this morning.
If this is a hardware issue, how do I diagnose it ?
Click to expand...
Click to collapse
If you tried a stock rom, a custom ROM , with all the same results it's probably a hardware issue, have you noticed excessive heat coming from the phone? You could always trade it in for a 6a and get 300.00 credit as long as the screens good and it turns on.
hammered58 said:
have you noticed excessive heat coming from the phone?
Click to expand...
Click to collapse
Yes in fact I have ?! How did you guess that, that's weirdly specific ?
It was heating up a bit, at least enough to be noticeable and to feel abnormal but not uncomfortable. I can't remember if it got warm while it was doing its updates or before. I would have guessed it was just working pretty hard if it had been happening during some updates. Weirdly enough now that it's doing nothing it's not warm anymore
hammered58 said:
You could always trade it in for a 6a and get 300.00 credit as long as the screens good and it turns on.
Click to expand...
Click to collapse
Hmm, that's good to know. I think I'll pass tho, I chose the 4a specifically because it's small and lightweight while not being a completely out-dated phone, the 6a would take me back to more or less the same size and weight as my current phone (xiaomi vince) which I find too big and heavy. Oh the things I'd do for a flagship phone that's like, actually small
Stepland said:
Well uh, the joy was short-lived. The phone lasted a couple hours before shuting down and going back into a short series of failed boot attemps, but now every failed boot attempt gets noticeably "further" in the boot animation than they did at the time of my initial post.
The phone managed to boot yet again, wifi + data + bluetooth still work.
Keeping an eye on it for now
Click to expand...
Click to collapse
As the others have pointed out as well, it is likely a hardware malfunction. Your radio partition (?) was likely corrupt, so we got rid of that, but if random reboots still happen PLUS your device overheats, it's 99% not a software issue.
Not sure about the RMA process, since you imported the device from overseas. Try contacting your POS?
Stepland said:
Yes in fact I have ?! How did you guess that, that's weirdly specific ?
It was heating up a bit, at least enough to be noticeable and to feel abnormal but not uncomfortable. I can't remember if it got warm while it was doing its updates or before. I would have guessed it was just working pretty hard if it had been happening during some updates. Weirdly enough now that it's doing nothing it's not warm anymore
Hmm, that's good to know. I think I'll pass tho, I chose the 4a specifically because it's small and lightweight while not being a completely out-dated phone, the 6a would take me back to more or less the same size and weight as my current phone (xiaomi vince) which I find too big and heavy. Oh the things I'd do for a flagship phone that's like, actually small
Click to expand...
Click to collapse
Your right though,, it's the size and weight of the 4a that brought me here in the first place so I can see your point in not switching, good luck!!
You seem really ticked off, I'm sorry if my answer came out as snarky or something ? that really wasn't the intent
Nevermind, completely misread your answer, non-native english speaker moment
Hm, just when I was about to post that the phone seemed to be working fine because it hadn't rebooted for 30+hours ... it just rebooted again.
And yeah it also got warm again while I was installing some apps ... so uh ... no luck
Stepland said:
And yeah it also got warm again while I was installing some apps
Click to expand...
Click to collapse
That's not necessarily an issue. Installing apps uses the CPU, which, in term, generates heat.
What we and hammerhead meant by 'the phone heating up' is it randomly becoming inexplicably hot.
Like for example when it's just sitting on your desk, not doing anything. No notifications popping up constantly, no music/video playback, nothing. Just when it's supposed to be in deep sleep.
This app is rather outdated and you need to type in 3 adb commands for the advanced stats to show up, but it still works perfectly for finding out if any apps are draining the battery in the background and to see if you have any wakelocks.
You could give it a shot, install it, enable in settings -> general "App Usage," "Device Usage Access" and "Record History," and wait a few days, see if you have any apps misbehaving.
Again, I'm still leaning toward it being a hardware issue, but hey, worth a try.
I give up, it just has to be a hardware defect.
Since with stock 13 it looked like the phone was almost stable (it would only reboot every 10 hours or so) I tried using it for a day, unfortunately it quickly went back to the exact same state it was in when I created this thread : the phone won't boot, it crashes two seconds into the boot animation.
Still, massive thanks to everyone who helped me through this !
I ordered a replacement.
If anyone wants the broken one my DMs are open