Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
ApplCobbler said:
Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
Click to expand...
Click to collapse
I feel your pain. Been there, done that. Although your process of bricking reminds me of a more sophisticated approach....lol....mine was out of total complete noobness.
Question:
1) Can you manually boot into download/ recovery manually using 3-button combo? If so you have hope (meaning your phone is basically "un-brickable").
-Bet that made you feel better huh?
-If you can't use 3-button to go into either modes, then you are in the same boat as i was. Hope you are still within your 30 days, or at least warranty. One way to tell if you can/ can't go into either modes is to check your "Batch #."
a) remove battery
b) look below your Serial Number
c) if your Batch # = 1007 = You are safe
d) Batch # = 1008 = good luck
2) When you say Brick, do you have the unfortunate "Phone (!) PC" screen? If yes, then its a "soft brick." If No, then its a "hard brick." I would start to worry.
3) According to your post, it sounds like you have the Regular Odin and NOT the One click version, correct? If you have regular Odin, i would at least try the One click. Regardless, both versions should be able to get you back to stock (JF6), but we already know how well your current version Odin has gotten you.
If you need help, there are TONS more knowledgeable people here in the Captivate forum than I. They should be able to help.
Good Luck!
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Stop trying to flash Froyo. Flash back to stock then master clear. Then go read the threads in the development section of the forum before flashing anything. The fact that you tried to apply Voodoo to Froyo and you tried to use one click lagfix on Froyo shows you haven't read and don't know what your doing. You corrupted something by flashing incompatable stuff, flash back to stock and master clear for now. Read a bit and then flash Froyo.
ApplCobbler said:
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Click to expand...
Click to collapse
LOL . I as well. I know enough to be dangerous.
Now, on to business. If you actually read what Rhiannon has posted for you, and click on the actual link itself, you will realize that the version of Odin you are using (yes the one click) is NOT the correct version for flashing back to stock (JF6/ Eclair.....NOT froyo). Remember, if all else fails....."The One must return to the Source...." <-----Plus 9,000 to whoever can guess where thats from.
Obviously your phone falls within the 1007 since you have the Luxury/ Advantage of manually entering Download/ Recovery mode....i wish i did.
Rhiannon224 said:
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
Click to expand...
Click to collapse
Well Said!
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Click to expand...
Click to collapse
I see you are still on Cog 2.2 B5......dont care for 8 or any of the new ones? Or Sheps? What's your story?
Mine is simple....Patience. lol
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
Click to expand...
Click to collapse
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Rhiannon224 said:
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Click to expand...
Click to collapse
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
spartan062984 said:
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
Click to expand...
Click to collapse
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
ApplCobbler said:
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Click to expand...
Click to collapse
Again, sorry if I sounded harsh, i am just trying to help you get out of the mess you're in. You can flash Froyo in the future you just need to learn about these ROMS and fixes so you don't have these kinds of headaches. I will stop repeating now. i really hope this works. I know your stressed and wasn't trying to give you a hard time, I just thought you were missing something and I am from NY and we are pushy Let us no if you get it working.
I have made some mistakes along the way too and it was because I didn't read the instructions clearly so I do understand how you felt.
Rhiannon224 said:
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
Click to expand...
Click to collapse
""Sory to hijack the thread""
I started it. No worries. I too would love to have voodoo. So far, with stock OS, ext2 + OCLF seems to work for me....for now. Keep in mind that i too would like to have the functionality of a Phone. That was my intention in the first place...lol.
Related
If you've flashed anything other than a direct from the factory flash, and are not yet aware of the dangers that may be faced when flashing to the eventual release of CYAN, then please read the next posting.....
Be aware, this is "Technically" a I9000 firmware. But with a few changes and a dash of Guru and, BAM, we got 2.2 on our Vibrants. A direct flash of the current I9000 Froyo blend won't work, so don't try it. But this will. Its running smooth and clean so far, with the only issues being a reversed volume key, and a I9000 boot screen. But there's no boot sounds or Tmobile flash for that mater.
Update: Currently no data. But should be an easy fix. Fixed
Flash at your own risk, yada yada.....
Flashing is identical to my other posting. So a copy and a paste I shall go....
Using Oden, you'll first need to put your device into Download Mode. From a device still on Vibrant firmware, you'll need to hold down the "volume down" button while booting. If you've been playing with I9000 firmware's like I was, your volume has been reversed and the reverse applies to you, "up volume". If you still can't enter download mode, you may want to try holding down the volume key + the power button. Plugging in your USB cable may also aid your efforts to enter download mode.
Once in download mode, use the attached files below to flash your device. I'll give you a quick run through of Odin, but for detailed information I'd suggest this YouTube video. Keep in mind that in this video the poster is actually flashing an I9000. But the process is similar in all respects with the only difference being the key combination used to enter Download Mode.
A system wipe beforehand is recommended. If your having Market issues after flashing, this is more than likely the culprit.
1. Open Oden.
2. Extract the .pit file, click the PIT button in Oden and load the file.
3. Extract the three .tar files from the firmware file, load each into the three fields directly beneath PIT. These being PDA, PHONE, and CSC.
4. Under Options, be sure the following three boxes are checked. Re-Partition, Auto Reboot, and F. Reset Time.
5. Put your device in download mode and plug it in. Pay attention to the "COM" number that's detected in Oden. Your going to want to work on "COM7". If your receiving messages that the driver failed to install, or couldn't be found, extract the attached drivers file and direct windows to search for the driver there. I've seen better results using this manual approach, versus the installer.
6. Now press start, sit back, and be patient. In my case, the install only took around a minute.
After installation has finished your sent to recovery, just hit the power button, which should be on reboot, and your done.
FYI; I stopped and rebooted my phone at every sequence during this flash process, and I never bricked. Not necessarily intentionally, but I am very rough on my toys. Even after freezing or stalling partway through cache setup, factoryfs, you name it, no paper weight. This phone is stout!
Please keep me apprised of your results.
Required Tools:
Odin3 v1.00...
depositfiles
Hotfile Mirror
Pit file, as mentioned in other threads, the 512 seems to work best...
Pit file
Hotfile Mirror
I located the following files on Softpedia. I'd recommend manually installing your drivers. My results using the installer weren't great...
Windows x64 Drivers on Softpedia
Windows x86 Drivers on Softpedia
Firmware:
Model number: GT-I9000 (We'll fix this)
Firmware version: 2.2
Baseband version: T959UVJE8 Updated to T959UVJFD
Kernel version: 2.6.32.9
Build number: GT-I9000-eng 2.2 MASTER 332 test-keys.332
Froyo By MS_Guru:
I'm glad I didn't release this, but I will keep it maintained in the event that its needed for brick explorations. Any Devs interested in any part of it, lemme know.
Reserved...
Firstly I'm glad someones finished this, its the end of the month, and the time when my business shifts into high gear. Which is why I've been MIA the past few days. But I have made a few observations which seem worthy of mention.
Firstly, to those of us who have been flashing I9000 builds, it is in fact true. Flashing directly to the coming release of Cyans Froyo with anything but a Factory T959 boot, will more than likely brick your phone. But now that we know this, something can be done about it. As it turns out, people like myself, who started flashing alien firmware right off the bat, were actually giving our devices what could be thought of as flu shots. So much so, that when I eventually went and flashed I9000 Froyo directly, my device had enough of an immunity to weather the storm and eventually thrive. Which I think is pretty interesting.
So if your in this boat, don't worry your not screwed, you should just be a little cautious until a clean fix is found. Don't take this to the bank, but through my own I9000 Froyo build, and spending time playing with the brick, I've made a few discoveries.
1. If you've flashed anything that's reversed your volume keys at any point, you have the brick potential.
2. You can have flashed a few different firmwares and still walk away clean. If you remember exactly what you've flashed, go back and look for a file named "boot.bin". Its almost always in the PDA section of the flash. So just open the "PDA.tar" file with "Winrar". In all seriousness folks, don't take this to the bank until more people can verify this. If the firmwares you flashed didn't contain this file, you may actually be clean.
One thing I did see a good deal of, am but with what little time I've had the past few days, this file was more often than not in the PDA when someone bricked. I thought about after recalling the following....
User fykick mentioned...
I can confirm that jm1 and jm2 also brick phones.
Click to expand...
Click to collapse
A review of those Firmwares does in fact reveal a boot.bin file. This should also be verified by someone else. But I believe this to be either a core part of, or the actual Recovery and Downloader in the raw, and the cause of most headaches. Another sign of trouble would be red lettering in the upper left corner of your Downloader page?
So to summarize, flashing other Firmwares, and never having inverted your volume keys. As well as the lack of the "boot.bin" file in those same Firmwares, and the lack of red lettering on the downloader page, MAY in fact mean you've caused no harm and can flash the pending Cyan. But wait til others have chimed in, these are only my observations at the moment.
So there's still more to come from all this, both from myself, and other devs. But just so you know it wasn't a total wash. I've been keeping track of apps as I went though all these firmwares, and let me say, I'm gonna be able to contribute some first class apps to our impending firmwares.
Notable apps...
1. Very clean Samsung factory direct WPA/WPA2 tether, and we're talking easy enough for a retarded monkey to use. No clue if we'll see it directly in our providers flash, as most American providers are against tethering.
2. Video codecs that integrated into the existing video player, but only seem to be included in European Firmwares. Found that one out accidentally when a few music videos got included in a transfer. The same files wouldn't play on a stock Vibrant.
3. More than one lockscreen, all super clean, and some with amazing media, and notification integrations.
And many more...
That's it for now. Look for more to come though.
it's been strongly advised by the programmers working on CM6 to not flash to 2.2
7/28 9:25AM
Scepterr:
"Vibrant and Captivate users do not flash the i9000 JP1 & JP2 Froyo release it does not work correctly and you can not revert back." I would suggest to stay away from all that is I9000 for now.
Wesgarner has started work on the Galaxy S and it is going "fine".
designerfx said:
it's been strongly advised by the programmers working on CM6 to not flash to 2.2
7/28 9:25AM
Scepterr:
"Vibrant and Captivate users do not flash the i9000 JP1 & JP2 Froyo release it does not work correctly and you can not revert back." I would suggest to stay away from all that is I9000 for now.
Wesgarner has started work on the Galaxy S and it is going "fine".
Click to expand...
Click to collapse
I can co-sign this. You WILL brick your phone. I will wait.....
Talk about giving someone just enough rope to hang themselves. . .
I want to try this out so badly, but I can't risk screwing up my Vibrant. I'm a huge follower of CyanogenMod, so I'll wait.
Makes me laugh...
I think they just wanted to be first... Almost there guys. It really is running nicely. And honestly, there's no hope in hell of brickin this phone, I've been trying. Shes a stout little B..
MS_Guru said:
I think they just wanted to be first... Almost there guys. It really is running nicely. And honestly, there's no hope in hell of brickin this phone, I've been trying. Shes a stout little B..
Click to expand...
Click to collapse
I doubt they were going for first. CM is more about being the best than being the first.
MS_Guru said:
I think they just wanted to be first... Almost there guys. It really is running nicely. And honestly, there's no hope in hell of brickin this phone, I've been trying. Shes a stout little B..
Click to expand...
Click to collapse
Cool. If you can get data working, I'll give it a go when I get home so I can run Odin. No winders with me right now.
Oh, and verify that we can revert to a prior backup.
No...its true. These methods will brick your phone. I thought it was just something i was doing wrong but after going back from xjm1 and 2 i have bricked two phones....so im gonna delete my post as this is now a somewhat verified fact for me.
I warned you guys last night to not flash this. Wait for the real thing. Not like our phones are not already amazing.
Well I'm not sure what to tell ya, but I'm bookin right along here. And when I say I've tried to brick, I'm not joking. When I first got this thing I tried shoehorning every ROM, Flash, Recovery, I could get my hands on to this phone.
Can someone do me a favor, go into clockworkmod and give me a breakdown of the keys and there associated numbers? I've got clockworkmod on already, but without a home key you get stuck in recovery. A quickie remap, and I'll be done.
IE.. Volume up is 164, I think? Volume down, Power, and each touch key. Theress a key feature in there, but don't wanna flash back just for that.
s15274n said:
I warned you guys last night to not flash this. Wait for the real thing. Not like our phones are not already amazing.
Click to expand...
Click to collapse
I flashed mine before this firmware. But it was an overseas firmware and when i tried to revert back my phone went totally dead.
i'm pretty sure with this you would have to go back to a stock kernel and then do a nandroid to stock 2.1 you made w/ nandroid...i could be wrong tho..but i don't wanna mess with my kernel unless i have to so i'm going to wait till this is an rom version of the .zip flavor and it's ported for the vibrant. or just wait for CM6, but the only thing i'm worried w/ cm6 about is, are we going to lose allshare/tv out/ 5.1 headphone simulatioin / the music player / dialer / phonebook / things i actually like from the samsung rom... but yeah i will flash this puppy once ported.
MS_Guru said:
Well I'm not sure what to tell ya, but I'm bookin right along here. And when I say I've tried to brick, I'm not joking. When I first got this thing I tried shoehorning every ROM, Flash, Recovery, I could get my hands on to this phone.
Can someone do me a favor, go into clockworkmod and give me a breakdown of the keys and there associated numbers? I've got clockworkmod on already, but without a home key you get stuck in recovery. A quickie remap, and I'll be done.
IE.. Volume up is 164, I think? Volume down, Power, and each touch key. Theress a key feature in there, but don't wanna flash back just for that.
Click to expand...
Click to collapse
Vol Up - 42
Vol Down - 58
Power - 26
Menu - 158
Home - 139
Search - 107
Back - 28
Well it is pretty well done, just need the key numbers. Hint hint... Go to recovery and click the option for key... something or other. Its really really easy.
Thank you ttabbal ...
sounds like MS_guru is more then the average user.
Good luck in your modding. Hope to hear more great news soon!
@ MS_Guru,
Hope you get it all figured out
Man...I'll pass I did the other "stock" "pre release firmware" and I damned the moment I did it. I'm back to stock with 3g and camera working thanks to scepterr but still with euro baseband. No thanks!
Well If it is just a fluke, Time will tell. As more people are willing to flash a foreign rom for Froyo than just a faster kernel. So we will see if its just an unlucky few who have bricked their phones or when all the people who flashed to this revert back and brick their phones. I know for a fact I have bricked 2 phones, reverting back to US firmware from any firmware after JG5...IE: jm1 and jm2. The first brick I assumed was a fluke...but then when the second one from the same method...I stopped testing my luck. I know before when using JG5 and before, I was having success, but something in JM1 and after are causing bricks. There is no guarantee that this bug is not present in the XP1 and XP2, but after two bricks, Ima hold off til CM6.
pychobj2001 said:
but the only thing i'm worried w/ cm6 about is, are we going to lose allshare/tv out/ 5.1 headphone simulatioin / the music player / dialer / phonebook / things i actually like from the samsung rom... but yeah i will flash this puppy once ported.
Click to expand...
Click to collapse
I hear ya. There is plenty I don't like on the phone, but there are some things I would like to keep.
silly me decided to install a custom battery icon. In the description for the mod on app planet it said to use with froyo but didnt say it would not work with eclair. I installed the mod without problems and I thought everything was going well, but now my phone is bricked, and wont load past the samsung i896 boot screen even after deleting all user data and wiping my cache in recovery mode. So I guess my only option now is to flash a rom using odin, but id rather prefer not to flash to a stock ATT 2.1 rom, i would like to flash back to my original stock rogers.
Is it possible to flash to an ATT rom, then do a factory reset from the privacy settings of the phone to bring me back to rogers stock rom?
ATT rom =/= Rogers rom
You'll need to search and find a Rogers rom you can stick in Odin and flash with if you want Rogers
I don't think you can easily return to Rogers stock rom using odin. Most people end up having AT&T logo on boot. However, since you're soft bricked anyways, why don't you try using Heimdall, new Open-Source Flashing Software and this dump generated from stock Rogers phone.
I haven't seen any reports of tests on Captivate yet, but it seems to work well on other Galaxies. Check Heimdall thread for more info, and if it works well for you, please report to this thread. Good luck!
thanks, i installed heimdall perfectly fine, it recognizes my device, but i cant download that PIT file from megaupload, its failed to download multiple times. Is there any other links?
I will keep trying
all good to go now,
used this rogers stock rom
http://www.megaupload.com/?d=BD2EF4WF
and flashed it without any problems. Glad to have a working phone again even though i lost everything
Did you use heimdall our some other method?
Sent from my SAMSUNG-SGH-I896 using XDA App
Hi! I just came across the same issue. I've been using the Cognition ROM on my Captivate for some months now and only today decided to switch to Perception 8. I downloaded the latter and rebooted through ROM Manager which, as I've done before, rebooted and backed up all my data. It then proceeded to erase all user data and cache and attempted to install Perception 8 ROM, but was unsuccessful. It provided me with a usual list of options, including 'Reboot', 'Backup' (i think) and others. I chose to Reboot thinking it would just go back to the last best ROM (i.e. Cognition latest, in my case).
Now it just reboots and refuses to go past the at&t World Phone boot screen.
I've tried the button combinations. Up-volume+down-volume+power button, up+power, up+home+power, down+home+power (!). All these seem to reboot the phone and in about 10 seconds after I press them, takes me right back to the same boot screen and not past it.
I'm fairly sure my old data is backed up somewhere inside.
I've tried to read the other forums, but nothing in particular seems to work for me. I run Ubuntu on my laptop, wanted to try Heimdall but its download page is down.
Any suggestions on how to proceed would be greatly appreciated.
1) Any other button combinations?
2) Any other tricks, including ways to using Heimdall (whose source files I can't seem to find), to get into my device?
Apologies for the detail, but I presume there's someone who knows exactly what I'm talking about.
OP, what software did you end up using on your computer to gain access to the device?
Thanks.
sshvetsov said:
Did you use heimdall our some other method?
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
yes i used it, installed the drivers on my pc, downloaded the rom i provided in my response and flashed it, worked flawlessly without problems.
nostratispeak said:
Hi! I just came across the same issue. I've been using the Cognition ROM on my Captivate for some months now and only today decided to switch to Perception 8. I downloaded the latter and rebooted through ROM Manager which, as I've done before, rebooted and backed up all my data. It then proceeded to erase all user data and cache and attempted to install Perception 8 ROM, but was unsuccessful. It provided me with a usual list of options, including 'Reboot', 'Backup' (i think) and others. I chose to Reboot thinking it would just go back to the last best ROM (i.e. Cognition latest, in my case).
Now it just reboots and refuses to go past the at&t World Phone boot screen.
I've tried the button combinations. Up-volume+down-volume+power button, up+power, up+home+power, down+home+power (!). All these seem to reboot the phone and in about 10 seconds after I press them, takes me right back to the same boot screen and not past it.
I'm fairly sure my old data is backed up somewhere inside.
I've tried to read the other forums, but nothing in particular seems to work for me. I run Ubuntu on my laptop, wanted to try Heimdall but its download page is down.
Any suggestions on how to proceed would be greatly appreciated.
1) Any other button combinations?
2) Any other tricks, including ways to using Heimdall (whose source files I can't seem to find), to get into my device?
Apologies for the detail, but I presume there's someone who knows exactly what I'm talking about.
OP, what software did you end up using on your computer to gain access to the device?
Thanks.
Click to expand...
Click to collapse
i used heimdall, which was linked above, but I was able to get into download mode through my phone since it was soft bricked. IF you can get back into Download mode, then you are fine... Keep trying until you do, otherwise you might have to use the JIG method.
stavs said:
yes i used it, installed the drivers on my pc, downloaded the rom i provided in my response and flashed it, worked flawlessly without problems.
Click to expand...
Click to collapse
That's great news! I'm sure a lot of rogers captivate users will be very happy to learn that. Just curious, where did the linked rom dump come from?
EDIT: Nevermind, found this thread describing Rogers stock restore procedure using Heimdall and the bundle you used.
@nostratispeak: if you have questions about Heimdall, you might want to check the official thread.
sshvetsov said:
@nostratispeak: if you have questions about Heimdall, you might want to check the official thread.
Click to expand...
Click to collapse
Yup. Just did. The site is back up and working. I've the downloaded the files too. Now, to get my phone to work.
@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
EDIT: I followed the instructions from this thread and I have the phone in what I believe, is the Download mode: Droid shoving dirt within a filled yellow triangle, with a message "Downloading" "Do not turn off Target". My device is connected to my laptop. I don't see anything popping up on the screen. I also have Heimdall frontend up and running in Ubuntu.
I've downloaded a few ROMs, including Cognition and some samsung stock firmware. There are conflicting information in different pages. Am not sure what to do next. Help?
nostratispeak said:
@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
Click to expand...
Click to collapse
Your device isn't bricked as such, it's caught in a boot-cycle. This is actually worse than a soft brick and in some ways is comparable to a "hard" brick. It's comparable to a hard brick because when you're in a boot cycle you usually can't get into download mode. Presumably the only option is to use a custom JIG, as you've mentioned.
There is no official terminology but a soft brick is generally when your phone displays the "connect phone to pc" screen. A hard brick is a bit more difficult to define, but I'd say it's fairly reasonable to assume that this is when your phone won't turn on or charge. A brick (full brick?) is when your device is absolutely not recoverable by any means.
nostratispeak said:
@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
EDIT: I followed the instructions from this thread and I have the phone in what I believe, is the Download mode: Droid shoving dirt within a filled yellow triangle, with a message "Downloading" "Do not turn off Target". My device is connected to my laptop. I don't see anything popping up on the screen. I also have Heimdall frontend up and running in Ubuntu.
I've downloaded a few ROMs, including Cognition and some samsung stock firmware. There are conflicting information in different pages. Am not sure what to do next. Help?
Click to expand...
Click to collapse
thats great news than, now with the one of the downloaded roms you have saved on your computer, take the data (ie Factoryfs.rfs,cache.rfs, modem.bin and Zimage) and link it appropriately in the program. Then just click the start button and it will automatically install the rom within minutes. You shouldnt see anything pop up, i dont remember seeing anything, but during the installation there should be a download bar on your phone to indicate data is being transfered and downloaded to your phone. After your phone should reboot and be back to normal.
stavs said:
all good to go now,
used this rogers stock rom
and flashed it without any problems. Glad to have a working phone again even though i lost everything
Click to expand...
Click to collapse
Does this remove the AT&T boot logo and replace with the Rogers logo as well? Stavs, I'm assuming you went from the Rogers ROM, back to the Rogers ROM, so this probably not apply to you, but have any of you guys been able to get rid of the AT&T logo from a previous flash, and restore the Rogers logo using this method, and ROM?
stavs said:
all good to go now,
used this rogers stock rom
megaup*****com/?d=BD2EF4WF
and flashed it without any problems. Glad to have a working phone again even though i lost everything
Click to expand...
Click to collapse
used the same rom flashed it with odin but didnt load the pit file... made sure re-partitioned was UNchecked and off i went... restored my phone to 2.1 and was finally able to get kies to recognize my phone and upgrade it after 5 days in hell trying various things, flashing different "stock" ROMs... i finally did it tho... running froyo as we speak...
I am not sure if anyone suggested this already but i896 users can flash stock Rogers 2.1 using this method. No AT&T screens. Works great.
http://forum.xda-developers.com/showthread.php?t=979133
Alright. I have a Captivate on AT&T. It's bricked. It was one click rooted and had Perception 9.5 installed. I did the clockwork mod automatically when I rooted. I didn't use Odin. I dragged the Perception zip onto the SD. Restore mode via 3 button, install. I ran it first time no prob. I kept it for about 7 days, and I decided I wanted to try 10.1, and then if that didn't work, ROMkitchen custom.
So, I needed to go back to stock, right? I saw the Odin3 version, but on Designgear's thread, the Odin3 link was broken. So, I dl'ed the JH7_OTA.zip file, dragged to my SD, 3 button restore mode, install. WRONG! I now have a perma-AT&T screen. I don't wanna mess anything up, as I know just enough to get in trouble.
Please excuse me, as I'm sure it's been answered somewhere. I'm new from iPhone, and I know forum manners. I'm on my way out to my job, where I'll remain for the next 5 days. I only have access to an XP machine.
Please help if you can, and thanks in advance.
Find a link for a reupload of the Odin One Click, its in the thread. And then put your phone into download mode then flash.
ShredNasty said:
So, I needed to go back to stock, right? I saw the Odin3 version, but on Designgear's thread, the Odin3 link was broken. So, I dl'ed the JH7_OTA.zip file, dragged to my SD, 3 button restore mode, install. WRONG! I now have a perma-AT&T screen. I don't wanna mess anything up, as I know just enough to get in trouble.
Click to expand...
Click to collapse
No you really didn't need to go back to stock, but that's water under the bridge now. I don't know which firmware you need for your particular phone. For a batch 1009 and earlier this should be fine. For others you may need this. Personally, I'd stay away from the one-click which disables button combos on all newer builds.
K, well I feel dumb. I dl'ed Odin3, discovered "restore mode" and "download mode" aren't the same thing, put my phone in dl mode, clicked start on Odin, and was finished. Super simple back to stock.
Thaks for the help though guys. I appreciate it....
opcow said:
No you really didn't need to go back to stock, but that's water under the bridge now. I don't know which firmware you need for your particular phone. For a batch 1009 and earlier this should be fine. For others you may need this. Personally, I'd stay away from the one-click which disables button combos on all newer builds.
Click to expand...
Click to collapse
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?
ShredNasty said:
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?
Click to expand...
Click to collapse
If you manage to mess things up to the point you can't flash a custom ROM through recovery/CWM. Or if you need to exchange/return the phone for some reason.
ShredNasty said:
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?
Click to expand...
Click to collapse
In my opinion, only if nothing else works. I went a couple of months flashing mine dozens of times without using odin. I only flashed to stock prior to sending my phone back to Samsung to see if I could get the GPS fixed/improved.
Right on man. I appreciate it. I'm learning fast. Next time I flash, I'll just flash right over P10.1....
From what I've read since joining this community is that people tend to have mixed results/opinions about flashing to stock before changing ROMS. Personally, I always do... Each Captivate out there seems to have different quirks that do odd things from time to time, and are sometimes completely random. If you have no problem simply flashing a new ROM over what your using currently... by all means. If you have problems or Force Close issues.. try going back to stock first... All depends on what you are comfortable with..
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd? The reason I ask is because I have been bouncing between cognition and paragon for about 2 weeks now NOT using the method of flashing back to stock 2.1 without a single problem. I'm sure there is a good reason flashing back to 2.1 before trying new roms, I would just like to know why. I was able to preform a stock wipe using odin3 one time last week (just did it to make sure the phone would do it) it just seems like a really long process, but I'll start doing it that way to avoid a brick.
Thanks
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
For the most part, you don't really need to flash back to stock. It used to be a bigger deal to flash back to stock because some of the Roms would intervene with each other and mess things up. It is still recommened for a clean flash, but I rarely do it and my flashes work great.
EDIT: @Trusselo: damn it! Second time someone beat me to the answer tonight!
HAHA
and forget ODIN ONE CLICK !!
i keep forgetting about this
http://forum.xda-developers.com/showthread.php?t=944418
ALL IN ONE CAPTIVATE TOOLBOX
I have been trying roms weekly since November and have only needed to flash to stock twice, after failed flashes caused by my lack of patience. YMMV of course
jayjr1105 said:
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd?
Click to expand...
Click to collapse
It's not necessary and not even a good idea. Also, why wipe cache and d-cache when the install script does that?
Trusselo said:
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
Click to expand...
Click to collapse
ROMs don't mod or use any files which are on the phone prior to installing them. All the files on your phone after the install were in the CWM flashable zip file. Any ROM cook would be stupid to do otherwise. The exception would be no-wipe ROMs, but you would never flash to stock before using one of those.
Ive also wondered this as well and talking to guys like opcow, and a couple other Devs such as MikeyMike and a lot of guys at the Andromeda IRC they all agree that you should be perfectly fine now as long as you wipe everything before you flash.
I may try with Andromeda when I get home because I have my PC and Jig there just in case but still may try now. But also tlaking to a lot of users that they dont even do it anymore now because of the install scripts and as Opcow said if you think logically its technically safer.
Trusselo said:
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
Click to expand...
Click to collapse
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Dlev7 said:
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Click to expand...
Click to collapse
+1 Guys if you don't know exactly what to do/suggest please don't say it. I'm not trying to start a war, but a wrong suggestion can easily soft or hard brick someones phone. This is a forum, so no one can stop you from saying things, but think about if it happened to you? You would be pissed!
Anyways back on topic, what model phone do you have, because having a 1009 model phone makes flashing and going back to stock (usually) so much easier. But then again, I rarely use odin because all the roms are compatible for the most part.
Sent from my SGH-I897 using XDA App
I've never used ODIN because I haven't wanted to try to run it from GNU/Linux in a virtual box.
I just wipe and flash from clockwork like the op. Been flashing roms for a couple months now, never had a single problem. (except when I noobed it up by trying to flash back to a nandroid backup via Rom Manager. Even then, didn't need Odin to sort it out).
If I ever run into a problem, then I'll try Odin, but I'm waiting to cross that bridge till I come to it.
To prevent exceptions or troubles from the version you already have... so everybody comes from the same rom, understand?
I flash to jf6 because that's what I have been conditioned to do for a while. However, the few times I was impatient and didn't....no problems either.
From all the reading I've done here, the only reason to do it is for the placebo effect.
There was once a time when all the new roms were built on the unofficial froyo and it only had 3e recovery. The quickest way to get around that was to flash stock. Also the lag fixes were tricky and easily fixed by flashing stock. Now recovery is in the kernel. As long as you insure the kernal lag fix in rom A understands the kernal lag fix in rom B flash away. Nandroid backups are kind of useless they don't backup the kernal or the modem. Save odin for when things go really wrong(;~ )
Sent from my i897 using XDA App
I have done it both ways, and there its no difference going back to stock and or flashing over other roms. I flash often, have not got stick in boot loop in months
I like to go back to stock since I KNOW that everything has been defaulted back to normal. Just a security blanket step for me.
I flashed andromeda over darkyy 9.3 just wiping data cache and d cache. Nothing wrong. Everything worked perfect so I got to believe that if you just wipe everything it should work perfectly.
Just for safety I got a jig and odin but for now I'm saving a good 45 minutes to not flash back to stock
Sent from my SGH-I897 using XDA App
I thought I knew what I was doing...
I've read and read and read. Thought I had all my ducks in a row. Thought I had everything figured out. But now I have a bricked phone.
I bought my Captivate refurbished from AT&T about 3 months ago. The mfg date is listed as 1011. It came with Froyo. By the third day I had it rooted and Cognition installed. Loved it. But lately it was starting to freeze up, lag, etc. so I decided to install Serendipity.
I followed the directions in the famous How-To thread here.
Odin reported success, but now my phone is stuck in bootloop. None of the tricks for getting it back into download mode worked.
I went to Radio Shack and bought some resisters and made a jig. Now, I can successfully get back to download mode now, so I'm still holding out hope!
I tried Odin again, but got the same result.
My warranty is up in 3 days. Called warranty place today and they won't do anything unless the phone can get to a recovery screen (probably their way of knowing when people have been doing what I've been doing!). Which it won't. I can put it in download mode with the jig. Otherwise, I just get the boot loop.
I have been stressing over this for the last 15 hours. I can't sleep. I've read countless forum posts. Now I find that Odin with Froyo and phones dated from 1008 and above is tricky. How did I miss that before? I've read so much, seen so many threads with people saying "do this" followed by "no don't do that" followed by "that's always worked for me" but it's not working for ME. At this point I'm confused and scared and just hope somebody can point me to instructions for getting a usable phone again.
EDIT: I see I misspelled "Odin" in the title of the thread... tried to edit it but I can't. Sorry.
That guide has not been updated for 2.3 roms. you should follow the instructions that were written by the rom maker, for the rom your trying to flash
This looks relevant http://forum.xda-developers.com/showthread.php?t=995143
- For unbricking
AdamOutler, is working on a unbrick method. http://forum.xda-developers.com/showthread.php?t=1206216
Or mobiletechvideos they have an unbricking service for 50$
(side-note if you have read and read like you said you should have had come a cross some of this.)
Which Cognition were u on ? And which Odin did u use ?
And since u can still get into Download mode u can relax a little, cause that's a good thing.
Lol relax If the phone shows any signs of life, that means it can be fix (usually). Now if the phone after odin doesn't want to turn on THEN your bricked. Since your phone is a newer build and they have been known to not always like jf6 Odin I suggest you try this KB1 odin. Best of luck
speedy_11 said:
That guide has not been updated for 2.3 roms. you should follow the instructions that were written by the rom maker, for the rom your trying to flash
Click to expand...
Click to collapse
Know that now! lol The instructions for Serendipity indicated I didn't have to go back to stock. But I just wasn't sure. So I figured I'd go ahead back to stock just to "be safe." That worked out well!
speedy_11 said:
(side-note if you have read and read like you said you should have had come a cross some of this.)
Click to expand...
Click to collapse
Yes, you are correct. And I deserve any amount of "stupid newb" criticism you can heap on me.
For2ndtwin said:
Which Cognition were u on ? And which Odin did u use ?
Click to expand...
Click to collapse
Which Cognition? Uhm... I don't recall. Whatever was the newest version when I installed it nearly 3 months ago.
I used the Odin One-Click. The filename is I897UCJF6-final-OCD-REV0. When I run it, the title bar says Odin3Execution_v1.0.
For2ndtwin said:
And since u can still get into Download mode u can relax a little, cause that's a good thing.
Click to expand...
Click to collapse
That's what I keep trying to tell myself...
prbassplayer said:
Lol relax If the phone shows any signs of life, that means it can be fix (usually). Now if the phone after odin doesn't want to turn on THEN your bricked. Since your phone is a newer build and they have been known to not always like jf6 Odin I suggest you try this KB1 odin. Best of luck
Click to expand...
Click to collapse
Thanks! I'm reading through the threads y'all linked to and I'm sure I'll be back with questions. This whole Odin thing, for one, has me confused. There's at least a dozen different versions available from samfirmware.com, there are different versions of the one-click (like the Designgears 2.2 one? Should I try that one?), then different "full" versions with different instructions ("only use the pda button," "use this pit file", "don't use a pit file", etc...) I'm trying my best to make sense of it all. I was in full-blown panic mode yesterday and trying to read through a dozen different threads at once. Maybe today I can slow down a bit, take a breath, and get this figured out.
The one click I linked should get you to stock. Atleast so you have a funtional phone. There is only one true odin with different versions (1.1 1.82 etc) one clicks r simplified odin that will only flash something specific like 2.1 jf6 or 2.3.3 kf1 to name a few. Samfirmware.com uses the actual odin as it supplies packages for it.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
prbassplayer said:
The one click I linked should get you to stock. Atleast so you have a funtional phone. There is only one true odin with different versions (1.1 1.82 etc) one clicks r simplified odin that will only flash something specific like 2.1 jf6 or 2.3.3 kf1 to name a few. Samfirmware.com uses the actual odin as it supplies packages for it.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Ok, another sucky thing is I'm on satellite internet and already dangerously close to being FAP'd. I've got to run into town this evening and will try to find some free wifi so I can download those things. Until then... it's just reading threads.
One quick question... that's a one-click you linked to? Posts 33 and 34 say to use regular Odin, not one-click. They provide a link to download regular Odin. Is the I897UCKB1-homeBinary.tar file part of the package I download from the link in the first page? The one-clicks I've downloaded have just been an .exe file.
HeathicusF said:
Ok, another sucky thing is I'm on satellite internet and already dangerously close to being FAP'd. I've got to run into town this evening and will try to find some free wifi so I can download those things. Until then... it's just reading threads.
One quick question... that's a one-click you linked to? Posts 33 and 34 say to use regular Odin, not one-click. They provide a link to download regular Odin. Is the I897UCKB1-homeBinary.tar file part of the package I download from the link in the first page? The one-clicks I've downloaded have just been an .exe file.
Click to expand...
Click to collapse
Because I'm a derp and didn't read it well. Regardless its the package files for stock KB1 use regular ODIN for it. Stick it in PDA. It doesn't have bootloaders so the possibilities of hard bricking are very low xD. My mistake for saying it was 1 click sorry xD
Ok, thanks. I'll post an update tonight after I get back home.
SUCCESS!!!
I now have a fully functional phone running what appears to be stock 2.2 firmware!!
THANK YOU!!!!
However... I can't seem to get into recovery mode. When I hold down all three buttons, it looks like I'm stuck in a boot loop again (ATT World Phone screen flashes). If I release the power button keeping the volume buttons held down, the phone just boots as normal. Is there a fix for this?
I still have all the folders for my old apps on the internal memory card. Can I delete these manually? I'd like it to be back to truly stock settings and start all over. Is that what the "Master Clear" in Odin is for? I didn't see that option in "regular" Odin.
I did get it rooted with Super-One-Click.
Ok, this is where I'm at.
Stock Foyo working phone.
Can't boot into recovery using volume & power buttons.
Rooted with Super One Click.
Installed Superuser.
Installed Rom Manager. At least now I can boot into Recovery Mode through the option in Rom Manager.
Flashed Clockworkmod using Rom Manager. Reported success, but Recovery Mode is still stock version 3e, not 2e. So, still can't install a new custom rom.
I'm a little nervous to try anything else at this point, but really want to be running Serendipity. Serendipity says DO NOT use Rom Manager to install it.
What to do from here? I'm researching, but any pointers would be helpful.
If I install Cognition again from Rom Manager (is that possible/safe at this point?), will that replace the Recovery Mode with 2e? Or is that not related at all?
not related at all.
you should really take the 30 seconds to search for that error you get when you try to reinstall packages from 3e recovery.....it would solve your problems.....
or do it the EASY way and just ODIN a freaking kernel on it that has built in CWM.
flash your rom of choice from CWM
HeathicusF said:
Ok, this is where I'm at.
Stock Foyo working phone.
Can't boot into recovery using volume & power buttons.
Rooted with Super One Click.
Installed Superuser.
Installed Rom Manager. At least now I can boot into Recovery Mode through the option in Rom Manager.
Flashed Clockworkmod using Rom Manager. Reported success, but Recovery Mode is still stock version 3e, not 2e. So, still can't install a new custom rom.
I'm a little nervous to try anything else at this point, but really want to be running Serendipity. Serendipity says DO NOT use Rom Manager to install it.
What to do from here? I'm researching, but any pointers would be helpful.
If I install Cognition again from Rom Manager (is that possible/safe at this point?), will that replace the Recovery Mode with 2e? Or is that not related at all?
Click to expand...
Click to collapse
You are in 3e recovery because you are running froyo. Flash to the stock 2.1 eclair and that will get you back to 2e. There are other ways but thats the most basic I feel.
Sent from my Samsung Captivate running Cognition 2.2 rom
capocaccia said:
You are in 3e recovery because you are running froyo. Flash to the stock 2.1 eclair and that will get you back to 2e.
Click to expand...
Click to collapse
Yeah, trying to flash the stock 2.1 is what got me in this trouble to begin with!
Pirateghost said:
not related at all.
Click to expand...
Click to collapse
Thanks!
Pirateghost said:
you should really take the 30 seconds to search for that error you get when you try to reinstall packages from 3e recovery.....it would solve your problems.....
Click to expand...
Click to collapse
I'm trying... but 1) satellite internet is frustratingly slow - not much better than dial-up at times; and 2) each path of research I take leads to several forks with several different people giving several different solutions to problems, some people saying it worked, some people saying it didn't, which leads to several more alternative solutions, some of which don't work, etc... It gets confusing after a while, but I'm trying my best to read through all the threads I wander through and to make sense of it all. Yeah, I'm a stupid newbie....
capocaccia said:
You are in 3e recovery because you are running froyo. Flash to the stock 2.1 eclair and that will get you back to 2e. There are other ways but thats the most basic I feel.
Sent from my Samsung Captivate running Cognition 2.2 rom
Click to expand...
Click to collapse
If you would have read the beginning og the thread you know that his phone didn't take well to jf6.
prbassplayer said:
If you would have read the beginning og the thread you know that his phone didn't take well to jf6.
Click to expand...
Click to collapse
There are more builds of 2.1 other than jf6...
Op look at the bottom of the first post of the odin one click thread by design gears there are 2 stock firmware packages the first one is an eclair build use the full version of odin (not one click) flash that and you're good.
Or search for the work around of 3e recovery, look in the sticky roll up at the to of the general section...it'll say "e: signature verification error"
HeathicusF said:
I'm trying... but 1) satellite internet is frustratingly slow - not much better than dial-up at times; and 2) each path of research I take leads to several forks with several different people giving several different solutions to problems, some people saying it worked, some people saying it didn't, which leads to several more alternative solutions, some of which don't work, etc... It gets confusing after a while, but I'm trying my best to read through all the threads I wander through and to make sense of it all. Yeah, I'm a stupid newbie....
Click to expand...
Click to collapse
funny thing, that STICKY section we have at the top of the forum....
theres this one called a 'STICKY ROLL-UP', not to be confused with fruit roll-up.
http://forum.xda-developers.com/showthread.php?t=1161102
all the info you need is located within it.....oddly enough
Pirateghost said:
funny thing, that STICKY section we have at the top of the forum....
theres this one called a 'STICKY ROLL-UP', not to be confused with fruit roll-up.
http://forum.xda-developers.com/showthread.php?t=1161102
all the info you need is located within it.....oddly enough
Click to expand...
Click to collapse
Yes, I tend to rely to heavily on the search feature and overlook sticky threads. Thanks for the reminder.
The "Fixing 3e" methods listed in this thread don't seem to be working for me. First method (the script) gives me an error. Tried with Win 7 64bit, and 32bit (two different computers). Yes, phone drivers were installed. Second method (manual copying of the file) doesn't work. When using Terminal Emulator to execute the command I get the message "Operation not permitted." When using ES File Explorer with Mount file System as writable checked in the settings, I get no errors or complaints... but nothing has changed when I boot into recovery.
Still working on it. Thanks for the pointers.
why dont you try one of the ODIN KERNELS that will add CWM for you? why are you wasting your time running in circles for nothing?
put phone in download mode
open ODIN, add the kernel into the PDA slot
connect phone
flash kernel
now you have CWM and can flash any 2.2 rom you want
Pirateghost said:
why dont you try one of the ODIN KERNELS that will add CWM for you? why are you wasting your time running in circles for nothing?
put phone in download mode
open ODIN, add the kernel into the PDA slot
connect phone
flash kernel
now you have CWM and can flash any 2.2 rom you want
Click to expand...
Click to collapse
After softbricking (is that the right term?) my phone with Odin, it makes me a little nervous. (Of course, I also recovered my phone with Odin, so maybe I shouldn't be nervous...).
This running around in circles...? We'll call it "education"!