yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Defbrett:
Ok i'm back with my Galaxy Tab (T-Mobile) (Rooted using z4root).

I was able to get my Wifi working again after copying and pasting the default bcm_supp.conf file (which i found on a Germany Website) and creating a bcm_supp.conf.bak file as well, to /data/etc/wifi. This combined with copying back in the original (factory)wpa_supplicant file got me working again.

I'm able to reproduce my findings over and over again and would like to see what one of you devs might have to say about it. Here is my process:

1. Turn my Wifi Off.

2. Make back up of wpa_supplicant from /system/bin and bcm_supp.conf from /data/etc/wifi.

3. Delete wpa_supplicant from /system/bin

4. I take the 0.6.10 wpa_supplicant and paste it into the /system/bin folder.

5. Turn my Wifi On.

6. Connect to my Home Wifi Network.

7. Enable Wifi Tether via my Rooted MyTouch, using one of those tether apps for rooted phones (code.google.com/p/android-wifi-tether/) .

8. Tab "sees" "AndroidTether(adhoc)"

9. I Connect to AndroidTether(adhoc)

10. Browse the web to confirm connection (works great!! :D).

11. Turn off My tethering on my MyTouch at which point the AndroidTether(adhoc) does not automatically disconnect from my Tab untill I tell it to "Forget" the connection.

12. Attempt to reconnect back to my Home Wifi Network and my Tab gets stuck in an endless loop of "Connecting, Disconnect, Connecting,...." switching between these states about every 5 seconds.

....after this the only way to bring my wifi back is to copy back in the original wpa_supplicant and bcm_supp.conf files but, even then it's a bit tricky (a pain).

So, my questions to any of you are; is my procedure correct? Is this the expected results? Am I totally off my rocker? :)
[Desire Android Development] DJ_Jedi:
I've flashed the wpa-6 zip and i can see my ad hoc network, but i cant connect. If i set up a wpa2 connection with my pc i cant even log, with a wep i reach the ip assignment, but stops there.

Tried with version 5, same result.

Any suggestion?
[Desire Android Development] 44enviro:
root permanent

Do I have to root my verizon galaxy tab (GT) permanently in order for this to work? I rooted the GT temporarily and replaced the file and all worked. After rebooting the GT it was back to where it was out of the box. Is there a way to replace the file permanently?

If I root the GT, can I image it to restore it to factory defaults if the need arises?

I am completely new to android OS and the GT as well, so forgive the noobie Q&A.

James...
[Desire Android Development] Defbrett:
james,

I've found that z4root doesn't work on permanent root it only works with temporary so, whenever you reboot your GT all the files are replaced.

Also you should read my post above as I've already tried to do this with my GT and it works great however; you'll have a hell of a time trying to get connected back to regular (infrastructure mode) wifi (i.e. not ad-hoc)....

personally since i've got no help here i'm just going to wait for to get a new phone that has a built in AP app. I don't think my mytouch supports infrastructure mode with that free wifi tether app so i'm SOL for a bit.

....if it works for you let us know.
[Desire Android Development] dexter93:
Well tried this with desire and windows xp... can see the network but i cant get an ip. tried with wep and without security but nothing, even with disabled firewall. Is it the pc or the phone's fault?
[Desire Android Development] muthax:
Anyone tried this on a Gingerbread ROM?
[Desire Android Development] :
Greetings,

Had just applied this update to my HTC Desire with Taiwan 2.2 stock rom & it just works.

Thanks for all your great works:)
[Desire Android Development] webvan:
Tweak works on Dell Streak 7 too, use version 0.6 of the wpa_supplicant.
[Desire Android Development] SuzukiDan7:
Sad to say, this is NOT working on my g1 moto droid running bugless beast 0.6 (android 2.2.1 base) using wpa_supplicant 0.6.1. I am rooted so I copied the file to my system/bin as instructed in this post and it causes my wifi to crash, disable itself, and force close the wifi settings screen.

Once I restored the old file my wifi is fine again but I really would love to steal my friends iPhone mywi signal =)

Anyone got a working file for g1 droid??
[Desire Android Development] aMpeX:
For all of you having problems with WiFi not working at all after pushing the file, check your file permissions.

from a root shell and the appropriate directory type

ls -l

if your permissions for wpa_supplicant are not 755 (rwe re re) or higher then set it using

chmod 755 wpa_supplicant

got wifi working again for me.
[Desire Android Development] m11c3:
i'm using legend.. replace file wpa_supplicant.. then reboot.. wifi not working.. then checking permision ls -l /system/bin/wpa_supplicant result

-rwxr-xr-x system sdcard_rw 312440 2010-08-17 18:12 wpa_supplicant

what wrong?

or legend can't use this version.. use old version 5.x from index hero?
[Desire Android Development] bala242:
pls compiled for mine i9003 ver is 6.10

i attc the original one
[Desire Android Development] xxguestxx:
Does this work for Ideos X5? =D....mine wont connect to my zyxel wireless modem. So i want to either try figure out how to connect phone to laptops AP or via Data cable. Is it possible? (cant try connectify either coz i got XP)
[Desire Android Development] kolaval:
It works perfectly...

Had to mount /system first but afterwards it's fine

Thank You
[Desire Android Development] :
Broken for me. Cm7 nightly 156
[Desire Android Development] slang:
I know this is an old thread but does anybody have the original wpa_supplicant for the motorola milestone? Please and Thank you
[Desire Android Development] daveba:
You don't need this for CM7 as IBSS network is accepted in the framework.
[Desire Android Development] rib.ale:
Good day friend, takes a lot activate Ad-hoc on my Htc one X (android 4.0.4) or my Galaxy Ace (android 2.3.6).

I bought a Robo Brookstobe Rover and he needs Ad-hoc to connect

My HTC One X has the following verção of wpa_supplicant: v0.8.x-htc-0:13

Please help me, I have no knowledge to do this alone suffice:

thank you very much
[Desire Android Development] mannu004:
can u patch my wpa_supplicant if i provide u

sir plz patch and compile my wpa_supplicant it is of samsung galaxy tab2 p3100
[Desire Q&A, Help & Troubleshooting] AndroJosh:
This is a rather random question just to see if it's possible or not, is it possible to port a rom of Windows Mobile on to a HTC Desire?

Thanks Josh.
[Desire Q&A, Help & Troubleshooting] Zhypr:
Luckily not.
[Desire Q&A, Help & Troubleshooting] !PANDA:
it is possible, as the hardware is better then some phones running Windows Mobile, but why would you wan it on your beloved Desire?!
[Desire Themes and Apps] corzradio:
Question. as you know or not know i have a hd2 leo with desire android rom. Im a nood to this but i love the themes some of you have . like the espresso..how do i make those work on my phone???. There is no nand or recovery but we can adb..please help
[Desire Themes and Apps] AndroHero:
does android on the leo have full r/w access :confused: i assume it does so you shudnt need recovery you should be able to to pull the framework-res.apk (or whateva its called) using adb, modify it then push it back :confused:
[Desire Themes and Apps] corzradio:
ok ..ok..

makes sense...so what would be the exact adb command to push the espresso bar??
[HD2 Windows Mobile 6.5 Themes and Apps] amilo123:
can anyone tell me what are the differences between igo primo and igo my way 2009 for WM?

thanks!
[Galaxy S I9000 General] setted7:
Hi all,

Had the lock pattern funtion enabled and my fanatastic mate wanted to see what happens if you put the incorrect pattern several times. Yep it locked me out and now finding out that the screen asking for

My gmail info is a bug and does not work.

Is there a fix for this issues so I can unlock the pattern lock.
[Galaxy S I9000 Themes and Apps] Tzi1983:
Hi guys, dont know what happened but my Galaxy S cant pull mails out of my hotmail account since friday, i cant see my old mails in the box and dont receive new ones too, any ideas ?
[Touch Diamond, MDA Compact IV General] ksxjc84:
I have a HTC Diamond running ROM 2.03.707.2 WWE, for some unknown reason, the past 2 months I keep having the following problems with my Diamond suddenly -

1. Random dial-outs to the last dialed number, when my headset is plugged in. I keep killing the calls and it keeps coming back.

2. Voice commander keeps activating without my clicking anything, and have my headset plugged in - tends to happen when I listening to FM radio/windows media player/TF music player. Same as above, I keep trying to kill it and it keeps re-activating, drives me absolutely nuts.

3. Calls tend to go on hold when I am talking halfway, I am sure my fingers did not hit the 'hold' button at all.

4. Sometimes, calls in progress are cut off - screen is off so I know cannot be because I pressed on it accidentally.

i am a noob so I have no idea of what to do about this, and I don't dare to just try and flash/replace ROMs as I am afraid that I'll brick it....
[Touch Diamond, MDA Compact IV General] julessouren:
Thank god I found this thread - I had no idea what to search for; I tried 'sudden calls', 'spontaneous calls' etc. but found nothing, and by digging through all the threads I found someone with the same problems, but alas, no answer yet.

I have to permanenty disable outgoing connections because this problem is so annoying. I also noticed it happend with the headset plugged in, and for me also when I'm playing some music with win media player. I can have the device locked (hold end button), turned off (top button on phone), or turned on, and this problem always occurs.

I'm using a custom rom, dutch, ver. 1.39.479.2 (forgot which one :() , radio version 1.00.25.05 (quad band/power save/connection improved version).

Was thinking this might have something to do with the radio, but somehow it seems the headset is definately causing this since thats the only common factor.

Any help from the pro's please? :)
[Galaxy S I9000 Android Development] Benjamin Dobell:
What is Heimdall?

Heimdall is a cross-platform open-source tool suite used to flash ROMs onto Samsung Galaxy S devices.

How does it work?

Heimdall uses the same protocol as Odin to interact with a device in download mode. USB communication in Heimdall is handled by the popular open-source USB library, libusb-1.0.

Why “Heimdall”?

The flashing software Odin is named after the king of gods in Norse mythology. Loke, the software component on the Galaxy S that provides functionality to flash, may also to be named after an important character in Norse mythology, often translated as Loki. As such I have named my flashing software Heimdall, after the Norse god, and guardian of the Bifrost Bridge.

What platforms does Heimdall run on?

Linux, OS X and Windows (XP, Vista, 7 etc.)

Why use Heimdall when we can use Odin?

Odin is generally unreliable and only runs on Windows systems. Furthermore, Odin is leaked Samsung software that is not freely available or well understood by the community.

Is Heimdall safe?

No matter what method you chose, flashing firmware onto your phone has a lot of potential for disaster. We have tested Heimdall with a variety of phones flashing several different firmware versions resulting in a 100% success rate. As such we believe that Heimdall is generally reliable. However keep in mind, just like any flashing software, Heimdall has the potential to brick your phone if not used correctly.

How do Galaxy S phones get bricked when flashing?

Besides the inherent risks like power outs, accidental removal of the USB cable etc. The Galaxy S appears to be running extremely unreliable USB control software.

A failure to flash does not automatically equate to a bricked phone. However if you're extremely unlucky and the flash fails whilst transferring the primary boot-loader, secondary boot-loader or params.lfs (all quite small) than you've got yourself a paper weight that you're hoping Samsung will replace.

Please be extremely careful mixing files from different firmware releases. Don't do so unless you're certain it will work!

What Galaxy S variants has Heimdall been tested with?

We’ve tested Heimdall with a Galaxy S GT-I9000 (8 GB) from the United Kingdom and Galaxy S GT-I9000 (16 GB) from Australia. We don’t personally have access to any other devices to test with, however users have confirmed Heimdall functions correctly with the AT&T Captivate, Bell Vibrant, Telstra GT-I9000T, Epic 4G and the Galaxy Tab.

Enough talk, where can we get it?

The latest release is available here. Please read the instructions and README files included in the archives.

I love you, man. Will you have my baby?

No, but I will very gladly accept donations. If you appreciate my work and would like to support future development you can make a donation here. If you think you have something else to offer, then feel free to shoot me a PM or contact me via the contact form on the Glass Echidna website.
[Galaxy S I9000 Android Development] andrewluecke:
Sounds interesting.. Certainly something to watch in the future..
[Galaxy S I9000 Android Development] invaderjohn:
for linux? YES! i love u ;)
[Galaxy S I9000 Android Development] AllGamer:
Kudos for you! wow it looks impressive :D

A question though....

the instructions seems to be very... Windows oriented.

What about Linux or MAC OS?

Do we need to run it with WINE, or just run it as a DOS executable?

same question for MAC OS, you know people in MAC are so used to plug and play, If i were a MAC user i'll just plug my phone in, and expect to run Heimdall by click on it and have it come up.

However at the moment it seems to require Windows emulation for it to run.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Thanks guys.

Also, I forgot to add in the README that you also need the same PIT file as the one that is installed on your device, probably version 512.

I can see by my website's bandwidth usage that people have been downloading the alpha. Has anyone tested it yet?
[Galaxy S I9000 Android Development] Benjamin Dobell:
The alpha release is just the Windows binaries. Whilst the source code certainly compiles for OS X and Linux I want to make sure that everything is running fine on Windows first, with Odin nearby if need be.
[Galaxy S I9000 Android Development] AllGamer:
ahh, Good to know, i was worried there for a second :)

I can't test it yet, my phone hasn't come back from repair.

i'll help test as soon as my phone is back.
[Galaxy S I9000 Android Development] husq510:
go public linux binary too, else ppl will use odin instead your and you wont receive much feeback as much as if you release linux binaries.
[Galaxy S I9000 Android Development] Benjamin Dobell:
I know it's a pain that Linux users have to wait (as usual). As much as I do want feedback, I don't want feedback from Linux users saying that the flash failed for some reason and that they don't have access to Windows/Odin.

I'm not actually sure if I'll ever release Linux binaries as binary compatibility across multiple Linux distributions is problematic. Of course once I've confirmed everything is working on other peoples' devices, what phone models are supported etc. then I will release the source code with instructions to compile for all supported platforms.

EDIT: Has Heimdall really been downloaded ~45 and no-one has bothered to install and run it? :(
[Galaxy S I9000 Android Development] mike.sw:
I'm having trouble with the following step:

4. Under Universal Serial Bus Controllers right click on the Samsung composite driver and chose Properties.

I don't have such device in device manager.

Windows 7 x86
[Galaxy S I9000 Android Development] jodue:
very cool stuff, thank you a lot!!!

first of all. i am a linux only user and had to run odin on a virtual box which is a pain in the ass but i fully understand your argument to first only release a windoze version to get it out of alpha state.

now, while i know that it's also possible to brick the device with odin and i have flashed several times now. i am a little afraid to try heimdall (to be honest). did you implement the additional security measures (delay+resend) after you bricked your device or before? you wrote that heimdall supports only full firmware flashes atm. it would be cool if we could also use it to just flash a kernel. any plans to implement this?

thanks!
[Galaxy S I9000 Android Development] Benjamin Dobell:
Is your device plugged in to your PC and in download mode?

I suppose you would also have needed to install Kies at some stage. However, Odin makes use of this driver so if Odin works it should be there.
[Galaxy S I9000 Android Development] mike.sw:
Oh god, I'm an idiot.

Connected phone to wall charger, and was sure it's my USB cable.... *facepalm*
[Galaxy S I9000 Android Development] Benjamin Dobell:
I implemented the delay and resend after my phone was bricked.

I think I was ludicrously unlucky in how my phone got bricked. Given that the primary boot loader is only 256 KiBs whilst the factory filesystem is over 250 MiB (plus other files). The chance of failing whilst the primary or secondary boot loader is being sent is quite slim.

When I was debugging Heimdall I would often intentionally stop at other points during the flash. After resetting it would just result in the connect phone to PC image being displayed (instead of booting). Then I could just restore with Odin (after several attempts) and then further restore using ClockworkMod backups.

However, by no means do I want to pressure anyone into running the software, especially whilst it's only an alpha release.

EDIT: I just realised I didn't answer your question about just kernel flashing. Yes, I definitely intend to implement functionality to only flash singular components at a time. I'd also like to implement functionality to dump files if possible. However I won't know if I can do that until I get my phone repaired or get my hands on another Galaxy S device.
[Galaxy S I9000 Android Development] mike.sw:
Hey again

I'm looking the flash.bat and see it need two files that my firmware (I9000JPJG8) don't have in zip/tar file:

-boot boot.bin -sbl Sbl.bin

How heimdall will handle it? Is it safe to go on?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Heimdall won't let you continue as the first thing it does (before connecting to your phone) is check that the specified files exist. Those two files are the primary boot loader and the secondary boot loader. I'm a bit surprised they're missing from your firmware. :confused: They're usually in the Code tar archive.

You'll have to grab them from somewhere. If you don't want to download more firmware then you can retrieve them from your device. Err, I'll update this post in a minute or two with instructions.
[Galaxy S I9000 Android Development] mike.sw:
This is one little tricky FW.

The last one I tried was I9000XWJM5 and it had 3 tar files as supposed.

This one just have one tar file, and people who installed it with Odin said to use only the PDA section with the single tar file.

I'm not sure, but it seem to work for them.

BTW in your README I think you should remind for the folks to put the pit file in the dir as well :-)

Also here in WIN7 it didn't let me change the driver as simply as stated in README.

What I had to do is to use the Have Disk option, and point it to the dir. Otherwise it says that Windows already have the correct driver installed.
[Galaxy S I9000 Android Development] Benjamin Dobell:
If you still have I9000XWJM5 laying around you could give that a go, it is the firmware I use.

If not you can get the boot loaders by copying them first to your sdcard using:

sudo dd if=/dev/block/bml1 of=/sdcard/boot.bin
sudo dd if=/dev/block/bml4 of=/sdcard/Sbl.bin

Clearly your phone needs to be rooted to use sudo.

EDIT: I need to go to bed now (it's actually well and truly morning here). I'll be on in 5-6 hours if you require any more help. Thanks for going to all this effort so far!
[Galaxy S I9000 Android Development] mike.sw:
Yea, I'll grab JM5 again just in case the **** hits the fan ;)
[Galaxy S I9000 Android Development] jodue:
thank you for the additional information on the process. i think i will give it a shot next time i want to flash a new firmware. donation is on the way!
[Galaxy S I9000 Android Development] AndreEli:
Thanks!

I'd done a few kernel flashes with the 512 pit, and they went fine. I just wasn't sure if I should be partitioning or worrying about CSC since I've never used Odin...
[Galaxy S I9000 Android Development] [Ramad]:
This program is very impressive...I'm glad that it let me flash JP6 using 512.pit file as I think that the 803.pit can cause lag during later use, and the flash itself did not take long.

Thank you Benjamin for the program and thanks to dirk1978 for the walk-through. :)
[Galaxy S I9000 Android Development] Benjamin Dobell:
Samsung just got back to me in regards to the bugs in the secondary boot loader. Apparently they have been fixed for the Froyo update (in particular the official Nordic update announced on October 15) and flashing via OS X should now be supported.

If there are any users who have a Mac and a Galaxy S running the Froyo update (in particular the updated Sbl.bin) would you mind giving Heimdall a go?
[Galaxy S I9000 Android Development] insty:
I'll give it a go now :)

Getting errors on compile...

./configure: line 1935: syntax error near unexpected token `DEPS,'

./configure: line 1935: `PKG_CHECK_MODULES(DEPS, libusb-1.0 >= 1.0.8)'
[Galaxy S I9000 Android Development] ashwinds:
Oh I would love to give it a go, but is there anywhere i can download the official version from?
[Galaxy S I9000 Android Development] [Ramad]:
There is no SBL in the Nordic version (JP6), the Arabian version has it (JPA).
[Galaxy S I9000 Android Development] Benjamin Dobell:
Hopefully JPA's Sbl.bin contains the fix then.

Samsung just told me the fix was included in the Nordic European version released on October 15. Presumably they were referring to the official version downloadable via Kies. Was your copy of JP6 retrieved via Kies or downloaded from elsewhere?

You're missing the libusb-1.0.8 SDK. If you've got 1.0.6 already installed on your system then you can modify configure.ac to use the outdated version, change:

to:

then run before ./config, make, sudo make install, run:

Or you can download and install version 1.0.8 following instructions on the libusb website.
[Galaxy S I9000 Android Development] [Ramad]:
I did not mean the KIES version(s) but JP6 and JPA that we can download in this forum.
[Galaxy S I9000 Android Development] Narcissus85:
Is there a way to flahs a kernel without a PIT?

i need it for flashing z4mod kernel on JMP and i read that i dont need to select pit file..

thanks
[Galaxy S I9000 Android Development] Benjamin Dobell:
Yeah my PIT file implementation is mostly just a safety thing. Although Heimdall does have functionality to upload a PIT file to a phone it's not actually used when you flash. All Heimdall does is download the PIT file from the phone and tries to make sure it matches the PIT file you've selected.

So whilst it is definitely possible to flash without comparing the PIT file Heimdall presently doesn't allow this. I haven't tried this myself but it should be simple enough to modify the source to not perform the PIT file check.

In main.cpp comment out everything from line 299:

through to line 356:

Also comment out the whole if statement starting at line 542 and ending at line 547:

Then compile as usual and you should be fine to flash a kernel without specifying a PIT file. Keep in mind this isn't recommended behaviour for regular flashes, hence why the current code isn't like this.