The pixel6 pro has an automatic reboot after aosp is flashed in, then it won't boot and becomes a brick, all buttons are unresponsive. I don't know what the problem is, the original Android version is 14, the one I flashed in is 13.
After installing the driver and plugging it into the computer, the port device will appear, and the QFIL software can recognize this port. Need "FireHose Programmer" && "rawprogram*.xml,", please help to solve the brick method or related resources
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since there is no Google service in my area, I can't send it back to the manufacturer for repair.
If your Pixel device is hard bricked, meaning it is completely unresponsive and cannot be turned on, there are a few steps you can take to try to resolve the issue. Here are some steps you can try:
Try a hard reset: Press and hold the power button and volume down button simultaneously for at least 15 seconds to perform a hard reset. If your device is responsive, this should force it to reboot.
Check your USB connection: Make sure that your device is properly connected to your computer via USB. You can try using a different USB port or cable to see if this resolves the issue.
Use fastboot to flash a factory image: If your device is still unresponsive, you can try using the fastboot tool to flash a factory image onto your device. This process can be complex and may require technical knowledge, so it is recommended to follow a detailed guide or seek professional assistance.
This is based on my experience but maybe some expert can suggest better treatment, I request them to suggest a solution.
GcamApk said:
If your Pixel device is hard bricked, meaning it is completely unresponsive and cannot be turned on, there are a few steps you can take to try to resolve the issue. Here are some steps you can try:
Try a hard reset: Press and hold the power button and volume down button simultaneously for at least 15 seconds to perform a hard reset. If your device is responsive, this should force it to reboot.
Check your USB connection: Make sure that your device is properly connected to your computer via USB. You can try using a different USB port or cable to see if this resolves the issue.
Use fastboot to flash a factory image: If your device is still unresponsive, you can try using the fastboot tool to flash a factory image onto your device. This process can be complex and may require technical knowledge, so it is recommended to follow a detailed guide or seek professional assistance.
This is based on my experience but maybe some expert can suggest better treatment, I request them to suggest a solution.
Click to expand...
Click to collapse
Thank you for your answer.
1. no response to any key operation on the device, the power button volume keys +- tried many times for a long time, there will be no response
2. replace the usb and port to connect to the computer there is no connection device other than the com port
3. I can't connect the phone to the computer to use Google's online fastboot tool to reset the phone because I can't turn it on.
Thanks again for your answer.
Related
Dear developers!
After successfully flashing and upgrading a friend's Samsung, I got the courage to do the same with my Lenovo Vibe P1.
I followed this video and everything was perfectly: I unlocked the bootloader, connected using QFIL and flashed the TWRP recovery he provided, until the 8:00 minute in the video the program said "Waiting for reset done..." and my QFIL just stucked on that message, so after waiting 5-7 minutes I disconnected the cable in hope that it will reboot to recovery, got some log errors and since then the phone is hard bricked.
Turning on does not work, recovery/bootloader/charging does not work, essentially the screen is dead, the only thing that works is recognization in QFIL program.
When I try to flash stock rom or that recovery from that video again, it first says a protocol error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try to Download again, now it gets stuck at the Working folder (last message in the log, see below)
EDIT: Depending on the QFIL version, the version below actually gives the same error as above after few minutes.
In addition, any attempt to connect the phone to Windows using USB results in numerous partitions being shown from the phone internal memory (many of which Windows does not recognize as formatted):
(https://i.imgur.com/otd7e0M.png)
Is there anything that could be done to recover my phone please? Not having the right financial situation to purchase a new one and school starts soon so pretty bad situation for me now.
Kind regards,
kangarko
Update! I deleted all partitions from the phone and was successfully able to flash a couple of ROMs from the Internet (including a stock one). However, after each flash one, I get the "Waiting for reset done..." message and than the phone gets disconnected from my Fusion (virtual Windows 7 in Mac), and when it gets connected again it says Finished but the phone is completely black. No signs of any activity, it does not restart itself nor vibrates, and I end up with the problem in my first post again ;(
Help still needed... noticed I typed "Lenovo" in the thread title instead of Vibe, I corrected that but the PHONE IS STILL BROKEN.
Alright, got it solved somehow.
Flashed "P1a42_S272_160506_ROW_QPST" using QFIL 2.0.0.3 and Lenovo usb drivers v1.1.33 + Qualcomm drivers 1.0.
Newer QFIL versions are disfunctional over my device.
Always make sure to hold Power button for 13 seconds to make sure the device is OFF, then connect to QFIL. After it finishes the flashing process, simply disconnect and hold Volume UP button + Power button for 13 seconds and than again to make it boot.
You can find some useful stuff here (including TWRP):
https://forum.xda-developers.com/vibe-p1/how-to/qpst-flashing-vibeui-3-1-s272-rom-t3386650
kangarko said:
Alright, got it solved somehow.
Flashed "P1a42_S272_160506_ROW_QPST" using QFIL 2.0.0.3 and Lenovo usb drivers v1.1.33 + Qualcomm drivers 1.0.
Newer QFIL versions are disfunctional over my device.
Always make sure to hold Power button for 13 seconds to make sure the device is OFF, then connect to QFIL. After it finishes the flashing process, simply disconnect and hold Volume UP button + Power button for 13 seconds and than again to make it boot.
You can find some useful stuff here (including TWRP):
https://forum.xda-developers.com/vibe-p1/how-to/qpst-flashing-vibeui-3-1-s272-rom-t3386650
Click to expand...
Click to collapse
Hi there.Did you experience USB not recognized?I already removed the battery-reconnect-hold volume + then connect the usb cable but still USB not recognized.
Hey XDA!
I found somewhere in web stock rom for QFIL, that you can flash when your phone is hard bricked (like mine was) or when you want to remove Add-X for free. Here are the downloads:
Qualcomm 64Bit drivers
Full Qualcomm flashing suite
QFIL image
My mirror of QFIL image (use when AndroidFileHost is slow for you)
Here are the steps to flash it:
1. If your phone is in 900E mode and you can't reboot to 9008, get a spare USB type C cable or microUSB to USB-C adapter.
1a. If your phone can boot into 9008 mode without problems by holding all 3 buttons, go to step 5.
2. Now you must cut your cable like this (image credit: [email protected] from MIUI forums)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Burn plastic on green and black cable
Something like that:
4. Now when your phone is fully turned off (you can get back cover off and disconnect battery), connect cable to your pc, short green and black cables together and connect it to your phone. After about 10 seconds separate the wires. Now your phone will boot into 9008 (aka EDL) mode. If you will get Unrecognized USB device prompt, connect battery when phone is turned on into 9008, detach EDL cable and connect normal cable.
5. Launch QFIL and set it like that:
6. Click "Download" and wait until finish. If QFIL will error with "system.img/cache.img/userdata.img not found" create empty files named "system.img", "userdata.img" and "cache.img" in stock rom folder.
7. When QFIL will finish flashing, hold power button in your Swift 2. It should boot to system now. If not, try to flash TWRP/Stock rom via fastboot, doing factory reset in Cyanogen Recovery or "fastboot format userdata".
Credits:
Me
Mike's Tech Life from http://mikestechlife.blogspot.com that posted stock QFIL rom, Add-X removal tutorial (http://mikestechlife.blogspot.com/2018/01/removing-add-x-from-wileyfox-swift-2-2.html) and QFIL Screenshots
[email protected] from MIUI Forums EDL cable images
I have long written the exact same guide. What is yours for?
JavaVOBIS said:
I have long written the exact same guide. What is yours for?
Click to expand...
Click to collapse
I see your point about duplicate but I guess you could say @puszekkkkk added photos and info on kicking into 9008 ...your guide was the inspiration or first but both guides are useful to people ...hopefully i won't need either but neat trick with spare usb to get into qfil mode
This destroyed my computer :'-(
I'm sad/frustrated to report that I attempted to follow this guide and completely destroyed my desktop computer in the process! ? I made the cable exactly as instructed and made sure everything was carefully wired with nothing touching anything it wasn't supposed to. I tried repeatedly to get my ZTE device to boot into EDL mode but it simply would not. And then, when I was trying once again, holding the green and black wires together for a few seconds, I suddenly noticed an electrical burning smell. Looking at my beloved little mini-desktop PC, I noticed a very bright orange-yellow piercing light coming from within and then realized this was a flame!! ? I quickly unplugged the PC and ripped the case off, and then blew out the small flame that had started to burn a specific chip on my motherboard. I think this chip must have something to do with USB-port power supply/support. It's a very specific chip and not one I can find online to purchase to repair/re-solder myself. My device is four years old now and is unfortunately out of warranty. I called the tech support center for my device anyway (ASUS) to see if they could do anything, and also wanted to inform them that their product had caught on fire, but they just took my information and said they were sorry but that they couldn't help me with this at all.
So now I am without my main desktop PC. ???
And my stupid ZTE device is still a useless paperweight... ?
richaardvark said:
I'm sad/frustrated to report that I attempted to follow this gu ?
... Homemade cables are a bad way to enter edl
Use fastboot :
fastboot oem edl
Using test point:
Search on YouTube for a video on how to open your phone and "shorting" two contacts to enter edl ( this is the method used by technicians and manufacturers)
Click to expand...
Click to collapse
Hello,
I got an issue with my Xiaomi Redmi 7. I was trying to install TWRP with adb, but something got wrong, and now my phone seems dead, bricked.
Nothing happens when I try to turn on, can put on fastboot mode (with power+volume down), nor restart it with power+volume up. The screen are just black, and even the notification led doesn't light up when I connect the charger. My guess is the phone is in EDL mode.
Connecting to my computer it recognizes it as "Qualcomm HS-USB Diagnostics 900E", and I can see it on MiFlash, but when I try to flash any stock rom, it stucks in the very beginning. Here's a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried different versions of the stock rom, MiFlash and computers, but got the very same result.
Do you have any idea what can I try to bring it back to life?
Thank you in advance!
Tamas
tamasv said:
Hello,
I got an issue with my Xiaomi Redmi 7. I was trying to install TWRP with adb, but something got wrong, and now my phone seems dead, bricked.
Nothing happens when I try to turn on, can put on fastboot mode (with power+volume down), nor restart it with power+volume up. The screen are just black, and even the notification led doesn't light up when I connect the charger. My guess is the phone is in EDL mode.
Connecting to my computer it recognizes it as "Qualcomm HS-USB Diagnostics 900E", and I can see it on MiFlash, but when I try to flash any stock rom, it stucks in the very beginning. Here's a screenshot:
I've tried different versions of the stock rom, MiFlash and computers, but got the very same result.
Do you have any idea what can I try to bring it back to life?
Thank you in advance!
Tamas
Click to expand...
Click to collapse
Hey mate, I'm not sure if you fixed it or not but I'm pretty sure that if it can boot to fastboot it's not bricked. What I suggest you would do right now is install xiaomi drivers onto your pc first and foremost (this actually fixed all my problems) then try to use adb and fastboot tools to fastboot flash recovery twrp.img. if that works you're safe and then proceed to advanced wipe, then vendors and system wipe then in an SD card or an otg flash USB install the lastest global or Europe ROM for miui 11.
Hello,
I've tried researching this issue but nobody seems to have the same issue that I do.
Background: I've had my Pixel C with the stock OS (Android 8.1.0) and everything else stock. It is not rooted, and the bootloader is not unlocked as far as I know. I bought it on eBay like 4 years ago. Never had an issue with anything. I have connected it with multiple USB A to C cables (to rule cables out) on multiple Windows computers (to rule out specific computer issue) that I've used with ADB on my OnePlus 7 Pro before, so all the platform tools should be good (ruled out that the platform tools were the issue).
Issue: I cannot boot this thing into fastboot mode. I can connect it to adb and get it listed in adb devices just fine. I set it to always trust the computer. I try issuing a "adb reboot bootloader" and the Pixel C screen shuts off like I would expect. The screen goes black, then...nothing. The rainbow lights on the back light up as though it's powered on, but nothing ever happens.
Troubleshooting:
So far, I've tried turning off the device completely, then powering it up while holding down the volume- button. This gets me the same black screen with the rainbow lights turned on.
I've tried holding volume- & volume+ while booting, and that gets me into Safe Mode (whatever that is). I've tried volume+ and power, which doesn't seem to do anything at all.
I checked device manager, and the device gets detected when it is in OS, but when I issue it the adb reboot bootloader command, and get the black screen, NOTHING shows up in device manager. No "other device" or "unknown device" or "android device" anything. In fact, listening for Windows audio alerts, I hear the device disconnect when it reboots, then I never hear it reconnect.
At some point after boot cycling it multiple times, it came up saying "The device is having trouble booting, you can click try again or you can try reformatting." It looked like the stock recovery, but not fastboot or anything. Haven't gotten that to show up again. I did go through with the device wipe.
If anybody has ANY ideas for how to get this thing booted into fastboot, please send them my way. It would absolutely make my week
EDIT:
Just tried this and am getting somewhere hopefully...
I did "adb reboot recovery" and it gave me the dead Android screen. Did Power & Volume+ and got the menu opened. Was able to get an adb sideload working and I sideloaded the latest OTA. Here is the logs shown on screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google release Android 12 Dev Preview and i decide to sideload that on my 3xl device (It not my daily use device so it fine for me)
1) I connect the phone, use adb reboot recovery in ota intrucstion and the screen gone black
2) It not show in adb, not show anything in the screen. I use Power + Vol Down for a while, then it show on adb devices with Window add device sound
Current State: + Black screen
+ Have vibration
+ Receive charging and show on adb, i use some adb command to check and it have 100% battery
Case i think happen:
+ No battery, no boot up : I tried use adb command and it in 100%
+ Screen die, error (Hardware): I dont think that happen because it working fine for me and i not did any damage to it, just reboot it to recovery. I tried a type-c to hdmi and connect it to my monitor but it
not render anything
+ Some firmware problems: I not flash anything yet, just boot it to recovery so i dont think this case happen, i tried some method like hold power, hold power + vol down but not work
It really weird things for me, it is the first time i see a device working normally just gone to black screen by boot to recovery, non respond in screen (squeeze gesture and fingerprint still give vibration), not ringing by call.
Some note may useful: I tried hold power + vol down, then hold vol + while still hold these two button, some kind of strong vibration happen then everything still the same
I really looking forward to people have the same problems and solved it!
Surfaceflinger might have been corrupted, so the only thing you can do now is try to guess the key combination for bootloader, or just use adb to boot into bootloader mode. Then flash the latest factory image. That will hopefully fix it.
My device not have oem unlock option, so seem like enter bootloader to flash image is not possible
But i have some update, i used a tool https://github.com/Genymobile/scrcpy and i show my display
to my computer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I try to touch on screen, use button, ... and everything seem like work. Only the display not display anything, just the black screen. At this point, i think it because of hardware problems - sound like so weird because i just run the device to recovery by adb