yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] frewys:
Thanks for all the reply guys!

@ickyboo, alovell83 Yes. Installed Kies. Installed separate drivers. No effect. It is not even in device manager list.

@decepticon The problem for me with bootcamp is to my knowledge (like I said new to Mac) they don't allow bootcamp on a partition HDD. Maybe I'm just "PC" and don't really need to make extra partitions to save time in case of need to reinstall (saving all music. images, movies etc on "D" partition). Enlighten me. Come to think of it. I could remove the extra partition install the bootcamp and THEN remake the partition?

(of topic. How much better FPS do u get on bootcamp compared to native mac? I ran it on my 2010 MacBook Pro 17" and have to lover the the settings pretty much to lowest settings to get playable frame rate)

@shawnfr that is interesting!! So I can use the bootcamp partion as a source in virtual machine!? Sounds sweet! Know if it is only possible in parallels? yea looks like there is something going on With the USB thing on the Samsung.. shame..

So After getting rid of all my PCs I had to use my fathers to finally flash the ROM. A LOT easier!! ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] decepticon:
If you already have a spare partition then you can use it. Just run through the Boot Camp setup and it will walk you through it. You can read your Mac partition in Windows but it's read only to protect it from any Windows virus.

I haven't checked FPS because it runs so bad on my 2007 Macbook Pro but in Windows I get a noticeable improvement due to the newest nVidia drivers in Windows. Sadly Apple won't allow hardware providers to release drivers directly for Mac.
[Galaxy S I9000 Q&A, Help & Troubleshooting] frewys:
That is just it. I get this cryptic error that i googled and to my understanding it cannot install on a partitioned disk. Right now I'm copying my entire drive to an external so that I can remove the partition and copy it back after hopefully getting the bootcamp up and running.

No I know about that whole driver fiasco for Mac. They are waaaaay behind windows on the graphdrivers... But thankfully steam seems to put some sense in Jobes.

Coming from Windows I think that the virus thing is exaggerated.. I had ONE virus of negligence during 15 years of PC. But don't trust common sense to all other million PC users ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] decepticon:
I don't know if it's relevant for newer MBPs but I did get a video update that says it solves issues with SC2.

I had some issues with Boot Camp and partition tables at first but I removed them all and did it all through Boot Camp and it worked fine. The virus things is exaggerated but common sense takes a back seat to "see me live on my web cam click here" lol
[Galaxy S I9000 Q&A, Help & Troubleshooting] frewys:
Been working on this annoying thing for a couple of hours.. Bootcamp is NOT very flexible.. But I found a way to "cheat" it.. I had to remove the second partition. Then make "system" partition the entire drive. THEN I make the Bootcamp partition. And after windows is installed I can repartiton the System and make my second "data" partition!! Messy. But hope it works. Installing windows soon.

The SC2 update didn't do anything for me. But I'm happy to see it.. At least that is a start.. I read it had some effect for some older MacBooks...
[Galaxy S I9000 Q&A, Help & Troubleshooting] frewys:
Nope.. No luck at all. Giving up for now on BootCamp. I guess I will stick to PCs for my SGS in the future. I dont really have time for gaming anyway so the issue with lack of partitioning is not really worth it :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] davanw:
I have not yet had any luck getting my SGS to show up in a Windows 7 VM running on VMWare Fusion.

USB virtualization is a tricky animal. A device has to be enumerated twice - first on the host, then on the guest. I imagine the SGS is having a hard time with the low-level second set config request. This seems fairly typical with high-bandwidth USB devices like PDAs.

When I get to work tomorrow I'm going to try it out against VMWare Server and VMWare Workstation. I might even try Hyper-V just for giggles. Workstation has the ability to disable the set config command. So maybe it will have more luck (doesn't help Mac users though!)
[Galaxy S I9000 Q&A, Help & Troubleshooting] frewys:
ok. Interesting. Good luck with that :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] frewys:
I just realized Mac has VirtualBox to! Anyone tried it? Maybe there is a small difference for the better in this case...
[Galaxy S I9000 General] Kasha:
Hello!

I tried to find an exact answer, but with no result.

My SGS has 3 button combination to get to recovery/download modes locked, but I still want to be able to flash new firmware - I9000XWJM7, which is the latest and most stable 2.1 release at the moment.

There's a nice script made by BackfireNL to reboot the working phone to recovery mode, but I don't understand if I will be able to use it when I flash the phone with Odin3.

I understand there's a risk of 'bricking' my phone without a chance of recovery, but I still want to try it. All I want to know is: it it's possible, what is the exact procedure?

Thanks in advance!

EDIT: Sorry, wrong forum, please move to - Galaxy S I9000 Android Development http://xdaforums.com/forumdisplay.php?f=665
[Galaxy S I9000 General] AllGamer:
you can even reboot the phone with the App from Market to "quick reboot"

you don't need any batch script file which uses ADB and requires to install windows drivers

it's much faster that way via quick reboot, then use odin3

but if you can access KIES, then use KIES to upgrade to whatever firmware you want with the registry hack
[Galaxy S I9000 General] Kasha:
I tried, my phone comes from Germany and has the DBT sales code, I changed the ProductCode in registry many times with different variants (also changed the values in DEVCONINFO and HIDSWVER), but was offered no option for firmware update in Kies (with test mode both on and off).
[Galaxy S I9000 General] Quantus:
This is not quite as insane as heating your phone in the oven, and you probably won't want to do this but...

Try bricking your phone, and then sending it to Samsung. I did, and I now can use the 3-button grips to enter download and recovery mode.

If I had the option, and prior knowledge of the importance of the 3-button method of getting into recovery or download mode I would have been more careful when I got my phone. I wasn't, and I purchased a phone with a disabled 3-button recovery. Darn.

Because I have flashed firmware onto different devices without any past problems, I elected to flash the Bell JH2 firmware (from JG9, using Odin), despite the lack of recovery options. In truth, I had little choice, as somewhere along the customization road I messed something up badly enough that continual force close messages made the phone unusable.

Obviously the flash failed, and I was left with the black screen of death.

I took the phone back to Bell, and they sent it along to Samsung (last Wednesday). Today I got the phone back and, just on the off-chance, tried the 3-button grip to enter download mode; less than a second later I was in download mode. I can now enter download and recovery mode with ease. Samsung also upgraded the phone to JH2.

I could't find any mention in the forums that Samsung would enable the 3-button features, or that JH2 enabled the features, but it appears that one or the other has done so. Draw what conclusions you will.

Before anyone asks: I have confirmed that the phone is the same phone (the s/n and imei stickers on the phone match the stickers on the original box, which wasn't sent with the phone to Samsung, and the phone remains sim unlocked), and I employed the same 3-button procedure this time as in all previous, failed attempts (actually I tried every trick of timing, grip, battery insertion, sim card and xd card in the previous failures).
[Galaxy S I9000 General] AllGamer:
:eek: wow! you got the phone back so quickly?!?!?!

it's been more than 5 weeks already for me, and i still don't have my original phone back

good thing i bough a few...
[Galaxy S I9000 General] Quantus:
Yeah. I was a little surprised myself.

While I didn't like the sinking sensation I experienced when I bricked the phone, all-in-all I am not unhappy with the result, as I expected to have to wait a month or two before I would be able to unlock the phone, cancel the Bell plan and use the phone with my Rogers.

Now I have a fully functional, unlocked phone after less than two weeks of ownership (yep, I bricked the phone 4 days after I got it - I guess I should be more appreciative of the features of my former HTC Hero ;) )
[Galaxy S I9000 General] AllGamer:
i beat you, i bricked my first SGS on the 3rd day of owner ship trying to flash Froyo Alpha, knowing i had a disabled 3 button phone :p
[Galaxy S I9000 General] xZeDgEx:
I am happy to hear you got your phone back so quickly. Mine was sent off by Bell on Wednesday, it died on its own accord though, no rooting or anything.

This loaner N97 is killing me, why on earth these phones are so popular in other parts of the world boggles my mind. Its most clunky slow ass OS I have ever used.. resistive touch screen on top of that makes me want to kill something.
[Vibrant Q&A, Help & Troubleshooting] LostinThesauce:
so heres the problem, i installed adw launcher and beautiful widgets and after installing the beautiful widgets the samsung widgets folder disappeared and do did the android folder all i see is a few of the standard widgets and all the beautiful widgets. i was wanting to use a couple of the samsung ones. how do i access then and start them.???? thanks in advance for any help.
[Vibrant Q&A, Help & Troubleshooting] atoz350:
They disappeared after you used ADW launcher. The Samsung Widgets can only be used with TouchWiz.
[Vibrant Q&A, Help & Troubleshooting] LostinThesauce:
OHHHHHHHhhhhhhhh well dont i feel like the tard. thanks for clearing that up for me.
[Epic 4G Android Development] noobnl:
USE AT YOUR OWN RISK

adb push C:\Users\*\Downloads\redbend_ua /data/local

adb shell

chmod 755 /data/local/redbend_ua

/data/local/redbend_ua restore /sdcard/zImage.bin /dev/block/bml7

or

/data/local/redbend_ua restore /sdcard/recovery2.bin /dev/block/bml8

http://www.sdx-downloads.com/devs/noobnl/redbend_ua.zip

stock kernel http://www.sdx-downloads.com/devs/noobnl/zImage.bin

clockworkmod recovery: http://www.sdx-downloads.com/devs/noobnl/recovery2.bin

put it in sdcard

build 2: fixes script (made a dumb mistake)
[Epic 4G Android Development] Badge2378:
So.. I used at my own risk.

after copying redbend over and trying to flash clockworkmod recovery I got a wierd error telling me something like the "file count is wrong" (if somebody else tries this PM me with the correct message so i can fix this)

I rebooted the phone and tried again. It worked and I can confirm clockwork recovery installed. I have not tried to do anything like format SD or install a zip yet, but I will.

After booting into recovery I was only able to find three working buttons.

1. The "Smiley" button next to left shift will allow you to navigate the menues, it functions like an up arrow would.

2. The "H" button behaves like the "enter" key

3. The "Searching Glass" (On the front, the rightmost lit button that looks like a magnifying glass) = return to the main menu within recovery.
[Epic 4G Android Development] Fixter:
I will test right now.

This is what I got.

FOTA : Make Block Device Nodes

lcd_init(498): start!

lcd_init(507): fb0 open success

lcd_init(514): width = 480, heig

open device file: Permission den

bmldevice_get_size: bmldevice_op

dst: /dev/block/bml8 partition s

part_size: 0x0

reboot: Operation not permitted
[Epic 4G Android Development] Fixter:
Bump for update.
[Epic 4G Android Development] Badge2378:
AH I just realized i still have the command prompt window up from both the attempt that work and the attempt that failed.

C:\android-sdk-windows\tools>adb push c:\redbend_ua\redbend_ua /data/local
1523 KB/s (313888 bytes in 0.201s)

C:\android-sdk-windows\tools>adb shell
$ su
su
# chmod 755 /data/local/redbend_ua
chmod 755 /data/local/redbend_ua
# /data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
/data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
RedBend Update Agent 6,1,14,1

FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/recovery.bin
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
failed to read from /sdcard/recovery.bin (Bad file number)

>>>>NOTE INSERT>>>>> BETWEEN THE PREVIOUS LINE AND THE NEXT I DID A BATTERY PULL REBOOT.

C:\android-sdk-windows\tools>adb shell
$ su
# /data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
/data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
RedBend Update Agent 6,1,14,1

FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/recovery.bin
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 20384 bytes
read finished

C:\android-sdk-windows\tools>
[Epic 4G Android Development] Fixter:
Thanks. I know what went wrong. SU was needed.

BTW. The first time I did it. The many read file appeared to me. But I did not have ClockWork recovery.
[Epic 4G Android Development] noobnl:
nice! time to update the post!
[Epic 4G Android Development] Fixter:
The thing is Noob, that I had the same result with one try. And I do not have Clockwork recovery.
[Epic 4G Android Development] Badge2378:
Here is a wierd bit.

If I reboot using "Volume Down" + "Camera" + "Power" i get into clockwork.

If I "Reboot to Recovery" using a software tool (Root Manager specifically) i end up in the stock recovery (Blue Text)

??
[Epic 4G Android Development] Fixter:
If I boot on Recovery it boots to recovery. Hm..
[Epic 4G Android Development] Fixter:
C:\SDK\tools>adb shell

$ su

su

# /data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8

/data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8

RedBend Update Agent 6,1,14,1

FOTA : Make Block Device Nodes

lcd_init(498): start!

lcd_init(507): fb0 open success

lcd_init(514): width = 480, height = 800

page_msize: 4096, phy_unit_size: 262144

src: /sdcard/recovery.bin

dst: /dev/block/bml8 partition size: 0x780000

part_size: 0x780000

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 20384 bytes

read finished

I do not have Clockwork.
[Epic 4G Android Development] Badge2378:
I should have said boot, as from power off.

If I start with the power off, then Press "Volume Down" + "Camera" + "Power" and keep holding them, i end up in Clockwork Rocovery v2.5.0.4

I'll shoot a pic as soon as my wife(and her camera) get home.
[Epic 4G Android Development] Fixter:
I'm gonna go check ROM Manager

Edit: Rom Manager boots me to Stock Recovery.
[Epic 4G Android Development] Badge2378:
Yeah, that's what i said before. The only way I've been able to boot into ClockworkMod is using the three button combo method.
[Epic 4G Android Development] Fixter:
I get the same thing using both methods.
[Epic 4G Android Development] shabbypenguin:
check the first post again make sure your applying the recovery.bin to bml8
[Epic 4G Android Development] Fixter:
If you check my last post with the code, you can see we both have the exact same results. Also. I copy, pasted.
[Epic 4G Android Development] rjmjr69:
I dont understand the parrt about

/redbend_ua restore'

where do I place that file in the tools folder of sdk? and clockwork file on root of sd card?
[Epic 4G Android Development] Fixter:
In the root of the SD Card.
[Epic 4G Android Development] rjmjr69:
thank you so all three files on root?
[Touch Pro2, Tilt 2 Themes and Apps] Allen Mead:
It's something that has always really bugged me, the black highlight on the las sms received on the threaded mode especially when there's a few loading and the screen slips down half way through typing, grr!

This mod is for HTC Messages ver. 1.5 (Build 2016.2424)

Well, navigate to here with your registry editor;

HKey_Local_Machine\Software\HTC\HTCMessaging\Miscellaneous

Change: "EnableListItemFocus" to 0

Job done :cool:

PS. as far as I know this hasn't been posed before, apologies if it has.
[Touch Pro2, Tilt 2 Themes and Apps] Allen Mead:
Dam it! Was working earlier, doesn't seem to be now.
[EVO 4G Q&A, Help & Troubleshooting] Mastema_Yage:
So I backed my phone up using Titanium and even moved all of my files to my computer. I completely erased EVERYTHING to try and update to 2.2 (froyo). Everytime I go to download it loads and then the exclamation point with the triangle around it pops up.

I went to my phone identity and this is what it shows:

Model Number: PC36100

I did root my phone before using the Unrevoked method but I don't know what to do.

Any help is really appreciated. Also, this is my first time posting this, just let me know if I should move this somewhere else.

Thanks
[EVO 4G Q&A, Help & Troubleshooting] bcnice20:
questions should be posted in the q&a forum just a heads up they get kinda ruff around here.

but to answer your q do you have a recovery image properly installed
[EVO 4G Q&A, Help & Troubleshooting] neodorian:
Two things...

If you root your phone completely (unlock NAND, etc.) then you can just flash one of the rooted Froyo ROMs in this forum. Most if not all are much improved over the stock one.

If you do root your phone, for the love of all things you consider holy don't install the OTA update even if you can! It makes re-rooting the phone much more of a pain in the ass. :D

If you are still running a 2.1 ROM then consider yourself lucky. You dodged a bullet. Check out the two threads in this forum:

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

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

I had so many problems trying to take supposedly easy ways out (unrevoked, simpleroot, etc.). Some people had an easier time but man...until I just did it like this I was having so many problems. It looks like a pain in the ass but it takes maybe 15-20 minutes and mainly consists of installing a few things and pasting some commands. Once you have NAND unlocked and a custom recovery, you will be able to do pretty much anything you want with your phone.

Good luck!
[EVO 4G Q&A, Help & Troubleshooting] xlGmanlx:
agreed, i tried all the "easy ways" and just manned up and did it the old fashion way and haven't looked back. I did have a little pucker factor to for a while since all the "easy" ways just boot looped me
[Captivate Q&A, Help & Troubleshooting] 02CWRX:
When I first got the phone earlier this week, I could plug it into the charger in the wall just fine with no issues, it would just charge. Now suddenly it started telling me USB connected and goes to the MTP screen and of course locks up the phone.

I can of course bypass this by switching the phone to mass storage mode, but since I have Kies and use it occasionally, it would be nice to not have to switch that setting each time depending on my charging/syncing situation.

Why would it have not locked it up with the MTP screen originally when charging from the wall but now it does? The results are the same whether its plugged into the wall or the USB port on the computer. I have two Captivates bought brand new on a family plan, both do this now with any combination of chargers and USB cables, wall USB port, or car charger. Neither one has a common application installed since the other is my girlfriends who hasnt done much to it yet, so Im blaming the phone itself for now...

~T.J.
[Captivate Q&A, Help & Troubleshooting] 02CWRX:
Interesting. I just checked with my BB charger and they dont do it using that charger, but they do it as soon as I connect the stock charger again.

Im wondering if its a voltage sensing circuit thats tripping due to the different voltages which should be applied - either wall charger or USB port. Maybe for some reason my wall chargers arent putting out enough voltage and its thinking its a USB port, but the BB charger is putting the right amount of voltage out?

Am I on base as to how it differentiates between wall or USB port? The number of pins obviously doesnt matter as all the cables have all the pins in them, unlike some charger cables which only have the power and ground. The only thing I can think of is that it uses the amount of voltage/current to tell the difference and create its reaction.

~T.J.
[Captivate Q&A, Help & Troubleshooting] Dani897:
Sounds like a problem with the stock charger, maybe usb cable alignment. My iphone wall adapter does this with the samsung cable but the samsung wall adapter doesn't, same with my car charger from att. Also I have a $5 walmart car charger that has a cable that splits into both a mini usb and a micro usb that isn't a real usb cable, it's charge only. That cable has no problem on any wall or car adapter. I believe the phone detects if its connected by checking voltage on a data pin (just a guess really) so if a nonstock charger is used it assumes that it is a computer. But it may also be a data signal that is given off by the charger.
[Captivate Q&A, Help & Troubleshooting] WeeklyWars:
did you try a new charger and if so, did it work? I've had my captivate since Thursday and on Thursday it charged and everything fine, but then yesterday,

a) no computer I connect it to while recognize it, no matter what I have it set too and have latest drivers installed

b) if I charge it, after I unplug it, it locks up to black screen and I have to remove the battery to get it to work

c) I also have an in-dash touchscreen monitor in my car that has a usb port because it works with an ipod. I plugged the usb into to use it as a car charger, unplugged it, same thing

d) it did say usb connected after it was unplugged, but I switched from mass storage to ask on connection and it went away

so is an actual wall charger the solution?
[Captivate Q&A, Help & Troubleshooting] WeeklyWars:
and now I unplug it, and if it locks, it will not unlock, just black screen

I have to take out the battery and then only way to get it to turn back on, is to plug it back in the wall
[Captivate Q&A, Help & Troubleshooting] Dani897:
^^^Ouch that's not right, if you can't figure it out you may need to re-flash or just bring it back under warranty, or insurance
[Galaxy S I9000 General] LeshaK:
Profit

Deodexed firmware [based on I9000XXJPC], you can apply themes etc

Root via su+Superuser 2.3.5

Working recovery

Ability to select only those components that you want (the size of the firmware from 72MB to 140MB)

http://forum.samdroid.net/f49/samdroidmod-kitchen-all-one-samsung-galaxy-s-i9000-2187/
[Galaxy S I9000 General] AllGamer:
cool! i'll play more with this after we get Froyo
[Galaxy S I9000 General] massigiulio:
rom manager

May I install it with rom manager?