Database Users

Hard brick? Can't boot to recovery

So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.

You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM

vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.

I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.

hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.

eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!

[REQUEST] US996 (Unlocked, not USC variant) stock recovery image or full firmware

Dear all.
My phone is US996 Unlocked, no USC variant model.
My phone has bootloop to recovery. My phone can't boot to system OS.
I tried flash boot.img and wipe data partition, I can't solve my problem.
Anyone, Can you help me?
I need stock recovery image or full firmware(KDZ).
Thanks.

naraymm said:
Dear all.
My phone is US996 Unlocked, no USC variant model.
My phone has bootloop to recovery. My phone can't boot to system OS.
I tried flash boot.img and wipe data partition, I can't solve my problem.
Anyone, Can you help me?
I need stock recovery image or full firmware(KDZ).
Thanks.
Click to expand...
Click to collapse
I was in a similar position to where it would just always boot into recovery forever. I tried doing several restores from stock and other backups. Different ROMs and even went through dirtysanta again. Nothing worked.
What wound up working was me getting into the device's factory restore screen (not TWRP's). I believe you get there by turning on the device while holding the Vol down + power button, when the LG screen comes up - let go of the power button for like 1-2 seconds and then press/hold it again. It should be a white screen that's asking if you want to do the factory screen or not. Just do that. It did its thing - then went to the LG screen again. I was a bit impatient and only waited like 2 mins. It didn't go anywhere (you could probably wait longer or so) but I just simply took out the battery and then put it back in.
It did wind up booting to the system again after awhile.
Just letting you know what I did after I messed up with a certain thing in a hidden menu.
Twisted

Not solved.
twistedvip said:
I was in a similar position to where it would just always boot into recovery forever. I tried doing several restores from stock and other backups. Different ROMs and even went through dirtysanta again. Nothing worked.
What wound up working was me getting into the device's factory restore screen (not TWRP's). I believe you get there by turning on the device while holding the Vol down + power button, when the LG screen comes up - let go of the power button for like 1-2 seconds and then press/hold it again. It should be a white screen that's asking if you want to do the factory screen or not. Just do that. It did its thing - then went to the LG screen again. I was a bit impatient and only waited like 2 mins. It didn't go anywhere (you could probably wait longer or so) but I just simply took out the battery and then put it back in.
It did wind up booting to the system again after awhile.
Just letting you know what I did after I messed up with a certain thing in a hidden menu.
Twisted
Click to expand...
Click to collapse
Thanks for your reply.
But, I didn't solve the problem. I tried your method, but is's no changed. bootloop to TWRP recovery.
I can't use my phone.

Solved . Thanks to all member
Dear all.
I solved the problem.
I tried flash system.img and boot.img use fastboot flash command.
and re-flash de-odex system use TWRP again, wipe data and cache.
It's rebooted to system OS.
Thanks.

H910 bricked after pulling battery during system lockup?

So this is a weird one for me. I've been running an H910 on an LOS 16 build from I think August and Gamma kernel 3.0 (never found the time to update stuff), and a couple nights ago I had the phone completely freeze on me while switching browser tabs, wouldn't even shutdown after holding the power button for ~30 seconds, so I pulled the battery to restart it. However, when I powered it on, after the initial LG logo I just got a screen of unchanging static IDENTICAL to what this poor soul had in the third photo of his linked album. My anxiety then ramped to 10 when I tried booting to recovery and after the "are you sure you want to delete your data" prompts I was greeted by the exact same screen. Booting to download mode would show the same screen after the few seconds of the "download mode" photo, and looking back I'm pretty sure it was just booting to download mode after encountering an error when I tried booting to system or recovery.
The bootloader was A-OK though, so the first thing I tried was flashing the latest TWRP, which seemed to work. I was able to boot into the system, but it was pretty buggy (the open apps button didn't work), so I tried booting to recovery, but it still gave me the static. I booted to system and it worked again, so I went back to fastboot and flashed the recovery again, which put me back where I started, static on everything but bootloader.
At this point I came to terms that things were getting wiped and began looking up what I could do in terms of KDZ flashing. I first settled on converting to US996, so downloaded US99610f_00_1205 and after dumping my system tried flashing it with the patched LGUP using the partition DL option. When I did, it cleared up the static issue in download mode showing the "Firmware Update" header and everything beneath it, but then download mode was still what recovery and system would boot to. I could boot to fastboot, but my bootloader was now locked. I tried that a couple times, but always got the same option, and the "Upgrade" option in LGUP would always return an invalid KDZ error due to H910 -> US996. My device still showed up as version H91010v as well. I then tried flashing over the H91510e_00_VTR_CA_OP_1205 KDZ as described in this thread for getting H910 root, but this gave me the same results.
So that's where I am right now, a phone with nothing but Download mode and where using Partition DL to flash stuff doesn't seem to actually flash it. The program I've been using is the LGUP files in this thread that's always linked. Any help on what next steps to take would be greatly appreciated, thank you.

Bricked Pixel 4?

Hi guys,
A few days into this fiasco now aha - my Pixel 4 seems to be (nearly entirely?) bricked.. won't turn on past the fastboot screen, pretty much stuck in a loop there.
I fear that I may have wiped it entirely or otherwise severely corrupted it. Was originally trying to root it, but never got that far and ended up in this mess.
I have tried to re-flash from the website as well as the batch file but it keeps getting stuck on the "fastbootd" screen when "uploading partition data 1/10".
I can access fastboot mode. It is unlocked. Cables and all that are definitely fine. Just can't bring it back to android.
Thanks for any help in advance
Edit: here's a link to the flashing process and what happens - Video

Anyone? Aha

have you tried to flash factory image locally? (instead of web flasher?)
what does the fastboot screen say when it boots into fastboot?
(It gives a reason for having booted into fastboot)

troubleshooting, bricked overnight

Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.

PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/

I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?

PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.

I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.

PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look

That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...