Related
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
So I rooted my G4 a week ago. Everything was fine, was running a stock rom, no issues whatsoever. So today, I was watching a YouTube video when my phone froze. Couldn't do anything, had to pull the battery. Then it wouldn't come on after putting in the battery. I pulled it again and left it out for about 10 mins, put it in, put it on a charger and it started charging. Turned it on, the date/time was wrong, kept saying it was July 21st and 2:38 pm. Went into settings and updated the date/time; was working after that.
I left it on the charger and went on with my day. Came back and the phone was completely off, no charging LED. So it's been like this all day, it won't charge (at least the LED indicator doesn't come on), won't turn on, nothing. I figured the battery was shot. I went over to my buddy's (he has the same phone) and tried his battery in mine, nothing. I tried my battery in his and it worked, so I've established it isn't a bad battery. I've tried everything so far, keeping the battery out and holding down power so it resets it's charge, EVERYTHING, etc.
When it did come on and it was displaying the wrong date/time, that was the day I rooted it and about the time it was rooted too (2:38 pm). So, has this happened to anyone else? Am I bricked/screwed? I just don't understand why it would just die all of a sudden. It's well taken care of, no damage or anything. I really don't know what to do, I'm in a rough spot right now and not having a phone is really going to make things even worse.
Was just curious if somebody could help me with this or has any other info.
Thanks in advance!
I'm going to try the Unbrick Guide on here, hopefully that works.
So I was able to get it into download mode but then it died on me. The battery only had a 40 percent charge and now it won't do anything (again). Does the battery need to be charged at least to 50% or more in order to get in into download mode?
Though the classic bootlooping issue is just that--the phone locks up and freezes, and then on restart continuously reboots to the LG logo--the underlying problem causes a whole spectrum of conditions. For example, some affected phones will just shutdown during boot, and not continuously reboot. The stage at which the shutdown occurs is also variable--it can happen before the LG logo appears, after it appears, after the carrier logo appears, etc. The point is that the bootloop issue is not always expressed as the classic continuous rebooting to the LG logo issue. What you describe with your phone definitely falls within the spectrum of what is possible so I am going to guess that you have been hit with the bootloop issue like many others.
This just happened with my wife's VS986 after 1.75 years of flawless service. She was using it last week, then bam, it froze up, and after that it was dead. On trying to restart it immediately, it was completely dead. But by letting it sit around for a while to cool down, it could boot to the LG logo and sometimes would do this 2-3 times before shutting down again. By placing it in the freezer to really cool it down, I could boot up past the Verizon logo, but then during the Android optimizing apps screen, it would fail again. So out of the blue--after 1.75 years of perfect service--bam, it was struck with the bootloop issue.
Though I had seen mention of the bootloop issue previously, I never really investigated it till my wife's VS986 was strickened. If you do a search on it, you will see it is extraordinarily common...
Fortunately, LG is now taking responsibility for this though they were basically denying there was a problem initially. The good part is that they are repairing phones with this particular issue for free of charge even if they are out of warranty. In my case, my wife's VS986 was clearly out of warranty, but when I called up LG and explained the problem, they said they would repair it free of charge. So they steered me to the lgmobilerepair.com website to set up repair service.
They supposedly fixed my VS986, and it is now being shipped back. Curiously, they identified the problem as "Unit is not charging with cable" with the repair being "Swap Board (Main/RF) : Others". By the way, this was definitely NOT just an issue of not charging--I have an H811, and on putting my H811 battery into the VS986, the VS986 had the same problem. And on putting the VS986 battery in my H811, it worked perfectly. Whatever the case swapping the mainboard is the solution, and they did that, so they can call it whatever they want.
Anyway, do a little bit of searching on the G4 bootloop issue, try the freezer test, etc., and I am guessing you will also become convinced your G4 has been hit by the bootloop issue. If so, call up LG, explain the problem, and I bet they will offer to repair it for free. Hope this helps, and do let us know the results!
Awesome response! I'm aware of the class action against LG, but with my phone being rooted I don't think it's the best option to contact them and it's out of warranty. I do not have a bootloop issue, my issue is I cannot get the phone to go into download mode. I really hope it isn't a main board issue like you had, that means I have no way of fixing it.
I was able to get the phone into download mode, this was right after I connected it to the PC via USB and held the volume down button while connecting it, it just came on. I was able to get to the T-Mobile splash screen then it started making a weird noise (almost like PC when it locks up, a high buzzing sound). I was able to then get it into DL mode (holding volume up while connecting) but it died on me during that phase or froze. After pulling the battery then, it will now not do anything. I'm optimistic that if I can get it back into DL mode I can flash the stock KDZ and get it working again. I will let you know what happens. After spending almost all day messing around and hassling my buddy for his battery (same phone, he charged his battery to 100% and let me use his, he's using mine) I'm going to have some beers and play Titanfall 2. I'll pick it back up tomorrow. Worst case is I have to get a new phone and I just don't have the means of doing that ATM.
Regarding your phone being rooted, my wife's VS986 was rooted as well. This did not even come up in conversation with the LG. Even though her VS986 was clearly out of warranty, as soon as I started to explain the symptoms I was seeing, the LG rep (without mentioning the word "bootloop") said he recognized the problem, and that they would repair it for free. In sum, at least in my experience, having the phone rooted did not make one iota of difference. I guess the takehome message is that this issue has obviously reached levels far greater than the average 5% electronics failure rate--LG recognizes it is a hardware problem, and is prepared to deal with it (even on rooted and out of warranty devices).
You said your phone does not have the bootloop issue, but I invite you to investigate it further because the bootloop issue is not strictly confined to continuously bootlooping as I tried to explain originally. What you have described completely fits within the spectrum of observed issues related to the bootloop issue. Question for you--when you turn on your phone, is it normal that it shuts off at some (whatever!) stage of booting? You said that at point you actually got into download mode, but then it failed there--is that the normal/expected reality? No, it's not, and this behavior is definitely one type of expression of the bootloop issue... And as you reported yourself, you boot seem to fail at a range of different spots, not always consistently at the same moment. If it were a software problem, wouldn't it always happen at the same stage? That it happens at different stages of the boot process suggests an external control, i.e. a hardware issue.
You asked about the freezer trick--let me roll things back a bit, and I'll get to this in a minute. The bootloop issue is supposedly related to a failed electrical connection for a component on the phone mobo, and so how far along the boot process actually gets before failing gets is related to thermal expansion of components, at least this is my guess. As I mentioned, when my wife's phone originally locked up, on trying to restart it immediately, it was completely dead, no LG logo no anything. But after letting it sit untouched for a couple hours to cool passively, the boot process would at least advance up to the LG logo, but then fail. After this, if I tried to reboot again while the phone was still warm, again, complete failure (not even reaching the LG logo) until I let it sit and cool for a while. This is all related to the freezer trick...
I read that on freezing their phones, some people were able to boot as far as the homescreen, and have a few minutes to rescue their contacts and photos before subsequent failure. So I tried that with the VS986, and was even able to get past the Verizon logo as mentioned above. But failure occurred during the optimizing apps stage, and I could never reach the homescreen. Whatever the case, this freezer trick simply works because of thermal contraction--by cooling the phone down enough, the components contract rebridging the failed electrical connection, and if it can can stay cool enough for long enough, you might actually have a few minutes to rescue things before failure.
There are some other data rescue techniques, too, and though you do not seem to be concerned about rescuing data, I mention them because they also point to this thermal issue. In particular, besides freezing, some folks have tried exactly the opposite--intense heating--and they have been able to get a few minutes of data rescue time out of their phones. This involves heating the back of the phone with a hair dryer until it is close to burning hot, and then trying to boot. This certainly works because of thermal expansion--heating the phone up so much causes everything to expand which literally forces the components back together bridging the failed electrical connection temporarily until the component heats up internally, and overcomes this extra pressure.
Another data rescue technique involves adding a spacer above the CPU to cause more force pressing down on the component to bridge the connection failure. And some people have literally ironed their CPUs in attempts to resolder things, and have had various levels of success. But in the long run, all of these attempted repairs to phones with the bootloop issue have the common characteristic of rebridging the failed component connection temporarily, and that is key here--they are only TEMPORARY. They work for anywhere from 1.) not at all to 2.) a few minutes to 3.) a few hours to 4.) a few days, but in the long run, they are temporary, and mobo replacement is needed.
Anyway, I encourage you to investigate the G4 bootloop issue a bit more before you conclude that your phone is not affected. And furthermore, in the long run, if you do conclude that it is afflicted by the bootloop issue, contact LG about it, and they will probably repair it for free. Don't fear about being out of warranty or having rooted the device--at least in my case these things did not matter!!!
---------- Post added at 11:53 AM ---------- Previous post was at 11:47 AM ----------
I have reread your description above, and now even more think you may have the bootloop issue! You wrote that you were able to get into download mode, but then it failed, and then it would not do anything. This is exactly my experience with the VS986--immediately after a failure when it was still hot, if I tried to restart it, bam, nothing, not even the LG logo. But if I let it sit around a while to cool, it then was willing to show some semblance of life. Let your phone sit around after the next failure to cool down a bit, and I bet that after that, again, you will start to see a few indications of life instead of it being completely dead. If so, this should convince you even more that this is a hardware-level issue, and not simply a matter of being able to get into download mode to reload the OS.
Well I let it sit without the battery for about 14 hours, tried it again today and nothing. It won't turn on, won't charge, no LED indicator, no download mode, no safe mode, nothing lol. I'm convinced it's completely dead at this point.
MTN927 said:
Well I let it sit without the battery for about 14 hours, tried it again today and nothing. It won't turn on, won't charge, no LED indicator, no download mode, no safe mode, nothing lol. I'm convinced it's completely dead at this point.
Click to expand...
Click to collapse
A suggestion--remove the back cover and battery, put the bare phone in the freezer for an hour in Ziploc bag, then pull it out, immediately put in the battery, and see if you can get some sign of life out of it. Obviously, this is not a long-term workable solution, just an experiment to see if you can get any signs of life out of it at this point. When you finally decide to let it warm up, do so while it is in the sealed Ziploc bag so it avoids direct condensation.
Whatever you conclude about your phone, the G4 is still a nice piece of equipment with a great camera even though it was released over two years ago. So repairing it is worth the effort if LG will do it for free. If you live in the US, their contact number is 800-243-0000. I'd suggest calling them up, explaining that out of the blue, the phone locked up, and since then, even though you have been able to do partial reboots a few times, it would always shut off during one of these boot attempts. Now it doesn't boot at all. There is no reason to mention that you rooted your phone a week ago (unless you want to...) because again, this is a well-known hardware problem that they know about, and that they are repairing even for phones that are out of warranty.
Admittedly, sending the phone in for repair is a bit of a hassle. In my case, I had to foot the shipping bill out to the repair facility in Ft. Worth, TX, but the turn around time was super fast. Indeed, it arrived to the facility this past Monday according to tracking, but was not actually checked in to their RMA system until Wednesday night. Notwithstanding, by Thursday evening, they had diagnosed it, replaced the mobo, and put it into Fedex shipping back to me all at no cost! I expect you would have a similar experience if you contact them to explain the problem like I have suggested.
Good luck, and let us know how the saga ends!
Your freezer trick worked! For now at least, I have the phone in DL mode but the KDZ I tried to flash gets stuck at 9% when using LGUP, I think I need to find the right KDZ to flash, looking for that currently...
UPDATE: Dead again, lasted in DL mode for maybe 10 or so mins. If that KDZ I had was right it might've worked, gonna refreeze and try again with a different KDZ...
So MTN927, I think the evidence is pointing to a hardware problem... It seems that you are thinking that this is a software-level problem, and that by reloading the correct KDZ, the phone will return to normal. Why would freezing the phone have any effect on a software-level problem? Of course, freezing the phone could clearly have an effect on a hardware-level issue.
I am not really a betting man, but at this point, I suspect that even if you find and load the correct KDZ, it will not solve your phone's problem because it appears to be a hardware-level issue. Whatever the case, give it a shot, and here's to hoping my logic above is incorrect!
Here is a possible technique that might give you a few more minutes to load a KDZ--after you freeze the phone, don't take it out, just let it sit there. And then, run a USB cable into the freezer to plug into the phone. I'm not sure it will buy you much more time, but maybe it will be just enough to get a KDZ loaded?
That's what I'm thinking, hardware and not software now, obviously.
I suggest you investigate the possibility of LG fixing it for free. Though it's a hassle to be without your phone for 1-2 weeks, at this point it's not working anyway so what do you have to lose? The G4 is still a great piece of equipment so repairing it is worth the effort.
verbage said:
I suggest you investigate the possibility of LG fixing it for free. Though it's a hassle to be without your phone for 1-2 weeks, at this point it's not working anyway so what do you have to lose? The G4 is still a great piece of equipment so repairing it is worth the effort.
Click to expand...
Click to collapse
Yea, that's gonna be the last resort. I'm checking to see if I can get a new phone right now with my carrier. Thanks for all your help though, you've been great. Honestly, if I can get it fixed for free then sure, but I'm not too confident in the phones future considering what's already happened.
MTN927 said:
...but I'm not too confident in the phones future considering what's already happened.
Click to expand...
Click to collapse
I will not be any less confident with my wife's repaired VS986, in fact, given that they replaced a known defective component, I think I will be more confident! Good luck with your replacement--here's to hoping your carrier is willing to help out given the G4's known history.
On April 6, my Mi 9 started turning off at random times - I tried but was not able to reproduce it, so could not identify the root cause to any app / battery level / etc. I could turning it on again by just pressing the power button. It would be stable for a couple of hours until it would shut down again.
On April 7, same symptoms shown, but just pressing power would not turn it on again. I had to press volume up and power, get to recovery menu and mark "reboot to system".
On April 8, same symptoms show, but this time, no key combination would turn it back on. If I connect the charging cable to power, no led would blink and there was no battery charging animation. Connecting to the computer, there was no USB device identified. It was dead.
On April 9, in the morning, while trying to turn it back on, it would blink the notification led twice, but that was it. So I sent it to a service repair shop - not a Xiaomi authorized service repair.
On April 13, the service repair shop has provided me a quote for fixing the phone: reformatting the phone. Since for me this was a hardware and not a software problem, I collected the phone back.. and it was working as if nothing happened, no software was updated.
On April 14, it shut down again, twice. Pressing the power up worked fine.
On April 15, I unlocked the bootloader and flashed the software again with MiFlash on fastboot mode.
The phone is now stable, although it's my secondary phone now - so I use it much less frequently. But since I have no idea what triggered the problem, I don't know if the phone is stable enough, or if the issue will repeat at any minute - especially when I most need the phone.
Also, I tried contacting the service shop technician, to check if he reconnected the battery cable or checked for any short circuit on the board, but couldn't because of the lockdown. So I have no idea why phone is back from the dead, and no idea if/when it will turn itself randomly again.
So my question to the experts:
1) What could have caused this issue with the phone? What are the possible ways to monitor / check what could have caused the issue? Is there any way to capture a crash report after fact?
2) How can I ensure that this won't happen again? I already reflashed the phone, but I wonder if I should do something else..
3) What can be done to try to reproduce the issue? If there is a way to learn from the phone crashing, what are the things I can do to improve the odds of the phone crashing again?
Thanks!
Update: I left the phone to be serviced... and they could not find any issue with the phone. It is now working, but I'm pretty sure in 1 or 2 days it will stop entirely again...
.. and have no way to monitor it
tha same problem here. my mi9 suddenly died! what can i do? waiting the service or buy a new one?
the same problem, my phone just suddenly said the system was destroyed
Same problem here. Service said "no warranty - damage due to damp"
I doubt it. But now I have to handle it on my own.
@lusp00ky: Does your phone still work after you re-flashed it?
Still hope the best ;-)
bollacken said:
Same problem here. Service said "no warranty - damage due to damp"
I doubt it. But now I have to handle it on my own.
@lusp00ky: Does your phone still work after you re-flashed it?
Still hope the best ;-)
Click to expand...
Click to collapse
Unlock BL and clean flash did not work for me.
Now it is dead until the battery is drained. After that it can be brought to live again by a charger.
I don't get it. -.-"
Hello XDA community yesterday I was using my pixel phone normally and it was working fine today morning I woke up to check time on my phone but my phone was dead, screen was completely pitch black, charging phone doesn't work screen stays dead, even its not going to bootloader it feels like phone is completely dead but when I connect it to pc I hear connection sound and a random pop up show that device is not detected etc. I searched on internet and it feels like when I was sleeping because my phone was on charging and WIFI was connected( normally I don't use WIFI I use mobile data) maybe a software update was installed which made phone software & drivers to get corrupted because nothing is working nor its charging, booting, vibrating its completely dead
I searched on internet and also installed QUALCOMM drivers on my pc that unknown popup while connecting while to pc shifted into
Qualcomm HS-USB QDLoader 9008
and I also get know that a firehose file can maybe fix my phone because maybe bootloader is corrupted or anything if anyone can help me in this matter I will really appreciate it. Thanks!
Noman8 said:
Hello XDA community yesterday I was using my pixel phone normally and it was working fine today morning I woke up to check time on my phone but my phone was dead, screen was completely pitch black, charging phone doesn't work screen stays dead, even its not going to bootloader it feels like phone is completely dead but when I connect it to pc I hear connection sound and a random pop up show that device is not detected etc. I searched on internet and it feels like when I was sleeping because my phone was on charging and WIFI was connected( normally I don't use WIFI I use mobile data) maybe a software update was installed which made phone software & drivers to get corrupted because nothing is working nor its charging, booting, vibrating its completely dead
I searched on internet and also installed QUALCOMM drivers on my pc that unknown popup while connecting while to pc shifted into
Qualcomm HS-USB QDLoader 9008
and I also get know that a firehose file can maybe fix my phone because maybe bootloader is corrupted or anything if anyone can help me in this matter I will really appreciate it. Thanks!
Click to expand...
Click to collapse
Did you try both
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
already?
Here is a guide on how to get ADB working:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Do you have OEM Unlocking enabled? Maybe unlocked bootloader (if your bootloader is dead and you haven't unlocked it previously, there might not be much hope for you)? If you can't even get into recovery/fastboot mode, you are in deep.
Morgrain said:
Did you try both
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
already?
Here is a guide on how to get ADB working:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Do you have OEM Unlocking enabled? Maybe unlocked bootloader (if your bootloader is dead and you haven't unlocked it previously, there might not be much hope for you)? If you can't even get into recovery/fastboot mode, you are in deep.
Click to expand...
Click to collapse
Yes i have tried both nothing is working my phone was fresh it wasn't rooted,its bootloader was locked it was basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i hear connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Noman8 said:
Yes i have tried both nothing is working my phone was fresh it wasn't rooted,its bootloader was locked it was basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i hear connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Click to expand...
Click to collapse
You might want to wait some time, until the battery runs out/depletes. Then try to charge it/start it. But that route will take a couple of days.
Noman8 said:
No my phone was fresh it wasn't rooted,its bootloader was locked it basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i head connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Click to expand...
Click to collapse
Morgrain said:
You might want to wait some time, until the battery runs out/depletes. Then try to charge it/start it. But that route will take a couple of days.
Click to expand...
Click to collapse
Ahan i see btw thanks for replying!
Noman8 said:
Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
Yes, your pixel is now dead. Similar to what happened with my Pixel 2.
NinjaCoool said:
Yes, your pixel is now dead. Similar to what happened with my Pixel 2.
Click to expand...
Click to collapse
Yes
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
r1pp3d2 said:
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
Click to expand...
Click to collapse
hi brother can it be fixed with firehose? please reply
and what are exact steps to flash Firehose!
r1pp3d2 said:
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
Click to expand...
Click to collapse
i am trying to flash this firehose to my pixel but it is requiring 2 more files "RAW PROGRAM & PATCH" FILE if u can help me here i will appreciate that!
That would be the backup of the phone. These are not backups.
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
nicauderan said:
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
Click to expand...
Click to collapse
Google doesn't just kill phones like that. My Pixel 4XL is still find, hell my Nexus 6 still works.
nicauderan said:
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
Click to expand...
Click to collapse
You are not getting your pixel back now u can replace motherboard now like i did i ordered new motherboard from ali express and Replaced it!
Just received motherboard from Ali and the pixel respawned.
Was charging my pixel 4, it was 100% charged for a good few hours, I woke up around midnight and was playing a game on my phone when suddenly it went black. I unplugged the phone and tried a few fixes. After crying it out and leaving it uncharged I plugged it into my portable charger where the lights came on, still nothing on my phone. I also tried plugging into my computer and no sounds or any sign it had been plugged into my computer from both phone or computer. I was thinking if this is a battery issue it should at least do something on my computer right? I have tried again to plug it into my portable charger and this time no lights on the portable charger. Maybe this isn't the right thread but I figured I'd post here anyway, any suggestions, should I take it to a shop? I'm not tech savvy, could it be a display or battery issue or a motherboard issue like above?
also to note, I had both the front and back glass changed almost a year ago now, and except from one dead pixel on the screen from the original glass break its been fine.
Also to note, I recently moved from Australia to Canada and am using a plug converter that my laptop computer is also plugged into and its fine, so I'm thinking it wasn't a power surge? It has two usb ports and a Au plug on the same converter plug.
Oh, you are not alone. 3 days after Android 13 update, I woke up, my Pixel 4XL alarm went off, used Android Auto to go to work and listen to music, checked email on it at work, plugged it in to my Pixel approved charger/cable as always, picked it up hours later and .... brick. No response to charger plug/unplug even with various other plugs and cables. No response to 30 sec of pressing power or power with up/down volume combos. It was a brick, just like many other Pixel 2,3,4,5 owners reported after various updates over the years, courtesy of Qualcomm chips and Google's lack of quality checking chips. Today's lesson: Stop paying Google for trash. It happened to me 280 days after the warranty expired. Google said that if it was from the Android 13 update, I should take it to UbreakitIfixit near me and they will fix it under an extension of 1 year to the warranty. We'll see. Sadly, it will still have Google's low grade Qualcomm chip design after the repair.
Tl;Dr - my pixel 5a5g got the black screen of death a few months ago. Last night, I tried using the flash tool to try to flash it back to Android from GrapheneOS - so that Google would be willing to fix it maybe. Flashing seemed to fail. Unsure what to try or do next.
---------------
My Pixel has had the black screen of death for a few months now. I'm assuming it is from falling a few feet to the ground. It had a custom ROM - GrapheneOS - on it. Unless I can reflash to stock Android, it sounds like Google/ubreakifix won't look at it, and thus - no chance of repairing it for free or a smaller charge.
The other night, I tried attaching an OTG keyboard to the phone to log in to it. Since the display is black, I'm not sure it worked. I also tried several times to press where I thought the numbers for logging in would be - on my completely black screen. Somehow, I was eventually able to get my PC and Google's flash tool to recognize the phone. However, I might have messed up on some steps - because I think it might be bricked now.
I think I forgot to remove the grapheneOS key via their Web installer before trying to flash android. I used minimal abd tools to unlock the bootloader (and it still says it is unlocked)... When I tried flashing back to stock android using the android web tool, it went through the motions, but then said something like it needs to detect the phone again after flashing. And it wouldn't detect the phone again. Even if I unplugged then replugged the phone. The directions said I shouldn't/wouldn't need to press any keys on the phone for this step, but it just wasn't progressing further... So, I ended up holding the power button and volume down button - and it went into fastboot(?) again - or whatever that does.
I can repeat the steps of going thru the motions of flashing the device now, but now it gives an error saying something like it can't lock the device.
Being that the 5a screen is completely black, I have no idea what is going on - or what to do from here. I've reached out to some local repair places, but honestly, if I can't flash it myself to stock so that Google/ubreakifix would look at it, then it probably isn't worth sinking money into.... There's decent condition used ones around $120 or something out there... And ubreakifix would probably charge between $160 and $200 for screen replacement + labor - and I'm assuming that's not including a motherboard replacement - if necessary.
Ubreakifix said that they would be willing to look at it, but they can't actually do any repairs to it if it isn't running stock Android. They'd charge for the labor, and they'd temporarily use a screen to look at what it is doing/not doing... But wouldn't actually do the screen repair. I'm assuming the phone never flashed completely, but I'm hoping they can tell me if their diagnostic tools work on it - since I imagine it should work -- IF stock Android is actually installed again on it.
I've also looked into doing something like getting a displaylink adapter + display link app so that I can see the screen on the computer... But even after my multiple attempts of logging in to the phone, I can't send app downloads to the phone. Google Play store shows that the phone was "last seen" months ago... And even if I could push the app download, GrapheneOS still requires manual approval from the user to accept/finalize install of the app... Which would be pretty hard to do without seeing the screen. And obviously since I've tried flashing the phone several times last night, i have no idea what the phone is looking like. Probably app downloads are out of the question now.
Apparently you can't normally do display out of any sort with Pixel phones. The rumor I've seen on here and/or reddit is that Google got rid of it years ago, maybe so that they can sell more Chromecasts...
Does anyone have any further suggestions? I could try using scrcpy or whatever it's called, but I probably should have tried to use that before attempting to flash the phone... It's sure hard to give up on something that I spent good money on. I'd like to think there's something I haven't tried yet that I can do to save it...
You could probably try these steps:
1. Open up Device Manager on PC
2. Connect your phone
3. Hold Power + Volume Down
If you have new device in Device Manager, you can do everything with your device like flashing or try "to remove the grapheneOS key".
Edit: I'm dumb and didn't notice that part where you tried this. You should just boot into fastboot and remove that custom AVB key with fastboot erase avb_custom_key, and then reflash the phone on flash.android.com. Hope that helps!