Develop Bugs

Bricked Swift

Hello Everyone!
I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?
Thanks in advance!!

Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.
In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317

Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.

narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
Does the phone give any indication of being connected? Notification light, starting the display, etc?
If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.
If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.

narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me

Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*

LG G8 STUCK IN Qualcomm HS-USM QDLoader 9008

Today I Bricked My LG820Qm
I was updating my Lg g8 using LG UP, When the Process on 64% my PC power off
After that my phone stuck in Qualcomm HS-USM QDLoader 9008
Any solution to come out from this mode to Downloaded Mode so that i can update using LG up.
I was updating G820QM10i_00_NAO_US_OP_0401 to G820QM20b_00_NAO_US_OP_1224
My LG up LGUP_Lab_Frame_Ver_1_16_0_3

Can you try to switch to download mode by press&hold VOL+ while inserting the USB cable (connected to PC). Phone needs to be off while doing so.

tron1 said:
Can you try to switch to download mode by press&hold VOL+ while inserting the USB cable (connected to PC). Phone needs to be off while doing so.
Click to expand...
Click to collapse
I tried not working
If i press&hold VOL+ while inserting the USB cable still my phone come with Qualcomm HS-USB Mode
thanks for your reply

What happens if you press&hold VOL- (furing the whole procedure) push the power button until the phone vibrates, release the button und press&hold the power button?

tron1 said:
What happens if you press&hold VOL- (furing the whole procedure) push the power button until the phone vibrates, release the button und press&hold the power button?
Click to expand...
Click to collapse
Which ever combination, Vol- + power phone power of
with in sec it boot to Qualcomm mode

I don't know where to ask so I'm gonna try here. My G820N is stuck on Android 10 beta. Whenever I flash an official kdz, it only allows for emergency calls. Can't do anything. Any help would be appreciated

Following, in right here with ya.

atsuisofu said:
Following, in right here with ya.
Click to expand...
Click to collapse
Try entering download mode with phone disconnected from USB cable.
Also try to see if it gets recognized by LG-UP or by LG Bridge. These 2 softwares don't need download mode to be able to flash, just the phone to be recognized on some PORT.
Try also factory reset hard menu. Also try switching between Slot A and Slot B. There is also this backup method. Phone is not dead on one of those slots.
If nothing works (but slot a slot b should 100% work) , wait for the firehose, it's just around the corner. That will restore the phone back 100%.
For more info search v50thinq on telegram app. :good:

I can t get to download as it freezes and without the USB cable it doesn't even try and enter. I appreciate the recommendations. I was thinking of the a/b seit hbut without the use of fastboot I am at a loss of how to switch between the two as I thought the system chose and the switch happened upon rebooting once a system had been selected ie as in turning the unit off after loading the os set a flag to go to the opposite system upon completing the inftframs and boot sequence.

vikramanananda said:
Which ever combination, Vol- + power phone power of
with in sec it boot to Qualcomm mode
Click to expand...
Click to collapse
Hi, i'm facing the same problem today, my QM will not go into any mode other than the Qualcomm mode. Were you able to recover your phone finally ?

vikramanananda said:
Which ever combination, Vol- + power phone power of
with in sec it boot to Qualcomm mode
Click to expand...
Click to collapse
did you ever get it fixed. im having the same problem.

johnnycm77 said:
did you ever get it fixed. im having the same problem.
Click to expand...
Click to collapse
me too, do you fix it?

vikramanananda said:
Today I Bricked My LG820Qm
I was updating my Lg g8 using LG UP, When the Process on 64% my PC power off
After that my phone stuck in Qualcomm HS-USM QDLoader 9008
Any solution to come out from this mode to Downloaded Mode so that i can update using LG up.
I was updating G820QM10i_00_NAO_US_OP_0401 to G820QM20b_00_NAO_US_OP_1224
My LG up LGUP_Lab_Frame_Ver_1_16_0_3
Click to expand...
Click to collapse
So, if the device, as you say, lost power during an update like that, then almost assuredly you have at least one, if not numerous corrupted partitions.
And, it's specific partitions on the device that allow it to enter download mode. One of these most know about or have heard of is the laf partition. But other have to be there also for it to work, I don't remember exactly what the others off the top of my head, but that info is easily found.
The key thing you need (or any others commenting same prob), is to be able to enter EDL mode and have qfil installed and recognizing the device. If you can get that far, it would be easy to find the correct partitions you could flash with qfil and then immediately go from qfil to download mode.
Many many people have done this. Just get qfil set up (see guides section) and get the device recognized. that takes some effort but it's def doable.

Phone Not Entering DA mode.

So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.

I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical

wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?

I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.

I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.

When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.

With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.

I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.

Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.

Question Oneplus 9 pro bricked, impossible to get to EDL

Hey all,
So i've unlocked by bootloader, flashed a custom recovery to then proceed with LineageOS flashing. However it went completely wrong as on reboot i'm stuck with the bootloader unlocked warning and then a blackscreen.
I still have access to fastboot mode however it's impossible to flash a customer recovery ("No Such Partition") and also impossible to directly "fastboot boot recovery.img" as the phone simply reboots on the warning and then blackscreen.
The only solution seems to get the device to qualcomm EDL mode and reflash all with the MSM tool (which I have as well as all the drivers) however I cannot get my Oneplus 9 pro to EDL mode...
I've tried all the fastboot commands (fastboot oem EDL, fastboot reboot EDL, none of them work) as well as the combination volume UP + volume DOWN + plugging the cable (it just boots the fastboot mode.
Honestly would greatly appreciate any help as it is the first time in a decade I hard bricked a phone like this as it seems all the partitions are broken.

Make sure you have it unplugged when you do the button combos, as it will just start to boot while it's plugged in. Also, if you can reach fastboot, you can almost definitely reach EDL. Try unplugging and holding power+vol up for a bit which forces it to completely power off. Then try getting into EDL through the normal button combo/plugging. This is what I had to do since once it got into the booting/no-booting cycle I couldn't get to EDL.

1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.

Good advice above.
Last time I couldn't reach EDL with my previous phone, it turned out to be an issue with the drivers I had installed. I uninstalled all Android-related drivers including some generic thing that showed up in device manager when plugging in the phone, then reinstalled the latest Qualcomm drivers.
Also possibly try a different USB cable if you have one. My OP9P didn't show up when the cable it came with was plugged into my USB-C port for some reason, but it worked fine with a generic Type-A to C cable I had sitting around.

Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...

Tornadeur said:
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Click to expand...
Click to collapse
I can fix it bro pm me telegram .. @Hunar71

Hunar999 said:
I can fix it bro pm me telegram .. @Hunar71
Click to expand...
Click to collapse
Can you help me too, I have exactly the same problem…

If you use Windows, you need to see "QDLOADER 9008" in Device Manager > Portable Devices.
When you got this it will work, 100% .
It worked for me a few days ago. My laptop runs on Windows 11 x64. And only have usb 3.0. NO usb 2.0.

was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.

Alberhasky said:
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Click to expand...
Click to collapse
Yeah make sure it's exactly the same name of that driver - worked for me on oneplus 9

If you have access to fastboot still. Try switching slots. Then going into EDL

For anyone looking for help, please DM me.

djsubterrain said:
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Click to expand...
Click to collapse
Thanks a lot man. Saved my Day. First 9Pro successfully restored ;-) Thank you and merry Christmas to all.

Guys I do not need to use the MSM Tool Anywhere until I reach the step where my device is being successfully detected as "QDLOADER 9008" in my windows device manager correct?
Or does the MSM Application need to be running when I reboot to EDL mode?
I am following this guide.
Please help

I always have phone powered off, and while holding both volume keys I plug it into USB cord(that is already plugged to pc) and then click on enum(button in msm screen) until it says connected then hurry and click start. Once it starts I can let go of volume keys.. Also more than likely u will need to click the box to "use lite firehose" or "Sahara communicaion" will keep failing.

make sure you have oneplus 9 pro drivers and " qaulcomm incorporated - Ports" Driver) and ("qaulcomm communications inc-Net" Driver) so your phone in edl which will be already most likely be running before you plug it in. just hold down both volume buttons and plug in to the usb port to your pc and release once plugged in and start the msm tool and hit enum it should say connect provided that you have all the necessary drivers above so the pc usb port will be able to communicate/recognize you device. its never usually A 1 and done type of thing. everytime i brick my phone its always the 100th try before i get a com port connected and the software communicating successfully, so just be patient and take your time. you will get it back up and running,

Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks

awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
can't get into edl mode
how can I get oneplus 9 pro into edl mode while it's refusing to turn off? keep in mind that I can't use adb. but was able get fastboot devices command to work and I did not use any third party roms, didn't unlock the bootloader, and do not have...
forum.xda-developers.com

awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse

Well you have a corrupted boot.img or you would not be trying to edl. Also you probably are holding down multiple buttons to power off to your phone and your either not remembering or forgot that these combination of buttons are booting you into other modes fastboot, recovery or system.

Question Bricked my Prixel 6 after flashing stock rom

Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks

Call whoever you bought the phone from and do warranty claim.

I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.

Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?

cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.

From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.

Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools

Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.

What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...

roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits

ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.

If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.

pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.

rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.

@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.

ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.

same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?

Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....

Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.

roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears