Related
Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
alpha-ro said:
Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
Click to expand...
Click to collapse
Did you ever try to buy it at Samsung Store? They maybe have it
I didn't consider that, i'll see if i can contact them directly, hopefully i can get the replacement i need. Thanks friend!
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
This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
re: bootloops
whitebloodcell said:
This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Go into settings>developer's options and ENABLE OEM UNLOCK then
go into settings>general management>reset>factory data reset and
reset the phone.
Once you have done that the phone will work properly without rebooting
provided that you have successfully odin flashed the official samsung
G935F S7 Edge firmware prior to doing a factory data reset.
Good luck, have a great day!
Thanks for replying. Unfortunately I can't get into the phone at all. Only screen I have access to a recovery and downloader.
So I left the phone alone for a while and tried booting into safemode. This time it worked - sort of. It is asking me for a password, but I have never set one. I only ever set a pin and fingerprints. But since wiping everything that doesn't seem to apply anymore. What is the default password? I am referring to the phone password, rather than a google account obviously. I am not at that stage of the boot up.
Update: found the password (default_password), still boot looping on the optimising apps screen.
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
I have flashed stock rom (initially the version that matches my carrier, although my phone was bought sim free and unlocked, and then the version for unlocked phones (BTU in sammobile I think)) but it still just boot loops. The phone can remain in download mode as long as it wants, and previously, when it was asking for the password, it was able to remain on that screen indefinitely. I would have thought if it was a hardware problem the boot looping would happen regardless of the action on screen. Immediately after flashing the stock rom, it did start to load before ooting. Now it just boots immediately at the Samsung Logo.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
Just to be clear, do you mean repartition here? I have not checked that option before, will try it.
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
vsn4 said:
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
Click to expand...
Click to collapse
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
You can wipe your phone by entering recovery. Default recovery has the wipe option.
alehawk said:
You can wipe your phone by entering recovery. Default recovery has the wipe option.
Click to expand...
Click to collapse
Was the first thing I tried. Didn't help.
I got the bootloop thingy and was the cache, I wiped and the phone booted up
alehawk said:
I got the bootloop thingy and was the cache, I wiped and the phone booted up
Click to expand...
Click to collapse
Thanks for trying to help, but, again, already tried that.
whitebloodcell said:
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
Click to expand...
Click to collapse
Hope all goes well, let us know if you get it sorted out.
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
AnubuRe said:
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
Click to expand...
Click to collapse
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
whitebloodcell said:
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
Click to expand...
Click to collapse
For those perhaps in similar situation in the future, Samsung didn't care that it was purchased second hand, despite what the fine print says. They just looked at the serial number. In the course of trying my own repairs I flashed a custom rom, which of course tripped the knox warranty void bit. When I took it into the service centre they saw this and then wanted to charge £225 for an out of warranty repair. I refused at the time. I later called Samsung support and explained the situation (I said a phone repair shop must have done the flashing). Again on the phone I was told it would be an out of warranty repair, and this time I agreed. They collected my phone and returned it to me today however, with no invoice or mention of charges, so it looks like they just did the repair no questions asked.
I have the same issues, so far I'm getting by with flashing a stock rom with pit file and doing repartition and nand erase, normal cache/ factory reset doesn't help, it sometimes even boot loops while in twrp.
Somehow Odin flashing helps for a random amount of time, but it has thus far, crashed after a month, or a couple weeks since the last flash, etc. So far it's been my 5th boot loop event in the last 6 months
It sucks but as I got mine from another country (/win), didn't get the warranty ;( plus I tripped Knox by rooting.
sounds hardware related to me..
i had a friend with a note 4 who had similar problems it would hardly ever boot sometimes boot straight into download mode..
if by chance it did boot it would boot once the device was locked for a short time it would reboot and start over again bootlooping..
it was the emmc flash memory that was failing...
a workaround i found for this was the first thing i did when finally getting it to boot was install "Wake Lock - CPU Awake" and set it to never let the device sleep and to startup on boot...
this "fixed" it as long as your phone does not turn off... he had insurance though and sent it off and they sent him a new refirb
again this note 4 was untouched never rooted or anything
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
im having pretty much the exact same problem except ive been unsuccesful at flashing the stock firmware for my galaxy s7 active (SM-G891A). the active series isnt the most saute after, so finding the right firmware is alil more difficult. which im pretty sure is how i got into this situation! my question is what exacly does checking the "reparation" option do. i read to leave to leave it unchecked/unticked. maybe thats why ive been unsuccessful. and someone told me awhile ago not to fill in the "bt" box becuz i have a locked bootloader. this correct or no?
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
Okay guys, I've got the S7 edge (SM G935F) Exynos var.
I restarted my phone yesterday, it hasn't been rooted or anything and it got stuck in a boot loop. Then I got the common 'blue light of death' with the black screen, rendering it useless.
Whilst in this state, I can't force restart the phone or enter recovery / DL mode.
The battery finally drained and I've flashed new (stock) firmware through ODIN. Still the same outcome.
I figured I could root and get a custom rom to maybe work however I have the FRP lock issue so I can't flash TWRP.
I'm open to any ideas, anythings worth a try at this point lmao, last phone I rooted was my S5 so a little out of touch with it all.
Cheers
JTec11 said:
Okay guys, I've got the S7 edge (SM G935F) Exynos var.
I restarted my phone yesterday, it hasn't been rooted or anything and it got stuck in a boot loop. Then I got the common 'blue light of death' with the black screen, rendering it useless.
Whilst in this state, I can't force restart the phone or enter recovery / DL mode.
The battery finally drained and I've flashed new (stock) firmware through ODIN. Still the same outcome.
I figured I could root and get a custom rom to maybe work however I have the FRP lock issue so I can't flash TWRP.
I'm open to any ideas, anythings worth a try at this point lmao, last phone I rooted was my S5 so a little out of touch with it all.
Cheers
Click to expand...
Click to collapse
I had the same issue for about a week now, luckily i didnt have the frp lock on, but I have tried everything possible from downgrading to upgrading to flashing a custom rom : everything seems to just fail in every way possible and youll always end up with the blue light of death as you call it. I came to the conclusion that this isnt a software related issue , it is more than a hardware issue related to the s7 edge... I ended up forgetting about it after all ... Good luck !
xTweeBy said:
I had the same issue for about a week now, luckily i didnt have the frp lock on, but I have tried everything possible from downgrading to upgrading to flashing a custom rom : everything seems to just fail in every way possible and youll always end up with the blue light of death as you call it. I came to the conclusion that this isnt a software related issue , it is more than a hardware issue related to the s7 edge... I ended up forgetting about it after all ... Good luck !
Click to expand...
Click to collapse
Love a good Samsung lmao, thanks for your reply