Related
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.
Hi, I bought my HTC 10 around 7 months ago and a few weeks ago it restarted and it´s kept restarting since then. I tried doing a hard reset from the recovery because it doesn´t boot properly, but it didn´t work. I wanted to flash the RUU but I couldn´t find the right one on HTC SUPPORT. I wanted to try rooting my device and wiping data using TWRP to install a ROM and see if this could work, but as my phone doesn´t boot, I can´t unlock the OEM or debug developer mode.
Now I can´t even access to recovery mode so I can´t check my OS model, I just can access to bootloader mode.
If anyone can help me I´d really appreciate it.
Did your device still S-ON?
MatiasCinic said:
Hi, I bought my HTC 10 around 7 months ago and a few weeks ago it restarted and it´s kept restarting since then. I tried doing a hard reset from the recovery because it doesn´t boot properly, but it didn´t work. I wanted to flash the RUU but I couldn´t find the right one on HTC SUPPORT. I wanted to try rooting my device and wiping data using TWRP to install a ROM and see if this could work, but as my phone doesn´t boot, I can´t unlock the OEM or debug developer mode.
Now I can´t even access to recovery mode so I can´t check my OS model, I just can access to bootloader mode.
If anyone can help me I´d really appreciate it.
Click to expand...
Click to collapse
If you didn't do anything to your phone it's probably the battery. This is the most talked about problem in these forums. Can you boot to download mode? If so what's your CID?
yldlj said:
If you didn't do anything to your phone it's probably the battery. This is the most talked about problem in these forums. Can you boot to download mode? If so what's your CID?
Click to expand...
Click to collapse
Now I can´t boot to download mode, just to bootloader.
fresh777 said:
Did your device still S-ON?
Click to expand...
Click to collapse
Yes
MatiasCinic said:
Now I can´t boot to download mode, just to bootloader.
Click to expand...
Click to collapse
Well seems to me it's a brick. What did you attempt to get where you are now?
yldlj said:
Well seems to me it's a brick. What did you attempt to get where you are now?
Click to expand...
Click to collapse
I just wanted to try to fix my phone. It´d be really great if I can fix it by myself but know I´m not sure if I can do it.
If I can boot to download mode I´m gonna try to flash the RUU, but I couldn´t find the right one because my phone was made in United Emirates as HTC support told me
MatiasCinic said:
I just wanted to try to fix my phone. It´d be really great if I can fix it by myself but know I´m not sure if I can do it.
If I can boot to download mode I´m gonna try to flash the RUU, but I couldn´t find the right one because my phone was made in United Emirates as HTC support told me
Click to expand...
Click to collapse
You need to flash ruu in download mode. What was wrong with your phone to begin with? Also what have you done? You can't just say I was trying to fix myphone and expect us to know what you have done. You need to provide more details
yldlj said:
You need to flash ruu in download mode. What was wrong with your phone to begin with? Also what have you done? You can't just say I was trying to fix myphone and expect us to know what you have done. You need to provide more details
Click to expand...
Click to collapse
My phone is in a stuck in a bootloop, I was using it one day and it restarted by itself. I was able to use it for a few minutes and then it restarted again untill the point that it doesn´t boot anymore. The only thing I have done is a hard reset from recovery, but it keeps restarting. Now I can´t boot to download mode that´s why I haven´t flashed the RUU, I just can boot into bootloader mode and when I try to boot into recovery or download mode from there it restarts again.
im having the same issue.
the buttons randomly stopped working, so i restarted the phone only to be greeted with a bootloop.
i had lineage os on my phone for a while, and today i installed a update, so that might be related to the sudden bootloop.
when i press vol down + power it just boot loops. if i press vol up + vol down it boots into the bootloader.
trying to start download or recovery mode just gets me into a boot loop again.
the bootloader says s-on.
i just found this in another thread
jichuan89 said:
Unbelievable - I actually managed to unbrick my HTC 10!! :victory::victory::victory: I still don't understand exactly what happened, but I'll document everything I did...
Before:
S-ON
Flashed bad boot image in download mode
Could not enter download, RUU, recovery, or system mode - all of them enter into bootloop
Could only enter white background bootloader mode (Volume Up + Volume Down + Power), which only allows flashing signed hosd image
What I did:
Followed @Tarima's link above. With the phone in the white background bootloader mode, I ran fastboot flash $x $x.img with $x = each of the partitions. Except for hosd, all the other commands printed an error like
Code:
sending 'xbl' (1809 KB)... OKAY
writing 'xbl'... FAILED (remote: cannot flash this partition in s-on state)
but I continued anyway.
Selected "REBOOT TO BOOTLOADER" from white background bootloader
Downloaded an RUU exe file from here (I got the 1.96.617.20 version, but in hindsight it probably doesn't matter which version), and extracted an RUU zip file (following this guide on Linux)
Renamed the RUU ZIP to 2PS6IMG.zip, copied it to the root of an empty FAT32-formatted microSD card, and inserted the card into the HTC 10 (inspired by this post and this post)
Selected "BOOT TO DOWNLOAD MODE" from white background bootloader
This triggered a screen prompting whether to install update from SD card (photo).
I didn't need to actually install the update from the SD card; instead, the presence of a valid update on the SD card may have short-circuited whatever was causing the download mode to crash loop, and allowed the phone to enter download mode and accept fastboot flash commands. Since my problem was a bad boot image, I just did
Code:
fastboot flash boot boot.img
with the boot.img extracted from the official Nougat OTA zip's firmware.zip, and it worked! Phone was able to boot back into system / download / RUU / recovery. :victory:
I'd already given up hope and bought another HTC 10 off Swappa I've now learned my lesson and I'm going to S-OFF at once.
Click to expand...
Click to collapse
i havent had a chance to try this yet since i dont have a usb-c cable on my hands right now, but i feel like it is worth a shot @MatiasCinic.
also here is a safe place to download the htc 10 ruu https://www.htc.com/us/support/rom-downloads.html
im gonna update once i tried it
justundefined said:
im having the same issue.
the buttons randomly stopped working, so i restarted the phone only to be greeted with a bootloop.
i had lineage os on my phone for a while, and today i installed a update, so that might be related to the sudden bootloop.
when i press vol down + power it just boot loops. if i press vol up + vol down it boots into the bootloader.
trying to start download or recovery mode just gets me into a boot loop again.
the bootloader says s-on.
i just found this in another thread
i havent had a chance to try this yet since i dont have a usb-c cable on my hands right now, but i feel like it is worth a shot @MatiasCinic.
also here is a safe place to download the htc 10 ruu https://www.htc.com/us/support/rom-downloads.html
im gonna update once i tried it
Click to expand...
Click to collapse
I´m gonna give it a try, but I´m not sure if it´s gonna work. Hopefully I might be able to boot into download mode and get to know my CID. Thanks
i promised to update once i tested the methode. sadly it didnt seem to work for me.
flashing hosd worked like in jichuan89 case. but puting the 2PS6IMG.zip into a formatted sd card didnt seem to work for me.
booting into download mode sill gives me a bootloop.
unless someone comes up with a new idea on how to fix this, i might have to get a new phone :/
yldlj said:
If you didn't do anything to your phone it's probably the battery. This is the most talked about problem in these forums. Can you boot to download mode? If so what's your CID?
Click to expand...
Click to collapse
Hey, I could find I sheet of paper where I wrote down the OS number when my phone was still booting into download mode.
OS: 3.16.401.2
***Locked***
***Fused***
htc_pmeuhl PVT S-ON
SN: FA714BN074
On the back of my phone is written "Model: 2PS6200
I don´t know if this could help
Thanks
MatiasCinic said:
Hey, I could find I sheet of paper where I wrote down the OS number when my phone was still booting into download mode.
OS: 3.16.401.2
***Locked***
***Fused***
htc_pmeuhl PVT S-ON
SN: FA714BN074
On the back of my phone is written "Model: 2PS6200
I don´t know if this could help
Thanks
Click to expand...
Click to collapse
That's all good but unfortunately if you can't boot to download mode you can't flash RUU. Also if the method above didn't work i think it's time to send it to HTC or but a new phine
yldlj said:
That's all good but unfortunately if you can't boot to download mode you can't flash RUU. Also if the method above didn't work i think it's time to send it to HTC or but a new phine
Click to expand...
Click to collapse
Alright, thanks for your help
Hi Guys,
I think the problem causes by power and volume keys' ribbon. When i try pressing and holding power and volume down keys the gray HTC logo appears. But when i try pressing only volume down key the gray HTC logo appears again. As if power button always pressing itself. I'm gonna try remove connection after normal HTC logo disappears. If it fix the problem i will inform you again. Wish me luck :fingers-crossed::fingers-crossed:
any update? did it work?
venom55521 said:
any update? did it work?
Click to expand...
Click to collapse
Since October 2018........yeah still very relevant
venom55521 said:
any update? did it work?
Click to expand...
Click to collapse
Unfortunately i buried my htc 10 with a ceremony :laugh:
I have exactly the same problem. Word by word of what is described here. I feel no linger alone ahah.
So I have two questions.You basically just copy de zip file named accordingly into an SD card and follow the steps? Can I do this on a Mac?
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!
LE2125 Installed but when TWRP loads none of the Dialog works, its locked up.
weeems said:
LE2125 Installed but when TWRP loads none of the Dialog works, its locked up.
Click to expand...
Click to collapse
How did you install twrp and is it 3.6.0
MrSteelX said:
How did you install twrp and is it 3.6.0
Click to expand...
Click to collapse
I used fastboot flash and it is 3.6.0 yes
weeems said:
I used fastboot flash and it is 3.6.0 yes
Click to expand...
Click to collapse
Wrong installation method
weeems said:
I used fastboot flash and it is 3.6.0 yes
Click to expand...
Click to collapse
You have to use fastboot boot twrp. Now you must install stock kernel and start over.
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
HellsBells7 said:
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
Click to expand...
Click to collapse
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
MrSteelX said:
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
Click to expand...
Click to collapse
Can you point me to a guide to doing so? I'm afraid I don't know, first time I've ever screwed up this bad. Not even sure where to get files or anything of that nature, Or how to get them onto the phone via fastboot (seems to be the only way to interact)
EDIT: Will this help me?
HellsBells7 said:
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
Click to expand...
Click to collapse
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
HellsBells7 said:
Can you point me to a guide to doing so? I'm afraid I don't know, first time I've ever screwed up this bad. Not even sure where to get files or anything of that nature, Or how to get them onto the phone via fastboot (seems to be the only way to interact)
EDIT: Will this help me?
Click to expand...
Click to collapse
Yes
OK, thanks for being patient with me. I have the program downloaded to my computer but I don't seem to be able to get my phone into the prescribed EDL mode. Fastboot, yes, but not EDL. The fastboot command from my terminal window isn't working, and obviously I'm too far gone for adb at this point.
Is there a combination of hardware keys that will force EDL? Or perhaps an easier way that I'm missing altogether?
Again, thank you for helping me. I don't remember having this much trouble with the 6T.
From fastboot. Temp boot twrp and have it boot to edl. If no touch, can you plug in a mouse. If all fails, with phone off hold vol up and down together and plug in USB cable
I got it back on to stock! Thanks for everyone's help.
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.
PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image
DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.
Read this thread if you haven't...
blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.
lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.
rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.
PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked
If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.
Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.