So hi. Had an issue with my GNex where I had to replace the charging port (easy) and I managed to tear the volume button cables in the process. Wasn't a huge issue until I had the clever idea of booting into recovery.
Currently using ClockworkMod Recovery 6.0.2.3, and because I'm not smart it's not the touch version. All I can do is select "reboot system now" and choose "no" to fixing root, because I can't navigate without the volume keys. Choosing to restart just brings me back to recovery, so I can't get back into the OS to flash the touch version (would I even be able to without the volume keys?).
Is there any way I can flash a touch recovery on the device without being able to use the volume keys? I can't boot it into Odin mode here.
(I suppose I could bite the bullet and get a soldering iron... I've got the replacement volume key, I'm just **** at small parts, obviously)
Got it into Fastboot mode with ADB, but for whatever reason the device driver that works while it's in Recovery mode does not work in Fastboot mode, so Fastboot isn't detecting it and I can't load the new recovery.
Baby steps.
For whatever reason Windows wasn't installing the ADB drivers properly so I had to do it manually? It even told me the driver I'd selected wasn't recommended, but it went ahead with it anyways and now both ADB and Fastboot work.
It's been so long since this has worked it looks like it's got a Jellybean AOKP ROM on it. Currently initiating swagger, though it's taking a while.
Aaand looks like it's a version of AOKP that just sits there loading eternally. Think I ran into this before, which is how I ended up in this situation to begin with. Must have found a way to get into recovery from here.
So... again, still not working, but for a different reason this time at least.
I really should just get a soldering iron.
If the connection to the motherboard isn't broke and its just the buttons that are broke, you can try using a paper clip to make contact with it and short out the connection which tells the phone the button is pressed its what i did when my power button went out, its a pain to do and get right but it might be worth is i wish i had pictures to show you what i'm talking about so i hope you understand! but if all else fails ebay is your best friend for new parts!
Dudeyourdead said:
If the connection to the motherboard isn't broke and its just the buttons that are broke, you can try using a paper clip to make contact with it and short out the connection which tells the phone the button is pressed its what i did when my power button went out, its a pain to do and get right but it might be worth is i wish i had pictures to show you what i'm talking about so i hope you understand! but if all else fails ebay is your best friend for new parts!
Click to expand...
Click to collapse
So, it's the ribbon cable connecting the buttons to the motherboard that's been damaged. I have a replacement, but I am not great with soldering and haven't tried it yet.
In the meantime, I bought a jig on ebay, and with that I've got it back into Odin mode. I'm absolute **** at retaining information/skills though and can't for the life of me remember how to get ADB to detect the damn thing once it's in Odin mode.
One thing I did just remember is that the USB connection on this phone is deep, so a few of the cables I have don't go in far enough, which causes complications.
Odin detects the phone, Heimdall detects the phone, Kies detects the phone (and tells me it's not supported). I just can't get ADB or Fastboot to detect the phone.
I've tried uninstalling and reinstalling drivers, I've tried swapping USB ports, I've tried different cables, I know this works because I've had it working before.
This phone is going to drive me to drink.
Sweet buttery gonads, I've got it booting into stock Android (no ADB, but Odin still working? Alright, there's a workaround).
I wish I still had that Moto G, it never had these problems...
So much luck using the Nexus Root Toolkit, and GAPPS/CWM Recovery Touch by Koush, I appear to have a functioning Galaxy Nexus running CM12.1? It's still verifying/optimizing apps, and that's where my Note 8.0 ran into trouble, so I suppose only time will tell.
22 of 91 apps optimized.
TL;DR for what I did:
I bought a jig on ebay. $1.50, free shipping, can't go wrong. It plugs into the bottom of the phone (with the power off) and puts the phone in Odin/download mode.
After getting fed up with trying to get ADB/Fastboot working on my desktop (it worked once, can't get it to now, no idea why) I tried it on my laptop. Tracked down a Nexus Root Toolkit (from Wugfresh) which automated a lot of the process, and had a good walkthrough for driver installation. Took three driver wipe/reinstalls on the laptop before it took.
Also the usb port (this being the one I replaced) is broken again, so I have to hold the USB cable at an upward angle for ADB/Fastboot to detect the phone at all. I just rested the cable on a screwdriver next to the phone and that did the trick. No jiggling at all.
The nice thing about the Toolkit is that it automates installation and does all the recovery stuff itself, which bypasses the lack of volume keys entirely. It flashed an up to date TWRP recovery, not sure if it flashed a touch one since I can't boot into recovery mode without the toolkit/ADB/Fastboot anyways.
The phone is still on it's last legs, but I've got CM12.1 installed now, as well as the Blackberry keyboard from the Priv, which was the whole point of digging the GNex out in the first place.
Links:
Nexus Root Toolkit:
http://www.wugfresh.com/nrt/
Glad to Hear! in all fairness i completely restored my Gnex but buying an broke one with functioning part someone sold it bricked for $14.67 on eBay, But if you bought the whole power button flex cable then its just a matter of opening up and snapping it down no soldering required i promise just push till you hear a click!
Dudeyourdead said:
Glad to Hear! in all fairness i completely restored my Gnex but buying an broke one with functioning part someone sold it bricked for $14.67 on eBay, But if you bought the whole power button flex cable then its just a matter of opening up and snapping it down no soldering required i promise just push till you hear a click!
Click to expand...
Click to collapse
Power button's fine, it's the volume keys that are damaged. I've got a bad history with translucent orange ribbon cables.
Related
Hi all,
I desperate need help. After an unsuccessful radio flash, my Desire won't even turn on. No response from any buttons or lights. Here's how it happened:
I'm relatively new to Android. I recently bought a Desire, to replace my Touch HD, which has seen about 25 different WM ROMs, over it's life.
I successfully rooted my Desire and had tried a few ROMs. I was sitting on the MoDaCo Custom ROM r17, which was all customised and running perfectly. I'd even used ADB to successfully update my wifi config to connect to my company LEAP-authenticated network.
I decided to flash the latest radio (32.37.00.32U_4.06.00.16_2), from this thread:
http://forum.xda-developers.com/showthread.php?t=687464
I entered Recovery using 'Fake-Flash';
I started flashing the radio image;
All the good messages were scrolling down the screen;
I kept one eye on the phone while I worked on my laptop;
I saw a message saying something to the effect of "Finished installing radio..." (sorry, I don't remember the exact wording);
The blue recovery menu had returned, with 'reboot device' as the default selection;
As I clicked the trackball, I saw another message appear under the 'finished' messages, which said "Writing rad " I guess it didn't have time to print the whole message, when I selected reboot.
The screen went blank then a graphic appeared in the middle (where the recovery exclamation mark and triangle usually appear), of a software box with a curved yellow arrow over it and the android icon peeking out from behind it. I left it for a while (already had that sinking feeling) then pressed the power button. It switched off and stayed there.
Since then, nothing that I've tried has received any response. Various combination's of button pushes, USB connection, removed SIM, SD and battery...nothing, not even an LED.
I've searched and haven't been able to find any solutions to this particular situation. Can anyone help, or am I totally bricked?
Regards, PF.
The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?
socktug said:
The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?
Click to expand...
Click to collapse
No question is silly under this circumstance!
Yes. I'd just taken it off overnight charge. 100%. If I plug the USB cable in now, there is no response from the LED.
Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty
socktug said:
Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty
Click to expand...
Click to collapse
ok. The charger has been plugged in for 35 minutes and still no response.
Also don't want to sound patronizing, but have you taken the battery out and turned on with the back button helld?
Ignore me, just reread your original post.
the procedure u said sounds rite, thats whats ment to happen, when you flash a radio, only other thing that comes to mind is, sure the radio u flashed was for the gsm desire?
so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.
cgrec92 said:
so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.
Click to expand...
Click to collapse
Right first time. It won't turn on at all. It doesn't react in any way to any of the button combinations I'm aware of from rooting and flashing it. Nothing happens at all.
I live in an HTC household, so I've tried a number of chargers and cables, including the PC's USB port. I haven't tried another battery...but the incumbent battery was holdng a good charge and was 100% at the time. What's more, I remember that the phone can run on the charger without the battery.
Not surprisingly, adb devices shows no connected devices.
I think everyone is right, it's back to HTC. I *hope* you're right that they cover it under warranty. I'm going on the weekend, so I'll let you all know the result.
Thanks to all for your help.
I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck
Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.
peewster said:
Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.
Click to expand...
Click to collapse
In the usb brick situation you can still charge. This isn't it!
socktug said:
In the usb brick situation you can still charge. This isn't it!
Click to expand...
Click to collapse
Ok i didn't know that.
If the phone doesn't turn on at all, you can maybe try sending it back to the shop for replacement. Chances are, they won't be able to know what happened, so you can pretend it just stopped working.
If it gets back to HTC, they probably won't bother to figure out what's wrong with the phone and just give you a replacement. Otherwise, they'll just send you the phone back and you won't have lost much (maybe postage costs?).
ash1684 said:
I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck
Click to expand...
Click to collapse
Thanks for the suggestion. I left the battery out overnight. Then tried to activate it (all the usual button combos) with:
Battery out, USB cable plugged in;
Battery in, USB unplugged;
Battery in, USB in.
I scoured the 'net for anything on protection mode for the Desire...no luck. If there is one, it hasn't been posted yet.
I would just act stupid and try to return it under warranty!
I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.
Umbrella Corp. said:
I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.
Click to expand...
Click to collapse
Yes, if it's totally bricked then just send it back to HTC and they will change it with no problems just same as acer done with my Liquid
All's well that ends well
Good news...
The HTC service centre were kind enough to replace my 'faulty' handset.
Re-flashed with r19 and radio updated (patiently) successfully.
Thanks all for your support.
Nice one. Glad it worked out for you
Sorry this is a long one. Phone is a Verizon Galaxy Nexus about five months old.
Using Galaxy Nexus Root Toolkit v.1.3 I managed to get the phone unlocked and (I think) install clockwork mod but when attempting to flash to root I got as far as "install from zip file . . .' but the next option "select zip file . . ." leads to a either an icon of a hat (which I presume is clockwork icon?) or a picture of an android with his belly open and an exclamation mark in a red triangle. I can no longer get to this point to confirm exactly which. Now when attempting to get to recovery mode I get into fastboot but after selecting "recovery mode" I always get the android with his belly open and a red exclamation mark and can never get to any menu.
Now all of a sudden possibly as a result of this process or else by coincidence usb on the phone appears to be either dead or sub-functional. This may also be why I could never flash to root, (bad USB led to corrupt or missing zip?). Windows does not detect any usb connection from phone, not even a failed one (no sound, no error message) but I have confirmed it's not the PC's error as other usb connections are working.
Also, confirming some sort of USB issue, the phone does not show the charging icon when I plug it into a charger UNLESS the phone is powered off, when I do see the charging animation. To make matters even more confusing despite not seeing the charging icon or the battery manager reporting that the battery is charging the phone does appear to be charging even while powered on but this was only after one night and I'm not quite 100 % certain it charged or that it charged at the usual speed. (thankfully I have an extra, separate, standalone battery charger).
I have re flashed to factory from the " backup and reset" menu inside Android and this did not help.
Simple question: any way to RELOCK phone without USB so I can at least make the phone appear un-tampered with so I can get a warranty service or replacement to fix the apparent usb problem?
bigger question: wtf is going on, is the usb issue perhaps a software problem? and is there anyway to fix the failed flashing process by perhaps transferring a zip file by some other means than usb to the proper directory?
Thanks for anyone who bothered to read this far.
Note: the actual sequence of events is a bit more complicated and now foggy in my memory but this I hope is close enough. If anyone wants more info I'll try to supply it. Let me just say that there were issues from the start of this process. merely unlocking the phone the first time had bricked my boot, all I saw was "Google" and a picture of an un-locked lock, getting into fastboot and then choosing recovery mode led to the picture of the belly up android but after several attempts I finally got past that one time and elected to flash back to stock from recovery menu. This was all before trying to root.
No to first question.
As for second question, pull the battery for about 10 minutes and see if it fixes your USB issue. Don't connect it to a computer to test the charging issue, and instead an outlet.
adrynalyne said:
No to first question.
As for second question, pull the battery for about 10 minutes and see if it fixes your USB issue. Don't connect it to a computer to test the charging issue, and instead an outlet.
Click to expand...
Click to collapse
Trying now, will report back. I think I already tried this though. I should also tell you I have three different batteries and behavior is same for all of them.
I'm not thinking its the battery but something stuck in hardware. Hence the leave it out for 10 minutes.
Left battery out phone unplugged for almost twenty minutes... and still no luck.
oops, I see I was supposed to put this in the Q and A section, sorry, new here, should I start over there?
Could be a hardware issue with your usb connector. Try cleaning it out with a blast of compressed air or something. I just found out today that the USB ports on the GNex are weak and prone to maybe needing repair.
Good news is that the part only costs $6.00 on ebay - if you're a DIYer.
zuberio said:
Could be a hardware issue with your usb connector. Try cleaning it out with a blast of compressed air or something. I just found out today that the USB ports on the GNex are weak and prone to maybe needing repair.
Good news is that the part only costs $6.00 on ebay - if you're a DIYer.
Click to expand...
Click to collapse
That was it! I blew it out, and then I cleaned a bit with alcohol, and then when that didn't do it I pushed up (or down) on the cable while it was plugged in and suddenly it came to life. I was able to connect to PC and lock it back. Now at least I can attempt a warranty repair if I so decide.
I had gently pushed up and down on the cable before to try to make a good connection but never once did it connect - I feel like the cleaning must have been needed but apparently was not sufficient to fix it fully.. So I suppose something is still amiss with the connector - either it is damaged or askew or else still a bit dirty.
I'm happy to be back to full stock, maybe I'll root again another day after I sort out the USB issue.
Thanks everyone!
In the future, I'd recommend steering clear of "one-click" or "toolkit" root methods. Sure, they work, and gosh darn it they are easy... but when something goes wrong, you'll never know what's actually the problem. Get comfortable working with fastboot and adb; it will take you a long way with this device.
This should help get you started in the right direction.
So, I finally got my Ubuntu udev rules set up and got my Kindle communicating with adb and fastboot. I went through the rooting kindle 6.3 process and I only made it to
fastboot -i 0x1949 flash bootloader
fastboot -i 0x1949 flash recovery
this is from:
http://forum.xda-developers.com/showthread.php?t=1568340
adb sent them to the kf, but the next step it says is your kindle will now boot into twrp and flash firefirefire. Well mine didn't it just stayed on the Kindle Fire screen, no reboot. I left it alone for about 20 min, then I think I probably screwed up by holding the power button down. It took about 10 sec then it powered off. Now it won't power back up. I'm worried that now I have no fastboot and no recovery?? Anyway any advice? Or at this point do I try to get amazon to warranty?
What is the filename you flashed the bootloader with?
I downloaded all the links, and I renamed it to fire.zip, and i renamed the twrp to twrp.img, just so i didn't have to type out the entire filename.. Is that a mistake?
sometimes I get lucky and plug it into the normal wall charger and it will wake it up
You don't flash a .zip file directly to your bootloader. That's a hard lesson to learn your first time around. It's a fairly pretty simple fix but you're going to have to make a Linux LiveUSB and pull the back cover off.
http://www.pendrivelinux.com/
http://forum.xda-developers.com/showthread.php?t=1430038
soupmagnet said:
You don't flash a .zip file directly to your bootloader. That's a hard lesson to learn your first time around. It's a fairly pretty simple fix but you're going to have to make a Linux LiveUSB and pull the back cover off.
http://www.pendrivelinux.com/
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
So I finally decided not to send it back and to just fix it.. I actually already have a successful linux setup.. So I did the pull the cover, short the pin, and nothing still... I'm about ready to give up on this thing.. Any suggestions? Anybody know if I can exchange from Amazon still? I'm assuming not
Do You think maybe my battery drained? It has sat for a while.. I just plugged it in to the "kindle" charger.. I'll see what happens in a couple hours.. The terminal is looking like it is good to go.
tried again after being plugged in for a while, still nothing. *sigh
There are a few things that could be going on. Your battery could be dead. Even in that state the power could still be on draining your battery but in most cases it doesn't take much to flash a new bootloader.
Before you try the shorting trick, hold the power button for 20 seconds or more to make sure the power is completely off. In Linux, make sure you are running firekit as the root user. Shorting the pin can be kinda tricky. I've seen that it works best with a pair of sharp pointed tweezers or a safety pin to keep everything static while plugging the device in. Sometimes it just takes a little perseverance to get the timing right so keep working at it.
In the case that your battery is just too dead to do anything at all, you'll want to get a factory cable. The factory cable bypasses the battery and powers the device directly which would eliminate the need for a decent charge.
In either case, it's all just a matter of not giving up on it. I would say that 99% of the time, if everything is done correctly, the firekit will work.
Awesome, I am doing the usb setup with the firekit just to be safe.. Thanks for your help.
Same Here
I followed the same guide to the same step and had the same problem. I also let it sit for a while, nearly an hour and then I shut it down by holding the power button. I will let it sit on the charger this evening and see if it will boot later. Otherwise I may try to send it back to amazon. Their customer service has been pretty great in the past.
Anybody fix this problem yet? My KF is doing the same after following the same root process. Won't power up, won't respond in any way. :crying:
I haven't tried opening it up as I don't want to void the warranty. Would a factory cable work instead or should I not bother? TIA
Plug your charger into it and see if a bootlogo appears on the display. If it does not, then the odds are your bootloader is broken and the only way to fix that is to open up your case and use Firekit. A factory cable relies on the bootloader to put the device into fastboot mode, so it won't help you if your bootloader is broken.
Thanks kinfauns (and previous posters)!
I did finally decide to open it up and try the Firekit solution. I'm kind of shocked I got it to work, ha ha. Everything is right as rain now so thanks a million to all who suggested it here and on other threads!
FYI I used some guitar picks, a license, and a metal collar stay to open the case. A couple light marks on the very edge and a very slight gap now, but otherwise the case is fine. (Pretty sure no one but me will ever notice.) I used a piece of solder wire to short the pin, a stiff paper clip would probably have worked better though. KF kept sliding at plug-in so I set it against a medicine ball to hold it, lol. I got the trick to work on the second try. (Actually maybe the solder wire is better since flexibility made the connection easier to press firmly.)
Went here for instructions and pics on how to do the short trick: evilsoapbox[dot]com/?p=1444
Thanks again!
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
rewkim said:
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
Click to expand...
Click to collapse
Do you get the blue screen when attempting both recovery and download mode?
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
rewkim said:
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
Click to expand...
Click to collapse
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
I appreciate your help - thank you. For what it's worth, no - there was never any text on my blue screen, and I couldn't ever get it to get into Download Mode. Plugging it in to a computer did nothing except give me a blue screen, and the computer never recognized it as a device.
I ended up getting a replacement G3, so [for now] my troubles are over. Thanks, again, for your help.
(I guess this thread can be closed now.)
Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
rewkim said:
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
Click to expand...
Click to collapse
Glad you got it replaced!!
And a shame for your friend :/
In my case, it was practically hopeless, nothing seemed to work, eventually i had to have the motherboard replaced. It was clearly a damaged bootloader, yet, they repaired it under warranty! funny
I doubt you can damage a bootloader without root or stuff.
I wonder what would suddenly mess with the bootloader after months of no issues?
I'm having the same issue. Or rather I had the same issue but I was able to get it back to stock through all the various .tot methods and using download mode and everything. I had no issues so I rooted it again, installed the 35B firmware from xdabbeb, as well as his 46A so everything is still stock, and running the latest android update, but the phone is still rooted. In any case it has been working fine for almost a week. Today it shut itself off again and now only blue screen when I turn it on. It barely gets past the LG logo before it blue screens again. I can't enter download mode because while installing the device on the PC it blue screens and crashes in download mode.
So I'm not sure what the deal is. I have the extended insurance and warranty but if you pull the battery for a couple hours and put it back in it will boot past the LG screen and start the OS, but the boot loading screen shows "Android" instead of "Verizon" so they'll know it's a custom firmware and do nothing for me. If anyone has any ideas I'm open to them! I would love to revert back to stock but with it crashing in download mode I can't even do that.
try these things but g3 is crap phone
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
can you explain what outfit in you are talking about? i am facing the same problem,
Simaramis said:
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
Click to expand...
Click to collapse
..
ARYA3 said:
..
Click to expand...
Click to collapse
Sorry "outfit on ebay" means seller on ebay. Don't remember what their name was. With the g3 it's like this: bootloop is usually fixable with a new battery. If it loads with charger connected, then definitely try new battery. If blue screen without a number, it's likely faulty motherboard. It may still boot occasionally, after leaving batt out or putting in freezer (yes freezer). If it does boot then do a backup immediately but phone is likely in need of new motherboard.
http://forum.xda-developers.com/showpost.php?p=70264535&postcount=9
BSOD is not so BSOD as you might think. This is actually the default view of the screen controller. It just means.... well... basicly... you're ****ed....
Something in the hardware doesn't fire up as it should and it's usually the SoC.... or the so called processor. Heating and baking might help if the problem is with low temperature welding but again it might not. And even if it does... it will be totally temporary (most cases weeks) because of the rapid increase/decrease of the processor temperature and thus welding joints... I'm basically in the same situation right now with the same phone... he fought well as it is 2014 phone after all but in the end it died heroically.... ;(
Hi dear friends, I have a little trouble with my Xperia, because after root the phone don't take charge anymore, and the PC doesn't recognize the phone, the only way to charge the phone, it's putting in bootloader mode, and the PC in bootloader mode It does not recognize it either, the person what I buy the phone says:
"my friend had sent it to Sony who replaced the USB Connector, as they thought maybe that could be the culprit. But obviously it seemed to be more of a software issue as the phone charges in fastboot or recovery mode, so it didn't fix it. Looking at it, they either didn't set the backplate correctly or a little bit off, or they didn't put enough adhesive. It's not an issue really, as all it takes is removing the backplate and resetting it back onto the phone or putting a little more adhesive. Or the phone is normally like this, I'm not entirely sure. But it's a fixable issue if you just remove the backplate and put it back on correctly.
I'm not entirely sure, I believe that it did take the charge before the rooting. I purchased the phone from a friend who knows nothing about repairing phones who rooted the phone and then it would not take the charge anymore. I bought it from him to fix it myself, but I just don't have the time any time soon to repair it hence why I'm selling it.
It only takes a charge when it's in fast boot or the recovery mode currently and it sometimes boots into TWRP Recovery Menu randomly and keeps on doing that, so the only way I figured to bypass that is to hold on the volume up button when turning on the phone until it shows powered by android (when it does the bootloop into twrp). I believe it is the software that is the issue and I'm pretty sure if a stock rom can be flashed onto it, then it'll be good as when you plug in a usb cable normally, it does recognize it for about a second or two, but then it cuts off.
So technically the phone does work with some work arounds, but I sold it as not working or for parts as technically the phone isn't functioning normally as well and has a few issues that can be annoying to the common person."
So This said the person that I bought the phone, and I don't know what do you think about this, If anyone knows what happened please let me know.