Develop Bugs

[Q] :( HEEEEEELP! STUCK AT LG LOGO WHEN I TRY TO BOOT! But wait, there's more......

I have spent the last 3 days searching XDA & trying every possible fix, no luck!
Here's my dilemma.....
I have custom recovery, TWRP 2.6.3.3, don't know what I did after trying to flash something........ I wiped everything except SDcard by accident. Like a darn fool, forgot after backing up everything via computer, to put a spares on my SDcard. Sooooo, I tried restoring by using LG FlashTool..... Here's where my problems began:
1. I can't load into download mode, it sticks at the logo to enter download mode but doesn't connect.
2. I tried ADB Sideload, sticks at "STARTING ADB SIDELOAD FEATURE.........."
3. No matter what mode (including Fastboot) I try, just won't connect to my computer the way I need it to. (*ALL DRIVERS HAVE BEEN REINSTALLED NUMEROUS TIMES, STILL NO LUCK.*) When I look in DEVICE MANAGER, it shows in "OTHER DEVICES" as "LG-LS980" (*Which is a good thing right? *)
At this point i'm at my wits end...... I tried to HARD FACTORY RESET, but didn't go thru. I'm afraid that if I tried it again, I could cause even more damage.
I've been without my phone for days & I'm about to go crazy if I have to pay LG or Sprint again for another phone!!!! I'd rather use my $600 on something else.
PLEASE TELL ME SOMEONE HAS FOUND A WAY TO GET AROUND THIS!
I've searched just about every forum & tried different methods.

Forgot to add that every time I power off from recovery, I get a the message about my device not being rooted, would I like to install..... When I swipe to install, nothing happens. Just powers off.

MsOhSoPhresh said:
I have spent the last 3 days searching XDA & trying every possible fix, no luck!
Here's my dilemma.....
I have custom recovery, TWRP 2.6.3.3, don't know what I did after trying to flash something........ I wiped everything except SDcard by accident. Like a darn fool, forgot after backing up everything via computer, to put a spares on my SDcard. Sooooo, I tried restoring by using LG FlashTool..... Here's where my problems began:
1. I can't load into download mode, it sticks at the logo to enter download mode but doesn't connect.
2. I tried ADB Sideload, sticks at "STARTING ADB SIDELOAD FEATURE.........."
3. No matter what mode (including Fastboot) I try, just won't connect to my computer the way I need it to. (*ALL DRIVERS HAVE BEEN REINSTALLED NUMEROUS TIMES, STILL NO LUCK.*) When I look in DEVICE MANAGER, it shows in "OTHER DEVICES" as "LG-LS980" (*Which is a good thing right? *)
At this point i'm at my wits end...... I tried to HARD FACTORY RESET, but didn't go thru. I'm afraid that if I tried it again, I could cause even more damage.
I've been without my phone for days & I'm about to go crazy if I have to pay LG or Sprint again for another phone!!!! I'd rather use my $600 on something else.
PLEASE TELL ME SOMEONE HAS FOUND A WAY TO GET AROUND THIS!
I've searched just about every forum & tried different methods.
Click to expand...
Click to collapse
So try this...
Push the power button to turn the device on. Let it sit.
After you know that the g2 is on and trying to do its think, Press and hold power buttton, do not let go. It will force turn off the phone, but it will start to turn back on, if you keep holding the power button till it shuts off for the second time, you'll be set and the device will be fully off.
Have Lg Flash Tool open, make sure you have manual mode on and you point to the right dll and right tot file, could be zv7 zv8 or zva.
Click the arrow to have the flash tool biin check the files. when that is ready, do this next part fast. Plug in your phone, and immeditaly press and hold Volume up and Power. Download mode should appear.
and you should be good from there! If you try to enter download mode by using volume and up without the cable plug in, you'll hit the factory reset menu which is tied to the recovery, it'll do nothing, only take you to recovery. I hope this is of some help!

Edit:try new boot loader or system flasher via twrp
proplem i faced is one button which used to enter recovery is damged
Flash stock Ignoring the unmonted ianot able to be mounted then change system partitions u will be able to mount
Enjoy

bmxerkid954 said:
So try this...
Push the power button to turn the device on. Let it sit.
After you know that the g2 is on and trying to do its think, Press and hold power buttton, do not let go. It will force turn off the phone, but it will start to turn back on, if you keep holding the power button till it shuts off for the second time, you'll be set and the device will be fully off.
Have Lg Flash Tool open, make sure you have manual mode on and you point to the right dll and right tot file, could be zv7 zv8 or zva.
Click the arrow to have the flash tool biin check the files. when that is ready, do this next part fast. Plug in your phone, and immeditaly press and hold Volume up and Power. Download mode should appear.
and you should be good from there! If you try to enter download mode by using volume and up without the cable plug in, you'll hit the factory reset menu which is tied to the recovery, it'll do nothing, only take you to recovery. I hope this is of some help!
Click to expand...
Click to collapse
This isn't working. I've tried this numerous times..... No luck.

myaservip said:
Edit:try new boot loader or system flasher via twrp
proplem i faced is one button which used to enter recovery is damged
Flash stock Ignoring the unmonted ianot able to be mounted then change system partitions u will be able to mount
Enjoy
Click to expand...
Click to collapse
I'm now completely lost.....

Ok... So i made a little progress....
I am now able to boot into fastboot mode.... No recovery now tho. If someone can help me with manually pushing everything I need to restore my phone, it would make my day!
I'm having withdrawal symptoms now. LOL! I MISS MY PHONE!

Problem solved!
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!

MsOhSoPhresh said:
This isn't working. I've tried this numerous times..... No luck.
Click to expand...
Click to collapse
MsOhSoPhresh said:
I am now able to boot into fastboot mode.... No recovery now tho. If someone can help me with manually pushing everything I need to restore my phone, it would make my day!
I'm having withdrawal symptoms now. LOL! I MISS MY PHONE!
Click to expand...
Click to collapse
MsOhSoPhresh said:
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
Click to expand...
Click to collapse
Glad to see you've fixed your problem! I myself haven't been around, had some down time to. My sim reader magically stopped working and then randomly started working days later. Anyway, congrats!!!

MsOhSoPhresh said:
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
Click to expand...
Click to collapse
Glad you figured it out. I was about to basically explain the steps to do exactly what you did.
Welcome back to the land of the living!

agentfusion said:
Glad you figured it out. I was about to basically explain the steps to do exactly what you did.
Welcome back to the land of the living!
Click to expand...
Click to collapse
After she got it the first time, which we both congratulated her for, something went completely wrong. She dug herself even deeper, but broke download mode. That was extremely fun to fix.

My HTC M8 Stuck at ONE Logo once restarted. No Recovery, No DWNLD mode available.

I've seen already this thread suggested by XDA thread locator.
https://forum.xda-developers.com/htc-one-m8/help/verizon-htc-one-m8-stuck-htc-logo-t3163088
But I'd try to explain as simple as possible the whole situation which happened hours ago.
Don't know what happened but my mothers phone went off and restarted with htc one logo on it and nothing else later.
Power button itself doesnt work and is not responding.
Configuration PWR + VOL UP gives me restart but no recovery mode, giving me sound effect of restarting phone and ONE logo on it without any other reaction whatsoever.
PWR + VOL DWN zero reaction
PWR + VOL UP & DOWN pressed together restarting the phone and then gives me HTC ONE LOGO and nothing else.
when Phone is plugged in to the computer and I'm forcing the phone to restart it shows me new Device on the computer as a CD Driver every time.
So I think there is still hope to get this guy back to life.
It's running on custom rom but unknown version because it was purchased as a refurb from ebay 2 years ago and it was running just fine utill this very day.
I'm absolutely noob with flashing twrping etc so please ELI5 if possible, any type of help will be much appreciated.
Thanks in advance.

Hey, I had this same problem a couple of days ago. Here's what I did to get the phone into fastboot, from where you can install a recovery, factory reset etc.
1. Hold the power button + vol up button for about 10-20 seconds. This should shut down the phone.
2. Hold the power button + vol down button to restart the phone back into fastboot.
If you can get into fastboot, there are plenty of guides which can help you flash a twrp image. If you want me to give you some instructions on that just reply and let me know. Good luck!

Note that this phone doesn't have download mode (as some other Android devices do); nor is there a button combo to go directly to recovery. But you can almost certainly still get to bootloader, and from there boot recovery. In the current condition, you can get to bootloader by:
1) Hold Power+ vol up (as you have been) to restart the phone.
2) Once the screen goes dark (signaling it is about to reboot) let go of the buttons, and only hold vol down
3) Don't let go of vol down until the bootloader screen appears.
4) If the above sequence fails, its virtually always because the user just didn't get the timing right (either started pressing vol down too late, or let go too early). Just repeat steps 1-3 until you get to bootloader.
Once in bootloader, try to reflash the ROM, or restore a TWRP backup (if you have one). Spontaneously stuck on HTC logo screen is often a result of the OS/ROM becoming corrupt or otherwise damaged, and flashing/restoring the ROM will often fix it.

Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
It's my mom's phone so basically reliabilty and robustness over flashing lights and numerous unnecessary functions.
Version of android doesn't really matter.
Thanks again for help so far.
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
TWRP might be extra helpful or the recovery it's functions are just fine?

Shewie said:
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
Click to expand...
Click to collapse
I'd need to know more about the phone in order to give any suggestions.
With the phone connected to computer, boot into fastboot mode, and (assuming you have fastboot setup on your computer) do the command: fastboot getvar all
Then post the results (delete IMEI and serial number before posting).
Also, what version TWRP (if that is the recovery installed)?
Shewie said:
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
Click to expand...
Click to collapse
You will be able to flash a ROM from the SD card, if using TWRP.
Shewie said:
TWRP might be extra helpful or the recovery it's functions are just fine?
Click to expand...
Click to collapse
Not sure what is being asked here (can't quite understand). Are you saying that another recovery besides TWRP is presently installed?

@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
I wouldn't mind link to the pack with "must have" to complete the process

Shewie said:
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
Click to expand...
Click to collapse
You have what is called the "stock recovery" or official HTC recovery.
You can't flash anything but OTA updates, or other official (HTC) signed zips with this. You need a "custom" recovery like TWRP in order to flash things like custom ROMs. So I'm curious what you meant before when you posted:
Shewie said:
Thanks [MENTION=660462]Sadly reflashing/factory reset failed few times due corrupted files.
Click to expand...
Click to collapse
What exactly were you trying to "reflash", what were the exact steps, and the results (specific error messages, etc.).

I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.

Shewie said:
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Click to expand...
Click to collapse
Okay, so you're confusing the terms. Factory reset doesn't flash/reflash anything (flash meaning to install some firmware or software to the device). The only thing that factory reset does is wipe user data.
At this point, I'd suggest the best/easiest course of action in the current conditions (stock recovery, locked bootloader) would be to run the RUU intended for your device. Your device is the AT&T version, so the RUU can be found at the bottom of the page (and instructions on how to install): http://www.htc.com/us/support/htc-one-m8-att/news/
RUU is a complete factory image. You download to a PC (PC required, won't work on Mac or Linux) connect the phone (booted into bootloader-fastboot mode) then just run the RUU, and it will do the rest.
I'm confidant this will get the phone up and running. Your mom may not like all the AT&T branding and apps, if it wasn't there before, and AT&T is not her carrier (one of the main reasons for these devices to have custom ROM - to remove carrier branding). But we can cross that bridge (if need be), after we get the phone working.

Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?

Shewie said:
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Click to expand...
Click to collapse
It just gets stuck sometimes. Just kill the process, and start the RUU again. It will probably work fine on the next try. It's a bit scary, as it says not to stop the process or disconnect the phone while it's running. But if it gets stuck like this, there isn't anything else you can do.

Good News, it's working. But it's bloated to the bones. How I can get rid of the carrier unnecessary software?
I was to afraid to kill the process during update to avoid scenario of bricking my phone completely.
But It's working!

Nexus 5x Recovery error, cannot go into bootloader, bootloader unlocked.

Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering

Psicovirus said:
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Click to expand...
Click to collapse
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.

Psicovirus said:
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Click to expand...
Click to collapse
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.

Nicktheprofessor said:
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Click to expand...
Click to collapse
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.

Psicovirus said:
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Click to expand...
Click to collapse
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.

Nicktheprofessor said:
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Click to expand...
Click to collapse
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?

Psicovirus said:
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Click to expand...
Click to collapse
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?

Nicktheprofessor said:
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Click to expand...
Click to collapse
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.

Psicovirus said:
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Click to expand...
Click to collapse
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.

Nicktheprofessor said:
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Click to expand...
Click to collapse
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.

Psicovirus said:
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Click to expand...
Click to collapse
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.

Nicktheprofessor said:
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Click to expand...
Click to collapse
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Edit2: Seems like i screwed up stalling stock recovery on top of twrp, sahme on me. How can i short the volume down button?

Psicovirus said:
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Click to expand...
Click to collapse
Reboot to recovery, use adb to sideload the OTA.
Reply to edit2: open it up, find the leads on the circuit board that go up to the vol down circuit breaker, use two needles and insert them into the solder where the breaker connects and while crossing the needles so they connect push power.
OR, fix the broken breaker, most of the time it's just a broken off brass dome that needs realigning, you'll need to fixate it which is just a needle's head worth of superglue on one side and a soldering on the other side (reflowing by heating the dome with a soldering iron usually works).
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.

Nicktheprofessor said:
Reboot to recovery, use adb to sideload the OTA.
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Click to expand...
Click to collapse
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?

Psicovirus said:
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Click to expand...
Click to collapse
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.

Nicktheprofessor said:
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Click to expand...
Click to collapse
Im trying to do that, i already have the phone open, sewing needles will do?

Psicovirus said:
Im trying to do that, i already have the phone open, sewing needles will do?
Click to expand...
Click to collapse
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.

Nicktheprofessor said:
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Click to expand...
Click to collapse
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.

Psicovirus said:
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Click to expand...
Click to collapse
You can use a q tip and some acetone to clear eventual lacquer from the solder points but the thing is, it's probably the emmc that is shot.
Your emmc obviously doesn't accept what the recovery the LGUP wrote to it. If it did, you'd be flashing the OTA right now. Why? I have no idea, I'd need to take the phone to the lab to examine what caused the degradation and even then I probably couldn't tell you much more about the actual cause.
And don't worry about it, your case is interesting and not easy to solve by simply doing a search, you weren't an arse about anything either and that is unusual and welcome.

Softbricked, locked bootloader ... HELP!!

I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.

Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?

Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools

Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.

Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.

Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.

Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.

Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks

Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.

Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.

Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?

Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/

After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...

Are you going to be able to RMA it? Is it still under warranty?

Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha

Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.

Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse

Good news! I got an RMA!!
Thanks for your help everyone!

Google pixel XL is now (probably) bricked

So i was trying to flash Lineage 16 to my pixel. after hours of messing around i got what was a broken version of it working. but i decided to try and fix it but now im bricked. tried to swap for boot slot A to B and now i cant even enter TWRP or even the normal recovery settings. i cant connect to my PC either because the thing wont register my pixel.
if anyone knows how to fix this please let me know

Same exact boat, I'll let you know if I make any progress. Problem appears to be related to the internal storage no longer being addressable.

RABBIDFIGHTER said:
So i was trying to flash Lineage 16 to my pixel. after hours of messing around i got what was a broken version of it working. but i decided to try and fix it but now im bricked. tried to swap for boot slot A to B and now i cant even enter TWRP or even the normal recovery settings. i cant connect to my PC either because the thing wont register my pixel.
if anyone knows how to fix this please let me know
Click to expand...
Click to collapse
Try and get into bootloader... turn phone off then hold power and down volume for like 30 seconds. If you can get into bootloader you can fastboot flash a good image back onto the unit.
Bootloader is not changed when flashing custom roms so should be ok.

adm1jtg said:
Try and get into bootloader... turn phone off then hold power and down volume for like 30 seconds. If you can get into bootloader you can fastboot flash a good image back onto the unit.
Bootloader is not changed when flashing custom roms so should be ok.
Click to expand...
Click to collapse
i can enter bootloader, but my pc wont detect my pixel. also unable to even enter recovery mode.
i have the pixel drivers installed on my pc. but if you can think of anything please tell me!

adm1jtg said:
Try and get into bootloader... turn phone off then hold power and down volume for like 30 seconds. If you can get into bootloader you can fastboot flash a good image back onto the unit.
Bootloader is not changed when flashing custom roms so should be ok.
Click to expand...
Click to collapse
THANK YOU SO MUCH. i got a file which had a Bat command file. that did everything in bootloader. unfortunately it booted to slot B but oh well. nothing twrp cant fix

RABBIDFIGHTER said:
THANK YOU SO MUCH. i got a file which had a Bat command file. that did everything in bootloader. unfortunately it booted to slot B but oh well. nothing twrp cant fix
Click to expand...
Click to collapse
Glad to help