Related
Okay so i ditched the stock rom for axura 1.0 and am using it...but i changed my mind and want to go back to stock...but never made a backup of my stock rom in clockwork like a moron. Now i tried Odin and here is the weird part it detects my phone in recovery mode...but not download mode so now im stuck trying to get back to stock vibrant 2.1...any suggestions?
Thank You
Start odin first, then hold the volume keys, then insert the usb cable
This always works for me when odin doesn't detect my phone
Sent from my SGH-T959 using XDA App
S4BRE2121 said:
Start odin first, then hold the volume keys, then insert the usb cable
This always works for me when odin doesn't detect my phone
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I Have the same problem I did all the steps even tried to do the step you told us to. Still didnt work. what should i do?
Sometimes reinstalling drivers works for me when Odin doesn't see it.
cgol92 said:
Okay so i ditched the stock rom for axura 1.0 and am using it...but i changed my mind and want to go back to stock...but never made a backup of my stock rom in clockwork like a moron. Now i tried Odin and here is the weird part it detects my phone in recovery mode...but not download mode so now im stuck trying to get back to stock vibrant 2.1...any suggestions?
Thank You
Click to expand...
Click to collapse
This is the easiest way. Download Terminal from Market and enter SU (gives you root access) and then type reboot download
Your phone will reboot into Download mode
i tried the su reboot download and it didnt detect it and i reinstalled the drvers too no luck cuz it says usb device not reconized when in download mode but when in recovery or normal mode it is detected no issue
Here's how I do it if everything else fails. Have ODIN v1.3 opened up first. Next, make sure phone is in debug mode and make sure its checked . Next,while phone still connected to pc, remove back cover and pull battery out. Before inserting the battery back in, hold the phone side ways while pressing the volume up/down at the same time now insert the battery. Your screen should now display yellow big letters -
Download Mode - Do not turn off target.
cgol92 said:
i tried the su reboot download and it didnt detect it and i reinstalled the drvers too no luck cuz it says usb device not reconized when in download mode but when in recovery or normal mode it is detected no issue
Click to expand...
Click to collapse
Read the Vibrant Bible here http://forum.xda-developers.com/showthread.php?t=771111 . Read the top 2 sections --Useful links and Odin.
By the way, is your phone rooted?
Have you tried using a different USB port? Sometimes that helps.
yes the phone is rooted and i tried using odin v1.0 and 1.7 ill try 1.3 idk if it makes a difference
One method I've read on the boards is to flash "Eugene's froyo that doesnt' Brick". Of course that is an Odin file so...we need to get Odin working for you. Like icandy said, try a different USB port and see if that works. If nothing else also post in Master's Axura thread and ask him/her what the best method of downgrading to 2.1 is. I'm not sure if you'd have to flash Eugene's Kernel Back Support or not. I know this isn't too helpful but hopefully it'll give you a few ideas.
~SB
so i was reflashing to cm7 #71 last night and i always do a clean install by formating boot system and cache. after i formated the 3 idk why but i let the phone shut off.
now i am stuck at just the vibrant logo. i have tried getting into cwm and download mode with no success. i plugged it in to the computer to see if i can at least access to adb no help there either.
does any body have a solution to this on this?
Um, first question; why do you format /boot? No where in any directions do they tell you to format that as that's where you're kernel is located.
And, if you can't access dl mode with the hardware buttons, why didn't you headed the large red letters telling you not to use CM7 if you can't access dl mode without the hardware buttons?
Have.you tried vol+ vol- and then USB? If you're running gb bootloaders (which you shouldn't be), then I don't know the button combo.
But the only way to recover is by geting into dl mode and Odin back to jfd.
Sent from my SGH-T959 using XDA App
I always format/ boot. Its a cleaner install and have no problems going from multiple kernel changes. I could get into download using button combo before I flashed. Now I cant
avengethis1 said:
I always format/ boot. Its a cleaner install and have no problems going from multiple kernel changes. I could get into download using button combo before I flashed. Now I cant
Click to expand...
Click to collapse
try this always works. take battery out phone, plug in usb to pc and phone hold vol + and -, and insert battery at same time, should put u in download mode.
Assuming u have a froyo bootloader
1) Power down ur phone
2) hold volume up + volume down then plug ur phone to a PC or laptop....don't let go of two volume buttons...
3) should b in download mode...
Sent from my MB860 using XDA App
ive tried every combo i can think of. still just sits at vibrant. was able to make a jig that put it into DLM but then was getting reconized at all by my computer even with all the correct drivers..... i think i actually might be outta luck
You could get a JIG which will automaticly put it into download mode. It can be found here http://www.amazon.com/gp/aw/d/B0053H73JQ/ref=redir_mdp_mobile/188-7446597-2980456
Sent from my SGH-T959 using XDA App
@halo
yea i was able to make one for 2 dollars and it works beautifully just now i cant get the computer to reconize the phone. i have the right drivers loaded but its seeing it as some crazy junk
edit: well got all the drivers working. made a new better jig and was able to get odin to reconize it.
didnt flash though. seemed jammed up. so i took it off of odin which left the phone in the phone to computer screen( PROGRESS) plugged it back into the computer. odin saw it and presto! back up and running on JFD
Ditto
I have done the same thing! Sent you a pm... Let me know what driver config you had to use to get it working.
Thanks!
I was flashing from MIUI 1.9 to MIUI ICS in CWM and all seemed well until upon boot it hung on the MIUI bootup screen. After waiting about 15 minutes I figured I would simply ODIN back to stock and try again as I normally do when I have a problem flashing. In ODIN however I was unable to make it past the boot.inf stage of the flashing. Stupidly I unplugged the usb cable mid flash and tried again, and again same result, it would hang at boot.inf. After trying a couple different stock ODIN files the phone will not turn on at all. Even if I pull the battery and connect the phone to the pc I cannot boot into download mode. When I connect to the wall charger the battery screen does not come on either.
Strangely if I press the power button on the phone with the phone connected to the pc, windows will make the sound of a usb device being connected, however, if I release the power button it makes the sound of a usb device being disconnected. ODIN does not seem to be recognizing my phone anymore since I haven't been able to boot into download mode.
I've bought a usb jib hoping this would solve the problem but it hasn't seemed to work. Maybe I'm doing something wrong.
Please someone help me get my phone up and running again. I've flashed numerous roms before and had trouble but nothing as serious as this.
Try reading up on Droidstyles Guide . Its in General section .
Sent from my SCH-I500 using xda app-developers app
Thanks for that. I went through his guide but unfortunately I think my problem is a little more serious. My phone will not turn on at all. I cannot boot into CWM, download mode or boot normally. The screen just remains black. It doesn't show up as a recognized device in windows but when I connect the usb cable it makes a sound of it being connected.
If any has any ideas on things I could try I would be really grateful. I bought my phone out of contract and can't really afford to buy a new one right now.
iztel said:
Thanks for that. I went through his guide but unfortunately I think my problem is a little more serious. My phone will not turn on at all. I cannot boot into CWM, download mode or boot normally. The screen just remains black. It doesn't show up as a recognized device in windows but when I connect the usb cable it makes a sound of it being connected.
If any has any ideas on things I could try I would be really grateful. I bought my phone out of contract and can't really afford to buy a new one right now.
Click to expand...
Click to collapse
Can you "3 finger" into recovery ?
Sent from my SCH-I500 using xda app-developers app
No, when I try to use the 3 buttons to boot into recovery the screen stays black.
Another strange thing it's doing is when I connect the phone to my Mac with the SD card in the phone the Mac will continuously popup a window that asks whether I want to connect the usb device to the Mac or my virtual machine. It flashes so fast I'm unable to click either option. If I connect the phone without the SD card in this menu never comes up but I'm still unable to boot into download mode.
Hmm....I've never heard this before...have you tried plugging phone charger in ( wall outlet ) and let it charge 8 full hours
Sent from my SCH-I500 using xda app-developers app
You say you bought " out of contract", from a private seller ? No warranty?
Sent from my SCH-I500 using xda app-developers app
I charged it from the wall charger overnight still no luck. Yeah, I bought it a year and a half ago used from ebay. I think it's really strange too. I've had plenty of hiccups flashing roms before but it's never been something ODIN couldn't fix and I'd at least be able to get into download mode.
I think you are going to have to use UnbrickableMod.
Thanks MM. I bit the bullet and bought a used Galaxy S II. I may still try that unbrickable mod so I can give my Fassy to my mom who's overdue for a smartphone. I've never used a soldering iron though and not too certain how successful I'll be.
iztel said:
Thanks MM. I bit the bullet and bought a used Galaxy S II. I may still try that unbrickable mod so I can give my Fassy to my mom who's overdue for a smartphone. I've never used a soldering iron though and not too certain how successful I'll be.
Click to expand...
Click to collapse
Have you tried the wall plug trick?
I had been running a Fascinate rom on a Showcase for almost a year & the same thing happened to me. Initially, the battery had run completely down and after full charge, I had nothing but bootloops. At first I could connect via odin, but could not complete flash.
After messing with it & yanking out the cable as you did, I had same issue, blank screen, pc would beep but that was it, pc/odin would not recognize or show the comm port. I would get unknown device.
Ultimately, I successfully repartitioned & odined a stock Fascinate Froyo EB01 rom by doing several things -- not sure which worked, but perhaps might work for you rather than soldering
First, I fully charged an oem battery using a spare battery charger (not in the fassy)
After charge, I put the batt in the fasc & plugged the fasc in to the wall charger while holding down the volume button & got the download mode to show up.
I left batt in when I unplugged from wall & the download mode stuck.
Odin still didnt recognize on my laptop, so I tried 3 other machines till I Odin finally saw the fascinate, at which point I odined Froyo with .pit & repartitioning as my starting point, then clockworked & rooted etc. I think I left battery in during the flash, then reflashed later in download mode with battery out.
I was also successful using heimdall a few times, when another pc wasn't available & odin wasn't playing nice. Was very odd, as 2 of those laptops ALWAYS worked fine with odin & the fascinated showcase before. Now they still won't recognize, but I can easily odin if I try diff computers --- some windows 7 some xp & some vista.
Magickly said:
Have you tried the wall plug trick?
I had been running a Fascinate rom on a Showcase for almost a year & the same thing happened to me. Initially, the battery had run completely down and after full charge, I had nothing but bootloops. At first I could connect via odin, but could not complete flash.
After messing with it & yanking out the cable as you did, I had same issue, blank screen, pc would beep but that was it, pc/odin would not recognize or show the comm port. I would get unknown device.
Ultimately, I successfully repartitioned & odined a stock Fascinate Froyo EB01 rom by doing several things -- not sure which worked, but perhaps might work for you rather than soldering
First, I fully charged an oem battery using a spare battery charger (not in the fassy)
After charge, I put the batt in the fasc & plugged the fasc in to the wall charger while holding down the volume button & got the download mode to show up.
I left batt in when I unplugged from wall & the download mode stuck.
Odin still didnt recognize on my laptop, so I tried 3 other machines till I Odin finally saw the fascinate, at which point I odined Froyo with .pit & repartitioning as my starting point, then clockworked & rooted etc. I think I left battery in during the flash, then reflashed later in download mode with battery out.
I was also successful using heimdall a few times, when another pc wasn't available & odin wasn't playing nice. Was very odd, as 2 of those laptops ALWAYS worked fine with odin & the fascinated showcase before. Now they still won't recognize, but I can easily odin if I try diff computers --- some windows 7 some xp & some vista.
Click to expand...
Click to collapse
I had the same issue. I think it had to do with the battery being too low. I think that ODIN could have a check in place to allow only to flash if the battery is not clos to low in case things go wrong. I had a second fully charged battery and when i read the above post, i changed the battery across and it set it to download and ODIN eventually detected it. Thanks for the help guys.
I have a similar problem, I was on PA JB rom 2.18, and I decided to flash latest devil kernel [1.5.2? or something like that]
so then it would just boot into devil recovery. and that's all. Tried to flash pa rom over it [to get stock recovery back] but it failed. also it had lots of errors about mounting.
So I did advanced restore, and chose to restore boot from other JB backup. This just made it worse, bootlooping into an android recovery with a "!" triangle, then immediately rebooting, over and over again..
So I put into download mode, and heimdall a boot.img extracted from the JB rom [paranoid android], and it still didn't work right.
So then I heimdall'ed the atlas.2.2.pit, thinking the partition was screwed. Then I was booted into cwm 6.x! So I thought I was out of the woods, and wiped, then flashed PA 2.18 jb rom, and then rebooted.. and then I had no samsung logo bootloop. I could tell cuz it was dark, and I could see the backlight coming on and off. on, off... on... off... endlessly.
I tried download mode, and it didn't work. That's when I got scared.. I tried it again, nothing. just the black [very dim black, because of super amoled technology] screen, coming on and off..
So I finally tried taking the battery out, and then it went into download mode!
But I still cannot figure out why it will not let me flash any rom. I'm gonna have to boot into windows and odin back to EH03.
Good thing I have a 3-4 day old backup.
So, do not use devil kernel unless you want a softbrick.
mvmacd said:
I have a similar problem, I was on PA JB rom 2.18, and I decided to flash latest devil kernel [1.5.2? or something like that]
so then it would just boot into devil recovery. and that's all. Tried to flash pa rom over it [to get stock recovery back] but it failed. also it had lots of errors about mounting.
So I did advanced restore, and chose to restore boot from other JB backup. This just made it worse, bootlooping into an android recovery with a "!" triangle, then immediately rebooting, over and over again..
So I put into download mode, and heimdall a boot.img extracted from the JB rom [paranoid android], and it still didn't work right.
So then I heimdall'ed the atlas.2.2.pit, thinking the partition was screwed. Then I was booted into cwm 6.x! So I thought I was out of the woods, and wiped, then flashed PA 2.18 jb rom, and then rebooted.. and then I had no samsung logo bootloop. I could tell cuz it was dark, and I could see the backlight coming on and off. on, off... on... off... endlessly.
I tried download mode, and it didn't work. That's when I got scared.. I tried it again, nothing. just the black [very dim black, because of super amoled technology] screen, coming on and off..
So I finally tried taking the battery out, and then it went into download mode!
But I still cannot figure out why it will not let me flash any rom. I'm gonna have to boot into windows and odin back to EH03.
Good thing I have a 3-4 day old backup.
So, do not use devil kernel unless you want a softbrick.
Click to expand...
Click to collapse
I think the problem is you used the wrong Devil... the latest is 1.6.1 and the older ones will not work with the new partition layout. Get it from http://rootaxbox.no-ip.org/derteufel/
Here is some FYI for you guys. If you are using a pc with a USB 2.0 or higher then it provides the power to go into download mode for Odin. That's why people say to remove the battery and then plug in the USB cable and hold the volume and power to go into download mode for odin. IF you are using a desktop then it's best to use one of the hardwired usb ports on the back of your pc, if it's a laptop then they are all hardwired to the motherboard. USB 2.0 and up all provide power through the usb port, therefore if you leave the battery in while Odin'ing it may not be a good outcome, this is just a suggestion.
netlagger said:
Here is some FYI for you guys. If you are using a pc with a USB 2.0 or higher then it provides the power to go into download mode for Odin. That's why people say to remove the battery and then plug in the USB cable and hold the volume and power to go into download mode for odin. IF you are using a desktop then it's best to use one of the hardwired usb ports on the back of your pc, if it's a laptop then they are all hardwired to the motherboard. USB 2.0 and up all provide power through the usb port, therefore if you leave the battery in while Odin'ing it may not be a good outcome, this is just a suggestion.
Click to expand...
Click to collapse
You are suggesting we leave the battery out while Odining? what good would that do?
mvmacd said:
You are suggesting we leave the battery out while Odining? what good would that do?
Click to expand...
Click to collapse
I always Odin without battery. Try it. Remove battery, connect to PC with Odin opened, hold volume down button for dl mode, and fash.
Sent from my SCH-I500 using xda premium
mezster said:
I always Odin without battery. Try it. Remove battery, connect to PC with Odin opened, hold volume down button for dl mode, and fash.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Yet again, I ask, what good would taking the battery out?
I'd have to set it and the cover down and put them back after Odin..
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
Yet again, I ask, what good would taking the battery out?
I'd have to set it and the cover down and put them back after Odin..
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It's probably just a precaution so you don't accidentally reboot the phone while flashing or something like that. Every guide I have read says to pull battery before using Odin so I do... and I haven't had any problems. I think it'll probably work fine with the battery in, but why bother taking the risk?
Crawshayi said:
It's probably just a precaution so you don't accidentally reboot the phone while flashing or something like that. Every guide I have read says to pull battery before using Odin so I do... and I haven't had any problems. I think it'll probably work fine with the battery in, but why bother taking the risk?
Click to expand...
Click to collapse
how would the battery cause the phone to reboot?
I have never Odin'd without the battery. And I never had any problems
I have a Samsung Galaxy S2 GT-I9100 that I recently rooted and when I rooted it it flashed a custom Kernel as well. Upon rebooting the phone, now my home button and back button soft key is not responding. I think I may have flashed a kernel from one of the Galaxy S2s that has the 4 soft keys along the bottom rather than the 2 soft keys and the home button, Whenever I try to flash anything through Odin now it says that a connection failure happens. If I put the phone into Download mode it is not recognized through Odin anymore either. Also, when I plug the phone into the USB of my computer and try to do anything with the phone through the USB it shuts it off and just shows the battery charging symbol. If I try to flash anything through recovery it says that Signature verification failed. I'm a bit stuck and I don't know what else to try.
kodyclarence said:
I have a Samsung Galaxy S2 GT-I9100 that I recently rooted and when I rooted it it flashed a custom Kernel as well. Upon rebooting the phone, now my home button and back button soft key is not responding. I think I may have flashed a kernel from one of the Galaxy S2s that has the 4 soft keys along the bottom rather than the 2 soft keys and the home button, Whenever I try to flash anything through Odin now it says that a connection failure happens. If I put the phone into Download mode it is not recognized through Odin anymore either. Also, when I plug the phone into the USB of my computer and try to do anything with the phone through the USB it shuts it off and just shows the battery charging symbol. If I try to flash anything through recovery it says that Signature verification failed. I'm a bit stuck and I don't know what else to try.
Click to expand...
Click to collapse
Try another usb port/usb cable/pc.
If it sees you phone, don't forget to close all kies applications (if you don't have kies, download it!)
kodyclarence said:
I have a Samsung Galaxy S2 GT-I9100 that I recently rooted and when I rooted it it flashed a custom Kernel as well. Upon rebooting the phone, now my home button and back button soft key is not responding. I think I may have flashed a kernel from one of the Galaxy S2s that has the 4 soft keys along the bottom rather than the 2 soft keys and the home button, Whenever I try to flash anything through Odin now it says that a connection failure happens. If I put the phone into Download mode it is not recognized through Odin anymore either. Also, when I plug the phone into the USB of my computer and try to do anything with the phone through the USB it shuts it off and just shows the battery charging symbol. If I try to flash anything through recovery it says that Signature verification failed. I'm a bit stuck and I don't know what else to try.
Click to expand...
Click to collapse
If you can acces recovery mode (Volume UP+Home+Power) you can save yourself:
-If you can't access the SD card by USB, try to remove your external SD card and connect it to PC through a card reader, if you don't have one, buy it because it's far cheaper than an new SGS2 (or 3)
-Download Phil'z kernel that suits your current ROM and copy it to your SD card
-Put SD card back into phone and flash this kernel (See post #3 of the above thread), depending on what kernel you have flashed, read the appropriate instructions (usually: Install Zip from SD Card > Choose Zip from SD card > select and apply)
-You are done :laugh:
BTW, can you provide a link to the kernel you flashed ?
Hope this helps
I have tried that. Everything I try to flash through recovery it says "signature failure" or something along those lines.
Sent from my HTC Acquire using xda app-developers app
kodyclarence said:
I have tried that. Everything I try to flash through recovery it says "signature failure" or something along those lines.
Sent from my HTC Acquire using xda app-developers app
Click to expand...
Click to collapse
Put your phone in download mode and flash philz kernel by downloading the tar and flashing through odin
kodyclarence said:
I have tried that. Everything I try to flash through recovery it says "signature failure" or something along those lines.
Sent from my HTC Acquire using xda app-developers app
Click to expand...
Click to collapse
Signature check error means that you are trying to flash a custom kernel (I may be wrong) on non rooted phone
Philz kernel could bypass this
Have you tried cwm flashable philz kernel ??
Envoyé depuis mon GT-I9100 avec Tapatalk
---------- Post added at 12:51 AM ---------- Previous post was at 12:50 AM ----------
xiFIL said:
Put your phone in download mode and flash philz kernel by downloading the tar and flashing through odin
Click to expand...
Click to collapse
He already said that download mode is not available
Envoyé depuis mon GT-I9100 avec Tapatalk
Download mode is available, but when I plug it into the USB port Odin won't recognize it. But all of the drivers are installed. I've tried to flash philz through Odin but it won't recognize my device as being plugged in unless the phone is actually booted into Android OS. Then when I try to flash it just shuts the phone off and pops up the battery charging image.
Sent from my HTC Acquire using xda app-developers app
AS Leech4 said what kernel did you flash?
kodyclarence said:
I have a Samsung Galaxy S2 GT-I9100 that I recently rooted and when I rooted it it flashed a custom Kernel as well. Upon rebooting the phone, now my home button and back button soft key is not responding. I think I may have flashed a kernel from one of the Galaxy S2s that has the 4 soft keys along the bottom rather than the 2 soft keys and the home button, Whenever I try to flash anything through Odin now it says that a connection failure happens. If I put the phone into Download mode it is not recognized through Odin anymore either. Also, when I plug the phone into the USB of my computer and try to do anything with the phone through the USB it shuts it off and just shows the battery charging symbol. If I try to flash anything through recovery it says that Signature verification failed. I'm a bit stuck and I don't know what else to try.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1294574
I used
CF-Root-SGS2_XX_XEO_LQP_-PROPER-v5.4-CWM5.tar
Sent from my HTC Acquire using xda app-developers app
And when it is in Download mode it says
Product Name: GT-i9100
Custom Binary Download: Yes (1 count)
Current Binary: Samsung Official
Sent from my HTC Acquire using xda app-developers app
kodyclarence said:
And when it is in Download mode it says
Product Name: GT-i9100
Custom Binary Download: Yes (1 count)
Current Binary: Samsung Official
Sent from my HTC Acquire using xda app-developers app
Click to expand...
Click to collapse
Regardless of what it says there, what does it say for model on the label under the battery?
ctomgee said:
Regardless of what it says there, what does it say for model on the label under the battery?
Click to expand...
Click to collapse
It says GT-I900.
But everything worked fine, then I flashed that file through ODIN and ever since the home button and the back button soft key wont recognize. So I'm pretty sure whatever I flashed was for the Galaxy S2 model with the four soft keys rather than just the two with a home button.
So flash another kernel for I9100.
Get it at xda tho.
Sent from the little guy
I've been trying. Odin won't recognize my device when in Download mode, when i boot into Android and try to do anything through USB it shuts down to the battery charging logo, through recovery I get "signature verification failure" all of these suggestions are helpful, but I have already tried them.
Sent from my HTC Acquire using xda app-developers app
kodyclarence said:
I've been trying. Odin won't recognize my device when in Download mode, when i boot into Android and try to do anything through USB it shuts down to the battery charging logo, through recovery I get "signature verification failure" all of these suggestions are helpful, but I have already tried them.
Sent from my HTC Acquire using xda app-developers app
Click to expand...
Click to collapse
Try keep phone and pc linked through USB cable and restart the phone in download mode.
and don't forget to close all kies process running on the background.
Try all usb ports, usb cable and / or another pc / laptop.
Sent from the little guy
Hi
Have u tried flashing another kernel through mobile-odin ?
I'm still new to this stuff but I think it should work for you.
If u want to try it look for the thread with same name dl it ..free version, you will also need another file in same thread called
MobileODIN_FlashKernel_I9100-v2.0 (in same thread further down)
you can dl them on pc, put on card install them try.
or try rom-customiser u should be able to flash a diff kernel or Rom without pc-odin or recovery mode.
Good luck
Peace
I tried keeping it connected and restarting it. I also tried stopping all Kies processes and that didn't work so I uninstalled it but kept the driver. That didn't work. So I tried reinstalling the drivers.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
kodyclarence said:
I tried keeping it connected and restarting it. I also tried stopping all Kies processes and that didn't work so I uninstalled it but kept the driver. That didn't work. So I tried reinstalling the drivers.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
So you can get to DL mode right?
And you're sure It's a I9100 Model.
- You've re-installed kies already, so we good there. If you've unistalled it, please re-install again & close all 4 kies applications running on background.
- Get a couple of USB cables (along with the original I9100's cable) and start trying them one by one on each USB port.
- Still don't work? Try it out on another PC, same drill.
- No luck? Try the same steps in "Windoze".
- If all above fail, try it all again.
You gotta make that PC see your device, it already did, so it can do it again.
Hey guys, I really need help with my situation. I've been looking all over the forums for 2days straight trying to find solutions to my problem. I have a galaxy s2 i777 and I had the sho-stock3 rom. Then I decided that I wanted to back up my rom, so I used rom manager to do it. that's when the problem started. when the phone tried restarting it was stuck where it says "galaxy s2" with the yellow triangle. I put it into download mode and tried to flash siyah kernel..it worked..but when I tried to reboot my phones says "firmware upgrade encountered an issue, please select recovery mode in kies and try again. of course kies wont let the phone connect. and yes all the drives are installed for my phone. now i'm just stuck trying to flash stock firmwares for the phone and the stock rom but it always fails in odin. please help me!!!!!
Hours76 said:
Hey guys, I really need help with my situation. I've been looking all over the forums for 2days straight trying to find solutions to my problem. I have a galaxy s2 i777 and I had the sho-stock3 rom. Then I decided that I wanted to back up my rom, so I used rom manager to do it. that's when the problem started. when the phone tried restarting it was stuck where it says "galaxy s2" with the yellow triangle. I put it into download mode and tried to flash siyah kernel..it worked..but when I tried to reboot my phones says "firmware upgrade encountered an issue, please select recovery mode in kies and try again. of course kies wont let the phone connect. and yes all the drives are installed for my phone. now i'm just stuck trying to flash stock firmwares for the phone and the stock rom but it always fails in odin. please help me!!!!!
Click to expand...
Click to collapse
Don't use rom manager again
Sent from my SGH-I777 using Tapatalk 4 Beta
Can you get in either cwm recovery or download mode?
Sent from my SGH-I777 using xda app-developers app
Teknodad1974 said:
Can you get in either cwm recovery or download mode?
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
yes i can get into download mode only by holding down on vol and plugging in the usb...no i cant get into cwm recovery
Try this page...
http://forum.xda-developers.com/showthread.php?t=1511906
Sent from my SGH-I777 using xda app-developers app
Teknodad1974 said:
Try this page...
http://forum.xda-developers.com/showthread.php?t=1511906
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
thank you, my phone is back again!!
Sweet enjoy your phone buddy!
Sent from my SGH-I777 using xda app-developers app
Hours76 said:
yes i can get into download mode only by holding down on vol and plugging in the usb...no i cant get into cwm recovery
Click to expand...
Click to collapse
this SAVED me...I couldn't get it into download mode for the life of me and that worked. I now have the correct i777 JB file (I accidentally flashed the wrong version). back in the game!
Help
sbello81 said:
this SAVED me...I couldn't get it into download mode for the life of me and that worked. I now have the correct i777 JB file (I accidentally flashed the wrong version). back in the game!
Click to expand...
Click to collapse
Hello
My friend just gave me I777 with this problem cause he bought a new phone, he couldn't tell me exactly when he got that "connect to kies". I never flashed anything or installed any rom's, I just want to get it back to life. Any solutions for me?
Fratula said:
Hello
My friend just gave me I777 with this problem cause he bought a new phone, he couldn't tell me exactly when he got that "connect to kies". I never flashed anything or installed any rom's, I just want to get it back to life. Any solutions for me?
Click to expand...
Click to collapse
Can you put the phone into download mode? I would assume the answer is yes if you still get the "connect to kies" message. Following are detailed instructions for getting into download mode.
Download Mode:
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
If the phone will go into download mode, you will need to use Odin desktop to flash the stock firmware. You should use the latest stock firmware. Go to the Download Repository and download Odin3 v1.85 from the link near the top of the page, and also download the latest stock firmware, "I777UCMD8 Stock Binaries (Android 4.1.2 Jelly Bean)" from near the bottom of the page. It's the next to last item. Download both to your Windows pc, and then follow the detailed instructions below to flash it onto your phone.
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.
3.) Shut the phone off.
4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
11.) When complete, you will get a PASS (or FAIL if unsuccessful).
The phone should boot up normally. If it does not, enter recovery (see instructions in the download mode section) and perform a wipe data/factory reset.