Well after searching and not finding anyone with the same problem I am having I decided to share. Last night after changing the battery in my Fuze the device got stuck in a power cycle loop. Startup splash screen for about 30 seconds and then reboot. I thought maybe SD card (throwback to the old days when SDHC could screw up the device), no luck. I read a thread where a dead battery was causing a similar behavior so I tested the battery and it was full (also tried two other batteries just in case), again no dice. Tried hard reset, and the device let me perform the hard reset fine but when it completed and I "Press Vol Up to boot" the cycle started again. At this point, my ideas were exhausted. I put the phone in BL mode and flashed stock ROM and SPL so I can return it. My only thought is that the power button on top of the device is stuck somehow and that is causing the phone to turn off and on constantly.
Anyway, AT&T customer (lack of) service can't get me refurb replacement for 2 days (and they are charging me the shipping on that). What a PITA!
Sorry to be so long winded. Anyone got any ideas on what might have happened so I can avoid it with the replacement? I was using Energy 2.0 v3/15/09 at the time of problem although I'm pretty sure the ROM had nothing to do with problem (it had been stable and fast for 3 weeks before the problem occurred).
Thanks
http://forum.xda-developers.com/showthread.php?t=501470
That came up when I did a raphael search for Boot Loop .... looks like a similar issue.
About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.
Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.
The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.
Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.
----------------------------------------------
The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).
I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.
Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).
The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks
Armando Penblade said:
About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.
Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.
The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.
Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.
----------------------------------------------
The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).
I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.
Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).
The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks
Click to expand...
Click to collapse
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This doesn't seem to have any effect on the proceedings.
I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.
Armando Penblade said:
This doesn't seem to have any effect on the proceedings.
I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.
Click to expand...
Click to collapse
But that's what it's supposed to look like when it's hard bricked, keep trying to write it then boot with it. Eventually it's going to work, unless you somehow fried your motherboard.
Sent from my SCH-I535 using Tapatalk 2
Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.
Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?
Armando Penblade said:
Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.
Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?
Click to expand...
Click to collapse
Not really, if you're getting that error message I'm assuming this should work. At the very least you could get a jtag repair and that'll definitely fix it. You could always try the other debrick file available from that thread also.
Sent from my SCH-I535 using Tapatalk 2
Hi,
I have a problem with my Galaxy SIII. It is from Virgin Mobile..
I uploaded a new software update- I tried avoiding this bc the last time I did, my phones battery was horrible and GPS did not work for a better part of a week. However, the upload message would not stop after two weeks, and it would drop my calls when it was giving me the notice/and or trying, it would also knock me off internet. So I did. However, my battery started to go to crap, at 20% it would shut the phone off, later for me to come home, plug it into a charger to be at 30% not 20%. I found that odd. However, it requested again without remorse, almost 30% calls were interrpted and I thought maybe this "Update again" might fix the problems. Nope, my suspicions became true. I seen my phone with the little droid guy and it uploading. However, when I got back to the phone, it was stuck on a Samsung screen. I can power the device on and off, it will go through the motions if you will, but soon as it hits the Samsung title cannot boot past it. To note when doing the " Software Update"- I had my phone on a charger. So cannot boot past Samsung screen and it freezes there.
I can go into Safe Mode if I use the buttons manually. However, I cannot restart the phone in safe mode. A Samsung guy mentioned that there might be a way to manually type commands in safe mode- the ownly thing my phone might be still good for- using a software that would recognize the device and save info onto an SD card before flashing. He found this out by typing a google search, I tried and cannot find it. He stated the data is probably still ok without a flash. However, how did I get data out of this before a flash lol? Any ideas?
I have seen this problem online with the Edge, but no solutions other than changing the device out. Hoping someone can tell me whats going on here.
I bought this phone from Sprint on 10/7/16 and didn't have any issues until 11/7/16 (1 day out of the time for me to add insurance to get it replaced).
On to the issue. It restarts every 2 min, if I allow the screen to turn off. If plugged in and charging, it just shuts down and freezes. Have to do a soft reset to get it up and running. I have no to date done 4 factory resets, and didn't install any new apps and pulled out my Micro SD card as well. All the pre-installed apps are up to date, as well as my firmware, profile, hell even my prl is up to date. Still happening.
I have been able to stop it by turning in the "Always on Display" that shows the date, time and battery percentage. It seems to have stopped the problem, but lets face it, that's not a fix. Its a bandaid over a leaky pipe.
Anyone have any suggestions? I have called Samsung and they said I can send it in, but I don't have a backup device at the moment. I sold my Note 3 when I bought this phone. I know I can get a loaner phone from Sprint, but I don't want to pay for it.
Thanks in advance.
PS - Non rooted phone.
Hello,
I recently changed the LCD of a S6 edge. I installed it and turned it on and it booted up fine. I went to make sure everything was working. While I was playing music it would restart. I thought it was odd, so i was waited til it came back on and started using other apps. Same thing..restart. So, i booted to safe mode. Same thing...restart.
So, I tried factory resetting. After that, it would just get stuck in a endless restart loop cycle.
I have also tried reinstalling the OS using Odin. I ran Odin and it said everything passed. The phone restarts and goes to installing updates.
It gets to 32% every time then it says "erasing". After a few seconds of displaying "erasing" it just starts its endless reboot cycle again.
**EDIT: I should add that it never restarts when it's in the download manger.** So, that makes me think its a OS issue.
*EDIT#2: This is a good video. I did all of this. Got to the 9 minute mark and where his comes on, mine restarts again.
Any help?
Thank you!
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
3mel said:
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
Click to expand...
Click to collapse
Hi,
thank you for your reply. I learned about all of this last night lol. so, i'm not exactly sure what you mean. I bought the LCD+frame from Ebay. It stated it was pulled from a working unit.
Could a bad battery cause all these issues? I notice when i power down (only way I can power down is if I Hold POWER+VOL DOWN and select power down) that the LED light stays on.
Hello, could someone delete this thread. I have posted a more detailed thread on this issue.
if it says it's an LCD screen it's not an original part. my point was that some people have had issues booting up roms because of screens.
that was something that was fixed in custom roms though so if you can't another solution a custom rom that works with 3rd party LCD displays might be an option to consider.