I appear to have acheived an error that had previously been documented on LG G3's, but it somehow happened to me now. When I was using my phone, at first the phone just kind of froze. I figured it was just a minor crash, so I took out the battery, waited a bit, then put it back in. I let it charge a little bit, and the LG and Verizon startup screens came up just fine. I let it charge for about an hour after that, expecting it to be fine.
Lo and behold, it was, in fact a kernel crash. I then attempted to follow directions, and pressed the down volume button. The screen turned off. The phone hasn't turned on since.
Can any veterans help me with this issue? It would seem I'm one of the first to have it, at least on this phone.
MisterEm said:
I appear to have acheived an error that had previously been documented on LG G3's, but it somehow happened to me now. When I was using my phone, at first the phone just kind of froze. I figured it was just a minor crash, so I took out the battery, waited a bit, then put it back in. I let it charge a little bit, and the LG and Verizon startup screens came up just fine. I let it charge for about an hour after that, expecting it to be fine.
Lo and behold, it was, in fact a kernel crash. I then attempted to follow directions, and pressed the down volume button. The screen turned off. The phone hasn't turned on since.
Can any veterans help me with this issue? It would seem I'm one of the first to have it, at least on this phone.
Click to expand...
Click to collapse
Do you recognize the drivers? Do not enter in any way ?, to use lgup, lgbringe or lg flash tool.
Related
Hi everyone, I'm new to this forum (first post), I've owned my Continuum for a few months now happily with no problems. I actually love the phone! But recently I ran into a pretty big problem...
Let me give you a little background on my phone first, I have used SuperOneClick on it, to grant super user permissions, I've used the program to grant me access to the phone tethering apps that are out (currently using Open Garden), and the AdFree app in the market. I havn't used anything else in regards to 'hacking' my phone so I'm a bit confused as to why I'm getting trouble.
Anyways here's my problem, lol! Well the other day I turned off my phone and tried turning it back on and I would get a grey battery with the spinning disk, and it wouldn't turn on :\! I tried holding all the buttons, for over 10 seconds, no avail. It still turned on to the battery and nothing. I tried taking the battery out for a whiiiile and nothing. Eventually I plugged in my phone to the wall and it magically worked. Actually that's the only way I've been able to get my phone to turn on lately. It works fine once it's on but every time I turn it off the same thing happens .
So that's truly why I'm here... Is my phone 'bricked', or are these some symptoms of being 'bricked'? Are there any fixxes I can go about taking to you know...fix the problem ?
Any help would be Greatly appreciated,
Thanks everyone,
-Matt
Oops, I forgot to mention that my phone has been acting strange sometimes in the sense that I plug it into the wall and the 'Mass Storage/ Media player' option comes up, even though it's not plugged into the computer, just into the wall.
Pretty strange huh?
Anyways thanks again everyone who helps!!!
Can you try taking out the battery, then putting it back in...
Then hold down the volume down key as you power it back on?
I would try un-rooting and doing a factory reset... that should eliminate software issues... If you're still having issues then take it to VZW and let them give you a new one.
This is not "bricking"... If a phone is "bricked", it does nothing, absolutely nothing, and the only way to make it useful is to use it to build something.
Sure, right now it says "Downloading... Do not turn off Target!!!".
Thanks for letting me know it's not bricked, that's a little reassuring .
After a while I just took out the battery and stuck it back in and attempted to turn on the phone the usual way, and it turned on just fine. I'm guessing it's fixed and hopefully it won't do that again.
I had an alarm app give me an alarm last night but I was busy in another app and dismissed the alarm in a way that the sound was still going. The only thing I thought to do was to do a reboot of the phone. I gave it a few minutes and when I pulled it from my pocket I noticed that it had not rebooted. So I held the power button for a few seconds and waited for that vibrate then the "Custom" screen.
Nothing.
Held the power button for about 30 seconds.
Nothing.
Good battery, at least 75% before this happened. No sweat. I have a spare battery that I know is 100%. When I put that one in, the phone immediately did a vibrate and gave me the "Custom" screen. Then dead. Power button did nothing.
Pulled the battery and upon insertion, I got that vibrate again. But this time I held Volume+ and I get that tiny blue bootloader message at the top of the screen for a half a second. Then dead. Tried it again and this time did Volume-, this time I got download mode for half a second. Then dead.
Tried all this with power plugged in and get even less. Nothing.
Connected it to a PC (OEM cord straight into the motherboard) and got nothing. No charging LED, no sound from the PC upon plugging. Nothing new showed up in Device Manager.
Did I just do the "Low Effort Brick" method just by rebooting? I have had this thing for a few years, running CWM then TWRP. Several ROMs in the past, xposed, done it all and never once even had a boot loop. Now I have a brick because I rebooted a phone that had been VERY stable for weeks (on Dan's GPE ROM)?
I am not so concerned about the device, I actually ordered a LG G4 already. What I REALLY want is the autobackup of Tasker that is in the internal storage. I know I have a TiBu of everything on the microSD and a TWRP is on there too. But both are a few days old and I have made many changes to Tasker in the past few days. Tasker updates a backup every time you leave the app, so I know I have a very recent file in there. But how do I get it?
It's not bricked. The power button on some S4's are janky. Mine did the same thing for a while. You can try smacking the power button on the corner of a desk or something but otherwise either just keep pulling the battery and trying, try opening it and cleaning the switch, or try replacing the switch.
It's hardware issue with power button. I've got the same issue with my S4. The only solution is to replace the button.
Good advice. Found a few YouTube videos that are pretty close the issue that I have. I shall do some work on this this weekend. Thanks for taking the time to respond!
Hell yeah. Effin HELL YEA. Found a few YouTube walk through videos and got down to the switch. Using my ever-awesome Simpson 260, I was able to determine that the power switch was bad. I exercised it a few dozen times and then it went open. Roughed everything back together (without screws) and got a boot.
Immediately made a TiBu of everything. I will also make a TWRP as soon as that is done. Now I have to source a power switch. I should have no problem replacing the switch. I have a fantastic solder station at work and a 20X magnifier. This shall be my crutch until the LG G4 arrives.
Thanks again for the advice. Proof again that this is a real community.
Side note: I went to AT&T to get my old Vivid back into action to replace my S4. When I mentioned that the device was rooted, they replied with some statement that my "jailbreaking" the device is what caused the failure. I asked if she knew what rooting was, and she said "yeah...jailbreaking". I asked her if she knew what an "unlocked bootloader" was and she just glazed over, mouth open. When I told her that the device has been rooted for years with no problem, she insisted that the problem happened when I "jailbroke" it.
Iv done all i could find on here to do, please heop me get my phone to boot up!!!
Perhaps you should give a bit more info. What were you doing before you got this issue. Were you updating, are you*rooted, what version of firmware and whose network are you on.
Sorry, I am rooted and I am with att, it was Working fine until I tried to put xposedon it , after I did that it went into this boot loop. I used Odin to root and it rooted fine and still worked. Then I attempted to put xposedon and it messed it up. I'm on att and 6.0.1. Let me know if you need to know anything else. Thank you
Tried goin back to factory
I also tried using Odin to go back to the original firm ware, now maybe I did something wrong but I t failed everytime I did it. Any help would be appreciated
When the same thing happened to me, I was stuck/frozen on the AT&T logo screen, I left the phone to drain all the way down. When it finally drained the battery and shut down, I was able to plug in the phone to my computer and get back to the download screen. I let it charge up a little bit, then I Odin'd it back to stock (PI2). I have since been unable to root again, but the same thing happened before. It was a couple months before I tried rooting again. At that time, I was successful. Someone else may have a more elegant solution.
Radiotsar said:
When the same thing happened to me, I was stuck/frozen on the AT&T logo screen, I left the phone to drain all the way down. When it finally drained the battery and shut down, I was able to plug in the phone to my computer and get back to the download screen. I let it charge up a little bit, then I Odin'd it back to stock (PI2). I have since been unable to root again, but the same thing happened before. It was a couple months before I tried rooting again. At that time, I was successful. Someone else may have a more elegant solution.
Click to expand...
Click to collapse
Thank you SOOOOOOOOOOOOO much, turned out i did the same thing and I got my phone back.. Thank you so much for taking the time to tell me what u did... Hav a wonderful day~!!!!!
Radiotsar said:
When the same thing happened to me, I was stuck/frozen on the AT&T logo screen, I left the phone to drain all the way down. When it finally drained the battery and shut down, I was able to plug in the phone to my computer and get back to the download screen. I let it charge up a little bit, then I Odin'd it back to stock (PI2). I have since been unable to root again, but the same thing happened before. It was a couple months before I tried rooting again. At that time, I was successful. Someone else may have a more elegant solution.
Click to expand...
Click to collapse
Couldn't you just have tried a manual reboot? Just hold power and volume hardware keys for 12 seconds. Once it resets enter into download mode.
Sass86 said:
Couldn't you just have tried a manual reboot? Just hold power and volume hardware keys for 12 seconds. Once it resets enter into download mode.
Click to expand...
Click to collapse
Tried. All buttons were unresponsive.
Radiotsar said:
Tried. All buttons were unresponsive.
Click to expand...
Click to collapse
I don't believe that but I guess it may be possible and the hard restart buttons are power and volume down for about 10 seconds, seems like an eternity before it reboots lol.
Sent from my SAMSUNG-SM-G935A using XDA-Developers Legacy app
for whatever reason, i wasn't able to put this into the development thread (that's already growing incredibly long and tedious to dig through). but i felt this should be out there for people to see in the case that they have the same problem.
just got my sprint v20 this morning. and like a true XDA lurker, i went straight for the root.
process went fine up until the part where you run step3.bat while in fastboot mode.
phone rebooted. straight to LG screen. stayed there for an hour.
tried a few battery pulls, adb device checks (showed offline most of the time, but sometimes would show 'device'), adb reboot recovery (froze), pull battery to turn phone off hold volume down and plug cable in.
nothing was working, straight to LG screen every time
then i dug around and came across where some models of phones would have a way to reflash the stock firmware from a pc program. dug into that and had no luck (.kga file not available for sprint phones yet)
then what finally worked. unplug phone, turn it off (battery pull), hold volume down, hold power button, as soon as phone turns on let off power button and hold again.
boom, straight into twrp. was able to flash my rom and the SU binary from there.
static on first boot (as described) lasted a little while before i heard the standard first start voice over, where i was able to turn the screen off with the power button, and back on to get a fully working screen.
everything works great now. hope this information helps at least someone with that everpresent lump in their stomach when they think they've screwed up their phone. . maybe this can be moved to the right place if a mod deems necessary.
Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.
Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.
If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.
Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.
Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838