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.
As you are about to see, I'm new to this.
I have been attempting to root my Captivate. I have tried Galaxy One Click Root and Super One Click 1.7, among others.
My phone won't enter recovery mode. I have tried to install z4root, which the phone blocks. I've tried using sideload wonder machine, which doesn't work either.
I downgraded to 2.1....nothing. Reloaded 2.2....nothing.
Any advice would be helpful at this point, and please be specific, as I am slightly retarded.
It its rumored that Odin one click to jf 6 will actually get rid if the recovery/ download modes, maybe try flashing a cognition ROM
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
ryanmahan said:
It its rumored that Odin one click to jf 6 will actually get rid if the recovery/ download modes, maybe try flashing a cognition ROM
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
That's not a rumor, it's a fact. Does not happen with all models.
What about full odin to jf6? I personally like to use odin every so often to master clear.
It would explain why superone click wouldnt root my phone lst time i master cleared, too. Ended up installing cwm and flashing straight to rom(which took care of rooting and 3rd party apps)
mrhaley30705 said:
What about full odin to jf6? I personally like to use odin every so often to master clear.
It would explain why superone click wouldnt root my phone lst time i master cleared, too. Ended up installing cwm and flashing straight to rom(which took care of rooting and 3rd party apps)
Click to expand...
Click to collapse
As I said, I'm slightly retarded. Do you know of a forum with instructions for doing this? Everything else I've tried has just caused a face to appear on my phone's screen laughing at me.
When you use super one click, did you enable usb debugging?
Sent from a place my wife doesn't know about
The captivate is actually an extremely easy root process...
Download this file update.zip
Put it on your internal SD card (internal Memory) not your SD card you can remove
Turn off your phone
Once off hold both volume up and down and hold power until you see the AT&T boot screen then let go of all 3 buttons. You should see recovery mode soon. Select Reinstall Packages, congratulations you are now rooted.
Is that the modded cwm? I think he said he was on 2.2. Regular cwm won't work with froyo(signature verification errors). There is a modded one somewhere on this site that either replaces 3e, our fixed sig on cwm.
Sent from a place my wife doesn't know about
I think he downgraded to 2.1 again which is what you'll need to be on to use the method I described.
jayjr1105 said:
I think he downgraded to 2.1 again which is what you'll need to be on to use the method I described.
Click to expand...
Click to collapse
I'm running 2.2
1-Downloaded and installed file update.zip to internal sd. Turned off phone. Tried to enter recovery mode. Got blank screen, att screen, blank screen, att screen, blank screen, etc etc.
2-Tried to install z4root. Blocked by phone. Tried to use sideload wonder machine, which can't detect the phone (in usb debugging mode and mass storage (tried both))
3-Tried Super One Click, which ran but did nothing.
4-Flashed to 2.1 and factory reset. Tried (2) again. Failed. Tried 1-3. Failed.
5-Flashed to a different version of 2.2. Started over. Failed.
I've been using some of the mobile tech videos, but everytime I get to the "Eureka!" phase, my phone just laughs at me.
use odin full version to flash speedmod kernel on 2.2, i even do this on 2.1, but on 2.1 you need the .zip file on the sdcard before you start because the phone will not boot with a 2.2 kernel, only enter recovery.
once on speed mod kernel you can either root and flash a kernel for att roms or flash a new rom without the need to root, the new rom will be rooted.
if you are on 2.2 you will need a computer one way or another, flashing back to stock can be a pain for those with the 3 button problem and it is way more time consuming than flashing a kernel, i have never used the tools out there but i don't know of an easier way than flashing a kernel via odin, especially if you intend to flash a 3rd party rom. also any time you flash a sbl.bin or boot.bin can be a dangerous situation. bad flashes that break the boot loaders aren't common but it causes enough "omg i bricked" threads to keep me from recommending it. there is a odin one click with a 3 button fix, if you use that once it will be fixed untill you flash a rom with odin that changes the bootloaders again. im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
you must not have the right drivers installed.
2.2 cannot be rooted by using an update.zip....you will need to get your drivers working and adb seeing the device....
sharp1114 said:
I'm running 2.2
1-Downloaded and installed file update.zip to internal sd. Turned off phone. Tried to enter recovery mode. Got blank screen, att screen, blank screen, att screen, blank screen, etc etc.
2-Tried to install z4root. Blocked by phone. Tried to use sideload wonder machine, which can't detect the phone (in usb debugging mode and mass storage (tried both))
3-Tried Super One Click, which ran but did nothing.
4-Flashed to 2.1 and factory reset. Tried (2) again. Failed. Tried 1-3. Failed.
5-Flashed to a different version of 2.2. Started over. Failed.
I've been using some of the mobile tech videos, but everytime I get to the "Eureka!" phase, my phone just laughs at me.
Click to expand...
Click to collapse
sounds like you need the 3button fix first. there is an odin stock rom+3button fix, it should take you to 2.1 but you will get recovery mode. if that fixes the recovery mode 3-button combo and the phone boots you can put the rom of your choice on the sd card, then odin flash speedmod kernel and flash the new rom, warning the phone doesn't boot a 2.1 rom with speedmod kernel, i only do this as a faster way to get into cwm recovery, only do that if you intend to flash a rooted rom from 2.1.
Dani897 said:
use odin full version to flash speedmod kernel on 2.2, i even do this on 2.1, but on 2.1 you need the .zip file on the sdcard before you start because the phone will not boot with a 2.2 kernel, only enter recovery.
once on speed mod kernel you can either root and flash a kernel for att roms or flash a new rom without the need to root, the new rom will be rooted.
if you are on 2.2 you will need a computer one way or another, flashing back to stock can be a pain for those with the 3 button problem and it is way more time consuming than flashing a kernel, i have never used the tools out there but i don't know of an easier way than flashing a kernel via odin, especially if you intend to flash a 3rd party rom. also any time you flash a sbl.bin or boot.bin can be a dangerous situation. bad flashes that break the boot loaders aren't common but it causes enough "omg i bricked" threads to keep me from recommending it. there is a odin one click with a 3 button fix, if you use that once it will be fixed untill you flash a rom with odin that changes the bootloaders again. im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
Click to expand...
Click to collapse
Do you have a suggestion for a stable rom? I don't want to get to the point where I've got it working and throw a terrible third party on it. I'm just looking for device speed and controll over all apps, especially bloatware.
all of the available roms are stable. to be honest TiBu will remove bloat if you want it to.
Try them all and see which one you like. Pretty much all of the custom roms are better than stock. If you like to stay near stock but run more optimized, see Cognition. Otherwise see which one you like more. It's not a hard process if you read up on it.
sharp1114 said:
Do you have a suggestion for a stable rom? I don't want to get to the point where I've got it working and throw a terrible third party on it. I'm just looking for device speed and controll over all apps, especially bloatware.
Click to expand...
Click to collapse
it is hard to go wrong with cognition which is a stock rom with some mods and bloat removed and tethering enabled, that will have the proper kernel and modem for the captivate which for me has great call quality, also the disadvantages of not having hsupa are overblown.
there is also andromeda which is the rom from the armani captivate and is well polished and complete, has some of the more useful samsung apps. this can be used with a 2.2.1 kernel ported from the i9000 for a slight speed boost (shows in benchmarks, may not be detectable in user experience) this has hsupa and is designed for the captivate
i9000 ports are newer 2.2.1 versions and all of the features work now so you may want a newer firmware version from one of those..
there are many 2.2.1 i9000 roms that are fully functional. that is more a matter of feature set and theme preference it is hard to say one is better than the other. id say for stable the speedmod kernel is about the best on an i9000 port, for experimenting with overclock or undervolt i hear that the kernel with paragon is awesome.
now it is odd that you say you flashed a different version of 2.2 but cant get into recovery, was that in odin? can you get download without adb commands?
Dani897 said:
im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
Click to expand...
Click to collapse
Use this method to flash back to stock. Supposed to be much safer that doesn't mess with the bootloader files. I have been using it for about 3 weeks now to flash back to stock. You CAN however still use the one click odin to master clear once you have flashed back to stock.
Back on topic... I would flash back to 2.1 using the above method and master clear to start fresh with this issue. Once that is done look for mobiletechvideo's 3 button fix video on youtube. But even if you have 3 button issues the Galaxy S one click root program should still get you into recovery. It doesn't always succeed in copying the update.zip file to the internal SD card but you can do that manually and just use the program solely to get into recovery. Make sure you have USB debugging on. After the stock flash and master clear it is off by default and samsung kies is on. You might want to invest in a Jig also since you have 3 button issues, it may save you hide someday.
As far as a good rom goes. Really all the 2.2.1 roms are pretty stable and fast. I'm currently using Continuum 4 with the paragon kernel and it floats and sips battery. If you like the stock look you can use cognition. If you like the green themed gingerbread look you can use Phoenix, Serendipity, Firefly, or Paragon which is my personal fav but hasn't been updated in a month.
Anyways good luck. I'm sure you'll figure it out.
oops, got double posted somehow
Thanks for all your advice and help. I finally got it rooted.
I've tried Cognition 4.3 and Paragon, both of which I liked. I like the appearance of Paragon, but the optimization just doesn't seem to be there. Cognition is great for customization, but I the appearance is just to 'stockish' for me, if that makes sense. Something in between would be nice. (Ideas?)
I plan to try Phoenix Unleashed, but i can't get it to download.
The reason why the programs are having a hard time seeing your cappy is because you need the Serial COM driver available only by installing Samsumg's software: Kies Mini... don't run the program just install it. Once you do this Odin and the Wonder Root program can see the phone. I had this issue.
I think we need to sticky/pin this for us who just flash the stock/leaked GB 2.3.3 along with the optional root from this thread since we can't post there http://forum.xda-developers.com/showthread.php?t=1127249
Since this is the route that I went I would be able to help answer questions for others. I see cognition, mosaic.... but how about us who like to keep it stock?
Brickster
Just want to say that I have learned so much on here and I have a lot of fun trying out different ROMs. Thanks to all the DEVs, when I get a job I'll buy you guys some beers lol.
So... This has soft bricked my phone every single time. The first 4 attempts were from stock eclair. My last attempt I was successfully running Stock I9000 2.3.3 NEE so I thought I would try it from there. Odin gets to boot.bin and then says FAIL! I got into download mode using VOL DWN and PWR which is the key combination from Stock I9000 2.3.3 NEE. I have been running I897UCJF6-final-OCD-REV0 to flash back to stock after brickness.
So i'm sure i'm missing something pretty simple, but any help is appreciated.
Woah dude, that was very very very close to being a hard brick. Boot.bin is the primitive bootloader. so you had a kf1 pbl, and since you had the combos for I9k boots you obviously had an I9000 sbl, (secondary bootloader that's where the combos are contained.)
Make sure the usb chord is on a port attached to the motherboard (in the back of the pc), if it is already switch to another. Reboot the computer and try again.
But with such a close call like that, and the fact that you said it fails every time I would avoid it altogether I mean its a stock rom, is it worth bricking over??
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
ttr187 said:
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
Click to expand...
Click to collapse
Use admin mode for Odin and change the compatiblity to Xp service pack 2. This is the best way to run Odin for Windows 7 x 64. Since I use Cog 5 v2, I strongly recommend following the instructions 100%. Please remember when you need to loading stock UCKF1 and when you load UCKF1, you are loading bootloaders, so any disconnection can brick you hard. Thank goodness for the simplified instructions there.
GB stock? I thougth captivate stock were eclair or froyo.
KF1 is the leaked gingerbread firmware for the captivate...
popfan said:
Use admin mode for Odin and change the compatiblity to Xp service pack 2.
Click to expand...
Click to collapse
After changing the compatibility mode to XP pack 2 everything worked like a charm. Then I was able to successfully flash Cognition 5 v2. Sweet!
Thanks.
Hello. I use Darky's rom 10.2. And I have problem with Dialer. It sometimes crushes and exits. Problem will be solved with reboot. how can I fix it? thanks.
I would try to flash again and make sure you do a data/cache wipe. I've had random issues with other ROMs when I did not wipe, and all was fixed once I flashed properly.
I know I'm not wiping everything while flashing, but I flash it as told as in FAQ. But my memory will stay unwiped after I run newly installed ROM.
When you say "memory" what exactly do you mean?
If you mean the /sdcard storage partition, that is normal.
yes, /sdcard storage partition.
Before flashing, I get warning message about wiping all data in my internal storage... what does it mean then?
The /data and /cache partitions. And the dalvik cache.
The first 2 are in the cwm main menu. Wipe data/factory reset and wipe cache. Dalvik is in the advanced sub menu.
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Griff1220 said:
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Click to expand...
Click to collapse
It appears to be asking for some encryption password according to one of these guys that posted in the following thread. But there is a way to get past it by the method in this thread...http://forum.xda-developers.com/show...02&postcount=7
Remove ur external sd and copy over/back up anything u want to save from ur internal sd before u do this, just in case.
data/chache wipe i should do right after flashing right?
I have a Captivate (model 1012) and was running Andromeda 3.
I guess the short version of this is as follows.
Wanted to flash back to stock Froyo from Andromeda.
First tried using Heimdall but failed 1/2 way through resulting in the dreaded Phone__!__PC icons.
Was unable to 3 button to download because my phone does not support it, so I used the 100K +1K ohm resistor "fix" which got me back into download mode.
Then used Odin3 One-click to reflash and applied the update.zip that it requested.
I am at the point where I can use Kies-mini to update to 2.2 which I have not done yet.
Everything is working just great except that when I make or receive a phone call, the person calling cannot hear me and I cannot here them.
It rings on an incoming call, I answer but I cant hear them and they cannot hear me.
One thing I do notice, is when I place a call and hit the speaker button, it turns green like the speaker is on, but I cannot hear it dialing like I used to.
After updating via Kies, the firmware version is 2.2 and baseband is I897uckb1.
Should I try to reflash or try a different modem?
Any suggestions?
Try re-downloading Odin 1click, verify the file size, then run it again. At that point, try the phone out to see if it has sound during calls.
I'm not sure why you're using Kies to go to 2.2....and your post is a little confusing. At one point you said you did not update to 2.2, then later you said it was on 2.2.
My bet is you just got a bad flash. Try it again, and you should be good to go. Heck, a factory reset might even do the trick.
Sent from my Cappy using Swype and my finger.
The problem is your modem. Replace it with one that is not an i9000 modem
Sent from my HTC Desire HD
Yes I agree. Sounds more like a modem issue than anything else.
One way to test would be to flash back to Andromeda and see if things start working right.
Wouldn't the Odin1-click put everything on new? PRL, SBL, kernel, modem and ROM?
Sent from my Cappy using Swype and my finger.
OwenW71 said:
Wouldn't the Odin1-click put everything on new? PRL, SBL, kernel, modem and ROM?
Sent from my Cappy using Swype and my finger.
Click to expand...
Click to collapse
yes. but he didnt actually use the real one click, because he indicated that he had to use a .zip file for it.....
Thanks everyone for the help. Was able to flash back to Andromeda 3 and everything works just fine. Not sure what is going on with Odin.
I would like to try it again. Can anyone recomend a good stock modem to try for my I897 just in case I get stuck again? The Odin that I used was I897UCJF6-final-OCD-REV0.exe (the update.zip I think was just for CWM).
Again, thanks for all the input.
Hello.
I'm having almost this same problem, just that I actually can hear the other people talking but they can't hear me. This problem doesn't happen when I go back to stock Eclair, there I can normally make calls and talk, but when I flash any custom ROM (I've tried Serendipity, MIUI and Darky's) this issue appears again :S
Please help me I'm really starting to lose my head
PD: Sorry for my English.
So I can't even describe how many things I frigged up here. This is the basic way it all went down: I went to replace my boot image using a method I found from the guy that does the Mobile Tech Videos. His batch file pushed some stuff (I think it made changes to the file system?) and unfortunately I kept getting the garbage screen on startup instead of my logo. I was still able to boot into Fasty III v1.3 though.
I went looking for an alternate method and found one that dated back to January 2011. It involved a different push to the filesystem (I think) and a .PIT file. Well, then the phone soft-bricked. I was still able to get into download mode, so I flashed I896UXKH2-HOMEBINARY.tar.md5 which, if I recall, is the stock Rogers Gingerbread update. Now I'm stuck boot-looping between the Rogers splash screen and the Galaxy S animation. I'm not sure if it's because there are just way too many things going on in terms of bootloaders, kernels, file system changes and ROMs. Volume UP + Home + Power doesn't seem to get me into recovery mode, although I may be able to do that using adb... not sure. I had Boogs kernel on there, and Fasty III. Did they get wiped when I applied the KH2 tar?
I'm basically looking for the proper method to get this thing back to stock 2.3.3 so I can learn from my mistakes and, more importantly, get my phone working.
Heading to dinner, I'm hoping someone can link me to a guide so I can tackle this when I get back. If you have any questions about any more specifics I will try and answer when I get back home.
Thanks in advance!
So I've found a post on XDA for the Odin Master Wipe (One-Click)... I'd rather not lose my internal SD storage, does anyone know if there is a slightly more complex route to take that would restore all of the stock bootloaders, kernels and ROM?
I am going to say you might have messed up your Partition. You need to find what ever is a "stock" PIT for your phone. I can assume the I897's should work but I don't know. That garbage screen in the beginning seems like either the image was corrupted or you messed up on the process. Either way I would recommend either a 1 click to JF6 (if your phone like those) or use that same KH2.tar with a suitable PIT assuming KH2 is froyo or eclair. If that KH2 is GB try a froyo first, fix your phone then worry about GB. I use a i897 so I could be way off on this.
prbassplayer said:
I am going to say you might have messed up your Partition. You need to find what ever is a "stock" PIT for your phone. I can assume the I897's should work but I don't know. That garbage screen in the beginning seems like either the image was corrupted or you messed up on the process. Either way I would recommend either a 1 click to JF6 (if your phone like those) or use that same KH2.tar with a suitable PIT assuming KH2 is froyo or eclair. If that KH2 is GB try a froyo first, fix your phone then worry about GB. I use a i897 so I could be way off on this.
Click to expand...
Click to collapse
The I897 and I896 are, as far as I am aware, virtually identical. I'll try to find a stock partition file for Gingerbread I896/7. I just flashed the device with the stock 2.3.4 file found in this thread, http://forum.xda-developers.com/showthread.php?t=1232703 but I'm guessing you might be right about having frigged up the partitions. Thanks.
armadadrive said:
The I897 and I896 are, as far as I am aware, virtually identical. I'll try to find a stock partition file for Gingerbread I896/7. I just flashed the device with the stock 2.3.4 file found in this thread, http://forum.xda-developers.com/showthread.php?t=1232703 but I'm guessing you might be right about having frigged up the partitions. Thanks.
Click to expand...
Click to collapse
Well, I'm boned. I flashed the PIT file and then the device wouldn't even power on. So I finally frigged my way into download mode again and now I'm trying to apply the Odin One-Click program with the Master Wipe. Any other suggestions would be grand.
And now, it seems that Odin One-Click is hanging at the Set PIT file... command. It's been at least 10 minutes. This phone is still capable of download mode, I must be able to restore it!
Dammit.
Right click the Odin and run as administrator first then connect in download mode. Be sure to hook up your usb end to the back of the computer or if laptop- to the first port. And you may need to reboot your computer just cause.
^ What he said. DO NOT try restoring partitions with a package with bootloaders, reduce risk to hard brick
4-2ndtwin said:
Right click the Odin and run as administrator first then connect in download mode. Be sure to hook up your usb end to the back of the computer or if laptop- to the first port. And you may need to reboot your computer just cause.
Click to expand...
Click to collapse
Any attempt to get into recovery or download now has left me with
RST_STAT = 0x1
PWIC = 0x3c
...
etc. I'm sure this is a screen that is not a good sign.
What about pulling battery and then trying to get into download mode.
If that does not work, then u need a Jig.
Don't worry, I have seen that screen or one similar on my phone as well. But a jig got me into download.
Will ur phone power on at all ?
Well, six lines of red hex status codes. This can't be good.
At this point I can't seem to get it to do anything but the six lines of code. That seems to pop up with the typical recovery combo. I don't have a jig, not exactly sure what that is but at this point I'm looking for any suggestions to get me into Download mode. Pull battery, sim, leave them in, whatever might help. This is the most boned I've ever been with an Android phone and unfortunately I need to rely on your experiences in the matter because I am not ready to give up on this phone. It's still a challenge and I love that, but this is also my primary mode of communication and I am the primary contact for my band.
This post will show you how to make a Jig... [HOWTO] *Layman's iGo Jig* [Solderless]
Thankfully, I just got 'er back into download mode... I'll let you know.
Unbrickable mod doesn't cost that much . I think 30-40 bucks....and if your handy you can do it yourself ., to prevent hadlrdbricks
Sent from my SAMSUNG-SGH-I897 using XDA App
Odin One-Click just seems to hang now...It's now sitting at File Analysis. I am happy that Download Mode is still available, but I'm really unsure of what to do. I'm on a laptop, Dell StudioXPS laptop with Vista 32-bit, I ran ODIN3Excution v1.00 as administrator but I'm still getting nothing. I also moved the cable to the USB port closest to me.
True but those $30-$40 + shipping can reach close to $100 on my end, dont know for someone in Canada.
Do you have spare cable? Wich ODIN 1 click you using ?
prbassplayer said:
True but those $30-$40 + shipping can reach close to $100 on my end, dont know for someone in Canada.
Do you have spare cable? Wich ODIN 1 click you using ?
Click to expand...
Click to collapse
Yeah, I have a spare cable. I don't think there is anything wrong with the cable, I think my tinkering has progressively made the situation worse. I am not going to spend money on this, there IS a process I can follow I'm sure. I HAVE Download mode capability, and a working computer. The Odin One-Click I'm using is showing Odin2Excution v1.00 in the title bar.
What did I do? **** up the partition table? So the bootloader doesn't know where to find the ROM? How can I undo this mess simply?
What I find most ironic is that I've successfully flashed kernels and roms to the phone, but the minute that I go and try to change the boot image, I friggin' brick the phone.
Go to dev section on one of the stikies and download Cezar's bootloaderless JF6 and give it a go.