[Q] Hard bricked never rooted. - Verizon Samsung Galaxy S III

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

Related

possible bricked verizon samsung galaxy s3

phone was all working fine until i guess attempted to install wrong version of CM10 said installed thru CWM did i said reboot then phone screen went black and now wont power on no Samsung logo or nothing just black but when i plug in to pc i hear the sound like looking for drivers for a device plugged in. anyone have them happen and if so any fix? before i do a insurance claim...
Jacob2kD said:
phone was all working fine until i guess attempted to install wrong version of CM10 said installed thru CWM did i said reboot then phone screen went black and now wont power on no Samsung logo or nothing just black but when i plug in to pc i hear the sound like looking for drivers for a device plugged in. anyone have them happen and if so any fix? before i do a insurance claim...
Click to expand...
Click to collapse
Guessing it's more of a soft brick and recoverable. Where did you get CM10 and what version of cwm? Unlocked bootloader?
Jacob2kD said:
phone was all working fine until i guess attempted to install wrong version of CM10 said installed thru CWM did i said reboot then phone screen went black and now wont power on no Samsung logo or nothing just black but when i plug in to pc i hear the sound like looking for drivers for a device plugged in. anyone have them happen and if so any fix? before i do a insurance claim...
Click to expand...
Click to collapse
You'll probably have to go into download mode, and odin back to stock.
Yeah it's probably a soft brick, if you can get into odin (power + home + vol UP) you should be good to flash back a stock w/root and be back up and running.
I just did this when I had to flash back from a bad download of the synergy nightly....or possibly it's a problem with the nightly, a good lesson to actually check the md5 on a download...
how will i know when in download mode if screen is black..it was CM10 that showed up on rom manager at one point CM10 konstakang JELLYO
If you pit it no dl mode while Odin is open and phone plugged in ...it should show up in the "com port area of Odin. I think even if you can't see it on the screen. It worked with my Charge. Give it a shot
Sent from my SCH-I535 using Tapatalk 2
Mike you have any ideas for me to try?
I've had similar issue in the past if you have sound when plugged in its probably just a display issue you will have to try to put it into download mode blind and flash stock unfortunately will have to set up from scratch but should do the trick
Sent from my SCH-I535 using Tapatalk 2
Power + home + volume up to get into download mode. It should show something on the screen if not try what was said above and put it in d/l mode with Odin opened and the phone plugged in.
I don't want to start some heated debated but I don't see the difference in "self bricked" and "self dropped into a toilet" when it comes to insurance. Now warranty that's a different story.
I have to disagree and agree with the guy who says these people are xxxxbags. I wouldn't go so far as to call people who want a working phone as a "xxxxbag" a bit irresponsible yes, but to go so far as calling them xxxxbags I think is a bit harsh.
On the other side of the argument are the people who act as if Verizon or Samsung are obligated to replace a bricked phone. You don't throw your phone around like a football then expect it to be replaced for free. People who flash custom roms, etc (including myself) are fully aware of the risks they are taking by doing so and should take the responsibility to try and fix it themselves. If they can't figure out how to fix it with the help of all the brilliant minds on XDA, Verizon won't have too much luck either.
mikeew83 said:
I've had similar issue in the past if you have sound when plugged in its probably just a display issue you will have to try to put it into download mode blind and flash stock unfortunately will have to set up from scratch but should do the trick
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thats kinda weird if its just the display when all was working just fine then went blank after CWM said install successful until i did a reboot :X.. i don't expect a "free" replacement" insurance isn't free anyways $99 deductible
mikeew83 said:
**** you god tell some one there scum bag for wanting a working device get your holier than thou **** ass self out of here people like you are why xda loses member base
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You're an idiot. You break your phone YOU take the responsibility for fixing it.
---------- Post added at 07:26 PM ---------- Previous post was at 07:22 PM ----------
UOTE=JBO1018;30370951]Power + home + volume up to get into download mode. It should show something on the screen if not try what was said above and put it in d/l mode with Odin opened and the phone plugged in.
I don't want to start some heated debated but I don't see the difference in "self bricked" and "self dropped into a toilet" when it comes to insurance. Now warranty that's a different story.[/QUOTE]
.
It's home+voldwn+power then vol up to continue.
And one is and accident and one is self inflicted. If you don't see the difference I can't help you:victory:
Nothing but a flame war here
It is against XDA rules to discuss ways to fraud the carrier into warranty replacement
You brick it, you bought it. That is what insurance is for.
Admit you messed up your phone and pay the deductible
Thread closed
Thank you for your cooperation
NFNM

[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..

Phone stuck after dead battery.

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

[Q] Bricked? And why?

So I am running cleanrom 5.5.1, unlocked bootloader and original first leak radios. I was texting and all the sudden bam. rebooted to a black screen. Can't access download mode or recovery. The Samsung logo pops up followed by the s3 logo, then a dimly lit black screen that never ceases till battery pull. When I try download mode, some blue text pops up in the upper left hand corner, then reboots to logo screens then back to black screen. Also, when I pull battery and put it back in, plug in a charger and the battery icon appers on screen. When it goes dark I can wake it with the menu button and see the battery icon again. Any suggestions? If not fixable, would I be able to get a replacement from verizon? (I bought the phone less than a month ago renewed contract. Any help is much appreciated!
If the blue text is popping up your trying recovery, not download mode. Pull battery put it back in then hold volume down , home, and power until the download mode warning shows up
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If the blue text is popping up your trying recovery, not download mode. Pull battery put it back in then hold volume down , home, and power until the download mode warning shows up
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
i too just ran into the black screen after flashing an aosp kernel running slim 3.1 and im trying this way of getting into recovery and i hold down volume home and power and it still boots normally. i think i soft bricked my phone because i see the samsung logo but i never get to a bootlogo and only the hardkeys light up. im losing my damn mind and dont know what to do! i know its fixable cause i can see the samsung logo but i dont know what to do because the three finger salute wont work to get into recovery and i know that my bootloader is unlocked. not trying to thread jack just figured itd be pointless to post a new thread when the op is having virtually the same problem -___- lol go figure the first day i have my s3 i do this ****.. good thing i still have my nexus til i get it fixed.
Deltadood24 said:
i too just ran into the black screen after flashing an aosp kernel running slim 3.1 and im trying this way of getting into recovery and i hold down volume home and power and it still boots normally. i think i soft bricked my phone because i see the samsung logo but i never get to a bootlogo and only the hardkeys light up. im losing my damn mind and dont know what to do! i know its fixable cause i can see the samsung logo but i dont know what to do because the three finger salute wont work to get into recovery and i know that my bootloader is unlocked. not trying to thread jack just figured itd be pointless to post a new thread when the op is having virtually the same problem -___- lol go figure the first day i have my s3 i do this ****.. good thing i still have my nexus til i get it fixed.
Click to expand...
Click to collapse
Well you're right. Since you get life it's fixable. I would say pull your battery for a little while. Put it back in then hold volume down, home and while holding them both hold power. Your phone should boot into Odin mode.
Back stock for now....YUCK!
I had exactly what your describing
jndd333 said:
So I am running cleanrom 5.5.1, unlocked bootloader and original first leak radios. I was texting and all the sudden bam. rebooted to a black screen. Can't access download mode or recovery. The Samsung logo pops up followed by the s3 logo, then a dimly lit black screen that never ceases till battery pull. When I try download mode, some blue text pops up in the upper left hand corner, then reboots to logo screens then back to black screen. Also, when I pull battery and put it back in, plug in a charger and the battery icon appers on screen. When it goes dark I can wake it with the menu button and see the battery icon again. Any suggestions? If not fixable, would I be able to get a replacement from verizon? (I bought the phone less than a month ago renewed contract. Any help is much appreciated!
Click to expand...
Click to collapse
I had just rooted and flashed Jellywiz the previous day. The next day at work, I don't know why, but I must have experienced some kind of massive battery drain. The phone would not reboot, I would plug it in and it would just vibrate and flash the battery sign on the display every few moments. I had to put the phone on a charger for about 15 minutes and let the battery charge until I was even able to get the phone to boot. I would not boot while plugged into an AC charger until I let it charge. Very weird, and it hasn't happened again since but I swore that my phone was bricked. Basically the battery was so dead it wouldn't boot the phone, let it charge with out ****ing with it for a while and then try and boot it up.
kintwofan said:
Well you're right. Since you get life it's fixable. I would say pull your battery for a little while. Put it back in then hold volume down, home and while holding them both hold power. Your phone should boot into Odin mode.
Back stock for now....YUCK!
Click to expand...
Click to collapse
I don't know how to use Odin I did the non odin way to root lol I can get into download mode tho so apparently its fixable thank god. I feel like a noob right now I didn't ever do anything like this on my nexus or tbolt and then the first day I do it on my s3 -___- guess I gotta read up on Odin
Sent from my Galaxy Nexus using Tapatalk 2
Deltadood24 said:
I don't know how to use Odin I did the non odin way to root lol I can get into download mode tho so apparently its fixable thank god. I feel like a noob right now I didn't ever do anything like this on my nexus or tbolt and then the first day I do it on my s3 -___- guess I gotta read up on Odin
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Odin is easier then it seems, but make sure you know what you're doing because you can brick your phone with it. However, there is a great guide right here on how to unbrick your phone. Just follow section 5, I did it last night(to just clean up my phone)
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Odin is easier then it seems, but make sure you know what you're doing because you can brick your phone with it. However, there is a great guide right here on how to unbrick your phone. Just follow section 5, I did it last night(to just clean up my phone)
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So do I need to do all the steps in section 5 including flashing the radios if I never messed with them prior to rooting?
Sent from my Galaxy Nexus using Tapatalk 2
Deltadood24 said:
So do I need to do all the steps in section 5 including flashing the radios if I never messed with them prior to rooting?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You may want to double check section 5 it's one file that includes the entire stock ROM including a locked boot loader and the radios that match.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
You may want to double check section 5 it's one file that includes the entire stock ROM including a locked boot loader and the radios that match.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh okay thank you man! Sorry to thread jack op! I'll check it out
Sent from my Galaxy Nexus using Tapatalk 2
thanks guys
The first several times nothing would work not even download mode, my recovery console was gone too. after several tries download mode popped up so I immediately hooked up to odin and reflashed a stock root. all good now. Still wonder why it borked itself in the first place. Seems to be a mystery but I'm not too keen on flashing cleanrom 5.5.1 again...
jndd333 said:
The first several times nothing would work not even download mode, my recovery console was gone too. after several tries download mode popped up so I immediately hooked up to odin and reflashed a stock root. all good now. Still wonder why it borked itself in the first place. Seems to be a mystery but I'm not too keen on flashing cleanrom 5.5.1 again...
Click to expand...
Click to collapse
i couldnt get odin to work on my computer for some reason and after searching through google i found a forum on getting into the stock recovery and figured id try it and my phone decided to cooperate and go back to clockworkmod after all that and now my phone is fixed lol technology..
No worries about jacking thread I'm glad my post lead others to help another with not the same but similar issues. I've been out of the dev circle since g1 days but I think its time to play around and execute some system dumps after a bit of tweaking. definitely like Odin! All in one multi partition flaher! Fashing via adb used to be too cumbersome with the early sdk's!
Sent from my SCH-I535 using xda app-developers app
Yeah I got a lot to learn about programs its crazy how much stuff there is to know and things constantly get added every day lol the android community is very interesting that's for sure
Sent from my SCH-I535 using Tapatalk 2

Vibrate Stopped Working?!

Title says it all. my vibrate no longer works for any part of my phone. any and all help is appreciated.
thanks
p2kmafia said:
Title says it all. my vibrate no longer works for any part of my phone. any and all help is appreciated.
thanks
Click to expand...
Click to collapse
It's possibly the vibrate motor. It's not unheard of for them to go out.
Sent from my ADR6425LVW using Tapatalk 2
+1. Hardware issue.
Still Charged Up
sounds like a personal problem - wore out your vibrator... j/k
never heard of that though - have you tried reflashing the ROM or resetting your sound settings?
tried everything but refreshing back from ep4. I was really hoping it wasn't hardware. wtf do I do now? haha
If you rule everything else out and it is the motor, it can be replaced if you don't mind a little disassembly. It's typically one of the easier repairs to do. In most phone, it's just a little round, flat cylinder, about the size of a small watch or hearing aid battery, clipped to the motherboard and connected by two wires.
how much would that cost and where do I buy the motor?
I'm pretty sure the motor is actually integrated (as in soldered) onto the board. Assuming you can actually find the motor, it's going to be a PITA desoldering and soldering that sucker. Why not just get your Charge replaced?
Sent from my SCH-I510 using xda premium
p2kmafia said:
Title says it all. my vibrate no longer works for any part of my phone. any and all help is appreciated.
thanks
Click to expand...
Click to collapse
What I have done. (I also have insurance)
ODIN with PIT
In the middle of re-partitioning with the PIT pull the plug and disconnect all battery sources.
When you turn it back on It will say to connect to the computer and download mode will not
work... Take it to the store and tell them that the vibrate alert stopped working. You checked
to see if there was an update and there was. Take the update and then this showed up. Works
every time for me >.< Any time I frail up my phone I incorrectly PIT it and make an excuse to
get another one bahaha
je2854 said:
What I have done. (I also have insurance)
ODIN with PIT
In the middle of re-partitioning with the PIT pull the plug and disconnect all battery sources.
When you turn it back on It will say to connect to the computer and download mode will not
work... Take it to the store and tell them that the vibrate alert stopped working. You checked
to see if there was an update and there was. Take the update and then this showed up. Works
every time for me >.< Any time I frail up my phone I incorrectly PIT it and make an excuse to
get another one bahaha
Click to expand...
Click to collapse
THIS IS WHY WE CANT HAVE NICE THINGS.
But yeah, that'll work, but make up some other excuse than taking the update, FP5 is too mature for this to work, but then again a VZW employee likely wouldn't know on a phone this old.
Sent from my SCH-I510 using xda premium
Bad mojo..
Sent from my SCH-I510 using Xparent Red Tapatalk 2
someone said swap doing it... i think it's the guy above me
.... lol
Sent from my SCH-I510 using xda premium
lukegman said:
someone said swap doing it... i think it's the guy above me
.... lol
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I use swap and my vibrate works just fine.
Sent from my AOSPA N7 controlled by Metallice's a32 Kernel.
I've had my charge since the day after it came out haha waiting on the s4 to upgrade I don't think they'll give me any more charges (I'm on #4). But not having vibrate sucks. I did hear that swap was doing this to some people and I have swap activated, I'm going to try that out for size, will report back
so i don't think replacing my charge is a possibility (unless I pull the this phone is f#@$!ng terrible card) which I'm not in the mood to do. Also, disabling swap did not help wiped dalvik also just in case that could affect anything. I was scared my phone stopped accepting charge and was about to re-partition my phone last night but it was 4am and my phone decided to work again so that's probably the last thing I can do and I'll do it when I've got some free time this weekend and report back for anyone having this same issue.
on a semi-related note what are you guys planning on upgrading to? I want to wait for the moto x but would rather get the S4 because I like what samsung has been doing with extra features in their version of android, but also the HTC M7 looks super appealing and its not mumbo jumbo like the s4
p2kmafia said:
so i don't think replacing my charge is a possibility (unless I pull the this phone is f#@$!ng terrible card) which I'm not in the mood to do. Also, disabling swap did not help wiped dalvik also just in case that could affect anything. I was scared my phone stopped accepting charge and was about to re-partition my phone last night but it was 4am and my phone decided to work again so that's probably the last thing I can do and I'll do it when I've got some free time this weekend and report back for anyone having this same issue.
on a semi-related note what are you guys planning on upgrading to? I want to wait for the moto x but would rather get the S4 because I like what samsung has been doing with extra features in their version of android, but also the HTC M7 looks super appealing and its not mumbo jumbo like the s4
Click to expand...
Click to collapse
I'm holding out for another Verizon Nexus to come around.
p2kmafia said:
so i don't think replacing my charge is a possibility (unless I pull the this phone is f#@$!ng terrible card) which I'm not in the mood to do. Also, disabling swap did not help wiped dalvik also just in case that could affect anything. I was scared my phone stopped accepting charge and was about to re-partition my phone last night but it was 4am and my phone decided to work again so that's probably the last thing I can do and I'll do it when I've got some free time this weekend and report back for anyone having this same issue.
on a semi-related note what are you guys planning on upgrading to? I want to wait for the moto x but would rather get the S4 because I like what samsung has been doing with extra features in their version of android, but also the HTC M7 looks super appealing and its not mumbo jumbo like the s4
Click to expand...
Click to collapse
I went with the ThunderBolt. HUGE ROMS but still one of the best LTE phones out ( as in being like a tank and being sturdy)

Categories

Resources