Related
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Remove Kies and reinstall see if it picks the phone up and installs the drivers .
jje
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
That kernel is for the Epic touch 4g is that your phone or do you have the international version? If you flashed the wrong kernel it could cause problems.
Yes it's an Epic touch 4g from sprint.
EDIT: Uninstalled Kies, reinstalled Kies, restarted computer, still no kind of recognition of my phone in any state (powered off, at "Firmware upgrade encountered" screen it boots into, or in download mode). Starting to get nervous, I used to at least hear a sound when plugging my phone into my comp. It is like there is nothing on the other end of the USB cable.
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
OperationIvy85 said:
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
Click to expand...
Click to collapse
Try to reset your binary counter with a usb jig.
you could try and download the drivers again from here and see if it then connects
http://modem-techno.blogspot.com/2010/09/epic-4g-usb-driver-download.html
I also had a similar problem once with an old i9000 and what worked was doing this and then connecting the phone first and then opening Odin.For some reason opening Odin first and connecting wouldnt find the phone.If nothing else works try wipeing the bin counter with the jig and send it back.Youll have to say that kies crashed while updating on Win7 64bits.Samsung know that before the September 30th kies update kies wasnt fully functional with 64bit drivers and they had a few phones replaced under warranty because of crashing kies updates on Win7 64bits.
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
The good thing is that your bin counter is at "0" again.The Kies thing is the real deal as there are also posts here on XDA of the same thing happening.I also know its true from first hand experience as it has happened to me and when i told them about the Win7 64bit driver problem (this happened to me a couple of months back too) they had no option but to accept it cos they know its true.Also i offered to e-mail links from forums with other complaints from users on 64bit PCs but they didnt even dought my storey and in 4 days it was back in my hand.I told them that when the update finalized the programe froze and the phone rebooted to a black screen.Had to pull the battery cos it appeared to be dead and refused to reboot again.Important to say that you where on Kies prior to the update I mentioned.Ived update to the latest Kies and it works fine now on my Win7 64bit so be carefull there that date is important
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
OperationIvy85 said:
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
Click to expand...
Click to collapse
Kies via to its Sep 30th update was not fully compatable with 64bits and gave a lot of problems to a lot of people.I had a few problems with it when I got a new laptop (HP Win7 64bit) so started searching the web for solutions and found that kies was designed mainly to support the windowsXP versions 32bit and had caused Samsung to accept various repairs under warranty because of crashing Kies updates mainly on android running phones.For some reason Bada didnt seam to affected.Maybe cos there arnt to many around like android.In the 4G forum there is post from someone who has bricked their phone using Kies to update and a reply from another with the same problem.Take it into where you bought it to start with and if its not there problem then they might send it back to Samsung for you.All you need to say is that you where updating your firmware via kies and on completion it froze and the phone booted to a black screen like mine did.You had to pull the battery and restart your PC to close Kies cos it wouldnt close or minimize or anything.Tell them that you searched on the net for possible causes and found what i told you about Kies and since you have a Win7 64bits PC then thats most likely to have been the cause.Your bin counter is at 0 so there is no way they can counter-attack your story.
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Who told you that the exclamation point means you voided your warranty?
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The sign you see means that your phone is semi-bricked and that you needed a jig to force the phone to boot into download mode.You can buy one on ebay for a couple of bucks.Best you do cos it could may mean that your warranty is void.Let me explain,no one can actually say that your warranty is void because of this sign but being only "semi-bricked" the service centre are still able to enter the phone and see the bin counter.So if you semi-bricked flashing a non official firmware or you have done so earlier and your bin counter is not at 0 then YES your warranty is void.Semi-brick is not so bad as you can normally fix it yourself but Hard-brick is a dead phone and you gotta pay for a jtag .In your case buy a jig force the phone into download mode and re-flash it yourself.You shouldnt need to go anywhere.Semi-bricking is something you save yourself.Just wait till the jig arrives in the mail.
EDIT:there have been posts of people pulling the battery for 10min and re-trying and it has booted to download.They say they have had to do so 4 or 5 times for it to finally work but if youve got time on your hands then give it a try.
---------- Post added at 04:48 PM ---------- Previous post was at 04:22 PM ----------
OperationIvy85 said:
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
Click to expand...
Click to collapse
Well at least you got a phone now hope they didnt charge to much!!!!Good on ya mate
Update on my issue....
It turns out the problem is because I tried to flash an I1900 firmware while my phone is a G variant (I900G).
After using the right firmware, it worked.
OperationIvy85 said:
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
Click to expand...
Click to collapse
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
sfoksn said:
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
Click to expand...
Click to collapse
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
aceofclubs said:
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yeah, I got stuck while flashing 2.3.5 Gingerbread... Yeah I think it has a new bootloader, as I remember Odin updating the bootloader section before messing up.
Is there any way I can get the USB jig to work? My phone is no longer recognized by the USB anymore so I can't even flash another bootloader or anything.
Is there anythign I could do to make the USB jig work without connecting it to the computer?
Can you get into download mode using the buttons?
Volume down+home+power
If so try and flash another Rom from intratechs thread to get back to stock.
If that works you can try again.
Sent from my GT-I9100 using XDA App
Here's the story - purchased a soft-bricked Vibrant for $50. It booted up to the phone - ! - computer screen. Took it home, used One-Click Unboot. Took a few tries, drivers, and USB ports, but eventually it worked. After that, it was just turning on and hanging at the Vibrant screen. Going along with other threads, I tried flashing to stock from ODIN. I followed this guide: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
ODIN was finicky but eventually recognized my phone on COM Port 4. With the appropriate PIT and PDA loaded, I clicked Start and all the files uploaded. The phone restarts and.. stuck at Vibrant again. ODIN even lights up with a green PASS but I've let the phone sit and sit and it never gets anywhere.
Is this thing a total dud? Granted I'm trying to boot without a SIM card in it but I didn't think that would make a difference. Please, someone help. I'm stumped and annoyed.
Tried following this guide as well. Same problem. I'm definitely frustrated.
http://forum.cyanogenmod.com/topic/6998-howto-recover-from-a-soft-brick-on-your-vibrant/
I'm having this same problem, any info would be nice. I've actually tried several different guides online and none have worked for me, I can never get past the bootloader screen.
Also, I have been unable to find the file to install CWR, so I have no backup. I know my phone isn't bricked because I can install different modems and such but nothing is working to get it back up and working.
Make sure you've got the right files. Grab the ones out of the noob guide just to be sure
Sent from my SGH-T959 using XDA App
Yep, same problem. I can't seem to get into recovery either. Or connect to ADB to reboot into recovery. I'm tearing my damn hair out over this.
I tried ODIN flashing the Froyo No-Brick ROM for the hell of it cuz I read it fixed this issue as a last ditch for some people. No dice. Boots to the Vibrant screen for a second, then Vibrant switches to Galaxy S and it just sits there.
If no one has any ideas soon, I'm just going to say screw it. Pretty bummed - I've been on a G1 forever and was excited to use an Android phone that doesn't totally suck.
Wrrryyy said:
I tried ODIN flashing the Froyo No-Brick ROM for the hell of it cuz I read it fixed this issue as a last ditch for some people. No dice. Boots to the Vibrant screen for a second, then Vibrant switches to Galaxy S and it just sits there.
If no one has any ideas soon, I'm just going to say screw it. Pretty bummed - I've been on a G1 forever and was excited to use an Android phone that doesn't totally suck.
Click to expand...
Click to collapse
Go into the Developers section and look at the 2nd or 3rd post "Bay_wolf's AIO Vibrant Toolbox 2.5" . Download that into your computer and run 'Flash to Stock'.
That should help you get to where you need to go. Try the one click method first.
PM sent to Wrrryyy
Thanks for the advice guys, but still no go. Installed the drivers from the toolkit but all I can still do is use ODIN to try and flash stock. Results are exactly the same. Reboot into recovery still isn't working - I have a feeling USB debugging was not enabled on this phone before any of this happened so I'm screwed in that respect.
Keep trying, it's not bricked, one combination of files has to work for you.
Well there's only so many files I can apparently try. I've tried JFD, JI6, Eugene No-Brick.. Is there anything else I should trying flashing with ODIN?
Take out your sim card and microSD card. Download the appropriate stock JFD files, make sure you check repartition; you should be fine. USB debugging box not being checked before has nothing to do with your problem now. I believe either your partition or your bootloasder is screwy. Follow my steps above and you should be ok.
In fact, look at this and follow it to the T.
http://forum.xda-developers.com/showthread.php?t=848737
That's what I've tried probably 30 times by now. Repartition checked and unchecked. And yeah I know USB debugging doesn't have to do with ODIN, it's why I'm assuming I can't get ADB to recognize the phone so I could at least try "adb reboot recovery".
Outside of flashing JFD, JI6, or Eugene's No-Brick, is there anything else I could try?
Wrrryyy said:
That's what I've tried probably 30 times by now. Repartition checked and unchecked. And yeah I know USB debugging doesn't have to do with ODIN, it's why I'm assuming I can't get ADB to recognize the phone so I could at least try "adb reboot recovery".
Outside of flashing JFD, JI6, or Eugene's No-Brick, is there anything else I could try?
Click to expand...
Click to collapse
Try eBay
Sent from my T959 using XDA App
I'm in the same boat, same scenario with constant boot loop. This is my girlfriends phone too
IA-32e said:
I'm in the same boat, same scenario with constant boot loop. This is my girlfriends phone too
Click to expand...
Click to collapse
Look for a new girlfriend on ebay
djquick said:
Look for a new girlfriend on ebay
Click to expand...
Click to collapse
Haha no Craigslist I ended up having her file a claim and send it back. I must have borked the bootloader somehow cause now it wont turn on at all. Thank God for insurance. She's SUPER pissed though.
Compared to my Galaxy SII this phone is very finicky and ODIN is even more unreliable than normal. Never hard bricked a device before.
Picked up a G2 practically new for $100. Loving it so far - rooting process was a snap.
F this Vibrant. Back to Craigslist it goes. Still open to ideas before it's gone so I can attempt to get my money back, lol.
Wrrryyy said:
Picked up a G2 practically new for $100. Loving it so far - rooting process was a snap.
F this Vibrant. Back to Craigslist it goes. Still open to ideas before it's gone so I can attempt to get my money back, lol.
Click to expand...
Click to collapse
The only thing I see that will fix the Vibrant when it's in this state is JTAG brick repair for $50. This is after spending 12 hours searching and attempting to ODIN different stock firmwares till I finally hard bricked it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-4g-vibrant-4g-jtag-brick-repair/
Yeah I was considering this. I e-mailed the guy asking if it was an appropriate fix. I figure, if the service takes care of a hard brick, it can certainly take care of a soft brick. Maybe I'll do that to keep it around as a back-up phone. Thanks for the replies, everyone.
Early yesterday I launched Kies and hit the update firmware option from the tools menu to see if the alleged ICS update was available for my phone. It appeared it was with, a message promoting that it would clear all personal data from the phone, which I then selected cancel so I could do a backup of pictures/videos on the phones internal SD.
Without doing any sort of backup yet I shutdown the phone, only for it to freeze on the shutting down screen. After 20 mins I pulled the battery and let the phone cool down since it had gotten warm trying to shut itself down. After replacing the battery and turning on it was stuck in a bootloop with only the SGS2 logo, never reaching the ATT logo.
At that point I came to XDA, which I frequently browse but have yet to root, and began reading and searching everything I could find.
Hours later I decided to attempt to flash the stock firmware from sammobile.com using Odin. The flash took a long time and I assume never completed. I left it overnight since I didnt want to unplug it mid-flash. Checking back in the morning the phone is black, Odin says failed/disconnected, and I find the battery completely drained. I charged it for a while then tried turning it back on and got the yellow triangle "firmware upgrade encountered an issue..." screen.
Now i'm attempting once more to flash the firmware but again it has been 30 mins on Sbl.bin. I've had a hard time finding stock firmware in different varieties with working links, so to not increase the flash counter in the event I ultimately have to send it in for repair.
Any suggestions on where to go from here? I've followed every direction I can find for flashing stock firmware and nothing has been successful.
Glad to help if I can. Please tell me exactly what package you flashed from sammobile, with a link if possible.
You should change the title of the thread.... I killed my phone. LOL!
http://forum.xda-developers.com/showthread.php?t=1313659
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
Try this.....
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
Download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package from Hotfile. Extract the contents of the zip file to a directory on your hard disk drive. This is a One-Click version of Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package plus stock modem from the development forum. (Contains stock zImage, factoryfs.img with root, and modem.bin.)
Start the Odin3 One-Click Downloader program by double clicking on "I777UCKH7 OCD With Root.exe".
Now Enter Download Mode:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
In Odin, the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]. The number could be different.
Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot.
Unplug the usb cable from you phone after it boots up. Success. You're Rooted.
SOURCE: http://forum.xda-developers.com/showthread.php?t=1311081
creepyncrawly would know better. It's his thread.
Download the file from below post to go back to stock I777UCKH7. Follow the instruction written in the post. I just had the same a while ago using the mobile odin to go back to stock. Got stuck on Samsung Galaxy SII screen. Pulled the battery and then followed the instructions from this post. I selected the one that says no BL 'I777UCKH7 OCD No BL'.
http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
Once you are done with the stock restore. To upgrade to ICS LE5 follow the instructions from below post. Make sure you read and follow the instructions as mentioned in the post.
http://forum.xda-developers.com/showpost.php?p=27707563&postcount=83
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
You downloaded I777UCKH7_I777ATTKH7_ATT and extracted I777UCKH7-rev02-home-low-cl503881.tar.md5?
Flashed the .tar.md5 in the pda slot?
What version of Odin are you using?
Edit: You're getting lots of advice here. Let me know if you need me to help troubleshoot your issues.
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
nett3 said:
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
Click to expand...
Click to collapse
Try using another micro usb wire if you have one. If not then get one from radioshack or bestbuy. I had the almost similar issue on my captivate with the original USB cable. Then I got a Rocketfish one from bestbuy and it worked like a charm.
I'm sure you might have already done this. Make sure you first run the ODIN and then put your phone in download mode.
krips your a genius!
The one click is now working thanks to the suggestion to pay attention to order of operations. I must have never plugged the phone in AFTER starting the one click. This was easily overlooked when I've been switching the phone between 2 PCs and 3 micro usb cables.
I now have a progress bar and have had made more progress than in the last 24 hours. Even after searching I did not find this solution, even though it's stated in the directions and it seems trivial, maybe it should be emphasized the one click needs to phone plugged in after it's running.
Thanks again. I'll update this post when it's back to being a phone again.
PS. BROKKANIC: you were right, if I didn't kill my phone then I sure was the impeding factor in its recovery.
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Is this a bootloader problem, kernel problem, or something else?
LOL!. Glad you got it working.
nett3 said:
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Click to expand...
Click to collapse
Flash back to stock first.
BROKKANIC said:
LOL!. Glad you got it working.
Flash back to stock first.
Click to expand...
Click to collapse
I believe that what I have been doing. I ran I777UCKH7 OCD With Root.exe, which resulted in bootloop, then ran I777UCKH7-CL503881-No-BL.exe, which also resulted in bootloop. Both completed successfully, but resulted in the same bootloop.
Odin appears unable to flash anything without it being a one click. I'm trying to flash Siyah-v2.6.14-att.tar. But Odin hangs at zImage with no progress bar.
What operating system you using: if windows 7 are you running as administrator ?
hd779 said:
What operating system you using: if windows 7 are you running as administrator ?
Click to expand...
Click to collapse
I've resorted to my WinXP laptop which has been more successful than my Win7 desktop. On the Win7 attempts everything is run as admin, but has many time bluescreened and hard reset the whole PC when attempting to flash anything with Odin. Maybe a separate issue, maybe not. But the XP machine is atleast successfully flashing the Odin one clicks.
Update: Odin standalone (non-one click) appears to be unable to flash anything, it will only hang when trying to write. One click Oden packages seem to work. Is there a one click with full stock sbl, param, kernel, etc?
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
gefox4vn said:
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
Click to expand...
Click to collapse
I haven't flashed a package with a bootloader yet. The only ones that work for me are Odin one click packages, and the two I've tried do not have bootloaders. I've been looking for one WITH a bootloader but no such luck yet, since maybe that would solve the problem.
The guide/link you've suggested will not work for me at this time. I do not have the ability to boot into any andriod OS. The only capability my phone has is executing Odin one click packages for some reason, even Oden standalone firmware flashes do not work.
I had a similar issue...I eventually got mine stuck at the ATT droplets....
Finally I flashed back to 2.3.4 stock....did the ota...then upgraded to ICS.
Its all on my work laptop so I wont be able to post any specific files or their names until monday...
Good luck!
Once your phone gets to the boot screen try to get into stock 3e (both volume buttons + power till 2nd SGSII splash screen) recovery and do a factory reset. Should boot after that. Good luck.
Sent from my SAMSUNG-SGH-I777 using xda premium
Why not try a custom ics rom? What else do you have to lose? Staying stock is overrated anyways. You may also have an antivirus stopping Odin but I doubt it. Just turn off your antivirus and try.
Sent from my SGH-I777 using xda premium
I installed SafeStrap 3.70 and tried to install RLS12 (on MK2). Things did not go so well. It booted to a black screen. Figured I would just ODIN back to stock and now my phone is really unhappy.
I tried flashing both of the firmwares from here (full did not work so I tried no-wipe):
http://forum.xda-developers.com/showthread.php?t=2578209&highlight=mk2
I can boot into download mode but not recovery. When I first flash a ROM via ODIN the phone will show the Samsung logo and even get to the Verizon splash screen. Problem is it will power off after a minute or so. If the phone is connected via the USB cable the charging battery screen appears. If I try to go into recovery it just powers off (verified by plugging in USB cable and getting charging screen).
One thing I have noticed is that even after flashing with Odin the Samsung custom splash screen still shows up. Usually that goes away.
I am open to any and all suggestions. My last two things to try is going through Kies Revovery. Next it to try downloading a firmware from sammobile.com.
diaftia said:
I installed SafeStrap 3.70 and tried to install RLS12 (on MK2). Things did not go so well. It booted to a black screen. Figured I would just ODIN back to stock and now my phone is really unhappy.
I tried flashing both of the firmwares from here (full did not work so I tried no-wipe):
http://forum.xda-developers.com/showthread.php?t=2578209&highlight=mk2
I can boot into download mode but not recovery. When I first flash a ROM via ODIN the phone will show the Samsung logo and even get to the Verizon splash screen. Problem is it will power off after a minute or so. If the phone is connected via the USB cable the charging battery screen appears. If I try to go into recovery it just powers off (verified by plugging in USB cable and getting charging screen).
One thing I have noticed is that even after flashing with Odin the Samsung custom splash screen still shows up. Usually that goes away.
I am open to any and all suggestions. My last two things to try is going through Kies Revovery. Next it to try downloading a firmware from sammobile.com.
Click to expand...
Click to collapse
I've seen someone else with this problem..
Think they took the battery out for like 5-10 minutes then they were able to boot into recovery then did a factory reset and cleared Cache then that either fixed it or they Odin back. Have you tried that? Sounds like you know what you're doing. I had to do that with my s4 as well after running into some issues
Edit:
Is this all on your stock slot or is hd12 on a rom slot???
Reason I ask is I had this happen to me and even after full Wipe in Odin my s4 was doing same thing as yours it sounds and mine was all on stock slot. My phone was really pissed at me.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Mistertac said:
I've seen someone else with this problem..
Think they took the battery out for like 5-10 minutes then they were able to boot into recovery then did a factory reset and cleared Cache then that either fixed it or they Odin back. Have you tried that? Sounds like you know what you're doing. I had to do that with my s4 as well after running into some issues
Edit:
Is this all on your stock slot or is hd12 on a rom slot???
Reason I ask is I had this happen to me and even after full Wipe in Odin my s4 was doing same thing as yours it sounds and mine was all on stock slot. My phone was really pissed at me.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Click to expand...
Click to collapse
Yes, this is in the stock slot. I had been running in the stock slot since RLS8(9?) without any problems but something has definitely changed.
Some good news! I went to bed at around 12:30 with Kies left running. It had stated the download process of the restore. When I checked on it this morning I had a red light on the phone which I had not had before (charging indicator). I unplugged the phone and powered it on. Low and behold I got a setup wizard. Looks like Keis does something that Odin does not. So when in doubt restore the stock image with Keis if you are stuck. BTW, when doing that I did the "Firmware Upgrade and Initialization" method. It asks for the model # and it is case sensitive for some reason. It took "SCH-I545" but was not taking "sch-i545".
diaftia said:
Yes, this is in the stock slot. I had been running in the stock slot since RLS8(9?) without any problems but something has definitely changed.
Some good news! I went to bed at around 12:30 with Kies left running. It had stated the download process of the restore. When I checked on it this morning I had a red light on the phone which I had not had before (charging indicator). I unplugged the phone and powered it on. Low and behold I got a setup wizard. Looks like Keis does something that Odin does not. So when in doubt restore the stock image with Keis if you are stuck. BTW, when doing that I did the "Firmware Upgrade and Initialization" method. It asks for the model # and it is case sensitive for some reason. It took "SCH-I545" but was not taking "sch-i545".
Click to expand...
Click to collapse
Well that's good news. Yea like I said that happened to me as well... I just didn't use kies. But looks like you're back up and running so you're good.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Hey guys,
I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)
I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
ozo012 said:
Hey guys,
I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)
I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
Click to expand...
Click to collapse
Here's an older post with links that might be helpful ( http://forum.xda-developers.com/showthread.php?p=57944591 ).
Make sure you're using the pit file when flashing the appropriate firmware in Odin.
Some common issues with Odin also are to make sure you're using a USB 2.0 port on your computer and use the phone's original USB cable or a good quality one if you don't have the original any longer. Also run Odin with Administrative privileges, make sure that Kies is not running in the background because it interferes with ODIN, and disable antivirus programs when running Odin.
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.
RIP Note II it was nice knowing you.
ozo012 said:
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.
RIP Note II it was nice knowing you.
Click to expand...
Click to collapse
Man... that sucks! I wonder if it was actually Odin, or if the EMMC chip just died. Either way, it doesn't really matter now. RIP Note 2.