Related
A strange thing happened and now I can't escape the bootloader screen. I lost my phone for a two days and when I found it it wouldn't come on. I connected it to a power cable and it immediately brought up the bootloader. The charge light won't come on but now the phone will power on without the power cable. Problem is it just brings up the bottloader and tries to install the rom image on the sd card. I put a new image on the card reinserted it and then allowed it to reflash. But it still just brings up the bootloader. Any advice?
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.
Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.
orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Lennyz1988 said:
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.
Click to expand...
Click to collapse
Reflashed from PC, reboot to bootloader behavior does not change.
ultramag69 said:
Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.
Click to expand...
Click to collapse
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?
cyberscribe said:
Reflashed from PC, reboot to bootloader behavior does not change.
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?
Click to expand...
Click to collapse
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1
this is certainly strange, could it be something with the SPL, i would look into that next if this doesnt help
cyberscribe said:
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1
Click to expand...
Click to collapse
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.
stevedebi said:
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.
Click to expand...
Click to collapse
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.
cyberscribe said:
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.
Click to expand...
Click to collapse
Fixed! Stable as a rock
cyberscribe said:
Fixed! Stable as a rock
Click to expand...
Click to collapse
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!
cyberscribe said:
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!
Click to expand...
Click to collapse
task 29 got me to the rom splash screen
cyberscribe said:
task 29 got me to the rom splash screen
Click to expand...
Click to collapse
reflash ROM from PC not SD. Reflashing after that from SD works. Hope I don't have to do this every time I change a battery!
I think I may be having the same or a similar issue as you cyberscribe. All of a sudden, I am getting restarted into the bootloader too.
I was using an older NRG 2.1 ROM (April-ish) and had to pull the battery after it froze up. Nothing new, it happens. The new part is that it would only restart into the bootloader screen. I thought it might be the older ROM, so I Task 29'ed and flashed NRG's newest 2.1 June 2nd ROM.
Successful boot and ROM setup while connected to USB. Unplugged USB, restarted phone, BOOTLOADER.
Plugged in USB, successful boot.
Unplugged USB, BOOTLOADER.
Plugged in wall outlet, successful boot.
Unplugged wall outlet, BOOTLOADER.
Obviously, I can conclude that there is an issue with trying to boot on battery power, or at least while not connected to a power source.
Anyone ever have this happen? Or have any ideas why this would be happening? I really don't want to have to find a power source every time I need to restart my phone, haha. I am still trying to troubleshoot further and will update if I find anything else worthwhile.
Also last night I tried restarting while plugged into car adapter, which as expected booted fine every time.
However, this morning I just restarted on battery power and it booted fine also. Nothing changed from last night to this posting. Honestly, I am completely at a loss as to why I am getting restarted into the boot loader seemingly at random. I thought I had it nailed down with the power source, but now that apparently is not the issue.
cyberscribe, are you still having issues? Anyone else ever have this problem? Any thoughts on a cause or solution? Or anything to help troubleshoot?
After the bootloader first pops up, there is a very quick screen that flashes, "Loading.... No image file", then goes back to the bootloader screen.
I have to discount my earlier theory that it will always boot when connected to any power source. Now it will only boot when connected via USB to the PC.
Looks like I am going to have to re-flash the stock ROM and then stock SPL and see if this solves the issue. Then, if not, I guess a warranty claim is in my near future.
I really wish we could have gotten some replies from smarter people than myself in this thread. haha
Finally flashed back everything to stock (SPL, radio, ROM) and still having the bootloader issue, looks like it is going to be a warranty claim after all.
Sounds more like a memory issue if it can't find the image file. If you both got your Rhodiums from the same carrier it could be a bad batch of phones...
Same issue on my tilt 2 just cropped up today. If I am reading the above correctly it sounds like 2 tilts and a t-mob rhodium having the issue, so different carriers. =/
Soft reset the handset and set it down, picked it back up and it was in bootloader. All attempts to get it out of bootloader (reflashing from sd, pc etc.) seem to complete just fine, but upon reboot dump into bootloader. May be a different problem than OP as I havent had any success in getting a boot after reflash.
Not sure if I am having the same problem, when I try to turn on it just comes up with the Touch pro 2 screen with the red text in the bottom left hand corner, I am using an energy Rom again from about April, I have tried re flashing but pc wont recognise/find phone, Wha acn be done?
Hey guys, I really need your help here.
I was trying to flash my mate's phone with the newest MIUI today, but it wouldn't work because the SD card wouldn't mount.
Now when he got this phone, it was already rooted. No idea how they rooted it, but there were a few Chinese apps on there. I got my phone (Samsung Captivate) from the same people, and there were also a few random apps on there, but I managed to flash a new ROM on that. It got to the point where I was un-rooting and rooting it over and over again, until I found a Clockwork Mod that worked on the Defy. It mounted the SD card fine, and then it installed the ROM using the "install from zip from sd card" function or something like it. It went fine, said it finished and it didn't lose power half way through the install. Rebooted the phone, and now it's stuck on the "M" Motorola logo. Went to go flash with sbf, and then it came up saying that the battery was too low so it wouldn't program. Well ****.
Tried the Mcgyver mod where you just splice a USB in between the battery and the phone, but that didn't work. I'm hoping that it will just charge from USB while the phone is off? I've read somewhere that it won't charge while it's off, but the LED is white (I think that indicates that it's charging). Occasionally the "M" logo comes on, but it goes away and starts "charging" again. It won't take to the wall charger for some reason, just doesn't want to charge D:
I've been at this for 8ish hours now, does anyone have any advice? Anything at all will be greatly appreciated.
Thanks,
Justin
How long have you been trying to charge it? That's normal behavior for the phone to show the Moto logo and go to battery charging animation when the phone is off. You should be able to power it on if it is plugged in though.
Are you in the boot loader when you try to flash the SBF? Reboot the phone and hold the volume key up to get to the bootloader. Use RSD lite to flash the SBF. I'm sure you've already looked at http://forum.xda-developers.com/showthread.php?t=966537. It's very helpful.
Good luck!
After flashing the new firm , try to make a WIPE before you install the zip !!
Worked for me!!
this should go to the development sector
youll find your answer there under "bricked phone"
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
Ive just encountered the same problem. Were u able to find a solution?
Shahin7631 said:
Ive just encountered the same problem. Were u able to find a solution?
Click to expand...
Click to collapse
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
anish100 said:
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
Click to expand...
Click to collapse
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
GStriker said:
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
Click to expand...
Click to collapse
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
GStriker said:
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Click to expand...
Click to collapse
Ive literally tried everything .even repartioned the phone . it works fine in recovery and download mode but as soon as i want too boot to android unplugged it restarts . when plugged it has no problem
Funny thing. I have a factory Sprint Note 2 with the latest kitkat updat and I am experiencing the same problem. Phone has not been rooted or messed with. If anybody come across a solution let me know. I booted the phone and unplugged the power button to verify and it does the same thing. Only stays on when in airplane mode or charging.
One more thing. I tried somewhat to do what was posted above about performance / cpu power. I put the phone in powersave mode and checked limit cpu and is is fully operation. problem gone. If I turn power save mode off I'm back to square one.
To late. Took a picture by mistake and phone jumped into boot loop.
i have GT-N7100 and same problem phone is stuck on boot loop when unpluged
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
i just tought maybe it needs new battery. cause before i unpluged it it showed 67% then bootlooped 2x then i pluged back in and it shows me only 5%. i think its battery cause it cant dishcharge in 1 or 2min
My initial problems were that it would drop signal and show an x with no bars intermittently. then i started having problems anytime the phone demanded use. Picture, internet, video. tried a few things listed above. Still would go into a boot loop when not plugged in. Battery would charge normally and show it percentage like normal. It would reach 100% with no difference in charge time. When battery saver is on it would not have a problem unless I use an app that demands more cpu usage, network connection, battery consumption. Put a new battery and problem is gone. some people say the battery show swelling but my battery looks identical to the new one. no swelling and it is not deformed in any way.
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Shahin7631 said:
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Click to expand...
Click to collapse
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
dcmobiletech said:
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
Click to expand...
Click to collapse
Ive tried already with another battery ....its a very strange situation while everything works fine in download or recovery mode when its unplugged ...i have ordered a third party battery to see if it'll make a difference or not ....i'll keep u updated tomorrow
GStriker said:
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
Click to expand...
Click to collapse
Where is the Preferences section? I am unable to find that on my Note 2 settings.
Experienced the same thing and this is the first time I had this. I was playing a game after I fully charged my battery and suddenly it turns off. So I waited for it to turn on where I noticed that it keeps on turning on and off and stuck on the " Samsung Galaxy Note 2" logo screen. Then I tried several things like clearing the cache and dalvik but it just do the same thing. I re-flashed the 4.4 ROM that I was using but sadly it does the same thing. I then noticed that if I plug in the charger it works normally and does not boot loop. And as soon as I remove the charger it will keep on restarting on and off on that screen. I was thinking that it might be a hardware failure or the battery itself. So I went to recovery mode and unplugged the charger, it stays on. Went to download mode without the charger and it stays on. Freakin' weird. I am about to flash a different ROM and will wipe everything and see what happens...
Fully charged the battery to 100%, unplugged the charger and it started to boot loop again. I allowed it to boot loop once and immediately went to recovery mode and saw that my fully charged battery went down to 3%. Tried different ROMS (Omega, DN3, and Phoenix), I still have this issue. Now can use my Note2 as long as the charger is plugged in...
Change your battery and solve the problem ?
Sent from my GT-N7100 using XDA Free mobile app
I did. Case closed!
red_hanks said:
I did. Case closed!
Click to expand...
Click to collapse
is it working fine after battery change? does it still get stuck in boot loop? mobile networks?
It works perfectly !
I'm having a weird problem. Yesterday I was using my phone as I normally do-- texting, playing simple puzzle games, etc.-- when I noticed the battery was at about 2%. I wasn't very concerned so I tried to send one last text before it died. Shortly afterward it died with the usual "Powering Down" alert. I thought absolutely nothing of it and once I had access to a charger, I did what I normally do: I turn on my phone, wait for it to get past the LG splash screen, and I plug it in once it gets to the boot animation. I do this so my phone will turn on instead of going into charge only mode. Also, like usual, my phone's screen dimmed seconds after the boot animation began (I assume from my automatic light sensor settings), and I could feel it vibrating a little (also something it typically does upon boot).
However this is as far as it got. I was very confused when about an hour later, the phone still hadn't completed boot. I removed the battery, inserted it again, and tried once more telling myself that I would wait as long as I could instead of just an hour. Booting the second time gave me identical results-- everything is normal (light sensor response and vibration indicating the phone is powering on) yet it gets stuck. The only difference is that this time I got to see the entire bootloop.
After the boot animation screen has run for a while, I get the usual "Android is starting.... Optimizing app ## of ##" (#= actual numbers). Once it finishes, instead of booting my phone, it begins the boot animation again. If left alone it will cycle between the boot animation and the "Android is Starting" screen indefinitely.
TL;DR:
1. ) Caught in bootloop between boot animation screen and "Android is Starting... Optimizing app ## of ##" screen.
2. ) The screen still dims and there are little vibrations that usually tell me the phone is about to turn on.
I have tried:
- a hard reset- this yields only a slightly stronger vibration and it starts the bootloop again.
- Download mode- this does the same as the hard reset
- Removing battery for a while- no results
- Full charge to completely dead to full charge again on charge only mode- no results
I am running CM13 Nightlies from late February (not completely sure which exact date). Which I flashed without issue about a month ago. I do have Xposed and run various modules, but I was using nothing at the time and hadn't for about a month. My computer recognizes my phone as an LG G3 Device, but refuses to access any files.
Any help would be greatly appreciated!!
Phone not starting.
First remove phone battery, insert it again, do not start phone. Connect your phone to original charger and charge it, while charging with the charger start your phone. Your phone should start if yes/no report me immediately. Your phone battery is failing to start your phone (Due to Low Voltage in battery). Replace with original battery.
jit1108 said:
First remove phone battery, insert it again, do not start phone. Connect your phone to original charger and charge it, while charging with the charger start your phone. Your phone should start if yes/no report me immediately. Your phone battery is failing to start your phone (Due to Low Voltage in battery). Replace with original battery.
Click to expand...
Click to collapse
Alright, I removed the battery, reinserted it (without turning the phone on) plugged it into the wall charger (seeing the charge only battery animation), and attempted to turn it on. Whenever I try to turn my phone on after plugging it in, I get the LG splash screen followed by the battery charging animation. It never reaches the boot animation. I'll let it charge for a while and try again.
Thank you for the advice!
Okay, I let the phone charge completely and attempted to turn it on whilst plugged into the wall charger again. Unfortunately I had the same issue. The phone shows the LG splash screen and then the battery charging animation again-- no boot animation.
musiceas66 said:
Okay, I let the phone charge completely and attempted to turn it on whilst plugged into the wall charger again. Unfortunately I had the same issue. The phone shows the LG splash screen and then the battery charging animation again-- no boot animation.
Click to expand...
Click to collapse
just start with a full reflash , if it doesnt boot up its simply broken
Jhinta said:
just start with a full reflash , if it doesnt boot up its simply broken
Click to expand...
Click to collapse
Yeah, I'm trying to avoid a full reflash/data wipe. Since I haven't messed around with any Xposed modules or root apps, I also haven't backed up anything for quite a while. No abnormal apps were running before the battery died, which leads me to believe this can be solved somehow without a full wipe.
Also, I tried to use my boyfriend's battery to boot up my phone. I thought it might be a bad battery-- as some people on-line have mentioned. Unfortunately, it still refused to boot and it produced the same bootloop.
You see , if and not and this and that dont help . te only way to save files is to get acces by recovery or boot, you cant boot but possible you have recovery so start saving your files you need. when you have or dont have your files . you stil need your system to boot for that to happen, it needs to work. so flashing a default rom with wipe sould work if it doesnt you flash original if that doesnt work its dead
Verstuurd vanaf mijn LG-D855 met Tapatalk
I think I forgot to mention, I cannot access recovery mode. I have the latest TWRP installed, but attempting to boot into recovery gives me the same results-- endless bootanimation/ "Android is Starting" bootloop.
So no acces at all . so what do you do ? Read above! Anyway good luck
Verstuurd vanaf mijn LG-D855 met Tapatalk
Solved
I fixed my problem. It turns out I was being an idiot and got the method of entering recovery mode on the LG G3 confused with my Samsung tablet. I should be able to fix the bootloop on my own now. Thanks everyone for your help! Cheers to idiocy.
Hey, I have the exact same issue right now. Did you solve your problem, and how? I tried removing the battery and charging with original charger to 100%. I connected it to my PC, went into Download mode and clicked "Restore Upgrade Errors" in LG PC Suite. It successfully flashed the firmware update, then it said "Android is starting.... Optimizing app ## of ##". But after that it restarted into bootlop again. Also I noticed that sometimes it vibrates, and my LED (light sensor) doesn't light up anymore.
Any advice? I haven't tried replacing the battery yet.
simon710 said:
Hey, I have the exact same issue right now. Did you solve your problem, and how? I tried removing the battery and charging with original charger to 100%. I connected it to my PC, went into Download mode and clicked "Restore Upgrade Errors" in LG PC Suite. It successfully flashed the firmware update, then it said "Android is starting.... Optimizing app ## of ##". But after that it restarted into bootlop again. Also I noticed that sometimes it vibrates, and my LED (light sensor) doesn't light up anymore.
Any advice? I haven't tried replacing the battery yet.
Click to expand...
Click to collapse
Hi i have the same problem with my lg g3 d855, after a reflash hi is start and do android optimazig after the tel is start and do this over and over. help please
Hi, the solution that worked for me was to
1. install drivers
2.install LGUP
3.flash "LGD855P_D855P10a_04" - found here https://drive.google.com/file/d/18tlmVNK_ba0jIapJy-Sz5wamxbIXh8xH/view
Hi guys,
So yesterday my phone randomly started turning itself off every now and then. As time went by, it happened more and more until it never turned on. So what I'm left with now is a "LG Lifes good" screen, then black screen, then "LG lifes good" again. So I thought I'd boot to TWRP and restore an old backup. At 1% completion, the phone simply went back into the bootloop. After this, I wiped through TWRP, tried to uninstall xposed, did everything i could to no avail. So I thought I'd wipe it back to factory with my laptop. So yeah yeah got the KDZ, used LG Flash Tool 2014, installed the drivers etc and proceeded to wipe it. It didnt work on my windows 8 laptop so i went to my windows 7 desktop. This completed to 100%. My phone got the the language settings then went back into bootloop. I've tried to wipe again but it never completes. What can I do.
All help is greatly appreciated!!!
420blazed said:
Hi guys,
So yesterday my phone randomly started turning itself off every now and then. As time went by, it happened more and more until it never turned on. So what I'm left with now is a "LG Lifes good" screen, then black screen, then "LG lifes good" again. So I thought I'd boot to TWRP and restore an old backup. At 1% completion, the phone simply went back into the bootloop. After this, I wiped through TWRP, tried to uninstall xposed, did everything i could to no avail. So I thought I'd wipe it back to factory with my laptop. So yeah yeah got the KDZ, used LG Flash Tool 2014, installed the drivers etc and proceeded to wipe it. It didnt work on my windows 8 laptop so i went to my windows 7 desktop. This completed to 100%. My phone got the the language settings then went back into bootloop. I've tried to wipe again but it never completes. What can I do.
All help is greatly appreciated!!!
Click to expand...
Click to collapse
It's your battery.I have had the same problem and replacing the battery with a new one got the phone into function.
Sotiris02 said:
It's your battery.I have had the same problem and replacing the battery with a new one got the phone into function.
Click to expand...
Click to collapse
Are you absolutely sure?? I let it charge overnight and when i turned it on in the morning (while still plugged in), it worked. After unplugging, it immediately turned off.
I really don't want to buy a battery and then find that it wasn't the problem.
Thanks heaps for your reply!!
update
So I can use my phone normally when it's plugged in. However, even when I power off the phone, I get the flashing LG logo and it won't turn off. What might the problem be?
420blazed said:
So I can use my phone normally when it's plugged in. However, even when I power off the phone, I get the flashing LG logo and it won't turn off. What might the problem be?
Click to expand...
Click to collapse
As i mentioned it's your battery.
Even if you over charge it,empty it while you are on TWRP and recharge it,your battery won't work like it supposed to.
Before two months or so,i got this problem(same as you)
I tried charging it all day,emptying it via TWRP(took me about 3hours+ with full brightness to empty it)and recharged it.After that i booted it (while plugged in) and after it booted,i used it about some seconds without the charger and it started again bootlooping.
So i decided to buy a new battery,bought it,removed the old one and inserted the new one,and it worked better than the factory one.
I Hope that my little story helps.
Greetings.
Sotiris02 said:
As i mentioned it's your battery.
Even if you over charge it,empty it while you are on TWRP and recharge it,your battery won't work like it supposed to.
Before two months or so,i got this problem(same as you)
I tried charging it all day,emptying it via TWRP(took me about 3hours+ with full brightness to empty it)and recharged it.After that i booted it (while plugged in) and after it booted,i used it about some seconds without the charger and it started again bootlooping.
So i decided to buy a new battery,bought it,removed the old one and inserted the new one,and it worked better than the factory one.
I Hope that my little story helps.
Greetings.
Click to expand...
Click to collapse
ok thanks so much!