Related
Alright, day 10 of my epic tale...
Handset: Samsung Captivate SGH-I896 (Rogers)
Computer: (MacBook Pro, WinXP 32bit, Win7 64bit)
Really the story starts about 10 months ago. Captivate boots up one day after a night of charging only to display "Downloading Do Not Turn of Target!!!". No matter what boot method of key combos will change this. Well the phone found its way into the junk drawer and forgotten about. Fast forward to about 2 weeks ago, my current fruit based named device type 4 receives a large blow from my 2 year old causing its all glass front and back to be unusable, parts are now on order. I look into the junk drawer to find a suitable interim replacement. I find my 'ol Samsung Captivate, put the battery in, plug it in and BOOM, it boots just the first day out of the box. Two days later, back to "Downloading Do Not Turn of Target!!!"... Damn. Everything I have tried from my 96+ hours of trial and error has led me here to post. ODIN, Heimdall, Kies, OneClick this, and OneClick that, nothing.
I have had the phone boot up properly twice in ~10 days, the back to Download Mode.
[TL;DR] I'm a n00b, every attempt that you can image and a few you can't. Samsung Captivate will NOT exit from Download Mode.
Thank you for your time,
Nate.
nelliottca said:
Alright, day 10 of my epic tale...
Handset: Samsung Captivate SGH-I896 (Rogers)
Computer: (MacBook Pro, WinXP 32bit, Win7 64bit)
Really the story starts about 10 months ago. Captivate boots up one day after a night of charging only to display "Downloading Do Not Turn of Target!!!". No matter what boot method of key combos will change this. Well the phone found its way into the junk drawer and forgotten about. Fast forward to about 2 weeks ago, my current fruit based named device type 4 receives a large blow from my 2 year old causing its all glass front and back to be unusable, parts are now on order. I look into the junk drawer to find a suitable interim replacement. I find my 'ol Samsung Captivate, put the battery in, plug it in and BOOM, it boots just the first day out of the box. Two days later, back to "Downloading Do Not Turn of Target!!!"... Damn. Everything I have tried from my 96+ hours of trial and error has led me here to post. ODIN, Heimdall, Kies, OneClick this, and OneClick that, nothing.
I have had the phone boot up properly twice in ~10 days, the back to Download Mode.
[TL;DR] I'm a n00b, every attempt that you can image and a few you can't. Samsung Captivate will NOT exit from Download Mode.
Thank you for your time,
Nate.
Click to expand...
Click to collapse
I really don't know that I have a good answer for you but first of all since you've indicated that you've tried several methods including one-clicks... did anything that you tried to flash show in the program you were using that the time that it went through and flashed?
m1batt1 said:
I really don't know that I have a good answer for you but first of all since you've indicated that you've tried several methods including one-clicks... did anything that you tried to flash show in the program you were using that the time that it went through and flashed?
Click to expand...
Click to collapse
No program was able to detect the phone, only one PC was able to detect that something was pluged in (WinXP 32bit), all attempts with various drivers did not change this. However once in a blue moon the phone boots just fine, battery charges I can sync with Mac & PC. This tells me that the general condition of the hardware is good.
nelliottca said:
No program was able to detect the phone, only one PC was able to detect that something was pluged in (WinXP 32bit), all attempts with various drivers did not change this. However once in a blue moon the phone boots just fine, battery charges I can sync with Mac & PC. This tells me that the general condition of the hardware is good.
Click to expand...
Click to collapse
So when the phone is in download mode and you plug it in via usb the computer doesn't recognize it at all? It's not listed on device manager as it should be or unknown?
I could be way off base but it almost sounds to me like your usb port is going bad. If it's shorting out in there it could explain why it's constantly going into download mode. And why every once in a while it actually boots and functions as normal.
m1batt1 said:
So when the phone is in download mode and you plug it in via usb the computer doesn't recognize it at all? It's not listed on device manager as it should be or unknown?
I could be way off base but it almost sounds to me like your usb port is going bad. If it's shorting out in there it could explain why it's constantly going into download mode. And why every once in a while it actually boots and functions as normal.
Click to expand...
Click to collapse
The USB on the phone does charge the batter, if I leave it plugged in and unplug it, it will sit in download mode until the battery runs dry.
Hello to everyone!
I have read everything I could find and tried a long list of things but unfortunately I am at a loss.
So I've come to you, as I can see that here there are a lot of people that have been through a lot.
Long story short: my Lumia 620 had Windows 8.1 GDR2 on it. Some cool thought said: install Windows 10 Insider Prev.
Well it installed, but I then wanted to revert. I first tried to do a hard reset using the button combination and the phone got stuck on the spinning gears.
I managed then to get the phone into the thunder logo mode. Unfortunately Windows Phone Recovery Tool did not recognize my phone.
There were a lot of tries until i came across the way with Nokia Product Support Tool.
So I did what was said there. And my phone got to reboot into a red background with NOKIA logo and a progress bar. It made it to the first quarter and then Nokia Product Support gave an error. I tried restarting the program, the phone, etc... only God knows what I did not try...
Now my phone is stuck at the NOKIA logo with red background and will not be seen either by Thor2, PST, WPRT and I can't even find it in the device manager.
WHAT ELSE CAN I TRY?!
LATER EDIT: I know why it died now.
I recently did the same thing with another 620, but this time the battery was full. I think that the other phone's battery died in the process of rewriting the firmware thus resulting in a hard brick. - mystery solved.
flash your phone
same problem with my lumia 620....flash your phone
Yay, I didn't think of that!
But seriously, I can't - the PC doesn't recognize it at all.
aqibpk said:
same problem with my lumia 620....flash your phone
Click to expand...
Click to collapse
ashesofpain said:
Yay, I didn't think of that!
But seriously, I can't - the PC doesn't recognize it at all.
Click to expand...
Click to collapse
check device manager, does it flick when you connect the phone?
use a usb viewer to uninstall all the drivers related to your phone.
surya467 said:
check device manager, does it flick when you connect the phone?
use a usb viewer to uninstall all the drivers related to your phone.
Click to expand...
Click to collapse
h t t p:// s27.postimg.org/x858v1rhf/Capture4.png
It flicks only when the phone is off, or the battery is out.
As soon as the phone starts up and shows NOKIA in white over red background, nothing exists in Device Manager related to the phone.
ashesofpain said:
h t t p:// s27.postimg.org/x858v1rhf/Capture4.png
It flicks only when the phone is off, or the battery is out.
As soon as the phone starts up and shows NOKIA in white over red background, nothing exists in Device Manager related to the phone.
Click to expand...
Click to collapse
use some usb viewer..uninstall all drivers related to ur phone...reinstall Nokia usb drivers.Restart computer. Try again..u could do a manual dead phone flash with product support tool.
LATER EDIT: I know why it died now.
I recently did the same thing with another 620, but this time the battery was full. I think that the other phone's battery died in the process of rewriting the firmware thus resulting in a hard brick. - mystery solved.
Yes, but can be reflashed
How can it be reflashed?
Can you do a how-to guide?
augustinionut said:
Yes, but can be reflashed
Click to expand...
Click to collapse
Yes you can reflash with nokia flash tool
Turn off your phone.
Note If your phone is currently stuck on the manufacturer's logo, try removing the battery to turn it off.
Disconnect your phone from the USB cable.
Hold down the camera button.
Continue holding down the camera button and connect the USB cable between your phone and computer.
Continue holding down the camera button until you see the connect-to-computer screen.
Release the camera button.
Leave the phone restart alone, will take around 4/5 minutes.
I hope this will surely works for you, if not then visit Nokia Lumia 620 Manual- guideusermanual.com/product-name-lumia-620-manual&po=672223&lang=English for help.
Hey everyone,
My friend came across an unfortunate problem with his HTC One. This is what happened according to him:
For the past few months the battery life was getting worse and became terrible, but it's been otherwise fine in terms of performance.
He was at work playing some music via aux
The song stopped playing unexpectedly
Figured that it was a problem with YouTube was like wtf, so he closed YouTube and tried reloading.
It wouldn't show anything and nothing worked, left it that way as to not mess it up more.
Then it completely froze and he shut it off
Not it wont turn back on at all.
He said he left it plugged in charging for a while, still nothing. Tried overnight, still nothing.
Says he really wants to get at least his pictures out of his phone.
So, what are some troubleshooting steps he can take, or what can he do?
suckafoola said:
Hey everyone,
My friend came across an unfortunate problem with his HTC One. This is what happened according to him:
For the past few months the battery life was getting worse and became terrible, but it's been otherwise fine in terms of performance.
He was at work playing some music via aux
The song stopped playing unexpectedly
Figured that it was a problem with YouTube was like wtf, so he closed YouTube and tried reloading.
It wouldn't show anything and nothing worked, left it that way as to not mess it up more.
Then it completely froze and he shut it off
Not it wont turn back on at all.
He said he left it plugged in charging for a while, still nothing. Tried overnight, still nothing.
Says he really wants to get at least his pictures out of his phone.
So, what are some troubleshooting steps he can take, or what can he do?
Click to expand...
Click to collapse
try to boot the phone while shinning a bright light to the light sensor. (this is protection to avoid booting the phone when its in your pocket)
Press and hold Power and Volume down for at least 30 sec
Connect the phone to a Windows computer using the original usb cable (or any other cable already known to work for data transfer) to a USB 2.0 port on your computer, then go to Windows devices manger, is the device detected as QHSUSB ? Or Qualcomm something?
Hi thanks for the reply.
He said that when he plugged into his PC, QHUSB_DLOAD shows up in device manager. So now what?
suckafoola said:
Hi thanks for the reply.
He said that when he plugged into his PC, QHUSB_DLOAD shows up in device manager. So now what?
Click to expand...
Click to collapse
Since the phone went in QHUSB_DLOAD by itself and randomly, this is an hardware failure, the phone will need a new motherboard. It would be fixable only if the phone went in this mode directly after flashing a (incompatible) firmware. Unfortunately there is no way to recover the data from it since the emmc is soldered on that defective board.
Sorry
Wow damn that's real bummer... so there really isn't anything he could do? I remember him telling me that he wanted to salvage pictures from his graduation, but this problem is not letting him
suckafoola said:
so there really isn't anything he could do?
Click to expand...
Click to collapse
Unfortunately no. Another perfect example why you must backup your important files regularly. Smartphones are unreliable for preserving data, they are not made to last very long (well like everything nowadays ).
I already heard of someone desoldering his emmc chip (not from a M7 btw) and soldering it back to other hardware to extract the data so this is not impossible but your friend would have to find someone really qualified to try this kind of thing and it will probably not be cheap if it can be done..... But no there is no conventional method (using your computer and a usb cable) to extract any data from this phone.
@alray I know it sounds silly, but would it be possibly to save the pics by booting into twrp and copying them to a USB otg?
I'm guessing no
And yeah, it's always a bad idea to keep important files and data on one device.. be it a USB flash drive, an external hdd, a laptop, a smartphone.... etc
there's always the chance of it refusing to work or getting stolen.
monrokhoury said:
@alray I know it sounds silly, but would it be possibly to save the pics by booting into twrp and copying them to a USB otg?
I'm guessing no
And yeah, it's always a bad idea to keep important files and data on one device.. be it a USB flash drive, an external hdd, a laptop, a smartphone.... etc
there's always the chance of it refusing to work or getting stolen.
Click to expand...
Click to collapse
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
alray said:
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
What if it says qualcomm something?
Shining a light method doesnt work, i left it charging for 3 days, nothing, i tried connecting it to computer and turning on, but not working...
boleguc said:
What if it says qualcomm something?
Shining a light method doesnt work, i left it charging for 3 days, nothing, i tried connecting it to computer and turning on, but not working...
Click to expand...
Click to collapse
Doesn't matters what it's saying exactly, it's dead. It's only possible to unbrick a m7 that went in a "Qualcomm something" mode because of a bad firmware flash. If it went in that mode itself, without flashing, your phone is dead.
Sent from my HTC One using XDA Labs
alray said:
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Yeah I expected that lol
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.
Was installing the new build using flash-all.sh (without wipe) as I was rooted with Magisk.
Installer got stuck halfway. Disconnected, tried booting, got an error message saying device may have been corrupted or something like that.
The phone doesn't boot at all now, not even to the bootloader. Literally nothing shows up on the screen.
Any help would be greatly appreciated.
Double-check your download and make sure you have panther for Pixel 7.
Depending on what is corrupted, it may be very difficult to recover. With Qualcomm SoCs you can use a low-level tool like QPST (Qualcomm Product Support Tool). For Exynos you can often use ODIN. For Pixel, ODIN doesn't work and there aren't any QPST files (prob never will be).
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.
Hung0702 said:
Double-check your download and make sure you have panther for Pixel 7.
Click to expand...
Click to collapse
Yes, the images are for panther.
Hung0702 said:
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.
Click to expand...
Click to collapse
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.
V0latyle said:
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.
Click to expand...
Click to collapse
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .
hammered58 said:
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .
Click to expand...
Click to collapse
The Android Flash Tool works via ADB, so if the bootloader is corrupted or fails for some reason, that isn't an option.
Pixel devices (at least Snapdragon ones) do have the Qualcomm USB mode, but Google's prescribed means of repair in this situation is to simply replace the mainboard; most repair stations do not have QPST or the necessary files to restore the bootloader.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.
In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly
Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got
Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder
dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!
Vio281 said:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.
Click to expand...
Click to collapse
Not really. That’s how I broke it while updating. My phone wouldn’t boot at all and wasn’t even detected by my mac and windows pc. Had to send it to the service center.
t3chwizard said:
In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly
Click to expand...
Click to collapse
Thanks, I will do that.
J0nhy said:
Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got
Click to expand...
Click to collapse
It was just a black screen. It wouldn’t boot into any menu whatsoever.
Sui77 said:
Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder
Click to expand...
Click to collapse
Yes, that’s how I initially updated which somehow broke it. Anyway, got it repaired for free since it’s in warranty.
grandpajiver said:
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!
Click to expand...
Click to collapse
Hi, I had to send in the phone for a repair. It was a free repair since the phone’s in warranty.
That happened to me with Pixel 6 Pro. The screen only showed the charging icin and wouldn't respond and the phone was getting hot. I ended up rebooting it by holding the power key and one of the volume buttons (don't remember which one) for like 30-40 seconds and that rebooted it and from there I got to recovery mode and flashed the image via sideload.