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
Hello,
Some threads with similar issues are already around, but I didn't find one with the same problem as me.
What I was doing when the issue happened:
I was trying to install cyanogenmod from the isntaller method (apk isntalled on the phone, application running on windows that installs it automatically). At certain point, it rebooted the device and the cyanogenmod logo was on the screen. After a while, the program gave an error "'We couldn't talk to your phone' - Samsung devices ONLY", which is described in their wiki. So the pc lost connection to the phone.
What I did:
1 - Since I had installed the clockwork recovery and tested it before, I thought "hey, no problem. I'll hust recover this S*it". So I disconnected the SIII from the PC and tried to enter recovery mode pressing "volume ip + home + power". While I have these pressed, the phone in in an infinite loop on the initial screen showing the brand and model. When I release them, it goes straight to the cyanogenmod blue creepy robot just there staring.
2 - Since that didn't work out since I now don't have a recovery mode and I don't have any functioning rom either, I found several tutorials for using Odin and reflashing and or repartitioning. PROBLEM: Odin seems to recognize the phone (com port), I click on the option and... FAIL!
2.1 - What I have tried: Different Odin versions (1.83 and 3.09), stock drivers from Kies, Zadig drivers.
So. There you go. I pretty much exhausted everything I could get from my head and interpret from google. So, No recovery, no ROM, fail at odin.
Any ideas?
Thanks in advance.
Remove kies from the pc reinstall drivers and flash a cwm recovery. From there flash a custom rom in recovery from ext sd. Odin 3.04 is good. I would keep trying to get into recovery though. Do you have that red mark in the corner on Sammy splash screen?
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.
My Gear S is frozen on the opening screen (showing Samsung Gear S logo) and will not progress. Have tried rebooting, clicking on recovery etc, but it seems to go back to this screen and will not go further. Any assistance would be greatly appreciated! I have put the watch into download mode (to try to re-flash it) and Odin is not detecting it.
Fixed.... Just in case this may help others. I downloaded new USB drivers, which still did not resolve the issue. I changed the cable to a genuine Samsung cable and rebooted the PC. Not sure if it was the reboot (due to the new drivers) or the improved cable, but Odin then detected the watch. Using the extremely helpful guide in the Gear S developers forum (http://forum.xda-developers.com/gear-s/development/definitive-guide-to-rooting-gear-s-t2973455), I then loaded fresh firmware onto the watch. After loading this and restarting the watch it for some reason went back into download mode, but after again holding the power button down put it into recovery mode and all seems to be working again. Quite a process, but got there!
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
It's always risky to apply mods.
To get rid off of all mods you applied re-flash tablet's Stock ROM.
If this doesn't work for you then take it to authorized service center and let them try to fix it.
jwoegerbauer said:
take it to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
They never fix anything. The only thing they do is charge you an absurd price and replace the motherboard or the entire tablet.
I'm on the same boat. Tablet can't get into download mode, just shows "This device has unauthorized software on it and is locked". Tried all possible button combinations to no avail.
SmiffyJ said:
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
I have the exact same problem, did you manage to recover the tab?
Thanks heaps