Related
Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam
AndroidLEK said:
Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam
Click to expand...
Click to collapse
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option
PSPNikos said:
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option
Click to expand...
Click to collapse
When I first downgraded back down to the MEA firmware that I was linked to from another forum, I discovered straight after flashing that it was a pre-rooted ROM and the wifi still would not turn on then.
The phone has been sent back to Samsung again today for another repair but last night as a last ditched attempt, I downloaded & flashed the stock XXUAMDM firmware from April and the wifi still refused to turn on.
I'm still convinced that the problem itself is hardware related rather than software based going by that the problem is still present regardless of what ROM I'm on, it's just a case of trying to get Samsung to see that. I can understand now why that Samsung the first time round probably only did a fresh re-flash of the MGA firmware instead of going ahead and taking the phone apart/replacing parts as I imagine it's very labour intensive/standard procedure and not only that - the S4's mainboard (from what I've seen the wifi module is part of the mainboard) retails at over £200 which is a hefty repair cost on their part.
Liam
It is some sort of permissions issue.
If you do chmod 777 on /dev/*, /system/etc/wifi/* it should be working.
The only thing I haven't figured out is why
And it has to be done again after rebooting the phone, wich makes me sad.....
How I fixed my WiFi and sound problems after updating to latest firmware over
Hi there. (Sorry for any mistake about my English). By the way, I'm newbie on Android.
After freaking out about my WiFi problem, i didn't even care about the others problems like the sound, and I don't know if there were or if there is still some, but WiFi and sound got fixed.
After a lot of research on Google and XDA I came to the conclusion that if I could just re-install the firmware, I had
1- I Download the same firmware you are on (i guess it safer this way) I got the same (I9505VJUEMKE) that had caused the problem when was update trough Kies.
GT-I9505_PDA_I9505VJUEMKE_4.3
Changelist: 2210919
Build date: Wed, 27 Nov 2013
CSC: I9505ZTOEMKE_ZTO_Brazil
MODEM: I9505VJUEMKE
Gdrive: (créditos ao +Alexandre Affonso - Vlw)
Two links for download this firmware. (really fast download since its on gdrive)
goo.gl / UrZWAE .
goo.gl / omJC9e "
2- Unpack the Zip File
3- Putt the phone in "Download Mode"
4- Open Odin 3.07 and Connected the cable. (check if Odin linked a port to your phone, i didnt get any color change, just the COM Port number and the "added" mentioned on Odin)
5- Load the firmware on "PDA", wait a few seconds till Odin load it.
6- Click Start and wait the whole process. Don't disconnect the cable until Odin says that it was Successfully.
Finished!
After all I did the root with Odin + CF Auto Root + Supersu and So far everything is fine and better than before.
Hope I can help few of you guys.
Thanks.
Hey guys! A week ago my phone started bugging, vibrating randomly and playing weird sounds until it turned off (rooted and rom installed, standard kernel). I tried to charge it but was unsuccesful. It simply would not charge nor connect to the pc. After playing with it i managed to get another rom installed. This did not fix the problem though. I believed the battery was the problem so I went and bought a new one, but once again it would not charge. I opened my phone to see if i could see any loose connection or something, but I was not able too see anything faulty. I'm now 100% sure this is a hardware issue, so would i be able to send it to Samsung for warranty-repair even though i have rooted my phone and flashed a different software? Thanks in advance!
I would really appreciate some help on this topic!
You tripped Knox so it's highly unlikely they'll repair it. Did you try a factory reset? Also might want to try flashing an Official firmware for your phone.
Sent from my SM-N910C using XDA Free mobile app
Yes factory reset and everything. As I said I'm SURE this is a hardware issue because the USB transfer/battery transfer is damaged. I also am not able to connect to Odin which further confirms that it is hardware related. How can i flash an official rom without Odin?
I have now had it in for repair at a local proffesional (no warranty). He told me he was not able to repair it and that he was unable to find the source of the problem. I love this phone and I would do anything to get it working again...
croulder said:
I have now had it in for repair at a local proffesional (no warranty). He told me he was not able to repair it and that he was unable to find the source of the problem. I love this phone and I would do anything to get it working again...
Click to expand...
Click to collapse
You could try to replace the USB module and see if that works. It's very cheap and worth a try.
I have already tried that.. I really have no idea of what to do
What can i flash via recovery to fully clean it of anything and set it as close as possible to factory standard or simply GET IT TO WORK? Any help is very appreciated
I have a serieux problem with my phone and it is when i put in my phone charging cable into the phone.
I get fatal reboots and the phone hangs totally 10 times after putting em into the starting screen or the system.
Before i had a few custom roms on my phone and want to try em out for it´s functions
My story:
I had the CrisisCross Rom on my phone , then i flashed a 6.0 Android Custom Rom on my phone because i had problems with my Samsung Gear VR from a friend and i had not yet installed the Samsung VR Feature and had read about the leak issues from the custom roms.
Because i had an issue on the 6.0 Custom Rom with Viper4android ( don´t know which rom it was ) it only doesn´t work the programm./
Then i got back to another custom rom and Viper4android work again.Later on my system hang out when i put the charging cable on it and i have seen a few pixels and then later on the total crash of the system.i have then try out to make other custom roms on it but i made maybe a wrong DBT Code ( i choose the Germany Code ) .
But the problem stay on my phone.i had this now for 4 weeks , everytime my phone was empty it must be reflashed almost twice a day and i can´t put my phone charging cable on my phone even with that it hangs on reboots.
I tried then out to live with that as long as it works i know it´s hard to make that every time it was recharged but i don´t want to send it back to the factory for getting crushed with the invoice later
As it is and was rooted to much i have no chance that the garanty will get on for that.
A few days before this day i have made a fresh stock rom 6.0 firmware on my phone but the charging problem stayed ( pixxel issues / fatal hangouts / system problems like pixxels on the PIN sycreen )
Also everytime when the phone is off i get pixxels on the full screen ( many colours ) when i stuck the charging cable in.
My question is now if it´s worth to send it back to the factory to repair it and if that is a system problem or a problem with the hardware?
Greetz:highfive:
Can i get an answer please :crying:
If you you don't know which ROM you flashed earlier how can we help? We're not mind readers. You also haven't said which model phone you have. F/C/G? Something else? Are you sure you flashed the right firmware for your model?
If you have, it sounds like a hardware problem. It's extremely unlikely to be CSC-related. If you're rooted and have a custom recovery, I'd wipe everything including system (you will lose EVERYTHING on the phone unfortunately), then flash stock firmware via Odin. If it doesn't work then, it's hardware.
Drastic, but with the lack of info you've given.... Good luck!
It is the 928F Model
I'm from Luxembourg and i choose the CSC Code from Germany ( DBT )
I think its a chip burned inside and it reacts when i put the phone charging cable into the smartphone ( screen full of pixxels )
I have already put the Stock Firmware on the phone flashed with Odin and backed up everthing with TB.
After a restart when i put out the cable from the charger i must make really fast to go in an app or play music , still it hangs/freezes sometimes even when sonebody calls me it freeze and i must restart it manualy.
When i was in the PIN enter when it vibrates and had a freeze it vibrates till i pushed the power and Vol-Button 10 seconds
I was almost afraid that it can explode :/ ^^
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Bro something similar happened to me as well .. even I did purchase new battery as everyone and also repair service guy said it's due to battery but that didn't solved the issue ..
Kindly check this xda post by me , it may help you.
https://forum.xda-developers.com/note-4/help/weird-white-bar-booting-sm-n910g-t3529413
adrscu said:
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Click to expand...
Click to collapse
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Hey guys and thanks for the replies.
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
adrscu said:
Hey guys and thanks for the replies.
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
Click to expand...
Click to collapse
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Amar.B said:
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
adrscu said:
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
Click to expand...
Click to collapse
All the best mate and it's my pleasure.. cheers
Sent from my SM-N910G using Tapatalk
Hello everyone.
My device is going into bootloop without usb cable.
With USB power adapter device works fine but when I pull out the cable smartphone is going to reboot (logo->reboot->logo->reboot...).
I tried the next:
I have changed battery to new but result is the same.
I have updated firmware through official Samsung SmartSwitch program but it also didn't help.
Recovery and bootloader are reachable.
I found info on stackoverflow that some crash logs could be stored by path /data/anr.
But my device isn't rooted and I can't get files from specified path.
Baseband ver. - N910HXXU1DPC1
Build number - MMB29K.N910HXXS2DQC7
Device status - official
Could someone suggest me some steps to check ?
Thanks in advance !
Re Flash to stock firm
To solve your problem you may have to download Stock firmware from sam mobile.com. Re-flash device using Odin3. Ive been dealing with a similar issue, and have had to do this several 100 times over the course of 3 day. It should solve your boot loop problem, but whatever else to are trying to do i'm not sure.
milesg86 said:
To solve your problem you may have to download Stock firmware from sam mobile.com. Re-flash device using Odin3. Ive been dealing with a similar issue, and have had to do this several 100 times over the course of 3 day. It should solve your boot loop problem, but whatever else to are trying to do i'm not sure.
Click to expand...
Click to collapse
Hello milesg86.
First of all thanks for your advice. But I think it will not help me.
I'll try to explain why.
I have already checked the latest firmware version for my device for my country on sammobile.com - it's N910HXXS2DQC7.
It's the same version that I reinstalled using SmartSwitch http://www.samsung.com/us/smart-switch/ .
Could it be the bug in firmware ?
Should I check some logs ?
you tried factory reset over recovery already? anyways: there are so many possible reason for a bootloop at Note4 --> mmc fail etc
Galixy said:
you tried factory reset over recovery already? anyways: there are so many possible reason for a bootloop at Note4 --> mmc fail etc
Click to expand...
Click to collapse
Yes, I have done factory reset through official recovery.
Also, I reinstalled firmware through SmartSwitch.
But both variants didn't help (
Galixy said:
you tried factory reset over recovery already? anyways: there are so many possible reason for a bootloop at Note4 --> mmc fail etc
Click to expand...
Click to collapse
Could you suggest how to check mmc fail ?
Fediir said:
Yes, I have done factory reset through official recovery.
Also, I reinstalled firmware through SmartSwitch.
But both variants didn't help (
Click to expand...
Click to collapse
Did you install a specific app or update before the loop occured? However it smells like a defect mainboard. Here is the deal: You can try root your phone (if the factory reset worked there should be a OS on your Note 4) and flash custom recovery like TWPR. Then do a FULL wipe through it and flash the OS you downloaded again through ODIN mode. Dunno how experienced you are with it but keep in mind you do it on your own risk and the warranty is gone (if you still got it anyways.....)
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
well, if the mmc fail would occur you would definitely recognize it
Galixy said:
Did you install a specific app or update before the loop occured? However it smells like a defect mainboard. Here is the deal: You can try root your phone (if the factory reset worked there should be a OS on your Note 4) and flash custom recovery like TWPR. Then do a FULL wipe through it and flash the OS you downloaded again through ODIN mode. Dunno how experienced you are with it but keep in mind you do it on your own risk and the warranty is gone (if you still got it anyways.....)
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
well, if the mmc fail would occur you would definitely recognize it
Click to expand...
Click to collapse
I have installed TWRP through Odin 3.12 recently (without root) https://twrp.me/devices/samsunggalaxynote4exynos3g.html.
Why you suggest to root the device ?
I want to clarify. Do you recommend to flash the official OS through Odin ?
What is the benefits from TWRP wipe ?
Also, now I am going to install this firmware https://forum.xda-developers.com/note-4/development/rom-nemesis-refined-v3-5-n7port-t3587637 .
Do you recommend it ?
P.S. Phone is working when connected to USB power adapter.
Thank you for comments !
Fediir said:
I have installed TWRP through Odin 3.12 recently (without root) https://twrp.me/devices/samsunggalaxynote4exynos3g.html.
Why you suggest to root the device ?
I want to clarify. Do you recommend to flash the official OS through Odin ?
What is the benefits from TWRP wipe ?
Also, now I am going to install this firmware https://forum.xda-developers.com/note-4/development/rom-nemesis-refined-v3-5-n7port-t3587637 .
Do you recommend it ?
P.S. Phone is working when connected to USB power adapter.
Thank you for comments !
Click to expand...
Click to collapse
Has been a while that i used TWPR but i guess, when you trying to do a full a wipe it's telling you anyways if the device is not rooted?
TWPR does a FULL wipe, which means your smartphone is "empty". It wont boot then because there is no OS anymore, so you flash through odin (hold volume down, home button, powerbutton) your stock firmware. On Note 4 i never had an custom rom, only on the old Note 2 and CM rom was pretty nice. I think they stopped working on CM but i am sure you will find a stable version for your phone right here in the forum
NEMESIS ROM was successfully installed but it didn't solve the problem
Device is going to reboot/bootloop when I remove the USB power cable.
The next step is the authorized Samsung service.
Thanks to all for comments.
P.S. NEMESIS ROM :good::good::good: I'll install it again when my phone will be fixed .
Hello to everyone.
Yesterday my problem was solved.
Issue was because of damaged battery. Authorized Samsung service provides to me original battery and it's work
As result, I requested fefund for my Amazon order of battery https://www.amazon.com/gp/product/B00SW22RJU/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 .
Thanks to all for comments !
I know this is an old thread but ive been going through this issue for a long time. But now recently happened to my galaxy s7 edge, exact same problem.
It only stays on with the charger cable connected, if i remove it, it goes to bootloop.
On the note 4 ive tried 4 different batteries, they all say samsung but not sure if they're oem from samsung. But i also swapped the mother board and also same thing happens , so its not the mother board thats damaged cause I tried 2 of them and same issue. Could be it be the charging port or should try a oem battery too ?
fevera1985 said:
I know this is an old thread but ive been going through this issue for a long time. But now recently happened to my galaxy s7 edge, exact same problem.
It only stays on with the charger cable connected, if i remove it, it goes to bootloop.
On the note 4 ive tried 4 different batteries, they all say samsung but not sure if they're oem from samsung. But i also swapped the mother board and also same thing happens , so its not the mother board thats damaged cause I tried 2 of them and same issue. Could be it be the charging port or should try a oem battery too ?
Click to expand...
Click to collapse
Then you have 2 bad mother boards...... anything that would cause the bootloop is in the motherboard
trinilu27 said:
Then you have 2 bad mother boards...... anything that would cause the bootloop is in the motherboard
Click to expand...
Click to collapse
Well its basically the same info that the person that did this thread. Same exact thing. I just havent tried a new oem battery i guess just knock off ones. But now also with this s7 edge is also happening
fevera1985 said:
Well its basically the same info that the person that did this thread. Same exact thing. I just havent tried a new oem battery i guess just knock off ones. But now also with this s7 edge is also happening
Click to expand...
Click to collapse
I did have
..i Have had a bad battery with one of my Note 4 S the phone would be fine until the battery got below 50% then it would constantly reboot.... Now is your phone looping or is it just stuck on the splash screen?
trinilu27 said:
I did have
..i Have had a bad battery with one of my Note 4 S the phone would be fine until the battery got below 50% then it would constantly reboot.... Now is your phone looping or is it just stuck on the splash screen?
Click to expand...
Click to collapse
Well for example if I have the phone connected to the charger, it will stay on like normal, I can make calls, use the internet etc.. Normal stuff. If I unplug the cord and say the battery is 100% it will sometimes stay on for like 5 mns and then it shuts off and starts restarting on and on to samsung screen or sometimes the carrier logo screen. It will do that for like 2 mns then it shuts off and wont turn on.
I plug it on the charger and battery shows 0% or 3 sometimes, but 5 mns before it was 100%..
Hopefully i make sense lol
fevera1985 said:
Well for example if I have the phone connected to the charger, it will stay on like normal, I can make calls, use the internet etc.. Normal stuff. If I unplug the cord and say the battery is 100% it will sometimes stay on for like 5 mns and then it shuts off and starts restarting on and on to samsung screen or sometimes the carrier logo screen. It will do that for like 2 mns then it shuts off and wont turn on.
I plug it on the charger and battery shows 0% or 3 sometimes, but 5 mns before it was 100%..
Hopefully i make sense lol
Click to expand...
Click to collapse
I take back what I said....I'll bet it is the battery....trust me if you're going to go buy a new battery pay out the little extra money for the extended battery you can find them on eBay and Amazon...well worth it
trinilu27 said:
I take back what I said....I'll bet it is the battery....trust me if you're going to go buy a new battery pay out the little extra money for the extended battery you can find them on eBay and Amazon...well worth it
Click to expand...
Click to collapse
Right.. I bought some local in a local phone store but those are fake. They have the samsung brand but its one of those places they repair phones and I knoe they're fake batteries. But yeah they didnt work. I found a authentic oem batteries on ebay that I'm going to order and crossing my fingers it works.
I have a Samsung Note 4 with boot loop problem. I am asking for advice because it has two Bitcoin Accounts on it that I can not retrieve anywhere else. HELP!!! Thanks in advance