yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] iplux:
i was on december android update with magisk installed. i tried today to install january update today - i patched the boot.img file (yes, i know it should've been init_boot.img), replaced the original boot file with the patched one on my pc and flashed the new january rom with "-w" parameter removed. That however didn't work (obvious reasons), i had no root. I then decided that the new boot.img file from the january update might have some issues , and decided to flash the january update with replaced boot.img patched from december update (again with -w parameter removed). The phone took it all, then the google logo popped up... after a few seconds it restarted and the google logo popped up again... it once again didnt boot, and restarted, but after the 3rd restart i was greeted with a message from the bootloader (i assume) that the system failed to load twice, and i was presented with 2 options - "restart and try again" or "factory reset the system". I chose restart, and the screen went black and that was all. (it was only after all of this happened when i realized that everything happened because i was patching the boot.img instead of init_boot.img).

Now the screen is black, no matter which button combination i am trying. Sometimes the screen flashes once or twice when i hold some buttons, but that aside- nothing. I assume the phone is still doing something in the background, because if i leave it on my bed sheets and touch it after awhile, the back is a bit warm, so obviously something is working, but im certain its not the OS.
[Google Pixel 7 Pro] febo17:
I hope you solve it, good luck and stay tuned
[Google Pixel 7 Pro] V0latyle:
Since this is a very new device, I suggest contacting Google for warranty repair, because that will be much easier than trying to diagnose what works and what doesn't, as well as trying to recover the device. You have a warranty; use it.
[Google Pixel 7 Pro] iplux:
just tried:

pwr

pwr + vol up

pwr + vol down

pwr + vol up + vol down

each for more than a minute, no response.
[Google Pixel 7 Pro] iplux:
I most likely will, i just don't want to because im in Bulgaria (a country where they dont sell the phone) which means i have to find a way to send the phone to the UK, and they will probably refuse to ship it back.
[Google Pixel 7 Pro] V0latyle:
Ah. Well...without the screen working, there isn't much you can do, beyond seek repair in your own country. If the screen isn't working, it's usually due to either of 2 reasons, both of which require specialty repair:

The screen and/or display controller are defective and must be replaced

The bootloader is corrupted and the mainboard must be replaced

The tools required to rescue a device with a corrupted bootloader are not publicly available, unfortunately.
[Google Pixel 7 Pro] simplepinoi177:
This is kinda crazy....

this is probably the first time/instance I've seen where tripping up the init_boot partition (with the boot.img used instead) caused this bad of a problem! Since the Pixel 7's changed things to init_boot, there have been very many people that have gotten tripped up flashing the boot.img to it, but it usually just results as a bootloop and a simple reflashing of the stock init_boot properly fixes things!

Are you sure you tried completely draining the battery? A hard reset can sometimes do wonders...

If Google doesn't "play ball", I'm sure you could find some 3rd party repair company/shop that would -- of course this will also cost money though...

Hopefully it works out for you OP!
[Google Pixel 7 Pro] iplux:
Flashing patched boot.img did nothing, the phone booted fine, just with no root. The thing is, i flashed patched boot.img from December update with the january rom after the first attempt was unsuccessful, because i thought that it wouldn't be a problem, and that was the end of it. The phone is slightly warm, so i assume it is trying to di something in the background. Hopefully it'll drain the battery completely in a day, and i'll try to bring it back to life again. I can claim google warranty, sure, but that means i have to fly to italy/uk/germany and stay there for a while. They accept and send shipments back only within the countries where they sell the phones unfortunately.
[Google Pixel 7 Pro] simplepinoi177:
i meant that flashing the boot.img was the problem; flashing the stock init_boot.img usually is the simple solution.

here's hoping you can get the battery to completely die, and power plugging it back in might yield some positive results...

It's unfortunate shipping situation, but that's why I suggested maybe a 3rd party repair shop/store as I'm sure they are willing to ship it anywhere -- Google is a corporation with international restrictions I imagine. Problem with that is Google would be willing to repair/replace it for free under warranty, 3rd party would not.

Maybe you have a friend or family member in those countries whose addresses you can use. I'm unsure, but if they are willing to ship to a P.O. box (they have those internationally right? I'm unsure if that's just a U.S. thing...), maybe you can set up some kind of arrangement that way...
[Google Pixel 7 Pro] iplux:
Small update, after draining the battery completely, it now displays a dead battery symbol for 2 seconds if i hold all 3 buttons for around 10 seconds. After plugging it back in, the screen is back to the previous state of occasionally flashing and then staying black. Will experiment more with it tomorrow!
[Google Pixel 7 Pro] how_now_brown_cow:
Had this happen to me -- no amount of tinkering will cause it to boot, I'd recommend finding a shop or RMA
[Google Pixel 7 Pro] iplux:
Yup, it's in some EDL-like state. If i charge the battery, the phone SoC is a bit warm. I have no clue what is it doing, but its doing something. Apparently there's an authorized repair center in germany that accepts shipments from all eu countries, so i guess i'll try that and see how it goes. Thanks.
[Google Pixel 7 Pro] iplux:
Update: Apparently from what i can see and understand, they pretty much replaced the whole phone at the repair shop.
[Google Pixel 7 Pro] Juuuuune:
A week ago, I encountered similar problems when I was ROOT on my Pixel6Pro: I mistakenly regarded the vendor_boot file as a boot file (in fact, it is universal on Qualcomm devices) and handed it to Magisk, but Magisk showed that the patch was successful. (Even if the file is incorrect) Then I flash into my pixel6pro on the file output by magisk on Fastboot, but the phone refused (at this time I did not know that the file was incorrect). After I tried many times, the pixel6pro was stuck on the BootLoader (Fastboot) interface and refused to connect with the PC. In addition, my pixel 6Pro disabled the power button at the same time (the system cannot be started by pressing the power button). I can only use Vol + / Vol- to change the startup option, but the power button does not work. By looking for customer service, I found a solution: reset the bootloader, it is very simple, just press and hold the Power Button and Volume Down for 45 seconds twice.When finished, power button was allowed to work and successfully reboot system At this point, the phone resets applications other than user data, such as the camera, which will return to the original version.
[Google Pixel 7 Pro] Juuuuune:
By looking for customer service, I found a solution: reset the bootloader, it is very simple, just press and hold the Power Button and Volume Down for 45 seconds and repeat the system twice. At this point, the phone resets applications other than user data, such as the camera, which will return to the original version.
[Google Pixel 7 Pro] iplux:
I've definitely tried that, and it didn't work. I sent the phone at the repair center, i got the receipt that they've changed the battery, motherboard and display. So they pretty much gave me a new phone. It's arriving tomorrow, i'll update when i get it
[Google Pixel 7 Pro] JW09I4:
Not when a device is booting to its EDL subsystem below the bootloader (think motherboard firmware) and is how most, if not all, devices are initially provisioned during manufacturing. It can be accessed in two ways, either via a specific button combination at power on or when the bootloader is corrupted (if it only boots to it and not the bootloader, the bootloader is likely corrupted).

The bootloader and EDL subsystem are not the same things - if a device isn't recognized by the PC while in bootloader mode [Fastboot or Fastbootd], it's either a software (update platform-tools and ensure Google's USB driver is installed via the SDK) or a USB cable issue (while it could be the device's USB port, that's highly unlikely unless it's filled with lint/debris)

Either the wrong button combination was held after your first reboot that resulted in the issue, or the bootloader was flashed incorrectly, since flashing the wrong init_boot.img || boot.img to the wrong boot/init_boot partition will not result in the device stuck in QLoader Mode

Many, myself included, have incorrectly flashed the wrong image to either the boot or init_boot partitions, and it does not prevent the device from booting to the bootloader since the bootloader is a separate partition, loading independently before the boot or init-boot partitions

The EDL subsystem is below the bootloader (think motherboard firmware) and is how most, if not all, devices are initially provisioned during manufacturing - if it only boots to it and not the bootloader, the bootloader is likely corrupted.

EDL mode shows the device as a COM serial device because a custom EDL application flashes a single EDL image to the device via serial that contains all partitions, including the bootloader, writing/overwriting the correct ROM address space

If the EDL subsystem was entered via holding a button combination at power on, you can exit it, but if it's due to corrupting the bootloader, warranty the phone since Google doesn't provide access to its internal EDL application or the EDL-specific ROM images. You can try Google's flashing through their site once you've installed the EDL driver, but I doubt it works if the device is in EDL Mode.

I can't recall what the button combination is, but do know it can be found on the OnePlus 8 forum since someone has uploaded the [EDL] QLoader program and images for recent OnePlus devices (the QLoader drivers can also be found there, as the device should show up as "Qualcomm HS-USB QDLoader 9006" or "9008" - all Qualcomm Android devices use the same QDLoader COM driver AFAIK)

To prevent issues like this in the future, always be mindful about checking the fastboot flash command to ensure you're not flashing the bootloader on accident and never flash both slots at the same time until after you've verified the device boots without issue after first flashing the active slot.
[Google Pixel 7 Pro] iplux:
Yeah, i assumed it was in EDL-like state, but as far as i know, we dont have tools available for pixels yet. Also the phone wasn't able to make a connection with the pc for more than 5 secs, and it was being recognized as Bulk-in COM device, no signs of a phone whatsoever. I got the phone back today, they've replaced the motherboard, battery and the display (pretty much gave me a new phone lol).

Also, I've flashed boot.img instead of init_boot AND ON TOP OF THAT, it was a patched boot.img from older firmware build, with the january one. I can't recall if i used the wrong fastboot command.
[Google Pixel 7 Pro] JW09I4:
For rooting, init_boot.img must be patched and flashed for the Pixel 7 Pro, not boot.img

AFAIK, Google's custom EDL application and the applicable EDL-specific image files have never leaked - except for OnePlus devices, I'm unaware of any other manufacturer that's had those internal-only pieces of software leaked.
[Google Pixel 7 Pro] oko17:
Have you been charged for the replacement? Because I probably have a similar problem
[Google Pixel 7 Pro] JW09I4:
Unless it's out of warranty, you shouldn't be charged since it's a quick fix if Google or one of their repair centers fix it since it's ~15min fix when you have access to the EDL program and image (it's a single image and literally take only 10 - 15min to overwrite all the partitions).

Replacing the motherboard is more labor intensive, and if it has to be done out of warranty by a repair center without access to Google's QDLoader program and image, it would likely be ~1hr labor plus the cost of the board (while a repair center's method may be slightly different, this shows how to replace the motherboard)
[Google Pixel 7 Pro] iplux:
Hello, google told me to bring it to a repair centre. I did, and they replaced the motherboard, display and battery and gave me the phone back functional... with gps not fiding any satelites, wifi 5ghz dropping just 2 meters away from the router and there was some dust under the telephoto lens inside the phone... i complained that their quality control SUCKS at repair centers (they probably forgot to attach one of the antennas to the mobo), and they now offered me a replacement. Im still trying to arrange it, thats rhe hardest part cuz im in a country where they're not selling phones.
[Google Pixel 7 Pro] oko17:
Thank you guys for your replies.

While being from Poland, I bought my P7P from amazon.de and contacted their support about the brick during update. Actually I realized that I have done everything okay but, I've stuck on fastbootd for like 30 minutes and then forced restart in recovery and before, the fastboot-all.sh stucked on bootloader so I wrote the commands manually, looks like MacOs<>ADB isn't the best combination.

At the beginning the consultant told me to contact directly with Google, but I complained that although there is general support page in polish, Google Pixels are not officially released in Poland and there are no repair centers. They proposed to send the phone back and full refund. So finally I'm not happy because I lost the full quality 4k videos from my last city-break (I have Google Photos backup in high quality, so photos are decent but videos only Full HD and LQ), but at least the replacement won't be a pain. Actually I will be refunded with the starting price, so I will probably spare ~100-120 euros, but it's not worth the lost data (videos), time and nerves.
[Google Pixel 7 Pro] JW09I4:
This isn't the same issue if it's booting to the bootloader and allowing access to fastbootd and recovery. A device booting only to EDL mode is hard bricked, as that's the low level system below the bootloader that allows writing all partitions from a single image, and if a device is only booting to EDL mode, it means the bootloader has been corrupted.

If you can boot to the bootloader, you can flash the device via Google's firmware page (select "Flash" next to the image version) by using the online Android Flash Tool
[Google Pixel 7 Pro] oko17:
Yes I'm aware of it. But after I forced the restart to system in fastbootd, it booted once, Google Logo appeared for few seconds and since then nothing but black screen. The only signs of life, were charging and connecting to Win10 it manifested as "Pixel ROM recovery"
[Google Pixel 7 Pro] immortalwon:
If every device had flash recovery tools like the older OnePlus devices like MSM, it would be ez to flash devices. Devices that don't have it, you need to do it right the first time and requires a lot of research. Hopefully you get it resolved.
[Google Pixel 7 Pro] JW09I4:
Have you tried booting to the bootloader and flashing the individual partitions directly from there (e.g. only flash boot, init_boot, and system, extracting them from the compressed file in the factory images download)? This assumes you have already unlocked the bootloader; if not, you'll need to unlock it first, which will wipe user data. You could also boot to recovery and sideload an OTA (just-in-case, OTA and factory images are different - OTAs are for sideloading, whereas factory images are for flashing partitions directly).​

​

You should be able to flash the device without issue since the bootloader isn't corrupted and the device isn't booting only to QDLoader Mode (it's obvious when this happens since it's always recognized in an OS by "Qualcomm Loader...").​

Flashing isn't difficult and only requires someone to download platform-tools from Google's dev site provided they have an unlocked bootloader (as well as Google's USB driver), but commands do need to be double-checked before executing them to avoid issues.​

I'm unsure what's meant by "a lot of research", as Google provides partition flashing instructions on the dev site and fastboot provides it's man page by executing:

fastboot -help

For the vast majority of devices that are unable to have their bootloader unlocked due to carriers and a resultant loss of advert and data mining revenue, the only method is sideloading an OTA image provided by the carrier (sometimes the OEM, but often the carrier only)

All devices have EDL mode programs and images, however why these are internal only is baffling since it's easy to put a device in EDL Mode and use the program to write/overwrite the ROM with the factory partition structure (it's literally point and click, taking 10 - 15min before the device is bootable again) and, upon flashing, the bootloader is automatically locked since that's the default state of every device.​

​
[Google Pixel 7 Pro] Namelesswonder:
The phone doesn't have QDL or use QDLoader software. Those are Qualcomm proprietary protocols and software for their SoCs, the phone doesn't have a Qualcomm SoC.

Stop bringing up QDL, literally just stop. You are getting nowhere. You can't use QDLoader with any Tensor device.

You also can't use Exynos download mode tools either, as Google has appeared to change the boot ROM and device IDs to make them incompatible.

There is nothing you can do, you can get into Pixel ROM Recovery for 10-30 seconds before the device automatically reboots, however it is for nothing as there are no tools to interact with the device in ROM recovery mode.

The best someone has gotten is to send the first stage bootloader to the device, however because the boot ROM is a blackbox and nobody knows how to further interact with it there has been no more progress.

Without the tools that Google uses your only option is to return the device if you can't force the device to boot the Android bootloader.
[Google Pixel 7 Pro] oko17:
Yes I tried it, pushing Power or Power+VolUP/VolDown for over 60 seconds do nothing.
[Google Pixel 7 Pro] immortalwon:
Probably internal because they want to also make money to flash peoples phones.
[Google Pixel 7 Pro] oko17:
You are right. As I wrote - I already contacted amazon.de, and will get full refund, so finally it's not that tragic.
[Google Pixel 7 Pro] JW09I4:
If you haven't already mailed it back, it's a relatively simple fix - simply flash the three aforementioned partitions directly from the bootloader, as there's likely nothing physically wrong if it still boots to the bootloader and the device is able to have its bootloader unlocked.
[Google Pixel 7 Pro] JW09I4:
Why does the device have a QDLoader mode and display as Qualcomm Loader USB... While in that mode?

Nvm - I made assumptions due to COM port wording in another post. Thanks for letting me know =]
[Google Pixel 7 Pro] iplux:
Actually if they can prove that you caused the damage, they can charge you for sure. Samsung's been doing it for ages, if you trip your knox and brick your phone after that, they blame you and repair the phone out of warranty.

Well, i sent my phone to comspot which is an authorized google repair center, and apparently they dont have the qloader program, because they've replaced my motherboard for sure (my imei is different). The display, motherboard and battery were replaced under warranty for me.
[Google Pixel 7 Pro] iplux:
Lucky... i bought mine from amazon.co.uk and i live in bulgaria... had to assure google that i cant bring the phone back to the uk, but i can send it to germany... also there is another problem - i cannot ship it from my country directly to them, it has to be picked from an address within the country, then the replacement will be sent back to the same address it got picked from... im currently trying to arrange that through a reshipping company, but its pain... 60€ for shipping to germany, and i'll probably have to pay another 60 on the way back from the reship to me, will see how it goes...

Also it should be possible to get it fixed in poland, at least i think so. When google sent me the prepaid shipment sticker i have to stick on top of the box, the delivery address was polish... so they probably have a warehouse there or something...
[Google Pixel 7 Pro] JW09I4:
Timing is off, as you need to release vol+ while still holding power as soon as the device powers off - holding all three continually will not boot to the bootloader. If releasing Vol+ didn't boot to the bootloader after 10s, release all buttons and hold down Power and Vol-
[Google Pixel 7 Pro] oko17:
I'm sorry this happened to you. That's a pain in the a..

Have you ordered it from amazon uk to Bulgaria or have you bought it being in UK?

I sometimes buy and return things from amazon.it and they don't have prepaid labels to return like amazon.de/fr but they are refunding it, after showing the invoice.

Yes there are few Amazon Warehouses in Poland, few times I ordered items on amazon.fr/de/it and they came to me from a warehouse 80km from my home :D
[Google Pixel 7 Pro] oko17:
Okay thanks for this. Although I already packed this Pixel 7 Pro, it's worth to try it.

EDIT: Unfortunately it didn't help.
[Google Pixel 7 Pro] iplux:
I ordered it through amazon to bulgaria

I dont wanna contact amazon about the phone, they can probably refund it, i just dont want to deal with the phone being held at customs for like 2 weeks.

I contacted google though, and i was trying to say that google probably have warehouses in poland. They sent me a prepaid label for pickup from an address in Germany, and the phone will get shipped to "ul. logistyczna 7 sekocin stary", which is in Poland and seems a bit odd how poland is a non-supported country, but they're sending my phone to Poland.
[Google Pixel 7 Pro] hongsedaima:
I encountered a similar problem yesterday. I used Magisk to modified the init_boot.img file, deleted the "-w" option, and then used "flash-all" to flash the phone. However, it failed halfway through and my Pixel 7 Pro turned into a brick. A merchant claimed they could fix it without opening the phone, so I sent it to them to handle. Hopefully, they can solve the problem.
[Google Pixel 7 Pro] JW09I4:
AFAIK, there's only two ways to fix the device without opening it: if you soft bricked it and it still boots to the bootloader (you could fix this) or if they have the requisite Google EDL program and image to flash the device while in EDL mode if it's hard bricked.

Generally, it's recommended to only flash the active or inactive partition when a partition image has been modified, not both (I'm unsure why trying to flash all partitions in fastboot with the modified init_boot image would result in a bricked device and it seems as though this would indicate the device is soft bricked since the radio and bootloader get flashed first prior to all other partitions.)
[Google Pixel 7 Pro] iplux:
I sent my phone to an authorized repair shop and they've changed the battery, motherboard and display. Im not yet convinced that even google themselves have such a program (in repair centers).
[Google Pixel 7 Pro] JW09I4:
I know =] I was replying to @hongsedaima, as those are the only two ways I know of to flash a device without disassembly.
[Google Pixel 7 Pro] Barsky:
My case is during Flash-all bar it stopped with some error I don't recall. THe phone was left in fastbootd mode. I chose to reboot device. Locked in edl on com 4. Went to Acherion or whatever it's called. He said "Mainboard needs replacing. Battery seems fine, but they have no mainboards as they are backordered. It has to go to google.

Oh well, dropped it off at FedEx that afternoon. My phone didn't have there various problem others I've read about. Just pray it stays the same .