Results 1 to 20 of 20
- 12-12-2011, 11:59 AM
Thread Author #1
ATT Samsung Galaxy S2 bricked
I've already tried the steps for unbricking that were listed in the other thread and my phone still isn't working. Here's what I've done so far:
I downloaded the Odin3v1.85 software, put my phone in download mode, and tried to install it. The upper left hand box said fail and now my phone won't do anything except say "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I then downloaded the unroot program and attempted to install it, it also says fail. Can anyone help me with getting my phone back to normal/a root that will actually work? I bought the phone yesterday (12/11). This phone is the S2 Skyrocket.Last edited by LucasBrown87; 12-12-2011 at 12:29 PM.
- 12-12-2011, 01:17 PM #2
I'm pretty new to installing roms but can't you just enter recovery mode and recover from there? I think it is hold volume-down & power to access recovery.
Sent from my SGH-I777 using Tapatalk - 12-12-2011, 01:24 PM
Thread Author #3
- 12-12-2011, 01:41 PM #4
- 12-12-2011, 03:14 PM
Thread Author #5
Re: ATT Samsung Galaxy S2 bricked
I've tried pretty much everything. I can still get to the page where it says "Warning!! A custom OS can cause... Volume Up: Continue, Volume Down: cancel (restart phone). But whether I press volume up or volume down it takes me to the same "firmware upgrade" page.
- 12-13-2011, 11:28 AM #6
Re: ATT Samsung Galaxy S2 bricked
Please excuse the seemingly simple questions. Be aware that this list is typed from memory, so if you have better information, or a more robust list of steps, or any questions about the steps, ask first

PC Connectivity:
1) Did you install the correct Samsung drivers for your operating system?
2) Had your PC ever correctly identified the phone to PC USB connection?
3) Did you ever successfully transfer files between the PC and phone?
USB Cable:
4) Is your USB cable known to be good (they can go bad if treated poorly, i.e. tugged hard)?
5) If not, do you have another that you can try?
Using ODIN 101
6) Did you remember to start ODIN before you plugged the phone into the computer?
7) Do you have the correct ROM for your phone (I notice that you're talking about a Skyrocket, this is a SGSII forum, there's an ambiguity there)?
8) Is the ODIN version you have a one-click, or do you need to select files in the slots (PDA etc)?
9) If #8 is a select-files version, do you know which files go where?
10) #9, are you sure?
Get phone into download mode
11) Do you know how to get your phone into download mode?
12) (check for forum-readers) What does the screen look like when you get there?
Assuming that:
A) You have the correct drivers installed on your computer
B) You started ODIN with nothing plugged in
C) You have the right ROM / version of ODIN
D) You chose the right files in the right places, if needed, in ODIN
E) You got the phone into download mode,
F) and then connected it to the computer
Check Connection
13) Does ODIN recognize that something just got connected (you should see a connection indicated in the top left hand area)
ODIN options
14) What ODIN options are selected?
15) Did you change any of these, or are they all still defaults?
Give it a go
16) What happens when you press the "START" button in ODIN?
Hope this helps, if it does, consider pressing thanks, it makes me smile
AoNThanked by: - 12-13-2011, 12:08 PM
Thread Author #7
- 12-13-2011, 02:21 PM #8
- 12-13-2011, 03:28 PM #9
Re: ATT Samsung Galaxy S2 bricked
dmcincubus,
Rooting a phone and installing a ROM are two completely different things. ROM install was what the original poster had had problems with.
I cannot imagine keeping an un-rooted phone. Rooting is necessary to stop / remove the bloatware junk that your carrier adds to the phone.
I rooted and ROMd my captivate.
My SGSII is rooted, this time I've stuck with the stock ATT ROM, as it is more than fast enough. I have all the ATT & Samsung stuff frozen (using Titanium backup, .... which requires root).
None of this is anything to be scared of, just do your research first. Even if you don't, or make a mistake, or find a new way to brick a phone, the community here (and over at XDA) are 99.99% likely to fix your problem, all without even coming around to your house for a cup of coffee.
AoNLast edited by anneoneamouse; 12-13-2011 at 03:42 PM.
- 12-13-2011, 04:04 PM #10
- 12-14-2011, 02:00 PM #11
- 12-19-2011, 08:02 PM #12
- 12-20-2011, 11:13 PM #13
Re: ATT Samsung Galaxy S2 bricked
Man glad the Sammi is wife's phone and she won't let me hot rod it but just reading about how much there is to learn...as an outsider looking in I gottah say thanks for showing what a great group of folks you all are over here....April my Torch is history...wondah what Samsung has in the wings...lol...
- 12-27-2011, 07:31 PM #14
- 12-27-2011, 08:04 PM #15
- 02-26-2012, 07:02 AM #16
- 04-05-2012, 05:30 PM #17
Re: ATT Samsung Galaxy S2 bricked - easiest resolution steps
You must be sure you have an AT&T Samsung Galaxy S2 Skyrocket; and you are stuck on a screen where you can get no further and it reads "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again"
You need to download Kies on your PC
Update it to the latest version
Your phone will not turn off
Your attempts to press and hold the volume down + power buttons will get you no where...
Remove the battery from your phone
You will see your phone serial number and model number sticker
The model number is SGH-I727
S/N is unique and alpha numeric so please make a note of it
Then return to Kies with your phone hooked up to the PC via USB... Kies and the phone will not give you clear indication that they are connected ... don't worry
Got to Tools menu in Kies and select Firmware upgrade and install
a new window pops up where you need to enter the s/n and model number of your phone. Use s/n as is on the sticker on your phone i.e. upper case letters if upper case letters used and small case if in small case and numbers
Model number is SGH-I727 as is
and select ok
ignore instructions select ok and proceed ...
You and your phone are back in business.
Thanked by: - 12-14-2012, 06:37 PM #18
- 01-01-2013, 09:39 AM #19
- 01-14-2013, 08:30 AM #20


Reply

































