Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
possibly?
Did you just update and it got stuck at the booting up????
opeller said:
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
Click to expand...
Click to collapse
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
ChainFires Son said:
Did you just update and it got stuck at the booting up????
Click to expand...
Click to collapse
No, it did not occur after an update.
theminikiller said:
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
Click to expand...
Click to collapse
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
You can download factory images from here https://developers.google.com/android/nexus/images
opeller said:
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Click to expand...
Click to collapse
First we should check if you can boot into the bootloader at all. First turn the device off. Then hold down both the volume buttons and then press and hold the power key. Keep holding all the buttons until you see some different colored text. If that happens we should be able to install a factory image, if it still gets stuck on the Google logo I unfortunately don't have any more ideas.
Tried pressing both volume keys and power button. Google logo show for a second, then black for 2 second, thank flashing red notification light every 1/2 second until I let go of the buttons.
When I release the buttons, the phone goes back to charging battery screen.
I see people suggesting that the red light flashing means a battery problem, but the device keeps trying to boot up while it is not plugged to the charger, unlike what happened to them
Any Ideas why this is happening or what the red light means in this case?
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
harishmenace said:
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
Click to expand...
Click to collapse
Oh it was just volume down, not both. Heh, sorry.
Use the Nexus Root Toolkit (NRT), it's the easiest way to unlock, root, flash and manage your SuperUser needs!
http://www.wugfresh.com/nrt/
Not sure, but maybe?
You can try using the nexus root kit & unlock your bootloader and see if a factory reset can work. If it does you can always relock it again ☺..Flashing a factory image can work too also ...
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
I'm you can't get into the bootloader then I am unfortunately not aware of any way to help you. If you can't even get into the bootloader I think it is a high probability that it is a hardware problem.
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
opeller said:
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
Click to expand...
Click to collapse
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
Bus 001 Device 005: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode),
Click to expand...
Click to collapse
on windows (XP/Vista/7)
Qualcomm something QDL Mode or something like this on "device manager"
Click to expand...
Click to collapse
there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
x1123 said:
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
on windows (XP/Vista/7) there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
Click to expand...
Click to collapse
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
opeller said:
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
Click to expand...
Click to collapse
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
That sounds like the battery is completely empty. Put the device on charger over a night and try then to boot into the bootloader.
Once I had these symptoms (red light flashing) on my N4, it was enough to charge the battery for one hour. Then it booted properly. It's worth trying.
x1123 said:
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
Click to expand...
Click to collapse
How do I do that?
Related
Hello everyone,
I was doing an antutu test, and the phone just shut off yesterday. The battery was about 60% and then impossible to restart it. I then let it cool down 10mn then tried again with no luck. I plugged to the wall with original cable and plug and then a red flashing light was lit. I went to read online about this behaviour to find out it was (to some people say) due to battery being dead and had to wait to recharge a bit. I let charge for about 2h but there was no icon of battery charging on the screen. No need to mention that i have tried everything (holding power button for 60sec, holding volume down + power button etc etc) nothing was working. Then i read somewhere on this forum i had to press volume down + power THEN plug it into wall. I gave a try then it worked it went to recovery mode.... BUT BUT BUT once i tried to go to each option (start, restart bootloader, recovery mode), the phone was shutting down right away after the google image and again red flashing light... Bummer... So since it was getting into recovery mode i plugged it to pc and then followed the thread on how to reinstall stock rom etc etc. I followed steps but since i was already with a custom rom and kernel (PA+TRINITY) i used the toolboxkit because the command fastboot was not working in the command window. I did flashed the stock bootloader following what was supposed to be flashed first.Result.. Now no red flashing light, but nothing else either, no light, no power, no charging, no recovery mode, nothing... ANY ideas would be highly apreciated before i call google for an exchange.
Thanks to all for help.
What exactly do you plan on telling Google?
How did you flash only the bootloader??
Did you try the toolkit to reflash stock???
Sent from my Nexus 4 using Tapatalk 2
ptesmoke said:
What exactly do you plan on telling Google?
How did you flash only the bootloader??
Did you try the toolkit to reflash stock???
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Well since it does nothing else anymore i was going to tell them the truth besides the part it had another custom rom and kernel and i started the toolkit and i placed the 6 stock .img int he right folder then i started by flashing the bootloader and was waiting for reboot to flash the rest of the images like it is mentionned on the thread on this forum.
I used the toolkit to flash the bootloader but now the phone is dead completly. No light flashing, no battery icon, it is plugged on the wall and i get no power in it.. This is why im stuck before trying to flash stock rom and wipe all datas...
If you have any idea... i take it gladly!! but im not very used with toolkit so i dont seem to know how to wipe all datas besides flashing stok data image?? but the question is hos to get power back in phone now???
thank you for your precious help
anyone else???
i have exactly the same
check my thread
http://forum.xda-developers.com/showthread.php?t=2050811
i flashed custom rom and kernel
bat was at 98%, putted it into my pocket, one hour later i put it out, used to unlock the screen, bamm nothing anymore since then
i am not even managed to get it into recovery
no solution worked for me
i have no idea what happend to my device, ic alled google cause i really think its an hardware issue..
What's a "deas Nexus 4"? geez. learn to spell check.
Send me the device.
asawoszc said:
What's a "deas Nexus 4"? geez. learn to spell check.
Send me the device.
Click to expand...
Click to collapse
Learn that a new sentence always starts with a capital letter, smart ar*e.
Sent from my Galaxy Nexus using xda premium
Vangelis13 said:
Learn that a new sentence always starts with a capital letter, smart ar*e.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
^ LOL. At least my phone works. WOOOOOOO!
asawoszc said:
What's a "deas Nexus 4"? geez. learn to spell check.
Send me the device.
Click to expand...
Click to collapse
Geez do you speak french like i do speak english, even with a small typo mistake....l? And no i will not send you my phone wahahahahaha. Just tell me what to please...
Regards.
Same issue for me durinng atwrp backup,
I was able only to enter in recover pressing pwr+vol down and connecting a usb cable. I've restored the stock rom but nothing has worked. the red light still blinking.
L.
lupick said:
Same issue for me durinng atwrp backup,
I was able only to enter in recover pressing pwr+vol down and connecting a usb cable. I've restored the stock rom but nothing has worked. the red light still blinking.
L.
Click to expand...
Click to collapse
Hello
Phone totally dead, not even charging anymore. Google sending replacement
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
LG G2 Stuck @ 49%
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
try with x86
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
i had exact same issue that progress stucked on 49%. if you are using 64bit OS, try to flash it with 32bit(x86) OS
good luck
tinydynamite00 said:
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
Click to expand...
Click to collapse
still no luck
El Killer said:
still no luck
Click to expand...
Click to collapse
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
tinydynamite00 said:
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
Click to expand...
Click to collapse
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
El Killer said:
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
Click to expand...
Click to collapse
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Please READ CAREFULLY
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
Esteef said:
Okay, after 12+ hours of trying every method possible on XDA I finally resolved my issue. I will update the first post just incase any others care or fall into the same dilemma I was in.
The LG Mobile Support tool would not download the firmware and it would NOT ask me for my IMEI to download it either.
So my solution....
***
Installed LG Mobile Support Tool then Installed the LG Drivers. (FROM HERE http://forum.xda-developers.com/showthread.php?t=2471370
BEFORE I connected the phone to the computer. I opened the LG Mobile support tool clicked (Options on the top right).
When the dropped down opened, I clicked the (Upgrade Recovery) option. THEN, is when the prompt opened to ask me what my IMEI is.
Before I entered my IMEI, I connected my phone to the computer in download mode, then proceeded to enter my IMEI and hit OK.
This is when the LG Mobile Support tool SUCCESSFULLY downloaded the latest official LG firmware and installed it.
*** BE AWARE, with the phone connected to the PC, the prompt NEVER appeared to enter my IMEI.
*** But with the phone disconnected, the prompt came up every time. This might be the trick for some people.
*** with the IMEI prompt opened, I then connected the phone , entered the IMEI, then hit OK. BOOM HERPES....
Well I'll polish this up more later. I hope this works for every LG G2 Variant and not just the T-Mobile one (D801)
-Esteef
Click to expand...
Click to collapse
THIS WILL WIPE YOUR PHONE COMPLETELY...
tinydynamite00 said:
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Click to expand...
Click to collapse
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
El Killer said:
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
Click to expand...
Click to collapse
Sounds good. A full charge can make all the difference. I learnt the hard way! One or more of us will be along should you need further help.
I do hope you get this sorted! I've come back from the brink too many times to not believe you won't.
tinydynamite00
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Falaco147 said:
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im trying but i get a battery to low error. i guess i need to charge it longer
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
El Killer said:
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
Click to expand...
Click to collapse
You are welcome... The first time I did it too my battery was at 28% and I panicked since I got the low battery error.
I could of sworn that my phone officially became a paper weight. My heart dropped.
I'm glad you are up and running with the rest of us!
-Esteef
1732359994
hey !
I have the same problem, but... I can't acces to the recovery :/ i tried to install CWM (with Freegee) over Team win recovery and... boot loop :
The rom 4.2.2 flex was gone, no boot animation
-When i pres volum down + power, i have the reset menu, but after that, there is a black screen and it's written at the top left "started usb_start Fastboot Mode ()"
Please, i need your help, i'm so afraid !!
Thx !
Esteef said:
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
THIS WILL WIPE YOUR PHONE COMPLETELY...
Click to expand...
Click to collapse
I know this thread is a bit old, but it saved my butt. Your method worked perfectly. Thank you for this post.
My LG F460 was bricked (error 570), only download mode was working. Esteef method works fine even my pictures and programs was saved. Thanks!
Today, I attempt to root my G2 and i done so successfully. After I attempted to add a recovery via Flashify as told to me from someone from this site and it softed bricked my phone to where i only powered on to fastboot mode. After researching further I attempted the ubuntu fix for the situation and after I cant turn my phone on and there is no charge light indication. HELP PLZ
deetea48601 said:
Today, I attempt to root my G2 and i done so successfully. After I attempted to add a recovery via Flashify as told to me from someone from this site and it softed bricked my phone to where i only powered on to fastboot mode. After researching further I attempted the ubuntu fix for the situation and after I cant turn my phone on and there is no charge light indication. HELP PLZ
Click to expand...
Click to collapse
hold power down for 20 seconds. let phone sit for 1 minute. now hold power and volume down. this should bring you to a white reset screen. press power 3 times.
gentlemandroid17 said:
hold power down for 20 seconds. let phone sit for 1 minute. now hold power and volume down. this should bring you to a white reset screen. press power 3 times.
Click to expand...
Click to collapse
i tried that and nothing happened.
When you plug in USB does charge light come on. Sounds like a battery went dead.
Sent from my LG-D802 using Tapatalk
I've heard some people are having issues with the charge port and/or cord also. Maybe try another cord and make sure it's plugging in tightly? I think the last person covered everything else.
gentlemandroid17 said:
When you plug in USB does charge light come on. Sounds like a battery went dead.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
No charge light at all =/
I had the same problem, it occured while switching from cwm to twrp. i used the unbuntu method ( i think you mean this right here: http://forum.xda-developers.com/showthread.php?t=2582142)
are you sure you were in fastboot mode? because i wasnt and it should say so in the top left corner if you were.
try different cords/ usb ports or even pc's to charge it. my mac couldn't find it at all, my windows did.
UnknownCloakedMan said:
I've heard some people are having issues with the charge port and/or cord also. Maybe try another cord and make sure it's plugging in tightly? I think the last person covered everything else.
Click to expand...
Click to collapse
Cord charge my tab just fine, therefore im assuming the cord is fine... i think
i have the same problem
deetea48601 said:
Today, I attempt to root my G2 and i done so successfully. After I attempted to add a recovery via Flashify as told to me from someone from this site and it softed bricked my phone to where i only powered on to fastboot mode. After researching further I attempted the ubuntu fix for the situation and after I cant turn my phone on and there is no charge light indication. HELP PLZ
Click to expand...
Click to collapse
I have the same problem my phone is completly dead i don't know what else can i do, the linux tutorial doesn't work because the pc don't detects the phone
did tou guys check if the twrp image you downloaded was correct size? Wonder if a bad download could cause this.
bachera said:
did tou guys check if the twrp image you downloaded was correct size? Wonder if a bad download could cause this.
Click to expand...
Click to collapse
For me the brick happened when i was flashing KK with TWRP, during the flashing appears something that said "couldn't not mount system" and the phone shut down and never power up again , no usb no charge, no linux, no nothing, when i plug my device in windows appears that the devices cannot install the drivers, and i've tried all the drivers and still doesn't work
Hold power down until phone is completely off. Then, hold power and down volume until you see LG logo. As soon as you see the LG logo, release and then quickly press power and down again. Hold until you see a white screen. Then go from there.
techbeck said:
Hold power down until phone is completely off. Then, hold power and down volume until you see LG logo. As soon as you see the LG logo, release and then quickly press power and down again. Hold until you see a white screen. Then go from there.
Click to expand...
Click to collapse
i've tried all the possible combinations of buttons and no one works, i've been holding the power button for a whole minute and nothing happened, and the other combination either, nothing seems to work i give up
It's just power you press after the logo, not power and volume down.
pimfram said:
It's just power you press after the logo, not power and volume down.
Click to expand...
Click to collapse
There's no logo, 'cause it doesn't turn on by any means , no matter what button or combination i press, there's no response.
Thanks
Have you tried getting into download mode?
pimfram said:
Have you tried getting into download mode?
Click to expand...
Click to collapse
i've tried everything, download mode, linux, recovery, lg mobile, and nothing works i think it's completly brick, i hope one day someone comes with the solution, because i went today to SAT and they don't even know what happened with my phone, and i bought it in another country so they don't want to get involve
So all you get is a black screen with you boot? There's probably a way to push whatever file might be missing or even an entire ROM but I lack the knowledge on how to do that. I remember I had to work some magic on my Galaxy Nexus but I used a toolkit so I'm afraid I've got no really useful information for you.
This also happened to me!
I am in the same state.
I rooted the LG, I installed the custom Rom, I installed an updated GAPPS and it wasnt working. I then went and installed another GAPPS overtop and I got stuck in boot loop. After I tried recovery from ADB I tried to restore from TRWP and it didnt take. After I rebooted nothing turned on, no LED, I tried ALL button combinations and nothing comes on at all. I am wondering if the phone died and now will not charge...I started with 60% but the last time i saw it it was down to 15% just thinking maybe it died completely and without any software to boot it wont charge...I have had it on charge for 8 hrs since and still nothing...
Please help!
Bobert the great said:
I am in the same state.
I rooted the LG, I installed the custom Rom, I installed an updated GAPPS and it wasnt working. I then went and installed another GAPPS overtop and I got stuck in boot loop. After I tried recovery from ADB I tried to restore from TRWP and it didnt take. After I rebooted nothing turned on, no LED, I tried ALL button combinations and nothing comes on at all. I am wondering if the phone died and now will not charge...I started with 60% but the last time i saw it it was down to 15% just thinking maybe it died completely and without any software to boot it wont charge...I have had it on charge for 8 hrs since and still nothing...
Please help!
Click to expand...
Click to collapse
I'm afraid to tell you, but our phones die there's nothing to do to saved them, we just have to keep them in that state meanwhile the solution comes up, because in this very moment there's nothing we can do
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
when i try any combination of buttons to access either the real recovery or the bootloader the tablet just plain ignores that im trying to turn it on, just doesnt work, it just turns on if im not pressing anything besides the power button.
to sum up to all my problems i would love to keep trying and see if at anypoint it will turn to bootloader, i havent seen the notification of the tablet being charged... meaning that i dont know if it has enough battery to last me the remaning ideas i had.
So in a nutshell
-no bootloader
-no fastboot
-no recovery
-cant tell if battery or not
Please if anyone knows how to fix or at least get me to a bootloader i would fix everything else, but i really need the guidance here
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Osivanlou said:
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
Click to expand...
Click to collapse
Are you able to get adb to recognize the device with "adb devices"?
KJ said:
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Click to expand...
Click to collapse
Yeah ive tried 4 other chargers, and nothing new, i know that the os itself takes care of the charging as does the recovery in some cases, but since i have non i dont know if its gonna charge at all or not and trying doesnt sound really appealing since i should save battery in case theres a solution and needs battery power
but thanks for the answer
[email protected] said:
Are you able to get adb to recognize the device with "adb devices"?
Click to expand...
Click to collapse
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Osivanlou said:
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Click to expand...
Click to collapse
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
erica_renee said:
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
Click to expand...
Click to collapse
yeh i know how to use the skip toolkit, yet i hope i have enough battery for the test, because the only friend that i know owns a nexus 7 left the country a few months back, so the battery sounds like its gonna be hard to get. Anyways, as u were saying theres a posibility that while the tablet is rebooting and rebooting it might be able to be found on the adb devices? and use the fastboot, cuz if thats true u would be the hero ive been waiting for...
imma check and tell u later,
thanks for the answer
Hi all,
I'm sure I am still one of many that cannot use XCnathan32's solution to fix their phones. I think the biggest problem is that it is difficult to discern between hardware vs. software being the culprit. If hardware, nothing I do can help. I've wanted to use the solution but when the computer cannot even find the device/recognize it, I cannot even start the solution. Let me explain what my phone is like/ the state the boot loader is in:
Google logo is the only thing to show.
Even when trying to boot from bootloader -> recovery mode, it only goes to the google logo and boot loops from there.
Unfortunately I did not unlock developer options / USB debugging so my bootloader is LOCKED, my computer does not recognize the 6P at all unless in boot loader. It gives a strange description of the device, but does not treat it as a device in the device manager. Even if it does show I cannot update it's driver. It essentially seems like only the bootloader is a device rather than the phone.
I have tried leaving the device to boot in hopes of it miraculously starting and allowing me to go to developer options, this has failed as well.
Would anyone know/ be willing to explain how to proceed from here? I'm sure the options are limited when the device does not even show up on the computer.
Note: I don't know much about TWRP, ADB, SDK etc, its all 2 days new to me.
Thanks for any help!
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.
Click to expand...
Click to collapse
I got it! Used a blowdryer though. Unfortunately it went back to boot looping even after I did a factory reset. I'm going to apply the fix now that OEM has been unlocked and USB debugging!
Archavius said:
I got it! Used a blowdryer though. Unfortunately it went back to boot looping even after I did a factory reset. I'm going to apply the fix now that OEM has been unlocked and USB debugging!
Click to expand...
Click to collapse
Congrats on getting it to work! Let me know if you need any help with flashing the modified images.
XCnathan32 said:
Congrats on getting it to work! Let me know if you need any help with flashing the modified images.
Click to expand...
Click to collapse
I'm currently writing a guide to get to the OEM unlock stage on your thread . Thanks so much for all of your work, my phone is currently booting. Its got the google logo with a unlocked pad lock on the bottom and then it switches to a section with android warnings saying "Device software cant be checked for corruption, please lock the bootloader".
Its actually bootlooping again... I've flashed all the images possible on your downloads part of the thread Not sure if there's another option to take to get rid of the bootlooping.
Archavius said:
Its actually bootlooping again... I've flashed all the images possible on your downloads part of the thread Not sure if there's another option to take to get rid of the bootlooping.
Click to expand...
Click to collapse
Have you been here? ?
Exodusche said:
Have you been here?
Click to expand...
Click to collapse
That's the exact guide I used. I also used his first guide before that one was published by XDA. It almost seems too simple though. I feel like I'm missing something. I flashed the 48B_A4 firmware, then the twrp3_1_1_4Cores.img and reboot. It still boot looped. I then proceeded to flash the other possible imgs to see if they would work. I cant flash the EX kernel since I can't boot into recovery since it just boot loops again.
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.[/QUOTE
Excuse my pessimism, but for real? I'm having the same issue, what exactly does this do?
Click to expand...
Click to collapse
JohnnyKilo said:
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.[/QUOTE
Excuse my pessimism, but for real? I'm having the same issue, what exactly does this do?
Click to expand...
Click to collapse
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
Archavius said:
JohnnyKilo said:
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
Format all partition except for internal storage.
1. Flash N2G48B_vendor.img into vendor partition
2. Flash N2G48B_4Cores.img into boot partition
3. Flash purenexus_angler-7.1.2-20170725-OFFICIAL.zip
4. Flash BeansGapps-Full-7.1.x-20170610.zip
5. Flash EX4_1_1_4Cores.zip (Elemental Kernel), step up the core speed one notch on first screen, leave the rest on default.
Reboot.
Waited about 10min on the animation screen (4 dot jumping), eventually phone completed booting
Click to expand...
Click to collapse
sorry to hijack your thread, can i know the steps that you took to enable oem unlock ?
Because i am in your similar situation, all i can see is the google logo & bootloader is locked (i cannot go to the settings menu because the phone doesnt bootup, i am stuck in the google logo).
If i run the fastboot flashing unlocl it fails (since bootloader is locked)
ShadowSounds said:
sorry to hijack your thread, can i know the steps that you took to enable oem unlock ?
Because i am in your similar situation, all i can see is the google logo & bootloader is locked (i cannot go to the settings menu because the phone doesnt bootup, i am stuck in the google logo).
If i run the fastboot flashing unlocl it fails (since bootloader is locked)
Click to expand...
Click to collapse
You need to use a heat gun or hair dryer above the fingerprint sensor. Keep phone at low battery but not empty. 5%
.....
mattrb said:
You need to use a heat gun or hair dryer above the fingerprint sensor. Keep phone at low battery but not empty. 5%
Click to expand...
Click to collapse
lol it worked. Thanks
ShadowSounds said:
lol it worked. Thanks
Click to expand...
Click to collapse
How did you know your battery was at 5%? At the fastboot screen I see that the battery says OK, but not a specific number. Does that battery field change when it gets below "OK"?
Archavius said:
I'm currently writing a guide to get to the OEM unlock stage on your thread . Thanks so much for all of your work, my phone is currently booting. Its got the google logo with a unlocked pad lock on the bottom and then it switches to a section with android warnings saying "Device software cant be checked for corruption, please lock the bootloader".
Click to expand...
Click to collapse
This is my phone. Can you help me?
Hi there - I ended up having to use a blow dryer to throttle the phone using High heat. I wouldn't recommend it, it wasnt safe and my phone after fixing stopped working in an hour. If your phone isn't working despite following the fix above get a new phone, the pixel 3a seems like a nice new option, good luck!
Stuck in recovery mode
Archavius said:
JohnnyKilo said:
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
OK, I don't have a bootloop problem per se, but I changed my battery and now it only goes to the Reboot bootloader screen. The arrow keys don't work to change the menu. Sometimes I can get it to Recovery mode, but neither the power key or arrow keys will work. Once I got it to the Start, but the power key did nothing. ADB devices returns nothing, so even though I installed the Google USB drivers in Android Studio I can't get the computer and the Nexus to talk to each other. I'm ready to try heating the device, but that goes against everything I've ever known about electronic devices. Are you sure? .
Click to expand...
Click to collapse
Don't heat up your phone, this thread is uselss for you.