so i recently flashed apex rom to my phone, and its my first 2.3 based rom. i started having some issues with these weird colored likes kinda like static on an older tv on the screen whenever i was booting into recovery and then recovery itself wouldn't show up at all. i figured it might have something to do with an older version of clockwork or something that didnt support 2.3 so i went into rom manager to update it, this is where it gets kinda weird. captivate wasn't in the list of choices for which phone i had so i picked one, and now my phone wont boot past the at&t logo. ive tried all the key combos i can find to try and boot it into download to odin it but i can't get anything to work. has anyone had this problem before?
Did you flash the correct (gingerbread) bootloaders?
And you probably should have stayed on the cwm version that your rom came with.
im guessing i didnt flash the right one since it seems to have broken it. and i dont think the rom came with cwm because it didnt change from before/after i flashed. nor was it working.
You might want to start over from scratch (stock), reread the instructions. Download everything aging (just in case you had a bad download). and flash once more.
cmw is built into every kernel except stock, that shouldnt be a problem
good luck
caepha said:
so i recently flashed apex rom to my phone, and its my first 2.3 based rom. i started having some issues with these weird colored likes kinda like static on an older tv on the screen whenever i was booting into recovery and then recovery itself wouldn't show up at all.
Click to expand...
Click to collapse
Yup. I got the same horizontal noise lines when flashing Cog5 v1.0 . I was sure that it was a soft brick. Used http://forum.xda-developers.com/showthread.php?t=1127249 to go to Stock 2.3.3 and it worked. Began from scratch. Hope this helps.
the main problem is that i cant get into recovery or download mode. if i try to boot the phone at all it freezes, either on the at&t screen or if i have the usb plugged in, the circular lines loading screen. im thinking im gonna have to run down to radio shack and get some resistors for a jig.
Related
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
cumanzor said:
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
Click to expand...
Click to collapse
Did you ever get this problem fixed? The reason I ask is because I'm in this same situation.
We seem to be having the same problem also... Nothing has worked for me so far
http://forum.xda-developers.com/showthread.php?t=960419
Pull your battery, pull your sd card, hold the volume button and plug in the usb cord, this will get you into download
Sent from my GT-I9000 using XDA App
Keep hope alive glaze!
Sent using XDA App
Im going to get a jig hopefully all goes well.
So I have my new Rogers Captivate for 2 weeks and I decide I would like to flash a Custom ROM onto it. I duly search the forums, reading the stickies and things like that.
I find the guide on how to flash Custom ROMS with videos, decide following these will be my best guide. So I download the ODIN one click as told, get the phone into download mode and flash it back to stock as the video showed me. Though this completed successfully, I ended up with an AT&T boot loop after it was done with my button combo to access download mode broken. So after I do some more searching on the forum, I find out this is not an uncommon problem. The solution is to make or buy a USB Jig. So I order a USB Jig off eBay. Guy I bought it from was great, shipped it out to me and it arrived today. I get it, pop it in and bam. Phone goes into download mode.
Next I follow the instructions a few other Canadian Captivate Owners have posted and flash it back to Rogers 2.1 Stock with Odin 1.3 and no pit file. I still get the AT&T logo on boot but it gets past it now. Goes to the I896 boot screen, then the Animated Samsung Bootscreen, then to the Rogers Boot screen with the dots moving on the bottom. I am patient and wait a bit. It finishes with that and then goes to a completely black screen. At first I thought the phone as off, but I touched the buttons on the bottom and they light up. They stay lit up as well.
Thinking something has gone wrong, I reflash it again. Same thing happens. I try flashing the same ROM with a pit file from the Odin download. Same thing happens again. Nothing but a black screen and the buttons lit up.
I am at a loss as to what to do next, as I have searched the forums and not found a good answer for this problem. Should I try flashing a new stock ROM onto it? What is my next move here?
Phone:
Rogers Captivate 10.10
ROM currently installed:
I896UXJI2-homebinary.tar
*EDIT*
Nevermind, I managed to fix it. I had the AIO Captivate Tools 2.6 (Rogers) installed and after the phone booted it dutifully reported that it was in debugging mode. So I selected load custom ROM and selected Firefly 2.3. It goes through its thing and clockwork recovery installs. I select to install the ROM.zip AIO Tools copied over and after it does its thing. Presto, a few minutes later the phone boots into Firefly 2.3 with no problems. I am running the ROM I wanted and I am a lot happier now.
I tried to flash the boot image for my first custom rom using easy kernel flasher, and my Vivid is now stuck at the white HTC screen. I then realized that I had used rom manager to flash CWM, even though I had already flashed the custom CWM from the superguide. Is this what caused my phone to hang at the HTC screen?
Is it safe to pull my battery? What is the next step, repeat step 2 from the superguide and then reflash the new kernel and rom?
I apologize if this has already been answered, I just haven't seen this exact question elsewhere and I don't want to pull my battery without being sure that I won't brick my phone or make my problem worse.
Rom manager does not work for our phones. That is why your phone is stuck. I remember another post like this. The guy pulled the battery and flashed the new cwm image without rom manager and it worked. I believe you would start at step two to correct your issue. Let us know how it goes for you.
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
androuglas said:
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
Click to expand...
Click to collapse
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
I tried again and it went in to h-boot, and i was able to reinstall the custom vivid CWM. But now I'm not sure if the kernel flash which started all this worked. Is there a way to find out while in recovery?
Should I reboot the phone now, or just flash the rom I was planning on flashing originally? Or should i try to return everything to stock and start all over?
cbronson41 said:
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
Click to expand...
Click to collapse
Thanks man. I got into recovery and fixed the CWM problem, but now I'm not sure what kernel I have running so I don't know if its safe to reboot.
Though I know how to use CWM I couldn't tell you how to check your kernel and whatnot from there. Best thing I can think of, or what I'd do, would be to wipe everything out and restore a nandroid, granted if you have one I've never really messed with kernels untill now so I don't even know if that would work
I realized I could just reflash the kernel while I was in recovery. It hung at the htc screen on the reboot like before, but i just pulled the battery, went back into recovery, flashed the rom, and now everything is working perfectly with the new rom. What a relief.
I think the original kernel flash may have actually worked, and I just freaked out when it hung at the htc screen and assumed it was because of the rom manager/cwm thing. It may have been fine all along.
Here is something that will help with flashing kernels.
http://forum.xda-developers.com/showthread.php?t=1423151
Flash Image GUI
ok i did the same thing awhile ago, i flashed new CWM then insatlled rom ...the Kernal did load thats the reason you got the white screen ..so just go ahead and load your rom you should be fine
Hello XDA,
For quite some time now I'm experiencing a rather irritating bug on my Galaxy S.
I have no idea on how I got this error, I just did. It pretty much showed up randomly.
When I start-up my phone I get a few weird screens, it looks like my phone is broken. The screens look like a mix of all possible colors the screen can produce, it looks like an ugly, digital rainbow (Currently charging my digital camera so I can provide a picture).
After the weird displays, the Darky's ROM intro pops up and everything goes perfect, I don't experience any problems whatsoever.
I now want to install a different ROM or Kernel but I have no idea on how since I cant go into the clockwork thing, it gives a weird screen like when starting up so I can't see anything properly.
I do however have the ability to connect through USB, any idea's?
Thanks,
Joris
Try to install ROM manager (from market) and try to flash new CWM.
Thanks for your answer!
"ClockworkMod Touch Recovery is currently not available for your device"
Thats the message I get when I try to do that :/
EDIT: hah, I think I tried the wrong option, I now picked "Install custom ROM" which made me select the zip and then boot into clockwork mode.
The clockwork mode thing is responding to what I enter (when the rainbow screen comes I need to press the power button to go to cancel all and boot up the phone)
Hmmm. I would probably reflash with odin. But never actually heard about your problem, so don't take my advice and wait for someone more skilled ;-)
Edit: So the CWM is working?
No, the problem is that when I try to "Install a ROM from SD Card"
it boots into ClockWorkMod and I have no idea on what to press, I'm pretty sure the clockworkmod is actually live, its the the screen thats ****ed.
This is what I see...
You probably don't have the gingerbread bootloaders, right? If so, that's the cause for these graphical glitches..
Also, don't use the ROM manager to flash a CWM or anything..it doesn't work properly on the SGS..
Sent from my GT-I9000 using Tapatalk 2
Yes that could be it, I think I got this thing since I updated to a later Darky ROM, a gingerbread one.
Any way to fix it?
HAH, just downgraded to stock rom/kernel then installed new ones.
[SOLVED -- Read my last post]
Posting on forum was my last resource, but I've tried literately almost everything I can possible find.
I already bricked my phone and had to unbrick, do everything (update firmware etc) all over again.
I am at a point where I am afraid to do something new to my phone now without knowing what they are...
Please bare with me, I am not familiar with exactly what flashing is or whatnot, I just followed the instructions and got where I am....
K, recently I decided to wipe my phone CLEAN and update to new CyanogenMod 9 from factory mode.
So, I have Captivate, I897. It was ECLARE with 2.1 firmware.
I have updated to 2.3.5 (Gingerbread [I897UCKJ2]), Rooted.
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
I installed Clockwork mod (Free version).
My goal is to install CyanogenMod 9, and part of the process requires me to enter the CMW Recovery Mod.
I dont even know what this looks like, but all I know is whenever I boot my phone, after the AT&T logo animation it seems to go into this "messed up" screen, where as if my phone is broken. Stays there for 3 seconds and then continues to boot back to its OS.
In ROM manager, it says Flash ClockworkMod Recovery (You must have the clockworkmod recovery installed to flash and restore ROMs!)
Another option within ROM manager is, Reboot into Recovery (Boot into Recovery mode for manual management.), which if I do access it, it takes me back to that AT&T logo animation and that "messed up" screen again, but this time it stays there. Where all kinds of colored pixels are on my screen as if my screen is broken. It will only continue to boot back to my OS if I press power button or some sort.
Im guessing that's my Recovery Mod, which my phone for some reason cannot see?
So I tried "Download ROM (Upgrade to ROM Manager (premium) to access the full list of ROMs!", hoping this may cure that messed up screen effect, which I think is the Recovery Mod for all I know... When I click to install, it gives me Confirm Phone Models. None are my phone model for me to install.. (It only gives me Google Nexus S / Google Nexus S 4G / Samsung Epic4G / Samsung GalaxyS i9000).
Earlier, I was looking at this, http://forum.xda-developers.com/showthread.php?t=1127578
which is a way to fix recovery mod(?) But I have NO idea how to even install those files... Maybe not the .tar file but the other one.
Please help? Am I the only one experiencing this kind of problem? Couldnt find anywhere else on youtube / google / forum..
Thank you VERY much in advance, really appreciate it..
-Dan.
danroh said:
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
-Dan.
Click to expand...
Click to collapse
This is your likely problem right here. The Kernel that is installed during the rooting process and typically when you install custom roms is what is responsible for installing and therefor you being able to access the CWM recovery. Flashing back to the stock kernel likely messed things up for you.
http://forum.xda-developers.com/showthread.php?t=1300843
Now if you follow that link it will take you to several one click options for flashing your phone to stock gingerbread but with a kernel containing CWM. Also keep in mind that it is possible you could have wifi issues if you've had them in the past, but if your goal is to get to CM9 just ignore the wifi for the time it shouldn't be an isuse in the end.
Hey OP,
See this.... TRusselo's Flashing Guide
Sent from my SAMSUNG-SGH-I897 using xda premium
You need Gingerbread bootloaders.
Thanks guys! I figured out the problem and solved it!
Like you guys said, I didnt have the bootloader. The gingerbread I installed was the no bootloader version. After reinstalling to the one with bootloader, I was able to access the recovery mod and that "rainbow screen" glitch was no more.
Thank you!