Related
Hello,
Recently (about two weeks ago) a friend of mine accidentally dropped his Galaxy Ace Plus into his toilet,
after he got it out, the phone was still on, but when he turned it off it wouldn't start up anymore.
I offered to have a look at the thing, although he already bought a new phone last week. Today he handed his Ace Plus over to me, and I mentioned that it still give a vibrate-feedback when trying to turn it on. I also found out the phone could still open in Download mode, and later I found the shortcut to the recovery (although stock's recovery has very limited options). When I went out of recovery the phone somehow started.
I went home and flashed the stock firmware of the phone (also flashed CWM and rooted the device to make some backups of data to move to his new phone), but now when I turn it off, it will still not start up when using the power button. And again, when I go to recovery and reboot the phone that way, it DOES start up).
My guess is that somehow the boot (partition?) is messed up.
I tried everything that's in my knowledge of Android 2.* phones (I've got an Sony 4.0 ICS phone myself, it works quite a bit different). I can't find a way to fix it myself, so I turned to this forums in the hope that one of you guys could help me fix his phone.
Regards, Drago
ALSO: to add, does flashing kernels work the same on these phones? Like, via fastboot with command line? I might want to try to re-flash stock kernel, hoping it fixes the boot.
Dragoboss said:
Hello,
Recently (about two weeks ago) a friend of mine accidentally dropped his Galaxy Ace Plus into his toilet,
after he got it out, the phone was still on, but when he turned it off it wouldn't start up anymore.
I offered to have a look at the thing, although he already bought a new phone last week. Today he handed his Ace Plus over to me, and I mentioned that it still give a vibrate-feedback when trying to turn it on. I also found out the phone could still open in Download mode, and later I found the shortcut to the recovery (although stock's recovery has very limited options). When I went out of recovery the phone somehow started.
I went home and flashed the stock firmware of the phone (also flashed CWM and rooted the device to make some backups of data to move to his new phone), but now when I turn it off, it will still not start up when using the power button. And again, when I go to recovery and reboot the phone that way, it DOES start up).
My guess is that somehow the boot (partition?) is messed up.
I tried everything that's in my knowledge of Android 2.* phones (I've got an Sony 4.0 ICS phone myself, it works quite a bit different). I can't find a way to fix it myself, so I turned to this forums in the hope that one of you guys could help me fix his phone.
Regards, Drago
ALSO: to add, does flashing kernels work the same on these phones? Like, via fastboot with command line? I might want to try to re-flash stock kernel, hoping it fixes the boot.
Click to expand...
Click to collapse
Try flashing some custom rom in recovery mode.
or try flashing stock rom using Jtag.
If nothing works then you should go to service center.
kk9999gada said:
Try flashing some custom rom in recovery mode.
or try flashing stock rom using Jtag.
If nothing works then you should go to service center.
Click to expand...
Click to collapse
Thank you, the first method indeed solved the problems.
I flashed the "Slimbean" ROM that has actually been released today, haha.
After that I restored a CWM Nandroid backup I created before flashing the ROM. The phone now starts normally.
Thank you very much.
Regards, Drago
Hy friends,
I have problems.
So I have a nexus 5, and I flashed several times, to test cyanogenmod, to test the preview of Android M, to install kernel... Maybe more that 12 times.
And it's happen. My phone now won't turn on. When I charge it the red led twinkle several times and after nothing. I can go to the bootloader but when I want flash something nothing happen. On the cmd console it seems like the installation works well but in fact it's useless. Yesterday I tried and suceeded to install TWRP ! Furthermore my Nexus 5 can't turn on alone, when I flash the bootloader must turn off then turn on, my phone no, I had to press Volum Down + Power button.
So yes, now I have TWRP on my phone and the application shows me that my intern storage of my phone is empty, like completly empty.
So maybe I have the solution, I want a backup which is compatible with TWRP to install it on my phone !
Do you have other ideas or maybe my idea is a ****ing bull**** and my Nexus 5 is definetly dead :crying:
Thanks a lot !
xython said:
Hy friends,
I have problems.
So I have a nexus 5, and I flashed several times, to test cyanogenmod, to test the preview of Android M, to install kernel... Maybe more that 12 times.
And it's happen. My phone now won't turn on. When I charge it the red led twinkle several times and after nothing. I can go to the bootloader but when I want flash something nothing happen. On the cmd console it seems like the installation works well but in fact it's useless. Yesterday I tried and suceeded to install TWRP ! Furthermore my Nexus 5 can't turn on alone, when I flash the bootloader must turn off then turn on, my phone no, I had to press Volum Down + Power button.
So yes, now I have TWRP on my phone and the application shows me that my intern storage of my phone is empty, like completly empty.
So maybe I have the solution, I want a backup which is compatible with TWRP to install it on my phone !
Do you have other ideas or maybe my idea is a ****ing bull**** and my Nexus 5 is definetly dead :crying:
Thanks a lot !
Click to expand...
Click to collapse
1) Adb a twrp flashable rom to your internal.
2) Use OTG and usb stick
If the led flashes red when off and connected to a charger, the battery is cmpletely discharged. Leave it connected to the original charger and USB cable for a few hours.
wangdaning said:
1) Adb a twrp flashable rom to your internal.
2) Use OTG and usb stick
Click to expand...
Click to collapse
I used adb to put a twrp recovery in my phone and when I want to install it with twrp it's wrote : FAILED. Gonna be different with OTG and USB stick ?
xython said:
I used adb to put a twrp recovery in my phone and when I want to install it with twrp it's wrote : FAILED. Gonna be different with OTG and USB stick ?
Click to expand...
Click to collapse
You can adb push the zip (rom) to the phone and try fastboot boot (twrp.img) then use twrp to flash the rom on the phone.
If this does not work it seems you motherboard is fried.
If you have twrp and the otg cable, then put the rom on your usb stick and connect in twrp. Try flashing off the drive.
Again, I am getting the feeling this is hardware. Your memory or battery seem to be failing. It has nothing to do with prior flashing. My N5 has gone through way more than yours, and I am sure others have done more than me. We still have working phones.
Also consider the power button issue.
Try the steps though.
wangdaning said:
You can adb push the zip (rom) to the phone and try fastboot boot (twrp.img) then use twrp to flash the rom on the phone.
If this does not work it seems you motherboard is fried.
If you have twrp and the otg cable, then put the rom on your usb stick and connect in twrp. Try flashing off the drive.
Again, I am getting the feeling this is hardware. Your memory or battery seem to be failing. It has nothing to do with prior flashing. My N5 has gone through way more than yours, and I am sure others have done more than me. We still have working phones.
Also consider the power button issue.
Try the steps though.
Click to expand...
Click to collapse
Thanks !
Do you know where I can download a TWRP recovery for nexus 5 (hammerhead) ?
xython said:
Thanks !
Do you know where I can download a TWRP recovery for nexus 5 (hammerhead) ?
Click to expand...
Click to collapse
TWRP thread in original development.
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!
So I got this Oneplus one from my friend and it's come to me to revive it as there is something wrong with it.. The current state of the phone is that when it's plugged on the computer it can go into fastboot mode or when I try to boot it I will see the oneplus one logo and then it will bootloop. No recovery mode. For some reason without plugging in the phone when I try to start it the phone just vibrates and then goes off and the screen is black all the time. Have charged the phone for an hour to make sure it's not out of juice.
This phone has unlocked bootloader and was on Lineage OS if I am not wrong but I am sure this friend has done something wrong in flashing the wrong file. I know there are loads of solutions which I have tried. Trust me I've tried all and then I am making this new thread or else I won't replicate content.
Things that I tried :
1. Tried flashing cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB via fastboot mode. Everything writes properly but still the same bootlooping and no recovery.
2. Tried flashing Color OS via MSM8974DownloadTool. Everything again goes fine and it's green but again got the Red oneplus one logo this time (maybe that's the color OS boot image) and then bootlooping. Also no fastboot in this mode.
3. Tried Oneplus One Patch released by them officially on their forum to revert the phone to complete stock. Again same issue.
Is there anything else I need to try to make this phone work or is this going to the bin
Any leads would be appreciated from you guys.
Thanks.
have you tried swapping out the micro usb cable because that might be your problem
Replace the batteries with a new one....
Try using fastboot image of cm11s, the very first factory rom for bacon.
I once had to go this far back when flashing sail rom or something
OK let me try with a new cable and let me try flashing cm11. Will update. Thanks.
Update : Trying since morning to get the CM11 fastboot file but unable to get it. It's there on android host server but I am getting constant speed of 10KB/s. Kept it to download for 6 hours and it failed to download.
Anyone has a google drive link to the file? It would be a great help.
If fastboot works there shouldn't be problems at all. First of all wipe everything including internal(search commands online)...also try "fastboot oem unlock" command again. Then just simply flash the latest TWRP via fastboot and from TWRP flash Official LOS15.1(works beautifully) and gapps.
i had somthing simular happened and what i did was i flashed color os then flashed twrp then cm and then booted it (it worked) then flash linage os 15.1 and thats that (i did this cuz i bricked mine while trying to make a boot logo)and btw make sure you have not got the color os boot logo set as the boot logo while installing other roms due to the fact color os boot logo stops or roms from loading make sure you have got the original boot logo!
choosymoron said:
OK let me try with a new cable and let me try flashing cm11. Will update. Thanks.
Update : Trying since morning to get the CM11 fastboot file but unable to get it. It's there on android host server but I am getting constant speed of 10KB/s. Kept it to download for 6 hours and it failed to download.
Anyone has a google drive link to the file? It would be a great help.
Click to expand...
Click to collapse
who are you downloading it from aka which developer
I am inside the OS so the issue was to do with the cable. So stupid but I guess flashing Color OS did help. Thanks a lot guys. We can close this thread. Also the battery seems to be broken, will have to change that.
because i had the same issue a few months back i totally bricked my opo and i thought my phone was gone and not coming back
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