Hey guys and gals, I think my note 2 is bricked. I am on stock rom, dont know specific builds, probably whatever is the latest update. I was using the phone friday afternoon and all of a sudden it just shut off. I tried to get it to turn back on, but it would only go to the Samsung galaxy note 2 bootup screen, then do the sounds to boot up. Then it would reboot. I did a battery pull, and it will not even make the sounds now (still get the bootup logo) then shuts off. I have searched some on the forums and I can get it into download mode and i can get to the screen where i can reboot/factory reset/ update (i have the red triangle w/ black exclamation mark). I have to hold the buttons down first and then install the battery to do either though. I have played with roms some when i had a galaxy nexus, but am a little rusty on it. I have not tried to install any roms on this phone though. Anyone know what might have went wrong/what i need to do to fix? I did a factory reset to no avail. Also, like i said, i have done some flashing if thats what i have to do, but really good directions would be great. Thanks.
Related
Hello all -
My "bricked" situation appears to be unique as I've searched all over and have only found others with at least a phone that has a display.
Scenario:
Had SimplyHoney 4.0 installed (I believe Voodoo Lagfix was enabled). Decided it was time to go back to stock. ODIN'd back to stock (doesn't that wipe any VooDoo?). Re-rooted phone and connected to Kies for giggles to see if it would actually work this time for an "Official" update. (Last time I connected the phone it would not recognize the phone as the appropriate phone for an update) This time it saw it as a Vibrant and proceeded to do the Froyo update. Once it was completed, the Vibrant's screen never turned on.
It feels warm to the touch when you turn on the phone after a few minutes like it typically does, but I can't see anything on the screen.
Did this update do an extreme brick to my phone that it is now a lost cause?
I appreicate any advice you have.
BTW, tried the download button combos that are out here and none of those worked.
When I last had my phone open to fix the GPS contact, I see there is a small battery. Would popping that help reset anything?
It's the same scenario in this video on YouTube - "Video of hard bricked vibrant" by htcpro1212
Sorry can't post links yet.
I had a similar situation with a friends Vibrant this is what I did...pull out battery, plug phone to computer with usb, do the three button combo (volume up down &power) while holding replace battery and that should put phone in recovery mode... hope this helps good luck!
Sent from my Nexus One using XDA Premium App
no point rooting if you're going to update with kies, it wipes root
you could have just used whitehawkx stock 2.2 rom, kies has a history of hard bricks after you've been on a few custom roms
keep trying button combo's (vol + and power with the GB bootloades) but chances are its hard bricked, if it doesnt work phone samsung or t-mobile and say you tried updating with kies and it doesnt do anything now
Pm sent I can fix this for you...
You should always try ODIN back to stock. Its such an Relief.
I'm not sure if this will work in this case or not. When I thought I had bricked my Vibrant, I had a picture looking like a phone-triangle-computer on the screen, so it wasn't blacked out.
I got a "jig" (search the forums or google it.) They cost less than $10 and have saved me several times when I've messed up to get me to download mode so I can use odin.
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
MooseV2 said:
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1393519
Click on the software and tools link and use rsd lite to reflash the stock os onto the phone. If that doesn't work I would take it to the sprint store.
I assume you tried pulling the battery?
I'm downloading SBF now. Hopefully it works, because I live in Canada and we don't have Sprint stores.
And YES, I tried pulling the battery. Multiple times. With every combination (eg, plug in, turn on, then insert battery; put in battery, turn on, then plug in, etc)
the sbf should work but may i ask how you managed to brick your photon? when i just got mine i did everything wrong and i never got even a soft brick so i'm interested what i didn't mess up haha
Quick question: I should be downloading the most recent? Will it make a difference?
And damn, did I actually brick it?? I'm pretty new to this thing, this is my first Android and I've had it for less than a month...
And nothing should have triggered it. I added another line in build (ro.media.setting.1080p or something) and I added another setting in /system/etc/mediaprofiles.xml. I was trying to add 1080p to the camera (unsuccessfully). I didn't remove anything, and even after a reboot it was fine.
It wasn't until the battery died, where it stopped booting up. Just my luck :/
You should probably choose one of the newer ones, just becasue of bug fixes, etc. If you happen to know what version you were running before then I'd choose that. I cant stress enough, make sure the one you download is for the Photon and NOT Electrify! And technically yeah that is a brick lol but its extremely hard to legit brick beyond repair a photon due to the fact that we have RSD Lite and SBF files to bring it back.
Strangely, I found a thread depicting the same problem that I had, although with the electrify. http://forum.xda-developers.com/showthread.php?t=14813
Anyways, the problem is fixed, by reflashing the SBF using RSD Lite, everything is back to normal! Well, almost, just have to restore my backup
Thanks so much for your help guys, I wouldn't have been able to fix it without you all!
can you fix a bricked phone??
My Photon has done the same thing! I rooted her and did the Bootstrap Recovery thing. Everything was kosher until I tried to load that stupid Beats Audio. Something happened between me flashing it and the reboot where it locks the phone. I tried to do the Android recovery screen, I wiped, I did about everything I could find. No bueno.
I followed this forum and clicked the software and tools link as instructed. I tried with RSD 5.6, and tried several iterations of SBF's located here and here. I was using SBF - 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM.
It lets me go into boot mode, and when I try to flash the SBF it appears to go through, but it always fails at the end. Which, the posts state it will do, but my phone will not reboot afterwords. After trying everything I could for a couple days, I decided to just take it to a Sprint store. Mind you I've had this under 30 days, but longer than 14 so they stated it would have to be replaced. They tried to flash, but said they were getting stuck too.
I know that a replacement is pretty much the answer, but just wanted to check one more time to see if anyone had any other ideas, or could point me to other forums maybe? Appears I've done what few have been able to accomplish...brick this joker.
ok so my (edit) *Vibrant is not booting up...
I press the power button, the vibrant turns on, logo pops up, boot animation, Tmobile animation and galaxy s animation plus sound all happened, The phone gets to the lock screen and within 3 seconds just shuts down.
Anyone know what could be wrong.
Phone is stock, neither romed or rooted. is this a battery issue, hardware or software
Does it boot up when you have it charging? And which phone is it, the Vibrant or the Captivate? Those are 2 different phones.
djquick said:
Does it boot up when you have it charging? And which phone is it, the Vibrant or the Captivate? Those are 2 different phones.
Click to expand...
Click to collapse
sorry simple mistake, it is a tmobile vibrant...
it boots up when plugged in and when not plugged in... gets to the lock screen and it just waits and then shuts down completely.
can boot into
stock recovery
download mode
Kontagious said:
sorry simple mistake, it is a tmobile vibrant...
it boots up when plugged in and when not plugged in... gets to the lock screen and it just waits and then shuts down completely.
can boot into
stock recovery
download mode
Click to expand...
Click to collapse
If you can boot into stock recovery/download mode, just do a factory reset or flash the stock rom using odin
djquick said:
If you can boot into stock recovery/download mode, just do a factory reset or flash the stock rom using odin
Click to expand...
Click to collapse
I tried the factory reset and it says cannot read update.zip
i tried the odin stock rom flash and same problem persists.
Kontagious said:
I tried the factory reset and it says cannot read update.zip
i tried the odin stock rom flash and same problem persists.
Click to expand...
Click to collapse
Maybe you have a defective bootloader or phone. If it's still under warranty, just bring it back to T-Mobile and exchange it.
was trying to fix a vibrant for a friend of mine with a very similar problem
after many hours of work w/ odin & attempting to flash different things.. i concluded that it was hardware related bc i made it all the way to stock but it would just shut down randomly
does it give any sort of message when it shuts off? or just goes black?
have you dropped it a lot?
jonen said:
was trying to fix a vibrant for a friend of mine with a very similar problem
after many hours of work w/ odin & attempting to flash different things.. i concluded that it was hardware related bc i made it all the way to stock but it would just shut down randomly
does it give any sort of message when it shuts off? or just goes black?
have you dropped it a lot?
Click to expand...
Click to collapse
im starting to think its hardware related as well. at time when i boot into stock recovery the battery logo just shows up, the android man with the the exclamation point. idk if up to a certain level of currect is drained the battery shorts out. how can i possibly test the battery??
There is no message or anything... as soon as it boots up to the lock screen it just goes black.
i just acquired this phone. I have a HTC Glacier that i use for my everyday. this used to be my friends old phone and it started doing this, he just got another one and gave me this said if i could fix it i could have it to mess around with. as far as i know it hasnt experienced much rough and tough life. on the outside it looks almost brand new.
So I bought a brand new battery and the vibrant won't even charge the new battery...
Sent from my HTC Glacier using XDA
sorry to revive this but did you try cleaning the battery contacts?
You probably moved on with life lol
Ok, so heres the deal. The s2 is my sisters phone, and she comes home and told me the phone wont turn on, that its stuck on the boot screen and it just keeps turning off and doing it again. So I started looking into it (Im an iPhone user, so I'm not too familiar with android devices. BUT I do know a bit about computers, cell phones and just technology in general). I ended up finding out that its stuck in a soft brick. So I started youtubing how to fix it. Found a great method using Odin3 and Samsung Kies. AND IT WORKED. I turned the phone back on, got past the lock screen and everything was all good.
After about 30 seconds, THE PHONE BRICKED AGAIN:crying:. And it went right back into the boot loop, I cant get it into download mode because it just keeps restarting after a couple of seconds. With that happening, I cant get the computer to recognize it so I can do a recovery fix with Samsung Kies. I legit cannot find any solution to it.
The thing that baffles me and is causing me a huge headache is the fact that THE PHONE IS NOT ROOTED. nothing has been done to it, its completely stock. So if there is no solution to it, can somebody at least tell me what might have been able to cause this?
Thanks to all,
Dariel
Well, you're in the wrong forum for the SGH-T989. That's probably your issue.
Hi all,
So today my Swift 2 plus is no longer booting correctly. It is hanging at the orange Wileyfox logo, you still see the animation on the Wileyfox text going from left to right but nothing will happen.
If let it run for hours now, tried restarting, tried charding to 100%, tried wiping the cache. I dont see any other option than to do a factory reset....
Anyone has some tips what i can do? I dont have an SD card near me to do a reinstall of some sort, i can get one if it will do the trick though.
I hope you guys can help me out with this problem, thanks in advance
oh btw. I installed all updates so i guess i am running the newest official version
Whenever I have had a bootloop (apart from the Nexus 5x!!!!!) a factory reset has normally worked. It's a pain but usually sorts it.
May not sort yours but I know it's usually worked for me. I always do a factory reset after an update anyways.
Have you held the power button and volume down button?
Mine (2X) randomly goes onto the same screen. (I believe it's a bootloop, but not sure.) When it does, I do that and it works. It is quite annoying though, especially when it happens at night and I don't hear my alarms...