long story short my wizard fell in the toilet last Jan of 08.. miraculously ,it worked till now, when a few weeks ago failed to flash a new rom. now its stuck on bootloader. my wizard cannot stay on without being plugged into the wall this is a fairly new concept to me because it just started doing that lol
if the battery is taken off the phone the screen messes up (white screen with flashing bars going diagonally) of course i would find out i had to leave the phone on for a week being charged so the screen would go back to normal on its own, so i never take the battery out.
It doesn't charge via wall charger it needs the cradle which i brought separately...another defect on the phone is how the red led light which indicates i guess being charged, is ALWAYS lit..
so i went on to flash the NBDX Rom successfully maybe a month prior to the accident. it went on to satisfied me till i decided to try something new, by flashing the SimOne MD2 rom (so tempting)
so now that the flashing was unsuccessful i am stuck on bootloader because since my phone cant stand being on without being charged it will turn off after a minute, so it will NEVER go on to finish ....
well anyway, that's my story. i just thought you would know (was bored) lol maybe its time for a new phone anyway ..Well, thanks for reading my article..
It sounds like a hardware, not software, issue. I think the timing was just a coincidence. Perhaps a new battery would help. Also, try charging with an external charger. Sorry about your loss.
Related
At The Beginning
I have a Cingular 8125 G3. I first began flashing new roms onto my phone 4 months ago after I unlocked it using "the definitive guide to unlocking phone" by DrDot. Everything went smoothly.
The Start of the Problem
A couple days ago, I was running the TNT 1933 with CoolCamera. SUDDENLY, my phone started to reset itself everytime I went on the internet, or downloaded emails.
The Attempted Fix
I decided to flash my phone to another rom, so I began by flashing it back to 1.05 rom that you use in "the definitive guide to unlocking phone" by DrDot, before flashing it to a better rom.
The Final Finally
In the middle of the udate process (for the 1.05 rom), my computer screen said, an error occured, and to redo the update. When I looked at my phone, it started to blink on the 3 color bars. It kept blinking until it died. Now it cannot read a charge or turn on. I tried leaving it on my charger overnight, hoping it would charge, and nothing (not even the charge light on the phone would go on. I also made sure the phone charger was fine, which it is. I even tried to charge it on the usb cable, and occassionally I see the 3 color bars flash). My phone is bricked.
buy a new battery and then flash a new rom
It is not bricked
I will try that
spencepu3 said:
buy a new battery and then flash a new rom
Click to expand...
Click to collapse
Okay, I'll try that. I'll let you know tonight.
keep in mind that when you are in bootloader mode (tri-color screen) the phone cannot be charged, this is why you should always have a 50% battery level when you flash a rom. A new battery should definately fix it, id flash it with a manufacturers rom that is known to work like the wizard love or t mobile 2.26
Everything is good thanks
I put a new battery in there and it is fine now. Thanks. How can I delete this thread? It is pointless now.
bringing the emty battery UP again with home tools
Please note that the following is highly experimental and if you consider to use the following "workaround" it is TOTALLY AT YOUR OWN RISK and i can not be held responsible for damages caused to your hardware or to yourself!!!!!
I had the same issue 2 times till now, what i made:
i took a USB cable (like the normal one i use for the wizard to connect it to the pc), cut off the mini usb jack. There are 4 wires in the cable we need the black one and the red one. The red goes to the + of the battery and the black goes to the - of the battery (on my battery the + and the - are marked), if on some batteries there are no marks for + and - you can use multi zet tool to check. The next thing is to put the cable in a free usb on the pc and the wires on the battery. Its quite difficult to find out the right place and position for charging the battery this way - but you actually need to charge it this way not more than 5-10 mins. Then you can boot normally and continue charging the "right" way. Use your old battery again. Thats all...
Regards
I really don't know if this is possible or not.... but I might need to get some new corduroys after a case of the brown adrenalin with my new sensation.
Got it Friday as could see progress on the rooting and sure enough Revolution came up with the goods same day. Rooted it Saturday.
Fully charged it, switched it off and went back to the HD2 - flip case and car kit arriving today. Really don't wanna damage my new boy toy by pocketing it with car keys etc.
Stone me though I thought I bricked it. Wouldn't switch on this morning - just a dark flicker of the screen. Sweat pouring off my forehead. Never bricked a device and flashed my HD2 & TP2 a million times and my £450 unlocked handset is 3 days old and dead..
Long and the short of it is plugged in the charger again and a few minutes later it powers up - 3% battery.
Is it possible it could drain switched off? Or should I blame the kids for messing with it and deduct my dry cleaning bill from their pocket-money?
After I rooted, I had to do a battery pull until I was able to turn my phone on again, although this doesn't really replicate what problem you had...
The battery does not drain if the phone is turned off.
Question is, was it definitely turned off?
Even if it wasn't, there's no way a full charge is going to drain overnight... Unless you had a Satnav running...
Sent from my HTC Sensation Z710e using XDA Premium App
You're right - it SHOULDN'T... I'd rebooted no problems several times after the rooting. Some OTA update came over and didn't install successfully though.
It'd be very odd (and a warranty issue, get ready to go into rooting reverse) but for now I'm inclined to just blame the kids. Unless anyone else has has similar experiences.
I guess time with it will tell.
EDIT: Apparently it's a known issue and has been fixed with the new CWM update! See: http://forum.xda-developers.com/showthread.php?t=1192300
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
EDIT: Good man. Thanks for the update. Better get onto that right away.
Yup.. that's the same experience... except I'm still on stock rom with tweaks.
What do you reckon - flash back to stock and see if it still happens? Really don't want it turning into permanent paperweight with an iffy bootloader for someone at warranty to find with their JTAG.
Morsolo said:
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
Click to expand...
Click to collapse
Hello All!
Three days ago I updated my GS3 to JB 4.1.1. I also ODIN'd TWRP onto my phone as a recovery and loaded SuperSU with an unlocked bootloader onto my phone along with BusyBox. I fell in love with my phone again as JB ran smoothly and I was even able to use Wallet Installer to get Google Wallet onto my phone. However, tonight, my phone seemed to experience a case of Sudden Death Syndrome. A common issue found by googling why my phone's failure to respond to boot commands and power commands.
It will not respond to attempts to boot into ODIN mode, my TWRP recovery and the only sign of life on my phone is a solid red LCD that lights up only if I remove the battery and leave the device plugged into a wall charger. Once I try to reinsert the battery, however, the LCD goes away and the phone once again turns into a coffee coaster. It's taking a lot of strength not to throw it against the wall. (I picked the worst week to quit smoking.)
I don't believe I hardbricked the device because three hours ago at the time of this post, I went to sleep and the phone was working and I was able to send and receive messages. I believe that rooting my phone actually made it even more stable than normal. I just can't believe my phone could just suddenly die. Could it be another case of Sudden Death Syndrome? (Corrupted NAND?) I bought this phone in August and many cases of SDS for the GSIII seem to occur within 150-200 days of activation, which would put me in that window. If I answered my own questions, please feel free to tell me. I'm just trying to explore all options as an exasperated user dealing with what seems frustration after frustration and the one release I have from that stress just **** a brick.
I am covered by Asurion Insurance (and if the crack on my screen will not be enough I plan on running it over with my car for good measure to get my money's worth) but I really do not want to have to file an insurance claim unless it is absolutely necessary.
Phone died just last night 12/29/12. The battery was running down, then beeped once like a warning to charge it. Plugged into the charger and no light whatsoever! The battery icon would come on for a second and then nothing. Left it on the charger over night. Nothing. No red charging light, no boot. Pulled the battery and re-plugged into charger. Same charging icon on screen but nothing else. Tried every combination of removing battery, sim card, memory card, and plugging it in to the charger and still won't boot. Tried a different charger and also my laptop. Nothing. The S3 is a USA Verizon variant. 16gb. Black. I guess it's off to Verizon this morning to get a new phone. Phone is only 45 days old!!!
You could try leaving it on the charger for a couple hours then booting into recovery and reflashing your rom. I've seen a couple instances reported on xda where the battery simply just gave up below 23% and refused to turn back on.
Edit: example, not even a couple weeks old...
http://forum.xda-developers.com/showthread.php?t=2056539
Sent from my SCH-I535 using xda app-developers app
If it is a case of "sds" Samsung will replace the board for free.
Ryno77 said:
If it is a case of "sds" Samsung will replace the board for free.
Click to expand...
Click to collapse
Only reports of SDS in the 150-200 day time frame that I saw was with the International Version and it is completely different motherboard.
What do you kids do to your phone? How old are you? I'm going to start a survey. Age please?
Sent from my SCH-I535 using Tapatalk 2
Update: Brought the S3 into Verizon. They pulled the battery (Like I did a few times!) and somehow got it working again!! FM ! Phone reboots and turns off and then back on. BUT..... if you turn it completely OFF and plug it in to charge then the same as I mentioned happens again. STRANGE. The only way to get it to reboot is to pull the battery and keep it out for about 30 seconds. Put the battery back in and it'll reboot again!!!! Is it me or is this a strange quirk???? The previous times I pulled the battery it was out then back in. This time I took it out, waited 30 seconds and VOILA! It works. Thought you might like an update. Verizon S3 bought on 11/17/12. Rooted and not oc/uc'd. Using Clean Rom 5.5.1
h
prdog1 said:
Only reports of SDS in the 150-200 day time frame that I saw was with the International Version and it is completely different motherboard.
Click to expand...
Click to collapse
That's good news..thanks for the correction.
I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..
Qhastic said:
I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..
Click to expand...
Click to collapse
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.
1BadWolf said:
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Sorry, meant clockwork mod, not cyanogen. I haven't flashed any ROMs on this phone yet.
Do you think the battery issue arose as a result of rooting/installing clockwork mod?
No no..Many phones these days fail to charge when drained because they use software to detect the charger and then allow current to flow.. This is unlike the older nokia phones or current HTC phones.. what you can do is as suggested above.. use a 9V battery or something that ought to do it.
Okay so it may be a little redundant but I'm gonna start from the beginning I bought a pixel 2 about a year and 1-2 months ago on Amazon I immediately knew I needed root and a custom ROM so I put linage on it as it was at the time the only ROM being updated I then switched to 2 others pixel dust and it was great but was missing a few features so I tried another one I'm still on and terrified to turn my phone off I'm not blaming the ROM
I went to bed the other day charging my phone got up on 100 scrolled Facebook for maybe 10-15 and it was on 78 I figured maybe I was on it longer than I thought or maybe it was too bright idk but I thought ok I'll go out and take less than 5 and I'll be back to charge it but I never got a chance the screen went black and never came back on. I plugged it in for an hour and nothing. I tryed PC it didn't show up at all no device manager nothing so I took the screen off and unplugged the battery (hesitantly) as I didn't know if it would ever work again I then used my heat gun on it set at about 445 (I don't know if it's bad solder just trying something new) I then put it back together and when I did it was in qqm 9008 (hard bricked) so I unplugged the battery again and it reboot to recovery before rebooting to the os.
Now I'm scared on what to do as I don't want the device to die incase it won't turn on again cause I lost work and can't afford another but I need to know if there's anything I can do to ensure that it doesn't happen long enough for me to flash a new ROM incase it's the ROM so please anyone with this phone that can help me out even a little would be great