yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Subie_07:
My experience with JH7.

I used the ODIN3 One click download to do a master reset and flash back to JF6.

Flashed JH7 Re-partition ... no boot...

Then I read not to use the ODIN3 one click when going to JH7 ... so I downloaded JF6 and continued to attempt to flash JH7.

Flashed JF6 No re-partition then to JH7 re-partition ... no boot...

Flashed JF6 No re-partition then to JH7 no re-partition ... no boot...

Flashed JF6 Re-partition then to JH7 Re-partition ... no boot.

Finally I flashed to JF6 Re-partition then to Jh7 no re-partition ... BOOT...!!

I was happy!

Now I have another problem... I can not undo the lag fix... I am using the APP Lag fix and it fails every attempt to undo... so now I am going to have to flash back to JF6 flash to JH3 restore my rom with Clockwork undo the lagfix then back up again then flash back to JF6 then back to JH7 then restore... eff...

The reason I plan on doing this is because when I first got to JH7 with everything stock the phone was moving alot faster then it was with JH3 stock... and with the lag fix... and when I restored everthing back the phones performance was the exact same as JH3 lagfix was... which was good but I dont know if it is in fact faster or it was just the new firmware placebo...

Anyways just posting up my experience getting to JH7 in case it helps some one else.

EDIT:

Oh and I haven't had a chance to test the GPS yet.
[Captivate Android Development] ewingr:
Do you know if the 'Vibrant Guys' report a working GPS?

Hmmm....maybe there is a thread in a Vibrant forum. I'll go see if I can find that. Haven't even looked in Vibrant forum yet.
[Captivate Android Development] Zilch25:
We aren't necessarily going to get the same software package the Vibrant is getting... AT&T decides what stuff comes pre-packaged with the Captivate, so if they so no- we don't get it.
[Captivate Android Development] ewingr:
Sure, understood. But if the GPS is fixed on the Vibrant, then that gives me confidence it will on the Captivate.

And, I did find a thread here on the TMobile site. I haven't read it all but have encountered an early post that indicates the GPS is completely fixed. Of course, if I had a dollar for every time I've read that, I could pay for a new Captivate. :p
[Captivate Android Development] Zilch25:
I was following the Vibrant thread a little bit yesterday and there were just as many people complaining about the GPS as we do in this thread. Seems like the results as usual are completely subjective :(
[Captivate Android Development] ewingr:
Bummer. I haven't gone to the Vibrant thread other than the Official T-Mob site one yet. Just finished tht thread, and there were 3 or 4 that reported good results, but to truly receive positive its fixed feedback, it probably needs a couple weeks of constant GPS on to see. (It took me that long before mine had finally shown the problems).

[SIGH]... ... ... [/SIGH]
[Captivate Android Development] Zilch25:
Well there's the thread going on here where someone is going to try flashing it... though I seem to recall GPS doesn't work AT ALL on Vibrant firmwares on the Captivate... guess we'll find out soon ;)
[Captivate Android Development] ewingr:
I just went through the Vibrant thread on the update, and searched for GPS, and read every post that referenced GPS.

Overwhelmingly, they reported it 'fixed' it or was very good. A small minority indicated it did not help.

The proof will come out over time. It took me 2 weeks of constant GPS use to even find mine screwing up. But once it started, it was pretty poor.
[Captivate Android Development] Zilch25:
Yeah I started reading it early after it popped out, so consensus may have changed, though it would be nice if samfirmware leaked out a build for us that's as new and shiny as the Vibrant
[Captivate Android Development] Kaik541:
and then once that happens, the i9000 will get a final froyo and then you'll have something else to fawn over impatiently =P
[Captivate Android Development] Zilch25:
At this point I'm not screwing with I9K froyo until it's a final build. The builds I've played with are garbage. I really just want a nice, solid Captivate firmware where everything works... so that I can start breaking things >=)
[Captivate Android Development] WheresWaldo:
I flashed this ROM today and have not had a chance to test everything, but I did not perform all the steps listed and everything appears to be working. First let me say that I have never repartitioned my phone, I flashed JH3 and now JH7 without incident. So this time I started off with JH3 already on the phone.

Steps:

TiBU all user apps and system data

removed any update.zip from /sdcard/

started Odin3

Initiated Download Mode

Loaded JH7 in PDA mading sure repartition was not checked

Flashed

After second reboot I was up and running with all my settings and home screen preserved. Phone reports I897UCJH7. The only thing different is that all the AT&T apps are back. There was no need to restore my backup. There was no need to flash back to JF6.

I just wanted to pass on my experience. Now I will need to download SRE 1.3x to restore root access as well as all the other wonderful things it does!
[Captivate Android Development] oldskooldawgz:
After a second reboot of my captivate im getting a lot better gps performance even good at following the bus
[Captivate Android Development] DJNgoma:
It seems the radio has improved, I've got some really poor signal in my residential area and it seems to be on full bars from the previous and recurring no bars. Sticking to JH7 for as long as possible, a bit scare of loading the latest SRE now with the current bug issues I'm seeing in it's thread.
[Captivate Android Development] itpromike:
So if I do the JF6 1 Click and/or repartition this means I'll lose everything that's on my internal SD right? Repartitioning deletes all data no?
[Captivate Android Development] Zilch25:
It only deletes the stuff on your NAND- not the stuff in /sdcard
[Captivate Android Development] JayPhill89:
It shouldn't touch your SD card files, but as a best practice, you should just take your SD card and SIM card out until the process is finished.
[Captivate Android Development] oldskooldawgz:
hes talking about the 16 gigs built in and that stuff should stay good unless some glitch happens
[Captivate Android Development] supertrac:
Flashed JH7 then flashed Fightspit's battery mod without a problem but my gps is still the same, took forever to lock the sats even outside and the option to rearrange the icon on TW is gone. Am i missing something?
[Captivate Android Development] dirtblade:
Do i need to use any .pit file when reflashing JH7?
[Captivate Android Development] fox945:
Has any one figured out how to access the GPS menu now since the *#*#1472365#*#* isn't working with JH7?
[Captivate Android Development] neptronix:
GPS and other thoughts and experience.

Hi everyone. Just wanted to confirm my results of this ROM. GPS so far has been very accurate and fast locks as well. Tested with Google Tracks. Like others, initial boot showed very responsive and quicker than previous JF6 or JH3. Very pleased. I have had no problem installing Lag Fix or SRE. Quadrant scores after lag fixes and misc. are in the 2200-2500 range consistently.

Awesome! Battery life been good as well, compared to previous ROM's.

I would like to note however, initially I came from JH3, and had many force closes after flash. After flashing fresh Odin OneClick to JF6, then imediately flashing JH7, no problems!
[Captivate Android Development] KCutrer1:
I'm in complete agreement on this one. I didn't even get to see if they were garbage or not, because if you botch the install of one of those it can thoroughly SCREW UP your device!
[Captivate Android Development] WalMarx:
I flashed this rom, and now my phone goes into recovery mode and can't move past that. It says:

update media, please wait...

E:Can't mount /dev/block/stl10 (Invalid argument)

E:copy_dbdata_media:Can't mount DBDATA: copy default media content failed.

The phone won't go into download mode, so ODIN isn't working either.

Any ideas? Or am I screwed?

Edit: When I try to go into download mode via command prompt, it says:

error: protocol fault <no status>

Also, it refuses to go into download mode via keypresses.
[Captivate Android Development] techniq35:
If you're running Launcher Pro, you can...

Long press -> Shortcuts -> Activities, scroll down and click on LbsTestMode, then click on the first item "com.sec.android.app.lbstestmode.LbsTestMode"
[Captivate Android Development] foxbat121:
It you read this thread carefully, you should know that you MUST flash to stock JF6 first (using OneClick flash) before flash to JH7. Otherwise, that's what you will get.
[Captivate Android Development] WalMarx:
I did read this thread. Very carefully. And I flashed to stock JF6 first using ODIN. Don't automatically assume I'm an idiot. I did everything as it was supposed to be done.
[Captivate Android Development] KaLiBLeeK:
If you didn't use the one-click ODIN sticky'd in this forum, there are some repartition issues that were mentioned earlier in the thread.
[Captivate Android Development] fox945:
Thank you! Never thought about that.
[Captivate Android Development] shoeboxin:
Perhaps it is because I flashed straight from JF6 (which I had been using all along) but JH7 seems just as slow when it comes to boot, installing apps or even navigating through them. Anyone else experience this, or do you think it is because I didn't freshly flash JF6 before flashing JH7?

Aside from that disappointing me a little, the flash itself worked straight from JF6 with re-part unchecked and no pit.

Lost root too.
[Captivate Android Development] Kaik541:
to me, it feels just a little bit faster, but it's still an August build, I don't think we're going to see (m)any improvements until we get a September release like our buddies over on the vibrant have. did you flash from a CLEAN JF6 or a "I've been running it like this for a week" JF6? because it makes a world of difference.

and of course you lost root, you changed the system software of your phone =P
[Captivate Android Development] WheresWaldo:
This is not the only way to do this so making this statement as an absolute is inaccurate, at the very least.
[Captivate Android Development] shoeboxin:
More like I've been running it for -since I got the phone- hahaha. I'm going to go ahead and just run one click odin back to a fresh JF6 and then try again.

(I kind of figured I would lose the root, but wasn't 100% certain since I've never changed roms before. Now I know!)
[Captivate Android Development] foxbat121:
So, tell us what did you do to flash back to JF6. Did you use One Click ODIN or normal odin? OneClick odin is the only way confirmed work. You can also re-partition with pit file using normal odin but not sure if that actually works.

And what did you do to flash to JH7 afterwards? Did you re-partition or not? You're not suppose to re-parition when you flash to JH7.
[Captivate Android Development] Kaik541:
yeah, always a good idea to go as "stock" as you can before flashing a new ROM. some of them don't need it, but it's always the safest bet. fortunately, all the eclair root methods seem to be "permanent" as of right now, there's been no need for a new root method for any of the 2.1 releases.

this will change when 2.2 comes out as apparent by the processes required for root with the i9000 leaked ROMs, though they've already got a method for that, so it seems like it shouldn't be THAT difficult
[Captivate Android Development] WheresWaldo:
I am not sure you won't end up in exactly the same spot after a week of use. If F6 was fast at first then slowed then H7 will likely behave the same way. Once all the apps you use daily are installed and all your widgets are in place you will likely not see any significant increase in performance until Froyo.
[Captivate Android Development] shoeboxin:
Has Samsung not done anything to address the lag problems in this rom? I was under the impression they had for the Epic, see this thread, and would include such a fix for future Captivate roms. Halfway thought because people were reporting faster performance after flashing to JH7 perhaps Samsung had addressed it...
[Captivate Android Development] rsx19:
whats the password for this thing
[Captivate Android Development] WheresWaldo:
I do not have actual proof, but what I can tell you is that all the claims of faster performance and other fixes (such as GPS) have simply been wishful thinking on the part of most and reported only a few hours after flashing (sometimes minutes). I have found that after a week or so, if you are using this ROM as stock as Samsung/AT&T intended, all the lags and slowness are back. I have looked over these ROMs carefully and do not flash my phone every day, much less multiple times per day. I am not using any lag fixes or GPS tweaks. I install all the regular apps I use and after a weeks time it performs about the same as it did when I first pulled it out of the package. Obviously some things are better, such as GPS performance but it still lags and does not run as smoothly as the hardware would dictate it should.

I am not telling you you shouldn't reflash, but just not to expect any miracles after you do. I really think that with everyday use you will likely be at the same spot you are right now.

Saying that, I did flash JH3 then JH7 but will likely not flash anything else until a real Froyo build comes from Samsung. I only have one app that FCs regularly (SL4A) and will get an occasional non-responsive app that I have to wait for. I did not expect JH7 to fix those issues and they haven't, I don't expect real performance gains until we have a stable 2.2 OS.

As far as Epic/Vibrant/Facinate/etc. most of their posts are about as scientific as ours. Flash then test then proclaim everything is fixed. Before anyone puts any significant time into actually using their phones, the process repeats over again.
[Captivate Android Development] The Bishop:
its in the thread a few times, you must lurk moar.
[Captivate Android Development] rsx19:
how do you flash this? sorry im noob :[
[Captivate Android Development] The Bishop:
hit the "Search This Thread" button at the top right, and type in "what is password" and you'll see all of the posts with people asking or answering that question in this thread - and the replies to what the password is. :)

Teach a man to fish ... ;)
[Captivate Android Development] shoeboxin:
its in the thread a few times, you must lurk moar. (see what I did there? hah)
[Captivate Android Development] Kaik541:
well to be fair, it's kind of apples to oranges with the Epic. it uses the touchwiz 2.5 interface, we have touchwiz 3.0. it's the "pro" variant with a keyboard. it has a 2 GB NAND, while we have a 16 GB moviNAND (essentially a specialized class 6 card). the software on that device is about as incompatible with the others as it could be (I think the Fascinate would be much closer).

so any lag "improvements" they see are because they're essentially running a different phone, while the Captivate/Vibrant/i9000 are more-or-less minor rebrandings.
[Captivate Android Development] The Bishop:
+1 Internets.
[Captivate Android Development] rsx19:
what are the settings of odin?
[Captivate Android Development] Kaik541:
PDA

PHONE

and CSC

seriously, read a sticky
[Captivate Android Development] rsx19:
wheres the sticky,
[Captivate Android Development] WalMarx:
I used One Click ODIN. I did not repartition when flashing to JH7.
[Captivate Android Development] foxbat121:
You can try to use normal odin with re-partition checked. You must have installed some custom kernels or other stuff that messed up the original partitioning
[Captivate Android Development] WalMarx:
I would do this, but I cannot access download mode by any means.
[Captivate Android Development] rsx19:
uhm...
[Captivate Android Development] jdsemler:
Just adding another GPS testimonial for this firmware...

I just did a 30 mile drive with the new firmware, and it was downright shameful. I had Google maps open, and the arrow never pointed in the direction I was going and was constantly bouncing around with a huge blue circle that took up more than the screen. It would sometimes show the arrow on the road I was on, but it didn't follow my movement, then it would jump a few blocks away and just hang out there for a while.

I guess it is good enough to let my weather app know what city I'm in, but it still is not good enough for any kind of navigation.
[Captivate Android Development] Kaik541:
bahahahaha

you don't think it's a bit silly that you put the same file in three different spots? reading through any of the stickies about flashing even the i9000 ROM explains how to do this.

PDA is for kernel/main file

PHONE is for modem (if it's separate)

CSC is for CSC (if it's available)
[Captivate Android Development] rsx19:
i think its funny how nobody tells you how to do it
[Captivate Android Development] Pirateghost:
read the stickies.....especially the i9000. the process is the same
[Captivate Android Development] ThisWasATriumph:
I'm sorry but I LOLed too...
[Captivate Android Development] Kaik541:
well if you actually READ through the forums and stickies and pages like you SHOULD before you're flashing a ROM onto your device, you wouldn't be having this issue.

we all figured it out at some point, and clearly it was from reading these forums. take the time, read through ALL of one of the stickies related to flashing (seriously, you learn SO much even if it takes time)
[Captivate Android Development] rsx19:
somebody tell me what its supposed to look like now im getting this error after reboot it goes into recovery

e: cant mount /dev/block/st110

(invalid augment)

e:copy_dbdata_media:cant mount DBDATA:

copy default media content failed.
[Captivate Android Development] Zilch25:
The reason for that is that you didnt read.

You're supposed to flash to JF6, then do JH7 WITHOUT repartition
[Captivate Android Development] Kaik541:
lol

so you didn't even read through THIS thread? it's been stated at least 10 times that you MUST flash stock JF6 with either the one-click tool or repartition selected.

if you're not going to take the time to read through the thread, it maybe be a bit ill-advised to flash a ROM. here's to hoping yours isn't one of the captivates that doesn't respond to the three button mode or else you're SOL

edit: actually I think adb still responds in this state, since it does when flashing an i9000 ROM without a functioning kernel
[Captivate Android Development] Kaik541:
http://www.multiupload.com/7WKESZFN7B
[Captivate Android Development] designgears:
this looks like froyo, I have ripped apart the factoryfs.rfs... just not getting past the boot logo

edit...

lame, they emailed it to me and said 2.2 :(
[Captivate Android Development] tysj:
JH7 is on samfirmwares now but it's listed as a 2.1 ROM.
[Captivate Android Development] gunnyman:
Here's an idea. Rip the kernel out and use the sgs froyo?
[Captivate Android Development] ThisWasATriumph:
Why is it named JF7 and not JH7? Which is it?
[Captivate Android Development] designgears:
Sorry guys, looks like we jumped the gun AGAIN...

2.1 rom, AGAIN....

grrrrrr
[Captivate Android Development] frenchtoasted:
So, it's a non-working 2.1 rom?
[Captivate Android Development] tysj:
Today we have 2 new firmwares.

ANDROID 2.1

- One for the Samsung Captivate.

- One for the Samsung Vibrant.

We test the Vibrant firmware.

Whats new:

- HD Camrecorder App.

- Task manager App.

- Gps Seems faster.

- New widgets.

- And fix a lot of lag things.

This 2.1 rom looks like a real android 2.2.

We are very happy with this new Samsung Vibrant rom.

Both roms will be soon available over Kies or New Pc Studio.
[Captivate Android Development] Kaik541:
yeah I think we're caught up on the fact that it's 2.1, but is it booting?
[Captivate Android Development] phr00t:
Downloading.. I have a birthday party to go to in a few minutes though :( I'll be checking back here to see if this is the real deal or not! :D
[Captivate Android Development] KaLiBLeeK:
Drats!

Although I'm not sure how they determined a 2.1 firmware "looks like a real Android 2.2"...if it's actually 2.1. Haha.
[Captivate Android Development] darkamikaze:
lol so confused.. so this is eclair right!?
[Captivate Android Development] Clienterror:
Yea it's eclair apparently, does it actually boot?
[Captivate Android Development] born_fisherman:
I'm downloading now - would like to know if it is running from someone else before I flash as I've been liking the i9000 MJF6 rom now :)
[Captivate Android Development] cropythy:
I'd like to know as well, but I'm willing to try if no one reports once it gets downloaded in 20 minutes
[Captivate Android Development] born_fisherman:
I have 5 minutes left :) I'm skeptical though since I haven't backed anything up yet and still have to flash back to stock first.. I don't think I can get myself to be the guinea pig
[Captivate Android Development] beazie0885:
Hey DG, I used odin and flashed back to stock jh3 then jh7 and I'm stuck at black screen too. Is it possible that the vibrant one and this one got mixed up?
[Captivate Android Development] designgears:
make sure REPATITION is selected and it will work right
[Captivate Android Development] beazie0885:
Got ya.
[Captivate Android Development] ThisWasATriumph:
Ah sweet! Initial thoughts?
[Captivate Android Development] rsx19:
i did flash JF6 first
[Captivate Android Development] Kaik541:
and did you click "re-partition" like it's been stated at least a billion times? and then to NOT select it when you do JH7?

because that's the exact issue that comes up when you don't follow that exact procedure

edit: if I'm coming off condescending, sorry, but it's hard not to right now. this is just so silly. seriously, you could have figured it out JUST by making it to about page 6 or 7 of this thread
[Captivate Android Development] foxbat121:
This always worked for me:

1. Power off, take out battery, SIM card and SD card.

2. Put battery in but don't touch power button.

3. Start ODIN

4. Hold vol up and down buttons while plug in USB cable. it will auto power on and go directly to download mode.
[Captivate Android Development] WalMarx:
I tried that just now. Goes right back to recovery. Tried through adb. Says "error: protocol fault <no status>."

I flashed to stock using one click odin, then flashed to jh7 (no repartition).
[Captivate Android Development] Kaik541:
are you sure you AREN'T hitting the power button when you do this? and that you're holding down BOTH volume buttons?

edit: also, were you sure that your phone responded to the 3 button controls BEFORE you flashed a new ROM?
[Captivate Android Development] rsx19:
i just did the exact something i was doing before except for the 3 files

and now its working fine, boots fine.
[Captivate Android Development] foxbat121:
Make sure you don't ever hit power button and keep both vol buttons firmly pressed until you see the download screen.
[Captivate Android Development] Kaik541:
well that's funny, because in your screenshot, you have "repartition" checked for JH7.... leading me to believe you repartitioned both times, which is where your problem came from
[Captivate Android Development] rsx19:
oh trust me i went through many trial and errors
[Captivate Android Development] neptronix:
Hi, not sure if I missed something or read the post wrong, and my apologies if I did, but you mention running this ROM after a week or so and the slowness coming back, but this JH7 just came out over this past weekend. How have you been running it for a week?
[Captivate Android Development] neptronix:
Question: At how far into the drive did you find the GPS doing this? Ive not had such problems as many seem to report, but def found the JH7 to be far better, after reviewing the recorded tracks, always showing me on road just as expected and quite accurate while driving. Google NAV was not a problem either. However, only tested most times on a few mile trip, not further.
[Captivate Android Development] dp1mat:
MMS

I was at work today only had edge I could send all kinds MMS with it fast. Before it wouldnt work unless you shrunk it down really small and it still took a while.