Hi! I've tried to update my Pixel 6 Pro using ROM from google's website and after loading the bootloader my phone went black and stopped responding.
It doesn't show up on the computer, but I hear the "device connected" sound when I hold the power button, and "device disconnected" as soon as I release my finger from it.
Hi! Which image file did you use? Are you sure it was for Raven? Or did you use Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
Also, try that site if you haven't already. It's fixed many (but not all) issues others have had with their Pixel 6 Pros. If you flashed the image for a different Pixel, however, the only thing you can do is RMA it back to Google to fix it.
roirraW edor ehT said:
Hi! Which image file did you use? Are you sure it was for Raven? Or did you use Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
Also, try that site if you haven't already. It's fixed many (but not all) issues others have had with their Pixel 6 Pros. If you flashed the image for a different Pixel, however, the only thing you can do is RMA it back to Google to fix it.
Click to expand...
Click to collapse
Hi! The May ROM, for raven. The biggest issue is that my pixel doesnt show on the computer anymore, no signs of life other than "device connected/disconnected" sound
Try rebooting the PC? Different USB cable, different USB port? Got a spare PC to try? Seriously, try Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own) though - it's worth a shot, even if it won't be that simple.
Ok, probably better list all the things I've tried:
- PC reboot (no help)
- Another PC (same)
- Different cable/Different port
The Flash Tool needs the phone to be seen by the PC, which for some reason is not happening.
The bootloader was unlocked when I tried to install the update
Try pressing the power button continuously for over 30 seconds? I forget if it's necessary to combine it with one of the Volume buttons. That should force it off if it's not already, then hopefully you can start over from scratch.
roirraW edor ehT said:
Try pressing the power button continuously for over 30 seconds? I forget if it's necessary to combine it with one of the Volume buttons. That should force it off if it's not already, then hopefully you can start over from scratch.
Click to expand...
Click to collapse
Didnt help either. The phone is off and pc does 'connected/disconnected' sound three times and that's it...
Efosamark said:
Didnt help either. The phone is off and pc does 'connected/disconnected' sound three times and that's it...
Click to expand...
Click to collapse
In addition to what the @roirraW "edor" ehT said, do you have the latest drivers installed?
Also, when you initially flashed the factory image (flash-all.bat I presume?), were you using the latest Platform Tools?
Lughnasadh said:
In addition to what the @roirraW "edor" ehT said, do you have the latest drivers installed?
Also, when you initially flashed the factory image (flash-all.bat I presume?), were you using the latest Platform Tools?
Click to expand...
Click to collapse
Yes.
One more thing: while I hold down the power button, the device breifly appears as "USB Composite Device"
Efosamark said:
Yes.
One more thing: while I hold down the power button, the device breifly appears as "USB Composite Device"
Click to expand...
Click to collapse
Does the phone charge?
roirraW edor ehT said:
Does the phone charge?
Click to expand...
Click to collapse
No indication of that
A last-ditch effort that I can think of: Try booting to safe mode? Otherwise, an RMA might be necessary, although I'd leave the phone alone for a good long while and check it again later. Sound crazy but this has helped me more than once, although I haven't had to do that on this device yet.
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Click to expand...
Click to collapse
roirraW edor ehT said:
A last-ditch effort that I can think of: Try booting to safe mode? Otherwise, an RMA might be necessary, although I'd leave the phone alone for a good long while and check it again later. Sound crazy but this has helped me more than once, although I haven't had to do that on this device yet.
Click to expand...
Click to collapse
Probably will try to leave it alone for couple of hours...
And just a heads up - no luck.
I guess I'll try and contact Google to get a replacement or something
Efosamark said:
And just a heads up - no luck.
I guess I'll try and contact Google to get a replacement or something
Click to expand...
Click to collapse
Good luck! I hope things go well with a minimum of pain.
Related
Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!
crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links
malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).
For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.
The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.
Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
LG gpad 8.3 vk810 . After installing a tweak for gaming graphics I stupidly bricked my tablet. Im new to rooting and android in general. The device gets stuck at LG symbol. I've tried clearing cache, and factory reset through holding the power and volume down. From what I've seen the next step would be to get it into download mode and use a LG utility, but I cant get it into download mode, also I imagine I need the right firmware once I do, Im very confused and just want to be able to use my tablet again. Thanks in advance.
Hi, did you look at my stickied guide for the VK810 in the General section?
Until you manage to get it into Download mode, there's nothing else to try. Perhaps some of the info I have in that thread will help you get that far.
roirraW "edor" ehT said:
Hi, did you look at my stickied guide for the VK810 in the General section?
Until you manage to get it into Download mode, there's nothing else to try. Perhaps some of the info I have in that thread will help you get that far.
Click to expand...
Click to collapse
Sorry, I can't seem to find it. As you can see I joined the forum yesterday.
iflow43 said:
Sorry, I can't seem to find it. As you can see I joined the forum yesterday.
Click to expand...
Click to collapse
In the General section, there's four "stickied" threads at the top. The thread I'm referring to has the title "[VK810.4G] [altev] most reliable way to root and install a custom recovery " and I also link to in my signature below.
I did look at it, I couldn't really find help there, truthfully I don't know what's going on even more than before haha. I cant get into download mode even by holding volume up and down then plugging in the usb, it just goes to the charging screen. Hell I wouldn't even mind no longer having root, I just wanted to be able to make use of my tablet while I'm still on contract till November. But thank you for the help. I believe I'm going to be using it as a paper weight until I can cancle that line through Verizon.
iflow43 said:
I did look at it, I couldn't really find help there, truthfully I don't know what's going on even more than before haha. I cant get into download mode even by holding volume up and down then plugging in the usb, it just goes to the charging screen. Hell I wouldn't even mind no longer having root, I just wanted to be able to make use of my tablet while I'm still on contract till November. But thank you for the help. I believe I'm going to be using it as a paper weight until I can cancle that line through Verizon.
Click to expand...
Click to collapse
On the VK810, you don't hold both Volume buttons to get into Download mode. With the tablet off, you hold the Up Volume button only while plugging it into a PC's USB 2.0 port with the original cable. Keep holding the Up Volume button for a few moments and you should see the extremely dim "Download mode" logo in the center of the screen. Sometimes it's barely noticeable.
You already had the drivers installed, right? Then reboot the PC after installing the drivers.
The first time you plug the device in Download mode to a new USB 2.0 port, or can take up to 10 minutes for the PC to load the driver. You'll see the tablet listed in Window's Device Manager in the Modem section.
Pretty sure my guide I mentioned also tells the way to get into Download mode.
roirraW "edor" ehT said:
On the VK810, you don't hold both Volume buttons to get into Download mode. With the tablet off, you hold the Up Volume button only while plugging it into a PC's USB 2.0 port with the original cable. Keep holding the Up Volume button for a few moments and you should see the extremely dim "Download mode" logo in the center of the screen. Sometimes it's barely noticeable.
You already had the drivers installed, right? Then reboot the PC after installing the drivers.
The first time you plug the device in Download mode to a new USB 2.0 port, or can take up to 10 minutes for the PC to load the driver. You'll see the tablet listed in Window's Device Manager in the Modem section.
Pretty sure my guide I mentioned also tells the way to get into Download mode.
Click to expand...
Click to collapse
I flashed 4.2.2 from you, installed twrp now im at the step of installing the 36b update downloaded from you with twrp, will i lose twrp when i do this? only reason i want to update is so i can chromecast my screen
iflow43 said:
I flashed 4.2.2 from you, installed twrp now im at the step of installing the 36b update downloaded from you with twrp, will i lose twrp when i do this? only reason i want to update is so i can chromecast my screen
Click to expand...
Click to collapse
No sir, as my instructions give in both the threads for my ROM and my guide for the easiest way to root and put TWRP on the VK810, you'll still have TWRP. The only caveat is that every time you want to switch from being able to boot the 36B ROM, you'll have to temporarily re-downgrade your bootloader (aboot.img) to 4.2.2 *again*, just so you can get into TWRP. Then when you're done in TWRP, you have to flash the 36B bootloader zip that I provide otherwise the ROM won't boot. You'll continue to still be able to get into TWRP if you forget, until you remember to flash the 36B bootloader zip.
Hi All,
Request all to provide any suggestions related to the below issue:
I rolled back from android n preview 2 to android m after which my display is scrambled.I am not able to view any thing on it.
But I am getting calls and able to pick them when I roughly expect the place where I can swipe the dialer right to pick the call.
Few things that I want to highlight is :
1)I had unstable wifi connection while downloading the android m OTA.
2)I removed the unlock bootloader check before rolling back in the developer options.
3)I can also sense that i am able to take screen shots when I am holding the power button and the volume down button based on the sound it normally makes (while capturing screenshots)
I am not able to come to conclusion whether this a hardware issue?(may be i need the replacement of the screen) or can it be due to corrupt ota file update?
Any suggestions would be much appreciated.
thanks
I would first see if flashing the m factory image solves the issue. Then look at hardware.
k.s.deviate said:
I would first see if flashing the m factory image solves the issue. Then look at hardware.
Click to expand...
Click to collapse
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
NeverBackDown said:
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
Click to expand...
Click to collapse
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
k.s.deviate said:
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
Click to expand...
Click to collapse
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
NeverBackDown said:
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
Click to expand...
Click to collapse
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
k.s.deviate said:
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
Click to expand...
Click to collapse
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
k.s.deviate said:
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
Click to expand...
Click to collapse
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
Possibly, I have no experience dealing with a service center unfortunately.
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
I also want to highlight that,I am getting a black screen on the fastboot mode too,i cant see nothing there..Only way i am able to identify that my device is in fastboot mode is by giving fastboot devices command.
So can this be a software issue?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
You might want to look into android screencast.
I don't know if it still works with the latest android releases, but back in kitkat days if I had a screen that wouldn't display I could use screencast and I'd get the framebuffer displaying on the PC. While viewing on PC I could then do touchscreen "guesses" more accurately and presumably you'd be able to enable OEM unlocked bootloader so you can flash factory images.
Hi Mates,
I have 1789-06 variant with unlocked bootloader.
I installed the pie version via flashall, all were OK.
but upon rebooting the splash screen prompted for "verity mode is set to disabled".
no matter what I tried, all failed - the phone reboots to the fastboot screen.
then I was wondering BP Tools mode where on the screen it was showing "disabled".
somehow I enabled and attempted to reboot - the screen went total black!
is there anything that can revive the phone?
thanks in advance for the support.
cheers.
Connect to your pc and simply try holding the pwr btn for a minute to see if it will boot, if not, try holding vol dwn + pwr for a minute to see if that will boot it. Listen and look to see if your pc is detecting the phone at all while you try. Also you can check your device manager to see if it is showing there.
41rw4lk said:
Connect to your pc and simply try holding the pwr btn for a minute to see if it will boot, if not, try holding vol dwn + pwr for a minute to see if that will boot it. Listen and look to see if your pc is detecting the phone at all while you try. Also you can check your device manager to see if it is showing there.
Click to expand...
Click to collapse
thanks bro for the prompt response.
however, no connection, no booting, no sound of device connection to the PC.
what can be the next mate?
beefytr said:
thanks bro for the prompt response.
however, no connection, no booting, no sound of device connection to the PC.
what can be the next mate?
Click to expand...
Click to collapse
Unfortunately, the black screen has been a bit of a fiasco with pie updates, especially for those who have tried pie on variants not intended for the firmware. No solution has been found yet, but I haven't heard of it happening by enabling bp tools. Connect to a 2.0 port and double check your device manager. Look for unknown devices, hs usb 9008, and try various button combos while trying to power and watch your device manager for new devices. In short you might be SOL, but if you're lucky and your pc recognizes the phone you might be able to blankflash.
41rw4lk said:
Unfortunately, the black screen has been a bit of a fiasco with pie updates, especially for those who have tried pie on variants not intended for the firmware. No solution has been found yet, but I haven't heard of it happening by enabling bp tools. Connect to a 2.0 port and double check your device manager. Look for unknown devices, hs usb 9008, and try various button combos while trying to power and watch your device manager for new devices. In short you might be SOL, but if you're lucky and your pc recognizes the phone you might be able to blankflash.
Click to expand...
Click to collapse
ok thanks.
actually, my phone was set to get the OTA.
the OTA s'mpy did not install without any reason saying "something went wrong".
anyways, the strange thing is that all happened after the BP tools thing.
I will see what I can do with USB 2.0.
this whole thing does not seem to be a brick, right?
beefytr said:
ok thanks.
actually, my phone was set to get the OTA.
the OTA s'mpy did not install without any reason saying "something went wrong".
anyways, the strange thing is that all happened after the BP tools thing.
I will see what I can do with USB 2.0.
this whole thing does not seem to be a brick, right?
Click to expand...
Click to collapse
Actually it kind of does. On oreo, it seemed the worst that would happen is you would soft birck. Basically a black screen but the phone would connect to the pc as a 9008 device and you could blankflash your way back to good. Since pie, something is happening and the exact reason hasn't been pinpointed. Usually it's those who have tried to flash pie for a variant it wasn't intended for. Some have lost their baseband and are still waiting for a solution to that, and a couple have full on bricked. At least there hasn't been any sign of life nor a way to do anything about it. Granted the bp tools thing is weird, but maybe a dav will pick up on this and maybe understand just what is happening and what is causing it.
41rw4lk said:
Actually it kind of does. On oreo, it seemed the worst that would happen is you would soft birck. Basically a black screen but the phone would connect to the pc as a 9008 device and you could blankflash your way back to good. Since pie, something is happening and the exact reason hasn't been pinpointed. Usually it's those who have tried to flash pie for a variant it wasn't intended for. Some have lost their baseband and are still waiting for a solution to that, and a couple have full on bricked. At least there hasn't been any sign of life nor a way to do anything about it. Granted the bp tools thing is weird, but maybe a dav will pick up on this and maybe understand just what is happening and what is causing it.
Click to expand...
Click to collapse
we'll wait and see!
thanks.
by the way, how do you "blankflash"? just in case...
beefytr said:
we'll wait and see!
thanks.
by the way, how do you "blankflash"? just in case...
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
All the best mate.
Thanks.
41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
what if what you advise does not work at all?
then it is a dead one?
beefytr said:
what if what you advise does not work at all?
then it is a dead one?
Click to expand...
Click to collapse
Yeah, the whole blankflash hinges on the fact that it is already in edl mode, but considering your circumstance, it is most likely dead like the few others. As of now there is no known way to revive them besides a jtag (untested and not confirmed) and you would need to tear your phone down to even try that, which isn't a viable option for most. Sorry I can't offer anything more.
41rw4lk said:
Yeah, the whole blankflash hinges on the fact that it is already in edl mode, but considering your circumstance, it is most likely dead like the few others. As of now there is no known way to revive them besides a jtag (untested and not confirmed) and you would need to tear your phone down to even try that, which isn't a viable option for most. Sorry I can't offer anything more.
Click to expand...
Click to collapse
thanks bro.
I will not bother for JTAG as it is - as you have rightfully said - untested.
my phone is still under warranty and I will try a replacement or a refund then.
cheers.
What did you do to boot your device.. Even mine is bootlooped.
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
What did you do to boot your device.. Even mine is bootlooped.
... Is it bootlooping or does it just not power on at all?
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
mkhcb said:
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
Click to expand...
Click to collapse
Doesn't your phone have to be unlocked to use the flash tool?
The data is all backed up so it's not a problem to lose it. The problem is actually making the phone to boot past the logo... I will try that Android Flash Tool but I fear that the phone should be unlocked first
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Maybe try sideloading OTA again. Are you able to do that?
mclarence said:
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
Click to expand...
Click to collapse
McNaccken said:
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Click to expand...
Click to collapse
Unfortunately, someone else in another thread reported that the Pixel Repair site (not the Android Flash Tool) hasn't been updated for the P6P.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Lughnasadh said:
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Click to expand...
Click to collapse
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
znel52 said:
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
Click to expand...
Click to collapse
Oh crap, didn't think about that.
I know not everyone has access to a laptop but if you do always use that over a desktop. In the event of something like this you will have the battery power to carry you through.
I'm sorry this happened to you. The only option may be to send it to Google for repairs.
Sorry for your phone. I experienced this on a nexus 6 that didn't have USB debugging or OEM unlock enabled. I tried sideload, put the update package on the phone storage, try to update with Android recovery. Nothing worked. Stuff happens with phones. I hope you can get a new phone.
God bless.
Sorry to hear this. It seems that I need to open USB debugging option just in case for my Pixel 6, which finally arrived across the ocean after a month.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
Since the Repairtool has not been updated for your needs and considering that your device is not unlocked, your only option is to contact Google (/your seller). Maybe they can offer you an updated version of the tool (unlikely) or replace your device.
You just described, btw, my horror scenario when updating the BIOS of my PC. The lights going out, when doing a firmware update o.o
Oh my. I'm so sorry for you to have experienced that.
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
My apologies for asking the obvious - did you select "adb sideload" in the recovery menu ? At least I was blind enough to oversee that I need to select this option first
Can you boot into fastboot from the recovery ? If yes you could also try installing a factory image instead of the update package.... I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
I had a similar issue with applying ota updates and have seen quite a few reports of users having trouble. Not sure what the deal is, but for some reason this phone seems super finicky with updates. Are you still in the return window? You may want to reach out to Google support or one of their "authorized repair shops".
For me, I ran the flash all bat, rebooted, got a message saying my device can't be trusted. So I rebooted, wiped data, rebooted again and got the same thing. So I rebooted, ran the flash all bat file again, rebooted phone, and screen went black and it never powered on again. Suspect circuit board may have fried some how. Anyways, long story short, contacted Google and had a replacement sent out with minimal hassle.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
so you can get through this... you'll be fine. pick adb sideload and it will say waiting, then run the command.
you can also change slots at the bootloader menu or try running the unlock oem command to see if it will allow you to unlock..... not sure if you can change slots without unlocking bootloader. try different USB ports on your computer (and restart your computer just in case) along with using the latest platform tools (adb/fastboot) and USB driver directly from Google (not third party apps or websites.
download the OTA zip again (and just open and close it quickly to verify it isn't corrupt).. and also make sure you have 5-10GB of space free on your computer.
usually the boot slot is changed whenever an OTA is flashed. it will tell you what slot you're in at the bootloader menu (where it says fastboot and device state locked).
can you try holding power button (when it's not plugged in) and as soon as you see then Google logo, hold volume down. that will get you to safe mode. and as quickly as you can, enable "OEM Unlocking" - which will allow you to flash a full factory image.
sorry for this comment being all over the place. if you need help, just reply, and I'll be more methodical next time
s3axel said:
I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
Click to expand...
Click to collapse
I don't think the problem is that his bootloader is locked - it's unlocked, however, they factory reset the device which likely caused USB Debugging to be turned off, as it defaults to after a factory reset.
I'm so glad years ago I swore to use Uninterruptible Power Supplies (UPS) for all the PCs I build for myself or my wife.