Phone stuck after dead battery. - Verizon Samsung Galaxy S III

The past two nights I have fallen asleep with a close (30%) to dead battery only to wake up and realize it died. No biggie, my fault for not throwing it on the carger. I plugged it in and was stuck at the 'Samsung Galaxy SIII' screen. I was able to manually enter recovery and do the wipe/flash routine.
My question is, is this a symptom of a bad flash or root or something? Do I have to live in fear of a dead phone? I have never experienced this on my other phones, although I don't make a habit of letting the phone die, not withstanding the last two nights
I have since made a nandroid
I am on synergy r118.
Thanks.
Sent from my SCH-I535 using Tapatalk 2

enix316 said:
The past two nights I have fallen asleep with a close (30%) to dead battery only to wake up and realize it died. No biggie, my fault for not throwing it on the carger. I plugged it in and was stuck at the 'Samsung Galaxy SIII' screen. I was able to manually enter recovery and do the wipe/flash routine.
My question is, is this a symptom of a bad flash or root or something? Do I have to live in fear of a dead phone? I have never experienced this on my other phones, although I don't make a habit of letting the phone die, not withstanding the last two nights
I have since made a nandroid
I am on synergy r118.
Thanks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Possibly Synergy 118...possibly a bad flash even tho you would have other symptoms as well. Just try to flash any other ROM and see what happens....but also if you just pulled the battery and tried to boot it again and did...then it's most likely just caused by the leaked JB it's not good but not that terrible either. good luck :fingers-crossed:

Thanks for the reply.
I will have to wait until this weekend to try another rom....
I would think if it's a synergy issue I would not be the first to find out.
My only other thought is the battery being too dead to do anything, even with wall usb plugged in. When I got my phone to boot after flashing it would show less than 15% charge.
I will try to troubleshoot it with different roms when I get a chance and post here with the results.
Sent from my SCH-I535 using Tapatalk 2

For anyone following this.
I have decided it is an app issue. I reflashed a fresh synergy rom. I am currently restoring apps a few at a time, rebooting,then making a nand everytime it boots ok.
I will let you know what app is doing this when/if i come across it.
Sent from my SCH-I535 using Tapatalk 2

Related

[Q] Anyone have success fixing restart issues?

I've had my G2X for about a month, and have been experiencing the common issue where my phone randomly shuts off and the only way to get it to turn back on is to pull the battery.
I've installed the GB update, that didn't fix it. Factory reset didn't help either.
Has anyone successfully fixed this issue on their phone? If so, what'd you do? Is there any chance that rooting my phone would correct the problem?
Sorry if there was a post about this, I couldn't find anything talking about if anyone's been able to fix the problem.
Thanks
yes... the onlyhh way to fix the problem is to root! nvflash clock work mod recovery, then flash eagle blood 2.3.3 rom and it is perfect...
Thanks, this did indeed seems to do the trick. Not a single reboot so far after 2.5 days.
Sent from my LG-P999 using XDA App
My G2X actually restarted on its own today. It was the first time since the first few days I had the phone over a month-month and a half ago. Wasn't really a big deal, lol. It comes back on.
Have been playing with this phone for 3 days now and haven't had any issues (I did install xboarder's stock rooted version). Minor screen bleed is the only issue.
Sent from my LG-P999 using XDA Premium App
Finally, someone (dmaniscool) who can say they switched to an xda dev'ed ROM and got rid of the lock ups. I've posted many times asking if anybody ACTUALLY FIXED a problem (specifically the battery pull lock up); I got no responses, and someone finally stated it. Great. Next time my wife's G2x locks up, I'm rooting and putting a ROM on it.
Thank you dmaniscool
-Bob
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
namklak said:
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
Click to expand...
Click to collapse
Will do, so far so good! I had no experience with rooting, and was able to figure it out looking at the guides available on the forum. It kind of looks intimidating, but it's not actually very difficult.
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
RZJZA80 said:
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Mine did both actually, shut down and restarts. But mostly just shut downs, which required a battery pull to power back on.
My 2 will do both - but I think the "shut-off" is a lock up, because the longer I leave it locked up, the less battery I'll have after I do a battery pull.
8 days of both phones not locking up by doing one restart per day per phone.
Since I raised the minimum CPU speed to 389 from 216, I have far fewer sleeps of death
You don't wanna know where this was sent from.
I've tried every ROM and kernel combination possible and nothing actually fixes these problems for me.
Wow this post was scary at first, I had a thunderbolt and no matter what. RUU, Different ROMS, Stock, Kernels, Radios. Changing all that didn't matter it still turns off constantly and doesn't turn back on till I do it meaning no text or calls, basically same as having a phone on silent all the time without even having the luck chance of pulling it out while ringing.....
I am on miui x.26 (whatever kernal that comes with it) and have over 40 hours of uptime. I haven't had a crash yet, I just manually restart every couple of days because I'm weird like that.
Sent from my LG-P999
Well 6 days into it and I've had a total of 2 shutdowns. I don't know if it was a coincidence, but both times were after being outside when it was ~90 degrees out.
This is still much improved, I used to get 3-4 per day on average.
I'm using Eaglesblood 2.3.3. I'm thinking of trying MIUI because it's so nice looking.
For me I did a battery replacement the first time directly from T-Mobile and the phone continued restarting on me. I was just about to request a replacement phone from T-Mobile until I recently purchased a different brand of battery containing the same specs as the stock battery and to my surprise no overheating and definitely no restarts. I feel that the restarts and lockups are due to faulty batteries shipped out with the phones. I'm suprised no one has mentioned this.
Sent from my LG-P999 using Tapatalk
Do you mind sharing what brand battery you purchased?
Sent from my LG-P999 using XDA App
Wow, I told the CostCo kiosk girl I was having lock up problems and I had my grandkids with me. She took my phone and pulled the battery - at the same time my grandson stated he had to go to the bathroom NOW. She either looked at the battery or something on the phone under the battery. I didn't have time to ask. She didn't really comment and gave me my phone back.
Hmmmmmm........
-Bob
ok so do they know what exactly is causing the shut downs or reboot on this phone? i just got mine today and it was pre installed with gingerbread and idk if there is root for the gingerbread build yet. i just want root but no custom rom for me. i love the stock rom. it kicked the crap out of my sensation 4g as far as speed goes in everyday use.

Phone acting stooopid.

Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D
AgentCherryColla said:
Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D
Click to expand...
Click to collapse
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2
wiswis said:
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
I have no clue where my other battery is at XO
I keep on getting status 0 in recovery with any rom. But when that isn't happening, the rom will hang on flashing. Like Bulletproof 1.1, it will hang at Apply Kevlar ...please be patient.
Fixed it, flashed a backup :3 Any clue why it did this? I had to format the phone like a million times Xo
::Sense 4.0::
????? That's weird ???????
Sent from my myTouch_4G_Slide using Tapatalk 2
Ok, so my phone was acting dumb. I was finally able to get it to boot, but knock on wood *knocks on wall*. I had to flash to stock (Still S-Off). Now I'm booted and running fine. I have no idea why. :T Puzzles me, also I'm tired as hell. So this might be very random.
I couldn't get my phone to stay on for more than 10 minutes. Sometimes it just wouldn't. Boot. I was not able to get Roms to flash (status 0).
So I (re)flashed CWM 5.5, and that seemed to help. Then I was only able to use backups.
Then I just couldn't get my phone to work :T
So I flash the update in the Hboot to get back to stock.
1st it booted fine. But I rebooted to Hboot, and got funky issues (would not boot past bootanimation)
Flash Hboot update twice.
Then I did two factory resets in Hboot.
Then I got my phone working. I've been slowly typing this over 1 1/2 30 Rock episodes. No reboots :T Should I unlock and get CWM on here? I feel like my issue was not being on a stock kernel. Plus on stock I'm getting crazy battery life.
I'll see how my night charge goes. Hopefully she stays booted :d
Sent from my myTouch_4G_Slide using xda app-developers app
Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.
Blue6IX said:
Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.
Click to expand...
Click to collapse
I just got a replacement phone about a month and half ago. The only Rom it stays stable with is the stock Rom. That makes a lot of sense tho', I was thinking my phone couldn't handle a UV. My phones running perfectly (and faster, and smoother than ever). I'm going to try unlocking it again, and reflashing the recovery. See how far that takes me.
Ok, so I unlocked my bootloader (No recovery). It was having trouble booting. Wouldn't boot with the USB plugged in. But I'm still 100% stock (S-Off, Unlocked). I'm going to run stock for 2 hours, and see if I get reboots.
So my phone acts up on custom kernels, that's what I'm seeing.
So my phone starts acting up when the battery is below 15%, and not running a stock kernel. :T

[Q] Unpleasantness... Bricked phone?

So, while I'm no expert I'm not new to rooting and flashing. Did it quite a bit on my older Droid Inc 1, and have performed a few on my new SG3.
I have 3 backed up ROMs on my SD, Synergy, Beans and CM10. I was running Synergy and decided to give CM10 another shot to see if I could figure out what was killing NFC. So, flashed it up with ROM Manager (Used Odin previously) and everything went swimmingly. ROM was running, NFC was working, all my apps were reinstalled, no problems.....
Decided to see if I could get Wallet working on this install, so flashed it in, made the changes to build.prop and rebooted.
Heeerreeee's where the trouble started. Part way through the reboot the phone just shut down. Completely. 100%. Dead.
I had 87% battery when I started so it 'shouldn't be a battery problem. No power, no LED when I plug in the charger, no vol-up, home, power to get into recovery.
One interesting thing did happen while I was trying to get the phone up, I removed the battery for a bit, and plugged the USB cable in and got a red charging light. Put the battery back in, light still there. 1 minute later, light goes off and still nothing happening with the phone at all.
Anyone have any ideas beyond all the stuff I've given a shot to?
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Unfortunately not. Only thing that seems to show up is in the device manager, a QHSUSB_DLOAD device that's banged.
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Well, I called Verizon and they've shipped me a replacement. I guess throwing all my bit and pieces into a new main body should work fine...
Oh no. Another one sending a phone back because of rooting. That's why they lock bootloaders.
Sent from my Galaxy Nexus using xda app-developers app
+1
Have you tried borrowing someone's battery to see if you can also least boot? I have four samsung batteries for the S3 and would consider sending it to you before getting a replacement. I think the cost of a battery is $3 on Amazon.
Sent from my SCH-I535 using xda premium
The reasons were different but i had the same thing happen to me, my phone wouldn't boot, wouldn't show up in the computer. Nothing, i tried my wife's battery, no change there either. I left it on the charger overnight and tried turning it on in the morning and after messing with it it came back on. Haven't had an issue since. Don't know what caused it, the phone just freaked out, turned off and wouldn't turn back on.
You can also try the resistor trick to see if that will bring your phone back. Here is a cheap way to do it.
http://hackaday.com/2012/09/03/saving-a-bricked-phone-with-a-pencil-lead/ Otherwise you can go to radio shack and pick up a resistor.
If Verizon sends you your phone back cause you messed with it, there is a brick repair service for like $60 bucks PM for the link if it comes to that.
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
hehe.. I can't say I was pleased with having to go that route, (can't stand being defeated by electronics) but all in all I can't imagine a simple software change causing the entire unit to just go dead. Not booting properly, or locking up and such, sure... but not just dead.
By this morning I had tried another battery (a friend has an SG3 also) to no effect, but I didn't try leaving it plugged in overnight. I did check the battery with an external charger I have and it was showing fully charged....
So, I'll get a replacement and stay away from CM10 at the very least.
**ihavenewnike - Not sure why you're on an android developers forum really...
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it.
Ahhhh... It's just like it never left. :victory:
keno1964 said:
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it. . .
Click to expand...
Click to collapse
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
ooofest said:
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
Click to expand...
Click to collapse
Don't like you.......
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
tekrhino said:
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
Click to expand...
Click to collapse
I have looked into those and will most likely make one very soon. (I think I have everything I'd need, just may need to cobble some resistors together).
Couple of things I noticed throughout this 'process', regarding the CM10 (9-15 nightly) ROM, NFC and google wallet....
At first install of CM10 I noticed that NFC was active and working normally. It could read my tags without issue. After Wallet was installed though, NFC disappeared. It wasn't just disabled, it simply wasn't there any more. It was after noticing this that I decided to reboot, at which point my original problem started.
The reboot never came close to completing though, it shut down before it actually made it to the 'boot' phase, as in, while it was shutting down.
The actual cause of the power off is still a mystery to me, as I can't see a simple app change causing hardware failure.
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
AB_ said:
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
Click to expand...
Click to collapse
I told them what happened, just left out a few bits of info.
"I rebooted it, and it never came back on." and that was that.
Nice.
I should have gone that method, but ended up paying for the repair service from MobileTechVideos
A friend has the qhsusb-dload showing up as well.. phone won't turn on.. flashed a bad kernel or rom I forget which.. red light comes on.. that's it.. its a Verizon i535 .. tried the resistor jig and nothing happens.. any ideas to fix?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Guess he had aokp rom then flashed neak kernel and that's when it died..

[Q] What the heck happened?

So I was listening to Pandora and texting when suddenly my phone turned off the screen. It was still playing music so I tried to hit the lock button so it would unlock but it wouldn't I tried it a couple times and still nothing. I then waited and while and nothing..Then I took off the battery and it was still playing music as if it still had the battery...for like 15 seconds. Then it tried turning on over and over without the battery on. Now it wont turn on at all. I've tried connecting it to charger, taking out battery, nothing. What happened?
So no recovery mode no DL mode no response from the phone at all now correct?
Sent from my SGH-I727 using Tapatalk 2
The_Blue_Waffle said:
So no recovery mode no DL mode no response from the phone at all now correct?
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I haven't tried either of those. If I connect it to the charger sometimes it will show the Samsung Boot Logo but then it won't move from there. I'll try recovery mode.
EDIT: Recovery Mode works
Was the phone hot at all when this happened
Sent from my SGH-I727 using Tapatalk 2
The_Blue_Waffle said:
Was the phone hot at all when this happened
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
No it was not. Normal Temperature.
Try to force it into recovery or download first. Had you flashed a new ROM (doesn't matter which one) recently?
Almost sounds like just a freak thing man if you can get her into DL or recovery I would consider stock for a few days in case it was hw failure just to monitor it otherwise restore a backup or flash something and drive on
Sent from my SGH-I727 using Tapatalk 2
The ROM I'm running right now is CyanogenMod the latest stable one. And is there anything else I could do instead of restoring? Because I'm going to lose a ton of stuff..
Well you can hope it will reboot . But that seems unlikely
Sent from my SGH-I727 using Tapatalk 2
If you flash a new rom you won't lose your data. You'll only lose apps and settings and stuff. Which you can backup with recovery (unless you meant download) if you can't get to recovery there's not much you can do for your settings. But reflashing won't touch any pictures or anything on the internal sd card.
Rehab4Life said:
So I was listening to Pandora and texting when suddenly my phone turned off the screen. It was still playing music so I tried to hit the lock button so it would unlock but it wouldn't I tried it a couple times and still nothing. I then waited and while and nothing..Then I took off the battery and it was still playing music as if it still had the battery...for like 15 seconds. Then it tried turning on over and over without the battery on. Now it wont turn on at all. I've tried connecting it to charger, taking out battery, nothing. What happened?
Click to expand...
Click to collapse
I'm not sure exactly what happened, perhaps a hard ware fault, but I am starting to believe there is more to this. I have seen the same thing happening quite frequently lately, and each device yes even my wife's iphone 4 did the same thing while she was listening to Pandora, as well as my niece with her Galaxy S II. Same as you experienced, she was listening to Pandora and was texting a friend, then the phone went dead.
So it is not localized to either iPhone or Android devices from the information I have been gathering. When I took my wife's iPhone to the apple store here in Anchorage, the rep I was dealing with informed me that they have had several in the last week that had the same issue, while doing the same thing as your device did. Of course all he could say was if it is under warranty they will give my wife a new one. So she did, just like many others.
I also spoke with Daniel @ Pandora and informed him of the same issue that was with my wife & nieces iPhones, as well as android devices. His reply was that Our app is not 100% designed for use with the latest iOS release, and not for android devices running Jelly Bean. We have had several complaints about this happening to both types of devices, you have to remove the battery and reboot the system. I asked him how to do that with an iPhone, and he informed me to "remove the back panel and the battery will pop out." After I laughed at him I reminded him that it is not possible for the AVERAGE user to remove the iPhone battery, but it is quite easily done on most Android devices.
Once I was able to get him to realize that the iPhone battery does not come out, he "remembered" that and informed me to uninstall the Pandora app, clear caches and reinstall the app. I then asked him how to do that since the screen would not come on? His reply was "well it looks like your phone is dead, you might want to go get a new iPhone. I informed him that I had already done so with my wife's iPhone but was working off of my nieces S II now. Ok, back through the script we go. Battery out, yadda yadda. Informed me that Pandora does not offer support for rooted devices or devices on UN OFFICIAL ROM'S, and JAILBROKEN iPhones.
I informed him I was working off of a bone stock Samsung Galaxy S II and that while my niece was listening to Pandora and sent a text message that is when the device was rendered useless. The S II was still dead screened at the time, and I had left the phone plugged into the wall charger for over 24 hours, so the battery should not be dead. Continued through the script with him, and finally I asked him, "Ok why is it that 2 different devices, running 2 different operating systems running the same Pandora app would both be rendered useless from listening to Pandora & sending a text?" His reply was We do not offer support for rooted devices.
Now I am not 100% blaming Pandora nor am I saying that their app is 100% at fault, but it is apparently an issue with the app itself possibly using too much system resources, and when another app wants some of those resources the Pandora app causes a force close that is not easily recovered from.
If your Skyrocket is still under warranty, or you bought extended warranty, I would highly recommend as above to return the phone to bone stock if at all possible, get all you need off of it that you do not want to lose, and run Pandora again, and see if it does the same thing, if so then return the device.
Interesting, so Pandora's app is not compatible with JB or iOS6. I'll have to take it off both my phones; TuneIn and iHeartRadio are better anyway lol
Interesting. I was listening to Pandora and running GPS. Mine froze up for a very long time, then rebooted itself.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Custom ROM flash failures
Hello,
I have Flashed ROMS with CWM recovery before with success, but recently have been getting failures. I can however, Flash with Odin still. The log I get with CWM REcovery is attached.
Search "adb" for backing up your current info before flashing anything.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Interesting. I was listening to Pandora and running GPS. Mine froze up for a very long time, then rebooted itself.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
That is what I was informed, but with hundreds of thousands of devices running JB I don't fully understand the issue there. It's good that your's rebooted itself. My nieces never rebooted, neither did my wife's. Again I am not sure of the issue, and would love to have a log of some one running it on their device, so that I could further investigate.
MasterDecker said:
That is what I was informed, but with hundreds of thousands of devices running JB I don't fully understand the issue there. It's good that your's rebooted itself. My nieces never rebooted, neither did my wife's. Again I am not sure of the issue, and would love to have a log of some one running it on their device, so that I could further investigate.
Click to expand...
Click to collapse
Well, I removed Pandora after that. I won't be using it anymore. Sorry man
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Well, I removed Pandora after that. I won't be using it anymore. Sorry man
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
No worries, but now I get to go and buy my wife a NEW iphone 5. Again she was listening to Pandora, and received a text message (this was on her 4S). screen went out, sounds stopped, and the life of her 4S was extinguished. I think it was on purpose, so that she could get the i5. But never the less I was actually there this time when it happened.
POOF, dead. *sigh* now if only ALL iphones would do this I would be happy.
MasterDecker said:
No worries, but now I get to go and buy my wife a NEW iphone 5. Again she was listening to Pandora, and received a text message (this was on her 4S). screen went out, sounds stopped, and the life of her 4S was extinguished. I think it was on purpose, so that she could get the i5. But never the less I was actually there this time when it happened.
POOF, dead. *sigh* now if only ALL iphones would do this I would be happy.
Click to expand...
Click to collapse
Damn. I think she did it on purpose too. I would've immediately uninstalled Pandora if I was her. She killed it on purpose!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Nope my boss gave her an i phone 4s. Which she in turn took took to at&t and traded it in for a note 2.
Sent from my Transformer TF101 using xda app-developers app

[Q] Hard bricked never rooted.

Hello everyone,
My S3 decided to die I guess lol. I always rooted my previous phones and knew the risks but never would I have thought it would brick being stock!!! From now on every thing gets rooted....
Back in February while I was on a trip it was on and then died. All the symptoms of a hard brick but 4 days later it finally turned on..... since then I have been using it but it always suffered form random freezing, flickering screen, camera static from flash, always dies when it gets to around 30% or lower.....
The other day I put it on the charger and came back to a black screen with a blue led... mind you I was just using it browsing the web.... Recovery mode kept shutting off....
Then nothing from the phone.
Got into download mode said "Downloading"...... pulled the battery and poof... instant paperweight lol
Were you Odining stock? Did you pull the battery while flashing stock? Just making sure since you said u got into download mode
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Were you Odining stock? Did you pull the battery while flashing stock? Just making sure since you said u got into download mode
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It wont go into download mode now... No I was just trying to turn it back on.... never really wanted to mess with it since it was Verizon and a Samsung phone at that.... HTCs seemed soo much simpler lol.
On a pc it is qhsusb_dload... I'm assuming my insane emmc chip had sudden death and
I added to bricking it?
Blackman778g said:
It wont go into download mode now... No I was just trying to turn it back on.... never really wanted to mess with it since it was Verizon and a Samsung phone at that.... HTCs seemed soo much simpler lol.
On a pc it is qhsusb_dload... I'm assuming my insane emmc chip had sudden death and
I added to bricking it?
Click to expand...
Click to collapse
Well considered it's never been rooted it's obviously a hardware issue. Get a replacement.
Sent from my SCH-I535 using Tapatalk

Categories

Resources