So, I flashed back to stock and master cleared using Odin. Then I went and did the OTA update from ATT and it said your phone will reboot in 5 secs. Well it turned off, like expected, and never came back on. Now it will not turn on at all. I get no response from anything I do. All button combos that I know of and nothing. I have no clue what happened. The OTA update screwed me phone up. Anyone have any suggestions or do I need to go to a warranty center or ATT store? Thanks.
Wow, this is where search could have helped. OTA was known to brick phones, Mini Kies would have got you to JH7 or designgears CWM zip.
Looks like a replace to me.
Sent from a phone somewhere in the universe
Well, sorry I didn't search for it. I had no idea the OTA bricked phones. I did look at other bricked phones threads before I posted. Anyways, I got my replacement already from local support center. She said it was a new phone but it has just as old of an IMEI number and is a 1007. But I tried out the GPS on the way home and it was absolutely perfect. Makes me think it was a hardware issue because the software is the exact same, of course. Anyways, happy that it works now. Just hoping that it really is a new phone and that the shutdown problem doesn't happen again.
Related
Firstly, may I apologise, I know this has been covered, I've trawled the internet for hours but just can't seem to get an answer.
I recently updated my UK, unlocked Galaxy S to Froyo via the registry hack, all was fine (ish). Because Froyo had been delayed in the UK and wasn't as great when it was running on my phone I thought it would be safer to revert back to 2.1 and wait until the official UK release came out (I know some will ask me why I did this, I just felt that Froyo was held back for a reason and I couldnt get an answer as to if I could update to the UK version if I already had the Scandinavian one). So I did the reg hack again and was offered 2.1. Everything seemed to go smoothly until the phone rebooted after downloading from Kies. Now the phone's animation starts then the flashing S symbol displays for an extended time. After that, the screen goes black. If I touch the two touchscreen buttons they stay on but do not go off. If I hold the power button the phone turns itself off and when the phone is powered off and I plug it into my PC with a USB, the battery charging sign comes on.
The phone was rooted and I did have the OCLF on but uninstalled that and un-rooted before changing the firmware so it was back to stock.
Before I get 20 people telling me to put the phone in download/recovery mode I must tell you that I can't. My phone has never been able to do it. I've tried every single way and button order suggested. I'm not the only one who's phone won't do it either so it's not just me. The only way I ever saw recovery mode on my phone was when I used the one click root on the PC.
I'm at a total loss. Debugging was turned off because Kies won't let you do anything with it turned on and so ADB recovery is out also.
Please help if you can.
Many thanks,
Ryan
Boot to download mode, do a repartition with Odin and 512 pit flash, remove battery and boot again to download mode and then do a odin firmware flash to which ever firmware you want.
thanks intratech but I can't boot the phone into recovery or download mode (sorry should have stated that). Believe me, I have tried every combination. I did a lot of research and discovered that there are quite a few people for whom that feature was disabled.
if the 3 button combo is not working on your phone, you should not do these risky stuff actually
take a look at this thing
http :/ / forum.xda-developers.com/showthread.php?t=819551
remove spaces
thanks Noobproof. I remember coming across that thread last night. Although I consider myself ok with software, soldering and slicing just isn't my forte. I haven't got a clue about soldering, etc. I've just come back from the Carphone Warehouse (Samsung suggested I go there as they are the service centres listed on the Samsung UK website). The engineer had the phone for half hour and said that the "board was faulty". Haven't got a clue what he meant by that, unless he meant the internal SD which a few people have had go on them. Anywho, he told me to ring Samsung and send it in for a repair. I did that and need to send my phone special delivery to a company called regenersis in Scotland.
I knew rooting and flashing custom roms was a risk, that's why I never touched Odin,etc. I used Kies to upgrade to Froyo and Kies to downgrade back to Eclair. You would think that sticking to official Samsung software would be safe. I must admit, when it was going well I loved my Galaxy but more and more I'm starting to wish I'd opted for the Iphone.It just seems that there have been so many glitches and bugs, I mean, why should there ever be a need for lag fix in the first place? I often found myself keeping my fingers crossed when downloading simple apps as that was usually touch and go!
Feeling a bit deflated now. Was hoping some clever boffin had designed a software solution that would recognise the phone and force it into download/recovery mode.
Ah well, thanks for taking the time to respond anyway.
Best wishes,
Ryan
You know i was very happy when i for the phone for the first time and while i was doing a research (i live in turkey and there is no stock android market here) i came along this forum. And i have learned that i havent got the 3 button combo. I downloaded the 3 button fix abd took the phone to samsung centre.
They told me that they cannot flash it and i made a huge fight then they accepted and i have my 3 buttons. Never give up your phone. I dont think the internal sd is faulty it is just corruppted if you can access the recovery menu you could fix it. Any way you have to find a service centre that has an anyway jig box other a jtag box otherwise they will have to replace the motherboard. Good luck
Sent from my GT-I9000 using XDA App
I had the same problem all i did was use a different firmware .. didnt choose anything in pitfile and did not check on repartition but checked only F reset and Auto reboot and flashed my phone and voila it booted perfectly fine
Hope it helps others with black screen problem after booting
thanks
mike
I had the same problem too. This method really works.
Wysłano z GT-I9000 z użyciem Tapatalk
OK so in Australia we got the SGS FroYo 2.2 update in November and when I went to upgrade my phone everything went stupid. Basically I'd never needed/wanted to root or anything like that my phone was running with its basic firmware plus OCLF to fix the lag. Basically I got over excited about the update and didn't read anything and well I bricked my phone because I didn't remove OCLF. That was fine and dandy until I released that my 3br would not work anymore (don't ask my why) so i had to send it in for warranty. So thats the background/past before everything went stupid again.
Now I got my phone back and the 2.2 upgrade had been installed the repair deatils where:
- Inspected and chemically cleaned all contacts
- Upgraded handset to latest available software DTJP3
- Unit tested and passed live on air test
- Handset meets all manufacturer specifications SU
Click to expand...
Click to collapse
Now like I said I got my phone back and everything was fine & dandy but I noticed it was really slow, slower then 2.1 was. Also my D button would not work, no matter how hard i tried to press it, even when I swiped over it the blue line thing goes around it. Along with not being able to press the d button, anything located near the side of the screen would just not register my touch. Also my phone would just decide without me touching it to just select things and malfunction, type whatever text it liked, it also would constantly scroll up and down and basically just screwed my head in. Now I thought this was just a temporary error so I restored factory settings through 3BR and privacy settings method and it seemed fixed. So I applied z4root so i could OCLF back to fix the lag but that bricked my phone so I had to reset it again and then I applied voodoo lagfix (the one click method from market). I didn't really notice and difference with the voodoo lagfix so i disabled it and bam! my phone went even more stupid. So I googled and searched xda and removed voodoo entirely by flashing back to the original firmware and that seem to fix everything but the D for about 5 mins and now its not as bad as it was but its still malfunctioning all over the place and I can't even have it on the 1st screen without it constantly going into my contacts and trying to delete them or type things...
So what do I do? If I send it back for warranty will they notice that the firmwares not optus but the orginal (from samsung-firmwares.com)? will that break my warranty? Plus sending it for warranty now will mean I won't get the phone back till January at the earliest. Or can someone suggest something else to go about fixing it?
Sorry about long post, thought going into detail would be better and more helpful.
Hey mate,
If you reflash with dtjp3 from samfirmwares then that is the firmware they put on and will not be able to tell you fkd with it.
Good luck
Alex
surprised it took this long, had counted myself one of the lucky ones.... even though i was one of the unfortunate saps whose phone came with the three button recovery disabled, (a two week trip to samsung for repair).... was running darky's rom 9.3 and various eaarlier versions since october with no problems... today google voice started force closing so i tried to reboot the phone and it would not boot up again... i went into recovery and tried a wipe, still no go.... then i tried to reinstall the rom, still no go.... when it is booting up it just keeps looping the loading screen and vibrates once, then pause, then three times... i can get into recovery and download mode.
anywhose my questions are this,
A) best way to determine that the SD is in fact bricked.....
B) best way to get a bricked SD card back to stock so i can send it back to samsung for warranty.
C) if i get it back fixed from samsung, should i try to off this piece of Sh*t phone that has given me, and others soooooo many problems. that is to say, has anyone who has had their phone fixed recently had their new SD card go corrupt again??
P.S. never buying anything samsung ever again, PERIOD!!, had a 30 inch monitor of theirs recently go bad as well, like i dont care if they cure cancer, bring peace to the middle east, and resurrect jesus!!! i still wouldnt buy a rememberance day poppy from them!!!!!!!
Sounds similar to mine when it bricked. The best solution is to use Odin and flash jl2 onto it and send it in for repair.
They were doing a replacement and compensation program through bell for a while but I think that's over now.
On the plus side, since my repair in December the phone has been amazing. No problems flashing different roms many times. The phone has been better than I expected! The number of phones dying from this issue have dropped significantly since the new year.
Sent from my GT-I9000 using XDA Premium App
is there a link you have to flashing this frimware with odin? never used it before....
hope the replacement and compensation is still going on, kinda pissed that bell didnt call me about it...
tried flashing JL2 with odin, when i have odin open and my phone in download mode, and i plug the phone in, windows does not recognize my device and thus does not install drivers for it and thus im pooched.... ergo vis a vis help please
i know im just talking to myself but just in case anyone wants to know, installed kies to get usb working, flashed JL2, gonna take phone in for repair now (2nd time) awesome!!!
Sorry it took me a while to reply. Forgot to check this thread. There are a bunch of threads about dealing with it. If you get a hard time there's a thread you can search for about filing a complaint to the ccts. That would get you the replacement and comp I think. Good luck!
Sent from my GT-I9000 using XDA Premium App
Hey All,
I decided to flash back to stock using the odin 3 method. Basically I was planning on getting rid of the phone soon. I cleared everything off the internal "SD" card, wiped all user data and cleared the cache. Booted back into the stock OS, everything looked fine. Checked the internal card again and it had written some new files. I assume these are just operating files for the stock OS.
So I power down the device correctly, pull the battery and install the sim card and 8 gig flash micro sd card. The micro card is completely clear. I boot the phone back up with no issue, it hits the network with no issues. I start looking though all the bloatware and go back into setting and turn the USB setting from Kies to USB storage. Then a get an odd alert telling me an update for my phone is available. So, I figure a stock update couldn’t hurt and let it download and install. It downloads to 100%, and advises it needs to reboot to install the update... Ok, so I let it... the screen come back with a progress bar and not much else. At 50% the progress bar stops and a message telling me the update has failed pops up... The phone then shuts off.......
Bricked..... I mean bricked bricked. 3-button doesn’t work, Jig doesn’t work. the 3 button battery pull doesn’t work. 2 button while putting in the usb cable with odin loaded doesn’t work. 3 button with battery out, usb in and then put the battery in doesn’t work.. This thing is dead....
Now my question....LOL... since I had cleared out any and all data, will AT&T give me crap saying I voided the warranty by flashing my phone?
Do they look at what’s stored in ROM? Because before the phone died I had flashed it to stock... I know how to call XBM (their exchange program) and I know they will send me out a refurb phone, to questions asked. But my concern comes in when I ship them back my device and start snooping around... what are they looking for? No liquid or physical damage. Normally I don’t try to get one over on the man, but it was their crappy update that bricked the phone, not my tampering….
any thoughts or experience with this matter?
Did you flash back to JF6 or something? That OTA was probably the busted JH2 they pushed out to all our devices last year, resulting in tons and tons of bricks. They shouldn't give you any crap over it - it was their own fault that your device got damaged - and if you flashed everything back to stock and formatted the internal SD, then technically your phone WAS at factory defaults, so they wouldn't be able to tell what you've been doing with it prior to that anyway.
Edit:
Also, if ATT gives you **** over it, mail it to Samsung. Tell them you were on eclair, got an OTA notification and it bricked your device. They'll ask you to mail it in without the battery and back cover, and swap the board for you. Takes about a week, but whatever.. beats having to deal with some dumbass ATT rep.
this is just good to know....dont flash to stock and try an OTA update.
This exact thing happened to me. My phone was replaced without question but the tech guy told me something interesting. Just to check things, he took the battery from my bricked phone and tried it in a new phone - nothing. The battery didn't even work anymore. Likewise, he tried a new battery in my bricked phone. Again, nothing. Anyway, I got the new phone and battery and all is well. He said it was junk now. They will never be able to tell what ROMS were flashed on there, I suppose.
jack man said:
This exact thing happened to me. My phone was replaced without question but the tech guy told me something interesting. Just to check things, he took the battery from my bricked phone and tried it in a new phone - nothing. The battery didn't even work anymore. Likewise, he tried a new battery in my bricked phone. Again, nothing. Anyway, I got the new phone and battery and all is well. He said it was junk now. They will never be able to tell what ROMS were flashed on there, I suppose.
Click to expand...
Click to collapse
Well I thought they do like a jtag, or am I wrong?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
nope, no JTAG, just a new motherboard
Idk what's the problem with Samsung phones and updates. I had the same problem with my Note 3 when KitKat got released, I had to get a replacement phone. Lucky for me the replacements Note 3 didn't have the update on it. However I wasn't so lucky with the Note 4.
I accidently hit the update on my notifications when I was half sleep.
Anyways.
Every since Lollipop been installed on my Note 4, it has been a nightmare from hell.
When I installed it on my original Note 4, I kept having my keyboard become unresponsive. Force close on multiple apps (stock Web, camera, calender, and more).
I called T-Mobile to see if they could send me a replacement. They "tried" to fix it, saying that I should do a factory reset and clear cache , which I already tried before I called numerous times.
Finally they said they said they were going to send me out a replacement phone.
I also asked if anyone have been complaining about Lollipop they said no, they were totally oblivious to Lollipop having any kinks (as always ). It's crazy they said that because I have read over 100 post bashing the new update.
I received the Note 4. I turned the phone on and Lollipop was already installed. I called T-Mobile and asked why was Lollipop installed on my replacement, they informed me that they are sending out the phones with Lollipop, and assured there would be no problems with it.
With in the first hour, my phone would turn off and not turn back on. I knew there was nothing wrong with the battery because it was on 90% and it worked flawless with another phone. So I drained all the electricity out the phone and put the battery back in. That worked, but it did over 20 times within that day. I called T-Mobile again , they told me I would have to go to a store and see if they could diagnosis the phone.
The next day I went to the store, everything came back clear on the diagnosis, but they could see it turn off randomly.
I called customer care and explained the situation and told them I need a replacement.
Now I am waiting on a replacement. If this one don't work, I think I will have to get on whole different phone. I'm on the verge of getting a flip phone because I know that I don't want to have an iPhone.
Anyone having these issues with the update Lollipop?
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
MajorTom_ said:
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
Click to expand...
Click to collapse
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
W0man09 said:
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
Click to expand...
Click to collapse
As long as you can get it into download mode something may be possible.
Odin to stock lollipop, factory reset / data wipe.
Additionally, I would consider a custom rom.
..........
If you really like kitkat better you could also Odin to stock kitkat, factory reset / data wipe.
MajorTom_ said:
As long as you can get it into download mode something may be possible.
Click to expand...
Click to collapse
Lol thanks for the help. I can't even get it to turn on, to get it in download mode. ??
. Now I'm just waiting on T-Mobile to send the replacement.