Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
thomasanderson said:
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Plug it into your computer (you'll notice that there will be a longer black screen in-between the bootloops) and hold down the power button for at least 10 seconds or more, then release it after the next vibration and the white BLU screen shows up. It might take a couple of tries.
If you manage to boot into at least recovery but can't boot into the system, then try clearing your cache/dalvik cache and try rebooting into system again.
If all of the above doesn't work for you, then your boot.img/system has gone bad, and you'll have to flash the stock images with SP Flash Tool (both of which can be found on other posts on this forum).
follow the instructions on the SP flash tool thread... sounds like what happened to me after bad flash... theres a lot of information in that thread that will set you up...
Thanks for the quick replies guys. The PC trick didnt work at all. I just called BLU and asked for a replacement(havent heard back from them ironically). I put the phone in the basement so I wouldnt have to deal with that incessant buzzing every 15 seconds. Eventually the battery died. Since I had it powered off finally, I plugged it in for about 10 minutes to give it enough of a charge to power on but not stay on to buzz for another 2 hours. This time I powered it on using the master reset button combo and was finally able to wipe the cache and restart the phone. Took a good 4 or 5 minutes to boot after that, but everything has been fine since. Really dont know what initially caused the issue, never happened before. Good thing too, cause BLU told me that they would send me a RMA within the hour and I still havent heard from them. Think this will be my last BLU phone. Thanks for the assist.
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
bolanoboyboom said:
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
Click to expand...
Click to collapse
??????
My phone is basically out of the box and I'm getting boot loop problems when I first boot. This happens like once a month
Sent from my PURE XL using XDA-Developers mobile app
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Update
num1greeter said:
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Click to expand...
Click to collapse
I tried to flash the phone, but the bootloop apparently wouldn't allow that. I had 0.0% progress after 3 hours. I then tried to go back into the menu you get from {Power}{Vol UP}: still no go. So, I started to take the phone apart again to get ready for shipping. The battery was still low so it didn't take long for it to die after I unplugged it from the computer. Out of curiosity, I tried to repeat finding the menu like I did earlier that day (conditions were that the phone had no charge when I connected it to the computer, and my SD card was removed.) No go. But, then I hit {Power}{Vol Up}{Vol Down} just to see what happened, and boom. My phone loaded up. No loop... Figured somehow the files had copied and the status bar was wrong. Turned the phone off, put my SD card back in and turned the phone on. Loop reappears ...I waited for the phone to die again, took out the SD, attempted to turn it on and the loop was there. Connected it to the computer and hit all 3 buttons, and the phone loads up. So, now I'm confused. Is there any way that the problem is some crappy connection to the SD?
Related
Hello.
I have searched the forums about my issue, and although there are a lot of threads about phones rebooting, there was none about such exact problem as I am experiencing. I apologize if I missed a thread which tackled this problem.
Symptoms:
1. my galaxy S 4G reboots about every 3 seconds: it only gets to the very first "Samsung Galaxy S 4G T-mobile" logo, and reboot
2. it is possible to access boot menu (volume up+down), but only for a split second, and phone reboots again
3. rebooting starts as soon as in put battery in, no need to even press the power button
All that started by itself yesterday. I thought it was a mechanical fault with power switch, I opened the phone, unscrewed covers, cleaned everything, but found no mechanical issue. I switched batteries, tried starting the phone of plugged-in charger, on usb cable, took out sd card, sim card, put a different sim card in... and nothing helped.
Phone runs on Gingerbread 2.3, stock by T-mobile, never had any other roms on it. Device is rooted.
If anyone has an idea how to approach this issue, please let me know. Or reply with a link to somewhere I can read more. I was not able to find much on this...
Thank you!
Malarz
The phone sometimes does a reboot loop if u take the battery out of the phone without turning the power off. Just keep trying to turn it on, and eventually it would reboot properly. Take the battery out of the phone for a few minutes, put it back and try to turn it on again. Do this a few times to see if it boot back properly.
Hit the thanks button if it helps. It's my motivator to be more helpful.
gizmoscoop said:
The phone sometimes does a reboot loop if u take the battery out of the phone without turning the power off. Just keep trying to turn it on, and eventually it would reboot properly. Take the battery out of the phone for a few minutes, put it back and try to turn it on again. Do this a few times to see if it boot back properly.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Click to expand...
Click to collapse
Thank you for a prompt reply!
I did take out battery for a long time, well over one hour, and took out sim card and sd card as well. Unfortunately reboot loop started immediately when I placed battery back in the phone. That's what made me think it was a mechanical issue with power button.
I will try keeping battery out a few times again today.
One other thing: the phone had been in hot and humid environment for about 30 minutes before this happened. Not the first time for this phone to experience high humidity, though. However, I did not find any moisture inside the unit.
Malarz
I had this happened to my phone. Just wait it out and keep trying to reboot, it will come around. Take the battery out and put it back on. Keep on repeating this step.
Also, when the phone is on, try to hold the volume - + and power button at the same time to see if u can get into boot mode.
Also u can use hair blow dryer to blow dry area around the power button.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Or, batt is dead...
You have a stuck power button. Take apart the phone and clean the power bottom with compressed air. Then rapidly push the button in and out for a while.
Resolution:
I took the phone apart, and checked the power button (which had been my first guess), and was seemingly all right.
The battery was also not the issue, as I tried 3 different batteries.
Having no other choice, I put the battery back in, and let the phone happily reboot at its own leisure. After over 20 reboots, the system came on. Then a few minutes later the device rebooted again, and the loop started all over. After a while it booted up again. This time I did not wait for the device to reboot by itself, and I switched the phone off with power button, and then turned back on, and it booted normally. Repeated this once more - normal boot again. One more power off, and I entered the boot menu and did factory reset. Once the stock reinstalled, everything would work perfectly - no more issues with boot loop.
So it seems to me as a software problem more than anything else.
Side note: for the last several weeks the phone displayed strange behavior, that is the screen would light up for no reason by itself, and quickly go off. Sometimes it happened once every few minutes, sometimes it happened several times a minute. Did it have anything to do with the boot loop? No idea. But it strengthens my hunch about a software issue, as that behavior also went away after factory reset.
Sorry for the lengthy post, but since I have not found a similar case anywhere in the forums, I though someone might find this interesting. I do not deal with phones except as a user, but some of you guys do it maybe professionally, so maybe this will be a curious puzzle for you to solve.
Malarz
It sounds like Gremlins....
Sent from my Amazon Kindle Fire using xda app-developers app
Do you have notifications set up? It could notify that u have incoming messages such as a text or an email.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Malarz said:
Resolution:
I took the phone apart, and checked the power button (which had been my first guess), and was seemingly all right.
The battery was also not the issue, as I tried 3 different batteries.
Having no other choice, I put the battery back in, and let the phone happily reboot at its own leisure. After over 20 reboots, the system came on. Then a few minutes later the device rebooted again, and the loop started all over. After a while it booted up again. This time I did not wait for the device to reboot by itself, and I switched the phone off with power button, and then turned back on, and it booted normally. Repeated this once more - normal boot again. One more power off, and I entered the boot menu and did factory reset. Once the stock reinstalled, everything would work perfectly - no more issues with boot loop.
So it seems to me as a software problem more than anything else.
Side note: for the last several weeks the phone displayed strange behavior, that is the screen would light up for no reason by itself, and quickly go off. Sometimes it happened once every few minutes, sometimes it happened several times a minute. Did it have anything to do with the boot loop? No idea. But it strengthens my hunch about a software issue, as that behavior also went away after factory reset.
Sorry for the lengthy post, but since I have not found a similar case anywhere in the forums, I though someone might find this interesting. I do not deal with phones except as a user, but some of you guys do it maybe professionally, so maybe this will be a curious puzzle for you to solve.
Malarz
Click to expand...
Click to collapse
Hardware not software. You had a stuck power button. By forcing the reboot with the power button you unstuck it. If you don't believe it research Occam's razor. Glad you got it fixed(unstuck) though.:victory:
EDIT: Here are some other people who have had the same issue on samsung phones.
Stuck power button
Stuck power button
Stuck power button
If you need any more let me know. lol
Received my Nexus 5 today after much waiting due to Google/courier making a mess of my delivery details over the last 9 days...another story altogether.
Straight out of the box, and after putting in my SIM, I stuck the phone on charge for a bit and booted her up, though it seemed like there was a bit of charge in it (40-50%) so felt happy unplugging it during some of the set-up...syncing accounts, connecting to wifi, sending a couple of test SMS and inputting my carriers voicemail number.
Then it crashed as I was reading a text, and wouldn't turn on again.
I put it down to teething problems and left it alone and on charge for a bit, and after 10 mins tried again and everything was fine. Booted up (and super fast at that). Spent another 20 mins or so messing around with wallpapers and adding a couple of apps that I use daily.
Stick it in my pocket to run a quick 10 minute errand (including trying to pair it with the Bluetooth in my car, unsuccessfully), and when I get back to the office I find the phone had shut down in my pocket, and it has now been unresponsive for the last 2+ hours.
I've tried leaving it on charge. Tried every combination of holding down buttons to elicit any kid of response, but absolutely nothing. Not so much as a screen flicker.
Would anyone have any advice on things I could try before I contact Google and pack it back off to them? I'm out of ideas. I can't get it to respond in any way to anything!
robotsonic said:
Received my Nexus 5 today after much waiting due to Google/courier making a mess of my delivery details over the last 9 days...another story altogether.
Straight out of the box, and after putting in my SIM, I stuck the phone on charge for a bit and booted her up, though it seemed like there was a bit of charge in it (40-50%) so felt happy unplugging it during some of the set-up...syncing accounts, connecting to wifi, sending a couple of test SMS and inputting my carriers voicemail number.
Then it crashed as I was reading a text, and wouldn't turn on again.
I put it down to teething problems and left it alone and on charge for a bit, and after 10 mins tried again and everything was fine. Booted up (and super fast at that). Spent another 20 mins or so messing around with wallpapers and adding a couple of apps that I use daily.
Stick it in my pocket to run a quick 10 minute errand (including trying to pair it with the Bluetooth in my car, unsuccessfully), and when I get back to the office I find the phone had shut down in my pocket, and it has now been unresponsive for the last 2+ hours.
I've tried leaving it on charge. Tried every combination of holding down buttons to elicit any kid of response, but absolutely nothing. Not so much as a screen flicker.
Would anyone have any advice on things I could try before I contact Google and pack it back off to them? I'm out of ideas. I can't get it to respond in any way to anything!
Click to expand...
Click to collapse
Try pressing and holding the Power and both Volume Buttons for about 15 seconds. Then try to boot.
abaaaabbbb63 said:
Try pressing and holding the Power and both Volume Buttons for about 15 seconds. Then try to boot.
Click to expand...
Click to collapse
Tried this (which I'd tried to no avail previously), and no joy. Wouldn't boot afterwards.
Left it on charge (which it had been for the 20mins previous to trying this) for another 10 mins. Came back to it, pressed power and it just came on. No boot. It was just already on.
Veeery confused now after trying intermittently to get it to boot for what is hours now.
Should I do a factory reset?
I'll log with Google that this has happened so there's less come-back if it dies again and I need to return it. Haven't tried it with a SIM in yet (need a working phone!), but will report back after that.
robotsonic said:
Tried this (which I'd tried to no avail previously), and no joy. Wouldn't boot afterwards.
Left it on charge (which it had been for the 20mins previous to trying this) for another 10 mins. Came back to it, pressed power and it just came on. No boot. It was just already on.
Veeery confused now after trying intermittently to get it to boot for what is hours now.
Should I do a factory reset?
I'll log with Google that this has happened so there's less come-back if it dies again and I need to return it. Haven't tried it with a SIM in yet (need a working phone!), but will report back after that.
Click to expand...
Click to collapse
I'd fully charge it before doing anything else.
jd1639 said:
I'd fully charge it before doing anything else.
Click to expand...
Click to collapse
Have done now. It's charged and I'm about to retry the SIM.
Possibly of note, after I checked it and saw that it had restarted, I checked the battery log and it showed that it had been running for 29m 25s on battery...yet was on charge. I'd attach the screenshot but I haven't posted here enough times for the forum to let me
It was unresponsive no more than 10 mins previously. 10 minutes would be generous.
Anything I can learn from that?
So the phone lasted all night with some light use. Left my Nexus 4 on with no SIM for alarms so I knew I could wake up this morning, but instead, to my joy, I had two phones alarming at me together!
So it was to my dismay that after I'd read some mails, checked some sites, and left the phone to go and get ready for work for 10mins...I came back to it dead again.
I heard some notifications come through (and I was in the middle of a conversation on WhatsApp, so that was normal). I saw the notification light flashing too, so the messages coming through, or at least the first one, didn't crash it.
It did however start up again, with no SIM, after some cajoling.
Is there some way I can see an error log, or a crash log? Or anything I can install to log this for the next inevitable time? Or is this sounding like a permanent hardware issue and I'll need to return the unit?
There's a thread somewhere you can find it, it will show you how to install stock firmware again.
Do that and if it occurs again, call Google to get a RMA
Sent from my Nexus 5 using XDA Premium 4 mobile app
Re-installing the firmware won't jeopardise my position in sending it back to Google, no?
Just went back to it to put the SIM back in it and it's unresponsive again. FFS.
robotsonic said:
Re-installing the firmware won't jeopardise my position in sending it back to Google, no?
Just went back to it to put the SIM back in it and it's unresponsive again. FFS.
Click to expand...
Click to collapse
No, but you have to unlock the bootloader first before you can flash a factory image and install adb (platform-tools) on your pc, and afterwards relock the bootloader again before sending it to Google.
Hi,
Guys I am going through some **** right now. Plese read the scenarios below and help me. I got no help at the oneplus forums.
Scenario 1 -
My phone was working fine until last night, I mean this is when I last used it. I switched it off and went off to sleep and in school today when I was trying to power it on the boot logo came and it went and after many tries the cyanogen logo came and it went away there is 80% battery. It doesn't charge also, like the phone recognises the charger but remains at 80% when I go to recovery try wiping cache and data, the phone switches off in few seconds. I can go into fastboot and stay for like 3 seconds then the phone switches off but I can connect it to power and keep it. I am on stock, latest CM12S. The only unusual thing I did yesterday on my phone is that I charged it using a different adapter but same cable. I can't seem to find this issue on google.
Scenario 2 -
Guys,
My phone's really messed up and I am scared to tell my dad cause he warned me before getting it for me. After the OnePlus logo comes, when I press the volume button and hold it, it works and as soon as I leave the volume button, the phone switches off. What is wrong? Do I need to send it back. I got it from Oneplus.cn so I am a bit worried and it's going to be tough to check what's happening.
Scenario 3 -
I removed cm12s and tried to flash oxygenos and I failed so then I installed cm11s and still have the problem, my phone can only boot in safe mode and as soon as I leave the volume button it switches off, same for recovery. Used the onplus toolbox by Inthiaano to install CM11S 44S.
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
ZMaissi said:
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
Click to expand...
Click to collapse
Thanks, that is sort of what I was thinking. I suspect the boot partition is corrupt. But, wasn't sure being a new customer with Verizon.
Hey can you link me something about how you downgraded your droid ultra from SU6-7.2 to SU6-7
LOL, just flash SU6-7 (CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml) with RSD-Lite. That's the easiest way.
rfunderburk39 said:
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Click to expand...
Click to collapse
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Mangu said:
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Click to expand...
Click to collapse
In the case of my phone, you could hold the power button in for a long period of time and then release and still nothing, not a flicker. I did not try voice commands, not a bad idea, but I did not want to open the phone due to the fact it was being replaced (further risking a decline on replacement).
On a similar note, the new unit seems to reboot at least once daily.
I've had this phone for about 2 months now, and from the beginning, it's had an issue where it would randomly freeze, restart, and get stuck in a boot loop for random amounts of time. Sometimes it would be fine after 2 minutes, sometimes it would need 10. I kept thinking this was a firmware issue - the phone WAS rooted with TWRP installed, but none of my past phones have had this issue and hardly anybody online seems to have had it, either - and just thought that maybe installing a custom ROM would fix it, but never got around to doing so.
3 days ago, my S7 went into a boot loop again, so I just decided to put it down and let it do its thing. After 20 minutes, however, it still wasn't booting, so I booted into TWRP, and cleared the cache and Dalvik cache. Another 20 minutes later, I went into panic mode and started doing Nandroid backups of my stuff. I decided that I had no other choice but to commence with finding a ROM to replace stock. In the meantime, I just plugged it in and let it keep looping, hoping against hope that it would just fix itself like it always did.
About half an hour later, I was ready to install the ROM I'd decided on. I went and picked up my phone, but all that I saw was the screen was black, and the blue notification LED was lit up. I tried holding Vol- + Power to start booting it into TWRP, but nothing happened. The phone didn't vibrate, the screen didn't change, and the LED stayed lit. I tried holding every button combination possible, for even as long as a minute, but the phone refused to respond. I tried plugging it into my computer, but Windows didn't detect anything.
Skip to today, and the phone's battery has long since died(the LED isn't lit up, so I can only assume...), and I just decided to plug the phone in for the hell of it just to see if maybe it would maybe work again. To my astonishment, 2 minutes later, the battery icon came up on the screen, but the charging animation wasn't there. When I held Vol- + Power, the phone actually responded and restarted! Though, it wouldn't boot past the Galaxy S7 splash screen, and when I tried to boot it into TWRP, it went back to being a brick. I let it sit for about 10 minutes, plugged it in, and this time tried to get it into Download Mode, and it worked!
I downloaded the Switzerland version of the G930F firmware, flashed it in Odin, and everything seems to have worked. Odin says it succeeded, but when the phone tried to restart, it got to the splash screen, and after a few minutes, the screen went black again. When I plug it in now, the Galaxy S7 screen will come up, but now I can't seem to get into Download Mode anymore(though, it DOES still seem to respond to me pressing Vol- + Power).
Does anyone have any idea what's going on? I can only seem to find 3 or 4 other threads on various forums about this problem, but none of them have any answers. People just keep saying the usual "Hold Vol- and Power to make the phone restart", but in case I haven't made it clear, THAT ISN'T WORKING.
And before you suggest that I return it to where I bought it for a replacement or refund: I bought this phone on eBay from a seller who said it was in pretty much mint condition. When the phone arrived, there was not a dent or scratch anywhere on the phone, even around the charger port, so I have no reason to believe he was lying. When I asked him about any possible problems with the phone's operational stability the other day, he says he tested it for about 2 weeks, and that he didn't notice anything.
Sounds like a hardware fault, not much else you can do other than flashing stock and factory resetting, which you've done
Considering it had a fault from day 1 it sounds like that fault finally caught up with it
Likely scenario if sent for repair, new motherboard replacement needed