Rooting the Captivate - Captivate Q&A, Help & Troubleshooting

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.

Related

[Q] Quick question about firmware version

Hi,
I've just upgraded to the galaxy s from the htc hero and had a couple of questions i was hoping someone could answer.
First off is there any way to tell which firmware versions are 'official' releases and which are leaked/beta versions?
I used to have a samsung s8300 so i understand the naming convention to some extent, however i was confused how the firmware jumped from I9000XWJG5 (July-release5) to I9000XWJM1 (M?-release1) and then finally to I9000XXJP1 & I9000XXJPC. It seems like the naming convention's gone out the window, or am i missing something?
With the hero all the updates are done using the recovery menu using update.zip files. Generally this update method keeps your settings & apps without the need to backup/restore every time. Is it possible to get the stock samsung firmwares in this format as it seems like odin will wipe everything? Or is it possible to trick kies into thinking your phone has a debranded firmware so it pushes the original roms instead of the bloated network ones?
Finally, i've seen various methods for rooting an existing rom. Are the update.zip files which root your phone rom specific or do they just root your existing rom regardless of its version?
Sorry if these are dumb questions, i've had a good look around everywhere and these are the only things i couldn't clear up.
Any answers are much appreciated!
Thanks,
Mark.
Hope this helps..
1. I9000XXJM1 is the latest official release for Android 2.1 (Eclair). All others after this more or less veer from Alpha to Beta..
2. Firmware naming convention is listed here Samsung Letter Codes
3. I doubt if complete firmware updates are done using update.zip. Not ruling it out but Nandroid/Data backup is probably the way to go..
4. update.zip are usually specific to ROMs unless indicated otherwise.
The sticky in this forum (Must Read)is fairly detailed, would have thought it is a must-read
reb73 said:
Hope this helps..
1. I9000XXJM1 is the latest official release for Android 2.1 (Eclair). All others after this more or less veer from Alpha to Beta..
2. Firmware naming convention is listed here Samsung Letter Codes
3. I doubt if complete firmware updates are done using update.zip. Not ruling it out but Nandroid/Data backup is probably the way to go..
4. update.zip are usually specific to ROMs unless indicated otherwise.
The sticky in this forum is fairly detailed, would have thought it is a must-read
Click to expand...
Click to collapse
Thanks for the reply.
Aye i've read through the faq it cleared most things up, was just these couple of things i stil wasn't sure of.
Is there any way to check whether the firmware is an official release or not? The link you posted is similar to what i had bookmarked from my previous samsung phone, but i'm still a little confused at to what the 'M' refers to in "I9000XXJM1", i'd have expected a 'G' or 'H'. Simarly with the JMC firmware.
thanks again!
Mark.
It also depends on region. But anyways do not install jpc or froyo betas. It will break your phone somehow
Sent from my GT-I9000 using Tapatalk
ickyboo said:
It also depends on region. But anyways do not install jpc or froyo betas. It will break your phone somehow
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I'm on JPC since 30-Aug-2010 and pretty happy with the performance so far.. No burns, scratches or breakages to report of
mark_glh said:
Hi,
I've just upgraded to the galaxy s from the htc hero and had a couple of questions i was hoping someone could answer.
First off is there any way to tell which firmware versions are 'official' releases and which are leaked/beta versions?
I used to have a samsung s8300 so i understand the naming convention to some extent, however i was confused how the firmware jumped from I9000XWJG5 (July-release5) to I9000XWJM1 (M?-release1) and then finally to I9000XXJP1 & I9000XXJPC. It seems like the naming convention's gone out the window, or am i missing something?
With the hero all the updates are done using the recovery menu using update.zip files. Generally this update method keeps your settings & apps without the need to backup/restore every time. Is it possible to get the stock samsung firmwares in this format as it seems like odin will wipe everything? Or is it possible to trick kies into thinking your phone has a debranded firmware so it pushes the original roms instead of the bloated network ones?
Finally, i've seen various methods for rooting an existing rom. Are the update.zip files which root your phone rom specific or do they just root your existing rom regardless of its version?
Sorry if these are dumb questions, i've had a good look around everywhere and these are the only things i couldn't clear up.
Any answers are much appreciated!
Thanks,
Mark.
Click to expand...
Click to collapse
I did the same last week... And I've been spun out with the whole firmware thing... of having to update to a base firmware then apply a zip over the top...
The hardest part of putting roms on the hero was picking which one to have .
Ibanez33 said:
I did the same last week... And I've been spun out with the whole firmware thing... of having to update to a base firmware then apply a zip over the top...
The hardest part of putting roms on the hero was picking which one to have .
Click to expand...
Click to collapse
Lol yeah thats true, too much choice Ended up settling on villainrom.
Sweet. Found the thread on updating to any official firmware using kies - will give that a try. Perhaps that should get added to the faq?

[Q] Question before flashing mods on my Captivate

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.

froyo rom for rogers i896 captivate

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.

Debranding the Captivate?

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.

Advanced ROM for SCH-i800 - Recommendations?

Just got this tab, and want to upgrade it from the crappy Verizon firmware. Would like the advanced features and root, but it must be stable for work and it must do 3G and/or 4G.
Apparently I have to install a ROM that is specifically for the SCH-i800 and not for the P1000? So how do I identify which ROMs are suitable?
I used to use CM7 on my Nexus One and now use MIUI which I think is great. Experiences on either, or some other flavor?
I am aware that ICS is available, but have the impression that it is not complete or stable. So I'd just as soon stay with Honeycomb or maybe lower as long as it can be relied on.
OK message received, there is none.
This matches my research. CM9 is shot through with bugs, and MIUI development is dead. No other contenders.
So I guess I stay with the factory firmware, root it, remove the crapware and set up security.
http://rootzwiki.com/forum/46-galaxy-tab-7-inch-developer-forum/
Sent from my Galaxy Nexus using XDA App
UGH, thank you JT. I am having a helluva time with this thing.
Trying SuperOneClick, but it does not recognize the device. No one says, but I suspect it depends on ADB. ADB apparently does not have the drivers for the SCH-i800, and I've no idea where to get them.
The Samsung sync software would not install in my XP running in VirtualBox -- drivers failed to install. So I plan on just putting files on the SD in another machine since I run Debian exclusively.
And there doesn't seem to be an alternative recovery like Clockwork or Amon Ra, but maybe I'm wrong.
Pretty much given up on flashing any better ROM, although I know you've done some good work, maybe for CDMA.
I'll check out that more applicable forum.
I also have the SCH-I800 from Verizon and the only ROM that I found that works with barely any issues is the GB 2.3.5 Galaxy Cube 3. You can find it here:
http://www.droidforums.net/forum/sa...galaxy-cubed-3-full-rebuild-11-21-11-a-2.html
If you have any questions or if you find any new working ROMS please let me know. Good luck.

Categories

Resources