Hello, yesterday my phone started a boot loop. I managed to flash an official rom jelly bean 4.3 and i erased all data.
After flashing the phone worked for 2-3 with no problem, but after that it stuck on boot loop again.
The weird thing is that when i plug in the power adaptor the phone boots normally, it works ok, but when i unplug it after a few hours suddenly restarts and stuck on boot loop.
Does anyone know what to do?
My phone is Galaxy s4 gt-i9505 jelly bean 4.3 official
sotos_2002 said:
Hello, yesterday my phone started a boot loop. I managed to flash an official rom jelly bean 4.3 and i erased all data.
After flashing the phone worked for 2-3 with no problem, but after that it stuck on boot loop again.
The weird thing is that when i plug in the power adaptor the phone boots normally, it works ok, but when i unplug it after a few hours suddenly restarts and stuck on boot loop.
Does anyone know what to do?
My phone is Galaxy s4 gt-i9505 jelly bean 4.3 official
Click to expand...
Click to collapse
What rom were you on before you flashed the stock 4.3? Also what bootloader and baseband is your phone currently on?
I was at jelly bean 4.3 before but rooted...
Here are the infos
sotos_2002 said:
I was at jelly bean 4.3 before but rooted...
Here are the infos
Click to expand...
Click to collapse
That looks fine.
Try wiping your cache and data again.
I had the same problem replaced my battery since you have still a warranty on your phone go to the store where you bought your phone and let it replace under warranty.
the original battery is from a bad serie that starts to swell after a month or 2. check out this thread:
http://www.androidauthority.com/galaxy-s4-battery-swelling-free-replacements-samsung-284308/
Yes probably your battery. Just bad luck.
Same problem here. a new battery is also the fix?
Streykatorato said:
Same problem here. a new battery is also the fix?
Click to expand...
Click to collapse
Had the exact same problem, phone would only boot up with power cable connected. Happened right after the 4.3 update, so I thought this was connected, however it wasn't. After a battery exchange the phone has been working fine every since.
Acer4605 said:
I had the same problem replaced my battery since you have still a warranty on your phone go to the store where you bought your phone and let it replace under warranty.
the original battery is from a bad serie that starts to swell after a month or 2. check out this thread:
http://www.androidauthority.com/galaxy-s4-battery-swelling-free-replacements-samsung-284308/
Click to expand...
Click to collapse
Yes indeed! It was a battery problem! My battery was swollen up!
Related
i rooted my 2 day old nexus 4 and updated to official 4.3.. all was fine until i flashed a kernel, the next morning the the phone just started to to endlessly bootloop
master resetting didn't work, flashing stock didn't work, was about to flash 4.2.2 while in bootloader and suddenly turned off... no power at all
now my phone is dead
i've looked everywhere!! i need help!!! Thanks
qaz2453 said:
i rooted my 2 day old nexus 4 and updated to official 4.3.. all was fine until i flashed a kernel, the next morning the the phone just started to to endlessly bootloop
master resetting didn't work, flashing stock didn't work, was about to flash 4.2.2 while in bootloader and suddenly turned off... no power at all
now my phone is dead
i've looked everywhere!! i need help!!! Thanks
Click to expand...
Click to collapse
No led? No nothing?
Fixed below... Threat can be removed IMO.
no LED no power ...nothing
it also made a funny sound, and not i can hear rattling inside the phone!!!
Ive gave my phone back to Asda Direct for a new one...new one is coming in 2 days hope that wont go wrong
thanks for your help
EDIT: got my new phone and its working great!!! loving the nexus 4!
I borrowed my Nexus4 to my sis for a couple of days. When I set it up for her (after Factory resetting it from the Settings Menu) everything was working fine. Now that she gave me the phone back it was stuck in the boot screen. I also realized that she forgot to give me the SIM Card Holder back which is now in her wallet. She told me that the guys at the mobile phone operator removed her SIM Card without turning the phone off.
I tried flashing Stock Android Firmware a couple of times. I tried it with 4.3.0 and 4.4.0. It always got stuck in the Boot Animation. The only Firmware that boots up to Android is 4.2.0. Even when i do a regular OTA update to 4.3.0 it gets stuck in the Boot Animation.
Is it possible that the Nexus4 is not booting up without a inserted SIM card. I know this sounds stupid, but it is the only explaination i have.
Did someone else experience the same issues?
Update1
I found out, that it's also booting up from 4.2.1. then i got a regular 4.2.2 OTA update which worked too. now was stuck with "Starting apps" after upgrading to 4.3 via ODA Update. Restarting the phone got me stuck in the Boot Animation again. I think I'm gonna wait until i can test it with a Sim Card.
The Sim card has nothing to do with whether the phone boots up or not. You need to wipe the phone clean and flash the factory images. Report back after.
Sent from my Nexus 4 using Tapatalk
ragerino said:
I borrowed my Nexus4 to my sis for a couple of days. When I set it up for her (after Factory resetting it from the Settings Menu) everything was working fine. Now that she gave me the phone back it was stuck in the boot screen. I also realized that she forgot to give me the SIM Card Holder back which is now in her wallet. She told me that the guys at the mobile phone operator removed her SIM Card without turning the phone off.
I tried flashing Stock Android Firmware a couple of times. I tried it with 4.3.0 and 4.4.0. It always got stuck in the Boot Animation. The only Firmware that boots up to Android is 4.2.0. Even when i do a regular OTA update to 4.3.0 it gets stuck in the Boot Animation.
Is it possible that the Nexus4 is not booting up without a inserted SIM card. I know this sounds stupid, but it is the only explaination i have.
Did someone else experience the same issues?
Update1
I found out, that it's also booting up from 4.2.1. then i got a regular 4.2.2 OTA update which worked too. now was stuck with "Starting apps" after upgrading to 4.3 via ODA Update. Restarting the phone got me stuck in the Boot Animation again. I think I'm gonna wait until i can test it with a Sim Card.
Click to expand...
Click to collapse
Hey, I met the same problem, have you solved it? could you tell me how to solve that? that drive me crazy.
I have read some posts that anything newer than 4.2.2 won't boot if the imei is not being displayed properly by dialing *#06#.
Same issue
Hi
How did you resolve this as I am having the same issue and nothing is working? thanks
tpc74 said:
Hi
How did you resolve this as I am having the same issue and nothing is working? thanks
Click to expand...
Click to collapse
See if your IMEI and your baseband is getting displayed. Otherwise you might have to flash the baseband of your android version.
i have the same problem, i just dont know what to do, i tried the cyanogenmod, 4.4.0 , 4.4.2 , 4.4.4 and i just tried 5.0 and nothing works, just 4.2 , and i have no problems with the baseband :crying:
__bump
any solution? I have the same problem
Y not root it and use a custom rom...Chroma 6.0 Marshmallow rom is one of the best out there...any specific reasons for sticking with stock rom??
Sent from my Nexus 4 using Tapatalk
When I had this a flash a new modem radio and I was fine...
I had a similar issue as you. Could not get past 4.2 version. Although I could get up to 4.3 by flashing an older modem radio after flashing the stock 4.3 image.
My issue was a broken proximity sensor. Any other version past 4.2 would not get past boot animation because the proximity sensor was not working (properly). I did a RMA and they changed the proximity sensor. After that, I could update all the way to 4.4 without issue. Still working today!
It's just a suggestion, but could you check if your proximity sensor is working on the 4.2 build? https://play.google.com/store/apps/details?id=ctsr.android.SensorTest&hl=en can help.
Or you could let someone call you and see if the screens turns off when you put the phone up to your ear and lights up again when you put it away from your ear.
Hey Guys,
I am facing a very strange issue with my N4. On Friday Night, I kept my phone for charging overnight and it was working as usual. on Saturday morning, I noticed that the phone was unresponsive and was showing a blinking red light. Tried to charge via various means but it was of no use. Finally went to a LG service centre were they could revive the phone but it was stuck in a bootloop. He suggested me that he will downgrade from KK 4.4.2 to JB 4.3 but still the phone was stuck in bootloop.
LG guy said that he doesn't have answer why this is happening. He said change the motherboard that will fix it. That is a very costly option which I cannot take. and he mentioned that there are tools online which will help it work but as an authorized service centre place he can't do it.
So here's what I did after reading several blogs, videos and but got stuck in the same place.
1. Booted in Bootloader mode, flashed stock JB 4.3 using Wugfresh Nexus Toolkit selecting the option Softbrick / Phone in bootloop.- Result : Stuck at Bootloop.
2. Flashed CWM Touch via fastboot, Went to the CWM recovery, Cleared the dalvik cache, Data, User data, Cache, Reflashed a Stock JB 4.3 - Result : Stuck at Bootloop.
3. Flashed KK 4.4.2 , again using the Wugfresh Nexus Toolkit - Result : Stuck at Bootloop.
I tried searching google for bootloops due to motherboard issues just to be clear from my side. The solution what LG guy gave sounded like I have no idea, lets replace the entire thing. Which i am pretty sure is not the correct method.
What my phone can do at this moment is:
1. boot into bootloader.
2. Communicate with the PC using Fastboot.
I know Nexus 4 is a developer phone and easy to recover from brick status due to its intended purpose. Please advise what else can I do to revive my Nexus 4 and let me know in case I haven't done any thing which can restore this thing back to normal.
Thanks and Cheers,
Sid
siddhu2411 said:
Hey Guys,
I am facing a very strange issue with my N4. On Friday Night, I kept my phone for charging overnight and it was working as usual. on Saturday morning, I noticed that the phone was unresponsive and was showing a blinking red light. Tried to charge via various means but it was of no use. Finally went to a LG service centre were they could revive the phone but it was stuck in a bootloop. He suggested me that he will downgrade from KK 4.4.2 to JB 4.3 but still the phone was stuck in bootloop.
LG guy said that he doesn't have answer why this is happening. He said change the motherboard that will fix it. That is a very costly option which I cannot take. and he mentioned that there are tools online which will help it work but as an authorized service centre place he can't do it.
So here's what I did after reading several blogs, videos and but got stuck in the same place.
1. Booted in Bootloader mode, flashed stock JB 4.3 using Wugfresh Nexus Toolkit selecting the option Softbrick / Phone in bootloop.- Result : Stuck at Bootloop.
2. Flashed CWM Touch via fastboot, Went to the CWM recovery, Cleared the dalvik cache, Data, User data, Cache, Reflashed a Stock JB 4.3 - Result : Stuck at Bootloop.
3. Flashed KK 4.4.2 , again using the Wugfresh Nexus Toolkit - Result : Stuck at Bootloop.
I tried searching google for bootloops due to motherboard issues just to be clear from my side. The solution what LG guy gave sounded like I have no idea, lets replace the entire thing. Which i am pretty sure is not the correct method.
What my phone can do at this moment is:
1. boot into bootloader.
2. Communicate with the PC using Fastboot.
I know Nexus 4 is a developer phone and easy to recover from brick status due to its intended purpose. Please advise what else can I do to revive my Nexus 4 and let me know in case I haven't done any thing which can restore this thing back to normal.
Thanks and Cheers,
Sid
Click to expand...
Click to collapse
Try not using a toolkit, and doing it manually instead:
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
abaaaabbbb63 said:
Try not using a toolkit, and doing it manually instead:
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
siddhu2411 said:
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
Click to expand...
Click to collapse
Flash the KitKat factory image. That might solve the mobile signal issue.
The battery one, if not solved my the kitkat image, might be a hardware fault.
abaaaabbbb63 said:
Flash the KitKat factory image. That might solve the mobile signal issue.
The battery one, if not solved my the kitkat image, might be a hardware fault.
Click to expand...
Click to collapse
So chances that the Motherboard is screwed?
siddhu2411 said:
So chances that the Motherboard is screwed?
Click to expand...
Click to collapse
Or the battery itself. If the motherboard was busted, then the phone wouldn't have booted.
siddhu2411 said:
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
Click to expand...
Click to collapse
Did you get this fixed? Were you able to upgrade beyond 4.2.2?
My Nexus is currently bootlooping if I try and upgrade beyond 4.2.2 - though my battery seems fine. I'm wondering if there's some similar problem though.
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
I accidentally posted in Android development. so sorry
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
fatboyinlycra said:
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Click to expand...
Click to collapse
I'm in a doubt about the battery, I think it's slightly swollen.
I guess I'll give it a try.
shaggyskunk said:
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
Click to expand...
Click to collapse
First thing I did.
Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
dineshh said:
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
Click to expand...
Click to collapse
Battery issue, solved with replacement
jetbruceli said:
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
Click to expand...
Click to collapse
Solved with battery replacement
huge thanx
Hello,
I received an OTA update with Android 6.0.1 and after that my S5 entered into a Boot Logo Loop unless I connect it with the USB Charger. If the phone is connected to the USS charger it reamains powered and if I disconnect it get the reboot loop (Logo Boot Loop).
I have tried:
Factory Reset
Wipe Cache
Installed with Odin the Firmware (Several Regions) also an Android 5.0 Firmware
I really don't know what to do now? Hoy do I choose another firmware from Sanmobile.com? Mine is the G900H
I hope you guys can help me to get my phone back.
Thanks in advance.
Problem SOLVED!!! Got a new battery and my phone is working again.
Could Samsung thru its OTA updated damage the battery to make you get the new galaxy?
My battery was fine until I got the OTA update!!
chure_63 said:
Problem SOLVED!!! Got a new battery and my phone is working again.
Could Samsung thru its OTA updated damage the battery to make you get the new galaxy?
My battery was fine until I got the OTA update!!
Click to expand...
Click to collapse
hmm ive been having random issues myself, where did you purchase your battery?
could high cpu usage & therefore temperature or voltage during the installation process cause something to burn out in the battery? how old was it?
kn00tcn said:
could high cpu usage & therefore temperature or voltage during the installation process cause something to burn out in the battery? how old was it?
Click to expand...
Click to collapse
I had mine rooted with 6.0.1 G900TUVU1GPE1_G900TTMB1GPE1_TMB using TWRP and SuperSU, 2 weeks after I started having these reboot issues, it stops when the phone gets plugged in. The only other solution if the battery doesn't fix it ( I found a Samsung Original for 9 bux on amazon), would be replacing the mother-"Logic" board (not very logical if it can't tell you why the unit restarted).
It's possible too
kn00tcn said:
could high cpu usage & therefore temperature or voltage during the installation process cause something to burn out in the battery? how old was it?
Click to expand...
Click to collapse
My phone I bought this year, It had a battery Made in China, the battery I just bought was Made in Vietnam, it seems to have fixed the problem