yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] junkyhlm:
Same problem

Hi guys, i've got the same problem and i've tried everything it feels like. It just wont go past factoryfs. Anyone that can helt me?
[Captivate Q&A, Help & Troubleshooting] l7777:
Stock cable sometimes helps too, I noticed that ADB will not stay connected with one of my cables but will work just fine with the stock cable. Crazy, but others have noticed it too.

Also, this is the wrong section.
[Captivate Q&A, Help & Troubleshooting] tehXKnight:
Hate to bring up an old thread, but I could not find this until I typed a title for a new post. :confused: Even google couldn't find it. Just saying this fixed mine and I passed some thanks around for you guys!

Oh, and that my phone won't even try to connect unless I use the stock cable and one specific USB port on the front of my compy.
[Captivate Q&A, Help & Troubleshooting] samson_420:
I am having this exact issue now. . . . I tried everything mentioned on here.

Swapped ports

Swapped cables (one is OEM)

Ran as Admin(Windows 7)

Ran compatibility to Windows XP SP2

Still nothing

Stuck at 2/3rds of the way when updating the factory image.
[Captivate Q&A, Help & Troubleshooting] n80k:
i'm having the same exact problem. i've tried flashing both the DI18 and DI07 from this page and it gets stuck 2/3 of the way thru factoryfs.rfs... what is strange is that i can flash to DK28 without a problem. i'm using odin3 v1.61.

my phone was stock until today when i flashed into the DK28 then converted to ext4. then i flashed the Frankenstein ext4 rom with clockwork. everything worked fine but i didn't realize i couldn't restore all my data from my original rom so now i'm trying to go back to those recover apps and settings from my original rom. could anything i have done today had anything to do with this problem? i've tried all of the above troubleshooting steps as well. i'm using windows but i'm considering trying heimdall on ubuntu if this problem keeps up

EDIT: i'm trying heimdall but the first step is to extract the .tar rom... the DK28 extracted fine but there were errors with my DI18 and DI07. looks like my problem might be a bad rom

FINAL EDIT: yep, sorry. i re-downloaded the eclair rom and it flashed fine. on the bright side, this forced me to use heimdall and i think i'll be using that from now on so i dont have to boot into windows all the time
[Captivate Q&A, Help & Troubleshooting] knife-edge:
Same problem

I had midnightROM 2.9.2 EXT4 installed.

Tried to odin flash back to stock Froyo and it stuck on factoryfs.rfs. Also, screen turns completely one color. Now it's purple.

Is this because the phone was formatted to EXT4 and now odin is trying to write in rfs format?

If so, how do I reformat phone to rfs? Of course the phone doesn't work or boot up so it has to be done through odin or Heindall.

Any other choices? I have Linux to use if needed.

I tried DI07 & DI18. Same results.

Thanks!

Knife

UPDATE-RESOLVED: 12 hours later.... After blue, yellow, purple burgundy and green screens. It finally worked. I monkeyed around with it, but not sure what the problem or solution was. Some things I did:

1. I downloaded another stock D28 and used Firefox's "Downloadthemall" extension, which ensured a checksum match.

2. In odin 1.61, I flashed a pit (non-victoria) only with "partition" box and reboot checked. It did something and completed.

3. Then, I used the one USB port that I hadn't tried - the one my wireless USB ant was inserted.

4. Did the victoria pit with "partition" and reboot checked and it worked!

5. This was after several fresh re-installations of 64-bit drivers in Vista 64-bit Home Edition.

Not sure what did the trick, but I suspect it had something to do with partitioning. I assume because I had previously converted to EXT4, there was trouble with just flashing rfs to it. Perhaps the first (or second) partition reformatted that area of the permanent phone drve.

Immediately, I put no-journal, 2.9.3, 3.1 theme-blue-ASOP and viper apocalypse theme on SD (titanium sdk & last back-up, and Launch-pro back-up already on SD). I followed instructions and CW3'd the phone. After EXT4 convert self-ran, I Did not reboot and flashed no-journal. Then, Did not reboot and flashed 2.9.3.. Re-boot. Turn off and turn on. Turn off and 3-finger to CW3. Flashed Midnight 3.1 them. Reboot. Turn off and turn on. Turn off and 3-finger to CW3. Flash Viper apocalypse theme. Re-installed apps one by one from titanium. Entered Launch-pro code. Restored Launch-Pro back-up.

Update: The rom pooped on me today while moving moveable apps to SD. It tried to shut down (9% bat remaining) and looped in the android boot immage. Nice green cloud circles, btw. Got it to main screen and everything FC's, including Launch Pro. It works a little bit in Launcher, but everything is force closing over and over again. I am going to wipe 3x and reinstall 2.9.3. Geeze, I came from 2.9.2 and life was good. I think 2.9.3 might be a booger until our beloved creater picks at it...some more. I'm looking forward to 3.0 ;-)

3 minutes later.....Wow, just went to midnight thread and I see 3.0 has arrived. Hurray, the booger is gone.
[Captivate Q&A, Help & Troubleshooting] CorranHorn666:
Was having this issue. Could not for the life of me get past the factory part, but luckly I used my school netbook and it worked.
[Captivate Q&A, Help & Troubleshooting] edunewz:
Run as admin

run as admin worked for me
[Captivate Q&A, Help & Troubleshooting] KnightNavro:
I had a problem where Odin got stuck at the factoryfs.rfs stage using Windows 7. Running as admin didn't work. I swapped USB ports, set it to run in XP service pack 3 compatability mode, and ran as admin. That worked.
[Captivate Q&A, Help & Troubleshooting] 41LY45:
Sorry to bump an old thread but it appears i have the same problem

Flashing back from MIUI 1.6.10

Stuck at factory.rfs before turning pink/blue/grey/black/Burgundy

Did ran it under admin and compatibly mode. same thing happened. :(
[Captivate Q&A, Help & Troubleshooting] AguxOne:
Hi, i've got the same problem with a i5800, problems with odin seems to depend of the computer of the user.

However instead of switching pcs, i used an app called "Sandboxie", don't know what is does exactly, but it helped me with other rebel apps too.

Just open sandieboxie and drag the odin .exe to the sandboxie window, choose Default box and click ok.

I fixed the problem with that, maybe i only was lucky, but you loose nothing trying, good luck!
[Captivate Q&A, Help & Troubleshooting] newter55:
Dont be sorry. You deserve a cookie for not opening a new thread.
[Captivate Q&A, Help & Troubleshooting] maximus-dev:
Had this problem today... Rebooted, did Run As and ran as the admin account and used a different USB port and it worked... you have no idea how happy I was.
[Captivate Q&A, Help & Troubleshooting] thatoneblondekid:
Need help with this issue as well, USCC Samsung Mesmerize. Trying to flash a pre-rooted 2.3.4 with Odin, I'm running as admin and in compatibility mode with XP Service Pack 3, plus I'm running it in Sandboxie as a previous user suggested. This is my first Android phone, and my first attempt at flashing ROMS or rooting it, so it could very well be user error. The package I downloaded was just one folder with two files in it, "atlas_v2.2.2.pit" and "USCC_EH09_root.tar.md5". I've got the .pit selected for the PIT option, and the .tar.md5 selected for PDA, PHONE, and CSC. Any advice? If it helps, I'm stuck on the second time of it saying factoryfs.rfs.

<ID:0/008> File analysis..

<ID:0/008> SetupConnection..

<ID:0/008> Initialzation..

<ID:0/008> Set PIT file..

<ID:0/008> DO NOT TURN OFF TARGET!!

<ID:0/008> Get PIT for mapping..

<ID:0/008> Firmware update start..

<ID:0/008> factoryfs.rfs

<ID:0/008> zImage

<ID:0/008> modem.bin

<ID:0/008> factoryfs.rfs <- That's where I'm stuck.
[Captivate Q&A, Help & Troubleshooting] b-eock:
Why are you in the Captivate forums
[Captivate Q&A, Help & Troubleshooting] mduma77:
try changing computers.

and by the way try to use a computer with a password for the admin account
[Captivate Q&A, Help & Troubleshooting] Failedsquare:
Thanks

Much thanks for the thread. I was flashing and the phone fell off the table came unplugged and the battery fell out. I thought for sure i screwed it up. Using odin in windows 7 i just swapped usb ports and ran as admin and it started working again. 2:12 to reflash fc09 release.
[Motorola Droid and Milestone General] GUARDIANBD:
hello there

1) is there any solution for the bad call quality?

2) what is TTY?

3) i have the GSM version of the Motorola Droid (Shoeles\Milestone) i'v enterd the

Secret menu code and it request from me the SPC code

i'v try'd 000000 (6 zero's) and its wrong password

did some1 can tell me the real code? i have an problem with Call quality...

thank u sooo much
[Motorola Droid and Milestone General] xslntx:
Only some people seem to be experiencing it. A fairly popular solution is to stick a piece of paper in the small hole at the top, rear of the device. I haven't tested it personally.

Some kind of deaf thing.

The password for this menu on the Milestone hasn't been found yet, as far as I know. Even if it was, I don't believe the same tweak for call quality found on the Droid would be applicable on the Milestone. As far as I know, it's specific to the Verizon network.

All that said, this is the wrong section.
[Motorola Droid and Milestone General] GUARDIANBD:
sry...

thank for the info :P

by the way,your thinking maybe my service provider (Cellcom) have this code?

some pp'l told me that the SPC code is just Residue of the Droid'd software

is it true? they are diffrent beyond GSM\CDMA?

regards :P
[Motorola Droid and Milestone General] xslntx:
I believe only Motorola has this code. The differences between the Milestone and Droid certainly go beyond the radios they use (GSM/CDMA)

The Milestone is locked down, Motorola doesn't want anybody to modify it. The Droid was released as a Google phone, which means it's allowed to be modified any way the user wishes. The Programming menu (what you want the password for) is one of the tools that let you change some otherwise-hidden settings that Motorola doesn't want you to change.
[Desire Q&A, Help & Troubleshooting] Gavincol78:
this month I am due an upgrade to phone contract with Orange UK and I am mixed between 3 phones and I was wondering what other think this is my list in preferance order:

1, HTC Desire either in brown or black

2, Samsung Galaxy S

3, Sony Ericsson Xperia X10 (the large one)

I have them in that preferance because I am a bit of new fan of HTC being a fairly new user (1-2 months) so I put that first preferance, the Samsung I put that as second as that seems more popular then the SE and the SE as third as I used to like the walkman features of SE in the past and the possible fact of the 8MP camera (which isn't really a feature I would use everyday).

Also my preferance to HTC is because of the fact that changing the firmware is more possible and also better customiseable.

I would go for a Desire HD but it isn't available on Orange UK yet
[HD2 Android Q&A, Help & Troubleshooting and Genera] jaedolla:
Just wondering if anybody can explain to me whats the difference between hastarin r7.1 kernel and michyprima's r11 kernel without flaming me. Obviously i know hastarins kernel is evo based and michys is not. that doesnt really explain much to me because i could run both kernels on evo based roms and on desire hd roms. i know with michyprimas kernel the cam works with flash perfectly and hastarins kernel cam doesnt work properly with premature flash. maybe some one can point out the pros and cons of both kernels. i dont want to get into a debate about which one is better or worst. just want to know the differences and pros and cons if possible so i can make a decision on which kernel is best for me. please dont flame for my noob question.
[HD2 Android Q&A, Help & Troubleshooting and Genera] justwonder:
Since both could run on your build why didn't you test them, and make decision for yourself? then tell us pros and cons for each.

My personal experience, maybe different from other

Evo base kernel:

PPP data connection, faster speed compare to rmnet, but to some network , it's not reliable. like my T-Mobile, I got disconnect all the time.

My bluetooth headset works

LED status notification, LED hardkeys, most off the time didn't work

They said light sensor works, but it wouldn't work on mine

They said G sensor work, no more freeze, I didn't test long enough to see if it really works

Nexus base kernel:

RMNET data connection, slower speed, but reliable.

My bluetooth headset didn't work

LED notification, hardkey works

G, light sensor didn't work
[HD2 Android Q&A, Help & Troubleshooting and Genera] polo735:
Michyprima now also has an evo based kernel. It is version r1 currently.
[HD2 Android Q&A, Help & Troubleshooting and Genera] jaedolla:
I did test both kernels and as I stated in my original post was the only differences I found was cam works on nexus kernel and it doesn't on Evo. I didn't notice any other differences that's why I asked the question.
[Galaxy S I9000 General] Prankey:
Bump.. Appreciate your help.
[Galaxy S I9000 General] Prankey:
Seems noone's using this feature which is VERY important to me. Can anyone help or should I contact Samsung to get this BUG fixed which exists on every firmware I have tried till date.
[Galaxy S I9000 General] Jumba:
No tethering problems here. Maybe your device is just faulty?
[Galaxy S I9000 General] kstepyra:
Hi,

i've searched all the internet for resolution for that and nothing.

Weird thing is that connection was working good on 2.1 and also on 2.2 and then stopped working just like that (1-10 minutes of connection and then dc for like 5-30 seconds)

Tried almost all apps on market which didn't help me. Now i am trying PDAnet which is working well for about 40 minutes now. I had some troubles installing it but finally did it with USB drivers delivered with PC program of PDAnet. Wifi 5mb/s download speed and just slight ping increase but i am far away from AP so that's the problem i think.

However if someone know if it's system problem (running win7 prof. sp1) or any 3rd party software it will be nice to get working again on standard tethering provided on i9000 as it doesnt require any 3rd party software on PC to get it working.

If dc's again come i'll post info.
[Galaxy S I9000 General] ttf:
I'm assuming that all your PC drivers are uptodate? According to me, it's a PC issue more than a phone one (check your PC logs & Firewall logs)
[Galaxy S I9000 General] kstepyra:
I have turned everything off (firewall, antiviruses etc.) and no changes. PDAnet is working well and as i saw it's .800 version of the usb driver, but new KIES installs .2000 one. Had problems with .2000 as PDAnet says i don't have usb drivers installed ;) Uninstalled KIES one and installed .800, then PDAnet installed well. However - this program was only one solution to work. I have to try normal tethering on XP and clean win7 on laptop soon as i get it on hands.
[Galaxy S I9000 General] fatjoez:
Bump for a still existant issue

Getting constant cutouts with USB tethering on Samung Galaxy S i9000T running Froyo 2.2.1 Darkys Rom 9.5

Wondering if maybe getting a Dock will fix it?
[Galaxy S I9000 General] aczelkri:
Problem here too.

I am having the very same problem too. USB tethering works fine (faster than Wireless tethering) in the first few minutes, then drops the connection, and usually I have to restart my phone.

The reason I would use USB is that for online gaming Wireless tethering is too laggy in some cases. I would really appreciate a solution here.

I am using JPU modem on Froyo 2.2.1 btw.
[Galaxy S I9000 General] zat81:
Nothing has been solved about this sissue?
[Galaxy S I9000 General] Prankey:
My Phone warranty is going to expire in about a month now. I am not going to keep this phone unless Samsung resolves this issue! Seems most of us are unaware of this issue and suggest they don't have the problem

I have been using smartphones since the first one, and never faced such issue. Using USB tether reduces latency significantly and also do not need to use Wifi on both phone and my laptop.

Some of us feel its a PC issue. How come connecting it to 4 of my PCs at home have exactly the same issue? They also have different OS and Firewall/AV.

On top of that, all the GB based ROMs have strange battery discharging issue after full charge and is killing my battery unnecessarily:

http://xdaforums.com/showthread.php?t=1134741

I have escalated these issues to Samsung yesterday. They are affecting me most as these are the primary use of this phone.
[Galaxy S I9000 General] Lunchbox115:
I don't have this problems, just give CM7 a try. ;)
[Galaxy S I9000 General] Brotuck:
Try any 2.3.4 Custom ROM, it works just fine.

Worked with it yesterday all day.

It still gets hot when using the 3G/Wifi connection, but with usb tether it rocks !
[Galaxy S I9000 General] Prankey:
I haven't tested 2.3.4 images for USB tethering much, however what troubles me most is ANY GB ROM start draining battery after full charge which is currently bothering me most as its killing my battery and phone unnecessarily while randomly making my phone go dead anytime even when USB/charger connected all the time (after going dead, restarts in battery charging mode as USB connection gets refreshed)
[Galaxy S I9000 General] Brotuck:
On my (and i guess others) Rom i get a least 24 / 48 hours. But it really depends on what you do with it during the day. I have not experienced any batterydrain on my custom rom. Ever.....

send from another galaxy !
[Galaxy S I9000 General] Prankey:
I ALSO get the same usage time AFTER DISCONNECTING the charger and using the phone normally.

However, my phone is used primarily for WIFI Tether of 3G connection and hence has to be plugged through the day most of the time when doing tethering. After full charge, my battery drains heavily as the charger is disconnected on GB (instead of disconnecting the battery after full charge) and hence killing the life of my battery through such abuse.
[Galaxy S I9000 General] fatjoez:
still experiencing this

just an unstable connection

works then every 5/10 minutes it'll stop working and pages will take a while to load then it just starts working again

it's like bursts of connectivity

currently on 2.3.3

can anyone confirm 2.3.4 fixes it after being on 2.3.3?
[Galaxy S I9000 General] jodroidbcn:
I'm using a JVR ROM (2.3.4) and have the same problems with USB tethering.

It's rather annoying; i've searched around and it seems to be widespread, I'm not sure if it happens to everybody though.

This is what I've noticed:

- The USB tethering stops working usually at the same time that my Win 7 laptop says that the device could be using USB 2.0 instead for faster speed. At that point, the phone disables USB tethering

- Re-enabling USB tethering on the phone settings makes it work for a minute or so, until the same thing happens

- It does not matter if the phone is on USB debug on/off (i've tried both), or whether it is set to use Kies, Mass storage, or media player under the USB connection menu

I'm trying to find a different USB driver, just to try if it solves anything. But have not been able to find a proper one.

It would help if someone on a 2.3.4 Rom could confirm that USB tethering works for them. At least we could then know whether it is solvable (via configuration, settings, etc.) or not at all until Samsung releases a fix.
[Galaxy S I9000 General] Iggys Pop:
I'm having this issue with the Samsung Captivate I897 running Froyo 2.2 through At&T, rooted. I realize that its not the same device this thread's meant for but possibly a related issue? I've been trying to find a solution to this for a few months now... I randomly get disconnected from the internet while using the USB Tethering. I'm forced to re-connect through the phone every 20 minutes or so... I've tried using alternate applications to tether and to use the Mobile AP... With all the apps I run into the same unstable connection as well as with the Mobile AP. This is rather frustating and the last time I spoke with Samsung, I was informed that they no longer "support" usb tethering. I'm at a loss as to what to do, if anyone has any insight this would be greatly appreciated...hopeully even though this is a different device, there's a relation somehow??
[Galaxy S I9000 General] techguy615:
Same issue here

I am on DLev's 4.2 Rom. KG3 Modem. I9000 Reoriented Kernel vG_2.1

I just flashed to this ROM and modem version after experiencing the same issues with Darky's XXJVR R3.2.(All stock as provided by the Dev.)

It seems intermittent at this point. I verified that the Mobile AP works great (as of last night). The USB tethering disconnects after a few minutes or seconds and the USB tethering option becomes "unchecked" on the phone itself. Windows 7 Complains about the speed of the USB port and I have swapped to a few different ones, but the same thing happens. Although I am typing this and it has been connected for 20 minutes or so with no issues.

I have also disabled any firewalls or Antivirus to make sure that wasn't the cause. Same issue. I am on Windows 7 x64 (SP1). I am starting to wonder if this a Windows Update that could have caused the issue.

Anyway, just to give more info to the subject.

Ok.. here is something I stumbled across that may have solved this. Appears to be a Windows 7 setting. I have a Captivate but I am running an i9000 Rom, so this might work and might not.

Open Control Panel-->System And Security-->Power Options-->Edit Plan Settings-->"Change Advanced Power Settings". Then navigate to the "USB Settings" and expand "USB selective suspend settings". If the value here is set to "Enabled", click on it and select "Disabled". Click "apply" and then Click "ok".

I pieced this together due to other people having issues with NIC drivers and Windows 7. They were able to get past it with settings on the card drivers under device manager and telling the driver not to do any power management on the card. The drivers for my device has no settings for this, so it is a possible workaround. I am waiting to see what happens. Can someone else give it a try as well?
[Galaxy S I9000 General] kf0916:
try the latest galaxian kernel.
[Galaxy S I9000 General] are-red:
Mine got working stable.. No freeze at all. Using semaphore 1.5v kernel
[Galaxy S I9000 General] kb909:
I use wvdial on linux which uses the phone as a modem via usb Try find something similar for windows
[Galaxy S I9000 General] techguy615:
Solved Mine

Ok, as I said I am on a Captivate with a i9000 ROM/Modem/Kernel (Dlev's 4.2).

The issue for me went away when I went back by one revision on the kernel I was running. I was running the i9000 reoriented vG.2.1 kernel and flashed the vG.2.0

Since then (have been testing most of the day now) and had no more issues with the USB tethering disconnecting randomly on me (Windows 7 x64). Might also be a coincidence due to a bad flash of the kernel the first time around.

Anyway, might be something for other people to look into. I doubt anything else I did fixed it. I know this is the i9000 thread, but I thought it might help. I found this when I was searching for a solution to my problem.

:)
[Galaxy S I9000 General] aczelkri:
I was using Froyo JPU ROM and had the same issue with USB (and also WiFi) tethering dropping the connection from time to time.

What worked for me:

1. Disable Fast dormancy (*#9900#)

2. Install Gingerbread JVK ROM

I suspect changing the ROM was the key, but who knows. Now it works flawlessly. (However, Gingerbread for Galaxy S has its own problems like battery drain while on charger and heavier memory usage... :( )
[Galaxy S I9000 General] mpjoe2000:
maybe this can help:

http://xdaforums.com/android/general/fix-usb-tethering-lags-freezes-windows-t3039183
[Galaxy S I9000 General] :
He had this problem 4 years ago bro, now you troll him lol
[Galaxy S I9000 General] caracolgeek:
Hi