Develop Bugs

[Q] htc wildfire s boot loop problem

So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:

a bit more info plz
alemale said:
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
Click to expand...
Click to collapse
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue

rishr4 said:
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
Click to expand...
Click to collapse
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.

alemale said:
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
Click to expand...
Click to collapse
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
2. There is a possibility that you could "brick" or bootloop your phone. There are two types of brick: soft (recoverable) and hard (non-recoverable). With a soft brick, the phone will not boot or keeps rebooting ("bootloop"), but it can be started in bootloader mode which allows repair of the ROM. With a hard brick, the phone won't even boot into bootloader after holding the power button for 10 seconds and the phone must be returned to HTC for service.
Click to expand...
Click to collapse
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the
PROCEDURE 1
Click to expand...
Click to collapse
then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.

rishr4 said:
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
Click to expand...
Click to collapse
I tried to unlock the bootloader but it wanted 2.3.5 so i tried to install the new version. now it can't do anything. Well this didn't broke my heart because the phone is pretty worthless . now i have to buy new phone sooner than i planned but still all help is still accepted.

Hi, exactly the same for me : I bought the phone 2 years ago and immediately unbranded it with a goldcard, but never tried to unlock it because it was my wife's and I didn't want to risk anything.
Now she got a new phone, I wanted to play a little with the Wildfire S ^^.
In order to unlock the phone on htcdev I had to update it from 2.13.401.2 to 2.13.401.3, with RUU because can't update with OTA (different CID), with goldcard inside.
After the RUU finished, it says "congratulations everything went well", but actually the phone does not boot, stocked in a loop "quick flash / turns off", can't access bootloader, no USB detection for ADB.
Can't send it to HTC because the 2 years warranty is expired, how ironic ! :laugh:
So... if anyone does know or see any trick that could help to boot anything on this "seems to be hard-bricked" kid... huge thanks to you

[Q] [HELP] P350 stuck on LG logo 4 softkeys blinking

Hi, I've just registered in this forum, though I've been reading you guys for almost a year. I just want to say that you guys are awesome, i've learned too much about android because of you.
Introduction
Said that, I recently had a problem with my P350g, I'll try to be as clear as possible hoping you can help me out.
The problem came after i installed CM 9 [stable 8] on it, at first it worked perfectly (a very few panics or reboots but i'm used to it :laugh. The next day after taking a photograph the cellphone got stuck, it had done that several times before with some other ROMs so i didn't pay much attention to it, so i took the battery off and put it again, and when I tried to turn it on, there it was, the lg logo with the 4 softkeys blinking.
-- It doesn't enter to recovery (i had recovery installed at that time) pressing [- power send] at the same time, it just stays there with the lg logo blinking.
-- It does enter to the emergency mode (yellow background with "emergency mode" in black letters) pressing [+ - power] at the same time.
-- It does enter to the fastboot mode pressing [+ power send] at the same time.
what i've already tryed:
--- i've read the wiki about this phone and try everything there (and everything found on google which is pretty much the same)
http://forum.xda-developers.com/wiki/LG_Optimus_Me
--- i've tryed using the KDZ updater as somebody on this forum recommended:
http://multidroid2.feed.nu/2012/03/27/how-to-unbrickflash-your-optimus-melg-p350-2/
using firmware from here:
http://lg-phone-firmware.com/index.php?id_mod=5
and from somewhere else on the internet, the problem here is, that when it comes to "restart the phone", it doesn't start, it just keeps getting stuck on the lg logo with the 4 softkeys blinking, after some time the KDZ updater shows an error: Upgrade Error WParam: 100 LParam: 6
--- i've tryed flashing the recovery from fastboot mode as shown on this thread:
http://forum.xda-developers.com/showthread.php?t=2131247
it flashes well, everything "succeeded" but whe it comes to reboot (flashboot reboot) the cellphone says on the screen rebooting cellphone (or something like that) but it never reboots. if I take the battery off and put it on again, and then try to turn it on, the cellphone shows at the same problem, the lg logo with 4 softkeys blinking.
--- I've also tryed this tool:
http://forum.xda-developers.com/showthread.php?t=1948326
it hasn't solved my problem either.
Computers' info
I've tried this on 2 computers:
windows 7 x86
windows 8 x64
both of them have the drivers installed, I've disabled the modem on both of them, both of them have the latest android SDK tools
both computers give me the same problems, please i need your help, i'm desperate, I've been with this problem for several days and I can't solve it. I hope you can help me out

bump!
Anybody? please, i'm desperate

Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?

kD said:
Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?
Click to expand...
Click to collapse
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens

I couldn't fash a rom via fastboot
IsraelMP said:
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens
Click to expand...
Click to collapse
Hi everybody, i tried to flash a zip containing the rom on my p350, though i could not flash it. i used the command:
fastboot flash system rom.zip
but it says the file/rom size was smaller than expected. (honestly i can't remember the actual sentence) and then it says (x < y) where x is the suposed size of the rom and y is the expected size.
i tried with several roms, and a backup a user uploaded somewhere which was suposedly legitimate.
Is there something i can do?

download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again

My Method
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).

Thanks for replying
MeeDa said:
download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again
Click to expand...
Click to collapse
thanks for replying, i did that, when i just plug it without pressing any button the cellphone does not get recognized by the software, when i plug it in emergency mode it does get recognized but the software gives me an error.
blazecodester said:
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).
Click to expand...
Click to collapse
thanks for the answer, I tried that way, though it keeps getting stuck in the LG logo with the 4 blinking softkeys when it comes to reboot the cellphone.

I want to root my ZE551ML but I don't know what to do pls help.

I tried to root my phone last night, but I stop midway of the process because of some problems like "phone not turning on with no vibrate at all when I restart after its stuck to inverted white screen, when I luckily turn it back on but it bootloops".
Heres the details:
I run unlock.bat then after its done it reboots with inverted white screen with logo then I run restore.bat and after it restart there is no sign of warning "failed verification" until it fully loads up, I go back to fastboot again to flash TWRP after running twrp.bat it says "flash succesfully" and the program closed by itself, then I go to recovery mode after rebooting I saw android error just like how it use to be. I press power button + volume up then release the volume up then I see the stock recovery (which it should be TWRP since I've done flashing it).
I think that my bootloader is still locked since there's no warning display of "failed verification". So I repeat the steps again after running unlock.bat, it reboots and the screen is inverted but it's stuck up to white logo, I waited for a while but nothing happens so I tried to reboot my phone "holding power button (power off)" when power on, it wont turn on, no vibration just a sound on laptop "connected sound and disconnected sound" I tried to power it on many times but still no luck I got panicked, jittery walking back and forth :crying:. Then I disconnect the usb cable and I tried to turn it on and suddenly I feel the vibration on my phone then it boots up but still stuck in white screen then it restart after keeping it for too long (while watching videos related to my problem)...
then my friend here said "ohh it bootloop" he read the instruction and he said to try this
"FAQ 1. Stuck at white screen with asus logo?
Sol. a) White screen means you are unlocked (action of unlock.bat), so you may give a try to restore.bat in fastboot mode."
and it solve my problem my phone is working again ... But I want to continue to root it but I'm afraid which steps I should go next, I still don't see the warning "failed verification" after my phone boots up and works again... I need HELP thank you
I also got question: is my bootloader unlock since it inverted white screen? or it still locked since there no sign of warning "failed verification"?

@PrinceLys
What is your build number in settings ,about phone ?

timbernot said:
@PrinceLys
What is your build number in settings ,about phone ?
Click to expand...
Click to collapse
ahmm I think this?
model number: ASUS_Z00AD
android version: 6.0.1
software information: WW_4.21.40.223_20161216
P.S my phone is back on working state.
I just don't know if I can proceed to root after the incident. I don't know, I just want to make sure that my bootloader is still unlocked after what I've done (it did white screen with black asus logo) or.... it doesn't unlocked at all since I don't see this warning "your device has failed verification and may not work properly." (I've attach screenshot from the video tutorial)
I tried to manualy check if my bootloader is really on unlock state but I can't using these methods
method 1: on device’s dialer dial *#*#7378423#*#* (failed)
method 2: fastboot oem device-info (failed)
my recovery it still on stock recovery even after I flash twrp
btw guide source: https://forum.xda-developers.com/zenfone2/general/root-install-xposed-marshmallow-6-0-1-t3456443
Q: should I still continue to flash twrp until it install?

Theres 2 bootloader unlock tools in general section , one is automatic

Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk

timbernot said:
Theres 2 bootloader unlock tools in general section , one is automatic
Click to expand...
Click to collapse
I'm going to look for it... thanks

musicman5844 said:
Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I've haven't fully read the instruction maybe tomorrow I will read it.
I just downloaded the files early and look into it... it seems like the versions are kinda latest (I don't know much about the droidboot ver. but I just look at the number on it "the higher the latest /heh") also the twrp is 3.0.3.
the ones that I used are all in package and it was 3.0.2 so I kinda go for the link you gave me
Thanks :good:

Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .

nanobrain---- said:
Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .
Click to expand...
Click to collapse
(I've finally think my bootloader is unlock after all.)
btw, did you succesfylly flash twrp?
Mine didn't flash (using twrp.bat), I guess I will try it again tonight if it fails again im gonna dl twrp from official and manually flash it.

Hard Brick with black screen and bootloops. Help will be appreciated

How my phone got bricked - Yesterday when i was listening to music my phone restarted, i turned it back on and it restarted again with a black screen (or blue screen because i can see it lighting up a bit).
I tried restarting it multiple times, turning it off and also punching it but nothing helped. Later i installed miflash and went back to stock rom. But the problem still persisted , black screen .
My PC recognizes the phone as a device , but i cant get into recovery or edl mode because the phone just reboots.
I have tried holding the power + volume up and every possible combination to get into some kind of recovery.
Now when i press the volume button on my phone i can hear the sound it makes when it can't go any louder , so im guessing my phone works .
Has anyone managed to fix this?
Edit: My phone got recognized by pc as QD9008 , and i was able to flash it with qfil , but my phone still has a black screen. I also flashed it with miflash and still black. Should i try doing the deep flash cable ? Will it even do anything ? Thanks.

Really don't know.

New info in post.

Did you unlock it and flash recovery?
Can you boot into recovery or it's just a black screen from the beginning?
Have you tried any other versions of zui?
Indian/Chinese marshmallow/nougat?

sotosgolf said:
Did you unlock it and flash recovery?
Can you boot into recovery or it's just a black screen from the beginning?
Have you tried any other versions of zui?
Indian/Chinese marshmallow/nougat?
Click to expand...
Click to collapse
Before i flashed my phone with mi flash , adb was able to recognize it , but now it can't so i cant flash recovery.
Everything is black with no image at all. I have tried other versions of zui 1.9 and 2.3. But i haven't tried an Indian version.

daxtera said:
Before i flashed my phone with mi flash , adb was able to recognize it , but now it can't so i cant flash recovery.
Everything is black with no image at all. I have tried other versions of zui 1.9 and 2.3. But i haven't tried an Indian version.
Click to expand...
Click to collapse
Since the screen has light and the phone is recognized by pc my money would go on firmware issue. I would try more versions of zui. I have read that qfil is better for flashing zuk than miflash. (I'm not an expert on this, just suggesting)

Hi, i hope you don't have the similar issues as i had?
Have a read!
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/zuk-z2-plus-stuck-edl-9008-port-help-t3713629

Flashed 3 different versions of zui and nothing . Let my battery drain but that didn't help either. So now i think my only option is to flash the unlock bootloader file , because i have read that could fix my issue but i cant get adb to recognize my device even in qd9008 mode or 900e . Any way i can get adb to work? Im really getting desperate here.

Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.

@daxtera, did you solve the problem? I had the same situation and still no luck

daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
open the phone and remove battery plug, then connect again

I have same problem. I disconnected battery, but nothing changed. I'm in stock ROM as it came from Bangood. Android 6.0.1 and ZUI versión 2.0.093 ST.
Problem came using phone normally without any flashing process. When connected to computer it is recognized as Qualcomm HS-USB QDLoader 9008. I tried to flash 2.0.093 ST ROM using QFIL but process always ended in Download file: Fire Hose Fail FHLoader Fail: Process fail. Can anybody help me to recover my phone usability? Pls give me any suggestion.
---------- Post added at 12:55 PM ---------- Previous post was at 12:54 PM ----------
I have same problem. I disconnected battery, but nothing changed. I'm in stock ROM as it came from Bangood. Android 6.0.1 and ZUI versión 2.0.093 ST.
Problem came using phone normally without any flashing process. When connected to computer it is recognized as Qualcomm HS-USB QDLoader 9008. I tried to flash 2.0.093 ST ROM using QFIL but process always ended in Download file: Fire Hose Fail FHLoader Fail: Process fail. Can anybody help me to recover my phone usability? Pls give me any suggestion.

daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
packpunk said:
@daxtera, did you solve the problem? I had the same situation and still no luck
Click to expand...
Click to collapse
Hello, would like to know, if you guys tried any further & were able to resolve this issue. Please advise.

daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
try this it might help ....
look at every post, many people have posted many different solutions, one might work for you
zukfans.eu/community/threads/deep-flash-revive-your-zuk-z2-from-hard-brick-state-9008-mode-easily.3504/
:good:

Dhananjay_Yadav said:
try this it might help ....
look at every post, many people have posted many different solutions, one might work for you
zukfans.eu/community/threads/deep-flash-revive-your-zuk-z2-from-hard-brick-state-9008-mode-easily.3504/
:good:
Click to expand...
Click to collapse
Thanks, the xda'ian who was facing this issue i.e. 'Black screen irrespective of QFIL success' reported that he was able to revive by opening the back cover & resetting the battery
Hope this helps everyone, who were facing similar issue.

kubersharma said:
Hi, i hope you don't have the similar issues as i had?
Have a read!
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/zuk-z2-plus-stuck-edl-9008-port-help-t3713629
Click to expand...
Click to collapse
rocky459 said:
Thanks, the xda'ian who was facing this issue i.e. 'Black screen irrespective of QFIL success' reported that he was able to revive by opening the back cover & resetting the battery
Hope this helps everyone, who were facing similar issue.
Click to expand...
Click to collapse
This didn't helped bro

xyro8651 said:
This didn't helped bro
Click to expand...
Click to collapse
My zuk z2 was like that. Press the power button. Then press and release the volume up for 10-15 seconds, then press and release the volume down 10-15 seconds. You press the power button anyway. Do it for about 5-10 minutes or more. Until the device reboots. When the device boots, choose download mode or EDL mode. Do a qfill or mi flash to flash your zuk z2

adhieputra1 said:
My zuk z2 was like that. Press the power button. Then press and release the volume up for 10-15 seconds, then press and release the volume down 10-15 seconds. You press the power button anyway. Do it for about 5-10 minutes or more. Until the device reboots. When the device boots, choose download mode or EDL mode. Do a qfill or mi flash to flash your zuk z2
Click to expand...
Click to collapse
It is not working bro |
My phone is still with that condition
screen with blank dark color with backlight

Question Hard Bricked Pixel 6 Pro Android 13

Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.

PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image

DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.

Read this thread if you haven't...

blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.

PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed

I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.

lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices

@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13

Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.

Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.

rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.

PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.

DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked

If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour

So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?

Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.

Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.