Related
Hello OnePlus X users and Oneplus users in general. After a lot of **** I decided to make this thread to point out my issues and my experience with Oneplus and OnePlus in general. This will be a long thread so sit down, take some snacks and “enjoy”.
(Thread will be posted on XDA, Op forums and Reddit.)
My OnePlus X
About 4 months ago I was using my phone and noticed something. It was getting really hot without doing any heavy tasks. I couldn't remember this happening before. I wasn't thinking much about it but I looked a bit more on the temperature of the phone in the next few days, and what I saw was that the temperature was not OK at all. My phone temperature was higher than normal. And the temperature came from the position where the CPU was placed. From this point of time I tought I could live with it..but I couldn't. I also found someone else with the same problem. He encouraged me to send my phone to OnePlus and let them repair it. This was the day.. And this was maybe the biggest fault in my life.
I got my phone back and I was so happy because the days without my phone were horrible, not be able to call and message is really annoying. I was also happy because I thought I had a completely working phone now.
But no...
First I noticed that the phone has a strange version of oxygen os installed. On the power button screen I saw a "report bugs" button. It maybe was a developer version but I'm not sure about that. The device was also a little bit hotter than average. I tried to flash twrp but it wasn't working. It gave me errors over errors. I tried to flashed an official version of OOS. I could flash it but twrp still wasn't working there. It gave me errors again.
The next day I finally managed to install twrp(version 3.0) but when I tried to flash or wipe something it gave me errors.
It took me a day to figure out what to do.
I tried to change the file system of my partitions. It removed the errors but gave new ones.
Like Error 7.
OnePlus changed the device identification. I couldn't flash any rom without editing it, not even OOS. After editing the rom a bit I managed to flash it. Well.. I got it flashed but I got a bootloop then. I tried it several times and gave up. I even tried every file system possible and wiped anything through twrp and through fastboot. It just wasn't working for me. I also tried it with OOS. And guess what… it wasn't working either. Same with the oneplus recovery.
Next day again. I finally flashed oos through the oneplus recovery somehow. I got a working system.
In the next day I was confident enough to try and flash twrp.
It was working. I flashed a rom. Everything was fine until I noticed something. The heat. The heat came back. And this is not a little heat around the CPU, no this is 50-70°C which spreads around the device.
The best thing comes now.
I looked at the paperwork they sent back with the package. They just changed the software nothing else. No new cpu. With that I lost my trust into OnePlus.
The heat
Let’s talk a bit more in depth about the heat.
It all started 4 months ago, my phone was always cold, a little bit of heat while gaming but no problems at all. Suddently it started to heat.
The temperatures raised above 50 for the first time. I asked around in various OnePlus groups on Telegram and even made a post on XDA. Almost no one had the same problem.
Only me and Nico seemed to have the exact same problem. We tried everything: wiping, underclocking, changing governor, flashed ROM’s (like sultan, but it didn’t change).
There were moments that the heat was above 70°C, I couldn’t even hold my device anymore.
Alot of people convinced me to contact OnePlus customer support.
OnePlus Repair center failed!
The customer support created a ticket for me and I was preparing my device for shipping.
UPS picked up my phone and I needed to wait 15 days untill my device returned. That was no problem for me.
I got a message: my phone was arrived in my country, I picked it up.
I was so excited no more heat! But I was really wrong about that. The heat was back!
I was so dissapointed. I checked the shipping papers and I saw this:
OnePlus B2C Hotline
Repair text from repair center
Legacy data deleted
Functional test conducted
Settings set
Software update conducted
They just changed something in the software part! It is a hardware problem, changing OS won't help at all!
At this point I don’t know anymore.
OnePlus “scammed” me, more then a week of wait and the issue isn’t even fixed.
I lost my trust in OnePlus.
Remeber what is one the OnePlus boxes ?
“Created together with our fans”
Then serve your fans, fix their problems!
They sucks on customer service.
They just changed the software nothing else. No new cpu
Click to expand...
Click to collapse
you mean they should have changed phone's CPU for you ?
BruintjeDeBart said:
Hello OnePlus X users and Oneplus users in general. After a lot of **** I decided to make this thread to point out my issues and my experience with Oneplus and OnePlus in general. This will be a long thread so sit down, take some snacks and “enjoy”.
(Thread will be posted on XDA, Op forums and Reddit.)
My OnePlus X
About 4 months ago I was using my phone and noticed something. It was getting really hot without doing any heavy tasks. I couldn't remember this happening before. I wasn't thinking much about it but I looked a bit more on the temperature of the phone in the next few days, and what I saw was that the temperature was not OK at all. My phone temperature was higher than normal. And the temperature came from the position where the CPU was placed. From this point of time I tought I could live with it..but I couldn't. I also found someone else with the same problem. He encouraged me to send my phone to OnePlus and let them repair it. This was the day.. And this was maybe the biggest fault in my life.
I got my phone back and I was so happy because the days without my phone were horrible, not be able to call and message is really annoying. I was also happy because I thought I had a completely working phone now.
But no...
First I noticed that the phone has a strange version of oxygen os installed. On the power button screen I saw a "report bugs" button. It maybe was a developer version but I'm not sure about that. The device was also a little bit hotter than average. I tried to flash twrp but it wasn't working. It gave me errors over errors. I tried to flashed an official version of OOS. I could flash it but twrp still wasn't working there. It gave me errors again.
The next day I finally managed to install twrp(version 3.0) but when I tried to flash or wipe something it gave me errors.
It took me a day to figure out what to do.
I tried to change the file system of my partitions. It removed the errors but gave new ones.
Like Error 7.
OnePlus changed the device identification. I couldn't flash any rom without editing it, not even OOS. After editing the rom a bit I managed to flash it. Well.. I got it flashed but I got a bootloop then. I tried it several times and gave up. I even tried every file system possible and wiped anything through twrp and through fastboot. It just wasn't working for me. I also tried it with OOS. And guess what… it wasn't working either. Same with the oneplus recovery.
Next day again. I finally flashed oos through the oneplus recovery somehow. I got a working system.
In the next day I was confident enough to try and flash twrp.
It was working. I flashed a rom. Everything was fine until I noticed something. The heat. The heat came back. And this is not a little heat around the CPU, no this is 50-70°C which spreads around the device.
The best thing comes now.
I looked at the paperwork they sent back with the package. They just changed the software nothing else. No new cpu. With that I lost my trust into OnePlus.
The heat
Let’s talk a bit more in depth about the heat.
It all started 4 months ago, my phone was always cold, a little bit of heat while gaming but no problems at all. Suddently it started to heat.
The temperatures raised above 50 for the first time. I asked around in various OnePlus groups on Telegram and even made a post on XDA. Almost no one had the same problem.
Only me and Nico seemed to have the exact same problem. We tried everything: wiping, underclocking, changing governor, flashed ROM’s (like sultan, but it didn’t change).
There were moments that the heat was above 70°C, I couldn’t even hold my device anymore.
Alot of people convinced me to contact OnePlus customer support.
OnePlus Repair center failed!
The customer support created a ticket for me and I was preparing my device for shipping.
UPS picked up my phone and I needed to wait 15 days untill my device returned. That was no problem for me.
I got a message: my phone was arrived in my country, I picked it up.
I was so excited no more heat! But I was really wrong about that. The heat was back!
I was so dissapointed. I checked the shipping papers and I saw this:
OnePlus B2C Hotline
Repair text from repair center
Legacy data deleted
Functional test conducted
Settings set
Software update conducted
They just changed something in the software part! It is a hardware problem, changing OS won't help at all!
At this point I don’t know anymore.
OnePlus “scammed” me, more then a week of wait and the issue isn’t even fixed.
I lost my trust in OnePlus.
Remeber what is one the OnePlus boxes ?
“Created together with our fans”
Then serve your fans, fix their problems!
Click to expand...
Click to collapse
You had me at reddit, post teh OP forum & reddit links to this post here.
A little sadness for your story, on the other side when I had a problem on my OPX, the front speaker was broken, they picked up my phone and in 7 working days it came back perfect!!
So I don't know.. maybe you can ask the costumer service for a replacement?
Anyway in my case they were really gently with me, hope for you too!
Same **** for me..
My charging port was somehow dead (the cable was very loose inside the port and phone only charged in a specific cable position), so I contacted OnePlus.
I was surprised how fast everything was going. Day 1 Request, Day 2 E-Mail with freigth label and delivery note, Day 3 UPS came by and took my package, Day 6 or 7 phone was back.
Then I opened the package and saw the excact same note from the repair company as you did..
I only charged it two times since the coming back (which went perfectly fine, no matter in which position the cable was?!?) and didn't really used it so I have to see if the problem is still really existing or there happened some voodoo **** which made my charging port working properly after doing some software reseting?
What ever, kinda the same experience that you encountered..
XqepX said:
Same **** for me..
My charging port was somehow dead (the cable was very loose inside the port and phone only charged in a specific cable position), so I contacted OnePlus.
I was surprised how fast everything was going. Day 1 Request, Day 2 E-Mail with freigth label and delivery note, Day 3 UPS came by and took my package, Day 6 or 7 phone was back.
Then I opened the package and saw the excact same note from the repair company as you did..
I only charged it two times since the coming back (which went perfectly fine, no matter in which position the cable was?!?) and didn't really used it so I have to see if the problem is still really existing or there happened some voodoo **** which made my charging port working properly after doing some software reseting?
What ever, kinda the same experience that you encountered..
Click to expand...
Click to collapse
Something has to change, there customer service and repair service is garbage
BruintjeDeBart said:
Something has to change, there customer service and repair service is garbage
Click to expand...
Click to collapse
I agree that OnePlus support is horrendous.
We have the following issue:
Basically if you reboot the phone, 9 times out of 10 there will be absolutely no signal whatsoever on the 3 UK network, the phone will just state emergency calls only. This happens on both 3G and 4G, but we usually have 4G turned off as there are not many areas within our region that support 4G yet. If you search Available Networks 3 doesn't show up.
Usually leaving the phone for hours the signal will come back, but sometimes it can be fixed by going into the Test Menu by putting *#*#4636#*#* into the dialer and going to Phone Information -> Toggling the Radio off and On a few times, but this doesnt work every time. My LG G4 is also on the Three network, so I have tried putting both SIMS's in the OnePlus X at the same time and the same issue occurs in both SIM Slots. If I put a Vodafone SIM in as well as the Three SIM, the Vodafone SIM works absolutely fine, regardless of the SIM slot it goes in, but it maintains a signal each time. The problem isnt signal in the area as we have full signal in our house. If I put my wife's SIM into my LG G4 it works absolutely fine 100% of the time.
I've exported various catlogs/modem logs and they have absolutely no interest in assisting.
Community Build 1 it worked flawlessly, but Community Build 2 its not working again. Their recommended fix is to use the Community Build 1 for the forseable...
Can see this phone will be getting sold and replaced with something else.
Little Update to my problem:
I made some tests today, my charging problem still exists. It only charges in a specific position.. I guess I have to fix it on my own :/
Gesendet von iPhone mit Tapatalk
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
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.
Got a used 6P 128 meg for christmas. Did OTA to 7.1.1 then unlocked bootloader, installed latest TWRP and rooted. Installed Pure Nexus 7.1.1 , Dynamic GAPPS and Flash Kernel on Christmas day. Been running great for 5 days then out of nowhere it started bootlooping at the GOOGLE screen. After establishing that I could not get anywhere with recovery but still reported device through fastboot I downloaded the latest factory image and flashed that with no change. At this point I am out of ideas. Any thoughts on grabbing a MM or 7.0 image? Actually any ideas are certainly welcome! Happy New Years everybody... LOL
CyberpodS2 said:
Got a used 6P 128 meg for christmas. Did OTA to 7.1.1 then unlocked bootloader, installed latest TWRP and rooted. Installed Pure Nexus 7.1.1 , Dynamic GAPPS and Flash Kernel on Christmas day. Been running great for 5 days then out of nowhere it started bootlooping at the GOOGLE screen. After establishing that I could not get anywhere with recovery but still reported device through fastboot I downloaded the latest factory image and flashed that with no change. At this point I am out of ideas. Any thoughts on grabbing a MM or 7.0 image? Actually any ideas are certainly welcome! Happy New Years everybody... LOL
Click to expand...
Click to collapse
Did you flash the entire factory image using flash-all.bat like Google suggests or do something more complicated where you flashed the factory image in pieces?
Actually I tried both ways. I did all the pieces separately but the data then formatted the data then then tried the flash-all.bat Starting to get worried for the first time since rooting my Samsung Moment on Froyo.
A couple of people with boot loop issues claimed that flashing 6.0.1 fixed their problem. If you are desperate it might be worth a try.
Bootloop?problem hardware https://www.google.it/amp/www.digitaltrends.com/mobile/google-nexus-6p-bootlooping/amp/
I was able to get Huawei to RMA it even though its out of warranty
Downloading 6.0.1 and then contacting Huawei are on the agenda then. I'll keep folks updated... Thanks guys.
EDIT: 6.0.1 flashed with no change. Still have fastboot access but any other option besides barcodes just reboots. Will start looking into RMA.
EDIT TWO: Huawei is blaming GOOGLE but they agreed to RMA. Looks like one is popping up every few day on here so how many are really happening??
Just happened to me. RMA on the way. I love playing with android but pixel and 6p having to many problems . I may go another OEM on android. Or hang myself and get an iphone .
How does the RMA process work with Huawei? Do they cross ship?
RMA?ok my problem RMA i'm be month later, no phone available and having to wait another day to get reimbursement phone, never buy more hauwei
i took a picture with my flashlight on last night and got kicked into a boot loop then it just died completely. when i plug it in no light goes on in the corner or anything. i did wake up to it stuck on the google screen put the second i pressed the power button it shut off again. I just got this phone back a week ago from getting the battery replaced now this happens. Weird thing is when i checked my warranty status for the battery replacement it said i was up 1/26/17. Now when i check it says im under warranty until 4/3/17. not complaining about adding on warranty time but i just found that odd
I dropped by phone 3 feet in a case on Sunday. the screen popped out about the width of length of a credit card on the button side. I snapped it back in. It worked until yesterday. My alarm when off to wake me up. It would not turn off and the vibrator was at least 100%, louder than normal. I held power to restart and it boot looped. I flashed 3 different factory images and no joy. I did 6.0.0 the very first image, and the last two January images. I suspect that this issue is a mechanical/electrical issue where the phone is not receiving enough amps/volts to complete the boot, since the bootloader and recover use much less power they still work. By mechanical i mean battery damaged or connections damaged/degraded. kind of like when you corrode the poles on your car battery. With in mind I got the phone in august 2016. week 1 I dumped a glass of water on the phone. Maybe corrosion on the battery terminals. Just a thought.
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