Hello
Ok so here we are, I've explored the forum deeply to search for a solution for this, but it's always the same thing for every topic: Nothing works, the author apparently just gives up and let his topic go away, and in the better case get his phone replaced, but I travel and for some reason there is no LG support around my current city. So I told myself: "Why don't I create my own topic ? Maybe this one will be the one ?"
I bought my phone about 4-5 months ago
My phone is stuck in a boot loop, the logo would just appear 2 seconds, disappear 2 secs, reappear and so on before eventually running out of battery and shutdown. At first it started with some random annoying shutdowns when I use it, but now it has got worse. I can only use it when it's plugged. I've tried every single solution found on the web, nothing works. All of this happened since the last firmware update I did from the settings, it is now on lollipop 5.0 20h-ESA-XXX
I came here so maybe I can downgrade or install a custom ROM, because I haven't tried that yet. But there is more:
My PC won't recognize my phone, it just says that the device is not working properly, but I can charge and use it while it is plugged
Tried other computers, it would just disconnect and reconnect again and again. i tried different cables, same thing. Can't use it. Instead would just shutdown and start charging. That problem may come from the drivers that won't install properly because it is said that the MTP USB Device: Failed
Finally, I tried rooting from the phone and without a computer. Kingroot doesn't work, Stumproot doesn't work and anything else won't work either
Sometimes I feel like I am about to throw my LG against a wall.
Please, can anybody help me fixing this ?
Up here
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!
Hi all
I have been messing with this problem for hours and im out of ideas.
I got this phone (D855) from a friend to see if i can get it out of its bootloop which she seems to have after getting an update from lg. I can get into (stock)recovery and hardware buttons config (or something) but when i try to enter download mode, it will only get there when the phone feels like it.
When i try to get into download mode i can see a little box saying "Download Mode" and then the phone restarts into some sort of charge icon loop. switching on and off showing a battery icon.
I have tried flashing different stock roms to see if any of them solve the issue but so far no luck. Near the end of flashing, the phone seems to want to reboot into download mode to finish the process but since i can only get into download mode occasionally it fails(i think). The LG flash tool 2014 says it was succesful but since it rebooted at about 85% and cant get back into download mode, i guess it failed.
I also think i cant charge the battery. for some reason the phone keeps showing the battery icon for a few seconds only to shut down and show it again. Like a charge loop. This is what i see for the remaining 15% of the flashing process.
The LG pc suite wont do anything because the battery seems to be too low. Problem is that i dont know how low it is and i cant seem to charge it for some reason.
Any ideas?
Exact same issue for me, everything you said is happening to mine. Got any help? I have read that maybe shorting it could help, have you tried?
Mudrost said:
Exact same issue for me, everything you said is happening to mine. Got any help? I have read that maybe shorting it could help, have you tried?
Click to expand...
Click to collapse
Not yet. I read that alot of people damage their phone trying to short it. It is not my phone so damaging it is not really an option.
I will try it with permission if all other possible solutions have been explored.
I tried the shorting thing and every step was succesful but it didnt change anything.
still the same so the shorting method does not work in this situation
Anyone?
Problem solved.
It turned out to be a faulty battery that caused my problems. Glad i didnt damage anything shorting the pins.
Battery replaced and all works like it should.
Nearly At the end of every month my my phone gets into some kinda software problem (example : Google has stopped working then process.android has stopped working and some other random **** which is quite annoying) whenever this happens the phone restarts on its own and never turns on,i mean it does but is stuck on loading screen.(note: I dont do anything stupid which might harm my phone. )So i have to flash my phone with spflashtool it.This time when i flashed the phone it didnt turn, i held the button for long but it was of no use, so i thought it might be the low on battery,but when i put it on charge nothing popped up... it wasnt charging. Then I thought it was the battery but my battery wasnt swollen and the day before I flashed it,it was running fine with full charge. , there was no sign of battery problem anytime i used it the consumption was normal.
Please help me fix this problem, and I also want a permanent fix to the software problem too.
Any senior member please help..
TIA
:fingers-crossed:
Update:I flashed the phone with new files but results were the same :'(
Saad6459 said:
Nearly At the end of every month my my phone gets into some kinda software problem (example : Google has stopped working then process.android has stopped working and some other random **** which is quite annoying) whenever this happens the phone restarts on its own and never turns on,i mean it does but is stuck on loading screen.(note: I dont do anything stupid which might harm my phone. )So i have to flash my phone with spflashtool it.This time when i flashed the phone it didnt turn, i held the button for long but it was of no use, so i thought it might be the low on battery,but when i put it on charge nothing popped up... it wasnt charging. Then I thought it was the battery but my battery wasnt swollen and the day before I flashed it,it was running fine with full charge. , there was no sign of battery problem anytime i used it the consumption was normal.
Please help me fix this problem, and I also want a permanent fix to the software problem too.
Any senior member please help..
TIA
:fingers-crossed:
Update:I flashed the phone with new files but results were the same :'(
Click to expand...
Click to collapse
same happens to me bro my android one is also dead same problem as yours when i tried with sp flash tool its end up with this error..... scr shot attached
☹
Bro,I flashed it thrice after but it didn't give any errors,but sadly it just wont turn on
If it were permanently bricked then it wouldn't have detected the phone...and bro lemme give you a suggestion,try changing it to firmware upgrade instead of download only.
Thanks for the reply
simmilar issue
same problem pls help in my case when i charge not charging the battery indicator just pops up and out i think its a battery error put in a new battery try to boot up nothing try to go in recovery nothing i have nothing to boot up from i think ill still try using fastboot and/or flashing and reporting back(ima try dead usb flash using spflash tool)
okay flashing works perfectly now i just need for figure out if the problem is with the charging/battery or the phone is dead
Same Problem
Bro, i have run into exact same problem. I even went to gallery and gave them the phone, they said they will charge 1500 as motherboard is dead but after one month they returned to me the phone saying that motherboard is not available. They are taking almost 14 days to return money so i have to visit again on 3rd june. But coming back to problem i have tried flasing with and without battery for 3-4 times. every times it shows success but the phone wont start. Even memory test was all fine. cant figure out what's the problem. i have tried both download only and format+download mode but nothing seems to work, If anyone finds a way to fix the phone please tell ASAP.
Same problem as the OP, mine's bricked as well after it began showing random FCs. Flashed KK and LP firmwares using SP Flash Tool but to no avail. The flash was successful tho but the phone never booted up
I'm kinda stuck in a similar situation. Let's start from the beginning -
When I got my Redmi Note 3 I stopped using my Canvas A1 and vaguely i remember that it was having software issues, rather than fixing it I just kept it away for a lot of months, and vaguely I remember that it just needed some flashing of rom and it would've gotten fixed.
And after all these months i'm need of this phone again. I don't remember much in depth details of the processes involved with it like flashing stuff etc. But I gathered as much knowledge as I could from the docs I had stored as backup & from the internet.
And IMO I think the flashing process was successful, but the screen is not turning on. Only once when I connected it to PC, the charging battery sign appeared(flashing thrice) but that was it. Nothing after that. And whenever I connect it to PC it detects the phone.
For now I've given it to a repair guy but I don't have much hope. He was saying that it could be just software problem, but I don't agree. If a smart person could comment on this thread so that we all could get some benefit out of it, in order to solve the situation or at least in my case I could research on something specific in the meantime.