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.
Related
To start, I was using I9000XXJP2 firmware on an unlocked samsung I9000 from Bell. I installed a lagfix a few days ago and everything was working fine. The phone was really slow and freezing a lot today so I decided to restart. Ever since then, the phone is stuck on the Samsung S screen (not the one with the triangle). I can get into download mode just fine and i tried reflashing XXJP2 using odin back onto the phone. Odin does everything fine up until i see a blue 'reset' on odin and the phone is in recover mode with the options asking for me to restart the system etc. I restored to factory settings from there and even cleared the cache and restarted but it is still stuck on that "S" screen at startup. Odin only says "pass" once the phone is disconnected. So as of yet I haven't been able to flash a working ROM back on the phone. If you have any ideas as to which ROM i should try, if you could place a link with that, I would be very grateful.
I've had this problem myself a couple of times (just happened today in fact).
Boot into recovery mode (vol-up, home & power). Do you see any error messages in yellow under the menu?
I was unsuccessful at reflashing any of the Froyo firmwares so I reverted back to the last official 2.1 firmware from Bell JH2. Since I was coming from a 512 pit firmware, I didn't repartition or specify a pit file. This ended up working for me. I've since flashed to JK3 and am about to go back to JPU.
Reply:
I actually do see an error message E:can't mount /dev/block/mmcblk0p1, Can't mount SD card.
I should mention that Im using the unlocked bell phone on fido. Will i lose the unlock if i downgrade? Also, if you could point me to the site where i can download bell firmware, that would be awesome. I went to samfirmware.com and they dont have canadian versions there.
Unless one of the pros comes by and says otherwise, I understand that's the error indicating internal sdcard issues.
However... if the thing is dead, you can't hurt it more by trying some fixes
You can get the official and unofficial Bell firmwares from samfirmware.com, you just have to look in the US section. You want the firmwares starting with "i9000UG". Here's direct download links for you:
JH2 (official 2.1)
http://www.multiupload.com/ZNBT2RY5Y0
JK3 (unofficial 2.2)
http://www.multiupload.com/WTZGSKJGPF
JK4 (official 2.2)
I've heard people flashing this via CWM but I haven't see the files.
Also, I've seen references to people saying their phones begin working again after this error msg after they've left the battery hour for hours.
Let us know how things go.
Reply:
No go. When i flash to 2.1, it just shows the "S" screen and turns off. When i flash to 2.2, does the same thing as my first post. I still can get to the download screen through all of this so I hope its not messed up too bad.
I tried several times this afternoon before it worked including clearing data/cache.
Although, I had a different error message so you might be SOL in the end.
called samsung
So I called samsung this morning and they basically said they won't repair it because Bell handles repairs. Since I dont have a bell account, I can't get it repaired. I keep reading on forums that if you can get into the download mode, if you see the battery icon when you plug the phone in, its not totally bricked so i still have hope yet everything I've tried doesn't work. I tried to adb into the phone in recovery mode and it detects it but says I dont have permissions to push files onto the phone. If anyone can tell me what possibly went wrong and if it is fixable, how, that'd be awesome because right now this is a very expensive paperweight.
OK guys I really badly need some help. My phone is in a non-workable state and I am starting to run out of options.
I did some mistakes but I will try to take out the details to list mostly the fact, hoping someone will take the time to give me directions.
- I have a galaxy s I9000 (switzerland/orange)
- I had upgraded to 2.2 via Kies.
- I got tired of the phone becoming increasingly slow. I found out about voodoo lag fix. I read 3000 forum posts, documentation and stuff, and when everything seemd easy enough, I installed voodoo via Odin.
- Here problems started. After installing voodoo, the phone booted, but the robot voice said "convert data partition. Not enough space on partition". Then again. And again. It was stuck in a boot loop. This problem doesn't seem to be documented anywhere i could find. The only instructions I could find on how to disable voodoo were to create some files on the disk, not very helpful when you can't boot the phone.
- I found a couple of threads with people who had the same message, and the advice their were given was to flash another rom.
- So I went to samfirmware.com and downloaded 2.2.1 for I9000 (JS8). I installed it through Odin. The phone booted, showed me the Galaxy S screen, then went black. Then it would vibrate every 20 seconds or so. Once, then 3 times in a row. I waited 30 minutes because in some places it said that may take long, but the situation didn't change. I rebooted, tried again after taking about the battery, wiped data, reset factory settings etc. The phone state wouldn't change, and I started to get a little desperate, because this was a stock rom, and if that didn't work...
- I read 3000 more threads, and phone a guy who had been in this situation, and got out of it by first installing "Eugene's JK2 froyo that never bricks" and then after wards reinstalling the stock rom.
- So I installed Eugene's rom. I knew it was trouble that it was a vibrant's rom, but I figured, I had read everywhere that as long as your phone supported download mode you could still always re-flash a new rom, so I decided give it a try.
- And the phone booted. Asked my pin, loaded stock android and all. I was happy at first, but then new trouble came. Now, whenever I plug in the USB, the phone's screen goes black after 4-5 seconds. When I unplug it, phone reboots. No charging battery appears when I plug the turned off phone on the charger.
- And worst of all, the buttons got mixed up. Vol up is vol down now. But more of a problem, 3 button recovery and 3 button download mode don't work anymore. I couldn't find a way to get them back. So I can't flash a new rom with Odin :-/.
- My latest was to install rom manager since I can access the market. I downloaded the tedgy rom. Installed the "clockwork recovery mode" from Rom Manager. It asked me if I had I9000 or vibrant, wasn't sure what it expected since I have now a vibrant rom on an I9000, but I put in I9000. Then I reboot telling rom manager to install Tedgy. I get a recovery mode screen which offers to reboot/reinstall packages/wipe data, then does a couple of operations, and finally gets stuck on :
can't open /cache/update.zip
(bad)
installation aborted
So there I go, with a vibrant rom on my I9000 (rooted, at least), a phone that can boot a half-functionnal android, but with a useless cable plug, an unchargeable battery, and a download mode I couldn't find... And waiting for my wife to get back with her phone so I can charge my battery again...
Any help or lead to help me get another rom installed on this phone again would be *greatly* appreciated. What other ways do I have to access download mode ? Or is there a way to get to it despite my buttons being messed up ? Maybe the rom manager issue can be fixed ?
OK well I got out of it somehow.
In case someone else had this same issue, here's how I got out of it :
1) Install ADB.
2) launch Odin
3) go to adb folder in command line and type "adb reboot download" but no enter just yet.
4) plug the usb cable on the phone.
5) type enter in the adb shell in the small window of opportunity you have before the screen goes blank. This reboots the download mode and allows new flashing via odin.
Any answer for this thread?
Did you fix the problem?
I'm stuck with the same case...
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.
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
ktvanhorne said:
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
Click to expand...
Click to collapse
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
BWolf56 said:
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
Click to expand...
Click to collapse
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
ktvanhorne said:
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
Click to expand...
Click to collapse
My guess is that something got corrupted, so yes, software issue. Find the required Odin and 2.3 kernel for the I9000 and flash them in download mode. It should run fine after that.
Got things resolved
Thanks for the help. I tried to follow your steps, but I could never get the phone connected to the PC. It would charge, but not connect to let Odin in. (It will connect to another PC without issues. I uninstalled and reinstalled the drivers, but no dice). However, in the process of putting the phone into download mode and rebooting it back somehow got me into the recovery screen. I did a factory reset through there and it worked.
Thanks for the help of all the contributers to the site.
K
So I decided to flash a rom. I haven't done so on this galaxy s6 edge. I've always done it on my previous galaxy phones. The phone already had all the pre-reqs for EXTREME SYNDICATE. Once the phone rebooted to download, I used odin to push out the new OE2 FLASH ME. After that was done the phone just went into a boot loop. I double checked and made sure all the files were correct.
Now I am at a point where even using odin with stock image just goes to samsung splash screen and song then just gives me a Startup Failed - Please connect verizon repair etc.
Is there anything I can do on my end or am I screwed with this phone now. I can still go to download mode and the recovery mode that lets me wipe, reboot etc. But nothing seems to work. Unless I am missing something here.
All help is appreciated, thanks!
Mods can close this thread. I tried everything. Eventually flashing different OE2 and OF1 finally got it working even though I flashed the stock ....