Ok so i am brand new to the xda forums and i joined because my friend said the people over here are very knowledgeable. I have a Galaxy SIII from verizon and i had it Rooted and i had cyanogen mod flashed on to it. I went to sleep woke up did a couple things then went to look at my phone. I tried turning it on i got nothing. I plugged it in and got nada. I then searched on the web to find out that it is hard bricked. I am only getting the battery notification LED when i plug in the phone without the battery inserted and sim inserted. Ive had this phone for a little bit but cant afford a new one so if you have knowledge on how to fix it please post. I have a p that can handle most anything so running programs and what not is easy if it comes to having to do things computer-side :crying:
Have you tried booting into recovery/download using the 3-button combos? Some people have found that leaving the phone on the charger for a while also makes it come back to life. If those don't work than you're most likely hard bricked. You can try the SD card de-brick method. Everything you need is in this youtube video (there are links to all the files you need in the video description):
http://www.youtube.com/watch?v=dU5H8NJ7vTM
Alternatively, you can send it to http://mobiletechvideos.mybigcommerce.com/ and they'll fix it all up and root/unlock bootloader/install any custom ROM and ship it back to you for $50.
I did try to boot into my twrp recover but it wouldnt work so i left it plugged into my pc while i played some garrys mod and then decided to put the battery in so i didnt lose anything. Out of instinct i hit the power button and it showed the battery charging boot logo. I nearly shat myself . but i remained calm turned it on and then it booted showed the cyanogenmod booter and loaded in with all my old files :good: My replies may be few and far between but i know its good to give and take in forums so ill check maybe once every 3 days and reply to anything i see by directing the messages at people personally
Related
I hate to post here, but I've searched everywhere and have not found a solution to my particular issue.
I rooted my new droid charge using this guide: http://forum.xda-developers.com/showthread.php?t=1122657
I flashed the debloated ee4 stock rom with PBJ with voodoo lagfix and it all worked fine. Today, I decided I wanted to try gummicharge and decide to flash it, I forgot to turn off voodoo before doing so, and the flash froze up before finishing. After a series of flashing/reflashing and turning voodoo, I eventually got to where the phone would only boot to CWM, and now will not turn on at all, or go to download mode (yes, I know how to do it).
I'm out of ideas, I feel like my phone might really be bricked for good. Please help! Thank you in advance for any advice.
Edit: the battery was low when I was flashing, but the phone was plugged in. I've read to leave the phone charging for a while and that might help, but I've charged it for 2 hours so far and nothing.
I know this doesn't help you at all but I am about to use that guide to root my droid charge. Did you like the pb ROM? I cant decide which to choose. I really dont want to do one and switch to another and screw up haha.
The pbj kernel was really solid, worked very well. I just wish I hadn't kept messing with things after they were how I wanted them =(
I know you say you know how to get to download mode. Have you tried the method where you poul the battery out then push the two volume keys and hold them while plugging in your usb cord(all while the battery is out)? Then I recommend flashing one of the full stock odins from p3droidin developement section in all roms.
I had tried this before, still nothing. I even read that sometimes Odin will detect a phone even without the screen coming on and decided to try, still nothing.
I forgot to mention. Have you tried pulling the sd card? Sometimes that helps. Pull it then try.
No SD, no SIM card, and no battery in it, still nothing.
I should add that the phone was getting hot to the touch, is it possible that the phone fried and this wasn't a result of a bad flash?
I'm no expert, but I was unable to enter CWM while plugged in. However, I was always able to enter download mode while plugged in (and battery removed). Try leaving the phone alone for a while? Heat definitely isn't helping things.
Well, I've got the insurance on the phone and I feel like the heat (not rooting) was my issue. I hate to give up, but I've tried everything I can think of.
wrarvoz said:
Well, I've got the insurance on the phone and I feel like the heat (not rooting) was my issue. I hate to give up, but I've tried everything I can think of.
Click to expand...
Click to collapse
Welp, that's why you paid for it. I would be crying in your situation because I never pay for insurance. You might as well; you can get rid of any tiny scratches or imperfections while you're at it!
Same thing happened to my charge today. Was charging and got pretty hot and shut off. Now when I charge it the 4 buttons flash and I can't get into do dl mode with or without battery. Gonna let it charge for a while and report back but I think its fried. Was running stock.
I'm scared that I may have lost one
I rooted with z4root, which seemed to go well. I downloaded rom manager (paid version) and flashed cwm. I had some trouble booting into cwm so i did a little investigating and ended up downloading bootstrapper as well. After enabling boot strapper I was able to get into CWM and do a nandroid backup.
I downloaded and flashed to newest CM nightly (8 I believe), and my phone seemed to be happy (it did want to power cycle when I was signing on to my google account at first, but after skipping the step in the set up wizard of the phone and just adding the account after it worked fine.).
I went to bed and did not plug the phone in. I woke up and saw that it was on still and proceeded to play a video game. I heard it beep across the room an hour later (no one around it) and figured it was getting low on battery since it had not been charged. When I picked it up to check the time, it would not start up. I have pulled the battery several times, tried to boot into cwm to flash my back up (could only get into the factory recovery), and I seem to be getting less and less response as time progresses. My power button doesn't seem to be producing any effect now and I can only get the screen to come up and display the big moto "m" if I plug the phone into a charging dock. I did charge my battery in my brothers OG droid since I heard that it wont charge the battery if it doesn't start up.
I'm by no means an expert, but I've had very successful rooting experiences with my Dinc (even soft bricked my Dinc, had a heart attack, then brought it back from the brink with help from this web site), a Thunderbolt, and a couple of fascinates. Never imagined a nightmare like this. Best part is this D2 is a loaner from my boss while I wait for my Charge to come in the mail!
Any help would be immensely appreciated.
ps. The only oddball variable that I can think of in this mix is that I'm using my micro SD card from my Dinc which had at least one nandroid left on it (which I deleted in Rom manager). I wonder if rom manager (or me... most likely me) got confused and possibly tried to flash cm7 for the Dinc from my SD card. User error, the story of my life.
try plugging the phone into a wall charger and leave it for a while. the charge window will come up
Yeah, battery power seems to be the simple answer to my power button not being responsive. I hijacked my brother's battery and my D2 powered up to the "M" screen and froze with just the power button press, or will boot into stock recovery (holding X on the keyboard while depressing the power after a battery pull), though I don't seem to be able to do anything effective from there. My battery is currently in my brothers droid charging as I continue to look for a solution/hope for more leads from this thread. Being able to consistently get a response from the phone is a step in the right direction though.
Have you tried powering up the phone into bootloader? That'd be a quick way to know if your data is corrupt. I went through that whole process last week. Only thing is that your battery can't charge in bootloader so make sure your battery isn't low.
Sent from my DROID2 using XDA App
If you're talking about holding the X key and power, then yes. This will bring me to the stock recovery menu. If there's an action that can be preformed from the stock recovery that will help me, I'm unaware of it. I know from cwm I would have the option to restore from a back up that I made (I have a stock back up and a back up from as soon as I got the phone up and running with a cm nightly rom).
I'm hoping that when I plug the phone into my computer it will be recognized. I read the instructions on how to run rsdlite here and aside from being able to navigate my phone menus to put it into usb mode, I should be able to take care of everything else. So now my real questions are; If my computer sees my device, is running the rsdlite program my best solution, and what's the next step if my computer does not see my phone?
try this
your phone will gharge if you put it in bootloader mode i know because ive done it now if you phones rom is jacked then flash it back to stock with rsd lite you can get the a955 stock rom from here this web site or my droid world also it will work there is noting wrong with your phone take care chris
I did search, both here and google, and have not come across a similar problem.
I picked up a nexus s 4g recently and unlocked the bootloader using fastboot oem unlock, flashed clockwork mod recovery on, and installed cyanogen 7. I then found out I'm a complete idiot because that rom was made for the GSM phone, and the radio doesn't work.
Tried to use fastboot to load an original rom back on, which failed, so found a windows machine and installed Odin, followed a tutorial on how to flash back to stock, Odin reported a pass, but the phone will no longer turn on.
No amount of taking the battery out, button combos, or charging has changed this.
I had about 70% battery when I tried to flash with Odin, so I'm fairly sure it's not a battery issue.
I also tried to adb devices with the phone hooked up, and nothing was found, so it shouldnt be an unresponsive screen.
Help?
did you make a nand?
I did not. Not sure if it would help, because I can probably download someone elses nand but I don't know how to do anything with it with my phone not powering on
I could be completely wrong about that, not very familiar with nandroid.
You can't get it into download mode?
Correct.
Essentially the phone is dead, it will not respond to anything.
Very similar to the battery not being installed, but I know for certain the battery has a charge.
I just checked the battery, and I retract my previous statements. 560mAh and 3.08 volts. Would that be low to the point of it not taking a charge through the charger?
I have it on a special charger directly on the terminals right now, I will post results once its through.
Read in the fascinate forum that a guy purposely flash a rom from a different device ans used Odin to revert back, also he gave a tip that one should keep trying to use Odin if the first try didn't work. Not sure if this will help never happened to me...
Sent from my Nexus S 4G using XDA App
Fully charged battery did not help
Try what they used to suggest with the epic when it was stubborn. Remove the battery. Plug the usb cable into the phone then into the computer. Try to put it into download mode. If that doesn't work, I can't think of anything else. If you have insurance, maybe they'll swap it when they see it's dead for a refurb. Be nice and play dumb. Tell them something like it froze one time and you pulled the battery and after that it wouldn't turn back on.
I could use my insurance, but its $100 bucks now. Sprint really changed their policy on that.
I also don't really want a refurb phone, when mine was NIB 3 days ago. I realize it's my fault but still.
A little background before I describe what brought me here to the forum for assistance. I had an SGS II (Telus - T959D) that I tried to upgrade...1st 3 Flashes went beautifully until I noticed that there was an ICS upgrade available...so I jumped on it...problem was the upgrade (while Odin said everything was right with the world) caused the phone to go into a permanent boot cycle (never going past the ICS flash screen). I took the phone into the local phone shop and they tried everything they could think of to reset or at least get it back into download mode...nada...zero zilch.
I then had a $600 paper weight. Luckily I still had my Motorola Milestone but I longed for my SGS back.
Yesterday I found an i9000 for sale. Already set up with ICS, running smooth and supposedly in mint condition...all this for $150. I got to the guys house who was just finishing wiping his personal data for me and reinstalling the Custom ROM ([ROM][MIUIv4][ICS][4.0.3][BETA8.1]drZMIUIv4- MULTI LANGUAGE[08/02/2012]).
I look at the phone...great condition...phone is cycling through the install and shows all the right partitions on the screen so I pay my money and walk out.
The phone never actually boots to an active screen and by the time I get the darn thing home it has gone completely dead.
Power button - NOTHING
3 button Download - NOTHING
3 button Recovery - NOTHING
battery pull 3 button Download - NOTHING
left charging all night - NOTHING
I tried to message the guy I bought if from and surprise, the 2 minutes it took him to respond to my offer to purchase has now gone 14 hours when the phone does not work.
I saw a post about a Brick Recovery option that involves ripping open the phone and soldering some jumpers...which I am fine to do...if there is some assurances that that will get the darn thing to at least boot up again.
Anyone who can help with this...my wife is none too happy right now...and in all honesty...neither am I. So I turn to the Android fellowship...HELP
Have you tried a two-dollar jig off eBay? Might be worth a shot before you go ripping her clothes off
Alternatively, you need to see AdamOutler's work
EDIT: Oh and for the price, if it's in good condition you got a good deal
But your phone was on and goes on?
If the phone turns on, its not bricked and there should a way to fix it.
Otherwise go to service point and tell them you don't know what happend, it doesn't work anymore...they should send it in and you get a worked one back.
Good luck.
archiv said:
But your phone was on and goes on?
If the phone turns on, its not bricked and there should a way to fix it.
Otherwise go to service point and tell them you don't know what happend, it doesn't work anymore...they should send it in and you get a worked one back.
Good luck.
Click to expand...
Click to collapse
Correct, but if you try the three-button combo and can't get into download mode, I think you need a jig
Jig no go
I had a jig from my last experience of bricked phone joy. Nothing.
I am thinking that the unbrickable mod is worth a shot...having a tough time finding magnet wire...not to keen on spending $20 on 3 spools when I need less than 1cm of wire.
[email protected] said:
I had a jig from my last experience of bricked phone joy. Nothing.
I am thinking that the unbrickable mod is worth a shot...having a tough time finding magnet wire...not to keen on spending $20 on 3 spools when I need less than 1cm of wire.
Click to expand...
Click to collapse
Someone in the i9000 forums may have some if you ask in the QnA section?
Sent from my Galaxy Note using XDA Premium
bricked sgs2
Hi,
I am with galaxy s2 I9100 on Lite'ning rom 3.6 and CF root kernel.
I flashed it with mobile odin pro.
Earlier I switched and tried to remove the yellow triangle by the method wit 1tar and 2tar and jig described by anonymous572 ("How to remove yellow triangle on any firmware with JIG") somewhere else in the xda. I did not see that this thread was about the Galaxy note and it said 'works on all ICS'...and missed the warning not to use it for sgs2. It worked indeed for the sgs2 to remove the yellow triangle.
But since then I can't enter clockworkmode, downloadmode and recovery mode anymore. Not via the buttons and not with the options in CWM manager and LRT toolbox and Odin Mobile Pro. I mean that I did not get any startup screen until after some minutes the lock screen.
Another reason could be that I restored backup via Titanium and also restored the system apps and data - which I know now I should not have done with a different new rom....
Last try was to start sgs2 with usb connected to PC and Odin activated. This worked and I could flash
according to the method as described in:
http://forum.xda-developers.com/showthread.php?t=1457458highlight=problems+with+recovery+modeed
I ticked re-partition and flashed the whole package including the pit file and this solved my problem.
(flashing without flashing the pit did not work).
After that I switched back to Lite'ning rom 3.6 and it's OK !
Jac
So I've been v customizing friends and families S3's today even an old LG Revolution, And I finally got around to doing my dad's and was using going to use odin to just flash the stock image of JB 4.1.2 and then boom lol
Anyways, it said Successful and all that good stuff, unplugged it, and then restarted it but instead it just shut off. And it wont turn back on, But it still makes the notification sound on my laptop for when a device is plugged/unplugged from the USB, and it started installing the Android device drivers as well, so something in that phone still has to be alive.
Please tell me I can fix thi. When I show up at his his house later with a broken S3, he's gonna be so pissed, and I just got a new Note 3 and I really dont wanna have to give it to him as a replacement.
Just read this in a thread if ound on here while doing a search - And if it doesn't work you can force it into downoad mode by holding down the power. volume down and power key without the battery and then putting in a micro usb cord plugged into the computer. Then put in the battery. -
when i did that, the notification LED lit up RED, but I think i did something wrong after that. So I am thinikin this is fixable if I can just get into stock recovery and format/reset system and cache.
and apparently this guy had the same problem and fixed his - Update:
Josh over at MTVideos is the bomb. He was very professional and accommodating. They are typically a mail order operation but I was desperate and only a couple hours away, so he let me stop by. As soon as I showed up, he put down what he was working on and jumped into my phone. This was the first 32 Gb version he'd seen, so we were learning as we went. He explained everything he was doing as he went. First, try the dongle to get into download mode. No go. Next, hook up his JTAG equipment and dump a full backup, Justin Case .
Next, carefully write, address block by address block a known good 16 Gb bootloader and test. All the way up to 18 ( which, if you read the linked threads, was where I dd'd the recovery). Bingo. Once a known good recovery was put back in, it booted right up.
Factory data reset and we were off to the races.
Moral of the story: the recovery is very important. MD5 that ish before pushing.
I do still have one issue. When it boots, it tries to put me in Factory Mode, then FC's "factory mode" twice before letting me use my phone...
Again, a big thanks to Josh for helping me out. Those guys at Mobile Tech Videos really know their stuff and are good at what they do.
BackSeatSuicide said:
and apparently this guy had the same problem and fixed his - Update:
Josh over at MTVideos is the bomb. He was very professional and accommodating. They are typically a mail order operation but I was desperate and only a couple hours away, so he let me stop by. As soon as I showed up, he put down what he was working on and jumped into my phone. This was the first 32 Gb version he'd seen, so we were learning as we went. He explained everything he was doing as he went. First, try the dongle to get into download mode. No go. Next, hook up his JTAG equipment and dump a full backup, Justin Case .
Next, carefully write, address block by address block a known good 16 Gb bootloader and test. All the way up to 18 ( which, if you read the linked threads, was where I dd'd the recovery). Bingo. Once a known good recovery was put back in, it booted right up.
Factory data reset and we were off to the races.
Moral of the story: the recovery is very important. MD5 that ish before pushing.
I do still have one issue. When it boots, it tries to put me in Factory Mode, then FC's "factory mode" twice before letting me use my phone...
Again, a big thanks to Josh for helping me out. Those guys at Mobile Tech Videos really know their stuff and are good at what they do.
Click to expand...
Click to collapse
So yea. dont have Jtag equipment, but apparently this type of Hardbrick has been fixed without JTAG before. Tnere are a few threads/Guides on here. So I just gotta go find a bigger SD Card cause apparently you need a 16GB SD and I only have an 8 right now cause my 64GB got stolen. Other then that I got everything I need including a dual-boot installation of Linux. So as soon one of the Electronic stores around here opens I am going to get that card and hopefully make this thign work.....
I dont get what Happened. I flashed like 4 or 5 S3's yesterday, all of them were on 4.1.1 so I used to odin to flash them to 4.1.2, that file worked fine for all of them, including thw two of them that were Verizon, just like this one is. The phone has never been rooted or anytiing custom at all done to it. And it was not even 3months old. And my stepdad barely uses the thing. Just gonna be one of those days I can tell already.
BackSeatSuicide said:
So yea. dont have Jtag equipment, but apparently this type of Hardbrick has been fixed without JTAG before. Tnere are a few threads/Guides on here. So I just gotta go find a bigger SD Card cause apparently you need a 16GB SD and I only have an 8 right now cause my 64GB got stolen. Other then that I got everything I need including a dual-boot installation of Linux. So as soon one of the Electronic stores around here opens I am going to get that card and hopefully make this thign work.....
I dont get what Happened. I flashed like 4 or 5 S3's yesterday, all of them were on 4.1.1 so I used to odin to flash them to 4.1.2, that file worked fine for all of them, including thw two of them that were Verizon, just like this one is. The phone has never been rooted or anytiing custom at all done to it. And it was not even 3months old. And my stepdad barely uses the thing. Just gonna be one of those days I can tell already.
Click to expand...
Click to collapse
Have seen that happen when battery too low and messing with SD Card and recovery. Remove battery and sd card a few minutes. Replace battery only and plug into charger for at least 30 minutes. Unplug and Try to boot. If it boots. Power off and replace sim card. Reboot. Worth a shot.
I will try that
Sent Using My Galaxy Note 3
Yea that didn't work.
Sent Using My Galaxy Note 3