Database Develop

[Q] [Help!] AT&T Galaxy Tab Black Screen Of Death

I have the SGH-i987 AT&T Galaxy Tab and while flashing it I recently got the black line in the middle problem. Considering the searches turned up a fix for that I followed the steps I could find (and using Odin) and was able to get it booting into the setup, after which I couldn't go any further because any attempt to get keyboard input caused it to crash and reboot. I've searched high and low for a way to get this thing back to stock and can't find a single source here or anywhere else on the web that is helpful. I'm hoping that someone here can help get me pointed in the right direction, because right now I have a useless device that does nothing but show me the battery is charged.
So you know: I've searched XDA and found nothing that applies to the AT&T model of the Galaxy Tab. The Verizon fix doesn't work and the T-Mo thread contains a dead link to the file I'd need. I've tried searching SamFirmware and it's been a completely useless experience-- whether that's due to poor layout and navigation or my being unfamiliar with how they keep any actual ROMs is beyond me, because the site just takes me in circles. Searching here hasn't gotten me anywhere either, since most point me to the Verizon thread (though one person has tried suggesting the T-Mo fix, but again dead links). I'm getting really let down, since I love how incredibly helpful and informative XDA usually is and this is one of those cases where I'm just spinning in circles trying to find an answer because I know the discouragement toward just showing up and screaming "Help!"
But I got nothin. I've done the searches. I've read plenty. I've searched the web (including this). I've been to the site that lots have claimed would have the file I was looking for. Nada.

Found this by searching in XDA under your device model, hope it helps
UPDATE: As rangercaptain notes, there's a simple fix (which I failed to find the first round) for the white line black screen brick (or whatever you want to call it.) For anyone else, this may still hold value for how to convert your AT&T Tab to a P1000 Euro version with phone functionality or if you need to otherwise recover/restore a rooted AT&T Tab that's not booting.
I bricked my SGH-I987 (don't ask how). It was an already rooted and unlocked Galaxy Tab I bought crippled (of course) from AT&T sans contract. It was bricked. I couldn't get to the bootloader but I could hear the Samsung startup sound and then I got a blank screen with a faint line through it.
Anyhow, here's what I did to recover it.
Install USB drivers (if not already installed, else skip. The files I eventually found were called usb_drivers_GalaxyS_x64.zip but work perfectly on my Win 7 Ult x64 system.)
Turn off Tab
Hold the [Volume Down] + [Power On] buttons until the Digging Android screen appears
Connect your Tab
Run Odin (as an Administrator if you're on Vista/7). If the phone is connected, you'll see COM with a value and color highlight (not blank and white). (I used Odin3 v1.7.exe)
In Odin, load the following files (which I downloaded from samfirmware.com - the download will be password protected with the password "samfirmware.com"):
PIT => P1000XWJJ4\P1_add_hidden.pit
PDA => P1000XWJJ4\P1000XWJJ4-REV03-ALL-CL639474.tar.md5
PHONE => P1000XWJJ4\MODEM_P1000XXJID.tar.md5
CSC => P1000XWJJ4\GT-P1000-CSC-SERJJ2.tar.md5
Make sure "Re-Partition" is checked
If all's set, click Start and Odin will do it's thing. The Tab will reboot a few times and I was done and "unbricked".

I've already tried that. I've tried using instructions that used Odin. I've tried instructions that used Heimdall. I've even downloaded and used this jar executable called soft unbrick or something like that.
This is driving me crazy. Nothing seems to work. In fact, the last thing I tried (which were instructions similar to yours) got rid of the white line but have left me with a plain black screen with the buttons lit on the bottom and nothing else. The only thing I can still do is get it into download mode.

sorry to hear that if i come across anything will post,

basia314, thanks for the attempt to help, but as soon as I did a google search on it I found the XDA thread in question, and it's one I've already found before. If you read the rest of the thread in question (here) you'll see that it doesn't work.
Currently XDA contains no thread with info on how to fix my problem. I've searched. Google has provided no links either. The closest I came to finding a solution is the suggestion that I let some guys fix it for $50.

GreNME said:
I've already tried that. I've tried using instructions that used Odin. I've tried instructions that used Heimdall. I've even downloaded and used this jar executable called soft unbrick or something like that.
This is driving me crazy. Nothing seems to work. In fact, the last thing I tried (which were instructions similar to yours) got rid of the white line but have left me with a plain black screen with the buttons lit on the bottom and nothing else. The only thing I can still do is get it into download mode.
Click to expand...
Click to collapse
You say you have tried that but your first post states that you did not find anything .... which one is it?
There is a stock AT&T rom here on XDA, where did you get the one you tried?
Can you get into Recovery? In the thread listed above one of the posts states that there is no boot image and a black Recovery screen that is functional. Maybe what you flashed is giving you these same results, have you tried waiting a bit longer after a flash to see if it will actually do anything, the first boot after a flash takes a little longer. Are you checking the re-partition box during the flash, the file linked in the other thread should be flashed with the re-partition box UN-checked.
Just trying to brain storm here, hoping you fix it.

Well, it's a moot point now.
After following the instructions here to fix a "soft brick" I've now gone to hard brick. Can't power it up at all and can't get it to download mode.
When I said I couldn't find anything here I mean I couldn't find anything that helped. I can find tons of threads, usually pointing to either dead links or saying "go to samfirmware" (which I do, and still find no helpful info). I've tried close to a dozen different things to try to get my Tab back, all things either found here on XDA or linked to in threads here at XDA. Not a single one worked. And now I have a Tab that is as bricked as can be.
Of course, I've found threads here that claim a Tab can't be totally bricked as well. Maybe their Tab can't be, or maybe they're keen on tearing the thing apart to fix whatever breaks, but I don't have the tools here to do that. For me, my Tab is as useful as a brick right now, and has been for a month of trying to get it back to normal.
For reference:
[x] I am following instructions as completely as they're given
[x] I read as much as I could find reference to for things I wasn't sure of ahead of time.
[x] I googled.
[x] In Odin I checked the repartition box when instructed to do so, and made sure it was unchecked when instructed so.
[x] I made sure every time that the device was recognized in Odin in Heimdal
But...
[x] Yes I was foolish to have not made a backup.
This is killing me, and I don't have the $50 USD to get someone to fix my Tab for me as claimed in this thread. So I'm stuck with a Tab that's bricked.

Still nothing
Interestingly, I could get Odin to see my device, but trying that stock ROM still failed. I have no way of knowing if I had it successfully in download mode because the screen is doing nothing. Completely black, no lights.
Any thoughts?

GreNME said:
Interestingly, I could get Odin to see my device, but trying that stock ROM still failed. I have no way of knowing if I had it successfully in download mode because the screen is doing nothing. Completely black, no lights.
Any thoughts?
Click to expand...
Click to collapse
So it's not completely bricked?
Just a question, but from the thread started by k0sh about unbricking, did you try and just leave your tab plugged into a WALL charger for a few hours.
I would attempt at restocking with the OVERCOME stock safe, following their instructions to the tit.
---------- Post added at 04:50 PM ---------- Previous post was at 04:46 PM ----------
It does sound like you are experiencing the same black screen that I mentioned from the other post.
If you haven't done so yet, do try the re-stock instructions from the OVERCOME thread using their stock safe.

It spends most of its time connected to a wall charger.
I'm guessing it's not completely bricked, but it's non-functional to me since I can get zero screen feedback. This means I can't tell when it's in download mode or not.
What's "the OVERCOME stock safe", for reference? I ask because I've followed the instructions on several threads already, and the problem has gotten progressively worse. Also, I've followed instructions 'to the tit' as much as I'm capable so far, so it's not like I'd be doing any different with some new set of instructions. I don't like trying to take shortcuts, though I have to admit that I've had to try to research the meanings of other references made before (i.e. - I have no clue what "OVERCOME stock safe" is, though I assume it's a ROM that I'll have to follow three somewhat-related links to in order to get to the megaupload site to get it).

Addendum to above...
I didn't mean to come off as flippant, though I am a bit on the frustrated side considering every set of instructions I've been able to find to fix my Tab has resulted in it being worse than before the fix.
I'm trying to search for the instructions you reference, but not finding any detailed instructions anywhere. All I find is "flash OVERCOME using Odin" or something similar. As I said I have a completely black screen, so I have no indicator of whether I've got the thing in Download mode. Yes, I found out that it's not completely dead by using Odin to detect a COM connection, but that's not necessarily a guarantee that I have it in Download mode, is it?

GreNME said:
I didn't mean to come off as flippant, though I am a bit on the frustrated side considering every set of instructions I've been able to find to fix my Tab has resulted in it being worse than before the fix.
I'm trying to search for the instructions you reference, but not finding any detailed instructions anywhere. All I find is "flash OVERCOME using Odin" or something similar. As I said I have a completely black screen, so I have no indicator of whether I've got the thing in Download mode. Yes, I found out that it's not completely dead by using Odin to detect a COM connection, but that's not necessarily a guarantee that I have it in Download mode, is it?
Click to expand...
Click to collapse
alterbridge86 has a very well known thread in the Development section (Don't follow the links just yet) that has been around for a while, the OVERCOME team has provided us with many very stable and fast ROMS. To do a nice fresh install of their ROM they recommend doing a flash of a stock firmware to clear all the bits and bytes. If you follow the thread you will notice a detailed (and I mean detailed) instruction setup which is linked below.
Now, I'm not saying that you are not a smart person or anything so don't take any of the following as an insult, I just want to help so don't mind the simple instructions.
If I were you, after downloading all the files that you need for the stock safe stuff, to make sure you are properly in download mode when necessary do the following;
1) start the ODIN software on your computer.
2) connect your tab to the computer, check to see if odin connects
3) If odin connects than your tab is obviously ON, with the tab still connected to the computer press and hold the power button until the tab shuts off, at that point ODIN will disconnect.
4) press and hold the volume down button, then press the power button for a sec or two (the standard way to get into DL mode) and very shortly after you should get ODIN showing that it is connected again.
This will probably indicate that your tab has some functionality that you might be able to work with, but it wont be easy. After flashing anything you should wait a while as everything you flash will require a long first boot. Especially when you can't see any prompts. After flashing the kernel the install guide says you should hear a "sexy robot" voice (STEP 9). The flash will be quick but when the device reboots if you are not hearing the voice DON'T TOUCH ANYTHING, alot is happening in the background give it a good 5 minutes for it to finish (even 10 for safety), it should boot into the stock OS. If you don't see anything reboot your tab by holding the power button for 5-10 seconds to shut it off then turn it back on. BUT WHATEVER YOU DO, WAIT AT LEAST THOSE 5 MINUTES after flashing the kernel because it converts your system from RFS to ext4.
The OVERCOME rom thread is located here
The INSTALL GUIDE is located here
Good luck.

I'm about halfway through the process, and I've already got the screen working again.
I took the initiative to search around on the search string you gave me ("Overcome Stock Stable") and came across the same page you link to above. I was actually just about to post it here for future reference if anyone ever found themselves in my position again.
I'm trying to consider whether to leave it at stock or to flash the Overcome ROM on it. Your thoughts?
(and many, many, many thanks!)

GreNME said:
I'm about halfway through the process, and I've already got the screen working again.
I took the initiative to search around on the search string you gave me ("Overcome Stock Stable") and came across the same page you link to above. I was actually just about to post it here for future reference if anyone ever found themselves in my position again.
I'm trying to consider whether to leave it at stock or to flash the Overcome ROM on it. Your thoughts?
(and many, many, many thanks!)
Click to expand...
Click to collapse
I'm very glad to hear that you got it working, I've got two tabs and half bricked both of them at one point or another. And I find it's actually not that easy to completely screw these things up, they just get frustrating trying to fix.
Anyway, you should definitely try the OVERCOME series of ROMs, they are really good. Lot's of small things that make it worth while as well as big improvements over stock (speed, battery etc.. etc..) I'm running BOCA on mine, had the Honeycomb RC1 on it for a few weeks and now am waiting for these wonderful devs to cook up a usable ICS ROM>
Enjoy

Go to: teamovercome.net and read. Their install instructions are some of the best I've read. These guys are really good.

Sorry I didn't see the second page, that you had gotten the answer already

[Q] Xperia phone dropped in water, ideas to recover data?

Hi everyone.
A few days ago a non tech-literate friend of mine told me that he had dropped his phone in the sink (clean, cold water, about three weeks ago). He had since bought another rolleyes: shame to not even try to repair it!) but had precious data on it. I agreed to try and recover it from him as he's quite a good friend. Since I only got the phone long after the incident, it is as far as I can know perfectly dry. I have never had any dealings with Sony before (phone-wise)... I think the data should be attainable, I just don't have the knowledge yet.
Symptoms :
When plugged off, the phone just sits there with really nothing happening.
When plugged on to a power cord (France), there's a softly blinking red light on the left of the top front speaker.
When plugged to a computer, the same soft red light is flashing. (I therefore imagine it indicates charging)
What I have tried :
Holding the power button
Unplugged, for 2, 3, 5, 10, 20, 30 seconds, to no avail
Plugged, and it vibrates shortly after about 6-8 seconds or 2-3 seconds (am I turning it on and off/long press to get the power menu?)
Connecting it to a computer (Windows 7 and Arch linux):
On Arch, there's nothing. No disk/drive of any kind is detected (/dev stays unchanged...)
On windows, the first time I connected I got the pop up indicating a driver install for an "unknown device", and the install failed. Browsing this forum I learned about PC companion, which I installed. Windows then successfully installed a driver for "usb device". Windows explorer does not detect the phone as a media device of any kind and PC companion refuses to connect to the phone : when manually prompted to connect, it recognizes something is plugged, but tells me it "fails(ed) to connect to the pone/tablet. Please refer to the guide", guide of course which is worthless. (No logs or smthng? geez, windows!)
What I have not tried :
I have *no* idea on how to remove cover to access battery and so on. As the back is perfectly smooth I am afraid to break smthng if I try with a knife blade or so...
Sacrificing chicken and/or blond virgins to the blood overlords while chanting black magic
My guess is the screen is dead ( as it shows no sign whatsoever) but the phone seems to be partly working. 1337 guyz out there, ideas, help? (actually anyone is welcome of course :laugh
The main objective is only to recover data, not get it back working (would've sent it for repair otherwise!) If you need more info, I'll be happy to provide it.
G'day to yall!
(As I am currently undergoing heavy fire from my engineering study teachers, I will check this post about once a week. sorry for the answering delays...)

Phenitei said:
Hi everyone.
A few days ago a non tech-literate friend of mine told me that he had dropped his phone in the sink (clean, cold water, about three weeks ago). He had since bought another rolleyes: shame to not even try to repair it!) but had precious data on it. I agreed to try and recover it from him as he's quite a good friend. Since I only got the phone long after the incident, it is as far as I can know perfectly dry. I have never had any dealings with Sony before (phone-wise)... I think the data should be attainable, I just don't have the knowledge yet.
Symptoms :
When plugged off, the phone just sits there with really nothing happening.
When plugged on to a power cord (France), there's a softly blinking red light on the left of the top front speaker.
When plugged to a computer, the same soft red light is flashing. (I therefore imagine it indicates charging)
What I have tried :
Holding the power button
Unplugged, for 2, 3, 5, 10, 20, 30 seconds, to no avail
Plugged, and it vibrates shortly after about 6-8 seconds or 2-3 seconds (am I turning it on and off/long press to get the power menu?)
Connecting it to a computer (Windows 7 and Arch linux):
On Arch, there's nothing. No disk/drive of any kind is detected (/dev stays unchanged...)
On windows, the first time I connected I got the pop up indicating a driver install for an "unknown device", and the install failed. Browsing this forum I learned about PC companion, which I installed. Windows then successfully installed a driver for "usb device". Windows explorer does not detect the phone as a media device of any kind and PC companion refuses to connect to the phone : when manually prompted to connect, it recognizes something is plugged, but tells me it "fails(ed) to connect to the pone/tablet. Please refer to the guide", guide of course which is worthless. (No logs or smthng? geez, windows!)
What I have not tried :
I have *no* idea on how to remove cover to access battery and so on. As the back is perfectly smooth I am afraid to break smthng if I try with a knife blade or so...
Sacrificing chicken and/or blond virgins to the blood overlords while chanting black magic
My guess is the screen is dead ( as it shows no sign whatsoever) but the phone seems to be partly working. 1337 guyz out there, ideas, help? (actually anyone is welcome of course :laugh
The main objective is only to recover data, not get it back working (would've sent it for repair otherwise!) If you need more info, I'll be happy to provide it.
G'day to yall!
(As I am currently undergoing heavy fire from my engineering study teachers, I will check this post about once a week. sorry for the answering delays...)
Click to expand...
Click to collapse
Not realla an idea, but maybe a little help. In the attachement you find a pdf. (Working Instructions for Assembly and Disassembly the phone). Hope, it helps a little. Good luck :fingers-crossed:

Thanks mate! Will look at it this weekend

One of the first thing you should try is to access fastboot. For this you have to hold volume down button while plugging it in to the computer. If the phone is a Xperia SP your led should be blue then (I'm not sure you have this model regarding the description you gave). If this works then we make a small step !

Right I'll try that. Looking at the pdf given by reinipic, it seems it is one, as the phone corresponds to the photo of the Sp C5303/5302/5306/M35h.
Oops my bad!! You are, good sir, perfectly right, the phone is not an SP, as all Sps seem to have the front Camera as well as three sensors on the left of the top speaker. The model I'm working on only has a camera on the right side. ...
Erm as such I'm quite into the wild as to how to guess what model it is (google image is not really being helpfull...), any tips on that?
attached are front, back, and side photographs of the phone.
I have as well tried to long press the down button while connected to a computer (windows 7). The led changed it's pattern : it blinked shortly red twice,then green! :good: The screen still stays off though (which may confirm my hypothesis that it's dead), and the computer does not react.
As always, thx for the help!

Phenitei said:
Right I'll try that. Looking at the pdf given by reinipic, it seems it is one, as the phone corresponds to the photo of the Sp C5303/5302/5306/M35h.
Oops my bad!! You are, good sir, perfectly right, the phone is not an SP, as all Sps seem to have the front Camera as well as three sensors on the left of the top speaker. The model I'm working on only has a camera on the right side. ...
Erm as such I'm quite into the wild as to how to guess what model it is (google image is not really being helpfull...), any tips on that?
attached are front, back, and side photographs of the phone.
I have as well tried to long press the down button while connected to a computer (windows 7). The led changed it's pattern : it blinked shortly red twice,then green! :good: The screen still stays off though (which may confirm my hypothesis that it's dead), and the computer does not react.
As always, thx for the help!
Click to expand...
Click to collapse
:highfive: Bravo man! As pecOra said, you hae done a grat step - the phone is alive! LED blinking red then green, means, that´s ready for flashing a rom with Flashtool! The problem now is to clarify, what Xperia-model it is, after this you can seach in the right thread for a Rom to flash it on the phone with Flashtool

Cool! This has me ask two questions though :
- wouldn't flashing a ROM erase the data I'm trying to retrieve? As it's not on the sd card (whose slot is on the outside, and empty).
- I'm afraid I'm slow here, but how would flashing a ROM help retrieve the data, as the main obstacle is that the data on the internal sd card is not readable

[UPDATE] : if, while connected to a computer, the up-volume button is long pressed, then the del becomes a stable and unchanging blue!

Phenitei said:
Cool! This has me ask two questions though :
- wouldn't flashing a ROM erase the data I'm trying to retrieve? As it's not on the sd card (whose slot is on the outside, and empty).
- I'm afraid I'm slow here, but how would flashing a ROM help retrieve the data, as the main obstacle is that the data on the internal sd card is not readable
Click to expand...
Click to collapse
STOP! Flashing a Rom ALWAYS deletes all data on the internal SD. In the current situation you can make again a functional phone. To readout the data from the SD is an other thing. For this experiment I am to less competent. Maybe another member is smarter than I am, sorry.

No probs! That's also my experience with my phone (wiping I mean), and is why I asked why I would want to flash a ROM. No worries, we all have different skills[emoji41] . I'll help you the day you mess up a samsung [emoji6]
Thx for trying!

Phenitei said:
No probs! That's also my experience with my phone, and is why I asked why I would want to do that. No worries, we all have different skills. I'll help you the day you mess up a samsung
Thx for trying!
Click to expand...
Click to collapse
:good: hope, pecOra can help you!!! He is a great man.

Ok that's good news, it means your phone isn't totally dead. The next step is to look if there is any way to access the data partition or sd from fastboot mode (when the blue led was on, it's generally used to access kernel/recovery partitions from the computer.) I'll make some search today and look in fastboot manual to see if I find something. You should try to find something too.
If there is no way with fastboot we'll try with adb but unless your friend was some kind of developer he probably kept it deactivated.
The phone looks more like a Xperia Z or a Xperia Z1 I think. Our xsp has a big led at the bottom.
Edit :
I found another thread with a similar problem. The solution is to flash a recovery and access adb from the recovery.
forum.xda-developers.com/galaxy-nexus/help/to-recover-data-fastboot-t1871698
The problem is that I'm pretty sure the phone must have an unlocked bootloader.
Is the phone rooted?

pec0ra said:
Ok that's good news, it means your phone isn't totally dead. The next step is to look if there is any way to access the data partition or sd from fastboot mode (when the blue led was on, it's generally used to access kernel/recovery partitions from the computer.) I'll make some search today and look in fastboot manual to see if I find something. You should try to find something too.
If there is no way with fastboot we'll try with adb but unless your friend was some kind of developer he probably kept it deactivated.
The phone looks more like a Xperia Z or a Xperia Z1 I think. Our xsp has a big led at the bottom.
Edit :
I found another thread with a similar problem. The solution is to flash a recovery and access adb from the recovery.
forum.xda-developers.com/galaxy-nexus/help/to-recover-data-fastboot-t1871698
The problem is that I'm pretty sure the phone must have an unlocked bootloader.
Is the phone rooted?
Click to expand...
Click to collapse
:good: +1

Right. I'll look into fastboot and confirm the phone model this we, and will look at the thread you dug out tomorrow (gitta get some maths and physics done first ). (Great job finding the thread by the way! I hadn't seen that one)
I'm certain the phone os neither rooted nor was usb debugging enabled, as my friend is absolutely not into tech.
As always, your help is much appreciated, thank you.

Phenitei said:
Right. I'll look into fastboot and confirm the phone model this we, and will look at the thread you dug out tomorrow (gitta get some maths and physics done first ). (Great job finding the thread by the way! I hadn't seen that one)
I'm certain the phone os neither rooted nor was usb debugging enabled, as my friend is absolutely not into tech.
As always, your help is much appreciated, thank you.
Click to expand...
Click to collapse
Mmmh this is not good. The solutions use adb so you must have it enabled but that's not really a problem because if your phone boots until adb mode, it will probably boot until usb storage mode too. So if you don't have usb storage when booting, you probably won't have adb mode either.
The second solution was to use adb (or usb storage) in another environment which is much less complex and easier to flash without losing any data : the recovery. The problem is that you can only flash a recovery with fastboot when your bootloader is unlocked. The other ways to flash it use adb and as we've seen we don't have it.
I'm pretty sure you can't access any partition from fastboot if your bootloader is unlocked because otherwise it would open easy exploits to gain root without losing your warranty unlocking your BL.
Now what you still have available is flashtool. This is the (copy of the, with more possibilities) official way to flash firmwares. You use it from your computer when your phone is in the mode with the green light. The problem is that with this you can only flash official firmwares. They might still repair your phone depending on the problem but you must be careful not to erase the data. If you want to try this I can help you in the procedure (you can even pm me en français if you want)
By the way, are you trying to access data like app data/ contacts / messages or data of the external storage?

I personally agree the solution of pec0ra to flash a stockrom with the flashtool, without erasing date. It should be the only successful procedure. Good luck man!
---------- Post added at 01:07 PM ---------- Previous post was at 12:40 PM ----------
reinipic said:
I personally agree the solution of pec0ra to flash a stockrom with the flashtool, without erasing date. It should be the only successful procedure. Good luck man!
Click to expand...
Click to collapse
Edit:
btw. when you are opening the flashtool and connect the phone with the pc, than you can see in the flashtool, which Xperia Model it really is, then you can search for the right stockrom and ... buuuuuum :laugh:

Right thanks a lot! I'll take the time to document my self a bit on all that and then I'll be happy to accept your proposal. Merci!

put it in a box of rice 4 days without touching.... you will see the results.

Kmiloxdxd, thanks for your proposal, I'll try! But as I said in the question, I got the phone at least a week after it fell into water, maybe more (up to 3 max) As such, I'm quite sure it's too late for that kind if trick... (which did save a few phones and watches of my own ^^)

You have 2 options..the first one is to reflash stock rom via flashtool without wiping data and the other one which requires a recovery, you can move this zip (http://forum.xda-developers.com/showthread.php?t=1646108) to your sd and move files from internal to external memory.

Is there any hope? (hard bricked...)

Hello Moto,
So I got my Moto G5s Plus awhile back when it was still new and I tried to root it right off (I know...it was stupid, I realize I should've waited a little until the stock firmware was released and more guides were made), and basically I ended up hard bricking my device.
There are no lights, the screen is completely blank, and the power button does absolutely nothing.
I have heard of a way to revive it from level 0, however, and I was on the path to doing that until I realized that-for some reason-my laptop does not recognize my dead phone at all. In the guide (which I've long since lost the link to..) it said that my phone would appear in my device manager (>start>right click on Computer>manage) under the android tab after installing a bunch of ADB drivers and such, as "ADB-somethingsomething". No such thing happened; I couldn't even find the tab it was referencing. Even after uninstalling and reinstalling the drivers that it mentioned, I couldn't seem to get my laptop to recognize my phone.
Interestingly enough, or perhaps not, I plugged it into my brother's laptop and it recognized it just fine (note, he had the drivers already installed and has meddled quite a bit already in this area).
Anyway, so now I have a pretty much mint condition hardware Moto G5s Plus, and I kind of don't want to spent money on another phone unless I know for sure that I can't fix this one. Is there any way to revive it from the dead?
P.S. I've found the stock ROM for the phone...but there's several different packages. (like..NPS26.116-26; NPS26.116-45; NPSS26.116-45-5; etc...) This my be a very stupid question..but how should I know which one is the one I need to download?
Any and all advice/help would be appreciated.
Thank you
[SOLVED]
So I managed to get it working without using a virtual machine.
To address the first problem, my phone wasn't even charged. To solve this I took a rubber band and tied it around the power and volume down buttons and attached it to a wall outlet for about an hour. (The little white light was flashing to signal that it was receiving power...which was more than I had accomplished than..ever..really...)
The second problem was my computer. I still don't know why it worked out like this, but essentially my computer never recognized my phone as the HS-USB or anything. Instead, my computer recognized it as Motorola ADB Interface (even though it was technically off and hard bricked..). This made recovering it easy, as I simply could fastboot flash the correct stock rom to my phone and go from there.
After trying a few different stock ROMs, I finally got the right one, and could boot into bootloader. And thus, finally, I was able to install TWRP, the OS back, Xposed, and Magisk.
I've used my phone for a bit now and no problems have come up. Installing Xposed did take a bit longer than I thought it would, but other than that I got me phone back.

My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help

jaura.mohit said:
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
Click to expand...
Click to collapse
Are they charging u for the motherboard Change

Yes 18000 rupees
---------- Post added at 06:55 AM ---------- Previous post was at 06:29 AM ----------
yograjfire18 said:
Are they charging u for the motherboard Change
Click to expand...
Click to collapse
18000 rupees hel p me to recover my phone

Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??

____Mdd said:
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
Click to expand...
Click to collapse
Yea, no, this is 100% software damage. Like I said, I have a mint condition (hardware wise) phone. I'm pretty sure what I did to mess it up was overwrite the data files for the previous OS. I remember trying to get it back to stock ROM, but having a crap ton of trouble finding it...and then pretty much doing a fight or flight thing and trying a stupid and edgy alternative. (I also remember, even while the phone was still working, it only booted into TWRP once or twice, otherwise it would always come up with an error)
I feel like all I need to do is flash the stock ROM to the device...but without my laptop even recognizing it, I don't know how. Essentially, the question being, is there a way to flash the stock ROM to my device without TWRP, without bootloader, without using the device at all (just my laptop); and if there is...does anyone know how?
Pressing the power and volume buttons did nada.
[edit]
I did some searching and I actually found the two links that I used while trying to recover my phone from the dead.
http://www.aryk.tech/2017/09/moto-g5s-plus-unbrick-solutions.html
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
The difference for me is that I never got my laptop to recognize it as any of the "HS-USB Bulk, HS-USB QDLoad 9008, QHS-USB DLoad 9008"; that's where I stopped in the steps.
I'll be trying to follow the steps in the first link again, but this time through virtualbox (make sure there's no conflicting drivers and whatnot). I'll post back with results whenever I get around to it.

flash -61

**Help needed with no charge and the lacklustre help not given via MAZE(Alpha 4gig)**

Hi guys, been a bit out of the loop (hospital) but bought an Alpha around sep last year...within 2 months i used a official Maze update (OTA) and it then no longer charges...got onto them via facebook (as there were no official threads for this phone back then) and they sent me this to reflash it...
http://www.mazemobile.com/download-center
The ROM used to be there, but they have the ****ing cheek to say "people tried to flash and blamed MAZE" now it was MAZE's update in the first place that buggered my phone.:silly:..i still have the original ROM...
https://drive.google.com/drive/folders/0B8XLZxEJR8albndMcXJhWGtlVDQ
^not sure if that works for you, but basically it was..
:A really crap tutorial
:Maze Alpha flash tool.zip
:Maze_Alpha_V05_20170816
I've followed everything by the letter to no avail???
Now MAZE are bloody useless, can i count on one of you clever chaps to help me out?
P.s it's the 4 gig model.
Many thanks lads...

Any joy?
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.

seedaripper said:
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
Click to expand...
Click to collapse
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)

Cheers...someone lives!
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
lukesan said:
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Click to expand...
Click to collapse

seedaripper said:
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
Click to expand...
Click to collapse
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
Charger you can easily check if you just connect it to another charger or a pc usb port. A PC usb port will only deliver (mostly) max 400mA to 500mA .. meaning it will charge, if it still does, extremely slow. So I would keep it connected to a pc all day long or night before trying to switch it on. Trying to switch it on during charging and batt at low level will probably not work. You could try to power on after 2 or 3 hours or so and if it powers on then I would power it off again to get at least some juice in it to play around.
Cable, I would go fetch another one, they will come in handy in the future too. If it doesn't fit properly because the port is to deep in the Alpha then just take a knife and carefully cut a very small piece of the plastic, just 1mm is enough. I've done this on the 2 extra cables I have here and it works perfectly and I don't even see it aesthetically so no harm done on mine.
Now if that still doesn't work we can try the next step. But be very careful to know that that will delete all data, pictures, etc off of the phone. Because of all my toying with this phone I stuck an sd-card in it and doing a backup before I play with it again.
The manual states that you have to press the volume up button.. Well you can already test that without hurting anything as long you don't press anything on the flashtool. So only volume up and then insert the usb cable to a pc. Now the mistake I made in the beginning was to also push the power button.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
Btw I know about their attitude. Well, as a Chinese company they must understand that by this attitude they will not going to sell any products anymore. I only bought mine because it was a special deal and I wanted to test an MTK chipset. They never replied to me why there is no real fast charge on it etc.
I also very very highly recommend you to invest, well for the price of a sandwich, to buy a usb charging doctor which will allow you to see the voltage and current. You don't need to be a doctor to us it and at least you see something instead of having to guess. Also while you are at it buy good quality chargers and a couple of cables. They will always come in handy and take some of the guesswork away if needed.

Top lad.
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
lukesan said:
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
.
Click to expand...
Click to collapse

seedaripper said:
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
Click to expand...
Click to collapse
Well don't flash it twice. You have to put it in that mode twice to start it to complete the procedure. I do not believe in the wipe it 3 times to be sure, turn around and jump to make it better or faster. Loads of voodoo that is not scientifically proven around. It's all about a 0 and a 1, there is nothing in between that.
But .£60 to send that charger, LOL.
A month ago I bought an Aukey charger that included a USB-C cable for like .£12 including shipping to Belgium. (well just followed the rain and snow and landed here)
Let us know what happens next.

Any update on what you did?

GAH!
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse

seedaripper said:
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
Click to expand...
Click to collapse
But what about the drivers etc.... What shows up?

ROM?
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...

Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
lukesan said:
But what about the drivers etc.... What shows up?
Click to expand...
Click to collapse

seedaripper said:
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
Click to expand...
Click to collapse
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.

seedaripper said:
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Click to expand...
Click to collapse
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64

dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.

er?
lukesan said:
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
Click to expand...
Click to collapse
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?

lukesan said:
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)

Can't get my head round multi quote?
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)

seedaripper said:
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
Click to expand...
Click to collapse
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.

lukesan said:
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
Click to expand...
Click to collapse
Pics ...hopefully...

Question [SOLVED] Pixel 7 Dead(?)

Was installing the new build using flash-all.sh (without wipe) as I was rooted with Magisk.
Installer got stuck halfway. Disconnected, tried booting, got an error message saying device may have been corrupted or something like that.
The phone doesn't boot at all now, not even to the bootloader. Literally nothing shows up on the screen.
Any help would be greatly appreciated.

Double-check your download and make sure you have panther for Pixel 7.
Depending on what is corrupted, it may be very difficult to recover. With Qualcomm SoCs you can use a low-level tool like QPST (Qualcomm Product Support Tool). For Exynos you can often use ODIN. For Pixel, ODIN doesn't work and there aren't any QPST files (prob never will be).
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.

Hung0702 said:
Double-check your download and make sure you have panther for Pixel 7.
Click to expand...
Click to collapse
Yes, the images are for panther.
Hung0702 said:
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.
Click to expand...
Click to collapse
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.

dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.

V0latyle said:
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.
Click to expand...
Click to collapse
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .

hammered58 said:
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .
Click to expand...
Click to collapse
The Android Flash Tool works via ADB, so if the bootloader is corrupted or fails for some reason, that isn't an option.
Pixel devices (at least Snapdragon ones) do have the Qualcomm USB mode, but Google's prescribed means of repair in this situation is to simply replace the mainboard; most repair stations do not have QPST or the necessary files to restore the bootloader.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.

In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly

Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got

Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder

dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!

Vio281 said:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.
Click to expand...
Click to collapse
Not really. That’s how I broke it while updating. My phone wouldn’t boot at all and wasn’t even detected by my mac and windows pc. Had to send it to the service center.
t3chwizard said:
In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly
Click to expand...
Click to collapse
Thanks, I will do that.
J0nhy said:
Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got
Click to expand...
Click to collapse
It was just a black screen. It wouldn’t boot into any menu whatsoever.
Sui77 said:
Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder
Click to expand...
Click to collapse
Yes, that’s how I initially updated which somehow broke it. Anyway, got it repaired for free since it’s in warranty.
grandpajiver said:
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!
Click to expand...
Click to collapse
Hi, I had to send in the phone for a repair. It was a free repair since the phone’s in warranty.

That happened to me with Pixel 6 Pro. The screen only showed the charging icin and wouldn't respond and the phone was getting hot. I ended up rebooting it by holding the power key and one of the volume buttons (don't remember which one) for like 30-40 seconds and that rebooted it and from there I got to recovery mode and flashed the image via sideload.