Related
Hi Everyone!
Really new to xda so I'm not sure if this is the right place to post this at (sorry). I have a nexus 5 that after I (purposely) rebooted, is now just stuck on the boot animation, (it was not updating to 5.1.0 or 5.0.1). I tried leaving it on but it just kept spinning until the phone died. I can access fastboot, and recovery, have tried wiping cache, and factory resetting multiple times. Nothing has happened. I have gotten adb and fastboot on my mac, and downloaded a factory image from google to try and reflash, but ./adb devices doesn't show anything, even though the phone is connected in fastboot mode. (On the google website it says drivers shouldn't be an issue?). My nexus 5 is running stock, was unlocked before but now still unrooted, its the US version and I have tried connecting to the computer with multiple micro-usb cables (including the one included in the box). What should I do? Or how do I get my nexus 5 to show in ./adb devices?
I'm stumped, any help would be greatly appreciated , thanks!
hanssw said:
Hi Everyone!
Really new to xda so I'm not sure if this is the right place to post this at (sorry). I have a nexus 5 that after I (purposely) rebooted, is now just stuck on the boot animation, (it was not updating to 5.1.0 or 5.0.1). I tried leaving it on but it just kept spinning until the phone died. I can access fastboot, and recovery, have tried wiping cache, and factory resetting multiple times. Nothing has happened. I have gotten adb and fastboot on my mac, and downloaded a factory image from google to try and reflash, but ./adb devices doesn't show anything, even though the phone is connected in fastboot mode. (On the google website it says drivers shouldn't be an issue?). My nexus 5 is running stock, was unlocked before but now still unrooted, its the US version and I have tried connecting to the computer with multiple micro-usb cables (including the one included in the box). What should I do? Or how do I get my nexus 5 to show in ./adb devices?
I'm stumped, any help would be greatly appreciated , thanks!
Click to expand...
Click to collapse
As long as you're able to charge the phone still while it's off you'll have some options.
When you do factory reset, does it complete the process and reboot on its own??
Just saw this thread. You might want to try it out.
http://forum.xda-developers.com/showthread.php?t=2957801
Sent from my 1+1
Mojar7070 said:
As long as you're able to charge the phone still while it's off you'll have some options.
When you do factory reset, does it complete the process and reboot on its own??
Just saw this thread. You might want to try it out.
http://forum.xda-developers.com/showthread.php?t=2957801
Sent from my 1+1
Click to expand...
Click to collapse
Yes it does does complete it, I reset it from recovery, so it completes and when it restarts its still stuck on the loop again for another hour. I'm downloading the file, hopefully it works
EDIT: Already completed the flash using the tool, but the first boot didn't work, reformatting again after the flash.
EDIT 2: Reboot doesn't work after the reformat after the flash.
hanssw said:
Yes it does does complete it, I reset it from recovery, so it completes and when it restarts its still stuck on the loop again for another hour. I'm downloading the file, hopefully it works
EDIT: Already completed the flash using the tool, but the first boot didn't work, reformatting again after the flash.
EDIT 2: Reboot doesn't work after the reformat after the flash.
Click to expand...
Click to collapse
Have you tried flashing through fastboot?? I'll be honest I'm not to knowledgeable on fastboot, maybe someone else would like to chime in for that.
I've used wug fresh nexus tools but you'll need the phone to boot up properly to get into developer settings to turn on USB debugging.
Sorry if I can't help any further.
Sent from my 1+1
Nexus 5 boot stuck
Bro just try to write the following Command in cmd in the platform devices folder
'fastboot devices' instead adb devices. copy the stock image to the Platform-tools folder and just flash it via fastboot commands. mine was stuck in boot animation and did the same
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 there people,
Well I did a big BS tbh. I was running AOSiP(20190407) but I was still having proximity issues now and there (doesn't matter what rom, I've got this for a while), so I flash a miui from time to time(maybe for a driver proximity fix).
Yesterday I remove the password(temporary), booted TWRP, flash miui 9.4.18(latest dev) and because I was in road, I've tried to flash AOSiP(20190407) back which stuck on the AOSiP logo, then I remember I did have the previous version 20190328? if I remember well, BIGGGGG mistake trying to flash that, phone can't boot and goes to TWRP recovery which is fine but when I see the data, well encrypted(scrambled that is) - doesn't asks for password of course
Tried to place a file via MTP(e.g. LineageOS latest or MIUI) without success ..tries to copy it but doesn't really do anything, my thought is to:
Buy a USB Type-C OTG cable or adapter and try to flash LineageOS or MIUI through that, if data are still encrypted then I'd try to put the very same password I had and maybe be lucky?
Any other thoughts? (of course deleting data would solve this but my latest backup is 1-2 months back which will make me very sad to lose 1-2 months of pictures, videos etc)
P.S. I've made a custom microusb OTG cable but using a usb type-c adapter doesn't make it work so I guess it's a pin-issue ..OTG microusb can't work with usb type-c that way, that's why I'm thinking of a usb type-c otg cable/adapter. I have a few microusb jacks laying around, that's why I tried that
Try to boot with latest twrp and see if it unscrabled partition...
AOSP roms do not boot with the latest vendor and firmware. If you flash an older version in twrp you should be good to go.
hocuspocus69 said:
Try to boot with latest twrp and see if it unscrabled partition...
Click to expand...
Click to collapse
I've got the latest TWRP for a while now
hmmm 3.3.0.0 is release but since I can't move the recovery in order to flash it I should do it via fastboot
EDIT: Can't do it via fastboot, doesn't work. I tried I see the device when I run the command well it does nothing hmmm I guess my only hope is with the solution I mention and MAYBE I'd be lucky
EDIT2: Tried again and again now it says "press any key to shutdown" when I issue the command ..maybe USB debugging issue? not sure, well if I can flash miui or something similar via OTG(I'll have the cable/adapter in a couple of days, no phone until then hhahahaha), if I keep trying it's either the first(doing nothing) or the second "change display black display with tiny letters on top left corner saying "press any key to shutdown" - oh well sht happen
M1chiel said:
AOSP roms do not boot with the latest vendor and firmware. If you flash an older version in twrp you should be good to go.
Click to expand...
Click to collapse
The part where I can't access data or write data in the internal memory is an issue so I can't do any "flash" ...I can try with OTG adapter/cable when I get my hands on it
Wish it will work as I'm out of options
I also got the tiny letters in fastboot mode. It turned out that fastboot commands only worked for one of the three usb ports of my laptop. I guess usb 3.0 didn't work.
M1chiel said:
I also got the tiny letters in fastboot mode. It turned out that fastboot commands only worked for one of the three usb ports of my laptop. I guess usb 3.0 didn't work.
Click to expand...
Click to collapse
Well different pc, original cable I flashboot recovery, now on 3.3.0.0 ...still data scrambled
Yeah, new recovery ...pretty same result
I guess I'll have to way an try the "OTG" method I was thinking about
P.S. Trying to move miui in internal storage still does nothing, well I tried. Now I only hope OTG would save me
Not sure if I could fastboot miui without losing data, it's been a while since I use fastboot
I tried with USB OTG adaptor, no luck. It doesn't work(can't see any usb stick) ..FML
Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?
Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.
hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please
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