Hello,
My OnePlus 3 just stopped working today, wihtout any reason, apparently.
I am able to boot on the OnePlus logo, I see the red dots turning indicating that the system is booting, but after few seconds the dots stop moving and the phone instantly turns off (the screen become black and nothing appears).
I can :
- Boot on the recovery : I wiped everything, flashed a stock ROM from OnePlus using the adb sideload with success, but the booting problem remains.
- Boot in fastboot mode : but the phone is locked and I cannot flash anything here.
Other observations :
- My battery is fully charged
- Storage is encrypted
Can anyone help me ? I don't have the financial ressources to buy another phone, so any help will be greatly appreciated...
try these option ..
https://www.youtube.com/watch?v=UUdDUfe7yUY
or
https://www.youtube.com/watch?v=O2_x9SnJ1Ak
kingviking said:
try these option ..
https://www.youtube.com/watch?v=UUdDUfe7yUY
or
https://www.youtube.com/watch?v=O2_x9SnJ1Ak
Click to expand...
Click to collapse
I've done it, but it didn't solved the problem.
Now, the problem is fixed. This is what I did : I unplugged the phone and let it reboot constantly overnight. At the morning, the battery was very low and the phone was off. I turned on the phone and it worked...
How the hell can this be possible ? What kind of problem is this ?
Related
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
Hello guys,
2 days ago my phone randomly bricked itself. It wasn't rooted or anything, everything on it was stock (I've been using it for 2 years).
Before the brick, I had the screen flickering issue, my WiFi stopped working and the sound also (this happened during a period of 2 months) - during this period my battery started draining very fast, I could use the phone for max 2 hours per day (stand-by or use, doesn't matter).
So 2 days ago I ran out of battery and left the phone to charge during the night. When I woke up, I tried to turn the phone on but at first It got stuck at the PIN insertion, and after rebooting it twice it just got stuck in a boot loop.
So what I did was follow the TOT guide and tried to flash a stock rom. All went well until I tried to do a factory reset before initial boot - I got a kernel crash and my phone is unable to enter download mode since this moment (the loading screen shows up, and once it loads the screen goes black and my phone is recognized as qualcomm. etc).
At this moment I found about BoardDiag and used the software in order to try to repair my phone. Everything works well with BoardDiag, but once it finishes it's job reboots, I get kernel crashes yet again and I am still unable to enter download mode (It's like the program didn't do anything and the phone just reverts itself to It's previous state).
So is this a hardware issue or am I doing something wrong?
Anyone?
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
this is the best method so far.
replace your battery as known to cause corruption boot problems when dying
Also try this..... download LG mobile support tool and install + run, ignore start upgrade > battery out > battery in (dont power on) USB cable in pc not phone > hold volume up plug in usb to phone, you will get download mode in blue in box on phone > now on pc > LG mobile support tool > choose options then UPGRADE RECOVERY. will take 57+ mins to complete (over 1 hour) it might seem stuck frozen at 10% to 22% it's not just wait it out...
Jahanzaibawan said:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
this is the best method so far.
Click to expand...
Click to collapse
As I said in the thread, I've already tried this but when the phone reboots and when I try to enter download mode again the phone is not being recognized again.
My Nexus 5x that was running 8.1 just randomly turned off yesterday and won't boot into android. Sometime later i tried to turn it back on and it worked and it turned off by itself 2 mins later. i somehow manged it to get into fastboot mode and I then unlocked the bootloader and flashed the stock firmware . But that did not help at all , in fact the phone was now completely dead and it only goes into fastboot sometimes while the other times it being stuck in a bootloop . while luckily when it went into fastboot, i have tried installing different boot images like boot4core but it still wont do anything its really weird,sometimes it doesn't respond to any key combination while sometimes it would go normally into fastboot. Need help , i Have no clue!! plzzz
Same Problem here! Running 8.1 and tap Uppdate Chrome and Alexa App, that the Phone freez and Reboot. After reboot he try to load the apps but freez. Now it wont boot to system and recovery say no command. When i now will enter Recovery the Phone reboots.
No open bootloader and no root. Stock 8.1 Rom from Google
Edit: Try to start Phone in Secure Mode (When Google Logo Popps up press Volume -) Say the System is Corrupt and do a Factory Reset. After Reset the Phone stuck on Boot too
Edit Edit: OK think thats the CPU Hardware Bug. Phone dont start anymore...
keltemp said:
My Nexus 5x that was running 8.1 just randomly turned off yesterday and won't boot into android. Sometime later i tried to turn it back on and it worked and it turned off by itself 2 mins later. i somehow manged it to get into fastboot mode and I then unlocked the bootloader and flashed the stock firmware . But that did not help at all , in fact the phone was now completely dead and it only goes into fastboot sometimes while the other times it being stuck in a bootloop . while luckily when it went into fastboot, i have tried installing different boot images like boot4core but it still wont do anything its really weird,sometimes it doesn't respond to any key combination while sometimes it would go normally into fastboot. Need help , i Have no clue!! plzzz
Click to expand...
Click to collapse
My daughters phone just started doing the same thing this morning. Haven't gone through any tests yet, but it is constantly restarting. Can't get it to go into recovery through normal means.
Since a few months, I'm facing this problem. The phone is working OK when I can get to the system, but If I turn it off or the battery runs off, it gets stuck on a loopboot: the Mi logo shows and restarts itself after a few seconds. Can't access the recovery mode (it just restarts again to the Mi logo), fastboot works tho'.
The only way I have to get to the system is to start the Fastboot Mode, keep the phone on it to drain the battery and once it's empty, plug it to the charger and try to boot 15-20 times until it magically works.
I've never unlocked the bootloader or tried to install anything, the ROM and Recovery are the Xiaomi's stock EEA. I'm on MIUI 13.
Any ideas about how I can fix this weird behavior? Anybody has faced the same problem?
Thanks for reading/helping and happy new year to you all!
helicida said:
Since a few months, I'm facing this problem. The phone is working OK when I can't get to the system, but If I turn it off or the battery runs off, it gets stuck on a loopboot: the Mi logo shows and restarts itself after a few seconds. Can't access the recovery mode (it just restarts again to the Mi logo), fastboot works tho'.
The only way I have to get to the system is to start the Fastboot Mode, keep the phone on it to drain the battery and once it's empty, plug it to the charger and try to boot 15-20 times until it magically works.
I've never unlocked the bootloader or tried to install anything, the ROM and Recovery are the Xiaomi's stock EEA. I'm on MIUI 13.
Any ideas about how I can fix this weird behavior? Anybody has faced the same problem?
Thanks for reading/helping and happy new year to you all!
Click to expand...
Click to collapse
Did you solve it? mine too acts so weird, it starts to call, reboots, and so on.
SubwayChamp said:
Did you solve it? mine too acts so weird, it starts to call, reboots, and so on.
Click to expand...
Click to collapse
Nope. One day it turned off and I never could boot back in again. Sorry.
..