Related
:crying: any ideas ?
everything was working perfectly and i didn't do anything , just when my first battery ran out , i shut it down and switch second battery then it just doesn't boot up anymore ... even with data cable connect with charger or PC, because usually it will show a charging animation when system isn't booted up ...
and one thing strange is that when i plug in my battery , phone doesn't boot up but it still heat up like i am using it ...
a little help please ...
qtwrk said:
:crying: any ideas ?
everything was working perfectly and i didn't do anything , just when my first battery ran out , i shut it down and switch second battery then it just doesn't boot up anymore ... even with data cable connect with charger or PC, because usually it will show a charging animation when system isn't booted up ...
and one thing strange is that when i plug in my battery , phone doesn't boot up but it still heat up like i am using it ...
a little help please ...
Click to expand...
Click to collapse
the same happen to me week ago! i think its jellybean...
Cascabreu said:
the same happen to me week ago! i think its jellybean...
Click to expand...
Click to collapse
how did you fix it?
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
qtwrk said:
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
Click to expand...
Click to collapse
Same issue with mine. Yesterday, 8/20/12, I broke a sim card connector pin and Nexus S wouldn't recognize sim card after a reboot. Rebooted the device again after the warning message: Sim card not detected/found.
Now Nexus S won't boot. Computers (Windows & OSX) can't recognize it's connected and 5 different charges won't show that the battery is charging. Battery still has a charge as I tested it in another Nexus S. When the battery is in, the device heats up. When connected to a power source, the device heats up.
Used Unbrickable resurrector with no success. UR shows: Device not found, No device detected.
Finally, I was running Jelly Bean from OTA update and not rooted. I noticed that in the past week or two the stock Andoird keyboard would cause force closing of apps or exceed processor threshold of 35% even if there was no program running. Google Now was also sucking the battery after the JB update. Turned that battery drain off on the other Nexus. Also, the Android Media process was taking a drain on the processor. Usually running at 40-50%.
Bought this used from CowBoom and hoping the extended warranty will replace or fix the broken sim card connector and unbrick the phone.
Luckily I have an iPhone 4S and a 2 yr old HTC Desire to turn to.
I've read on another thread, perhaps?, that two other users in the past week or so have had this same problem.
nexus s GT-I9020T Bricked after JellyBean
qtwrk said:
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
Click to expand...
Click to collapse
Same happened to me. The Unbrickable resurrector also didnt detect the phone. so i made the Unbrickable Hardware Mod (httpxx://forum.xda-developers.com/showthread.php?t=1566475) remove the xx from httpxx. now my phone is being detected and the tool is able to load its files. but still the phone is dead, no thing happens and the tool shows no device found after it loads the files. but when i picked GALAXY S from the drop down menu. the tool loads the files and now both the tool and the phone shows download mode with an android shoveling dirt. heimdall now detects the phone but it doesnt work caz its not a GALAXY S. So let us know what happens if u try this mod. cheers
The exact same thing happened to me. Strangely, it's happening with JB roms. And yeah, i told my problem in a very educated way on the ROM topic and they simply deleted the post, how nice.
Anyway, i just sent the phone to the warranty almost three weeks ago, i'm waiting for them to fix it or give me a new one.
djdeepblue said:
The exact same thing happened to me. Strangely, it's happening with JB roms. And yeah, i told my problem in a very educated way on the ROM topic and they simply deleted the post, how nice.
Anyway, i just sent the phone to the warranty almost three weeks ago, i'm waiting for them to fix it or give me a new one.
Click to expand...
Click to collapse
no , i was running 4.0.4 , AOKP M6 , as matter fact , it seems to be a problem of latest BOOTLOADER
dokugan ryu said:
Same happened to me. The Unbrickable resurrector also didnt detect the phone. so i made the Unbrickable Hardware Mod (httpxx://forum.xda-developers.com/showthread.php?t=1566475) remove the xx from httpxx. now my phone is being detected and the tool is able to load its files. but still the phone is dead, no thing happens and the tool shows no device found after it loads the files. but when i picked GALAXY S from the drop down menu. the tool loads the files and now both the tool and the phone shows download mode with an android shoveling dirt. heimdall now detects the phone but it doesnt work caz its not a GALAXY S. So let us know what happens if u try this mod. cheers
Click to expand...
Click to collapse
well ... i don't have these tools to do hardware level of modifications ...
anyway , i just send to repair , i think , the motherborad or something should be replaced ...
i was thinking about buying a new phone such as Galaxy Nexus if my Nexus S can not be repaired or way too expensive to repair...
i had same issue a few days after upgrading to JB JRO03E. i got the main board replaced under warranty. took about 2 and half weeks.
the phone came back with GB installed but OTA'd to ICS then JB JRO03L.
I had the same issue running cm10-0823. Screen froze while sitting idle. Pulled and replaced battery, and phone won't come back.
Looks like cm10/jb is causing some burn-out in circuit board; cpu, memory...?
_android_ said:
I had the same issue running cm10-0823. Screen froze while sitting idle. Pulled and replaced battery, and phone won't come back.
Looks like cm10/jb is causing some burn-out in circuit board; cpu, memory...?
Click to expand...
Click to collapse
as i have heard is that new bootloader messes with hummingbird CPU ...
I have exactly the same problem I flashed Codename Android ROM 3.4.1, done some overclocking (only 1200 MHz) and the device crashed. Well, nothing unusual. But I removed the battery, I think it was just when the device was rebooting - I think display turned on, I noticed some flash when the battery was already removed.
I tried to turn on the device, but it's dead. Display doesn't turn on, UnBrickable Resurrector says device not found.
I can send the phone to the warranty, but it's unlocked. Do you think they will find out it's unlocked? Even if the download mod doesn't work etc?
What should I do?
Well, I happened to end up with the same problem. Installed latest cm 10 nightly, started rebooting my phone. The moment I restarted it from CWM I realised that I forgot to flash some mod in CWM so I pulled the battery to go into recovery. Phone bricked, no input at all. Sent my phone on warranty, I hope they won't mind it had unlocked bootloader and cm10 on it ;P
That's just a bit stupid to be honest, pulling the battery while booting why not just wait?
Sent from my Nexus S
Now I know it's stupid. Do you think they will repair it even though it's cm flashed and unlocked?
i sent mine to repair and they fixed without paying a dime!
Cascabreu, you just made my day Well, I just have to wait now
nexususer1 said:
Now I know it's stupid. Do you think they will repair it even though it's cm flashed and unlocked?
Click to expand...
Click to collapse
The mainboard is fried. No way of knowing previous state of your phone. They will just replace the board.
Sent from my Nexus S using XDA Premium HD app
_android_ said:
The mainboard is fried. No way of knowing previous state of your phone. They will just replace the board.
Click to expand...
Click to collapse
I had the same issue back in August just after I flashed 4.1.1/JRO03E. It just died one day while listening to music. Took about 3 weeks to get the mainboard replaced under warranty. It came back bootloader unlocked and with Gingerbread 2.3.3 installed.
Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
I guess this is an option also: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
mcappleman said:
Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
Click to expand...
Click to collapse
Call verizon and they will send you an replacement. If its thats far gone theres no way they can check to see if its been modded.
Me too!!!!
Message removed
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
fr8cture said:
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
Click to expand...
Click to collapse
But I've had it for 20 days now and their website says they don't allow returns or replacements after 14 days. Or is this different because it randomly died?
Also. I don't get insurance on my phones because they always would charge me $10 or more a month and then when the phone died they would charge half the cost of the phone just to get it replaced!
Honestly I think I may just send it to MobileTechVideos.........
Unless I still have a chance with Verizon. Hard decision............
I'm pretty sure the 14 day timeframe is for refunds on the purchase. Most electronics have some sort of manufacturer's warranty.
Have you tried to get it into download mode? volume down, then home, then power, Hold them all together until it boots into download mode? Do this while plugged in maybe?
samsung s 3
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
You really give your phone number out to strangers like that?
Sent from my SCH-I535 using Tapatalk 2
cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
mcappleman said:
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
Click to expand...
Click to collapse
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
silver04v said:
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
Click to expand...
Click to collapse
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
mcappleman said:
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
Click to expand...
Click to collapse
If you can't get into download mode then yea, most likely I guess or the battery died. I just didn't see that you said you tried to get into download mode.
Sent from my Synergized vzw S3!
Glad you got this fixed! Also i think its a 30 day replacement or swap for another phone if you don't like it. Thats what i was told when i got mine.
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
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
Hi there, bought samsung s6 almost 2 years ago, everything worked great until after about a year it suddenly turned off and bootloop started, the logo itself appeared and nothing more. Connecting to charging didnt change a thing. I decided to wait and after it discharged, it started working normally again and turned on. There has been no problem since this week. Suddenly went out and after connecting to the charging again started to display only the logo and nothing more. But this time, neither discharging it nor charging anything (it is already week like that). I did some research on the internet about recovery mode, etc. but even this recovery mode did not turn on, only could enter the download mode and do a reset (power + volume down). I decided it maybe was battery problem since phone was going from 100% to 0% in like 2 hours lol. I took it to local repair service to exchange the battery for a new one, they did and told me it still doesnt work and bootloops, so battery wasnt the problem, but the motherboard was. They told me that they can try to flash a soft but probably its not the problem and something happened to motherboard. (yesterday) I decided that im gonna just go to the distributor point where i ve bought it and im gonna demand a repair or refund since its on warranty (2 weeks only left lmao) and they told me that samsung probably will just replace this phone for a new one (so im gonna lose all my stuff and things there are REALLY important, 20k important photos, really important messages and more) so i was like okay if im getting new one instantly i need to get this stuff back somehow so i told them ima be back in 2 days when i get the data back. Sooo today i found that there are ways to recover data from bricked phones so i did use dr. fone and went to recovery while on download mode. Then it showed that it failed and nothing changed but to addition recovery is not seandroid enforcing appeared above the logo since then. I thought ok whatever just gonna lose my stuff but getting new phone so whatever. Then i found out that there is something like knox and when i checked it it was flagged 1 (0x0500) and learned when knox gets to 1 warranty is gone and i was like what has just happened LOL. So my question is what should i do now really jesus this is pathetic if i really got rid of my warranty just like that, i wanted to give this phone back tomarrow to get a new one, but now i dont really know what to do im scared that samsung will say that i caused the damage by doing something in system and there is nothing i can do, if the red text wasnt above the logo maybe they wouldnt even check knox status and other stuff but now it just screams like something was done lol should i try to get rid of the red text so they wont see anything and pray or just leave it as it is now and give the phone back (and pray too) or maybe it is not really a problem? i havent rooted and changed anything, havent unlocked any bootloader, too (i think lol) Btw in download mode system status shows official, binary says custom. I think its worth to say that this samsung was getting REAL warm sometimes, i know all of these s6 are like that but trust me it was burning maybe that caused the problem? idk what to do i have time till tomarrow morning to think what im gonna do with this warranty stuff. Since its on warranty only 2 weeks more i have just like one try if they accept the demand, if they dont its gg. What should i do what do you think? :|