So my wife has had her Note 8 a couple months and has been experiencing soft brick problems. Her phone will go to sleep and then won't wake up. It can only be started in safe mode and then restarted normal. We started to think it was the phone so we sent it back and Verizon sent one of their lovely factory referbs as a replacement. I felt after having the phone for only a month she should get a new one but that's a whole other story. Anyway back on topic, her replacement has the same problem. I'm starting to think this is more of a problem with the software and not a hardware issue and was wondering if anyone here has had the same type of problem? Before anyone comments with searching Goggle, yes I've done that, cleared the cache,reset the phone, and it still randomly soft bricks.
xVallex said:
So my wife has had her Note 8 a couple months and has been experiencing soft brick problems. Her phone will go to sleep and then won't wake up. It can only be started in safe mode and then restarted normal. We started to think it was the phone so we sent it back and Verizon sent one of their lovely factory referbs as a replacement. I felt after having the phone for only a month she should get a new one but that's a whole other story. Anyway back on topic, her replacement has the same problem. I'm starting to think this is more of a problem with the software and not a hardware issue and was wondering if anyone here has had the same type of problem? Before anyone comments with searching Goggle, yes I've done that, cleared the cache,reset the phone, and it still randomly soft bricks.
Click to expand...
Click to collapse
why you don' try to install the current software that your wife phone is running using odin?
android-incredible said:
why you don' try to install the current software that your wife phone is running using odin?
Click to expand...
Click to collapse
She has the current software. I'm starting to think the last update might have been the problem.
The phone has the December security patch?.
android-incredible said:
The phone has the December security patch?.
Click to expand...
Click to collapse
Yes the phone has the December security patch. It's been soft bricking since before that though.
xVallex said:
So my wife has had her Note 8 a couple months and has been experiencing soft brick problems. Her phone will go to sleep and then won't wake up. It can only be started in safe mode and then restarted normal. We started to think it was the phone so we sent it back and Verizon sent one of their lovely factory referbs as a replacement. I felt after having the phone for only a month she should get a new one but that's a whole other story. Anyway back on topic, her replacement has the same problem. I'm starting to think this is more of a problem with the software and not a hardware issue and was wondering if anyone here has had the same type of problem? Before anyone comments with searching Goggle, yes I've done that, cleared the cache,reset the phone, and it still randomly soft bricks.
Click to expand...
Click to collapse
Sorry you are having issues and that you have been sent a refurbished replacement. It would probably be a good idea to download the factory firmware and flash in Odin, even though it is the same version...reason being, a factory firmware flash can eliminate most corrupted software issues...
You can download your firmware and then follow the guide here:
https://forum.xda-developers.com/showpost.php?p=74087340&postcount=1
If the device continues to do the same thing...there may be an app or setting causing the disturbance...
Where can i download the stock firmware?
Related
hey
my phone has been acting weird for a while now.
the phone crashes a lot, some times it freezes while scrolling, some times it shuts down, some times it restarts on its own....
i tried to root the phone and flashed it with wanam, but it didn't stop crashing, then i flashed with omega v12, but the problem still continued...
shall i rule out that this might be a software issue?
what hardware part might be causing such behavior
ashrafezz said:
hey
my phone has been acting weird for a while now.
the phone crashes a lot, some times it freezes while scrolling, some times it shuts down, some times it restarts on its own....
i tried to root the phone and flashed it with wanam, but it didn't stop crashing, then i flashed with omega v12, but the problem still continued...
shall i rule out that this might be a software issue?
what hardware part might be causing such behavior
Click to expand...
Click to collapse
That doesn't sound good...
IMO it's most likely a hardware issue.
It's hard to say which part is causing this. Maybe the storage?
I hope this aren't SDS symptoms.
That would mean that SDS would be still possible with 4.1.2
muena90 said:
That doesn't sound good...
IMO it's most likely a hardware issue.
It's hard to say which part is causing this. Maybe the storage?
I hope this aren't SDS symptoms.
That would mean that SDS would be still possible with 4.1.2
Click to expand...
Click to collapse
i have no clue what that would be
i have the insane chip, but i do not know if this is sds or not
the phone hadent been stable since the 4.1.2 upgrade....
ashrafezz said:
i have no clue what that would be
i have the insane chip, but i do not know if this is sds or not
the phone hadent been stable since the 4.1.2 upgrade....
Click to expand...
Click to collapse
AFAIK if you had the SDS symptoms before the update, it is possible that you experience SDS after the 4.1.2 update.
I would backup all data, restore stock kernel/rom, unroot and return the phone for warranty.
ashrafezz said:
i have no clue what that would be
i have the insane chip, but i do not know if this is sds or not
the phone hadent been stable since the 4.1.2 upgrade....
Click to expand...
Click to collapse
use eMMC Brickbug to check using the memory test. In theory if it fails it is affected by SDS and your phone will die someday. If not it could be another problem. But as I said it is just "in theory", nothing 100% sure.
Sent from my GT-N7100 using xda app-developers app
aka_sirok said:
use eMMC Brickbug to check using the memory test. In theory if it fails it is affected by SDS and your phone will die someday. If not it could be another problem. But as I said it is just "in theory", nothing 100% sure.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
done that.
it passed the memory test although it has the insane chip.
i have no clue what this is, i bought it from the grey market so i just have a shop warranty.
am sending it in tomorrow for them to check it.
if nothing happens, i will have to send it to the official Samsung service.
appreciate your kind reply
ashrafezz said:
done that.
it passed the memory test although it has the insane chip.
i have no clue what this is, i bought it from the grey market so i just have a shop warranty.
am sending it in tomorrow for them to check it.
if nothing happens, i will have to send it to the official Samsung service.
appreciate your kind reply
Click to expand...
Click to collapse
Don't jump to conclusion so fast, do you use any custom kernel? I suspected it's due to wrong configuration
Try to recall what the last stable status of your phone would be help a lots...
Sent from my GT-N7100 using Tapatalk 2
sklchan said:
Don't jump to conclusion so fast, do you use any custom kernel? I suspected it's due to wrong configuration
Try to recall what the last stable status of your phone would be help a lots...
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
As he wrote in his first post, he rooted the phone because of the issues.
So it happened with stock system too.
Well new start from full wipe did it for me except I restored all apps with titanium Backup.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Well new start from full wipe did it for me except I restored all apps with titanium Backup.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Same here
had some reboots(1/day), but after factory reset and update to DMC 3 no reboots since ~12 days.
First l left ereything untouched and added step by step every 4 days root, frameworkmod, my core Apps (via titanium backup)
As I've said, lots of these crashing are due toto conflicting setting...
Sent from my GT-N7100 using Tapatalk 2
UtkarshGupta said:
Well new start from full wipe did it for me except I restored all apps with titanium Backup.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
tried to restart, and factory reset, and wiped the cash and made a full restore....
nothing worked
even the custom roms didn't do much
i sent it out to service to c what they have to say
ashrafezz said:
tried to restart, and factory reset, and wiped the cash and made a full restore....
nothing worked
even the custom roms didn't do much
i sent it out to service to c what they have to say
Click to expand...
Click to collapse
Please don't forget to tell us what the problem was, when you get your phone back.
muena90 said:
Please don't forget to tell us what the problem was, when you get your phone back.
Click to expand...
Click to collapse
Yup same here, would like to know the culprit of the error as well...
Sent from my GT-N7100 using Tapatalk 2
Run stress test.
Sent from my GT-N7100 using xda premium
so, i got my phone back from the shop.( it is not the official Samsung retailer, just the shop that sold me the phone).
the guys said that they re-installed software and tried several kernels.
after a week of trials of reinstalling with no success, the guy called and said the phone is ready and working fine.
i got the phone and it worked fine for 5 min, then started acting crazy again.
i decided to root to see if i could get it going,
after several trials of rooting and un-rooting, and finally out of frustration, i knocked on the phone's back where the Mother board is located and re-rooted the phone.
suddenly the phone worked without freezing for the 5 days so far....
i am still monitoring the phone, but it seems that banging on the mother board had an effect on it (as weird and silly as it might seem)
i know that my phone fell a lot and that my son dropped it like a zillion times before it went acting crazy.....
i thought maybe something moved inside, and well, it seems i was correct (so far at least)...
ashrafezz said:
so, i got my phone back from the shop.( it is not the official Samsung retailer, just the shop that sold me the phone).
the guys said that they re-installed software and tried several kernels.
after a week of trials of reinstalling with no success, the guy called and said the phone is ready and working fine.
i got the phone and it worked fine for 5 min, then started acting crazy again.
i decided to root to see if i could get it going,
after several trials of rooting and un-rooting, and finally out of frustration, i knocked on the phone's back where the Mother board is located and re-rooted the phone.
suddenly the phone worked without freezing for the 5 days so far....
i am still monitoring the phone, but it seems that banging on the mother board had an effect on it (as weird and silly as it might seem)
i know that my phone fell a lot and that my son dropped it like a zillion times before it went acting crazy.....
i thought maybe something moved inside, and well, it seems i was correct (so far at least)...
Click to expand...
Click to collapse
Do you fancy hitting mine too?
Ive had this issue the past month, I have the insane chip aswell. Sent it off to Samsung as one day, it literally just made the screen go funny (multi colours, as if you pulled a cartridge out of the n64 or a Gameboy).
Samsung then took my warranty off, as they deemed it down to a small crack in my top right glass bit, which doesn't affect the phones use at all, as it was there for 3 months. They attempted to charge me £290 for a replacement logic board, and a new glass panel for the front, whish I think isn't fair as it wasn't the screen crack that caused the SDS on my phone.
Got mine back today, and the first thing I did was download all of the tools necessary to flash the ROM, only to find that I get a FAIL message in Odin, due to a missing PIT partition or something.
I now own a fancy paperweight, as I can only put this all down to a properly franked memory chip.
my phone is rooted i'm on 13B everything was fine since i got my phone back in august till today i was listening music and was gonna skip to next song that moment is when my phone froze completely after pressing the power button the phone reboot by itself but got stuck on the lg screen i removed the battery after a few attempts it turned on. after 30 minutes or so it rebooted it self again but now even removing the battery it won't pass the lg screen. any ideas? suggestions?
probably the same problem a lot of other people are having. I also had the same symptoms as you, on rooted 13B.
you can try resetting or reflashing your phone but most likely you need a replacement.
theirs a problem with the motherboard going bad, i just had the same problem and lg sent me a replacement under warranty but i wasnt rooted
dagnisaun said:
probably the same problem a lot of other people are having. I also had the same symptoms as you, on rooted 13B.
you can try resetting or reflashing your phone but most likely you need a replacement.
Click to expand...
Click to collapse
bayniner said:
theirs a problem with the motherboard going bad, i just had the same problem and lg sent me a replacement under warranty but i wasnt rooted
Click to expand...
Click to collapse
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.
killa408shark said:
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.
Click to expand...
Click to collapse
How were you able to flash 13B if it was stuck in a bootloop, ive already recieved my replacement but id like to factory reset my old one before i send it back
bayniner said:
How were you able to flash 13B if it was stuck in a bootloop, ive already recieved my replacement but id like to factory reset my old one before i send it back
Click to expand...
Click to collapse
I put the phone in download mode and flashed 13B KDZ. But unfortunately my phone got back in the bootlop. Good thing I'm gettingmy replacement
It's a hardware issue, not software. A lot of the earlier G4s have "loose contacts" that cause the bootloop to occur. LG has acknolwedged it and are replacing any affected phones without incident. Just call verizon and they'll ship a new one.
Yup, happened to me just his week. VZW shipped another one to arrive the next day. FWIW, I strongly recommend everyone backup their phone to removable SD card using LG's on board Backup utility. If this challenge happens to you, getting back up and running quickly will be much easier if you have this backup ready to go.
...my $.02.
Happened to me as well last night. Took it back to Verizon today and they are sending me another one. I didn't have insurance and no questions were asked. Obviously they recognize the problem. Last LG phone I will own! Unless the G5 is insane. Hehe
Happened to me as well, yesterday. Interesting how this is happening to everyone at almost the same timeframe. I'll take it to Verizon to get a replacement shipped.
I had the same problem, and contacted LG support and they said it will take 9 business days to repair the phone. This seemed like an awful long time to be without a phone, I asked if there was any way to speed the process up and they said no. Thankfully I was able to borrow a phone from work for the duration of the repairs. Considering how this is a major problem with many handsets, I think LG is handling the whole situation pretty badly.
Hi. I have a genuine AT&T note 4 that I got when it was released, ergo it's fairly old. Ever since a few days ago, the phone has been slow to open things, freezing for a few seconds before responding trying to do just about anything. When it "freezes" after I attempt to do something (like open an app, swipe a page, use keyboard, turn off wifi, etc etc) absolutely nothing responds; the 2 buttons on the front, the power button to turn the screen off, nothing. The time that it stays frozen has increased, and now it might stay frozen so long i just take the battery out.
The oddest thing about this to me is that the phone will function normally, too; it still functions fast and responsively 50% of the time, it doesn't freeze every time i try to open something, for example. There seems 0 pattern to it. I've already tried a factory reset, helped a little at first and now seems the same again.
What do I do? What's wrong with it?
If it's still under warranty get it replaced. Mine did the same last month and was able to get a replacement through my Square Trade warranty service. Resetting the phone didn't help with issue either and that's ATT Best Buy, Samsung will recommend doing 1st.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Grr said:
If it's still under warranty get it replaced. Mine did the same last month and was able to get a replacement through my Square Trade warranty service. Resetting the phone didn't help with issue either and that's ATT Best Buy, Samsung will recommend doing 1st.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
I doubt it is, and my screen is cracked too, so I don't think they'd take it. If they would though, a new phone would be nice lol
Try to reset cacne by going to recovery mode
Sent from my Samsung Galaxy Note 4 using XDA Labs
Try a factory reset. I had issues similar to yours and it definitely helped. Be sure to back your data up before hand.
Seams like bad nand flash. I had same issue with my nexus 7 2012. That thing has so many annoying issues that i sold it eventually. Try resetting and cache clear and do not install any 3rd part app for few days. If it stays smooth and fast then its app issue not the nand issue. If starts to behave as expected stuck 50? of time then it is definitely nand issue only hardware fix (replacement will fix it).
If you are a curious type like me you should try odin. It will reset every thing of your device and probably fix any known software issue (flashing has risk u may brick your device)
xateeq said:
Seams like bad nand flash. I had same issue with my nexus 7 2012. That thing has so many annoying issues that i sold it eventually. Try resetting and cache clear and do not install any 3rd part app for few days. If it stays smooth and fast then its app issue not the nand issue. If starts to behave as expected stuck 50? of time then it is definitely nand issue only hardware fix (replacement will fix it).
If you are a curious type like me you should try odin. It will reset every thing of your device and probably fix any known software issue (flashing has risk u may brick your device)
Click to expand...
Click to collapse
It's not smooth and fast, so I tried to reset with ODIN and resulted in more problems.. refer to
http://forum.xda-developers.com/note-4-att/help/numerous-problems-flashing-stock-t3458982
and help if you can please!
thank you.
I am afraid I have only bad news, I myself did a odin flash oday twice and it went through without a hitch. It seams like odin failed to write to a partition hence failed the over all process. My previous statement is valid. Your phones nand memory is at its last breath. If u cant affort to replace your phone then try getting it repaired. A motherboard replacement sbould fix the issue. Ebay search can belp you with that and. Ite 4 is an old device so replacement should be faily easy to find.
Hi all, I have a HTC 10 unlocked version which is running Android 7.0, Software version 2.41.617.3.
I've owned the phone since October, around November it started randomly rebooting. It occurred maybe once every few days or once a week and the frequency increased.
I sent the phone to HTC for repair earlier this month, and they sent it back saying they couldn't reproduce the error.
I had thought the issue was my SD card, so since receiving the phone this week from HTC I have not installed my SD card. The phone worked 3 days before randomly rebooting an hour ago.
I've sent all the crash log files to HTC, and now realize that I might have not sent them at all.
I know others have had this issue with their HTC 10, has anyone figured out a cause?
Also, is the replacement phone from Uh-Oh protection new in box or a refurbished phone?
Highlyanimated said:
Hi all, I have a HTC 10 unlocked version which is running Android 7.0, Software version 2.41.617.3.
I've owned the phone since October, around November it started randomly rebooting. It occurred maybe once every few days or once a week and the frequency increased.
I sent the phone to HTC for repair earlier this month, and they sent it back saying they couldn't reproduce the error.
I had thought the issue was my SD card, so since receiving the phone this week from HTC I have not installed my SD card. The phone worked 3 days before randomly rebooting an hour ago.
I've sent all the crash log files to HTC, and now realize that I might have not sent them at all.
I know others have had this issue with their HTC 10, has anyone figured out a cause?
Also, is the replacement phone from Uh-Oh protection new in box or a refurbished phone?
Click to expand...
Click to collapse
Did they send it back in the same condition, or did your phone come back with all of your apps and data still intact?
You could try to run the US Unlocked RUU to see if that fixes it ( it should), and run it without restoring any data.
xunholyx said:
Did they send it back in the same condition, or did your phone come back with all of your apps and data still intact?
You could try to run the US Unlocked RUU to see if that fixes it ( it should), and run it without restoring any data.
Click to expand...
Click to collapse
Thank you for the suggestion.
I went through all of the standard troubleshooting before they escalated me to repair status.
First I did safe mode, after it rebooted in safe mode I did a factory data reset. After the reset I did a cache wipe and that didn't work. I also did a cache wipe, and factor data reset. Finally, I installed the RUU from their webpage and the problem persisted.
I wiped the phone and set it back to them, they were unable to get the phone to reboot during the 2-3wks they had it.
Any other suggestions, or answers to the question about Uh-Oh protection?
Highlyanimated said:
Any other suggestions, or answers to the question about Uh-Oh protection?
Click to expand...
Click to collapse
The replacement phone can be either refurbished or new, according to the ToS from HTC.
I just received my Uh Oh replacement from HTC the other day, and it looked new but was not in a retail box. It was shipped by Ingram Micro which is a wholesaler.
Too bad my replacement is doing the exact reboot thing you described, which is why I am reading the forums tonight. Sigh.
auggie721 said:
The replacement phone can be either refurbished or new, according to the ToS from HTC.
I just received my Uh Oh replacement from HTC the other day, and it looked new but was not in a retail box. It was shipped by Ingram Micro which is a wholesaler.
Too bad my replacement is doing the exact reboot thing you described, which is why I am reading the forums tonight. Sigh.
Click to expand...
Click to collapse
Sorry to hear that Auggie,
For the past 9 days I haven't had any reboots. Solution, turn off 4G LTE and use only GSM/WCDMA. Perhaps give that a try, if the same thing happens, then I think it means there's an issue with the radio (firmware/hardware).
Sucks, because service here on AT&T in LA is worse than when I lived in NYC and no LTE is like torture.
Thanks, this workaround solved my HTC reboot issue, keep using 3g is a pain but at least no need to buy a new phone. HTC supports or technicians really don't understand and know how to solve the issue
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!