Anyone give me direction on how to debrand the ATT Captivate?
Seems very little if not no info on it.
I have 2.3.5 on it (KK4).
Not to be dense, but could you please elaborate a little on what you mean by "debrand"? Are you looking to remove all the AT&T things from the software side? Hardware? Physical appearance of phone?
The SW. Make it more like a generic I9000 phone. I used to work at a cell phone manf and we had generic SW, and then the carrier branded SW around. 3/Hutch was one of the best for being very close to Generic, but obviously those phones were never sold in the US.
Right now I am stuck with ATT boot up screen, ATT only CSC, ATT bloatware, other stuff that identifies it with ATT.
I have a phone that has production released 2.1 on it (older android) and ATT has no clue what it is, yet it has ATT software. Much less is blocked via the network on it. Want to get the I897 Captivate closer to that if possible.
jmtheiss said:
Not to be dense, but could you please elaborate a little on what you mean by "debrand"? Are you looking to remove all the AT&T things from the software side? Hardware? Physical appearance of phone?
Click to expand...
Click to collapse
If you're really into getting rid of all things AT&T, you could flash the i9000 Gingerbread bootloaders to get rid of the AT&T startup screen, then flash CyanogenMod to get rid of everything else (it's open source, no AT&T specific-things other than maybe some APN settings).
If you're wanting to go to a more stock look, though, I'm sure there are some fairly stock-eque roms in the Development section that would suit you.
Where do I find the GB BL? I googled and didn't find.
The file names of the files are often very cryptic on what they should be used for. I did a LOT of phone flashing where I was, and as bad as our filenames were, they are nothing as bad as the ones I find. Any good clue to know which file to use for each segment (phone/CSC/PDA, etc)? They are rarely if ever named with phone/csc/pda in the filename.
jmtheiss said:
If you're really into getting rid of all things AT&T, you could flash the i9000 Gingerbread bootloaders to get rid of the AT&T startup screen, then flash CyanogenMod to get rid of everything else (it's open source, no AT&T specific-things other than maybe some APN settings).
If you're wanting to go to a more stock look, though, I'm sure there are some fairly stock-eque roms in the Development section that would suit you.
Click to expand...
Click to collapse
The easiest (and least hassle-laden) way that I've found to flash the Gingerbread bootloaders is to grab a stock ROM with them included. I would recommend the procedure in this post, as it has the i9000 BL's you're looking for.
I'll see what I can come up with. The only issue that I have heard with the I9000 files is the lack of a menu button causes issues. Can I do BL's only from that?
General rule where I was, you never go back on BL's, once you go forward you don't go backwards. Bricks it all too often....
?????????????
taethebest said:
222222222222
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
If you're really only wanting to do the bootloaders, go to this thread. There is a link in the first post that says "I9000 GB Bootloaders". Those will be the ones you want if you don't want to flash a full rom.
I'd say a more expanded version of your rule is to flash bootloaders as few times as absolutely necessary. Once you have these bootloaders on the Captivate, there shouldn't be a reason to change them again, as you can load all the Froyo, Gingerbread, AOSP, and ICS roms that are floating around the forum.
What menu button issue are you referring to? That's a new one to me.
I9000's don't have a soft menu/home button like the Cappy does, the I9000's have a dedicated button. Probably should have said home button. I have a I897, but we have a I9100T here at work I can look at too. I like the I9100T much better....
jmtheiss said:
If you're really only wanting to do the bootloaders, go to this thread. There is a link in the first post that says "I9000 GB Bootloaders". Those will be the ones you want if you don't want to flash a full rom.
I'd say a more expanded version of your rule is to flash bootloaders as few times as absolutely necessary. Once you have these bootloaders on the Captivate, there shouldn't be a reason to change them again, as you can load all the Froyo, Gingerbread, AOSP, and ICS roms that are floating around the forum.
What menu button issue are you referring to? That's a new one to me.
Click to expand...
Click to collapse
Ahh. It shouldn't matter - to flash bootloaders, you'll need to use Odin or Heimdall, so a menu button won't impact that.
Do I need to check Phone Bootloader Update in Odin? I tried the I9000 BL from that link and didn't seem to affect operation any. How do I know what bootloader is loaded?
If you flashed that Odin file, it should have a new first boot screen when you start up the phone - it should say "Galaxy S I9000" in white letters on a black screen, instead of the AT&T globe.
Tried again with BL option checked, it now shows the I9000 screen momentarily then goes to an ATT screen on boot. I guess part way there....
EyesofThunder said:
Tried again with BL option checked, it now shows the I9000 screen momentarily then goes to an ATT screen on boot. I guess part way there....
Click to expand...
Click to collapse
The first screen is the bl splash, the second is the kernel splash.
EyesofThunder said:
I9000's don't have a soft menu/home button like the Cappy does, the I9000's have a dedicated button. Probably should have said home button. I have a I897, but we have a I9100T here at work I can look at too. I like the I9100T much better....
Click to expand...
Click to collapse
You can still flash I9000 firmware on the captivate.
You will need a reoriented kernel from the cappy dev section, that will fix the screen rotation issues.
I posted a zip in this post to flash after the kernel to remap the buttons.
Related
QQ regarding this:
Are all SGS devices sufficiently similar enough such that a custom ROM for one (say the VzW Fascinate, or a Euro version) will be directly usable by others, or will what differences there are in hardware build (e.g., internal memory, camera flash vs. none, etc.) fragment efforts in the developer community enough that custom ROMs will be slower to achieve?
The Captivate intrigues me since an unlocked version should be very usable in Europe (and for getting rid of ATT bloatware as well as all the other fixes a rooted phone is likely to get before ATT bothers to do so).
They should all be the exact same internally, meaning the same rooting procedure of the european galaxy S, should also apply on the att version or any other version for that matter, and i hope so cause on the 18th im getting a captive woot =]
rafyvitto said:
They should all be the exact same internally, meaning the same rooting procedure of the european galaxy S, should also apply on the att version or any other version for that matter, and i hope so cause on the 18th im getting a captive woot =]
Click to expand...
Click to collapse
im getting a captivate too, however, there are some differences between the hardware and internal guts between the phones. To name a few, Storage Space, Flash for rear camera, and the front facing camera.
These could affect the internal guts/firmware on the device.
But lets hope we can get a sweet and fast root
Non of the gsm versions have flash beside the camera, ROM capacity and the front facing camera hardware have nothing to do with the rooting of any android device, im almost 100% that the european samsung galaxy S rooting procedure will work on any other samsung galaxy S variation.
We'll know soon enough...perhaps even within a week of the Captivate's release (hey, that's an interesting play on words).
The rooting procedure will work - however the recovery mode my be crippled as the M110S (Korea) version is. Need to wait for a custom recovery - or use ODIN to flash.
But if you dont have backup of the old firmware it might be more difficult to root.
Anyways the samsung version of android is in general pretty easy to root. (no locked bootloader etc)
For all intents and purposes the Vibrant/Captivate should be identical in every aspect except for accessories. (Wonders why those forums weren't just merged together). TMobile's 3G bands are different, too.
There's already a quickie root file posted by justadude over in the Vibrant forum. One file in the .zip needs to be updated to reflect the Captivate model number (SGH-I897) but in theory, it should work.
http://forum.xda-developers.com/showthread.php?t=723479
Here is the edited and signed root update. Anyone with a Captivate care to try? It's the Vibrant root with the AT&T model added, so it should work
For reference the Captivate is the SGH-I897
so rename this to update.zip place in the root of the SD connect to adb and type adb reboot recovery and select "Reinstall Packages" using the volume keys and power to select
EDIT: removed the update.zip please see this post for the updated one
nvm 10char
**double post**
xdaapp crash :-0
tried the signed update.zip and it didn't work for me.
@chaoscentral - I think your updater script is using DOS-style CRLF end of line characters. Try changing it to LF.
@zakdeutsch - Is that a Fascinate? I see ro.build.fingerprint = "verizon..."
Nope, certainly a captivate
I tried it on a Samsung Captivate and also had no luck.
wimbet said:
I tried it on a Samsung Captivate and also had no luck.
Click to expand...
Click to collapse
How do you have one already?
Regardless I hope this thing is rootable fairly quickly.
TexUs said:
Regardless I hope this thing is rootable fairly quickly.
Click to expand...
Click to collapse
Ditto. I'm thinking, though, that we're not going to see much movement on the root front till after release...
Anyone wanna give this one a try? I had edited the update script in wordpad before which I'm sure added some kind of funky formatting. So I made this one in ubuntu and signed it in windows(since I cant figure that one out in ubuntu)
This should work though, and keep in mind it only has the model numbers for the Captivate, no fascinate or epic 4g or vibrant
Hi to All,
Is it feasible now to install the Nexus One Android 2.2 on the Captivate?
Thanks
Muhamadabdelaall said:
Is it feasible now to install the Nexus One Android 2.2 on the Captivate?
Click to expand...
Click to collapse
No. I don't even know if anyone has even had a good look at the Captivate bootloader yet. Reportedly there is a FroYo ROM dropping very soon for the Korean Galaxy S and possibly soon for the US versions as well. Bodes well for getting 2.2 on the phone in the not-so-distant future. Probably.
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.
This may be a noob question but I would like to modify/flash my phone but I have a question before I do. I have done a few searches to find an answer but came up with nothing so far.
I have been browsing the forums for different mods that you can do for the Samsung Captivate. Out of all the mods that I have seen (One Click Lag Fix, Root, Cyanogen, Leaked Froyo Build, GPS settings changes, Removal of AT&T bloatware, unlocking phone for other carriers, side loading enable, and various others), they can ALL be undone using the Odin3 One-Click Stock Rom process correct?
ttp://forum.xda-developers.com/showthread.php?t=731989
Hoever, each captivate has unique phone identification information such as IMEI, Device ID, Wi-Fi MAC Address, etc? Are there any mods that change the unique information for each specific phone? If so, how does Odin3 One-Click Stock ROM process correct that? When Odin3 reflashes to "Stock" ROM, I just want to know how that works if each phone has specific information.
Thanks in advance!
yes they can be undone with odin one click, however once you stray from stock it is most likeley that you wont be able to update to the official 2.2 from att.
personally im going to wait and update to official 2.2 from att then root and nandroid backup and the fun will begin because I will have a backup of the official update with my unique device id to fall back on. in my opinion this is the safest way to make sure I dont screww myself and not be able to update. once that is done it wont be long untill someone builds a decent rom from scratch plus like I stated before I will have a nandroid backup of the update for my phone if I try something and dont like it.
If you still feel compelled I havent gone to the leaked 2.2 but I did have verry good results with stock 2.1 and voodoo lagfix on anather captivate. the phone was verry fast with verry few side effects well woth it if you really cant wait.. But just remember once you stray from stock I believe the only way you will get to 2.2 will be through these forums.
shadow65781 said:
But just remember once you stray from stock I believe the only way you will get to 2.2 will be through these forums.
Click to expand...
Click to collapse
anyway whatever you get from these forums will be much faster and cleaner then stock versions...
anyway i got question about the topic - i had stock 2.1 (JF6), backuped it, tried some cognition 2.2 beta, then flashed with odin to stock and the restored my backuped jf6
did my IMEI, Device ID changed?
(wifi's mac address cannot be changed)
thanks in advance
I am speculating here.
I dont think it can change any hardware I.D info but software I.D is anather story it could possibly cause problems with the O.S interfaceing with other stuff like market.
someone with more knowledge please chime in
Theres a new app in the app store (as of a few days ago) that allows you to change your Android ID#. Called Android ID changer
Unfortunately, it won't figure out what your unique # is. If you install Cognition, you have the same ID# as everyone else.
I'm not sure about Odin - stock. My Odin 2.1 # is different than the Cognition one. Ends in 43b1. I'd be really interested to know if anyone else could check their Odin 2.1 eclair JF6 (all stock, not modified) android ID # and see if it ends the same as mine. If it's different, then that means you can always revert to JF6 to figure out your real #. If it's the same, then I guess that means for the time being your SOL for figuring that out for now.
You can always check it before making modifications....
Shadow; you are probably right, but at the end of the day software is all that matters...
Thanks for the responses. Judging from what I have been reading on the replies so far, nothing can bring me back to my original stock android 2.1 OS with all original software IDs my phone had even if I use the steps outlined in the
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
forum post.
How do you find out what your android ID is?
gormander said:
Thanks for the responses. Judging from what I have been reading on the replies so far, nothing can bring me back to my original stock android 2.1 OS with all original software IDs my phone had even if I use the steps outlined in the
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
forum post.
How do you find out what your android ID is?
Click to expand...
Click to collapse
Just as long as you are running any of the stock eclair 2.1 without any mods all your unique id's wil display correctly, even if you have flashed to cog 2.2 or leaked 2.2 if and when you flash back to a truly stock eclair 2.1 the id's will return correct.
The android id changer app from the market will display the current android id your phone has when you open the app - it shows the current id just above the entry field where you can change your id. So download the app open it get you id write it down, save it in a safe place, then if you flash any rom the does not populate you unique id correctly you can reinstall the android id changer and enter your correct id manually.
Is [STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY method a "truly stock eclair 2.1" as you mentioned in your post Davy? Also, are there any other IDs I should be aware of and take note before I flash/mod anything?
Thanks.
gormander said:
Is [STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY method a "truly stock eclair 2.1" as you mentioned in your post Davy? Also, are there any other IDs I should be aware of and take note before I flash/mod anything?
Thanks.
Click to expand...
Click to collapse
I believe odin 3 one click in that thread is a straight rom off a phone with samsung jf6 stock install - yes I'm fairly certain it is stock. There is another odin 3 one click for the leaked 2.2 which is obviously not stock.
If you download an app from the market named simply " ID " it still give you four of your phones id numbers for your info.
I'm pretty sure all your phones id numbers are either generated from hardware coded info or your google account - so as long as you gave properly coded software on your phone these wil always populate correct - even if you install something that messes these up of you remove the bad software replace it with good software it should then populate the id numbers correctly again.
Such as the android id in the leaked froyo that isn't being generated but simply being copied to every phone it is installed on - when you replace the froyo leak or any of the roms built off the leak with one of the stock samsung roms your phone will then generate the id correctly again.
No thread jack but i thought id ask in here.
If im rooted and ONLY rooted on 2.1 will that not allow me to update to official froyo?
Nickel Dime Bay said:
No thread jack but i thought id ask in here.
If im rooted and ONLY rooted on 2.1 will that not allow me to update to official froyo?
Click to expand...
Click to collapse
maybe, maybe not. Some of the people who were rooted only (no mods) were able to update to the jh7 update. And from what I have heard mini kies has worked to update for everyone that flashed back to stock and tried to update that way - but this is all some what of a guess as we don't know exactly how att and/or samsung will role out froyo for the captivate.
You are all really funny. Your worried about getting an official OTA from AT&T so you won't mod your phones, lol. Your choice I guess but the last AT&T OTA bricked a lot of phones that had not even been rooted. The ROMS that you find on these forums are way better than any of the stock Samsung and AT&T put on them with their bloaty, buggy software. I won't do any OTA updates, I wait until the developers here fix them, remove the crap AT&T put's on them and speed them up. I give you guys credit though, staying stock sucks bad, it freaks me out to see that stock screen everytime I flash back to stock before flashing a new ROM to my phone. I only stayed stock for 2 weeks and never turned back, glad I did it too. I would've bought an I Phone 3g if I wanted to stay stock and not mod a phone. Go look around the forums and read the threads, don't just skim them or you won't learn anything. See what custom ROMS and kernels are cooking and what people are experiencing with them. We had the OTA rooted on here a few hours after the update was rolled out, you won't miss anything by not recieving it officailly from AT&T. Hell we already have some good Froyo ROMS and kernels. Keep waiting if you want but there's plenty of goodies here why wait?
Rhiannon224 said:
You are all really funny. Your worried about getting an official OTA from AT&T so you won't mod your phones, lol. Your choice I guess but the last AT&T OTA bricked a lot of phones that had not even been rooted. The ROMS that you find on these forums are way better than any of the stock Samsung and AT&T put on them with their bloaty, buggy software. I won't do any OTA updates, I wait until the developers here fix them, remove the crap AT&T put's on them and speed them up. I give you guys credit though, staying stock sucks bad, it freaks me out to see that stock screen everytime I flash back to stock before flashing a new ROM to my phone. I only stayed stock for 2 weeks and never turned back, glad I did it too. I would've bought an I Phone 3g if I wanted to stay stock and not mod a phone. Go look around the forums and read the threads, don't just skim them or you won't learn anything. See what custom ROMS and kernels are cooking and what people are experiencing with them. We had the OTA rooted on here a few hours after the update was rolled out, you won't miss anything by not recieving it officailly from AT&T. Hell we already have some good Froyo ROMS and kernels. Keep waiting if you want but there's plenty of goodies here why wait?
Click to expand...
Click to collapse
Different strokes for different folks man, Its not like im using the tw3.0 and the blue bubble background lol ive customized stock 2.1 how i want it to look and its working PERFECT for ME, fast as hell, gps locks on quick etc. Flashing a rom is nice and all but the risk of bricking youre phone is high (theres always odin i know) and if stock is working for people then more power to them.
The way I look at it is, the phone belongs to you, do what you want with it or to it as you please.
but I do agree with one point above, I personally would not trust a samsung/att update to not mess up my phone. But that does not mean it won't work well for you or that you won't be happy with it that way.
gormander said:
However, each captivate has unique phone identification information such as IMEI, Device ID, Wi-Fi MAC Address, etc? Are there any mods that change the unique information for each specific phone? If so, how does Odin3 One-Click Stock ROM process correct that? When Odin3 reflashes to "Stock" ROM, I just want to know how that works if each phone has specific information.
Thanks in advance!
Click to expand...
Click to collapse
IMEI can never change. I don't think your device ID can change buy your Android ID can change as you've been told by those before me. If it possible to change your WiFi MAC address, only I'm not sure how to do it. If you can do it in a full version of Linux, I don't see why it's not possible on our phones. Also, before you do any mods, make sure you backup a couple files onto your computer for safe keeping. The ones I'm talking about are in the /efs directory of your phone and relate to unlocking the phone for other networks. The second you go to mod your phone, these files will be erased and replaced with ones that are harder to get your unlock code out of.
is anyone building a froyo rom for i896 captivate from rogers, there has been alot of problems with people flashing to at&t roms and failing to restore their original stock rogers rom. This is the only reason keeping me back from flashing to an already available 2.2 froyo rom. I know nothing about linux, programming or any of that stuff and was wondering how difficult it would be to build a rogers 2.2 froyo rom or are there pieces missing to build it?
look at this tutorial:
http://www.mmacleod.ca/blog/2010/10...sung-galaxy-s-captivate-to-android-2-2-froyo/
stavs said:
is anyone building a froyo rom for i896 captivate from rogers, there has been alot of problems with people flashing to at&t roms and failing to restore their original stock rogers rom. This is the only reason keeping me back from flashing to an already available 2.2 froyo rom. I know nothing about linux, programming or any of that stuff and was wondering how difficult it would be to build a rogers 2.2 froyo rom or are there pieces missing to build it?
Click to expand...
Click to collapse
saddly not yet , were canadian , meanin we get phones 6 month later , most dev will ( eventually mod our own rom )
redjersey said:
look at this tutorial:
http://www.mmacleod.ca/blog/2010/10...sung-galaxy-s-captivate-to-android-2-2-froyo/
Click to expand...
Click to collapse
ahh much appreciated, will look into this a bit. thankyou.
DAGr8 said:
saddly not yet , were canadian , meanin we get phones 6 month later , most dev will ( eventually mod our own rom )
Click to expand...
Click to collapse
i dont see how it could be THAT difficult to take the at&t leaked froyo rom and make the necessary adjustments for the i896 captivate. I just dont want to lose my GPS function (its working very good) and i dont want the annoying AT&T splash screen
stavs said:
i dont see how it could be THAT difficult to take the at&t leaked froyo rom and make the necessary adjustments for the i896 captivate. I just dont want to lose my GPS function (its working very good) and i dont want the annoying AT&T splash screen
Click to expand...
Click to collapse
If you know nothing (your words: first post), then how can you gauge the difficulty of doing such a thing?
I just helped one of my friends load the 2.2 AT&T i897 update, working fine on his Rogers i896. Soon as Cyanogen release something for the Captivate we plan to be updating him again.
At this point for the GPS to be fixed I'm pretty sure we need the source code or atleast a rom from ATT that it works 100% correctly with.
The cognition roms for the I897 work fine on the I896 -- thats pretty much how I've had my friends Rogers Captivate running froyo since launch week. You obviously have to load your own APN settings and whatnot though.
PS. Probably best to use the rogers modem file -- it's in the I896 thread.
Lots of people are running or have tried there. I do have some build prop changes and apn changes for the rom but until I have my friends phone back here to test them I don't want to share something that could very well just bootloop. Plus I want to try cognition b2.4 on there and adapt the changes to that since that just came out too.
stavs said:
i dont see how it could be THAT difficult to take the at&t leaked froyo rom and make the necessary adjustments for the i896 captivate. I just dont want to lose my GPS function (its working very good) and i dont want the annoying AT&T splash screen
Click to expand...
Click to collapse
you get the drift , its nto complicated , its just we need someoen we same interest as us i.e a candadian dev or a bored US one
btw I use all the roms and I just flash our rogers modem on top of it so my gps is perfect
well one of the main reasons i want to flash to a 2.2 rom is because i have read that it improves battery life and fluidity of the OS, i could possibly live without flash 10.1 and the use of installing apps on my sd card for a little while.
I'm on my 7-8th charge right now, could be slightly more and my battery life is average at best. Had it running 2 hours before i went to school, fiddled with it a little (a little music, a little browsing, testing out GPS functions) then tested out the GPS using Ndrive to school. During this time i had some ocassional 3g use (<10 minutes), about 20-30 minutes of wifi browsing, and about 3-3.5 hours of listening to music. I also used the gps coming home to test out its accuracy and functionalities. By the time i got home my battery was red.
I've calibrated the battery also, and used several guides to help improve battery but nothing that i have done has made any dramatic difference. I was thinking maybe a 2.2 rom could help with that.
Sorry, i m very new to Android phone ~~~
I wanted to flash my i896 into Froyo 2.2
but so far, looks like there is no way to get off ATT split screen at bootup right ???
DAGr8 said:
you get the drift , its nto complicated , its just we need someoen we same interest as us i.e a candadian dev or a bored US one
btw I use all the roms and I just flash our rogers modem on top of it so my gps is perfect
Click to expand...
Click to collapse
It's been hit or miss with that keeping the gps fixed (depending on the phone -- i flashed 3 -- and what it was coming from or what the user was playing with -- mostly different cognition versions). The key factor there seems to be doing a wipe even after a fresh reflash, then it seems to work well consistently. Thanks for the feedback on it. I don't have a captivate myself so it makes it impossible to do any realworld testing on my own.
ime2010 said:
Sorry, i m very new to Android phone ~~~
I wanted to flash my i896 into Froyo 2.2
but so far, looks like there is no way to get off ATT split screen at bootup right ???
Click to expand...
Click to collapse
Yeah I'm too nervous to do much digging around there -- I think the first one is being kept along with the bootloader. Some other folks on here were trying to sort that out. The second part of the bootscreen is easy to change. I think we're going to be stuck with the ATT one until we see something from Rogers (2.2) or someone does some very tricky and potentially dangerous work. I just wouldn't worry about it for now I were you. In theory most if all damage you'd do could be repaired with ODIN but definitely don't quote me on that.
so far my flashes have been pretty rough.
I came from a nexus one where i could just load the .zip file and install easy as pie from there. This bul**** odin flashing drives me up the damn wall, but i can get it done, I have had this phone for a week and have tried many roms. I tried going back to stock rogers and it was a complete fail. When odin flashed back to rogers, i still had the stupid att logo, but whatever i dont see it all the time, and it would randomly try to download things from the market. Tried reflashing, and the same thing, except 5 mins later and the market just wouldnt download a damn thing for me. I dont have a reason for this but whatever.
I have tried going to stock i897 att rom and my phone will not boot, it just just a boot loop, so i cant even go to perception build, so i had to odin flash to cognition 2.2.
So far I am pretty happy with it... battery life is better than stock, no lag, it comes pre-rooted, but my signal isnt strong like when i first got the phone on factory stock OS. I want to flash the modem files only but i havent been able to find the files or the instructions how to.
I am thinking of going back to the nexus one, but am willing to make this phone work for me. Only one more thing i dont like about this phone, is the camera! Out of all things the camera kinda licks a sweaty nootsack.
i896 i897 i9088
I think i896 is the same as i897。You can use adb to enter download mod, and use i897's rom. In china, we have i9088 wich is Chinese captivate. It can also use i897's rom. No Bug, no problem.
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again
Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.
I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.
If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....
the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.
Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!
another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...
Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.
oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!