Database Info

Getting Rainbow screen on every boot and when trying to get to recovery mode

Getting Rainbow screen on every boot and when trying to get to recovery mode
For some reason I cannot get my computer to detect my device thus I can not even get into download mode. when I launch Odin and and not able to access my SD. I am at a lost here since now I cannot flash nor can I odin to get back to stock can anyone help here? I think I have tried everything I can find.
I just recently flashed octane 2.x per the instructions under development

rozzko said:
Getting Rainbow screen on every boot and when trying to get to recovery mode
For some reason I cannot get my computer to detect my device thus I can not even get into download mode. when I launch Odin and and not able to access my SD. I am at a lost here since now I cannot flash nor can I odin to get back to stock can anyone help here? I think I have tried everything I can find.
I just recently flashed octane 2.x per the instructions under development
Click to expand...
Click to collapse
If you came from Froyo, follow this guide: http://forum.xda-developers.com/showthread.php?p=16762954
Hope this helps.
sent from my CommandCenter using xda premium

sounds like the bootloader.
flash a froyo rom, then try to odin. AFTER you have tried installing the drivers linked in the previous post. That guide should work.

Did you get this fixed?
Sent from my SGH-T959V using xda premium

I bought a Jig an can get into download mode but still cant get into recover (because of the rainbow screen) and i cannot get my computer to recognize my my phone either via sd or via odin or i think i could solve this.
thanks in advance

I bought a Jig an can get into download mode but still cant get into recover (because of the rainbow screen) and i cannot get my computer to recognize my my phone either via sd or via odin or i think i could solve this.
thanks in advance
Click to expand...
Click to collapse
Go into the control panel & uninstall the USB drivers & kies mini if installed. Then reinstall Kies Mini & use the menu option to reinstall the drivers. See if that helps.
Sent from my SGH-T959V using XDA App

I re installed drivers several times and used a different machine. I feel like I am stuck and there might now be a solution to this except toss the phone in the ocean!

rozzko said:
I re installed drivers several times and used a different machine. I feel like I am stuck and there might now be a solution to this except toss the phone in the ocean!
Click to expand...
Click to collapse
Could it be the cable you're using? I've seen quite a few posts here about people using cables that were bad and/or too long and it prevented the phone from being recognized via USB. People could charge the phone but not use ODIN or anything.
Do you have a different cable to try?

ive tried two different cables, i could try another one thats a good idea. somehow i think maybe i messed up the mounting, i thought i followed the instructions to a t. UMMU .. i will try a few different cables when i get home tonight... actually just tried at work no dice, my system storage is also only showing 126 MB

rozzko said:
ive tried two different cables, i could try another one thats a good idea. somehow i think maybe i messed up the mounting, i thought i followed the instructions to a t. UMMU .. i will try a few different cables when i get home tonight... actually just tried at work no dice, my system storage is also only showing 126 MB
Click to expand...
Click to collapse
I thought the phone did not boot up. How are you seeing how much storage you have left?
I'm curious to know what state it really is in. There has to be a way to get it going for you.

the phone boots fine during the boot after the initial boot screen where it says galaxy s 4g it goes into rainbow patterns. so every time i try to get into recovery when I am in the recovery menu (or into where the recovery menu should be) i cannot see anything because of the rainbow screen. I was told maybe i have the wrong boot loaders installed.
because i cant see recovery and I cannot get my computer to see my phone I have no idea what to do get my phone back to stock to start over.
This is why I am stuck.
If i could get my computer to see the phone I think i could odin back to stock, using the dongle is half the battle as i can get in recovery

rozzko said:
the phone boots fine during the boot after the initial boot screen where it says galaxy s 4g it goes into rainbow patterns. so every time i try to get into recovery when I am in the recovery menu (or into where the recovery menu should be) i cannot see anything because of the rainbow screen. I was told maybe i have the wrong boot loaders installed.
because i cant see recovery and I cannot get my computer to see my phone I have no idea what to do get my phone back to stock to start over.
This is why I am stuck.
If i could get my computer to see the phone I think i could odin back to stock, using the dongle is half the battle as i can get in recovery
Click to expand...
Click to collapse
Pardon me if I'm not getting it....but yo said it boots fine but then you get the rainbow screen when the Galaxy S 4G logo should appear? The rainbow screen is definitely a boot loader issue. I'm just trying to figure out a way to either get you into a download mode where the phone is recognized or into recovery so you can get it going again.
How are you getting it into recovery mode?
I'm wondering if Heimdall would be your best bet? You could try to download it from here, extract it somewhere, then go into the Drivers folder and double-click zadig.exe. Select Options from the menu bar, select List All Devics then select Samsung Android Composite (something along those lines), then click Install Driver. This is a different driver than the one that comes from Samsung.
After that, maybe try Bhundven's [Heimdall][One-Click][UVKJ6] The KJ6 Heimdall One-Click Collection [12/11/2011]. Select whichever one-click file you want to go for and follow his instructions. They all have the GB bootloaders in them, so you should be set.

Usually both volume buttons power button for a few secs or through rom mgr

rozzko said:
Usually both volume buttons power button for a few secs or through rom mgr
Click to expand...
Click to collapse
From what I've read ROM Manager is a no-no on this model phone. I dunno why, but I've read that on a few threads.
Let me know if you're able to install Heimdall and the open source drivers that come with it. If you can, you can get into download mode, and it sees the phone, then you can try the One Clicks or even just flash the boot loaders from a ROM that contains them.

I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.

rozzko said:
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
Click to expand...
Click to collapse
Ugh...well let's hope for the best. I would uninstall any drivers and programs like Kies you have installed first, then install the Heimdall drivers. Let me know how it goes.

so i uninstalled drivers executed Heimdall and put phone in download mode with dongle. the computer still did not detect phone, however i got my replacement SGS4 today put it in download mode and it was detected immediately.
I dont know what else I can do do get the phone detected or fix the boot loader to get into recovery

rozzko said:
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
Click to expand...
Click to collapse
Maybe I'm missing something. How are you switching between debugging mode and mass media if you can't boot the phone?
The way I understood the problem, you would get to the SgS logo screen during boot, then the whole screen would be covered by the rainbow effect, which renders the screen unreadable, nd thus the phone unusable. Is that correct, or is the problem different?

the rainbow screen happens right after the SGS Logo then fades out once the lock screen comes on.
it also shows up once I try to get into recovery but from that point I cannot see anything and have to reboot.
Phone works after fully booted
both debugging and mass storage have been tried

You need to flash the "GINGERBREAD" bootloaders. This issue is 100% caused by froyo bootloaders. Once you obtain the GINGERBREAD bootloader, there is a 100% chance that the issue will go away. Flash THISTHIS/download. in heimdall. Get into recovery, then flash a rom of your choice.

[Q] Odin wont recogize my Captivate

So this is my first question ive posted. i hope its in the right place. I havent found anything on this specific problem anywhere
Anyway I was running SerendipityVII and started having issues with some things. so i flashed DarkyRom from recovery.. everything was fine for a while but some of the aspects of Serendipity were still showing. so i decided to use Odin to flash back to 2.3 then flash Darky alone. So heres the issue. after flashing the PIT, pda, csc and phone files from the SerendipityVII install download, you then need to flash reorient Kernel1.1 which appears to fix issues with the original flash,(auto rotate not working properly, home button acting as back button, etc) well after rebooting and putting phone in download mode again to flash kernel. Odin will now not recognize my phone. Kies will not recognize it either. so when i hook up the phone Windows(XP), recognizes the different hardware elements of the phone depending on mode but installation fails on several of them...
Now thats the problem. the question is can i fix this? Oh super one click root wont recognize either and in recovery mode the power button wont select the option. Stuck on a jacked up version of 2.3 and need to do something...
Thanx in advanced

ok not too long after posting this question i figured out the issue. turns out yes it was a driver issue and i think i was caused by kies... anyway i uninstalled the samsung drivers under control panel. rebooted computer then reinstalled them and Viola.. Odin works again

I'm in a little trouble here.

Well, Ive been flashing roms for a while now and I have an issue with my captivate.
Lets start in the beginning. I had my captivate on THS ICS rom and It was going great. But my captivate isn't that great anymore. The power button is broken, but I was able to go around that. (Sidenote: It turns on when I plug in the battery.) Anyway, I wanted to go back to stock because I did have the right bootloaders. (I couldnt get into download mode with the button combination. I thought it was the bootloaders fault. Im I wrong?) I wanted to switch to I9000 bootloaders but I had to start fresh. But before all that, I noticed that while I was on ICS rom, I was unable to go to download mode. I used to before, but it magically disappeared (I know it didnt, I know I did something to it but I don't quite remember when it happened.) So I was unable to flash a new rom, if I wanted to.
A couple of days ago, I bought a jig and it worked! It took me straight to download mode. So I decided to get my Captivate and make it go back to stock. So I opened Odin, it found my Cappy and I clicked start. But, it stopped at factoryfs.rfs. I waited a half hour and nothing. So I unplugged it and now it won't turn on. But it can still go into Download Mode and be seen by Odin but it just wont finish. I tried both odin one click and the regular odin. I looked everywhere for more than six hours and nothing came up. Please guys, if anyone knows what I can do to fix it, please reply.
I might have missed something, but just ask if you need any more info. Please help me.
Edit: I forgot to add this:
While I was on the ICS rom, I switched over to CM7 to see if the process of going back to stock would be easier. Thats when I tried to flash stock. It didnt work as well as I thought it would.
And I knew that I didnt have I9000 bootloaders because I installed the Icy Glitch kernel and each time I tried to have DIDDLE on it would go to deep sleep mode and I was unable to wake it back up.

As long as you can get to download mode you are fine. Try flashing a different stock from. Or using Hiemdell

I've tried both odin and Hiemdell. But with Hiemdell, it would always tell me that I dont have the drivers installed. So, it installs it for me. Even with the drivers installed, it keeps telling me that I dont have the proper drivers installed.

I have had this exact problem, where a bricked captivate can get into download mode but when restored to stock through a one-click, it freezes on the factoryfs.rfs. However, in my case after freezing at this stage, the phone was completely inoperable, and could not even enter download mode, so I am suprised yours could.
What works for me is to remove the battery, wait for a few seconds, put the battery back in, use the usb jig to enter download mode, and then WITHOUT the phone plugged into the pc, download and open this one-click file http://http://forum.xda-developers.com/showthread.php?t=731989.
Once the odin one click is open, plug the usb cable into the pc, and then into the phone. This one-click has never failed me. Hope this helps.

Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?

Juiceboy125 said:
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Click to expand...
Click to collapse
Depending on the CWM recovery you're in, you can sometimes use the search capacitive key to do the same thing as the power button will do.

I had the same problem you had with Odin stopping on flashing a file, turns out I was using a third party USB cable. I switched to the USB cable provided by Samsung when I bought my cappy and problem solved. Hope that helps.
Sent from my SGH-I897 using XDA

Finally!
Well, I got my Cappy up and running again. While I was stuck in the CWM I just decided to install Gingerbread using a One click and it worked. Now I'm back to CM9. Thanks guys for the suggestions. I guess I just needed to wait and double check everything.

[Q] Stuck in a soft boot (2nd time) trying Adb to get past the recovery file issue

I've spent weeks surfing the forums trying to get past the common recovery file rename and replacement with a system manager that is in super user mode etc. I don't know if it's the particular version of the recovery file that I've replaced being bad, but the first time I was soft bricked I was able to physically reset with a guitar wire in that whole ( was weird cuz it seemed like the button wasn't going to work cuz after minutes of turning the phone on and off it just randomly worked) Let me explain better because after chosing a different recovery file it soft bricked again however the reset isnt working. Ok so if I have USB cable in it brings up charging battery logo (showing the battery as dead which isnt true because the time it did reset... when it worked, the icon illuminated green suddenly. If the USB isnt connected upon turn on the samsung comes on indefinitely (forever)... tried with sim in & out etc. If I reset into download mode it just says downloading (let it go for three hours before stopping it once). Ive installed odin and tried to fix it that way... I made a Jig with 3X100k resistors and 1 1ohm 1watt ..( attempting to get the 301k resistance between the 4th and 5th pin in the micro usb connection... Didn't work ( used a voltmeter to test the jig but I didn't know what the reading should be but I saw a difference ( thougt the 1 watt addition was messing it up so I omitted that resistor. Still didnt work.... guess I could splurge and buy a jig online as a back up if I cant beat it differently. Lastly and more promising was downloading ADB and getting it running correctly... at first because of the inability to adjust bugging or not the device wasnt recognized... miraculously I left it alone andcame back and tried it... device is recognized... tried to adb pull recovery.orig file to C: to rename and push back but I didn't see it on the PC to rename after Adb says the pull file command was done. Thanks for your patience with all this info on first message. Im new to this. Im sad that I have to get into this just to take control bake but there is a user and or group that is runing in my background and changing my permissions and running so many processes its like slow motion. doing this so I can run the roms to control my traffic and get some Ram back... I wish I could just ask him to please stop. Thank you for any help.

If I reset into download mode it just says downloading (let it go for three hours before stopping it once)
Click to expand...
Click to collapse
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.

Odin
ApexPredatorBoids said:
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.
Click to expand...
Click to collapse
Odin wasn't recognizing the device before at all, but since I set up ADB and ran the adb sync comand, now when I run Odin it recognizes the device as com5 not com++ (not sure if that matters). I'll try and start a pit and see what happens.
If I went back to stock what kernel do you recomend I flash and do you know a good recovery file to replace the original one to get past the signature verification when reinstalling packets.

Flash entropy's dd kernel. There is no need to replace any recovery file in GB (that's only on froyo).
Sent from my sweet & buttery Infuse

Help Just Soft Bricked New Samsung Galaxy S Blaze 4G SGH-T769

I followed this links w.mobilescommunity.com/android-tips-tutorial/208463-how-root-samsung-galaxy-s-blaze-4g.html[/url] instructions to a "T" and when the phone came back on it stops at the welcome screen no matter what. I tried to install ClockworkMod Recovery per these instructions /theunlockr.com/2012/04/17/how-to-root-and-install-clockworkmod-recovery-on-samsung-galaxy-blaze-4g/[/url] and it seemed to work as I get the OMR mode when I try to get the download screen without having it already cable connected to the PC. When I have it connected to the PC I am able to get to the "Download" mode. OI! I never have had a problem rooting before. The stock OS ICS 4.0.4 was on it and I bought it new from T-Mobile and then it did the OTA update a week ago. I have had nothing on it other than stock and a few camera apps. I have already tried to return it to OEM with the OMR recovery but its still the same, always booting to the welcome screen. When I try to get it into a mode, ether the recovery mode or the download mode, it sometimes vibrates several times and then "May" go into one or the other depending if its cable tethered or not. HELP PLEASE, I disabled and this is my only outside contact short of coming into town to use the Internet at a cafe. Thanks, Jeff

Blaze Soft Brick
fallendaemon said:
I followed this links w.mobilescommunity.com/android-tips-tutorial/208463-how-root-samsung-galaxy-s-blaze-4g.html[/url] instructions to a "T" and when the phone came back on it stops at the welcome screen no matter what. I tried to install ClockworkMod Recovery per these instructions /theunlockr.com/2012/04/17/how-to-root-and-install-clockworkmod-recovery-on-samsung-galaxy-blaze-4g/[/url] and it seemed to work as I get the OMR mode when I try to get the download screen without having it already cable connected to the PC. When I have it connected to the PC I am able to get to the "Download" mode. OI! I never have had a problem rooting before. The stock OS ICS 4.0.4 was on it and I bought it new from T-Mobile and then it did the OTA update a week ago. I have had nothing on it other than stock and a few camera apps. I have already tried to return it to OEM with the OMR recovery but its still the same, always booting to the welcome screen. When I try to get it into a mode, ether the recovery mode or the download mode, it sometimes vibrates several times and then "May" go into one or the other depending if its cable tethered or not. HELP PLEASE, I disabled and this is my only outside contact short of coming into town to use the Internet at a cafe. Thanks, Jeff
Click to expand...
Click to collapse
----- Did you ever get your Blaze fixed?....

pretty much the same problem i have!!! i currently have the samsung galaxy s blaze and rooted it to the custom rom from konane using the odis program, it said passed and auto rebooted my phone, but when it gets to the home screen where you touch the android to set up your phone like its brand new, when i hit the android bot all that happens is a message force closing a bunch of apps appear. i can get to the download mode to install new roms and i've tried to re root back to the stock rom but now my computer doesnt recognize my phone. i've downloaded and installed the samsung drivers from several different forums including the ones recommended here but still nothing. what im wondering is if theres a way to install the rom or driver from an sd card to the phone or something else that im missing, or is my phone just screwed? any and all help is greatly appreciated.