Can anyone help me with this problem?? I tried many ways but there isnt anything possible. The community either ignores me or gives me a simple answer. Can anyone just give me a suggestion of what i cant do?
You can't do anything with it by the looks of things, it's gone.
me too.....
On the same boat but mine is being recognized by my PC.
Same here... some extra info.. but still broken.
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).
tacua said:
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).
Click to expand...
Click to collapse
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Done that
mb_guy said:
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Click to expand...
Click to collapse
I had lurked this forums for 3 year now, and until now I signed up to post my experience. So yeah, I have looked on this forum and other sites for the correct KDZ. If you look careful on that post (as I did) that latest full LP version KDZ is 10h, which already have it for a while. However when this happened to my phone, it was already on 10n which is the version I expect to find somewhere to be able to recover my phone. Recently, I see that is available version 20e but that is already MM, I want to observe how it behave on the community before I decide to go there.
No matter what is the case, the phone was sent for repair. I think mine when under the worst case scenario of the so much mentioned bootloop. So much, that it even opened the bootloader and show me the fastboot prompt, although that the Canadian version is locked.
For my experience with the Nexus, they come with two bootloaders, the normal that can be updated locked and unlocked and a emergency bootloader that is available when the device is almost bricked and the normal bootloader is borked. Finally there is a low level manufacturer flashing that use the OEM SOC application to put the initial ROM. In the past I have been able to play with the Rockchip and the Nvidia Tegra 3, applications at that level. So those devices are simple "unbrickables". Low level Qualcomm (QHUSB_BULK) flashing is barely mentioned on the net, no process detailed, no application available so far that I can find.
My experience with LG so far is like buying a PC with installed OS, no recovery CDs, no website to download the recovery, no access to the BIOS, no "normal" human soul is allowed to create a full backup of the HD without going on a major hackaton with not assurance that what you get will work in future case of emergency. If something happens to the OS when you are out of warranty... you are royally screwed.
Guys try the oven method it may work. Some are saying it lasted 24 hrs others say its still active. It may be dangerous but worth a shot since no one else is taking action on this fix.
Also my phone was just rooted. At that time I wasn't trying to do anything with modifying but just using instagram.
Related
Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.
I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.
Try reinstall usb drivers, rsdlite, different usb port, and different pc.
@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.
If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.
im having the same issue, did you solve it?
im having the same issue, did you solve it?
try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...
You have tried the McGyver-trick?
I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.
Ok. At least you have the time now to enjoy your sunny weather in Brazil...
RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help
First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx
Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again
i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan
hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..
Basically, this: http://forum.xda-developers.com/showthread.php?t=1384415
No one responded to that thread because it was in the wrong forum.
I got the "Phone -- ! -- PC" screen, and was attempting to fix it before getting this black screen of death.
Galaxy Nexus GSM
Rooted, Codename ROM, don't think there is a Kernel in there
Carrier: Virgin Mobile
Edit: I won't be able to respond for a couple hours as I'm going to work. Any and all help is much appreciated.
Original post from above thread below:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
What i with my little (almost nothing experience in android) would do its going to another computer with no drivers installed, would download the toolkit and install those drivers, then plug the phone and see what happen, im sure its not bricked since the computer recognice it.. I did lot of stuff with blackberry and there was a lot of ways to recover a phone like that... From here if the toolkit recognice it in any way.. Then you could try to do some of those steps.. As far as i tried doing all kind of stuff to my phone, toolkit its for much the Best Tool and way to do anything to your phone or at least for starters like me
Sent from my Galaxy Nexus using xda premium
But the computer doesn't actually recognize it. The "detection" sound it makes is for an unresponsive device. It won't charge, won't be recognized, and no matter what combo I use, it doesn't turn it.
I played dumb, called Samsung, and now I'm going to send it in. Thanks for the help though.
sometimes my screen goes blank and I have to pull the battery and everything comes back to normal
Phone is Verizon Galaxy Nexus, running the vicious jellybean build that first came out (yeah I was too lazy to install a new ROM when the first Jellybean build I got my hands on worked fine)
Alright so here's the sequence of events,
Last night - phone working just fine
When I went to look at my phone and set an alarm for when I went to sleep I noticed it was powered off. So I tried to power it on and it hanged at the Google logo. It did this for about 20 minutes, and then I pulled the battery and tried again. This time I left it at the Google logo bootscreen over night (plugged in). Note: I'm not sure if it was bootlooping or hanging at this point, I don't remember it vibrating)
I'm awaken in the morning by the sound of my phone vibrating every 10 seconds. I look at my phone and it's at the unlock screen but the only things I can do are emergency call and, strangely, it asks me to enter a password to decrypt my phone. I never encrypted it. I started freaking out, at this point I probably should of started Googling for a default password or something, but in my morning stupor I rebooted the phone and it just bootlooped on me.
I got into CWM recovery, looked for a NANDROID backup but it kept telling me sdcard wasn't mounted, and attempting to mount it failed. I'm not seriously scared.
Reboot back in to CWM recovery to see if anything changes. Nope.
I Google this problem and land on this page. (I guess I can't post links, but it tells me I just have to reflash CWM) I think, "oh, I just have to reflash CWM. Not too hard!
I downloaded the GN toolkit and update to the latest CWM touch.
Attempted to reboot phone - nothing happens. All buttons unresponsive, no battery shows up when trying to charge. My laptop doesn't find it.
More Googling. I land on this page (link removed - GSM forums for legija's .bat unbrick fix thing), so I try plugging in my phone to my laptop without the battery, sure enough I see the OMAP 4460 device attempting to install. I follow the instructions and install the OMAP drivers, but when I plug in my phone it acts as if its being unplugged and replugged back in constantly. It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail
And so that's where I am. I have my phone plugged in right now incase for some reason it isn't charged, but I'm stuck. I hope I gave enough information for anyone to help me, thanks!
Sleete said:
[*]More Googling. I land on this page (link removed - GSM forums for legija's .bat unbrick fix thing), so I try plugging in my phone to my laptop without the battery, sure enough I see the OMAP 4460 device attempting to install. I follow the instructions and install the OMAP drivers, but when I plug in my phone it acts as if its being unplugged and replugged back in constantly. It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail[/list]
And so that's where I am. I have my phone plugged in right now incase for some reason it isn't charged, but I'm stuck. I hope I gave enough information for anyone to help me, thanks!
Click to expand...
Click to collapse
some also have had this issue "It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail"
but no, they've managed to do it in the end, it's just that you have to be ultra-quick
can you still get in fastboot/bootloader? if yes, flash latest twrp (i'm sure it supports encryption); if after flashing twrp it still doesn't work, flash google stock images by following the procedure here
Thought I should update this in case anyone else manages to hard-brick their phone, but I sent it in to Samsung and they replaced the entire mobo under warranty. I think they either didn't care or it was bricked enough where they couldn't tell I rooted it. Also good side effect of fixing the finicky USB port on my phone. Happy ending!
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
RuedasLocas said:
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
Click to expand...
Click to collapse
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
RandomUSA said:
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
Click to expand...
Click to collapse
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
RuedasLocas said:
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
Click to expand...
Click to collapse
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
RandomUSA said:
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
Click to expand...
Click to collapse
Try to don't mess with the audio chip!
Turn ON the phone with no cable connected.
Mine have that long boot only the 1st time, after that behaves normally.
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
Of course that until your phone boot completly you can't do any changes...
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
BTW... you install "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All" and "LGMobileDriver_WHQL_Ver_4.2.0" ? Maybe it helps to have those installed before flash.
Maybe it is the same in some devices (also depending on the phone Firmware version) to have those or others but, mine only work with those two installed.
Try this:
Re-flash with LGUP using the v20p again.
After the process is done and the long boot starts (wait 5 minutes or so), take out the battery, let the phone cool down for 10 minutes.
Insert the battery back on the phone and turn it ON.
Leave it until boot finish, go for a walk, watch some TV, forget about the phone.
Of course that if after 30 minutes stills without boot up, you can consider that you have a problem. And me out of ideas... sorry.
Wish you all the best luck on that, regarrds.
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
first of all: what model? we have 11 models for the g4 and not all behave the same way.
second: use SALT. SALT shows your previously installed firmware
third: try flashing custom ROMs instead of STOCK
fourth: I guess you know about http://bit.do/ilapofixg4 ?
.
steadfasterX said:
...
third: try flashing custom ROMs instead of STOCK
...
.
Click to expand...
Click to collapse
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
RuedasLocas said:
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
Click to expand...
Click to collapse
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
steadfasterX said:
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
Click to expand...
Click to collapse
Thanks for responding! I have a t-mobile h811 variant, LGUP/SALT currently shows my firmware as 20p, I decided to try updating to 20x using lg bridge, but the firmware is still listed as 20p despite the process being completed 'successfully'.
I know that flashing the KDZ worked because it overwrote my recovery and I no longer have access to TWRP. Before flashing the KDZ I tried several ROMS (stock 20p, aokp, lineage OS).
Now the phone is bordering on being a paperweight because I have no means of installing TWRP. I have an unlocked bootloader but there is no way for me to enter the bootloader. Is it possible to repackage a KDZ with a custom boot image or custom recovery?
Before flashing the KDZ and losing access to TWRP, I tried modifying the system boot.img to limit the number of cores that could be used to 4, and even 2 cores without any luck.
Right now, I don't think the phone has any bootloop issue or heat related problem because powering on the phone has become perfectly functional, the phone does not reboot itself (just stays at "Life's Good" with the blue blinking LED), recovery worked fine and handled a lot of load for hours reaching 40C+ on the CPU and with no issue.
I found the guide to unlock downgrade and root 20i, but since i was already on 20i i figured id just skip to the unlock part.
ADB connected.
Got the oem unlock to work flawlessly, tried to boot TWRP, and it said file sent, cannot boot, file unsigned (or something similiar, can copy paste the actual text when i get off work tonight)
I got annoyed and just booted the phone normally and it worked fine and is unlocked-
But cant get the phone to show up on adb again.
Maybe try the universal drivers? Seems to hang on the drivers- the laptop has them installed but the phone doesnt know that they are and keeps asking me to reinstall (which doesnt work)
Any ideas?
Should i start over,upgrade the stock rom and then downgrade, like the directions actually say?
redchigh said:
I found the guide to unlock downgrade and root 20i, but since i was already on 20i i figured id just skip to the unlock part.
ADB connected.
Got the oem unlock to work flawlessly, tried to boot TWRP, and it said file sent, cannot boot, file unsigned (or something similiar, can copy paste the actual text when i get off work tonight)
I got annoyed and just booted the phone normally and it worked fine and is unlocked-
But cant get the phone to show up on adb again.
Maybe try the universal drivers? Seems to hang on the drivers- the laptop has them installed but the phone doesnt know that they are and keeps asking me to reinstall (which doesnt work)
Any ideas?
Should i start over,upgrade the stock rom and then downgrade, like the directions actually say?
Click to expand...
Click to collapse
The LG driver you've installed on your laptop is most likely no longer functional for the phone. If it shows in Device Manager when you're trying to connect it, uninstall it (mine didn't work either after unlocking/using FWUL, or something else, for whatever reason).
Once the current driver is uninstalled, turn off your computer, plug your phone in with the USB cable and then turn on the computer and let Windows install the driver now (It worked on mine).
See the attachment below for a screenshot of the current driver for my LG G4 that is working completely.
I got it to show up, but I've realised I have the motherboard issue common to G4's.
The phone hangs at 'bootloader unlocked' lg screen.
Hope the seller will give me a refund or exchange.
redchigh said:
I got it to show up, but I've realised I have the motherboard issue common to G4's.
The phone hangs at 'bootloader unlocked' lg screen.
Hope the seller will give me a refund or exchange.
Click to expand...
Click to collapse
It may just be a 'soft brick' you've encountered, in which case you should be able to it overcome relatively easily. First thing to try, is just unplug the phone and take out the battery. Put the battery back in and see if it will boot up. If not, see if you can get into Download mode and flash your rom version for your phone model with LGUP-NEW.
With respect to TWRP, if you can get into bootloader/fastboot mode, refer to this thread: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 and follow the instructions to flash by fastboot commands. Use the latest preview version for your rom version, i.e., MM, N or O.
Note: The Thanks button at the bottom right of the post should be used when members are trying to help you with your issues. It's an XDA courtesy, so please learn to use it.
sdembiske said:
It may just be a 'soft brick' you've encountered, in which case you should be able to it overcome relatively easily. First thing to try, is just unplug the phone and take out the battery. Put the battery back in and see if it will boot up. If not, see if you can get into Download mode and flash your rom version for your phone model with LGUP-NEW.
With respect to TWRP, if you can get into bootloader/fastboot mode, refer to this thread: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 and follow the instructions to flash by fastboot commands. Use the latest preview version for your rom version, i.e., MM, N or O.
Click to expand...
Click to collapse
Thanks for the tip. I already tried ADB (wouldn't boot reliably), LG UP (completes successfully- the phone, when LG UP sends the reboot at 75% or so, just hangs on the LG screen forever (though LG UP says it was successful). I also have LG Bridge, but haven't reached any level of success with it either. Luckily all these bookmarks will come in super handy with my replacement.
(Also the day it broke, somehow the camera activated in my pocket. I detected the warmth, but working an assembly line, under a cameras watch, I couldn't pull it out and fix it quickly.
sdembiske said:
Note: The Thanks button at the bottom right of the post should be used when members are trying to help you with your issues. It's an XDA courtesy, so please learn to use it.
Click to expand...
Click to collapse
Thanks for the reminder, I'll try to remember.
redchigh said:
Thanks for the tip. I already tried ADB (wouldn't boot reliably), LG UP (completes successfully- the phone, when LG UP sends the reboot at 75% or so, just hangs on the LG screen forever (though LG UP says it was successful). I also have LG Bridge, but haven't reached any level of success with it either. Luckily all these bookmarks will come in super handy with my replacement.
(Also the day it broke, somehow the camera activated in my pocket. I detected the warmth, but working an assembly line, under a cameras watch, I couldn't pull it out and fix it quickly.
Thanks for the reminder, I'll try to remember.
Click to expand...
Click to collapse
OK - one last thing to try if you want to try it. Using the power and volume keys, see if you can get into Recovery mode to do a hard factory reset
- refer to this link for the how-to for entering Recovery mode: https://www.androidexplained.com/lg-g4-recovery-mode/