Related
I have CWM 3.0.8, and want to get back to the red recovery, so that I can flash a new rom on my fascinate. The problem is, that I can not for the life of me get my phone to show up on Odin. I have tried on two different computers. I have used Odin on both computers for this phone, so the drivers are all installed. Any ideas? The rom I have now is a force close nightmare. I would like to get back to something that is stable.
Thanks for any help,
Brad
bradbradbrad said:
I have CWM 3.0.8, and want to get back to the red recovery, so that I can flash a new rom on my fascinate. The problem is, that I can not for the life of me get my phone to show up on Odin. I have tried on two different computers. I have used Odin on both computers for this phone, so the drivers are all installed. Any ideas? The rom I have now is a force close nightmare. I would like to get back to something that is stable.
Thanks for any help,
Brad
Click to expand...
Click to collapse
Follow this guide.
http://forum.xda-developers.com/showthread.php?t=1001064
Sent from my SCH-I500 using XDA Premium App
Ive used odin before, I just cant get the fascinate to be detected by the computer. It wont even mount the sd card via the usb cable to transfer files. I got the phone in download mode, connected to the computer through the usb cable, but can not get the yellow "added" dialog in odin so that I can flash the .tar file...
Thanks for the help so far,
Brad
Maybe a stupid question but do you have Odin open before you plug the phone in.
Sent from my SCH-I500 using XDA Premium App
You can also try to reinstall drivers or even odin check to see that you have odin 3 1.3 and maybe reinstall odin it can be found here in one of the forums.
I have tried it both ways, going into download mode, then opening odin, and first opening odin, then going into download mode.
Now, I have another problem. I was able to do a data wipe, which stopped the force close loop. I was then able to get my phone workable at least. Then, while resetting everything, I dropped it on my coffee table and the touch screen will not respond. The phone's soft keys work fine and i can turn it on, but have to do a battery pull to turn it off. I have tried turning off/rebooting, and again doing a data wipe. I don't know what else to do other than take it in, but I don't think that is possible since it is rooted
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(((
Hi, so I have the SGSIII on Verizon and I tried to flash the rooted stock.img, but it failed and now whenever I try to boot up the device, it says."Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
I'm assuming that you installed the drivers and Odin connected correctly to start the flash. Can you still get into download/Odin mode? Turn phone off or battery pull. Hold the volume down, home, and power buttons till the phone turns on and the yellow triangle appears. Hit volume up. Plug your phone back in and see if Odin sees the connection. Then try flashing again. Don't touch the phone till it completely reboots.
Sent from my DROIDX using xda app-developers app
I had same issue and it was because the tar file I had downloaded to flash wasn't the complete file. Try downloading it again and then try again with Odin.
All of the sudden, even though I really didn't do anything besides try to go into download/odin mode (which did come up), I rebooted and all was good. I even had root. Whoop! Good for me I guess.
I am also suffering something along those lines with Odin, although just a tad different so I felt it didn't warrant a new thread.
I am attempting to root my Galaxy S3 using Odin, with the stripped down rooted .img
As you can see, when attempting to flash it, I am getting failed multipal times, so I am at a loose for words right now
imgur.com/hy9Bk.png
ssjvegeta003 said:
I am also suffering something along those lines with Odin, although just a tad different so I felt it didn't warrant a new thread.
I am attempting to root my Galaxy S3 using Odin, with the stripped down rooted .img
As you can see, when attempting to flash it, I am getting failed multiple times, so I am at a loss for words right now.
imgur.com/hy9Bk.png
Click to expand...
Click to collapse
try a different package. i have not seen that one. there are others known to work. read the stickies. the ones posted there are tried and true.
EDIT: As I've now gotten Odin to flash again, and my device still won't boot, I'm really starting to think Andromeda's recovery has wiped something vital that isn't restored with a "regular" stock ROM image. PIT? EFS? Partitioning? Something like that? Odin successfully flashes the whole image tar (which I've previously used successfully), and the boot splash now correctly changes to the default Samsung one without triangle, but still the phone won't boot (as described in msg #3). So I'm now wondering if there's any way to a more aggressive restore (whence the topic title change)? Or am I barking up the wrong tree here?
----------
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Daniel Smedegaard Buus said:
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Click to expand...
Click to collapse
the reason for Dream and Andromeda not booting ur phone is that, if ur paranoid rom version was latest, then it comes with the new JB mali drivers for which only Dori v7.4 and siyah v5.0 are compatible
since u have already messed up too much with ur phone, u can try the 'KIES' option as the last resort to restore it back, since odin flash is not wrk'ng for u
Okay, so I tried installing Kies and connecting it. A variety of connection attempts, but it just won't connect to the device.
But, I'm making some progress! I've found that when I can get the phone to boot into the "Firmware upgrade encountered an issue." screen, I can get Odin to flash the stock Gingerbread image (still won't in download mode). And I then get a reboot with the regular Samsung boot splash (no yellow triangle) - except it never gets past it. After about a minute, it'll go black and then boot back up to the same splash screen and the same problem.
This is the exact same image I've used previously to revert the device to stock. So I was kinda hoping to see a normal clean. But unfortunately no donut. It reminds me of a computer I once bricked by screwing with its BIOS - it never got beyond POST and so I couldn't reflash it.
Is there something like a BIOS in this thing that could've gotten damaged in some way? And if so, is there any way to use Odin or another tool to fix that?
Cheers,
Daniel
Tried flashing a couple of matching CF kernels. I now get the green battery after the grey one, but still no boot.
All turned out the be the Shun Andromeda kernel re-introducing the hard brick bug. If you have the same issue, see my reply here for links to where you can get the custom PIT trick up and running.
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