Develop Bugs

3 button download/recovery mode saved my butt.

Within the 14 days return policy I took my Galaxy back after it bricked for no reason. I was almost stock other than unlocking it and running ADW. Too many things wrong with them so I gave it one more chance with a replacement. The new one has a working recovery/download mode so that's the biggie for me. The lag seems better and the GPS actually works. Great, I feel better. But I decided that I won't root it yet since 2.2 is coming soon. I'll let it flash as designed before digging deep.
Yeah, right. After noticing that the WiFI is still flaky at random times I turned it off again today when it wasn't passing any data. 3G still working so fine. But then the Market started to FC which I've not seen at all. I shut it down and rebooted again which is the fix for my WiFI. Well, it once again decided to brick just like the last one. I get past the logos and then just a black screen. She's bricked and I didn't even root it this time. Only thing not stock was ADW launcher instead of the Samsung thing that I don't like.
So I put her into recovery mode and did a factory reset. That fixed it and I setup all over again. Luckily with 2.1 you get a list of all your previously installed apps in Market the first time you enter so if you don't leve the app you can quickly install everything again. 20 minutes later I'm back in business except this time I'll stick with the launcher it came with, can't think of anything else that would cause this sudden bricking other than the wonder phone might be a piece of crap. I just don't know yet.

By reading the title I thought you meant that Samsungs new update to activate the 3 button combo had saved you. Having a phone with download mode enabled is quite hard to brick, you can always just put it into download mode and reflash with Odin.

That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.

3rdcoast said:
That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.
Click to expand...
Click to collapse
This is just my opinion but I don't think the phone would have come with the update, it would have just been an untainted unit that didn't exhibit this problem. Only a subset of new units were lacking the download and recovery modes and the fix released a couple of days ago was designed to correct that problem.
These modes are a standard feature of pretty much any Android device.
At any rate, good to hear that you have a fully functioning unit out of the box. I had to go to some length explaining and demonstrating the issue to the store from which I got my unit lacking these modes as well as my carrier until the fix came out and I fixed it myself.

I don't know either. I based my guess on the fact that Sam's fix happened to be an update that version matches what mine now shows. And my situation is a prime example why all phones need this mode. Not everyone would fix it the way I did but it only cost me 30 minutes and a few curse words because my pictures are all gone before I could get them off but I'm back up and running and that had to save somebody a few hundred dollars.
I'm still very nervous though, it did brick this morning without me doing anything. This time I don't even have NoLED or ADW but I can't leave it that way forever. My trusty Magic is way more tolerant of OS abuse.

[Q] Note 2 Dead? SDS?

Hi Folks,
Stock Note II N-7100 (Received from O2 in October 2012). Had, previously, moved from the O2 branded firmware to stock week I received the phone. No water damage or anything, not dropped, phone has lived in a rubber case since new.
No issues since (v occasional random reboot, monthly maybe?).
Today, mid call, I was dropped, and the phone what I thought was rebooting on me (Samsung Galaxy Note II [white, non animated] logo popped up), but it stayed up, rather than moving through the animated logo to the OS.
Vol-Up + Home + Power won't take me to recovery (Vol-Down + Home + Power will take me to an ODIN flash screen).
Connecting a charger brings up the battery, a 'spinner' appears in that for a second, then freezes, battery icon never changes to the animated charging logo.
Does this sound like SDS? or something else? Is there anything to be done at home to recover? Or is it a hardware fault in which case I'll start the process of tracking down a service centre & dig out an old handset in the mean time.
Thanks all,
Gavin.

gicarey said:
Hi Folks,
Stock Note II N-7100 (Received from O2 in October 2012). Had, previously, moved from the O2 branded firmware to stock week I received the phone. No water damage or anything, not dropped, phone has lived in a rubber case since new.
No issues since (v occasional random reboot, monthly maybe?).
Today, mid call, I was dropped, and the phone what I thought was rebooting on me (Samsung Galaxy Note II [white, non animated] logo popped up), but it stayed up, rather than moving through the animated logo to the OS.
Vol-Up + Home + Power won't take me to recovery (Vol-Down + Home + Power will take me to an ODIN flash screen).
Connecting a charger brings up the battery, a 'spinner' appears in that for a second, then freezes, battery icon never changes to the animated charging logo.
Does this sound like SDS? or something else? Is there anything to be done at home to recover? Or is it a hardware fault in which case I'll start the process of tracking down a service centre & dig out an old handset in the mean time.
Thanks all,
Gavin.
Click to expand...
Click to collapse
Sounds like Half SDS for me(in half SDS you can go only into Download mode) With what version of android was your phone 4.1.2 or 4.1.1 this information will be good for us, sorry for your phone try reflashing it with stock rom with ODIN and if the process fail go to the service center with your warranty but check in Download mod if the Binary count is 0 and everything says Stock, not Custom. Good luck mate.

wowrlz123 said:
Sounds like Half SDS for me(in half SDS you can go only into Download mode) With what version of android was your phone 4.1.2 or 4.1.1 this information will be good for us, sorry for your phone try reflashing it with stock rom with ODIN and if the process fail go to the service center with your warranty but check in Download mod if the Binary count is 0 and everything says Stock, not Custom. Good luck mate.
Click to expand...
Click to collapse
Thanks,
Can't recall the version, tho I think 4.1.1? Whatever was avail in October. The in-phone thingy kept reporting 'no update' so hadn't moved on to anything further.
Download screen says:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
If that's any use (no sign of a counter).

gicarey said:
Thanks,
Can't recall the version, tho I think 4.1.1? Whatever was avail in October. The in-phone thingy kept reporting 'no update' so hadn't moved on to anything further.
Download screen says:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
If that's any use (no sign of a counter).
Click to expand...
Click to collapse
They may remove your warranty for the System status its says custom, have you rooted the phone and from which country are you? You should have updated to 4.1.2 with odin the SDS is kinda fixed even thought there are still people with dead Note 2 with 4.1.2.

wowrlz123 said:
They may remove your warranty for the System status its says custom, have you rooted the phone and from which country are you? You should have updated to 4.1.2 with odin the SDS is kinda fixed even thought there are still people with dead Note 2 with 4.1.2.
Click to expand...
Click to collapse
Hmm... believe I may have rooted right at the start for a reason related to the flashing a non-O2 ROM, though wasn't running a rooted phone since. I'm UK based.
Assuming ODIN will flash the phone (even if it won't, subsequently, work) would that reset the System status?

gicarey said:
Hmm... believe I may have rooted right at the start for a reason related to the flashing a non-O2 ROM. I'm UK based.
Assuming ODIN will flash the phone (even if it won't, subsequently, work) would that reset the System status?
Click to expand...
Click to collapse
No you must have working phone and reset it with triangle away.

wowrlz123 said:
No you must have working phone and reset it with triangle away.
Click to expand...
Click to collapse
Sure I did that way back when.

dont worry about the "custom" part. it is known that SDS changes the status to custom so it doesn't matter at all. Send it to samsung and it should be repaired. then check if it have a new chip or an old one
Sent from my GT-N7100 using xda premium

Either way, if you're in the EU, rooting does not void warranty unless it can be proven that rooting is the direct cause of the problem.
Sent from my GT-N7100 using Tapatalk 2

As someone else said, try flashing a rom in odin before doing anything else. A stock system will reset the status to official. Triangle away is only needed to reset the count and usually doesn't reset the system status anyway.
Sent from my SPH-L900 using xda premium

aka_sirok said:
dont worry about the "custom" part. it is known that SDS changes the status to custom so it doesn't matter at all. Send it to samsung and it should be repaired. then check if it have a new chip or an old onem
Click to expand...
Click to collapse
adytum said:
Either way, if you're in the EU, rooting does not void warranty unless it can be proven that rooting is the direct cause of the problem.
Click to expand...
Click to collapse
Thanks chaps, this helps settle a few nerves.
billard412 said:
As someone else said, try flashing a rom in odin before doing anything else. A stock system will reset the status to official. Triangle away is only needed to reset the count and usually doesn't reset the system status anyway.
Click to expand...
Click to collapse
Sadly, no go, due to lack of a PIT according to Odin.
Called Samsung, mail in with 2 week turn around, or walk in and should have it back in 2 days? Sound about right.
There's a Service Centre 10 mins from my office, so I shall walk it in there, but (rather annoyingly), am on a training course until Friday so I won't get along till then. Excellent timing! Still, walk in ought still be quicker than sending it away.
In the mean time, I have hauled out an old SE Arc S running ICS for the time being. Feels painfully slow & restricted (low memory) compared to the Note2!
Thanks for all your help guys.

So...
Walked the phone into the service centre (CRC - http://www.crclondon.co.uk/repairs/samsungrepairs) on Monday, who told me they'd need to send it up to their Level 3 centre, which would likely be a 7-10 day turn around.
Took a call from them today, claiming that as the phone had been rooted, they couldn't do it under warranty, and it would cost £120 to repair. I rather firmly mentioned the aforementioned EU regulation which, I understood, meant that nevertheless, the repair, unless caused by the root, ought still be covered under warranty. The chap was completely intractable, refused to pass me to a supervisor of any sort for further discussion, so I've told him to have it returned to their office and I would collect ASAP and deal with Samsung directly where I hoped to have a more satisfactory discussion.
Seems like it's likely to be back with them on Friday - I will probably collect on Monday and get it dispatched same day.
Wish I hadn't bothered waiting for the walk in centre now. The Sony Arc S I'm currently using is frustratingly slow by comparison with what I've become used to!

I think you were being too honest.
I got my note2 motherboard replaced last month. and since they coundnt tell whether i had rooted or not and samsung havent officially made any announcement about sds, i told them what i found on the net that the system status shown customs because the nand memory was corrupt and it couldnt read the product name nor system partition thereore it defaulted the system status to be custom.

As a further update, Samsung central help group pretty awful to deal with, and not resulting in a satisfactory resolution.
Was eventually promised a call back, finally got an email 4 days later basically telling me 'whatever our 3rd party service centre told you we will stand by, if you collect & send to us, we'll lookup their response and use that in communication with you..' 'If you want to challenge their assertion, you'll need to source a report from an independent assessor.'
So, from all this - Ultimately, I need the phone back in a reasonable timeframe, so I've asked the 3rd party service centre to effect the repair, and I'll pay their £120 bill. I have also told them that I want whatever components they replace (I'm told likely motherboard), and copies of their full engineers report containing details of the fault found, diagnosis of cause, and resolution steps - returned to me along with the device so that I retain any evidence I require for further discussions (getting them to agree to this was an awful task, as they initially quoted various recycling regulations).
Once it's back in hand, I'll then revert to Samsung again, and work my way up through the escalation queue.
Next phone, I suspect, won't be a Samsung device. Maybe Nexus.
Fun fun fun...
G.

How do I tell if i still have Dev ed.?

Long story short samsung repaired my phone and I think they sent back retail ed.
How can I tell
in download mode it says qu
qualcom secureboot : enabe (csb) is
that reads to me like boot loader is locked.
Anyone?

pospower said:
Long story short samsung repaired my phone and I think they sent back retail ed.
How can I tell
in download mode it says qu
qualcom secureboot : enabe (csb) is
that reads to me like boot loader is locked.
Anyone?
Click to expand...
Click to collapse
Under Download Mode it says "Mode: Developer" if it's still a Developer Edition. The guy I got mine from had the same thing happen. The first time he sent it in they sent it back with retail firmware in it. He got back in touch with them, sent it back and the second time they got it right. But before it came back he switched to T-Mobile. He sold me his Verizon Note 4 Dev Ed. It's working like it's supposed to now.
They can do it right but you'll probably have to hassle them to get it done. Good luck. :fingers-crossed:

Important note!!
stueycaster said:
Under Download Mode it says "Mode: Developer" if it's still a Developer Edition. The guy I got mine from had the same thing happen. The first time he sent it in they sent it back with retail firmware in it. He got back in touch with them, sent it back and the second time they got it right. But before it came back he switched to T-Mobile. He sold me his Verizon Note 4 Dev Ed. It's working like it's supposed to now.
They can do it right but you'll probably have to hassle them to get it done. Good luck. :fingers-crossed:
Click to expand...
Click to collapse
TO ALL OWNERS OF THE SAMSUNG NOTE 4 DEVELOPER EDITION (VERIZON)!
IF YOU HAVE DORKED UP YOUR PHONE - i.e. if you flashed the OTA with greater than version BOAF (or any version which took your developer phone and cooked it into a retail item), please read...
I just sent in my phone to Samsung, as I was one of "those" who accidentally whacked my Note 4 back to retail stone age!!
My phone is on it's way back, they overnighted the device.
Not only did they reflash my phone back to developer (gosh, would just love that ability to do that, yes!!), but my screen had burn-in and asked if they could replace the screen - I'd pay for it. They charge $237.01 to do it, BUT (BIG BUTT) the deemed it a manufacturer defect, and replaced it for no charge - NICE!
But, there are a few things to note: that's if you want to preserve the Note 4 for a while.
1. If you are stuck in retail mode, Samsung will fix it, at no charge. it takes a little less than two weeks to get it back to you.
a. Call 888 987-4375, follow the prompts, when you get to your first representative, ask them to pass you through to a service / support supervisor. Then, state you have a developer edition in which got put into retail mode (say it took an update) and you'd like it to be flashed back to developer - PLEASE NOTE: They will push it back to KitKat (ANJ5) "what the phone came with". They should not give you a hassle, they'd be glad to do it as a free service.
b. If there is another legit issue (like screen burn-in; in my case) they will diagnose it, and screen burn is typically covered, even out of warranty - pending any determination of additional abuse, but they will generally cover it. Additionally, any other defect that they may find, they will replace as...
c. Historically, my experience with Samsung is, even if the device, monitor, tv, computer etc is not functioning properly, even out of warranty they will repair it, again, pending any signs of abuse. this has been my experience - i.e. in 2003 I had a Samsung monitor which had a intermittent bug in it - even 2 years after the initial complaint and out of limited warranty, they had a new monitor in my hands next day, couldn't have been nicer too me, and I did not have to ask, they offered.
So, having said that - Though I think Samsung is completely dog-gone batty for doing up the Note 5 / S6 the way they did (sooooooo applesque) - they do stand behind their products.

anticloud said:
TO ALL OWNERS OF THE SAMSUNG NOTE 4 DEVELOPER EDITION (VERIZON)!
IF YOU HAVE DORKED UP YOUR PHONE - i.e. if you flashed the OTA with greater than version BOAF (or any version which took your developer phone and cooked it into a retail item), please read...
I just sent in my phone to Samsung, as I was one of "those" who accidentally whacked my Note 4 back to retail stone age!!
My phone is on it's way back, they overnighted the device.
Not only did they reflash my phone back to developer (gosh, would just love that ability to do that, yes!!), but my screen had burn-in and asked if they could replace the screen - I'd pay for it. They charge $237.01 to do it, BUT (BIG BUTT) the deemed it a manufacturer defect, and replaced it for no charge - NICE!
But, there are a few things to note: that's if you want to preserve the Note 4 for a while.
1. If you are stuck in retail mode, Samsung will fix it, at no charge. it takes a little less than two weeks to get it back to you.
a. Call 888 987-4375, follow the prompts, when you get to your first representative, ask them to pass you through to a service / support supervisor. Then, state you have a developer edition in which got put into retail mode (say it took an update) and you'd like it to be flashed back to developer - PLEASE NOTE: They will push it back to KitKat (ANJ5) "what the phone came with". They should not give you a hassle, they'd be glad to do it as a free service.
b. If there is another legit issue (like screen burn-in; in my case) they will diagnose it, and screen burn is typically covered, even out of warranty - pending any determination of additional abuse, but they will generally cover it. Additionally, any other defect that they may find, they will replace as...
c. Historically, my experience with Samsung is, even if the device, monitor, tv, computer etc is not functioning properly, even out of warranty they will repair it, again, pending any signs of abuse. this has been my experience - i.e. in 2003 I had a Samsung monitor which had a intermittent bug in it - even 2 years after the initial complaint and out of limited warranty, they had a new monitor in my hands next day, couldn't have been nicer too me, and I did not have to ask, they offered.
So, having said that - Though I think Samsung is completely dog-gone batty for doing up the Note 5 / S6 the way they did (sooooooo applesque) - they do stand behind their products.
Click to expand...
Click to collapse
Well that is really good to know. [emoji2] Thanks for the info.
Sent from my SM-N910V DE w/ MoRom

Can someone take a picture of the download screen that shows its a developer edition. I'm having a hell if a time communications with plano repair. They are either playing dumb or they are dumb. Got phone back broken first time second time broken but locked. Now they are sending me emails saying phone checks out fine what is the problem. I need to show them what an unlocked boitliader looks like I think it im going to get a retail phone back again.

pospower said:
Can someone take a picture of the download screen that shows its a developer edition. I'm having a hell if a time communications with plano repair. They are either playing dumb or they are dumb. Got phone back broken first time second time broken but locked. Now they are sending me emails saying phone checks out fine what is the problem. I need to show them what an unlocked boitliader looks like I think it im going to get a retail phone back again.
Click to expand...
Click to collapse
It's not too clear but maybe it'll be Ok.
Update: Did you follow the directions posted by @anticloud one post above my last post? Who is plano repair? The only people who have a prayer at knowing how to deal with a Dev Ed phone is Samsung Corporate Headquarters. And even there only a small handful of people who actually set up the Dev Ed phones are going to know what to do.

Unrooted LG G4 stuck in boot loop

My G4 has randomly restarted on me a few times before (only once at a time), but I thought nothing of it. However, this time, it has gotten stuck in a boot loop. My phone was fairly hot from watching videos at a high brightness, and that is when I noticed it restarted for the first time. My G4 is NOT rooted, and I even went into recovery mode and wiped the cache and it is still stuck in the loop. Is there anything I can do besides try a factory data reset? I really do not want to lose all of my data because I did not even get a chance to do a backup as this happened unexpectedly.

Hey did you ever get this problem solved, same thing happened to me today not rooted was watching a video phone froze and now im stuck in bootloop

This just started happening to me on Friday. I have a warranty replacement on the way (and I managed to get the guys at my Verizon Wireless store to give me a loaner Samsung Galaxy S4 so I wasn't completely without a phone all weekend).
It looks like this may be a fairly widespread problem and related to HW version 1.0 of the phones:
https://www.reddit.com/r/lgg4/comments/3k5ofv/verizon_bootloop/
https://www.reddit.com/r/lgg4/comments/3oos3e/lg_g4_stuck_in_boot_loop_pulled_battery_tried_all/
I'm hoping my warranty replacement is a 1.1 version phone, but that's probably wishful thinking on my part.

chairthrower said:
This just started happening to me on Friday. I have a warranty replacement on the way (and I managed to get the guys at my Verizon Wireless store to give me a loaner Samsung Galaxy S4 so I wasn't completely without a phone all weekend).
It looks like this may be a fairly widespread problem and related to HW version 1.0 of the phones:
https://www.reddit.com/r/lgg4/comments/3k5ofv/verizon_bootloop/
https://www.reddit.com/r/lgg4/comments/3oos3e/lg_g4_stuck_in_boot_loop_pulled_battery_tried_all/
I'm hoping my warranty replacement is a 1.1 version phone, but that's probably wishful thinking on my part.
Click to expand...
Click to collapse
i read about the problem with the motherboard going bad i thought it had more to do with the serial number or the manufacture date mine was 505, anyway i recieved my replacement from lg and new serial is 512 but HW version is still 1.0

Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.

Galaxy S20 Ultra Boot Looping / Shutting Down

Hi, I have a Galaxy S20 Ultra 512GB from T-Mobile. I have an issue that manifested itself a couple of hours ago, and have never encountered anything like it.
My S20 seems to be shutting itself off every time it boots fully and I have no idea how to fix it. I have tried safe mode, clearing cache, etc. Nothing has fixed it so far.
Is there anyone that could guide me in the right direction to potentially fix this, or do I have an expensive paperweight?
Edit: I have tried factory resetting as well now, and that did nothing to fix the issue. It gets part of the way through setup, then reboots again. Maybe I could be directed to try flashing the latest update file?
Edit #2: I was able to figure out how to fix the issue entirely and no longer require help, unless the issue crops up again.
Edit #3: I have no idea what's causing the issue but it's back. Phone shuts off after some time of use, I have no idea what to do at this point...

In case the issue persists after a factory reset and not using a backup to restore the phone I would suppose that the unit is defective and return it, if possible. If return is not possible, you could try and have Samsung repair it as it must be covered under some warranty, as it is brand new.

corwin_amber said:
In case the issue persists after a factory reset and not using a backup to restore the phone I would suppose that the unit is defective and return it, if possible. If return is not possible, you could try and have Samsung repair it as it must be covered under some warranty, as it is brand new.
Click to expand...
Click to collapse
Yeah... I tried to get into contact with T-Force to have T-Mobile send me a replacement as I am still financing the phone, but it looks like they don't even have it in stock and mistakenly are trying to send me a downgrade S20+ variant instead... Looks like I have a very expensive paperweight on my hands.
As for Samsung, all they were able to offer me at this point was to take it to a service center but with the pandemic limiting everyone to be able to work or go outside I don't think I can even do that at this point.

Nathaniel9001 said:
As for Samsung, all they were able to offer me at this point was to take it to a service center but with the pandemic limiting everyone to be able to work or go outside I don't think I can even do that at this point.
Click to expand...
Click to collapse
In EU Samsung offer courier pickup for repairs ... ask Samsung again if you can send your faulty handset in for repair

Nathaniel9001 said:
Hi, I have a Galaxy S20 Ultra 512GB from T-Mobile. I have an issue that manifested itself a couple of hours ago, and have never encountered anything like it.
My S20 seems to be shutting itself off every time it boots fully and I have no idea how to fix it. I have tried safe mode, clearing cache, etc. Nothing has fixed it so far.
Is there anyone that could guide me in the right direction to potentially fix this, or do I have an expensive paperweight?
Edit: I have tried factory resetting as well now, and that did nothing to fix the issue. It gets part of the way through setup, then reboots again. Maybe I could be directed to try flashing the latest update file?
Edit #2: I was able to figure out how to fix the issue entirely and no longer require help, unless the issue crops up again.
Edit #3: I have no idea what's causing the issue but it's back. Phone shuts off after some time of use, I have no idea what to do at this point...
Click to expand...
Click to collapse
It doesn't say what you tried to do to fix this - so if you haven't already -- I suggest downloading the most recent firmware (via Frija) and then flash in Odin. Don't use the HOME CSC - use the other one, this will force you to wipe data when it first boots up - when finished, it will boot up and you can set it up like a new phone.
If you don't already have it, you can download FRIJA here: https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Be sure to use the most recent patched Odin - https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
If this doesn't work, then it is most likely a hardware issue - but try this first to be sure.
Hope this helps.

Geekser said:
It doesn't say what you tried to do to fix this - so if you haven't already -- I suggest downloading the most recent firmware (via Frija) and then flash in Odin. Don't use the HOME CSC - use the other one, this will force you to wipe data when it first boots up - when finished, it will boot up and you can set it up like a new phone.
If you don't already have it, you can download FRIJA here: https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Be sure to use the most recent patched Odin - https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
If this doesn't work, then it is most likely a hardware issue - but try this first to be sure.
Hope this helps.
Click to expand...
Click to collapse
Hi, I tried exactly this process and the issue came back after a few minutes of using the phone along with a bit of graphical corruption when trying to use the phone. I'm guessing it's definitely a hardware issue. That's too bad though, I tried to get a replacement through T-Mobile and they have none in stock, I guess I'll see if I can get Samsung to replace it.

Good luck!

Geekser said:
Good luck!
Click to expand...
Click to collapse
Thank you! It's been a week now and I made a ticket with Samsung to have the phone repaired the same day I posted about it. I finally received my repaired phone, it turns out there was indeed a bad SoC on the motherboard and they went ahead and replaced the board, so I got to keep the phone I bought. It's too bad I couldn't recover my data, although I don't feel too bad about it anymore.
Mods feel free to close the thread, as this has been solved.

Nathaniel9001 said:
Thank you! It's been a week now and I made a ticket with Samsung to have the phone repaired the same day I posted about it. I finally received my repaired phone, it turns out there was indeed a bad SoC on the motherboard and they went ahead and replaced the board, so I got to keep the phone I bought. It's too bad I couldn't recover my data, although I don't feel too bad about it anymore.
Mods feel free to close the thread, as this has been solved.
Click to expand...
Click to collapse
Glad to hear it all worked out for the best. Hope you enjoy your phone!