Develop Bugs

Gnex: bricked or dead? Please help.

Hey guys, I just inherited a non-functioning gnex. The previous owner said the phone was working fine until it fell of a ledge whilst in a bag. There is no obvious physical damage to the phone chassis or screen.
When I try to power on the phone, it vibrates once but nothing further seems to happen and the screen stays black. Several minutes later though, it starts making some of the android system noises seemingly at a random. If I press either of the volume buttons, it makes the standard volume up or volume down ringer noise. But nothing else really happens other than a continuation of some of the system noises. Sometimes it seems to load a media file or a game once the phone has been powered on with the battery in. When connected to a windows machine, the device mounts and the contents of the phone are uncorrupted.
I've tried different combinations of the power buttons+volume rockers to get into recovery or fastboot, but so far no luck.
I've also tried the OMAP flash but can't get the computer to recognize the phone as a omap4460 for more than a couple of seconds. I've tried the Samsung drivers and the universal naked driver.
The only thing I haven't tried is ODIN (which I'm assuming won't work without being able to enter fastboot or recovery?), which might be last act of desperation before giving up. I'll update accordingly.
Any other suggestions would be greatly appreciated.

I think you have a damaged screen.
try to put phone in odin mode, pull battery out, reinsert it, press volume down with power button for 3 seconds, connect to pc, open odin, see if odin recognize your phone.

Yep it sound like everything is working except for screen. You can try to open it to disconnect and reconnect the screen: http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182/1 (not sure exactly how) if it doesn't work you can order a replacement screen (eBay or such) and do it yourself (expensive and not easy) or give it to a repair shop (expensive but easy).

Sounds like it's a damaged LCD, not cheap...
I'd buy it off you if its the vz nexus (For parts.)

Thanks guys, I suspect it's the screen also. I haven't gotten around to Odin yet but that will likely be my final attempt at trying to revive the phone.
If it is just screen damage though, would that prevent me from entering recovery mode?
I should've probably already mentioned that this the international version of the gnex (i9250m from Bell Canada), so no LTE.

horseycraze said:
Thanks guys, I suspect it's the screen also. I haven't gotten around to Odin yet but that will likely be my final attempt at trying to revive the phone.
If it is just screen damage though, would that prevent me from entering recovery mode?
I should've probably already mentioned that this the international version of the gnex (i9250m from Bell Canada), so no LTE.
Click to expand...
Click to collapse
I'd recommend fastboot. Same thing, less steps, though you will need adb...
(If its available for your model, if not odin would be your only choice. )
Odin has a few more steps...
Long story short you wouldn't know if the screen is dead sadly, with out a replacement, best of luck!

Any insight on how to get into ADB or fastboot? As stated in the OP, the power button combos don't work. Furthermore, I don't have a way of enabling debugging mode.
I still haven't tried Odin, I won't have access to a windows pc for a few more days. I'll update accordingly.

Getting into fastboot is very easy:
Turn off. Since you can't see anything pull battery and reinsert to make sure.
Press volume up, volume down and power at the same time for few seconds.
You feel a vibration like it does on every boot.
That's it, you are in fastboot mode.
To verify, plug into computer and type fastboot devices
If it writes something like this:
0149BD34ABCDABCD fastboot
then you are in fastboot mode.
If it doesn't work, check the drivers. Remember that you need to install the drivers once for every mode (in Windows). fastboot? drivers. MTP? drivers. ADB? drivers. ADB in custom recovery? drivers. Download mode? drivers. OMAPFlash? drivers again. And different modes have different drivers too.

Options for Recovering Files & Phone Repair???

Today hasn't been one of the better ones this week. Putting aside my pride for a moment, here's what happened. In my frustration, I threw my phone into a cardboard box. Aiming for the side of the box...it ricocheted of the floor then the side. Yeah, not the best available option to vent!
So...screen spiderwebed and the screen will no longer turn on. Phone vibrates when the power button is used, yet screen is blank.
I'd like to ask for help for the following:
Retrieve several important files that weren't back yesterday: Pictures & program files not synced for privacy reasons, plus TWRP backup from a couple of days ago to internal memory b/c SD full.
Screen damage or more involved? To determine if I spend time fixing or buying a replacement phone.
Phone is the Canadian Koodo T989D running CM11 8/04 with TWRP 2.7.1
Phone Symptoms:
After removing and replacing battery
Pushing power button - Normal 'turning on' short vibrate, screen doesn't turn on (no light/pixels light up)
Recovery Mode - Normal Vibrate, release pwr button and again screen blank with exception of top Left corner showing multiple pixels, unrecognizable
Download Mode - Plugging in the USB cord causes the phone to vibrate every 2 or three seconds and the cycle repeats. vibrate...vibrate...vibrate...continuous
Any thoughts on troubleshooting to determine if retrieving files on the phone is still an option?
Would appreciate ya'll sharing your common knowledge that uncommon while I'm this frustrated. After switching to an AWS service provider (WIND) 2 weeks ago my backup phone isn't compatible - Galaxy Ace GT-S5830D. Thought it was until I tried, then realized it isn't. I'm kind of flustered that I acted so impulsively and doubly because I thought I had a backup phone, ughh!

I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?

MASTERBLASTER69 said:
I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?
Click to expand...
Click to collapse
Thanks for the educated guess and ADB suggestion to recover files.
Yes the computer shows 3 drives when attached in Recovery Mode. And darn it I can't remember if debugging on or off. The computer doesn't recognize the phone by default while in recovery mode. If this is the case, would ADB likely allow access to the phone? Not a tool familar with yet.
Unlikely that the battery is damaged if the phone turns on. Still stays cool while on or charging. Which is good news.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.

the computer shows 3 drives when attached in Recovery Mode.
Click to expand...
Click to collapse
I don't understand why you see 3 drives... I'm sure Windows will ask you to insert removable storage if you try to access the drives, right? If that is the case, and you have no screen/touchscreen, only ADB will allow you full access to everything in the phone.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.
Click to expand...
Click to collapse
Yes. Here's the tricky part though, in order to make adb work, your computer needs the right drivers for your phone.
I think you should try to follow the HOWTOS (How to Install Android ADB Interface Drivers) on installing the drivers for ADB.
If all goes well, you can check if it worked by typing 'adb devices' from the windows commandline. Then it would be possible to use adb to get your files back.

If the phone boots into the system...if, since you can't see it....you should be able to open the sd folder on your pc and simply copy/move what you want to the pc.
Just checking if you've tried this.

Stuck in Fastboot boot loop after OTA update -- HELP!

So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.

I have access to the device via usb / fastboot, adb is not registering. If anyone has any suggestions on what I can try, please let me know. I do not have a backup or a version of the OEM ROM. Every effort so far just sends me right back to the Fastboot screen with 3 options. Anything I can run from command prompt using fastboot alone that would help in this situation? Any way to do a factory restore without having an actual OEM image?

Well im stuck at the verizon screen too but for a different reason
JRSwole said:
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance

dadrumgod said:
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
Click to expand...
Click to collapse
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.

JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Thanks for your response, I have unfortunately tried that too and wipe cache, reset , all back to fastboot. I figured it would be impossible without a pc. Oh yea my stock recovery says modified in the top left corner, but anyway I can get access to a PC But honestly it's been awhile since I even needed to use one and don't know exactly where to start, like navigating around, and how to install what software on the pc. I can't find anyone that will walk me through it locally or online and every tutorial I find is missing some lil step I need. I know Android in detail but after basic root my experience hits a brick wall. I'm capable of more jus got to get broke in on a pc again. Now I only care to root for stuff like freezing apps, gesture control, and really want to use any app in dual window. Ain't screwing with any system tweaks again it was pointless lol I guess I need all the right files and hit up the pc...can't really do worse no??
Sent from my VS986 using Tapatalk

JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Oh yea I almost forgot I got side tracked earlier. I know there is already a twrp, I have 2 versions (2.8...something and the next version strait off twrp site. I was the one guy it wouldn't flash through flashify for but others claimed it did. God knows really, but I'm gonna wait till I have a PC of my own before I touch my g4 but man the ability to open any app in dual window is just too damn sweet...if I could only change that one word on build prop to false without all the other hassle
Sent from my VS986 using Tapatalk

JRSwole said:
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.

gnomesinrome said:
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
Click to expand...
Click to collapse
If your problem is from an OTA failing due to taking it while modded and you can get to fastboot the following command might fix it:
Code:
fastboot erase cache
That will delete the OTA zip and break the bootloop.

moto z2 on "press any key to shutdown" potential hardbrick

I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?

latadswapnil said:
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
Click to expand...
Click to collapse
The phone is unbrickable unless the hardware issue.
Sent from my LG-LS997 using Tapatalk

cgigate said:
The phone is unbrickable unless the hardware issue.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Can you please suggest a way to get into bootloader ? because currently whenever I switch on phone it shows tmobile logo(boot screen) and nothing happens and there is a message in left top corner "press any key to shutdown" . I tried to switch it on with volume down and power key but nothing happens blank screen.
Also it is not getting detected on my laptop not even as unknown device.

latadswapnil said:
Can you please suggest a way to get into bootloader ? because currently whenever I switch on phone it shows tmobile logo(boot screen) and nothing happens and there is a message in left top corner "press any key to shutdown" . I tried to switch it on with volume down and power key but nothing happens blank screen.
Also it is not getting detected on my laptop not even as unknown device.
Click to expand...
Click to collapse
Have you tried holding vol up and pwr to boot into bootloader?

41rw4lk said:
Have you tried holding vol up and pwr to boot into bootloader?
Click to expand...
Click to collapse
Yes I did try that and it only shows the Tmobile boot screen and "press any key to shutdown" on left top of screen as attached in the picture. :crying:

latadswapnil said:
Yes I did try that and it only shows the Tmobile boot screen and "press any key to shutdown" on left top of screen as attached in the picture. :crying:
Click to expand...
Click to collapse
Make sure you're using a 2.0 port from your mobo, not a hub and not a 3.0+ port.
Unplug your phone and try entering these commands one at a time, you might need to unplug before each command.
This all depends on whether you had your bootloader unlocked, adb enabled, etc. You put yourself in a weird state.
Unplug, open cmd prompt and enter
fastboot reboot bootloader it should say waiting for device
plug in your phone and hopefully it'll get you there. If not, repeat above and try
adb reboot bootloader
following the same procedure
fastboot reboot recovery
like above
adb reboot recovery
Hopefully one of those will get you somewhere where you can try to reflash the phone, factory reset, whatever it takes.
Since your pc doesn't recognize your device... who knows.
Last resort
Fastboot oem blankflash
If that works you should be ready to blankflash

41rw4lk said:
Make sure you're using a 2.0 port from your mobo, not a hub and not a 3.0+ port.
Unplug your phone and try entering these commands one at a time, you might need to unplug before each command.
This all depends on whether you had your bootloader unlocked, adb enabled, etc. You put yourself in a weird state.
Unplug, open cmd prompt and enter
fastboot reboot bootloader it should say waiting for device
plug in your phone and hopefully it'll get you there. If not, repeat above and try
adb reboot bootloader
following the same procedure
fastboot reboot recovery
like above
adb reboot recovery
Hopefully one of those will get you somewhere where you can try to reflash the phone, factory reset, whatever it takes.
Since your pc doesn't recognize your device... who knows.
Last resort
Fastboot oem blankflash
If that works you should be ready to blankflash
Click to expand...
Click to collapse
Yes bootloader was unlocked and adb was enabled also phone was rooted.
I am trying what you have suggested but its not working till now. I tried on USB 2.0 ports and 3.0 as well but nothing happens. neither blankflash executes nor any of fastboot or adb commands executes.
will linux OS help ?

latadswapnil said:
Yes bootloader was unlocked and adb was enabled also phone was rooted.
I am trying what you have suggested but its not working till now. I tried on USB 2.0 ports and 3.0 as well but nothing happens. neither blankflash executes nor any of fastboot or adb commands executes.
will linux OS help ?
Click to expand...
Click to collapse
Never hurts to try, the thing is your phone is in some limbo state and your pc doesn't doesn't see it. I can't imagine that linux will help much. Have you tried holding the power button for a minute or so? I don't know what the sde partition is honestly, but obviously you shouldn't have messed with it. What lead you to that partition and what exactly did you do?
You might uninstall your moto drivers, adb drivers, and fastboot drivers and see if plugging your phone in will detect on your pc as new hardware. Might try installing qualcomm diag drivers to see it it will recognize your phone. I afraid that until your pc sees it, any command is pointless since it can't communicate with your phone.

41rw4lk said:
Never hurts to try, the thing is your phone is in some limbo state and your pc doesn't doesn't see it. I can't imagine that linux will help much. Have you tried holding the power button for a minute or so? I don't know what the sde partition is honestly, but obviously you shouldn't have messed with it. What lead you to that partition and what exactly did you do?
You might uninstall your moto drivers, adb drivers, and fastboot drivers and see if plugging your phone in will detect on your pc as new hardware. Might try installing qualcomm diag drivers to see it it will recognize your phone. I afraid that until your pc sees it, any command is pointless since it can't communicate with your phone.
Click to expand...
Click to collapse
SDE are mobile partitions and I was trying to delete modem partitions as I had installed pie modem on my device and I might have accidentally deleted the bootloader partition or something like that.
after holding power button for a minute nothing happens same screen appears and disappears as I have attached in my previous reply.
is there a button combination which can direct this device in edl mode?
laptop is not reading my device yet, I tried different laptops different ports and different cables. linux is also not reading the device.
please let me know if you know any way I can boot this in edl mode to blankflash. I tried that cable way green and black cable short thats not working either on this device.

latadswapnil said:
SDE are mobile partitions and I was trying to delete modem partitions as I had installed pie modem on my device and I might have accidentally deleted the bootloader partition or something like that.
after holding power button for a minute nothing happens same screen appears and disappears as I have attached in my previous reply.
is there a button combination which can direct this device in edl mode?
laptop is not reading my device yet, I tried different laptops different ports and different cables. linux is also not reading the device.
please let me know if you know any way I can boot this in edl mode to blankflash. I tried that cable way green and black cable short thats not working either on this device.
Click to expand...
Click to collapse
There is no key combo as far as I know to enter edl mode on this phone, and most likely it wouldn't solve your problem. You flashed pie modems on a TMO device, that has been done before and no one has been able to recover from that. Even if you were to somehow get your phone booting, you wouldn't have a baseband or any cell service.

41rw4lk said:
There is no key combo as far as I know to enter edl mode on this phone, and most likely it wouldn't solve your problem. You flashed pie modems on a TMO device, that has been done before and no one has been able to recover from that. Even if you were to somehow get your phone booting, you wouldn't have a baseband or any cell service.
Click to expand...
Click to collapse
While if the OP is correct, and the problem is that they replaced their bootloader, then that's exactly what edl mode is for. However, you're definitely right that there's no key combination. I've been trying to get my moto into edl for days. I even got the battery to die. It just makes other diagnostics more annoying when I need to charge. So far, from what I can tell, the MSM8998 in a Z2 force first of all plays by different rules, uses a different programmer, and is generally not going to respond to the stock "qualcomm unbrick" tutorials. If it gets into edl, then you might be able to blankflash. But I guess keep trying different things, from what I've read the drivers and usb ports are finicky even with phones where this is known to work. It is not known to work with TX1789, at least not with the ease it works in other snapdragon phones. It's actually a massive security vulnerability (if it works it allows arbitrary read/write from the lowest level of the chain of trust, bypassing most security by default. It's a total backdoor), it's just unfortunate we're on that side of the fence. It doesn't have to be that way, but it was designed to see all unsigned software as equally malicious.

latadswapnil said:
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
Click to expand...
Click to collapse
Does anybody have any new suggestion how I can get into EDL mode?
my phone is still stuck on to the screen where it says press any key to shutdown. It doesn't get detected at all on any USB port or with different cables.
Does anybody know if there are any EDL short points on motherboard or deep flashing cable?
although I tried cutting regular USB C cable for trying to short the two cables and force put it in edl mode but nothing worked yet.
If anybody has any suggestion please throw some light.

Question Phone probably hardbricked

Hi to all, yesterday I tried to root my phone following a guide here on XDA Developers (I don't remember which one). I have a Pixel 6 Pro and I tried to flash boot.img when the phone, after being restarted, starts to bootloop and then I try to turn it off. Then, the panic. The phone doesn't seem to be recognizable by ADB nor fastboot and the screen is permanently black. When I try to hold Power button and other combinations (while plugged to my PC) Windows emits some system sounds like "plugged" or "unplugged device" but I can't find my phone like recognizable.

Phone isn't hardbricked, but softbricked.
Re-flash Stock ROM.

xXx yYy said:
Phone isn't hardbricked, but softbricked.
Re-flash Stock ROM.
Click to expand...
Click to collapse
I can't interact with phone, I just see "Pixel ROM Recovery" on devices when I connect to my PC. I don't even know if it's in recovery, if it's on or off

You might be better off if this thread was moved to the Pixel 6 Pro forum -- I can move this if you request.
But determining if you can get into Fastboot/Bootloader Mode will determine whether this is soft-bricked or not; whether this is recoverable on your end or you'll have to bring it to Google/repair shop. At this point, the only way to get into that mode is through the button combinations -- I've seen some instances where user had to hold the button combination for 1-2 minutes before it popped up; and obviously the device will need to have sufficient battery charge...

simplepinoi177 said:
You might be better off if this thread was moved to the Pixel 6 Pro forum -- I can move this if you request.
But determining if you can get into Fastboot/Bootloader Mode will determine whether this is soft-bricked or not; whether this is recoverable on your end or you'll have to bring it to Google/repair shop. At this point, the only way to get into that mode is through the button combinations -- I've seen some instances where user had to hold the button combination for 1-2 minutes before it popped up; and obviously the device will need to have sufficient battery charge...
Click to expand...
Click to collapse
If you could move it to Pixel 6 Pro forum I'd be grateful, btw idk if I can reboot into bootloader. In fact I would like to know if I can. I tried to read this https://forum.xda-developers.com/t/...evices-with-deleted-bootloader-sboot.3573865/ but I can't understand many things. So if you know how to repair it, I would be very grateful

Chexet48 said:
If you could move it to Pixel 6 Pro forum I'd be grateful, btw idk if I can reboot into bootloader. In fact I would like to know if I can. I tried to read this https://forum.xda-developers.com/t/...evices-with-deleted-bootloader-sboot.3573865/ but I can't understand many things. So if you know how to repair it, I would be very grateful
Click to expand...
Click to collapse
First and foremost is seeing if you can get to Fastboot/Bootloader Mode; When your device is off and not connected to anything (at all, no cord connecting to PC or power plug or anything), hold the Power & Volume+Down buttons simultaneously for up to 2 minutes. If you cannot power on into this mode, you will not be able to flash your device's stock firmware to re-establish any system data that may have been corrupted. It is unlikely, but you may have other options if you can boot into Recovery Mode or somehow into the OS, but if you cannot get into Fastboot Mode, it is too unlikely that you would be able to boot into these. But if you are successful into loading Bootloader/Fastboot Mode...
There's two ways i would suggest you go about it...The first and easiest is to run the official Google Android Flash Tool -- You should be able to load up the latest factory firmware version for your device (Raven), and it should be able to flash the factory image onto your phone to get it working; BE SURE to check the "keep data" (or do not wipe; I can't recall off the top of my head) and to flash to both slots (just to be safe). The second way is to follow THIS GUIDE (as directed by roirraW "edor" ehT's Pixel 6 Pro guide who holds the defacto quintessential central guide in the Pixel 7 Pro forum in which is most up to date, but not catered to "raven") -- specifically you will find what is needed in the "Update and Root Factory Image" section; play close attention to the method using the "flash-all.bat" as that is the simplest and most straightforward way to go about it.. Please read everything and place close attention on being sure to go about it without "wiping" your device (removing the "-w" in the flash-all.bat file), else if you are able to recover your system, your data will not be there when coming back to it and everything would be factory reset.