Develop Bugs

[Q] Phone won't turn on! Vibrates and Green LED only

morning guys/gals,
last night i put my phone to charge, woke up this morning and turned on the screen and it said "no sim card detected, reboot device". Now when I rebooted the device all I get is 5 vibrates and the green led light stays on. Screen stays blank!!. I tried battery pull several times, tried vol-down + power but all I get is the vibration with the screen off and the led on.
When I hook my phone to the laptop I can't access it via fastboot/adb, it shows up as "Qualcomm CDMA Technologies MSM" with a yellow exclamation mark in the device manager. I tried forcing different drivers on it (e.g. adb composite, bootloader) but none let me access the device via cmd.
Now I got clockwork, running latest android revolution 2.0.8, device is radio-soff and eng-soff.
What am I to do now? Is there possibly a hardware fault? If I cant get to access to the device to restore it to stock, I'm going to struggle to get the device replaced, isnt it?
any help is very much appreciated!!!

What ROM were you running on it Prior to this happening?
was there any apps running in the background?
the Vol - + Power should get you into bootloader, if you cant get into bootloader I would be tempted to say fooked, and take it back to the shop as they wont be able to boot it either,, but thats the defeatist attitude...

lefty83 said:
morning guys/gals,
last night i put my phone to charge, woke up this morning and turned on the screen and it said "no sim card detected, reboot device". Now when I rebooted the device all I get is 5 vibrates and the green led light stays on. Screen stays blank!!. I tried battery pull several times, tried vol-down + power but all I get is the vibration with the screen off and the led on.
When I hook my phone to the laptop I can't access it via fastboot/adb, it shows up as "Qualcomm CDMA Technologies MSM" with a yellow exclamation mark in the device manager. I tried forcing different drivers on it (e.g. adb composite, bootloader) but none let me access the device via cmd.
Now I got clockwork, running latest android revolution 2.0.8, device is radio-soff and eng-soff.
What am I to do now? Is there possibly a hardware fault? If I cant get to access to the device to restore it to stock, I'm going to struggle to get the device replaced, isnt it?
any help is very much appreciated!!!
Click to expand...
Click to collapse
it sounds like a h/w fault, i had a simlar problem on my classic desire, turned out it was the 3rd party battery i bought that was at fault, yours sounds diffrent though hope you sort it out

darkenedhammer said:
What ROM were you running on it Prior to this happening?
was there any apps running in the background?
the Vol - + Power should get you into bootloader, if you cant get into bootloader I would be tempted to say fooked, and take it back to the shop as they wont be able to boot it either,, but thats the defeatist attitude...
Click to expand...
Click to collapse
ok very strange, I was playing i around with the phone, now if I pull the battery and connect it to the usb cable the light went red instead of green and it automatically booted in clockworkmod (thanks to the "bug"). vol down + power didnt get me there so once I was in clockwork I thought let me wipe battery stats (eventho I wiped them when rom was freshly installed). I thought the device is unplugged but the green light stays on (after full charge), maybe battery issue. Now after wiping battery stats I'm able to boot the device again.
Thats weird but hey atleast my device is back on track. Either faulty battery or some software bug, either way if anyone experiences a similar issues (phone wont boot, just vibrates 5 times and green led), just pull battery, connect phone to usb cable on your laptop or wallcharge and clockwork should boot up, wipe battery stats and u should be fine

You gotta love that ClockWorkMod recovery image

Hi
I had the same issue yesterday. After one hour of stress(I have DHD for 4 days), I finally find out solution which worked for me:
1.) pull out the battery from phone for at least 10 minutes.
2.) connect phone to the charger.
3.) pull battery to the phone and wait
4.) after orange light recovery should boot up.
5.) wipe battery stat.
6.) enjoy your phone again.
Hope this will help to somebody .

May I know why such incident occured?

thermoska said:
Hi
I had the same issue yesterday. After one hour of stress(I have DHD for 4 days), I finally find out solution which worked for me:
1.) pull out the battery from phone for at least 10 minutes.
2.) connect phone to the charger.
3.) pull battery to the phone and wait
4.) after orange light recovery should boot up.
5.) wipe battery stat.
6.) enjoy your phone again.
Hope this will help to somebody .
Click to expand...
Click to collapse
my phone doese not turn on, when i press the volume - with power button, green light blinks. would not go in to recovery mode. when only power button is pressed it vibrates three times and amber light flashes.
please help

ray00136 said:
my phone doese not turn on, when i press the volume - with power button, green light blinks. would not go in to recovery mode. when only power button is pressed it vibrates three times and amber light flashes.
please help
Click to expand...
Click to collapse
Having the same problem and wiping battery stats isn't working for me! See here for more info on my problem!

thermoska said:
Hi
I had the same issue yesterday. After one hour of stress(I have DHD for 4 days), I finally find out solution which worked for me:
1.) pull out the battery from phone for at least 10 minutes.
2.) connect phone to the charger.
3.) pull battery to the phone and wait
4.) after orange light recovery should boot up.
5.) wipe battery stat.
6.) enjoy your phone again.
Hope this will help to somebody .
Click to expand...
Click to collapse
Thanks for your reply! this worked for me, allmost.
I did however had to press the Power button ONCE to start the phone.
- Plugged in charger, pulled in battery, (orange light was turned), then after 25 sec I pressed the Power button - and Voila! My Phone started as normal.
I diden't need to do any "Wipe battery status", but after reading about it I did it anyway. It was'nt necessery though in my case.
THanks a lot you guys for your replys! I thought for sure my phone was dead.

try sptool to format your phone except the boot loader then try to flash the phone, if its not working then change the mother board !!!!!

Bricked. Only white LED. Battery Good.

Pretty sure I bricked my phone. Been digging through the forums all night and can't find anything.
When I plug it into USB I can get the White LED indicator. Only sign of life tho.
Can't boot the phone at all though. Always just a black screen; no backlight.
No motorola logo..
RSDLite won't recognize because I can't get into bootloader mode.
Battery is fine, checked it with a multimeter and I'm at 3.3V
Tried a friend's Defy battery.. no dice.
Any suggestions?

does your friend battery have a full charge on it?
it happens to me before, i turn the defy off, plug the charger, and left it for 30 to 45 minutes and i can boot afterwards. try it, might work for you too.

thanks been trying that out. his has full charge. I also mcgyvered mine and it's fully charged as well.. hmmm

what did you do that caused the bricked phone? did you try to downgrade it from 2.2 to 2.1? because that caused me the same thing, white led, rsd wont recognize it (windows error sound when plugged into usb), and i couldnt solve it, had to bring it back to motorola...
sent from my cm7 defy...

i have read somewhere in the devs forum about a corrupt bootloader experienced by one of our friend there. try to look into that and possibly get you some clues. Another possibility is to remove your sdcard, my crappy class 6 gives me a white lights only boot when im still in froyo, although it happens only once or twice. at this point, might as well try it out eh?

you need to flash with rsd it will read the phone is stuck in bootloader mode download your stock sbf and flash with rsd it will bring your phone back to life!!

make sure you remove battery plug in usb cable then replace battery while holding the vol + key

zakoo2 said:
what did you do that caused the bricked phone? did you try to downgrade it from 2.2 to 2.1? because that caused me the same thing, white led, rsd wont recognize it (windows error sound when plugged into usb), and i couldnt solve it, had to bring it back to motorola...
Click to expand...
Click to collapse
I actually purchased it from someone who said that it was bricked. I am trying to get back in touch with them to find out what happened but no info yet. I've been trying to deduce what could of happened. But one thing I'm almost certain of is it wasn't water damaged. As I said the battery is still intact and I've never seen a phone go without taking the battery with it. Moisture indicators look fine as well.
I don't get any sounds when plugging the phone into USB. Device manager doesn't even blink. Can you return to Motorola if you are off contract? Any info on how that works? Not giving up yet, just wondering.
cengiran said:
i have read somewhere in the devs forum about a corrupt bootloader experienced by one of our friend there. try to look into that and possibly get you some clues. Another possibility is to remove your sdcard, my crappy class 6 gives me a white lights only boot when im still in froyo, although it happens only once or twice. at this point, might as well try it out eh?
Click to expand...
Click to collapse
Thanks, I will definitely look into that corrupt bootloader situation. I pulled the sd card (been in there the whole time) but it didn't make a difference. There wasn't really much on the SD Card except for a few empty (autopopulated) directories: LOST.DIR, .android_secure, etc.. and the stock froyo SBF file for the phone: p3_jordan_umts_2.2.1..(blahblah).sbf it's a US T-Mobile Defy.
So it likes like maybe the previous owner was trying to flash. Although I don't know why they would put SBF on the SD.
pmp326 said:
you need to flash with rsd it will read the phone is stuck in bootloader mode download your stock sbf and flash with rsd it will bring your phone back to life!!
Click to expand...
Click to collapse
pmp326 said:
make sure you remove battery plug in usb cable then replace battery while holding the vol + key
Click to expand...
Click to collapse
RSD doesn't ever see the phone at all. Thanks for the suggestion. Tried to insert battery after plugged in and while holding vol + key but no difference. Been trying all sorts of key combinations from the forums but no luck there either. The drivers are completely up to date.
All suggestions appreciated! Thanks guys!

any more ideas by chance ?

It's a silly thing, but have you tried pressing the power button AFTER connected USB? Anyway try switching Config-->DeviceID options in RDS.
I was stuck at your point, only white led, hacked the battery and it has been recognised by RDS after some unistall/reinstall... try, try and try again

This happend to me too (black screen, only white led) when i tried to flash some korean froyo. I just removed the battery, connected usb, put battery back, power + vol [+] and RSD recognised it (even if screen was black)

I confirm (I had the same problem...) that your Defy is not bricked :
- don't connect the phone to the PC
- launch RSDLite and choose your SBF
- remove the battery cover (of your phone of course, not your PC ! )
- remove the battery
- plug the USB cable only in the phone
- your phone in left hand, press power + vol.up with 2 fingers of the same left hand
- put the battery into the phone with your free hand, so the right !
- when the white led appears, you can remove your 2 fingers from buttons
- then plug the USB cable in the PC
- RSDLite recognize your Defy !!!
- you can flash...
Sorry for my bad english !

If all above suggestions still fail on you. I would think it might possibly the USB port is broken or some hardware issue which is why it was sold to you as bricked Defy in the first place.

one2wan said:
I confirm (I had the same problem...) that your Defy is not bricked :
- don't connect the phone to the PC
- launch RSDLite and choose your SBF
- remove the battery cover (of your phone of course, not your PC ! )
- remove the battery
- plug the USB cable only in the phone
- your phone in left hand, press power + vol.up with 2 fingers of the same left hand
- put the battery into the phone with your free hand, so the right !
- when the white led appears, you can remove your 2 fingers from buttons
- then plug the USB cable in the PC
- RSDLite recognize your Defy !!!
- you can flash...
Sorry for my bad english !
Click to expand...
Click to collapse
Thank you, my phone is alive

HTC Flyer stuck on boot screen after 3.2 upgrade

Today there was an update 3.2 for my HTC FLYER so I downloaded it and started the install process. ( This was an official update as my rom is official )
So I started the install process and after some time it installed, and it started booting.
When it came to the HTC booting screen ( green HTC logo with white background) it stopped there and never booted to the Home Screen. I kept it like that for aprox. an hour but it didn't move from there.
Every time I rebooted it , kept stucking on the same point and never loaded on the home screen.
I tried factory restoring, through HBOOT but it kept transfering me to the HTC boot screen and kept staying there without going to the home screen.
My device was already S OFF .
I also tried connecting it to my PC with the USB cable but it didn't want to install the drivers. It failed every single time. I tried running HTC Sync but also it never recognizes the device.
Can anyone please help me? I can't even turn the device off, it keeps restarting to the boot screen and stays there for an unlimited amount of time.
With regards,

BUMP : Anyone???

I got the same problem. Anyone has a solution?

eric
got the same problem,can't even get the device to reset to factory,and the power light just keep blinking orange color,can't root to another OS either.
have tried the adb method and can't find the device.so can't do the RUU way.
anyone got any ideals?

I am in the same situation right now since last night... badly need to go back to the S-Off and phone feature running....

I've read about this problem in a german community. This workaround may work for you, but you do this at your own risk. I'm not responsible for any malfunctions or damages on your device! also note, that your sd-card will be completely wiped!
If you read the bold text above, you can try this:
plug in your flyer with your HTC AC charger
enter hboot
jump to "factory reset" with vol-down
HOLD vol-down AND power for ~30sec (after ~15sec the screen will be black with background-light, still hold down both buttons!)
after ~30sec the screen will be completely black
now you should see the green "arrow-ring", only now release vol-down and power
wait up to 10min and your flyer will boot properly

Got the same problem.
It's frozen: nothing works.
How do you connect it to the electrical grid?
Can you let it until the battery runs out?
Please help.
Thanks in advance,
DD47

DonalDuck47 said:
Got the same problem.
It's frozen: nothing works.
How do you connect it to the electrical grid?
Can you let it until the battery runs out?
Please help.
Thanks in advance,
DD47
Click to expand...
Click to collapse
Just plug in your HTC AC-power plug.
If you do that, your battery won't run out.

Edit: Removed, because question was answered above.
Thanks, woggly4
DD47

boot the htc flyer
If you plug in the AC-adapter it won't run out of power but you need to power it on to use it.
First download the recovery.img file for your flyer.
Then you need to setup the android SDK in your computer.
Boot it into the fastboot mode.
And then you run this commands from your command line
"cd C:\"the path where you have the fastboot file"
"fastboot flash recovery "the path where you have the recovery".img

Desire Z wont power on :(

Hey guys,
Running ILWT CM7. Flashed about two weeks ago. My phone has been working fine except for the past few days where it's been constantly freezing, requiring a battery-out and turn on, and rebooting on it's own.
Last time it froze, I removed the battery and turned back on, and it got to the "htc" logo and froze. After ~25minutes, I took the battery out and tried again.
Phone seems completely dead, won't respond to power on, volume down and power on, no lights come on when charger cable is plugged in. When USB cable is plugged in and no buttons or anything on the phone is pressed, my laptop attempts to install drivers.
Tried leaving battery out for 30minutes and trying again, but no luck.
Any suggestions?
Cheers!

Stuck in RUU mode?
Kaph said:
Hey guys,
...
Last time it froze, I removed the battery and turned back on, and it got to the "htc" logo and froze. ...
Phone seems completely dead ... When USB cable is plugged in and no buttons or anything on the phone is pressed, my laptop attempts to install drivers.
... Any suggestions?
Cheers!
Click to expand...
Click to collapse
Looks like your phone is stuck in RUU mode.
In RUU mode you see the silver "HTC" logo as long as your phone is connected to your computer with an USB data cable. No charging lights will show in this mode.
You can use the following command to boot your phone to Android:
Code:
fastboot oem boot
When that does not work, because your partition table or system partition might be corrupted, then you would have to use the correct RUU (Rom Update Utility) for your phone to get it back to a working state.
When you have a bricked internal memory chip (emmc) than nothing will work properly to restore your phone to normal working conditions.
In the case you have an engineering HBOOT you could boot a ROM from SD card, but that is a far shot.
Best regards,
Catherall

catherall said:
Looks like your phone is stuck in RUU mode.
In RUU mode you see the silver "HTC" logo as long as your phone is connected to your computer with an USB data cable. No charging lights will show in this mode.
You can use the following command to boot your phone to Android:
Code:
fastboot oem boot
When that does not work, because your partition table or system partition might be corrupted, then you would have to use the correct RUU (Rom Update Utility) for your phone to get it back to a working state.
When you have a bricked internal memory chip (emmc) than nothing will work properly to restore your phone to normal working conditions.
In the case you have an engineering HBOOT you could boot a ROM from SD card, but that is a far shot.
Best regards,
Catherall
Click to expand...
Click to collapse
Thanks for the help
When plugged in with the USB cable -> computer, I still get no response from the phone itself. Screen doesn't turn on, still seems dead. My laptop still says "Installing device driver software" to no avail, and phone is still dead. No lights, screen is off, nada. As though it was powered-off.
ADB Devices lists nothing, and fastboot oem boot hangs on <waiting for device>.
Am I out of luck? I could send the phone off for repair, but as I'm rooted I think warranty is void.

Remarks
Kaph said:
Thanks for the help
My laptop still says "Installing device driver software" to no avail, and phone is still dead
ADB Devices lists nothing, and fastboot oem boot hangs on <waiting for device>.
Am I out of luck? I could send the phone off for repair, but as I'm rooted I think warranty is void.
Click to expand...
Click to collapse
Windows seems to need a driver installation for using fastboot. Did you try to automaticall install device driver software? Have you installed HTC sync on your Windows computer?
When your device does not respond at all, and even refuses to connect in fastboot, then nobody can tell that you have been rooted.
Best regards,
Catherall

Sounds like your EMMC is fried, as of now I don't think there's a solution other than sending it back. Many say HTC accept and fix it even though it is s-off
Sent from my HTC Vision using XDA

did you get this worked out? i had a similar problem, ended up booting into fastboot by holding the trackpad and the power button, then just selected reboot and my phone powered on like nothing had happened, i was running the same rom.

Hey, did you alreasy tourned your phone to the fastboot mode?
Or does your device still have a black screen during boot?

I rooted this phone and when I was done trying S-OFF, phone would not respond to anything. It would only blink the orange notification light when I pressed Power and Vol+, or it would stay steady green with both Vol keys and Power. But the phone screen would never turn on. So after trying for hours to figure it out. I finally took the battery off, plugged the phone held pressed the power button and then put the battery in place the phone finally turned on and it worked. I turned the phone off again and it was doing the same issue. So I did the same step but this time with power and vol- to get in the bootloader and changed the hboot version to Desire Z. After that phone works perfectly, turns on and off with out any issues.
I did have to try the trick a couple of times idk why but it would work once in a while not everytime i tried it. Hope this helps anyone who also ends up with a similar issue.

Question Bricked my Prixel 6 after flashing stock rom

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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