[Q] Froyo, From Leaked To Official - Captivate Q&A, Help & Troubleshooting

As the title says, this is what I'm trying (have been trying....) to do.
I got my Captivate for Christmas 2010, I can't remember what exact version it was running, all I know is that for a fact it was Eclair.
I wish I knew what stock I had on my phone and all that jazz, but the one thing I never read before flashing or rooting my phone was that I should root and make a Nand Backup before hand. Oh well right?
Anyways, basically here is what I've done to my phone:
I flashed ODIN-1-Click for the leaked Froyo JI6 - I897UCJI6-OCD-REV02-Low-designgears_1
had absolutely no problems, everything worked like a charm.
Next, I used SuperOneClickv1.5.5-ShortFuse and I chose "Root" and "Enable Side-Loading"
again, no problems.
From there, I proceeded to do the following:
-Install of TiBu, AdFree, Terminal, Root Explorer, SGS Tools, and Busybox
-TiBu Used to "Freeze" most bloatware on phone
-Terminal given #su root command and approved
-AdFree added, packages installed
-Within Terminal, added exception to WordsWithFriends to allow ads
-SGS Tools used to replace default Camera App to allow power button for capture
-Root Explorer used to replace TW_Touch tone to modified 5% audio level version...I'm sorry, but at the lowest System Volume this is just way too loud.
-Installed Go Launcher EX and made my phone look awesome
-TiBu used to Freeze TW Launcher
I don't think there is anything else I've done with my phone that is really worth mentioning. No Lag-Fix unless it was included in my JI6, but I do know that I have free Wifi Tethering.
Now, for those still following, after all this, obviously the Official Official (Not-Leaked) Froyo came out, not a big deal, because I probably would've gone crazy just using Eclair for 2 months (I kinda flashed my phone on the 3rd day of owning it after coming from basically a RAZR V3).
Soooo, in my attempts, to get the official version of Froyo (flame on me, I don't care), I have "Bricked" my phone twice on separate occasions trying to go clean.
By bricked I mean AT&T Boot Loop of Doom w/o the ability to use any of the keys. So hey wouldn't you know it, but I have a USB Jig now.
1) WTF do people mean when they say to Flash back to Stock? There are like 20 different things available, which one is stock? and what would mine have been new out of box at Christmas 2010?
The thing that Bricked me twice was JF6 which I though was stock, guess not, I'm not sure... I have no idea why it won't work for me or if I'm doing something wrong, or I got an incomplete download of it, it's title is: I897UCJF6-final-OCD-REV0. On the other hand, I have managed to get JH2 to work (idk wtf JH2 is, I don't hear it often, but it got my phone to turn on), Kies actually managed to recognize my phone, however I could not update it in Kies and if I remember correctly, Mini-Kies wouldnt recognize the phone.
And also JI6 also allowed me to recover from Brick-mode, which I Flashed to Originally, and obviously it wont show up in any Kies in any way/shape/form...
Anyways, if anyone can provide any info, help, or advice, I would really, really, REALLY, appreciate it.
What am I doing wrong?
Help?.......
Now aside from that, I know there is a pre-release version of KB1 running around, but has anyone managed to get a version of the Official February 24th KB1 out to the masses for download that doesn't involve Kies?

Sorry to bump this, but I'm still looking for any possible advice anyone might have. I've tried using the search feature but to no avail. I've found "similar" things to mine, however no one seems to either have the same problem I have or be in the same situation.
I apologize for it being such a long read, but I just wanted to thoroughly describe my situation in the chance that it would be able to further increase the capability of someone helping me.

Here you go, these are the two files that people mean when they say go to "stock".
2.1 is the "Official Stock" for 2.1 - http://www.megaupload.com/?d=SBSMALFJ
2.2 is the "Official Leak Stock" for 2.2 - http://www.megaupload.com/?d=QL6NX702
As far as I know, there isn't a Odin One-Click for the "Official" Official 2.2 yet.
If updates are free if you're with AT&T... How about just going to 2.1, then upgrading it by connecting to AT&T that way? Just an idea

Sounds like the build of your phone is 1010 or higher so odin jf6 likely won't work, but you found that out .
You can try this
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
You are already through half the steps, just flash jh7ota
Or you could modify your recovery and install clockwork and flash cognition 4.1.1 which its more our less stock kbi that is already rooted and debloated
Not sure of a cmw flashable kb1
CM7

Excellent! I totally forgot about that, thanks mcord11758!

Ok, somethin i learned when using kies to upgrade to 2.2. 1) USB debugging has to be on. 2) Make sure to UNroot your phone before trying to upgrade with kies 3) I also had the boot loop. Restarted in recovery mode and cleared all user data. That fixed it.
Also, think about upgrading to superoneclick 1.7
BTW, if you want CWM to work, you should shell root before regular root (reboot after shell root) and dont forget to enable nonmarket apps
GOOD LUCK!

@venomio: I already have those two files, but thanks for confirming that no one has released an official KB1 2.2. I'm glad to know I just haven't failed despite looking thoroughly.
@mcord11758: I actually hadn't thought about that. I thought that I'd be set with JH2 in terms of being allowed by Kies to update.....yeah no I was wrong obviously. I just figured the additional steps involved with the JH7ota would make Kies hate me more. But yeah, I think this may be my solution- although if for whatever reason it didn't work it'd just be really annoying. I've already had to revert to JI6 twice now hoping for the Kies update.
Out of curiousity, why in the world does JH2 work on my phone?
And what exactly does it mean to have a 1010 Captivate?
Still @mcord11758: Now I do have clockwork recovery installed (still on JI6 as I'm typing this), however for whatever reason, I can't seem to see any of the bonus features that it should provide in the recovery screen. I think I've read that this is a typical problem and I need to get 3e_Recovery or something, but I wasn't really sure how it worked or how to apply it. And the hold up I have on Cognition is the fact that I don't know how easy it is to revert everything back to default (like lag fix and stuff). Any info on these topics would be appreciated
@mrhaley30705: Yeah, I'm updated to SuperOneClick 1.7 now. 1.5 Just happened to be what I used originally, and for whatever reason wouldn't work any longer after further trying to flash things in these recent turn of events. Long story short, after a lot of pain trying to re-root, I realized 1.7 was out, got it, and it worked.
I will say that I have avoided the Shell Root as I don't fully understand how it works and I've gotten by using just the "Root". Isn't Shell Root un-reversable? I'm just worried about that since I'm attempting to get a Kies Update.
@Everyone/All: I really appreciate all the feedback big time. This has been a pretty stressful, long process even though at times it has felt fun and rewarding.
I think I'm going to do what mcord11758 said when I'm not at my girlfriends place. For whatever reason, if I need my Jig, I don't want her to see cuz she'll know I'm messing with my phone again. (She gets upset at me when I get upset at the phone). I'll leave you with a fun image that I saw from someone's sig once.
Btw, anyone who posted above this will have received thanks.
I hope that's not totally lame of me.

Update: It worked!!!!
I Officially have the Official final release of KB1 Froyo 2.2
I used the following as suggested:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Afterwords I followed:
http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=558&AT_ID=368733
And I was able to get Kies Mini to recognize the phone (unlike with JI6) and allow me to select Phone Upgrade (Unlike with JH2).
One big thing I've seen, is that my phone is missing the GMS Updates, I do not have google's GenieWidget (News and Weather).
I don't know if anyone else is having this problem, and I don't know if there is any fixes. I do remember though, that while I had JI6 installed, apk's of the GenieWidget I found around the web would not work.
I know it's probably lame, but I was actually hoping to get this, as I was trying to get it in JI6 as well.
Pic attached of my desktop showing Kies working.

Good stuff, great that you managed to get it going!

Related

CONFUSED N1 Owner

Hello folks,
Well I recently made the switch from iPhone OS to Android , picked up a used Nexus One in pretty good shape, no scratches, like new and what not, the phone is amazing BUT I am having a hard time understanding some stuff (I thought I was getting a stock N1, and it seems it has been loaded w/ custom ROM and is rooted and unlocked. -which not bad in my opinion, but...
I still have some questions, I am trying to update to Froyo 2.2, and im not sure if I will ever get OTA since the phone has been messed around with and if i manually update to 2.2 it will cause trouble.
1) When I boot the phone it shows the "lock" to be opened, so I am assuming it is oem unlocked, the phone has working WiFi tethering (just like in 2.2)
2) also in the menu of the phone there is an app "superuser permission" which thats why assume the phone is also rooted
And finally In the "About phone" I get the following:
firmware 2.1-update1
baseband
32.36.00.28h_4.06.00.12_7
kernel
2.6.34-cyanogenmod
mod version
cyanogenmod-5.0.8-n1-test3
build
epe54b
I have reset the phone to factory settings, but the same info comes up everytime. the phone runs flawless, no lags, overall i love the phone.
And finally if anybody knows please feel free to share, I am trying to open port 80 on the N1 while it is running Wifi tethering and the only way i have found to do this is if the N1 is rooted, correct me if im wrong... i have a rovio that is refusing to connect to the N1s network...
Any positive input will be highly appreciated! thanks!
Your not very confused!
Your phone is unlocked and has root. its running cyanogenmod-5.0.8-n1-test3.
You can install a custom froyo rom without too much of a problem from recovery. Remember to nandroid-backup everything from recovery first.
Get into recovery by holding down the volume down button as you press the power button to power on the phone.
Heres an example of tethering via usb/forwarded port
http://blog.tangorangers.com/2009/02/tetherbot_android_and_slackware_how_to/
you can install 2.2 with no problem but you have to manually do it. you might get a notification for ota's but you won't be able to install them. just install it manually.
Man you guys are awesome! thanks for clearing this up for me.
atomoz said:
Man you guys are awesome! thanks for clearing this up for me.
Click to expand...
Click to collapse
Yeah man, you're money. For a used phone it is set up in possibly the best way possible for someone new to android and ready for you to throw the new CM6 ROM on there. You even have the proper radio already. You're good to go.
You can install Froyo in various ways. If you want total stock you can follow the instructions on this link and let OTA froyo install itself. If you need root you can download that from HERE
This method requires SDK installed with Fastboot on your computer with mandatory USB Drivers.
Or you can go the very easy way and use ROMs that is allready cooked, ready to flash in recovery right over your old ROM, like the link that is in my signature. It works great for me and is pretty much stock with root and a couple of extras you can delete via ADB if you don't need them..
Just download the Rom, drop it on the root of your SD Card and flash away in Recovery. all done!
What you are running is a test version of Cyanogen which is not the stable version. So it seems the previous owner didn't bother flashing it.

[Q] noob about to root and lag fix. advice wanted

Hi all, I hope you're not all tired of another noob posting up how-to questions. I come from a pretty solid background of writing modified firmware packages Motorola and Blackberry units, and writing custom themes for them both, so I am a bit familiar with the processes involved in rooting. Android is an entirely new beast though. I love it already, but I've also identified some things I'd love to be able to change. I've been reading everything I can in these forums for the past week, and I think I might be nearly ready to start diving into the root world. Yes, I've used the search a LOT Before I do root though, I wonder if you all might be able to add some insight into a few questions I haven't found the answers to thus far:
My rooting goals: remove the AT&T bloatware, possibly do a lag fix, and above all, do it the safest way possible. Baby steps first for me.
1) Rooting methods: Should I do the manual way, I found in that pdf guide on this site, the "GalaxyS_One-Click_Root_All_Models.zip" method, the mystery "update.zip" folder method, or the "one click root lag fix" method? Which is the safest and most tried and true for Stock 2.1 f/w, Baseband I897UCJH7? Also, what would be the best method to use if I wanted later to unroot?
2) Lag fixes: I've read that lag fixes can cause major problems when trying to undo them later on. Is there a lag fix that works well that is safer than others to load that can be removed easily? Are lag fixes even worth it?
3) Odin3: Am I correct in assuming that since I have JH7 that the most recent version of Odin is not capable of fully restoring my phone back to stock? I've been seeing posts from many people say that even using Odin, their phones get stuck during the revert process and cannot get back to stock. This is probably my biggest concern of all, in case I brick my phone. I've done that a LOT of times with Motorolas, and it's not a bit of fun trying to restore them.
Thanks very much in advance. Best wishes to all
The first piece of advice I have is make sure you have a cappi that you can get into recovery and download modes via the button combinations - if you can do this then you will be able to recover to a working configuration from just about any situation.
second, make sure you want to do this, because as you can get back to a "stock configuration" once you begin applying lag fixes or custom roms you will not likely be ever able to get back to your own stock configuration.
As for which rooting method - I have used and update zip and ryanza OCLF to root. Both of these methods are easy to unroot - at least until you begin applying lag fixes and/or custom roms.
If you are sure you want to move forward and root the very first thing you should do after rooting before you do any lag fixes or remove any bloat is get clockwork rom manager. Learn how to use rom manager and make a full nandroid backup of your phone before you do anything. If you have a good nandroid backup saved in a safe location then you can use this to get back as close as possible as you can to your own stock configuration later on.
Oden3 will get you back to a stock jf6 configuration. This will not be your stock configuration, but it is a working stock configuration.
Lag fixes do improve the lag in the file system some. However, before you play with any of them educate yourself as much as you can about the particular one you are going to try and use. I have applied both OCLF and voodoo and have been able to remove both of them. But if you don't follow the steps correctly you can have problems - after all with the lag fixes you are reformatting part or all of your data partition where the os is residing which is inherently risky. You can easily lose data and even soft brick your phone forcing you to use Oden3 to get back to a working state.
Lastly, I am running Cognition 2.2 beta 5 very successfully - and I do recommend it for anyone that has entered the rabbit hole of modifying this phone. And with my current config my phone is running so well that the lag fix is not needed for me anyway. My phone is running smooth and fast.
P.S. Just make sure you are not going to have any major regrets if things go wrong before you do anything at all, because any and all of these steps have some amount of risk associated with them. Make sure you are prepared for dealing with voiding your warranty and even though it is hard to brick this phone, it could still happen so be ready for that too should it happen.
i would agree, go with cognition 2.2. i only had my captivate for a day, and found it very easy to get it installed without any hassle.
Thanks for the info all. I've read about Cognition a fair bit and was wondering if I ought to go for it. What are the differences between it and the standrd Froyo leak?
A more pressing question: If I went to Cognition 2.2, would I be able to easily get the official release OTA and install it normally when/if it becomes available? Are there step-by-step guides out there for getting that release onto and off of the phone? I'd hate to get Cognition on there and find out that i couldn't easily get it back to a state where I could get the full deal on there. I've read some horror stories about just that lately...
charging rhinos said:
Thanks for the info all. I've read about Cognition a fair bit and was wondering if I ought to go for it. What are the differences between it and the standrd Froyo leak?
A more pressing question: If I went to Cognition 2.2, would I be able to easily get the official release OTA and install it normally when/if it becomes available? Are there step-by-step guides out there for getting that release onto and off of the phone? I'd hate to get Cognition on there and find out that i couldn't easily get it back to a state where I could get the full deal on there. I've read some horror stories about just that lately...
Click to expand...
Click to collapse
If you are wanting to get OTA updates then I wouldn't even root your phone - while it is possible to still get OTA's after rooting, once you begin modding (lag fix, or custom rom) you oare increasing making your phone less and les compatible with any OTA available.
NOTE: I personally will not ever apply an OTA myself - but rather will wait for someone else to create a custom mod of any OTA feature I like - them donate that dev a few dollars and use their mod.
Im getting my cap this Friday, I was going to post the same thing OP. Looks like cog 2.2 is the way to go when i get it.

[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.

[Q] Bricked phone after JI6/Odin

Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
ApplCobbler said:
Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
Click to expand...
Click to collapse
I feel your pain. Been there, done that. Although your process of bricking reminds me of a more sophisticated approach....lol....mine was out of total complete noobness.
Question:
1) Can you manually boot into download/ recovery manually using 3-button combo? If so you have hope (meaning your phone is basically "un-brickable").
-Bet that made you feel better huh?
-If you can't use 3-button to go into either modes, then you are in the same boat as i was. Hope you are still within your 30 days, or at least warranty. One way to tell if you can/ can't go into either modes is to check your "Batch #."
a) remove battery
b) look below your Serial Number
c) if your Batch # = 1007 = You are safe
d) Batch # = 1008 = good luck
2) When you say Brick, do you have the unfortunate "Phone (!) PC" screen? If yes, then its a "soft brick." If No, then its a "hard brick." I would start to worry.
3) According to your post, it sounds like you have the Regular Odin and NOT the One click version, correct? If you have regular Odin, i would at least try the One click. Regardless, both versions should be able to get you back to stock (JF6), but we already know how well your current version Odin has gotten you.
If you need help, there are TONS more knowledgeable people here in the Captivate forum than I. They should be able to help.
Good Luck!
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Stop trying to flash Froyo. Flash back to stock then master clear. Then go read the threads in the development section of the forum before flashing anything. The fact that you tried to apply Voodoo to Froyo and you tried to use one click lagfix on Froyo shows you haven't read and don't know what your doing. You corrupted something by flashing incompatable stuff, flash back to stock and master clear for now. Read a bit and then flash Froyo.
ApplCobbler said:
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Click to expand...
Click to collapse
LOL . I as well. I know enough to be dangerous.
Now, on to business. If you actually read what Rhiannon has posted for you, and click on the actual link itself, you will realize that the version of Odin you are using (yes the one click) is NOT the correct version for flashing back to stock (JF6/ Eclair.....NOT froyo). Remember, if all else fails....."The One must return to the Source...." <-----Plus 9,000 to whoever can guess where thats from.
Obviously your phone falls within the 1007 since you have the Luxury/ Advantage of manually entering Download/ Recovery mode....i wish i did.
Rhiannon224 said:
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
Click to expand...
Click to collapse
Well Said!
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Click to expand...
Click to collapse
I see you are still on Cog 2.2 B5......dont care for 8 or any of the new ones? Or Sheps? What's your story?
Mine is simple....Patience. lol
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
Click to expand...
Click to collapse
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Rhiannon224 said:
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Click to expand...
Click to collapse
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
spartan062984 said:
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
Click to expand...
Click to collapse
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
ApplCobbler said:
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Click to expand...
Click to collapse
Again, sorry if I sounded harsh, i am just trying to help you get out of the mess you're in. You can flash Froyo in the future you just need to learn about these ROMS and fixes so you don't have these kinds of headaches. I will stop repeating now. i really hope this works. I know your stressed and wasn't trying to give you a hard time, I just thought you were missing something and I am from NY and we are pushy Let us no if you get it working.
I have made some mistakes along the way too and it was because I didn't read the instructions clearly so I do understand how you felt.
Rhiannon224 said:
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
Click to expand...
Click to collapse
""Sory to hijack the thread""
I started it. No worries. I too would love to have voodoo. So far, with stock OS, ext2 + OCLF seems to work for me....for now. Keep in mind that i too would like to have the functionality of a Phone. That was my intention in the first place...lol.

[Q] Rooting my captivate, can't copy root file to phone

Hey folks. I'm bailing on Gingerbread because it was causing me too many problems. I'm trying to get back on Firefly 3.0 and I'm stuck at getting the phone rooted.
Whenever I try to copy the Root.zip from the AIO folder over to the phone's root folder, I get an error about the parameter being incorrect. I'm not sure what to do at this point.
Use Fugu root? Easier.... Also depending on what Gingerbread you are on there are kernels that have the root scrip baked in them.
^ you misread he's not on gingerbread, he wants to flash firefly.
You don't need root to flash a ROM. Odin a kernel that has cwm baked in. boot into recovery and flash the ROM.
Thought he was on GB trying to get on... you know what ya I missread. @OP do what Studa said xD. Wonder why people think they need root to flash roms..... I blame Rom Manager.
I know I don't need to root the phone, but in order to get certain things done on the phone, it's necessary.
I'm actually at a wall right now. I used SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click which successfully booted my phone to ATT 2.2 firmware, but I can't get any Odin to pick up on it now. I've tried five different Odins.
At this point, I think once I get the phone up and running on Firefly, I'll be walking away from flashing until I get another phone. Then I can use this for testing, etc.
On a side note, before I started this project yesterday, my modem was messed up. Now it would seem I have a successful connection to wifi, which I couldn't get.
As great as that is, I still can't get Odin to pick up my phone. Any thoughts?
Was that kb2 package heimdall?
If so you have to uninstall the heimdall driver and reinstall the Samsung driver.
Either way I would reinstall the Samsung drivers but it is a must if you used heimdall add the drivers conflict.
Alright. That's done, but I'm on I896UXJL1-stock now, and I'm pretty sure in doing that through Odin 1.85 I unrooted the phone. Correct me if I'm wrong. That's why I used the ATT stuff, because it auto-rooted the phone.
So it would seem I have some issues to work through. I can either root my phone and be stuck with ATT firmware that I don't want, or I can unroot the phone and use Rogers stock and hope for the best with Firefly.
This is by far the most confusing computer-related issue I've ever worked with. There's too many options to play with and they all work differently.
Why would you be stuck on at&t firmware? Why do you need to root before flashing firefly? Why don't you root Rogers stock?
you're confusing everyone involved lol
Okay, so maybe I'm a little in the dark on the rooting issue. Basically, I'm going back to Firefly because I thought it was amazing. Fast, responsive, and no issues I can think of on my phone.
I'm rooting the phone because it's my understanding that in order to spoof my location in order to get certain apps (Google Music), I'd need to be rooted.
I'm having a hell of a time trying to get this done, and my biggest problem, to reiterate, is that I have about fifteen different Roms, all either ATT or Rogers, three different Pit files, and so, so many Odin programs.
I'm now on 2.1 with that Toronto stock firmware, in order to work around the 3e error in recovery mode when trying to put on Clockwork. Unfortunately, now I'm getting some other error in regards to the Update.Zip file, Status 7.
I apologize for confusing people, but I promise I've read as much as I can about the tools I'm using, but I'm running in circles, flashing back and forth trying to find solutions.
you do not need to root before flashing the rom. it will be rooted after and then you can do what you need to do to get your apps working if you need to (firefly contains canadian locale cause its based off of rogers froyo firmware) changing stuff before you flash so apps can work is a waste of time as the flash will overwrite the firmware you just tweaked.
now, since your on eclair i'm attaching an update.zip that contains cwm, put it in the root folder of your sdcard boot into recovery select reinstall packages twice and it should boot into cwm where you can then flash firefly.
You're a frickin' genius, Studa. Don't let anyone tell you otherwise. I've got Firefly on thanks to that Update file, and I'm getting the ball rolling on everything else. If I wasn't so broke, I'd donate, but I hope my thanks is good enough. I really appreciate the help. It cut through twelve hours of stupid.

Categories

Resources