Database Users

Errors in /cache/recovery -- Bricked????

Yesterday, it randomly started force closing all apps repeatedly (force close loop) and often freezing until the battery was pulled. It would work fine after powering on for 30-60 minutes at a time but then start messing up again. Sometimes it messed up right away though.
Today I made a nandroid backup and then tried wiping data/factory reset and wiping cache. I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know that is not good. But what does it mean??
---
Anyway, now no matter what ROM I flash (CM7.0.0, or an old nightly 37, 41, etc), I click "Reboot system now" and the screen just goes to black forever. I have to pull the battery again.
But then it freezes at the MyTouch 4G screen (left it for 10+ minutes). It never gets past that.
Yes, I even did a nandroid backup before wiping. But even restoring that does the same thing: it restores, I click reboot, and it goes to a black screen.
But no matter what, after a battery pull, it just freezes at the MyTouch 4G screen forever.
I *can* get into the white hboot/fastboot screen via Power + Volume Down and then get into CWM Recovery from there.
It just can't *boot* into any Android rom.
Am I bricked?? Is there a way to fix this??
Please help!

Everyone that i am aware of that has encounter this has not been able to recover from it.
It looks like it might be truly bricked.

Do u have the good emmc chip or bad? Theres plenty of threads regardin that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.4

Yup it looks like your eMMC chip went bad. I have a phone here that is doing the same exact thing. I have tried everything from fastbooting a new bootloader to the PD15 whatever its called full restore image. Nothing is working at all. I fear you have a truly bricked phone.

Ah [email protected]#!#[email protected]#[email protected]#$!$ !!!!!
A) What could have caused this?? From my viewpoint, of course it seems totally random but from reading other people's cases, have you guys seen any common link or can think of something that could have caused this?
[Edit] And B) Also, do you think T-Mobile would warranty replace it even though it is rooted with CyanogenMod 7 (even though it cannot be seen)? It was purchased Oct 2010, and I do have insurance on it.

Paul22000 said:
Ah [email protected]#!#[email protected]#[email protected]#$!$ !!!!!
A) What could have caused this?? From my viewpoint, of course it seems totally random but from reading other people's cases, have you guys seen any common link or can think of something that could have caused this?
[Edit] And B) Also, do you think T-Mobile would warranty replace it even though it is rooted with CyanogenMod 7 (even though it cannot be seen)? It was purchased Oct 2010, and I do have insurance on it.
Click to expand...
Click to collapse
once they see Clockwork ROM manager they'll know it was rooted.

cmdmilitia13 said:
Do u have the good emmc chip or bad? Theres plenty of threads regardin that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.4
Click to expand...
Click to collapse
How do I check?

neidlinger said:
once they see Clockwork ROM manager they'll know it was rooted.
Click to expand...
Click to collapse
Well, A) that's only if they press Volume Down + Power button. Do they normally know how to do that?
Also, B) is there a way to remove CWM?

Paul22000 said:
How do I check?
Click to expand...
Click to collapse
you have to be able to get into recovery.
http://forum.xda-developers.com/showpost.php?p=13834944&postcount=1

neidlinger said:
once they see Clockwork ROM manager they'll know it was rooted.
Click to expand...
Click to collapse
I have heard of people frying their motherboards by over volting the charging port so they no longer turn on before sending it in for a warranty return. I cant comment on this but if I can get mine warrantied that way I will do it. Not like the motherboard is any good now so might as well try. However! I do not suggest doing this.

Paul22000 said:
Well, A) that's only if they press Volume Down + Power button. Do they normally know how to do that?
Also, B) is there a way to remove CWM?
Click to expand...
Click to collapse
I'm sure they check first thing.
technically you could if you have the .85 hBoot.
But if you have the .85 hBoot they'll know the phone was tampered with since the engineering screen is different

neidlinger said:
you have to be able to get into recovery.
http://forum.xda-developers.com/showpost.php?p=13834944&postcount=1
Click to expand...
Click to collapse
Unfortunately, I'm not able to use adb even though I have it installed:
What am I missing here to get adb working?
In case I can't get that working, do any of these help to see if my emmc is bad?

Paul22000 said:
Unfortunately, I'm not able to use adb even though I have it installed:
What am I missing here to get adb working?
In case I can't get that working, do any of these help to see if my emmc is bad?
Click to expand...
Click to collapse
to get the phone working again? nope. To get it to an honest warrant-able state yes.

I was able to check the eMMC chip version on my bricked phone so you should be able to also. You need to be in clockwork recovery to do it.

neidlinger said:
to get the phone working again? nope. To get it to an honest warrant-able state yes.
Click to expand...
Click to collapse
Yes, at this point I don't care about getting this phone working. I have been paying for insurance every month since October, so getting it replaced is fine by me.
I just want to know how to get the phone in a state so that T-Mobile doesn't deny my warranty because I put CyanogenMod on it.
How do I get to back to a warrant-able state? That would be AMAZING. Any would would be MUCH appreciated!

Paul22000 said:
Yes, at this point I don't care about getting this phone working. I have been paying for insurance every month since October, so getting it replaced is fine by me.
I just want to know how to get the phone in a state so that T-Mobile doesn't deny my warranty because I put CyanogenMod on it.
How do I get to back to a warrant-able state? That would be AMAZING. Any would would be MUCH appreciated!
Click to expand...
Click to collapse
it's pretty much impossible at this state. If you have the .85 hBoot you could flash the stock image. but you need a working rom to flash back to .86 hBoot. When you do not have.

neidlinger said:
it's pretty much impossible at this state. If you have the .85 hBoot you could flash the stock image. but you need a working rom to flash back to .86 hBoot. When you do not have.
Click to expand...
Click to collapse
Wait? I thought you said I could get it back to warrant-able state in your last post? Did I misunderstand what you said?
Either way, is there a way to just get rid of CWM?
If I can do that, then the *ONLY* way for them to tell I did anything would be the hboot version at the top, correct?
I would be willing to try going to multiple T-Mobile stores and hoping to find someone that didn't know about hboot versions.
So as long as I can get rid of CWM, I will be confident enough to go to multiple T-Mobile stores in order to TRY to get a replacement.
Is there a way to get rid of CWM on a bricked phone?

Paul22000 said:
Wait? I thought you said I could get it back to warrant-able state in your last post? Did I misunderstand what you said?
Either way, is there a way to just get rid of CWM?
If I can do that, then the *ONLY* way for them to tell I did anything would be the hboot version at the top, correct?
I would be willing to try going to multiple T-Mobile stores and hoping to find someone that didn't know about hboot versions.
So as long as I can get rid of CWM, I will be confident enough to go to multiple T-Mobile stores in order to TRY to get a replacement.
Is there a way to get rid of CWM on a bricked phone?
Click to expand...
Click to collapse
i did say to get it to a warrant-able state you need ADB up and running. But there lies a problem when, and i mentioned, it will not get the phone working again.
you need two things 1) a stock recovery image 2) to flash the stock .86 hBoot.
If you have the engineering hBoot, .85 you can flash the stock recovery image. Just has you would flash clockwork via hBoot. but to get back to the stock .86 hBoot you need to have the phone up and running. Which you cannot do at this point. You are correct the only way they would tell if it's been tampered with is the .85.xxxxx hBoot version at the top of the screen.
If you have the .85 hBoot you could try flashing the stock recovery image to the phone and see if that will overwrite CWM.

neidlinger said:
i did say to get it to a warrant-able state you need ADB up and running. But there lies a problem when, and i mentioned, it will not get the phone working again.
you need two things 1) a stock recovery image 2) to flash the stock .86 hBoot.
If you have the engineering hBoot, .85 you can flash the stock recovery image. Just has you would flash clockwork via hBoot. but to get back to the stock .86 hBoot you need to have the phone up and running. Which you cannot do at this point. You are correct the only way they would tell if it's been tampered with is the .85.xxxxx hBoot version at the top of the screen.
If you have the .85 hBoot you could try flashing the stock recovery image to the phone and see if that will overwrite CWM.
Click to expand...
Click to collapse
A) So just to make absolutely sure. Even with ADB, there's 0% chance of ever getting this phone booting into Android again, correct?
B) If so, well replacement is the only opton. So from the pictures above in post #12, I have 0.85, yes?
C) So I just need to flash the stock recovery image from CWM to overwrite CWM?
D) If all three are correct, then which file do I need to flash? Is is one of the two files listed here? http://forum.xda-developers.com/showthread.php?t=843289

Paul22000 said:
A) So just to make absolutely sure. Even with ADB, there's 0% chance of ever getting this phone booting into Android again, correct?
B) If so, well replacement is the only opton. So from the pictures above in post #12, I have 0.85, yes?
C) So I just need to flash the stock recovery image from CWM to overwrite CWM?
D) If all three are correct, then which file do I need to flash? Is is one of the two files listed here? http://forum.xda-developers.com/showthread.php?t=843289
Click to expand...
Click to collapse
a) with adb up and running you can flash the stock recovery image, but not the old school hBoot
b) i am at work and WebSense blocks alot of images.
c) yes
d) depends on if you had the pre or post OTA recovery image.

[Q] Please help with bricked phone

I've spent quite a while tonight FINALLY getting this MyTouch 4g (Glacier) to root and now I'm stuck in a bind.
Everything seemed to be going well and I got the Cyanogenmod 7 flashed onto the phone via Clockwork ROM Manager. Then the first time I rebooted it got to the Android logo with the spinning arrow and went into a constant loop. After about 20 minutes of this I pulled the battery and tried to restore the phone via the recovery image I created with clockwork. Here is the current status of the phone:
1. CAN get into HBOOT and HBOOT USB (but I dont think ADB can see it, or at least I haven't been able to get it to)
2. CANNOT get into recovery, phone just reboots itself to the red exclamation
3. PD15IMG.zip tries to restore the phone but fails.
What can I do to get the phone back into some sort of usable condition. I dont care where, I can start over as long as I have something to work with.

sdavidson0316 said:
I've spent quite a while tonight FINALLY getting this MyTouch 4g (Glacier) to root and now I'm stuck in a bind.
Everything seemed to be going well and I got the Cyanogenmod 7 flashed onto the phone via Clockwork ROM Manager. Then the first time I rebooted it got to the Android logo with the spinning arrow and went into a constant loop. After about 20 minutes of this I pulled the battery and tried to restore the phone via the recovery image I created with clockwork. Here is the current status of the phone:
1. CAN get into HBOOT and HBOOT USB (but I dont think ADB can see it, or at least I haven't been able to get it to)
2. CANNOT get into recovery, phone just reboots itself to the red exclamation
3. PD15IMG.zip tries to restore the phone but fails.
What can I do to get the phone back into some sort of usable condition. I dont care where, I can start over as long as I have something to work with.
Click to expand...
Click to collapse
does bootloader show Fail-PU when flashing PD15IMG.zip?

saranhai said:
does bootloader show Fail-PU when flashing PD15IMG.zip?
Click to expand...
Click to collapse
Nope, looks to me like the equivalent of what you're asking is that it says "Fail UZ"
I've attached a few screen shots for reference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sdavidson0316 said:
Nope, looks to me like the equivalent of what you're asking is that it says "Fail UZ"
I've attached a few screen shots for reference.
Click to expand...
Click to collapse
It failed to unzip the update. Try redownloading the pd15img. This time verify the MD5SUM and try it again.

ALrighty.....this is my st00pid face. I guess in my lack of sleep last night I forgot to check the MD5SUM.
That worked....now let's see if I can break it again!!

sdavidson0316 said:
ALrighty.....this is my st00pid face. I guess in my lack of sleep last night I forgot to check the MD5SUM.
That worked....now let's see if I can break it again!!
Click to expand...
Click to collapse
Cool Glad it worked for you.

New question, essentially the same topic:
This whole thing started because I tried to flash CyanogenMod 7 onto the phone and it messed up. The phone reboots into Cyanogen and the little android on the skateboard with the arrow just goes into a repeating cycle. It will come on for 10ish seconds at a time and then just cycle back and do the same thing. I've let it go for >20 minutes and nothing changes.
Does anyone have any suggestions on how to get this ROM working? It took me so long to get it rooted with S-off that I'll be darned if I'm stopping now!
Thanks in advance!

sdavidson0316 said:
New question, essentially the same topic:
This whole thing started because I tried to flash CyanogenMod 7 onto the phone and it messed up. The phone reboots into Cyanogen and the little android on the skateboard with the arrow just goes into a repeating cycle. It will come on for 10ish seconds at a time and then just cycle back and do the same thing. I've let it go for >20 minutes and nothing changes.
Does anyone have any suggestions on how to get this ROM working? It took me so long to get it rooted with S-off that I'll be darned if I'm stopping now!
Thanks in advance!
Click to expand...
Click to collapse
Verify the MD5SUM of the ROM as well. You may of gotten a bad download.
What i personally do when i download and install a new OS is
Download OS to computer
push the OS to the SD card
verify the MD5SUM
reboot into recovery
nandroid backup
factory reset
flash new OS
flash g/apps (if needed)
reboot system
to check the MD5SUM while it's on the SDcard just use the line command from either the terminal emulator or CMD prompt.
Code:
# md5sum /mnt/sdcard/<file_name>.extension

neidlinger said:
Verify the MD5SUM of the ROM as well. You may of gotten a bad download.
What i personally do when i download and install a new OS is
Download OS to computer
push the OS to the SD card
verify the MD5SUM
reboot into recovery
nandroid backup
factory reset
flash new OS
flash g/apps (if needed)
reboot system
to check the MD5SUM while it's on the SDcard just use the line command from either the terminal emulator or CMD prompt.
Code:
# md5sum /mnt/sdcard/<file_name>.extension
Click to expand...
Click to collapse
+1
You can also check the md5 sum when its on the SDcard using the free mand5 app from the market.
Sent from my HTC Glacier Sense 3.0 using xda premium

Thanks to everyone for helping out, I finally got it working last night when I had time to sit back down with it.
I was trying to use the ROM Manager version of the Cyanogen instructions and it ended up that that was the problem. I switched over to the recovery version based on your suggestions and it worked great.
Thanks again!

General feeling around here is that the only thing ROM Manager is good for is flashing ClockworkMod recovery. There are folks who won't even do that with it.
Sent from my HTC Glacier using XDA App

ROM manager ruined my recovery I had to completely re push recovery thru adb
Sent from my PG86100 using xda premium

[Discontinued]

Download and Install LG United Mobile Driver
Download and Install LG Mobile Support Tool​
Boot your phone into download mode:
Put your G2 into download mode by switching it off, hold the Volume up button and insert the usb cable into the phone; wait for the drivers to finish loading if doing it for the first time.​
Start the LG Mobile Support Tool and click on Options -> Upgrade Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should now download the firmware (about 2gb) and flash it - this may take some time.
This is needed if you stuck in a bootloop after the flash is done:
Factory reset (this wipe your data and sdcard):
1. Turn the phone off.
2. Press and hold the Power and Volume down button.
3. When the LG logo pops up let go for a second and press the combo again.
4. You'll be prompted to press the Power button 3 times to wipe the device.​

I would hate to have to use this, but wow what a good find. Thanks for contributing.
Sent from my LG-D800 using Tapatalk 4

Just got my g2. About to root install twrp etc. This is exactly what I was looking for. Thanks for posting.
Sent from my LG-D801 using XDA Premium 4 mobile app

For anyone putting in dashes with the imei number, dont it wont work with em.

Just wanted to notify that this method made my 32gb D802 a 16 gb one!

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.

x714x said:
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.
Click to expand...
Click to collapse
I know it does'nt wipe data, but it reflashes recovery, and in my case something went wrong. But Lg DO sell D802 as a 16 gb model!

Can anyone using this method please post results. Just wondering if there is more success with this method as opposed to the other method. Thanks.

Saved my bacon today!

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?

Noam23 said:
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?
Click to expand...
Click to collapse
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/

karstensson said:
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/
Click to expand...
Click to collapse
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?

Noam23 said:
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?
Click to expand...
Click to collapse
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.

karstensson said:
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.
Click to expand...
Click to collapse
Why should a password appear at that stage ???
If you went through all of the flash process successfully, booted successfully and only then did a factory reset (when you saw that password), I see no reason to blame the factory reset that you did. This is something to do with the flash process. Maybe this is kind of a punishment that LG unleash on those who use this process ? seriously, why on earth would anyone try to flash his LG2, if it wasn't to get rid of root ? I also don't understand how the password went away after you did hard-reset, since the device was "hard-reset" when you did that flash. You said that you re-flashed about 5 times, did that password appear after each of those 5 times ?

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
Same issue here.
I also got the question after I used the software to enter my encryptionkey. Wich I didnt have.
So I had to hardreset from the recoverymenu (volume down + pwr), then I suddenly had 10.77GB left instead of 26.77GB or something similar.
Annoys me pretty darn much at the time beeing!
I did use my IMEI, not my serialnumber and model. I'll try to use the serial and model this time around, and see if there are any differences at all in doing so.
And yes, it does say 32GB on the back. So we're not mistaken it for a 16GB-model
And it does say that the model is the 32GB when I check the hardware-info on the android itself.
Maybe this has something to do with me using the adbcommand for mounting storage incorrectly?
I thought however it would be reset when I used the LG Mobile Support Tool to hardreset everything though.

Will this work with the AT&T model D800?
Also does this remove all traces of root to the point where you get your warranty back?

what was the solution to this...

Does this work with the TMO versions?

The windows application keeps getting a Windows error and closing shortly after the process begins. Any tips?

I would prob stay away from this if i was anyone else....Because it must be messing people phones up and changing the storage capacity

VS980 TWRP bootloop after botched lollipop OTA while rooted like a dummy

So yeah. As the title says I had a rooted VS980 on 4.4.2 with some bloat removed and I accidently hit the wrong button when prompted for the upgrade, I was in a hurry. yes, I'm a moron, and yes, I know this is probably wasting someone's valuable time and I thoroughly apologize for my n00bishness
having said that, I have tried to go through various tuts but none of them seem to be working. yes, it's likely that I am simply doing it wrong, but whatever the case I am stuck with my phone in a bootloop always returning to the TWRP recovery. I believe that means it is soft bricked so I'm hoping this can be fixed fairly easily with the right direction and some patience for my ignorance. I can't seem to get it into download mode with turning it off, holding the volume+ button and plugging it in, it just goes to twrp. :'(
my hope is to get a rooted lollipop. if that is not possible then I would be fine with going back to stock or possibly even a custom rom if it's not too awfully complicated. honestly, I'm at a point where I'm beginning to accept that I probably shouldn't be screwing around with it too much and will likely bite the bullet and just keep my phone stock since there are really only a few minor irritants that make me want to root it.
any help is very much appreciated.

anybody? pretty please? any ideas at all?

Deviouz1 said:
anybody? pretty please? any ideas at all?
Click to expand...
Click to collapse
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well

a.perkins89 said:
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
Click to expand...
Click to collapse
actually, it doesn't look to be the same problem. i dont have download mode, but i do have recovery. it boots to twrp like a champ. what i think i really need is how to get the flash file VS98011A_01.zip on my phone via ADB Sideload, specifically when i cant get the drivers to work.
i've tried the following drivers:
LG_VZW_United_WHQL_v2.14.1.exe
LG_VZW_United_WHQL_v2.20.0.exe
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1_3.10.1.0
I may very well be mistaken about what needs to happen, i'm no expert, obviously, but from everything ive read any of those should have worked. i think if i can get the right flash on the phone i should be able to flash it via twrp no?

I"ll help
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200

Jaqueezzzy said:
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
awesome,thanks you, i'll try that!

Deviouz1 said:
awesome,thanks you, i'll try that!
Click to expand...
Click to collapse
Just so you know it talks about flashing a ROM, but just use the zip you need insted, because it's the same principal.

Step 9 Fails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i just happened to have a brand new data cable, tried again with same result so its not media related unless there is an issue with the plug itself, but it's charging and the Device manager shows the correct name ie VS980, it just has a yellow bang on it and i cant find a driver that changes that.
read some more and found others with the same issue apparently which led me to here: http://forum.xda-developers.com/showthread.php?t=2715408
which is where i found the "download mode restore" file you mentioned(i didnt see it in the thread you provided), but without the ability to get adb usb command to work i dont see how i can use it.
any ideas?

Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart

siggey said:
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
awesome, ty sir. i happened to have one of those laying around from when i cracked my screen on my old one and couldnt interact with the screen. took a while to find it buried but i have it and i have successfully been able to access a thumb drive. i think that might be all i need.
will report back though regardless.

ok, now i'm rrrrrEEAALLYY freakin confused...
successfully flashed (via the install section of twrp with usb otg thumbdrive mounted.)
xdabbeb_vs98028a_bootstack.zip
and
xdabbeb_vs982.5_1.1.0.zip
from
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
but when i reboot, it goes directly to twrp still.
wat? :'(

ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.

WOO-FREAKIN-HOOOO!!!
at the setup wizard now.

Deviouz1 said:
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
Click to expand...
Click to collapse
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.

thecadman99 said:
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
Click to expand...
Click to collapse
sweet, i'm glad someone else found it useful.

Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....

thecadman99 said:
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
Click to expand...
Click to collapse
Is your baseband recognized by chance?

Deviouz1 said:
Is your baseband recognized by chance?
Click to expand...
Click to collapse
Nope... its UNKNOWN
And I have not download mode
And I have not cdc serial showing up when connected
And TWRP and Root are gone
I'm starting a new thread for help- I've been working on this for 2 days lol.
Thanks for the reply!

Bootloop until the battery is dead (unable to boot to fastboot)

Hmm, i was using my Nexus 6p as usual and i don't have any problem with it. One day i woke up because of my alarm rings, i closed the spotify and unplug the headphone. The phone automatically rebooted and does not stop at all until the battery dead. I was thinking about it is bootlooping so i decided to get into recovery and wipe the cache. However, i can't even get into bootloader because when i successful went into bootloader, within 1 second, the device automatically reboot again and start bootlooping. I don't have any chances to boot into recovery. I tried to flash new image but unfortunately does not work.
I asked my friend who is doing phone repair to check whether it is power button stuck or other possible problems to make this thing happen. The results are power button and battery working fine and does not broken or not functioning. I was about to send my Nexus 6p to Huawei Service Center since there is no Google Service Center in my country. Before that, i want to know if anyone has this kind of problem? I would like to fix this myself if possible and if there is any solution for it. Thanks and sorry for my bad english. I have provided a video sample about the situation of my Nexus 6p to show if anyone of you don't know what kind of problem i am facing right now. Please also ignore the sound of my video because of my bad shooting skill.
My Nexus 6p currently on
Android 8.1.0 Beta 1
Some photo sample of how i tried to reflash new image to my Nexus 6p in bootloader below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video sample of my Nexus 6p situation (seems like the video cannot be played in the post, i will give the link instead. Sorry about that)
https://www.youtube.com/watch?v=uiy-ToOPrP0&

https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330

Exodusche said:
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
Click to expand...
Click to collapse
Thanks for your helping. I have a question about that, the post is trying to said that i should flash the 4core patched boot image file right?

yaohui said:
Thanks for your helping. I have a question about that, the post is trying to said that i should flash the 4core patched boot image file right?
Click to expand...
Click to collapse
Yes you need your bootloader unlocked and then fastboot the 4corefix.img for 8.1. I understand you can't keep your phone on long enough to use fastboot. So you will have to sort that out first. Only thing I remember someone being able to do was heating up the back of the phone with hairdryer. That way it would stay on long enough to preform. There might be more ideas how you will have to read through the article.

Exodusche said:
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
Click to expand...
Click to collapse
Exodusche said:
Yes you need your bootloader unlocked and then fastboot the 4corefix.img for 8.1. I understand you can't keep your phone on long enough to use fastboot. So you will have to sort that out first. Only thing I remember someone being able to do was heating up the back of the phone with hairdryer. That way it would stay on long enough to preform. There might be more ideas how you will have to read through the article.
Click to expand...
Click to collapse
Thanks, Appreciated. I will try it.

yaohui said:
Thanks, Appreciated. I will try it.
Click to expand...
Click to collapse
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .

Exodusche said:
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .
Click to expand...
Click to collapse
My bootloader is unlocked at first actually, so now i'm going to try to flash the modified 4core boot.img.

Exodusche said:
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .
Click to expand...
Click to collapse
no luck
am i doing the right thing? I did not heat up my Nexus 6p yet because 2am now here. If really need the hairdryer to warm up, i will try it later.

yaohui said:
no luck
am i doing the right thing? I did not heat up my Nexus 6p yet because 2am now here. If really need the hairdryer to warm up, i will try it later.
Click to expand...
Click to collapse
Ok my bad I didn't read correctly your not on latest 8.1 December your on 8.1 beta 1?
Maybe need a different image. Might be easier to first flash latest stable 8.1 but go though the image list and see if yours is there.

Exodusche said:
Ok my bad I didn't read correctly your not on latest 8.1 December your on 8.1 beta 1?
Maybe need a different image. Might be easier to first flash latest stable 8.1 but go though the image list and see if yours is there.
Click to expand...
Click to collapse
Actually, I did perform flash using all of the modified boot.img and all the result are same. I will try to look into it more.

yaohui said:
Actually, I did perform flash using all of the modified boot.img and all the result are same. I will try to look into it more.
Click to expand...
Click to collapse
See if you can flash the latest 8.1 Stable then go back and flash the first image we tried.

Exodusche said:
See if you can flash the latest 8.1 Stable then go back and flash the first image we tried.
Click to expand...
Click to collapse
it seems like my Nexus 6p remain the same situation after warm up the back of the phone using hairdryer.

yaohui said:
it seems like my Nexus 6p remain the same situation after warm up the back of the phone using hairdryer.
Click to expand...
Click to collapse
Sorry to here that it was a shot in the dark. Are you able to flash stock image through fastboot?

Exodusche said:
Sorry to here that it was a shot in the dark. Are you able to flash stock image through fastboot?
Click to expand...
Click to collapse
I don't think i am able to do that since my Nexus 6p reboot automatically even in bootloader

Besides, i realise one thing that when my phone is on bootlooping, normally you will need to hold power button + volume up + volume down to get into bootloader. but in my case i don't need to. During bootloop, i just need to hold volume down and it will go through bootloader. but the result is still same as previous which is bootlooping still.

yaohui said:
Besides, i realise one thing that when my phone is on bootlooping, normally you will need to hold power button + volume up + volume down to get into bootloader. but in my case i don't need to. During bootloop, i just need to hold volume down and it will go through bootloader. but the result is still same as previous which is bootlooping still.
Click to expand...
Click to collapse
I think your motherboard is fried. The people at repair shop unable to do anything? If you go to the service centre, they'll ask you to replace the motherboard. How old is the phone?

tropical cactus said:
I think your motherboard is fried. The people at repair shop unable to do anything? If you go to the service centre, they'll ask you to replace the motherboard. How old is the phone?
Click to expand...
Click to collapse
Yup, the guy just told me the same thing that i might have to change the motherboard. He asked me to send to the official service centre is the best solution. My phone is around 2 years. I just posted here to see if anyone is facing this kind of problem and looking for solution to fix myself. Since the motherboard is fried, i think i can't do anything for it unless i change the motherboard, so i think i will send to service centre later. Thanks for your reply and @Exodusche your help.