I was on Miui rom, but I wanted to go and try Simpley Honey, so I went to CWM and wiped everything like it said, and I accidently formated the boot too. Is this why I'm stuck at the screen? i tried everything` Odin,Heimdall,Aio toolbox and all drivers for vibrant,but pc dont recognize my phone and there are only show <unknown device>
PLEASEEEEEE HELP TO FIX MY VIBRANT
Couple of things to try.
First, if you want to Odin, then I usggest going into your device manager on your PC and uninstalling your drivers. Then reinstall them manually of with the Toolbox.
Second, (Rule #1-Always make a back up)- Hopefully you made a nandroid back up of your MIUI that you were on. If so, you should be able to restore that and then wipe properly.
Third, if you can get into Recovery and you don't have a back up, then try to flash a ROM (2.3.x or higher since you were on MIUI) and see if that gets you back up and running.
Pretty sure that if you wiped Boot.img your phone is still recoverable. It isn't like you wiped out the bootloader or anything. Those are not touchable from CWR, so don't fret that part.
i uninstalled all drivers then installed again but odin dont recognize my phone(unknown device) in download mode,and i can not acces to CWM(((
do uninstall those drivers again and just download and install samsung kies mini it will automatically recognize and install drivers for you.. hope this will help you...JFD by odin will be the best way after that...
NB:for future reference---
always remember two things before flashing any rom...
** do nandroid backup
** get back to stock by odin then proceed any rom you want...
Haha, I did this before (about 2 weeks ago). I just placed it in download mode, then flashed back to stock using ODIN.
I tried everything but pc dont recognize my vibrant(((
dont freak out man, like everybody has said you did not brick your phone. when you click format boot, you only wipe the boot media (the startup image/video). you're boot-loaders are still in tact. this is all about getting your pc to recognize your phone. try to connect on another computer and try different variations of connecting to the computers, try a different usb port. Once I thought I bricked my vibrant as in I couldn't get into download mode or anything. I stupidly unplugged it while it was installing factory.rfs on odin, I thought it was stuck. Nothing would come up with any button combo pressed. then nine hours later and a change of usb ports, I got it into download mode an odined to stock.
but ive already tried it in many computers and usb ports,but still no success(((
Related
Now that I have your attention, after a series of mistakes, I am stuck in recovery with a rom that won't flash, an sd card that won't mount and cwm recovery so I don't think I can use adb to move files. Also, no nandroids (learn from my mistakes children!)
I'm not used to samsung phones so I don't know if it is trying to flash the rom from internal memory or not but under mounts it says unmount /mnt/sdcard so I think that means its trying to flash from internal memory which I don't think is possible.
EDIT: Wait, now I just have the boot screen no recovery... HELP!
I see Sprint as your provider....is this to deal with a T-mobile Vibrant? Just asking...
Read about ODIN. It will get you right back to where you need to be.
http://forum.xda-developers.com/showthread.php?t=821625
Yes its a tmo vibrant (its my friends phone, luckily im bigger than him)
So after a couple hours of searching, I can get the phone into download mode, I have the right odin and software to go to stock, and supposedly the right drivers, but when I plug the phone in to get to download mode, my computer recognizes it, it goes into download mode, but odin doesn't see the phone(a box is supposed to go yellow?). The only thing I can think of is that I have the wrong drivers but my computer sees it just fine...
I think it's the phone not letting the computer get to it. I'm almost positive I have the right drivers but when I plug in the phone in download mode nothing happens in odin. Anyone have any ideas? Any help would be greatly appreciated.
Well, If you can get into recovery without CWM that is better Try the holding down the vol-up/down and hold the start/on button at the same time if it blinks on then off then on then off then release all buttons if that works you should see the recovery menu, if you have the rom in your internal sd card, then you can install by choosing install from sd card then choose select file next menu.
If not you may need to use
Get Odin going (version 1.7or newer) have the usb plugged into the computer not the phone remove the battery and this time only hold the vol up/down at the same time and then plug in the usb. That will get you into recovery and you can odin back or install from there.
READ the NOOB guide by S15274N in the General section sticky. It has a complete play by play on how to do this.
Good luck
Yea I currently have odin 1.7 with I assume the right drivers (ive never had the phone plugged in to this computer while operational) and I do exactly that to get the phone in download mode and odin never sees it. The computer dings and recognizes it (thats how im installing the drivers) but not odin.
Remove the battery, put back in
Open odin
Plug usb into pc, not phone
Go to download mode
Plug usb to phone
Com 3 or 5 connected?
And be positive you have the right odin
If you can get into clockworkmod you should be fine. Just select install from SD and scroll to the zip file of the rom. Give it time to reboot say 5 to 10 minutes. While that's working get the newer version of Odin 1.8??? If the Tom fails in clockwork then do a battery pull. Start Odin. Plug USB into phone only. Hold both volume up and down. While holding plug USB into computer.
I'll go to the computer in a sec and see if I can find a link for latest Odin.
Sent from my GT-I9000 using XDA App
Steps 1 through 4 but odin doesn't respond to the phone being plugged in.
If it makes a difference, to get to download mode, I have to boot into recovery, go to 'ULF Lagfix features' and select reboot into download mode. It also will go into download mode if I hold the volume buttons and then plug in the phone.
I really dont see what I'm doing wrong thats why I started a thread.
I have odin 1.7 ill go try to find 1.8?
Wait, why can't you just reboot? Did I miss something?
Um all the phone can do is go to recovery, and download mode, I have a rom on the phone that won't flash, after a little research, i'm pretty sure the md5 checksum of that rom is bad, therefore won't flash. Im not a samsung guy, is it possible to flash a rom from internal memory? Could I just push a rom through adb? All I have is recovery though and im pretty sure that doesn't support adb. I do have the option to mount usb mass storage though.This is why i'm using odin as a last resort because im used to htc phones this is my friends sammy.
Try this version of Odin...http://www.mediafire.com/file/z7e8fg365znsfpn/Odin3 v1.81.exe
Nope nothing. Damn could it be that I have the wrong files, but that wouldn't change the fact that odin isn't seeing my phone. Does odin take an extraordinary long time to find the phone or something because nothing happens when I plug in in download mode? BTW thanks for the help its nice to see some support
Also I'm not clear as to where your at exactly. When you flashed the rom did it reboot to the Vibrant screen or give you a message in clockwork that it failed. If it booted to the vibrant screen did you give it at least 5 minutes or more to boot (it can take awhile for the initial boot.)
Either way the newer Odin version should recognize the phone. I know I had problems with the older versions.
Yea I put the rom on let it sit for 15 min, came back changed the language then gave it a reboot to let it settle back in. It reset again on the reboot. After about another 30 min of messing with it, im like screw it lets go to another rom that I already had on the sd card, I booted into recovery, to find that it wasnt seeing the sd card. I then restarted (in norwegian) and put a new rom on the phone. (On my mac it recognized the sd card and the internal storage so I put it on both in case) I then went to flash this new different rom through recovery which failed. The new rom flash deleted the old rom but never flashed the new one, leaving me with recovery. After hours of trying to figure out if I can adb push a new rom into recovery, I decided to try odin. After installing drivers and finding all the stock files, im now at this point where odin wont see the phone. Thats just about the whole story give or take.
Edit: The only problem with your rom was that it reset the language every time I turned it on and that it lost my sd card because it was the wrong kernel. I'm now trying to flash a different rom, in an attempt to fix the sd card, but it failed for whatever reason, and has left me with nothing.
TheSilverStig said:
Yea I put the rom on let it sit for 15 min, came back changed the language then gave it a reboot to let it settle back in. It reset again on the reboot. After about another 30 min of messing with it, im like screw it lets go to another rom that I already had on the sd card, I booted into recovery, to find that it wasnt seeing the sd card. I then restarted (in norwegian) and put a new rom on the phone. (On my mac it recognized the sd card and the internal storage so I put it on both in case) I then went to flash this new different rom through recovery which failed. The new rom flash deleted the old rom but never flashed the new one, leaving me with recovery. After hours of trying to figure out if I can adb push a new rom into recovery, I decided to try odin. After installing drivers and finding all the stock files, im now at this point where odin wont see the phone. Thats just about the whole story give or take.
Click to expand...
Click to collapse
Okay got it now...First, did you try the newer Odin that I posted? Second are you able to ADB push to the internal still. If you can do either of these then go here..http://forum.xda-developers.com/showthread.php?t=870480 if doing ADB the get any of the .zip files, push to phone and flash. If able to use Odin then get any of the .tar files. Go into Odin UNCHECK repartition and only load the .tar file into PDA and click start.
Seems that there is a problem going backwards from 2.2.1 to 2.2
Hope this helps.
Yes the new Odin is the one I just tried and it's still not working. Also, when I try to start adb it says no such file or directory. I can only get into recovery and I dont think adb works from recovery. I guess what im trying to say is that my sd card won't mount, I can only flash from internal memory, but I cant add or remove from the internal memory because I don't have a rom to boot into. Also, for whatever reason, odin won't find my phone. Sounds grim unless I can try odin on a different computer (maybe that would make a difference) or I can adb push files to my internal storage from recovery.
Do you still have the my rom on there and have you tried to reflash it?
If not try that and then put one of the kernels from the last link on your phone and flash that first then flash the rom you are trying to get to. I am assuming that you are not trying to flash to the CM7 rom because that has a few steps just to get ready to flash.
EDIT; If you are able to reflash SimplyGalaxy2.3 let me know and we can go from there to get you back to where you want. Also which rom are you trying to flash to.
ok first post so i wont waste any time getting to my problem, how I caused it and what i have tryed to fix it.
i have a vibrant running 2.2, last night i tryed to root using aio toolbox not knowing it only worked for 2.1(my mistake).. so heres what happened it boot my phone into download mode and from there i tryed to install packages only to get a error about signature so i reboot my phone and tryed to use odin to downgrade only to realize that somehow i screwed up my phones ability to connect to pc, it charges but does not go in debugging massstorage etc, so from there i went back into download mode and tryed to reinstall packages only to get error about missing update.zip, i dont have superuser and dont know how to get the update.zip back without usbmode or superuser. ive tryed everything else, it will detect my wifes vibrant but not mine. i know its my phone not the pc/usb/drivers etc etc PLEASE HELP NEWBERT
just keep trying odin to get back to 2.1
my usb's dodgy aswell, charges and takes like an hour or 2 before it actually comes up on computer and phone saying its connected
i messed up mine the other day and it took me like 2 hours of trying to get it to connect to odin going through all 4 of my usb ports like 10 times each but it eventually did it so just keep trying
try different ways:
pull battery out and connect usb and open odin
hold vol up and down and push battery back in and it should go to download mode
or
leave battery in, open odin hold vol up and down and plug usb in and that should go to download mode
mine only works with the 2nd way for some reason, the 1st way seems to work for most people though
ive tryed this it will go into download mode but odin wont detect it, i think its something with my drivers on my phone. im completely new to this but i know it worked flawlessly untill i tryed to root, im not sure what went wrong besides i used aio toolbox intended for 2.1 on 2.2
Odd. I have never used the AIO Toolbox, never felt the need to, but yes, if you are able to get into download mode, but ODIN is not recognizing, it does sound like a driver issue.
You may want to uninstall/reinstall (here are the drivers, be sure to note the 32/64 tabs) LINK
Also, make sure you have the latest ODIN (check my going back to stock guide)
You might also want to make sure the pit/tar you have for JFD are good by checking the md5, I use hashtab to do this. (I realize you are not at that point yet).
Try rebooting your PC, pulling your battery and waiting a bit... trying different USB ports, be sure to remove other USB devices too before rebooting your PC (my ODIN will NEVER work with my webcam hooked up).
If that does not work, wonder if other drivers would help...
+1 follow above
- So the phone won't boot completely? That sux!
- If it did you could bluetooth the update.zip from her phone to urs.
.....but.......
- It automatically boots into recovery?thats odd
***How are you getting into Download mode?(the yellow triangle with android dude shoveling) Button combo maybe?
I installed the latest nightly build (cm_galaxys2_full-88.zip) on my phone yesterday night and restored the all the apps through Titanium Backup. Everything was working fine until this morning I tried to create a backup using CWM recovery in Rom Manager. The phone shut down and has since been stuck on the initial boot screen (one with the Samasung galaxy S2 logo). It does not boot into recovery mode using the button combinations. I can only get it into download mode but Odin does not recognize it as I thing i forgot to enable USB debugging.
I have tried removing the battery and rebooting and also tried to access it through odin a number of times. But nothing seems to work.
What am I missing here ?
This might help?
mjondj said:
I cannot boot into recovery, but I can boot into download. However, odin is no longer recognizing my GS2 when I plug it into my PC.
The bootloop began when I was attempting to flash the cyanogen7 with the google apps.
I read every post in this thread, and have seen a number of people who cant boot into recovery, but can boot to download. I haven't seen anyone else mention that their phone is no longer recognized by odin on their pc.
Please help.
edit:
Perhaps odin doesn't see my phone because I didn't have USB debugging enabled? if that's the case, what can I do?
------------------------------------------------------------------------------------------------------------------
solved:
heimdall overwrites a driver and stops odin from seeing your phone. i attempted to remove it, unsuccesfully. but loaded odin onto a different computer (that had never seen heimdall).
i booted into download, connected to 2nd pc w/ odin, and ran CF-Root-SGS2_XW_NEE_KI8-v4.3-CWM4.tar (search forum) in PDA. this made my phone bootable again.
Click to expand...
Click to collapse
also check that you dont have kies running on your pc
icecreampop3 said:
This might help?
also check that you dont have kies running on your pc
Click to expand...
Click to collapse
Thanks. Although that did not do what I expected it to (due to some license issues), but it got me into recovery mode from where I could restore a Nandroid backup. Am back on RevolutionROM for now. Looks like CyanogenMod will have to wait for me.
I experienced the very same thing for the first time today. Had checkrom revolution and ran rom manager to backup and am now unable to boot into recovery/download. Will try to hook it to odin then
Hello all,
I've encountered a problem with my Straight Talk Galaxy S II S959G after flashing the CWM from this thread:
http://forum.xda-developers.com/showthread.php?t=2559694
I was running 6.0.1.2 or something along those lines. And I was running the 4.2.2 SuperNexus ROM. I can only get to the Samsung Galaxy S II screen and then it goes blank, but does not shut off, as my computer recognizes as being on. However, I cannot DO anything with it even though it can be connected to my computer. Odin v1.85 does not seem to recognize it either.
If someone could help, it would be much appreciated.
It sounds like you just have a soft brick if you're still getting the Samsung logo.
ODIN is intended to be used in download mode. Are you able to get into download mode (hold vol +/vol -, then plug in the USB cable)? If so, you should be able to reflash the kernel, assuming that's what broke. I like to keep an ODIN flashable full stock ROM (minus bootloaders) handy in the event that I mess things up badly.
I don't have experience with the specific ROM you are trying to flash (I was actually planning on playing around with that one soon).
jpasher said:
It sounds like you just have a soft brick if you're still getting the Samsung logo.
ODIN is intended to be used in download mode. Are you able to get into download mode (hold vol +/vol -, then plug in the USB cable)? If so, you should be able to reflash the kernel, assuming that's what broke. I like to keep an ODIN flashable full stock ROM (minus bootloaders) handy in the event that I mess things up badly.
I don't have experience with the specific ROM you are trying to flash (I was actually planning on playing around with that one soon).
Click to expand...
Click to collapse
I'm not very experienced with all of this, but, I have tried Odin mode. My computer does not recognize my phone when it is plugged in.
I do have the stock rom that my phone came with too, but I do not have a Samsung official USB cable to use with it, which, supposedly, is required for this to work. And I do not know if my Odin version on my computer is outdated either.
Epications said:
I'm not very experienced with all of this, but, I have tried Odin mode. My computer does not recognize my phone when it is plugged in.
I do have the stock rom that my phone came with too, but I do not have a Samsung official USB cable to use with it, which, supposedly, is required for this to work. And I do not know if my Odin version on my computer is outdated either.
Click to expand...
Click to collapse
Many usb cables will work just fine. The original cables are known to be of good quality. Odin3 v1.85 is recommended for this phone, although any version of Odin should work.
Did you open Odin on the desktop before putting the phone into download mode? Sometimes the problem is as simple as wrong sequence.
If you have a USB jig, use that to put the phone into download mode. Then connect it to the computer while Odin is open on the desktop.
Make sure you have the correct driver installed. You should have "SAMSUNG USB driver for mobile phones" in your add/remove programs dialog in windows. If not, install it. If so, uninstall it, reboot, reinstall it.
Try different cables, different usb ports, even different pc's.
I'll try not to butt in too much, since creepyncrawly obviously has a lot of experience.
(at this point, I'm assuming you're on Windows)
Like he said, it's sounds like it's most likely a driver issue. When you first plugged in the phone, did you get a Windows balloon notification saying "Installing drivers"? If you open up device manager, do you have any devices with an exclamation point next to them, indicate a device that failed to start? If so, make sure the Samsung drivers are installed.
A USB jig is definitely nice to have handy. I use this one (as long as you can wait a few weeks on shipping). If you can get into download mode, your bootloaders are probably safe (meaning you should be able to recover easily).
I actually installed that CM11 ROM yesterday on my SGH-I777 (I can't say anything specific about your model and how it may differ, but it seems to basically be the same phone as the I777). I was running stock non-rooted JB 4.1 with stock recovery, so I had to take a little more of a convoluted route to get there.
In the end, here's the thread for you. Once you can get ODIN download mode working again, you should be well on your way to fixing it (flash CWM 6.0.4.5 from ODIN, boot into recovery, then try the ROM install again).
Well, I've tried flashing CWM again using Odin. While I actually can USE Odin this time, it just isn't working... My phone still only turns on and goes blank after the Galaxy S II screen.
I had something similar happen the other night when I flashed a kernel that was apparently incompatible with my Captivate (although it should have been fine). The phone would get stuck on the Galaxy S boot screen. I had to reflash a known good kernel to get it working again.
If you can get into the recovery, you can try a wipe/factory reset + wipe cache.
Is ODIN detecting the phone but just failing to flash the files? What error is it getting?
If ODIN is flashing the files properly, but still preventing full boot up, it's probably easiest at this point to flash back to a stock ROM. The previous thread link has the instructions and flash files (I personally have an S2, not an S959G, so it's a slightly different process).
Hi - I don't know if it is a completely outdated method, but this worked on my father's SII skyrocket yesterday when I was encountering a similar softbrick issue:
Get zadig (http://zadig.akeo.ie/), start zadig, get the phone in download mode, hit Options -> List All Devices, select the Samsung or similar device from the dropdown and replace the default USB driver.
Then use heimdall (http://forum.xda-developers.com/showthread.php?t=755265) to flash in a replacement recovery.
Double check that your phone is detected in download mode: heimdall detect
Then flash the recovery: heimdall flash --RECOVERY recovery.img (try CWM for your phone version)
(some places will have you add --no-reboot. that didn't work for me. let it auto reboot)
After it powers down, quickly disconnect the USB cable and put your fingers on the +/- buttons to get into recovery mode. From there push over whichever ROM via adb, etc. etc.
jpasher said:
I had something similar happen the other night when I flashed a kernel that was apparently incompatible with my Captivate (although it should have been fine). The phone would get stuck on the Galaxy S boot screen. I had to reflash a known good kernel to get it working again.
If you can get into the recovery, you can try a wipe/factory reset + wipe cache.
Is ODIN detecting the phone but just failing to flash the files? What error is it getting?
If ODIN is flashing the files properly, but still preventing full boot up, it's probably easiest at this point to flash back to a stock ROM. The previous thread link has the instructions and flash files (I personally have an S2, not an S959G, so it's a slightly different process).
Click to expand...
Click to collapse
It says Odin is successful, but still nothing happens. And I cannot get into recovery no matter how many times I try.
It seems flashing the stock ROM with Odin has worked now, but, now my phone has the tracfone start up animation just looping over and over.
Epications said:
It seems flashing the stock ROM with Odin has worked now, but, now my phone has the tracfone start up animation just looping over and over.
Click to expand...
Click to collapse
Boot into recovery and wipe caches; sometimes you have to do an extra wipe to get out of this type of bootloop.
SteveMurphy said:
Boot into recovery and wipe caches; sometimes you have to do an extra wipe to get out of this type of bootloop.
Click to expand...
Click to collapse
I'm having difficulties booting into recovery.
Epications said:
I'm having difficulties booting into recovery.
Click to expand...
Click to collapse
If you have the stock boot animation you should have recovery. Take the battery out, then put it back in and hold power+volume +/- until you get recovery. I have sometimes had to do this extra step after restoring stock.
Make sure your phone isn't plugged in while you're trying this, btw.
grand quattro CWM TRAPPED
Epications said:
Hello all,
I've encountered a problem with my Straight Talk Galaxy S II S959G after flashing the CWM from this thread:
http://forum.xda-developers.com/showthread.php?t=2559694
I was running 6.0.1.2 or something along those lines. And I was running the 4.2.2 SuperNexus ROM. I can only get to the Samsung Galaxy S II screen and then it goes blank, but does not shut off, as my computer recognizes as being on. However, I cannot DO anything with it even though it can be connected to my computer. Odin v1.85 does not seem to recognize it either.
If someone could help, it would be much appreciated.
Click to expand...
Click to collapse
HI BROOOO I M A GRAND QUATTRO USER EVERYTIME I SWITCH ON MY CELL MY CELL DIRECTLY GOES IN CWM MOD M WORRIED ALOT HELPPPPPPPPPPP ME
Please can you assist me.
I've read through so many threads explaining that it is easy to fix if I use ODIN. However I cannot seem to get ODIN to recognize my Galaxy S3.
I was doing a factory reset on my device, which has Cyanogenmod installed. Upon rebooting, the phone is now stuck with the Teamwin logo and it continues to loop.
In cannot seem to charge the phone because it's stuck in this mode and when I install ODIN and along with the SAMSUNG USB Drivers. I have no luck with my computer recognizing the device. I am able to get into the Download mode by holding Power, Volume Down and Home buttons - I click Volume up to continue. I then check my ODIN screen and it never appears to say ADDED or anything of that sort.
I'm scared that my phone is going to soon run out of charge and then I will not be able to even attempt to fix this. Please help me.
I've tried the above steps in both Windows 8.1 and Windows 7 and cannot get either of them to recognize my device.
N.B. I have also tried different USB ports as well as different USB cables.
Once again, I plead for any assistance.
Can u go to the custom recovery ??
If so
Do a clean wipe
Do a factory reset (do not do a clean to install new rom,just erase your data)
Wipe your cache
Wipe dalvik cache and see if u can boot it up
Goodluck
Use the latest odin version and see
And why didint you take a nandroid backup before installing custom roms
If u took it
Just restore it
U will surely boot it up
Hi there,
Thanks for your reply.
I managed to solve the issue by using a computer which already had my device USB drivers installed.
The other 2 computers I tried didn't seem to want to recognize the device due to the bootloop - but when linking up to a computer which linked to my phone prior to the ordeal, ODIN then recognized the device and I was able to load stock rom back on.
FYI, I wasn't able to access recovery.
Thank you for your quick response.