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
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
cugami said:
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
Click to expand...
Click to collapse
GO here : http://forum.xda-developers.com/showthread.php?t=1993044
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
A while back I unsuccessfully tried to root my Samsung Galaxy S3.
The phone still worked OK, rebooted fine, etc., was using it for months.
Just recently though I decided to factory reset so I can give my phone to a family member, and this happened (see pics below ). Now it just hangs on T-Mobile screen and never boots at all.
http://imgur.com/gallery/0BWqcUA
Can anyone point me in the right direction to flash the default factory image back on there.
This is with T-Mobile in case that matters.
Thanks in advance.
UPDATE:
I located this thread:
http://forum.xda-developers.com/galaxy-s3
Also tried downloading this driver:
http://www.samsung.com/us/support/owners/product/SGH-T999ZWATMB
The problem right now is neither ODIN nor ADB sees my device. I have the device in "Downloading" mode (boot power down key, home ,power button).
Also tried the up-volume boot and adb side load.
Uninstall all Samsung drivers, reboot, and install Samsung Kies. This will setup the drivers you need, then you can use Odin to restore. If this doesn't work, try different cables, ports, or another computer. Check in Device Manager to see which driver is loading and manually switch if needed.
PS. You're not going to be able to communicate with the phone via adb without it booted and USB Debugging enabled or with a custom recovery that you're booted into.
Hello all,
So, let me keep it as short as possible.
The incident
I was talking on the phone, after the call i tried to hang the phone and there was just a black screen (phone stuck).
Pushed Power button steady and the phone rebooted and never boot again.
Mobile bio
The phone was rooted (2+years ago with CF Root)
Rom was stock European 4.1.2
I have available a full nandroid backup (boot.img etc)
The latest Custom recovery i had installed was CWM (ver. 4 something).
Current status
The phone is stuck at boot with a yellow triangle.
The phone can get to download mode (and be recognized by odin)
The phone cannot get to the recovery menu, (to be more precise when i press vol+, home, power the phone finally gets to a black screen {no backlight} but it is recognized by the command "adb devices" as in recovery status)
Kies cannot connect either in recovery mode or download mode. (Stays in connecting message).
Tried the following
Installed various kernels (Siyah-s2-v4.1.5, Siyah-s2-v5.0.1 etc)
Installed various roms (including stock roms) via odin with NO error.
Installed the original .pit file for 2Gb S2 system memory.
Tried the flashing method with 3 separate files (CODE_I9100XXLSJ.tar, CSC_HOME_OXX_I9100OXXLS1.tar, MODEM_I9100XXLS6.tar) via odin appropriate fields.
Tried two different Odin versions (1.85, 3.07)
So after trying all these, i finally rest my hopes in the community.
I really hope there is something more i can do, in order to fix my phone.
Thanks in advance for your time and effort.
Hello again...
Still trying to find a solution...
Some more info, in download mode i get the following info:
Custom binary download: YES (1 counts) and it doesn't change no matter how many times i flash anything through odin.
Does this count change only if you flash a new rom via recovery?
Anyway, i'm pretty desperate so i keep on trying to find a solution...
ANY help appreciated.