I've posted in the general Q & A but nobody likes to answer
I was running Darky's mod for awhile and decided to try Cyanogen mod. So I went to CWR and installed it from my root nothing went wrong...
When i rebooted my phone it shows the Samsung Galaxy S bootscreen, then it shows the platypus screen, then CWR going through some stuff (yellow triangle with ''!'' shows up in the background where the android should be) and it just reboots again. I tried to put it into recovery mode... No luck
Then i tried to put it in download mode to flash Stock Froyo but it's not going into boot mode. I tried taking out sd card and SIM card, No luck. Theres no Radioshack in my city so that i could Jig it...
Any help (My Phone is Samsung Galaxy s Fascinate Telus(3g+)
Related
Hi my vibrant seems to be bricked and nothing I do seems to be able to fix it.
I was using different 2.2 ROMS and I tried to reboot recovery but then it got stuck on the bootup screen.
So I tried to ODIN back to stock, except when I ODIN and it restarts the phone it turns off after the "Galaxy S" boot animation. Trying ODIN back multiple times won't fix the problem either.
I can go into the stock recovery and Download mode just fine. Anyone know what's wrong?
BTW it happened after I did partition SD card in ROM manager.
I heard that you could flash Eugene's 2.2 froyo ROM and it'll work but I can't even get into the bootloader, stuck on the default on. Please help
EDIT: Figured it out!
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
It's not bricked. Probably just in a boot loop. Just need to play around and get into download mode.
speedy11131 said:
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
that doesnt make a difference, i've been on simply honey like 2 month on froyo bootloaders and works fine apart from rainbow on boot and not being able to see recovery
speedy11131 said:
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
That happened to me before, I used and tried a different cable and got into download mode with functioning odin. Also, try removing battery, then put the battery back in. then with pressing volume up and down with power switch plug in usb. Hope this helps. Vibrant is hard to brick.
Sent from my GT-I9000 using xda premium
It is not dead yet, follow the steps as follow thread to go back in beginning and flash rom you want again.
http://forum.xda-developers.com/showthread.php?t=734475
Depending on which version of ODIN you are using the sequence works best like this:
1) Get the phone into a download acceptable mode with use of a usb cable (JIG is most appropriate)
2) Have ODIN running BEFORE connecting the phone
3) Now connect your phone and attempt the flash. Version prior to 1.7 were extremely picky with following this sequence. As of 1.7 POST ODIN seems to not bug so much the sequence of when the phone was plugged in.
Report back with your results...
speedy11131 said:
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
1) take your battery out
2) plug your phone a laptop/desktop
3) hold volume up and volume down + put the battery in
...should be in download mode...I am assuming u have a froyo bootloader...
If that don't work then on step three instead of holding both volume buttons only hold volume up..that works for GB bootloader...
Hi guys,
Here's what I've done.
Galaxy S2, rooted several days ago using CF-Root no problem.
Flashed Cyanogen 7.1 been using it for a couple of days, no problem.
I had the yellow triangle on boot and I bought a USB Jig thinking that would remove it.
It put the phone into Odin mode, but didn't remove the triangle.
So then, still with Cyanogen 7.1 on the phone, I powered off the phone, connected it up on Odin and used the PDA button to flash an official Samsung Kernel (Kernel_I9100XWKI4) - I remember XKWI4 was on my phone originally before I did anything. I guess this had changed with Cyanogen being installed.
Now the situation is I cannot power the phone on at all, just black screen.
Plugging in the USB jig does absolutely nothing.
If I have Odin open and connect the phone to the PC, Odin does recognise the phone.
Can anyone help me please - only had the phone a week!
Remove battery wait 10s, put battery back and either use the jig or boot while holding home vol-down and power.
i remember when i was fixing my brother galaxy s captivate after i flashed cyanogenmod i had to install google aosp drivers as opposed to samsung drivers to get odin to recognize his phone. So...try that.
Thanks for the replies guys.
Basically ODIN can see the phone.
I had managed to get the phone to boot to the Samsung screen (triangle gone as now on Stock Kernel) however it would stay on this screen forever.
I have used ODIN and flashed CWM recovery 4.0.1.5 to the phone which I can access using the 3 key combo. Obviously after doing this, the phone now boots with the triangle however it stays on the Samsung screen permentantly.
I figured I would try to re-flash Cyanogen.
Problem I now have is that Cyanogen is on the removable SD card - the phones internal 16Gb "card" is empty.
I can't get CWM to see anything on the removable SD card.
If I simply power on the phone currently, I get the Samsung flash screen with the triangle (no longer bothered about removing this, I just want the phone to work!) and it stays like this permentantly.
I can access CWM Recovery Mode, however it cannot see the removable SD card.
I can also access ODIN download mode and the phone is detected with ODIN.
I am unsure as to what Kernel is currently on the phone.
Either connect your phone to the pc while in recovery, go to mounts and storage and mount sd (or internal memory, no idea what the actual name is) and copy the rom to the internal sd card. Or use odin to start fresh again.
my phone originally started out with the stock 2.1update 1 firmware, t959ujfd...
when i turn on (off then on) the phone it would boot to a "Samsung Galaxy S GT-I9000" logo, then switch to a "Vibrant Samsung" logo.
when i received my phone this was how it booted..
Later, i rooted the phone, and flashed clockwork mod recovery.. I made a CWM recovery back up here..
After creating the backup, i put CM10 on to the internal sdcard and installed it via CWM. During the
installation, it rebooted into the newer version of CWM recovery. After choosing "reboot device", my vibrant
would first load the "Samsung Galaxy S GT-I9000" logo, then the Cyanogen mod logo. but then the screen would
flash, and the cyanogen mod logo would appear again. Shortly it dumps me right back at the new version of CWM recovery..
At this point, i thought i flashed CM 10 incorrectly, so from the CMW recovery, i restored that first back up. after restoring that
back up, my phone no longer boots.. Right now if i leave the batter in and plug in a USB, the circular spinny charging icon appears,
then freezes (it doesnt spin).. i can turn on the phone, but it stays stuck at the "Galaxy S GT-I9000" logo.. I cant boot into recovery.
so i read a bunch of other threads about perhaps when ibought the phone, it had a GB bootloader. and i have tried ways to get my vibrant
into download mode.. which unfortunately i havent.. So i can't use Odin and flash back to stock.. Hopefully you guys can help me get back to stock so i can at least use my phone and/or start over installing CM10..
Note: i did not install/flash anything else other than CM10. i did not use custom kernels, or install Google Apps etc..
Edit: Ok, now i can reliably get into download mode. for some reason, the physical button combinations were wrong for my vibrant.. instead of the
usual 3 button combo, my download mode was volume up + power.. this was also the reason why i had a hard time getting into recovery since it was
volume down + power.. It seems as if, my boot loader was changed when i bought the phone..
That's the combo I use I don't have boot loaders. Son if that worked did you get it fixed with Odin or heimdall
Sent from my SGH-T959 using xda app-developers app
All you had to do is flash cm10 again. Most of the times you have to flash jb roms more than once because of the different cwm versions . Make sure you read the entire thread before taking action, I'm sure it said that somewhere but anyway Gb bootloaders are much more convenient so that's a plus. Just flash back to stock with Odin or if you still want cm10 then boot into recovery and flash again.
Sent from my SGH-T959 using Tapatalk 2
Sent from my SGH-T959 using Tapatalk 2
Hi, today I tried to downgrade my Galaxy S3 from Cyanogen 12 to stock firmware (So from Lollipop to Jellybean) but now it's stuck on the bootsceen and I can't access the recovery mode, I can just access download mode.
Hi Hencick - Welcome to XDA.
I'll just naturally assume that you're familiar with flashing roms...
Were you running a custom kernel with CM?
Can you access adb functions with a pc?
I have a similar problem on my phone I discovered today. I just get the Samsung logo on screen, it goes off, then comes back (bootloader loop i guess).
It was just sitting on charge. It hasn't done anything for a while other than updates, now when I come to it, it's like this.
I can't get into recovery mode, adb mode, download mode or anything. Just the Samsung logo flashing up, then going and coming back up.
Is this recoverable?
As it it keeps powering up, then off, then back up I'm not even sure I can use Odin on it.
TIA.
Edit: Ok, I can get it into download mode it seems. Only, now I'm not sure what to do! lol