Related
Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda
LMurphy said:
Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda
Click to expand...
Click to collapse
Definitely sounds like malware. You have two choices that I see, either root and custom rom or flash back to stock. Since you are stock you'd just be overwriting your existing install. Read this thread and decide your course of action http://forum.xda-developers.com/showthread.php?t=2203309
Looking for a quick fix here as I can't go to the service centre and get a replacement until at least Tuesday, and I need my phone working before then. I'm hoping someone else has had the same problem and can help me out.
My Moto G froze and became unresponsive (while I was refreshing my Gmail inbox) and it would not accept any input. I held down the power button and the power menu opened, however when I tried to power it off, it wouldn't accept my touch input. So obviously the next course of action was to hold down the power button for 10 seconds to force a reboot. The Motorola logo appeared and the phone vibrated... then it did nothing.
I tried this a few times and still nothing happened. I am able to boot into the bootloader, but apart from that, the phone goes only so far into the boot cycle before the screen goes black and does nothing.
Motorola's website suggests that if the Moto G becomes unresponsive, and the regular 10 second reset doesn't work, you should hold the power button for 120 seconds and keep it plugged in to a charger. This didn't work either. As of right now, my phone is just sitting here on my desk with what I would call a 'black screen of death.' Help would be appreciated.
I cannot boot into recovery, I cannot access anything. The phone is stock, unrooted, and running KitKat 4.4.2 without any modifications whatsoever. It's about 5 months old now, so it's still covered by warranty and I don't want to void it.
Narwhal73 said:
Looking for a quick fix here as I can't go to the service centre and get a replacement until at least Tuesday, and I need my phone working before then. I'm hoping someone else has had the same problem and can help me out.
My Moto G froze and became unresponsive (while I was refreshing my Gmail inbox) and it would not accept any input. I held down the power button and the power menu opened, however when I tried to power it off, it wouldn't accept my touch input. So obviously the next course of action was to hold down the power button for 10 seconds to force a reboot. The Motorola logo appeared and the phone vibrated... then it did nothing.
I tried this a few times and still nothing happened. I am able to boot into the bootloader, but apart from that, the phone goes only so far into the boot cycle before the screen goes black and does nothing.
Motorola's website suggests that if the Moto G becomes unresponsive, and the regular 10 second reset doesn't work, you should hold the power button for 120 seconds and keep it plugged in to a charger. This didn't work either. As of right now, my phone is just sitting here on my desk with what I would call a 'black screen of death.' Help would be appreciated.
I cannot boot into recovery, I cannot access anything. The phone is stock, unrooted, and running KitKat 4.4.2 without any modifications whatsoever. It's about 5 months old now, so it's still covered by warranty and I don't want to void it.
Click to expand...
Click to collapse
Can you boot into bootloader mode and use adb command from a pc? If yes, maybe you can try to flash a stock recovery img file via your pc to phone.
echui2014 said:
Can you boot into bootloader mode and use adb command from a pc? If yes, maybe you can try to flash a stock recovery img file via your pc to phone.
Click to expand...
Click to collapse
Would that require unlocking my boot loader though? I don't want to void my warranty, especially considering I did nothing to the phone and it's currently unresponsive.
I am not sure - but my guess is that bootloader needs to be unlocked to install custom recovery to "recover" & backup userdata before flashing the entire original stock firmware; that's usually the first step we see in all those modding guide in different forums online.
How to get into safe mode
www[dot]youtube[dot]com/watch?v=NSHzoSEx8xY
** I am unable to post outside url yet.**
I suppose you can also contact motorola support to see if they can help you recover your data before getting the phone fixed or replaced under their warranty program.
Hi Guys,
Don't you have any problem after the upgrade to the April patch?
I updated on 3rd of April (the patch level was 5th of April ), and then next day the Youtube app got frozen... then the whole device got frozen.
Nothing helped, only the long-press on the power button until the device restarted...
One day later the device was frozen on the lock screen... same thing, long-press on the power button, until the phone restarts....
Then it seemed the device was stuck was on the boot screen. It happened for more than 10 minutes, so I restarted again.
Boot done, device seems alive. Few minutes later slow screen unlock, the device only reacts on every 2nd-3rd power button press, and no reaction anymore.
Screen is black, power button long-press (more than 30 sec) does not help , putting it to the charger does nothing (the battery was on 50% when the problem happened).
I tried to press the power button for minutes, no reaction. I pressed it together with the volume buttons, nothing.
Via USB cable the ADB is not connected.
Any idea? Similar problem to anyone?
How could I make work again? (At least until I save all of my data)
(The phone was never rooted, it was on stock rom from the beginning.)
Have you tried holding volume up+power for 20 sec?
Sent from my [device_name] using XDA-Developers Legacy app
RMA the phone with google, this sounds like a faulty device to me. Did you sideload the April OTA ?
I have tried with all button combinations, no result.
The April patch was an over the air update, not sideloaded.
Is there any way to backup my data?
Or get it back from Google when I send it back?
I had my older HTC phone suffer the same fate back in India. I had installed a kernel that I had built and tweaked and hence not covered by any warranty
I was told the only way to get it back is to use a JTAG. If there is anyone with a JTAG for Snapdragon 835 series, you could get them to reset it.
My journey: https://forum.xda-developers.com/showpost.php?p=29150171&postcount=6
hackworks said:
I had my older HTC phone suffer the same fate back in India. I had installed a kernel that I had built and tweaked and hence not covered by any warranty
I was told the only way to get it back is to use a JTAG. If there is anyone with a JTAG for Snapdragon 835 series, you could get them to reset it.
My journey: https://forum.xda-developers.com/showpost.php?p=29150171&postcount=6
Click to expand...
Click to collapse
Thank you for the details, I will try to look at the gobi source and achieve something.
Meanwhile I created a new topic (https://forum.xda-developers.com/pixel-2/help/bricked-pixel-2-qusbbulk-t3776464) , because I discovered the device is visible on my old ubuntu machine as a QUSB__BULK modem.
(so I guess some part of the gobi driver hacking is not necessary, because at least the device is visible as a USB device)
First off, my google pixel is 100% stock. Last night when I went to bed, I had no issues with my phone. I woke up in the middle of the night because the screen was on and very bright. It was the white google boot screen, but with a bunch of corrupted text sporadically over it, and it was stuck there. I held down the power button to reboot, but when it did it would get to my unlock screen, but be frozen there. After about 5 seconds on that screen, it would reboot itself, and just continue that over and over. I tried holding down the volume down button to get into the bootloader, but when I go into recover mode, it just gives me the logo of the green android guy with a red triangle exclamation point on it and it says "no command" below it. So I reboot, and the only way to stop the boot cycle is to to back into the boot loader and select shutdown, so that way it will stay off.
Any words of wisdom? I was really not looking to get a new phone at this point...
I'll add that I used the instructions here to try to apply a rescue OTA using ADB according to these instructions: https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view. It completed successfully, but didn't make any improvement on the situation.
Update #2: I ended up trying to do a factory reset from recovery mode and that also doesn't seem to have helped.
Did you try installing a more recent OTA than what you originally had?
I already had the most recent OTA so I can't get a more recent one.
Try again in a few days when the February update is released. If it still doesn't work, it's possible a memory chip got fried.
If you're in the US, look up your nearest uBreakiFix location. They handle all Pixel warranties in the US. There are a number of reports in various threads of people getting their phone repaired for free, even outside of warranty.
I am in the US, but the nearest location for me is about 1.5 hours away. I guess I could give them a call to find out if it's worth the drive.
Why do you think a new OTA update would help where an old one wouldn't?
Is there any way I can flash the full image without having previously unlocked the bootloader?
Well i am experiencing the same problem on temporary basis since 2-3 days and the problem seems to be with the power button. I get it fix when i take it out of the body cover and try to clear the dust around power button and seems to fix it but it still happens in the morning or at night at home.
I've tried flashing patched boot.img file from the December update with the january rom, because patched boot.img file from january update wasn't working. The phone rebooted twice, displayed a message that the phone failed to boot and gave me options to either restart and try again or factory reset. I chose restart and the phone is since then bricked. Black screen, occasionally if i hold some buttons it flashes faintly but thats all. If i connect it to a pc, it is able to connect after holding some buttons for 2-3 seconds as a COM device, but then it disconnects again.
Also apparently i forgot that p7p was different and did the whole thing with boot.img instead of init_boot.img.
iplux said:
I've tried flashing patched boot.img file from the December update with the january rom, because patched boot.img file from january update wasn't working. The phone rebooted twice, displayed a message that the phone failed to boot and gave me options to either restart and try again or factory reset. I chose restart and the phone is since then bricked. Black screen, occasionally if i hold some buttons it flashes faintly but thats all. If i connect it to a pc, it is able to connect after holding some buttons for 2-3 seconds as a COM device, but then it disconnects again.
Also apparently i forgot that p7p was different and did the whole thing with boot.img instead of init_boot.img.
Click to expand...
Click to collapse
Is it out of battery?
mackdacre said:
Is it out of battery?
Click to expand...
Click to collapse
sadly no, around 60-80% maybe
hello have you tried pixel flasher?
jejemc said:
hello have you tried pixel flasher?
Click to expand...
Click to collapse
i will try now, but i dont think it'll work since the pc doesn't recognize the phone. i can make the phone somehow connect to the pc for 2 secs, but it connects as COM device and instantly disconnects after that.
Edit: it did not work
and holding the power button and volume up or down for a while does nothing?
jejemc said:
and holding the power button and volume up or down for a while does nothing?
Click to expand...
Click to collapse
correct. power + vol up, power + vol down, all 3 buttons pressed at the same time - nothing, all nothing. I'm able to make the screen for a brief second if i connect the phone to charge and press all 3 buttons or volume down + power, but that's all.
iplux said:
correct. power + vol up, power + vol down, all 3 buttons pressed at the same time - nothing, all nothing. I'm able to make the screen for a brief second if i connect the phone to charge and press all 3 buttons or volume down + power, but that's all.
Click to expand...
Click to collapse
alas it means sending it sav I don't see what else to do.
jejemc said:
alas it means sending it sav I don't see what else to do.
Click to expand...
Click to collapse
small update, i just noticed that the phone is slightly warm, so its definitely on and doing something in the background with the screen completely off. I will give it a night to completely discharge and see if i can get it to show literally anything on the screen. If not, i gotta think of a way to ship it to the UK so it can get fixed, because i'm in a non supported region sadly.
Have you tried holding down the power button for 15 seconds?
febo17 said:
Have you tried holding down the power button for 15 seconds?
Click to expand...
Click to collapse
yup, sometimes that makes the screen flash for a split second and then nothing. tried pretty much any combination for up to 30 secs. sometimes its a single screen flash, sometimes it flashes twice. It's barely visible.
iplux said:
yup, sometimes that makes the screen flash for a split second and then nothing. tried pretty much any combination for up to 30 secs. sometimes its a single screen flash, sometimes it flashes twice. It's barely visible.
Click to expand...
Click to collapse
Just to see if I understand better, so the phone is on but the screen doesn't work as it should?
Try it even longer than 30 seconds (up to maybe 60 seconds) , I also had some problem with my P7P stuck and needed to push it really long
febo17 said:
Just to see if I understand better, so the phone is on but the screen doesn't work as it should?
Click to expand...
Click to collapse
i was on december android update with magisk installed. i tried today to install january update today - i patched the boot.img file (yes, i know it should've been init_boot.img), replaced the original boot file with the patched one on my pc and flashed the new january rom with "-w" parameter removed. That however didn't work (obvious reasons), i had no root. I then decided that the new boot.img file from the january update might have some issues , and decided to flash the january update with replaced boot.img patched from december update (again with -w parameter removed). The phone took it all, then the google logo popped up... after a few seconds it restarted and the google logo popped up again... it once again didnt boot, and restarted, but after the 3rd restart i was greeted with a message from the bootloader (i assume) that the system failed to load twice, and i was presented with 2 options - "restart and try again" or "factory reset the system". I chose restart, and the screen went black and that was all. (it was only after all of this happened when i realized that everything happened because i was patching the boot.img instead of init_boot.img).
Now the screen is black, no matter which button combination i am trying. Sometimes the screen flashes once or twice when i hold some buttons, but that aside- nothing. I assume the phone is still doing something in the background, because if i leave it on my bed sheets and touch it after awhile, the back is a bit warm, so obviously something is working, but im certain its not the OS.
iplux said:
i was on december android update with magisk installed. i tried today to install january update today - i patched the boot.img file (yes, i know it should've been init_boot.img), replaced the original boot file with the patched one on my pc and flashed the new january rom with "-w" parameter removed. That however didn't work (obvious reasons), i had no root. I then decided that the new boot.img file from the january update might have some issues , and decided to flash the january update with replaced boot.img patched from december update (again with -w parameter removed). The phone took it all, then the google logo popped up... after a few seconds it restarted and the google logo popped up again... it once again didnt boot, and restarted, but after the 3rd restart i was greeted with a message from the bootloader (i assume) that the system failed to load twice, and i was presented with 2 options - "restart and try again" or "factory reset the system". I chose restart, and the screen went black and that was all. (it was only after all of this happened when i realized that everything happened because i was patching the boot.img instead of init_boot.img).
Now the screen is black, no matter which button combination i am trying. Sometimes the screen flashes once or twice when i hold some buttons, but that aside- nothing. I assume the phone is still doing something in the background, because if i leave it on my bed sheets and touch it after awhile, the back is a bit warm, so obviously something is working, but im certain its not the OS.
Click to expand...
Click to collapse
I hope you solve it, good luck and stay tuned
Since this is a very new device, I suggest contacting Google for warranty repair, because that will be much easier than trying to diagnose what works and what doesn't, as well as trying to recover the device. You have a warranty; use it.
oko17 said:
Try it even longer than 30 seconds (up to maybe 60 seconds) , I also had some problem with my P7P stuck and needed to push it really long
Click to expand...
Click to collapse
just tried:
pwr
pwr + vol up
pwr + vol down
pwr + vol up + vol down
each for more than a minute, no response.
V0latyle said:
Since this is a very new device, I suggest contacting Google for warranty repair, because that will be much easier than trying to diagnose what works and what doesn't, as well as trying to recover the device. You have a warranty; use it.
Click to expand...
Click to collapse
I most likely will, i just don't want to because im in Bulgaria (a country where they dont sell the phone) which means i have to find a way to send the phone to the UK, and they will probably refuse to ship it back.
iplux said:
I most likely will, i just don't want to because im in Bulgaria (a country where they dont sell the phone) which means i have to find a way to send the phone to the UK, and they will probably refuse to ship it back.
Click to expand...
Click to collapse
Ah. Well...without the screen working, there isn't much you can do, beyond seek repair in your own country. If the screen isn't working, it's usually due to either of 2 reasons, both of which require specialty repair:
The screen and/or display controller are defective and must be replaced
The bootloader is corrupted and the mainboard must be replaced
The tools required to rescue a device with a corrupted bootloader are not publicly available, unfortunately.
This is kinda crazy....
this is probably the first time/instance I've seen where tripping up the init_boot partition (with the boot.img used instead) caused this bad of a problem! Since the Pixel 7's changed things to init_boot, there have been very many people that have gotten tripped up flashing the boot.img to it, but it usually just results as a bootloop and a simple reflashing of the stock init_boot properly fixes things!
Are you sure you tried completely draining the battery? A hard reset can sometimes do wonders...
If Google doesn't "play ball", I'm sure you could find some 3rd party repair company/shop that would -- of course this will also cost money though...
Hopefully it works out for you OP!