Note 4 wont turn on, "cannot boot normal" and "downlaoding target, dont turn off"
Its a Note 4 SM-N910F, Android 6.0.1, BB N910FXXU1DPE2, kernel 3.10.40-7733605 [email protected] #1
i feel I have tried everything... History:
Phone has been working fine for a year, upgraded to 6.0.1 no problems about 2 or 3 months ago. no new apps installed. Last week it started getting very laggy, keyboard strokes took for ever to register. I thought, ok, time to to a factory reset to blow out any old cobwebs. Did it via the menu. However the phone froze midway thought. I left it for an hour and then pulled out the battery. I popped it back in and it performed the reset without me having to press anything. Cool, thats good I thought.
Now I was going to change the battery, so I powered off as normal and put my other 2 week old original samsung battery in, and it would not power on. After a few reinsertions it powered back on. I though i have to do another reset. So I tried, and it would not reset. It just died. I cant restart the phone, it dies. If I shut it down normally. it wont turn on back on, I have to take out and reinsert the battery multiple times, holding down the powerbutton between to discharge. this can take up to 10 tries now. Sometimes it will go th the unable to bot in normal mode and "downloading , do not turn of target, but it will stay there for ever, more than an hour.
Every 15-20 tries it would turn on, let me get in via pin, only to start freezing up within a min, and then die again. Somewhere I read that a guy hada similar problem, and he used wakelock and that worked, on level 4. I managed to download that and used it, and hey presto, it works!
Now I had to power down the phone for a reason, and it took me about 30 min of battery and powerbuttonholding before it managed to boot up, and I was quick enough to start wakelock on level 4.
It wont boot in to safe mode, it wont boot in to recovery mode, it wont boot in to the factory reset mode. Its the same with either battery, and different cables.
Any ideas what i can do here, or what could be wrong? I havent gotten it wet or banged it.
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
armstrongracer said:
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
Click to expand...
Click to collapse
are you still under warranty? i sent mine to a samsung center, the guy recognized the problem as the motherboard, said I wasnt the first. That was 3 weeks ago, they are STILL waiting for the parts. They say the Samsung factory are way behind with repair parts, etc etc. I am hoping it will go under warranty. Ill update when I know!
I've been having the same problem that started yesterday morning. I've tried a few different solutions but nothings worked, I get the feeling that my phone is dead and I'm not in warranty either. I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
neils0911 said:
I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
Click to expand...
Click to collapse
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
bonfilet said:
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
Click to expand...
Click to collapse
Definitely...surely it couldn't have been that hard to make a device with a battery that was still removable on the newer phones. It's frightening how many forum posts I've found with people having their phones just brick out of nowhere (and that's just the note 4). I've given up trying to fix mine, I've tried every method I could find and nothings worked. I can only assume that this problem is simply the motherboard of the phone not working anymore. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
neils0911 said:
. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
Click to expand...
Click to collapse
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
mymigi said:
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Click to expand...
Click to collapse
If you are able to boot it into Download Mode then you should Download Stock Rom file for Galaxy Note 4 from Sammobile and Flash it through Odin..
Everything will be OK... ?
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can find here firmware for N910A , 5.1.1 and 6.0.1 : https://simunlockremote.com/firmware-support/
bonfilet said:
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
Click to expand...
Click to collapse
I think the camera on the note 4 is absolutley terrible. I might even go so far as to say the pictures are unusable. the applied noise reduction renders everything splotchy, colors are off and its not sharp at all. and Im not talking dark conditions here.
Anyway, my phone was repaired under warranty and is back to working as it should. It was indeed the motherboard, so if you have the same troubles I had, those are your best bets.
I don't think replacement via warranty will be available. I will attempt to power into download mode and verify if I can get it back up and running. If not, a good ole paperweight.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here ..
https://www.androidfilehost.com/?fid=24459283995298017
---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here. .
https://www.androidfilehost.com/?fid=24459283995298017
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
onno72 said:
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
Click to expand...
Click to collapse
My phone is also random Rebooting
It also shuts down at 25% of battery remaining, Have you also faced similar issue?
Download the app "Wake Lock" and run the Partial Wake Lock option. Apparently the updated software impacts the CPU. For the restarting issue, put it in the freezer for a couple minutes. You may have to take the battery out once, but it has worked for me every time.
This looks very much like the issue reported here:
https://forum.xda-developers.com/no...-error-fix-t3434335/post72944466#post72944466
There are temporary fixes (wakelock), but ultimately this is a harware issue, and the fix is a new motherboard.
I think that underlying it is a problem with heat affecting the eMMC chip or its connection to the motherboard.
See also:
https://us.community.samsung.com/t5...ePhones/thread-id/12183/highlight/true/page/1
http://www.classlawdc.com/2017/04/25/investigation-samsung-galaxy-note-4-mmc_read-failed-defect/
Hey can u pls get me the stock firmware for n910gddu1dpb4
You might find this interesting. Since I couldn't get mine to power up at all, I called Samsung tech and they quoted me $75 to fix it and they would pay for shipping. I figured it was better then getting another phone off Swappa. 2-3 weeks later i get an email that they are repairing it under warranty at no cost to me. I got a refurbished phone since i know my IEMI number was different. they didn't explain why. Anyway, I got lucky i guess.
Related
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
this is a problem i have just posted about a couple of mins ago
but i can get it recovery mode and fatory reset with the vol up, home and power
then it will boot but obviously i have to then reset everything from scratch which is really annoying so anyone got any idea re this
lucky for you that you can get into recovery. Right now I'd be happy with a hard reset, it doesn't take long to rebuild the setup. I'd like to know who decided to remove the recovery mode, that's evil and keeps me from simply resetting the device.
its all the apps re downloading and installing them and resetting up accounts and swype and all that lot need a fix asap
do you know what version of andoid you are running
yes but at least you can get a working phone again, I can't without being able to get into any boot menus. Honestly it only takes 30 minutes to setup again from scratch. I'm on 2.1 and what I find at least on my HTC when it had 2.1 is that I setup the google account, let it sync contacts etc, then from Market Downloads I'll see listed all my apps that were previously installed. As long as I don't leave that screen I can install each app one after the other. Or a proper backup....
Any other magic key combos to reset this thing???
did you try hooking up to kies?
Yes but that does nothing since it never fully boots.
3rdcoast said:
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
Click to expand...
Click to collapse
Same thing happened to my phone, but a factory reset did nothing. The internal SD card gave out. Phone is now sent away for 3 - 6 weeks awaiting repair.
my phone did this to me today too, I was just about to post about this when I saw this thread.
So its an SD Card problem? theres no hope of getting it fixed without sending it in?
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
3rdcoast said:
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
Click to expand...
Click to collapse
i went to best buy today to try and exchange it, and apparently they only have a 14 day exchange policy with phones despite it saying 30 day on the receipt, anyhow i phoned samsung and they said i have to go through bell, even though im using the phone on telus, so that should be interesting.
So all the people that are having this problem have the Bell model?
Today i got mine off eBay, as soon a i turned it on, i get exactly the same thing.
It wont load into Android, i see that galaxy S logo and then black screen.
If i go into recovery i see "cant mount SD Card".
The more is search this forum the more i see that all the people with this problem are owners of the Bell i9000M model.
I seriously think they have some defect with the manufacturing line of the phone.
Have you guys installed any firmware on your phone before this happened?
mine is like that out of the box.
Mine is the same Bell model. There seems to be some issues with them which makes the lack of download mode even more dangerous. Right now it doesn't feel like the warranty is going to cover us for problems not our fault. I hope they replace it next week but if it still lacks download mode I'll remain nervous.
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
bigc_13 said:
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
Click to expand...
Click to collapse
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
I haven't flashed any 3rd party roms. I did do the official update via Keis which even at the store today they reminded me that I should do the update.. That update seemed to go well and has been working for over a week until I turned it off for an hour. It still isn't clear if the disabled 3 button mode is hardware or software related but we all seem to have that in common too. So before they dismiss the whole thing and we get hosed over technicalities such as unlocking it should be clear that there are clear defects in these phones as far as I can tell.
I want to be comfortable that I'm not left out of hundred of dollars just because I choose to buy it outright and not be tied to contracts. Samsung has to play nicely because it is their phone. Bell has to play nicely because they are bringing them in and distributing to retail. What carrier I use should be irrelevant because the problems are not related to usage.
FYI, the clerks went off for conference to decide if I somehow got the phone against policy. Either they trust my story or I got mine moments before they got the memo about not selling outright.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Same here, stock JH2 from Kies. Not rooted. Boots to Galaxy S logo, then black screen. Mine is sent in for repair... Almost two weeks now.
Seeing more and more of this being posted. There is obviously some issues with this phone.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Our posts crossed..
Yes I believe mine had the JH2, the official keis offered firmware. I was looking forward to the biggie update at the end of the month so wasn't about to risk bricking before then. Irony stepped in anyway.
I'm a bit nervous until I get a new one. At that point if the 3 button mode still doesn't work I'll remain nervous that I'll get another potential brick.
edit-> yes, I simply shut it down for an hour or two to use the SIM in another phone to test that phone. At next boot it died. I knew something was wrong when the logo stayed up for much longer.
I have the 3 buttons enabled so it is not related to the 3buttons being disabled, however when i boot into recovery it clearly displays an error that it can not find the internal SD.
There is definitely something wrong with the Bell Galaxy S corrupting itself.
I bought mine from an eBay seller, he is saying the phone booted fine when he shipped it but when i opened the box today i only got this black screen after logo.
Gladly the seller will take it back.
Maybe this is why there are shortages everywhere in Canada. I hope the caught this up and are fixing it with the new batch.
Hi,
Not sure what is happening to my phone. I have had stock 4.2.2 rooted with CF auto root for months and had no problems. A few weeks ago my phone started to randomly shut down, not properly just complete power off in an instant. It would then start to reboot and get to the Samsung S4 logo screen before powering off again and trying to reboot and then gets stuck in a constant loop. At first I was able to just reinstall CF root with Odin and it would start up OK. I could also get it to start by re-installing Philz recovery.
Now though, that doesn't work so this morning I installed JB 4.3 I9505XXUEMK8-PRE-ROOTED-KNOX-FREE-ODEX-FULL.tar.MD5 and it says that it is rooted and everything seems to be OK but after an hour or so it has started to randomly shut down again. If I attempt to go into recovery (stock) and clear the cache partition it will reboot normally and run for a while until I use an app and do it again. Am I doing something wrong here or is my phone just knackered?
Phooka
Maybe is coz the RAM is overloaded. Take a look in:
- Press HOME button for 2 secs
- U will see 3 icons in the bottom. Click on the "cheese"
- Tab "RAM"
- If ur phone use more of 1 GB of RAM for run ur apps maybe will be time of delete bloatware
I had the same problem in GT-I9500, I had to get it repaired in a service center.
There was a problem with mother board to charger port connection..
Hope it helps you!
Random Shutdown
praveen_kalasa said:
I had the same problem in GT-I9500, I had to get it repaired in a service center.
There was a problem with mother board to charger port connection..
Hope it helps you!
Click to expand...
Click to collapse
Thanks. Probably not as I've been told that warrantee will be void now as I've flashed whilst having Knox installed which I understand to be irreversable
random shuts and boot loops
Joku1981 said:
Maybe is coz the RAM is overloaded. Take a look in:
- Press HOME button for 2 secs
- U will see 3 icons in the bottom. Click on the "cheese"
- Tab "RAM"
- If ur phone use more of 1 GB of RAM for run ur apps maybe will be time of delete bloatware
Click to expand...
Click to collapse
Thanks. its running at 1.04 out of a possible 1.78G. When cleared it drops to 847 MB.
I Am Phooka said:
Thanks. its running at 1.04 out of a possible 1.78G. When cleared it drops to 847 MB.
Click to expand...
Click to collapse
If u wanna try to recover some RAM u can delete some bloatware that u dont use. Tc with what u delete. I let u some info about if u wanna try -> HERE
I have this problem, I swear it is because of the dodgy battery. (I have the BD battery)
When I plug it in to charge all works again properly.
Last night my battery was showing in the high 60's the phone went off. When I put charger in the battery was at 3%!
Very annoying, going to take to Geek Squad tonight and see if they wil lreplace battery. Guy here at work has same phone, different battery derial number and no problems at all.
Hopefully they will change the battery, I don't have any paperwork with me but the phone is obviously within the 1 year warrenty.
Random Shutdown and boot loop
choccy31 said:
I have this problem, I swear it is because of the dodgy battery. (I have the BD battery)
When I plug it in to charge all works again properly.
Last night my battery was showing in the high 60's the phone went off. When I put charger in the battery was at 3%!
Very annoying, going to take to Geek Squad tonight and see if they wil lreplace battery. Guy here at work has same phone, different battery derial number and no problems at all.
Hopefully they will change the battery, I don't have any paperwork with me but the phone is obviously within the 1 year warrenty.
Click to expand...
Click to collapse
Interesting. I have noticed a couple of times when I look at the battery stats that it has drained from say 90% to 3% in less than 1min, just a verticle line. When I plug it in to charge it says that it's at 90% or whatever it was. Other times it needs charging and is almost dead. It's as though it has shorted out. I wonder if that is the problem here.
random shuts and boot loops
Joku1981 said:
If u wanna try to recover some RAM u can delete some bloatware that u dont use. Tc with what u delete. I let u some info about if u wanna try -> HERE
Click to expand...
Click to collapse
Thanks for that. It's quite a list. I'll go through it and remove the ones i think i can do without and see how it goes.
Same Issue
I have the same problem with my I9505
- It shuts down randomly (sometimes you see a few seconds in advance that your connection to the mobile antennas disconnects), when you look at it, in the middle of a phonecall, ... whenever it's nog plugged in to the power of external battery
- It's almost impossible to get it powered on again (gets stuck in a loop of rebooting: most times at the Samsung logo or after it's on for a few seconds), unless you connect your charger that is connected to the powergrid or external battery
- sometimes it resets the phonelanguage to default (so in stead of for example Dutch, everything is in English again)
I just cleared the cache and removed some programs...
Fingers crossed
--> I'll give an update if anything changes
Random Shutdown and boot loop
LinusN said:
I have the same problem with my I9505
- It shuts down randomly (sometimes you see a few seconds in advance that your connection to the mobile antennas disconnects), when you look at it, in the middle of a phonecall, ... whenever it's nog plugged in to the power of external battery
- It's almost impossible to get it powered on again (gets stuck in a loop of rebooting: most times at the Samsung logo or after it's on for a few seconds), unless you connect your charger that is connected to the powergrid or external battery
- sometimes it resets the phonelanguage to default (so in stead of for example Dutch, everything is in English again)
I just cleared the cache and removed some programs...
Fingers crossed
--> I'll give an update if anything changes
Click to expand...
Click to collapse
I've tried that as well. Didn't work. The problem you describe is exactly the problem I have. I have ordered another battery but I don't think it's that. I'll let you know if it is. I hadn't noticed that it always boots OK if it is plugged into the mains. Wish I knew what was causing the problems.
Random Shutdown and boot loop
So I think I am finally getting somewhere. I took this screenshot straight after it shut down and got stuck in a boot loop. So I plugged it into the mains and it started OK. The battery just gives up when i stress the device with a hungry app or when booting which causes a heavy drain on the on the power even when its got a healthy charge. Got a new battery on order. Take a look at the screenshot. You can see the battery instantaneously drops to zero charge until it's re-booted on the mains.:laugh:
LinusN said:
I have the same problem with my I9505
- It shuts down randomly (sometimes you see a few seconds in advance that your connection to the mobile antennas disconnects), when you look at it, in the middle of a phonecall, ... whenever it's nog plugged in to the power of external battery
- It's almost impossible to get it powered on again (gets stuck in a loop of rebooting: most times at the Samsung logo or after it's on for a few seconds), unless you connect your charger that is connected to the powergrid or external battery
- sometimes it resets the phonelanguage to default (so in stead of for example Dutch, everything is in English again)
I just cleared the cache and removed some programs...
Fingers crossed
--> I'll give an update if anything changes
Click to expand...
Click to collapse
in the list I forgot to mention that the known wifi's are also wiped. --> you have to connect to them again...
I too am having this exact problem; I'm glad to hear it is not only me, not that it helps any of us.
I posted in another thread, but the symptoms everyone here are describing are exactly what I am seeing:
- Sudden battery drop from anything (it's happened to me before about 5 minutes after unplugging from the wall socket) to zero; then phone goes into a loop unless I plug it back into the mains socket
- When plugging into the mains socket with this issue, sometimes the battery is empty and sometimes it shoots straight back up to where it was
- Plants Vs Zombies 2 is the sure-fire way for me to reproduce this issue
- examined logs (although not sure if the right one) using CatLog; nothing obvious (in fact the last line on one of the logs is litterally cut halfway through)
- Wifi connection details lost occasionally
I have reflashed about 4 other (4.3) ROMs (and I tried a 4.4 GE one too) and they all seem to do the same; I am wondering if it is something to do with the non-Knox modems required to flash the 4.3 ROMs as I don't think I had this problem before updating to 4.3. I don't have the time or patience to revert back to a 4.2 ROM to test this though.
I can go for a couple of days without this happening, but fire up PvZ2 and here we go again.
I too have a new battery on order (allegedly genuine from a well-known auction site), so I will update this thread when that arrives to see if it makes any difference.
I don't like this post for one reason.... it means that the problem I am facing won't solve with a format and a new fresh flash... :crying:
I was spending some time on XDA searching for a good stable firmware to flash because I am having your exactly same issues on my phone... I just tought my phone got a bit messy because I have 130 apps installed and a lot of stuff on it.. so I was just thinking of solving all my problems with a new rom... but then I found this 3d...
So you are telling me that my problem won't get solved so easely? How am I going to deal with a Phone that randomly shuts up??? I need my phone and over the last week it got always worse.. first it shut up at about 5pm.. (at ca 15% charge) then at 3pm and 50% charge... today it shut up at 11am and 80% charge... soon I won't be able to use my phone at all!!
I'm happy I backed up all my data today, but it still doesn't solve my problem since I really need my phone... :crying:
This evening I'm going to flash anyway... let's see what happens..
PS I own a GT-I9505 with 4.2.2 stock rom (root)
Random Shutdown and boot loop
Sorry to hear there's a few more out there with the same problem that I am having. AhHm... Sorry, WAS having. I tried re-flashing all sorts of ROMS from 4.2.2 to Echoe KitKat 4.4, flashed CF Root, reinstalled philz touch recovery god knows how many times all to no avail. I now know that it is nothing to do with your ROM or phone setup. It's Samsungs crappy battery. As soon as I put in my new battery problems solved. I have been running multi-window apps whilst having FB on in the background and watching a film all at the same time. If this was gonna crash it would have done by now.
Problem solved. Don't buy the cheap SPB £9.99 one on ebay it has lots of bad reviews. I got this one with no problems:
http://www.ebay.co.uk/itm/GENUINE-S...114?pt=LH_DefaultDomain_3&hash=item3f278d6f32
Hope this helps and don't forget the thanks meter.
I Am Phooka said:
Problem solved.
Click to expand...
Click to collapse
I'm glad you solved.. this means there could be a solution to my problem... in any case the fact that alla batteries here seem to fail in the same week is really strange!!
And the thing I hate most is that a 500€ phone shouldn't be dying after just some months!
After having spent some time googling around.. I found a solution... well, not exactly a solution... let's say I found the core of the problem...
I found some very interesting posts on the misfuncion on all Samsung S4 Batteries Made and Produced in China with SN starting with BD....
And guess what? my battery corresponds!!
If you look at the battery you will notice that it is a little "bumped" and not perfectly flat...
Here in Italy many users went to samsung customer service and got the battery replaced!
Tomorrow I will check to see if I can get a new battery... for now I'm happy to know exactly what to do in order to get my phone working again!
Samsung Batteries beggining with BD.
I Am Phooka said:
Sorry to hear there's a few more out there with the same problem that I am having. AhHm... Sorry, WAS having. I tried re-flashing all sorts of ROMS from 4.2.2 to Echoe KitKat 4.4, flashed CF Root, reinstalled philz touch recovery god knows how many times all to no avail. I now know that it is nothing to do with your ROM or phone setup. It's Samsungs crappy battery. As soon as I put in my new battery problems solved. I have been running multi-window apps whilst having FB on in the background and watching a film all at the same time. If this was gonna crash it would have done by now.
Problem solved. Don't buy the cheap SPB £9.99 one on ebay it has lots of bad reviews. I got this one with no problems:
http://www.ebay.co.uk/itm/GENUINE-S...114?pt=LH_DefaultDomain_3&hash=item3f278d6f32
Hope this helps and don't forget the thanks meter.
Click to expand...
Click to collapse
nioBee said:
After having spent some time googling around.. I found a solution... well, not exactly a solution... let's say I found the core of the problem...
I found some very interesting posts on the misfuncion on all Samsung S4 Batteries Made and Produced in China with SN starting with BD....
And guess what? my battery corresponds!!
If you look at the battery you will notice that it is a little "bumped" and not perfectly flat...
Here in Italy many users went to samsung customer service and got the battery replaced!
Tomorrow I will check to see if I can get a new battery... for now I'm happy to know exactly what to do in order to get my phone working again!
Click to expand...
Click to collapse
Yeah I found that out tonight also. I called samsung earlier today and they said if it is less than 2 years old they will repair it and I should send it to them. I have flashed so many ROMS since I purchased it last year and one or two with Knox which as we know registers that it has had a custom download which voids the warrantee so I thought it would be a waste of time sending it to them. Also I need my phone for work so it was easier to purchase a new battery.
Bad samsung batteries
nioBee said:
After having spent some time googling around.. I found a solution... well, not exactly a solution... let's say I found the core of the problem...
I found some very interesting posts on the misfuncion on all Samsung S4 Batteries Made and Produced in China with SN starting with BD....
And guess what? my battery corresponds!!
If you look at the battery you will notice that it is a little "bumped" and not perfectly flat...
Here in Italy many users went to samsung customer service and got the battery replaced!
Tomorrow I will check to see if I can get a new battery... for now I'm happy to know exactly what to do in order to get my phone working again!
Click to expand...
Click to collapse
Hi,
Do you have a link to the info? was it on an official samsung site?
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
I will follow up on the battery swap when mine arrives.
hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart
I've got a Note 4 (AT&T SM-N910A) that is having a problem with reboot looping. I've read some of the posts on this issue, but the solutions I've tried so far haven't worked. I'm kind of overwhelmed by the number of posts on this issue and trying to find solutions. I just want to list some of the symptoms I've had and things I've tried, and if anybody can suggest anything else to try I'd really appreciate it.
The phone started rebooting constantly, sometimes it makes to the home screen before rebooting, sometimes it doesn't even make it past the initial Samsung logo.
It rapidly got worse, the phone was completely locking up during various phases of booting up.
Plugging it into the charger doesn't help.
Completely drained and then charged the battery, didn't help.
Removed the microSD and SIM cards.
I just got a new battery, which didn't solve the problem, but improved so at least it is no longer locking up during the boot process.
Booted in safe mode, didn't improve.
I put the phone in the freezer for a couple of hours. This gave me enough time to install Wake Lock and enable the PARTIAL_WAKE_LOCK mode.
After the freezer and wake lock, I had maybe 5 minutes to transfer some files from internal storage before the reboot started up again.
I can get into recovery mode, where it seems stable, but I don't know if that can help me at all.
At this point I'm only hoping to recover some files from internal storage, then it's time to be done with this phone. Kind of sad that a smartphone that was an $800+ "flagship" barely lasts two years. Thanks
thepieguy said:
I've got a Note 4 (AT&T SM-N910A) that is having a problem with reboot looping. I've read some of the posts on this issue, but the solutions I've tried so far haven't worked. I'm kind of overwhelmed by the number of posts on this issue and trying to find solutions. I just want to list some of the symptoms I've had and things I've tried, and if anybody can suggest anything else to try I'd really appreciate it.
The phone started rebooting constantly, sometimes it makes to the home screen before rebooting, sometimes it doesn't even make it past the initial Samsung logo.
It rapidly got worse, the phone was completely locking up during various phases of booting up.
Plugging it into the charger doesn't help.
Completely drained and then charged the battery, didn't help.
Removed the microSD and SIM cards.
I just got a new battery, which didn't solve the problem, but improved so at least it is no longer locking up during the boot process.
Booted in safe mode, didn't improve.
I put the phone in the freezer for a couple of hours. This gave me enough time to install Wake Lock and enable the PARTIAL_WAKE_LOCK mode.
After the freezer and wake lock, I had maybe 5 minutes to transfer some files from internal storage before the reboot started up again.
I can get into recovery mode, where it seems stable, but I don't know if that can help me at all.
At this point I'm only hoping to recover some files from internal storage, then it's time to be done with this phone. Kind of sad that a smartphone that was an $800+ "flagship" barely lasts two years. Thanks
Click to expand...
Click to collapse
You probably have hardware that is failing (most likely the memory chips on the motherboard). On any of the reboots have you seen a screen like this: http://thedroidguy.com/2015/12/could-not-do-normal-boot-mmc_read-failed-error-on-galaxy-note-4-1052795 ? I've been told that the "ddi : mmc_read failed" message is an indication that the memory chips on the memory board are failing.
It's probably time to contact Samsung Customer Support (1-800-SAMSUNG). That's what I finally did and they repaired my Verizon Note 4 for $70.31 to "like new" condition. See my post here: https://forum.xda-developers.com/showpost.php?p=71863607&postcount=310.
Your mileage may vary, however. Someone else took the same approach and it is going to cost them more. See post here: https://forum.xda-developers.com/showpost.php?p=72258958&postcount=313. You don't have to agree to Samsung's repair estimate if you think it is too high. My understanding is that if you refuse they will send the phone back for no charge. Before I sent mine in I had mentally set an upper repair limit of $150 since you can still buy new Verizon Note 4's on Amazon for about $300.
Good luck.
Dwillian said:
You probably have hardware that is failing (most likely the memory chips on the motherboard). On any of the reboots have you seen a screen like this: http://thedroidguy.com/2015/12/could-not-do-normal-boot-mmc_read-failed-error-on-galaxy-note-4-1052795 ? I've been told that the "ddi : mmc_read failed" message is an indication that the memory chips on the memory board are failing.
It's probably time to contact Samsung Customer Support (1-800-SAMSUNG). That's what I finally did and they repaired my Verizon Note 4 for $70.31 to "like new" condition. See my post here: https://forum.xda-developers.com/showpost.php?p=71863607&postcount=310.
Your mileage may vary, however. Someone else took the same approach and it is going to cost them more. See post here: https://forum.xda-developers.com/showpost.php?p=72258958&postcount=313. You don't have to agree to Samsung's repair estimate if you think it is too high. My understanding is that if you refuse they will send the phone back for no charge. Before I sent mine in I had mentally set an upper repair limit of $150 since you can still buy new Verizon Note 4's on Amazon for about $300.
Good luck.
Click to expand...
Click to collapse
Hey thanks for your input. I haven't seen any kind of error screens pop up. $70 to have your phone reconditioned is a really good score for you. I was able to pull my phone from the freezer several times and at least got all of my photos and videos off, which was my primary goal.
Good morning all,
my 6p looks completely dead. I've installed the latest Android O factory image from the Google Developer site, flashed it and was running withot issues until today.
I was about to write a comment on Facebook, and then the phone freezed. After seeing how the phone was not recoverying, I tried a hard reset by long-pressing the power and both the volume keys. Then, the phone got a black screen, didn't vibrate, and now looks totally dead.
It's not charging or responding in any way, no matter how I press it. I'm quite confident the phone was over 50% when this issue occurred.
I don't really know what coul've caused this, but on my side, the preview was flashed cleanly with a complete factory reset, and I've only restored media files, without rooting.
Any ideas as to what should I do?
Do you get anything showing up on a computer when you plug it in?
jmaclean62 said:
Do you get anything showing up on a computer when you plug it in?
Click to expand...
Click to collapse
Hi jmaclean, nothing, not even in Windows Device Manager...
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Zwitterion said:
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Click to expand...
Click to collapse
Yes a bad choice I would say - as an owner of a Nexus 6P device currently awaiting repair (thank god I'm in warranty) - I can tell you this device is plagued with issues that only become apparent as soon as your warranty is approaching expiry.
I love the phone, the design and build quality aesthetically speaking but would never be buying from Huawei again. The device is plagued with poor design that people believe leads to the CPU failing for some odd reason causing the dreaded bootloop issue.
My phone died literally in front of me and never worked again. I've contacted Huawei to get some clarification if this is an inherent fault as thousands are complaining about it and they just plain deny it and maintain if the warranty expires your out of luck. Apparently fixing the bootloop requires a motherboard change which in itself costs over $200 apparently. May as well get another phone for that as even the replacement component will eventually fail!
Sounds like a power issue. Maybe there's an open at the power switch or bad battery connector or battery. It most likely is nothing to do with Android oh it's just a coincidence. If you would have not even flashed Android O it would have still done this
seems like you will need to open up your nexus and unplug the battery, and then put everything together and try
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
paracha3 said:
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
Click to expand...
Click to collapse
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
murphyjasonc said:
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
Click to expand...
Click to collapse
Yes I was able to apply that and got it to work. Thanks