yashsingh1/xdaforums huggingface dataset:
[Xperia Arc Q&A, Help & Troubleshooting] the_tooon:
I have different d-links in office and home.

Home one is going down in very first attempt to connect until hard reset (arc shows good wifi connection though), office one is a bit harded and stand still, but arc is loosing connection after, I guess, few mbytes and need wifi turn off\on magic.

I can't describe how this *&@# annoying... :-(
[Desire HD Q&A, Help & Troubleshooting] RED_:
Ok so first and foremost, for the last two days (Sunday and Monday) my mobile network not been working at all. I turn it on and it acknowledges that but nothing happens, no notification in the notification bar at the top, nothing.

So i tried to fix it myself, did some googling, tried the t-mobile forum as that is my network and found an interesting post, posted 6 days ago. This person had a very similar problem to me and the solution they gave was to change an APN setting. In particular the Authentication type to "PAP or CHAP". That did nothing. Someone else told me to change the APN type from default to "*". Now that did work.

I had my mobile internet back, so i thought fine problem solved but bloody hell is it slow. It was never this slow, in fact before the problem i was quite impressed whenever i used my mobile network. Even when using HSDPA it is still very slow. Loading a website takes minutes rather then seconds.

To solve this i went to the t-mobile website and got new APN settings. Those new settings didn't even use HSDPA. I was stuck of GPRS! So i went back to the other settings and well i'm back to the problem of having a ridiculously slow mobile internet.

Anyone had the same problem? Or have a fix? Sorry for making this very long but i like to explain everything.

Would really appreciate any help on this matter. I plan on calling T-mobile tomorrow but if their APN settings didn't work i have no idea what to expect.
[Desire HD Q&A, Help & Troubleshooting] raze599:
Nobody expects it but if this has just happened out of the blue then its more likely on T-Mobiles end. Maybe they're having some problems. Call them tomorrow just to confirm.
[Desire HD Q&A, Help & Troubleshooting] RED_:
Cheers, will call them of course. I asked around and nobody else has had problems, i would have thought their own forums would be going mental if it was a big problem but maybe its confined to a small local server or mobile tower around here. We shall see.

God knows when the problem actually started, i was in Central London looking for a Starbucks and thought my phone could tell me, noticed it didn't work. I do know that it wasn't the gingerbread update because it was working after that.
[Xperia Arc General] matteh80:
Hey!

I can't start the calendar app anymore. Just get a message that the process com.android.calendar couldn't start and I have to force quit.

When I check under sync settings it says there is a problem with the sync right now, but I haven't found anyone else with the same problem...

I have frozen some stuff with Titanium Backup, but it worked before. What do you need for starting the calendar?

Anyone got an idea on how to proceed?

THX.

/matte
[Galaxy S II Q&A, Help & Troubleshooting] nadacjb:
Hi As I'm a student I'm looking for cheapest deal with sgs2. I found one deal with o2 with 18month contract for £18.5pm and £149 for the phone. It includes 50mins call, 250txts and 100mb. To me it sounds good cuz I don't really use calls and Internet much. However I use lots of txts to my fried so I'm looking for good deal with unlited txt does anyone have any suggestionss? :)
[Galaxy S II Q&A, Help & Troubleshooting] Xero Xenith:
What are your specifications?

Any networks to avoid?

How much data/calls?

Are you OK with lots of money upfront?

How many months? (12/18/24?)

Also, it may be a good idea to measure up how many texts you actually use. It may be cheaper to get that deal you mentioned, and then just pay for as many extra texts as you use, than pony up extra every month for unlimited.

Obviously if you're using 1,000+ every month you'll probably want unlimited, though :p
[Galaxy S II Q&A, Help & Troubleshooting] nadacjb:
I don't really mind about calls/data and upfront As long as it's not too much.. And I think 12 or 18 month would be good and I think I use +1000 every month.. Do you have any good ideass? Thanks :)
[Galaxy S II Q&A, Help & Troubleshooting] Xero Xenith:
OK, let's make a few assumptions...

1. You want to minimise total cost of ownership over 18 months.

2. If you got a 12 month contract, at the end you would cancel it and get the cheapest SIM-only deal possible with unlimited texts.

3. You don't mind about network.

Idea 1: £500 upfront (SIM-only) then £5 per month GiffGaff over 18 months.

TCoO = £590

Idea 2: Nothing upfront, then £28 per month with T-Mobile over 18 months.

TCoO = £515

http://www.affordablemobiles.co.uk/...amsung/galaxy_s_ii/17707417.html?source=rupiz

I can't find any better than that for now :) the second one is a great deal over 18 months IMO. I wouldn't like it myself because it's third-party T-Mobile data (which has capped speed), but overall a good deal :)
[Galaxy S II Q&A, Help & Troubleshooting] nadacjb:
Wow thanks :) and mmm what do you mean about third party t mobile dataa?
[Galaxy S II Q&A, Help & Troubleshooting] Xero Xenith:
Basically, when you buy a data plan direct from T-Mobile, it works like it should. But when you get it from a third-party reseller, it's limited to (I think) 350kbit/s down.

You may like to research the exact figures yourself, but it wouldn't mean you can't use the internet. It would just make it slow at downloading anything except small files/websites.
[Galaxy S II Q&A, Help & Troubleshooting] blickmanic:
the cheapest is o2's ')
[Galaxy S II Q&A, Help & Troubleshooting] Xero Xenith:
The O2 deal he mentioned doesn't include unlimited texts...
[Galaxy S II Original Android Development] Benjamin Dobell:
Original Thread:
[Galaxy S II Original Android Development] Benjamin Dobell:
Source has been pushed to Github. Let me know how it goes for you Galaxy S II folk.

If you're appreciative of the updates don't forget to donate so I can get myself a Galaxy S II :)
[Galaxy S II Original Android Development] PoTi_96:
Gr8 news! :D

Hope this won't increase the flash counter in download mode when it's finished

Swyped from my overclocked GT-I9100 using XDA Premium App
[Galaxy S II Original Android Development] Chainfire:
I'm happy with Odin on Windows, but great work nonetheless !
[Galaxy S II Original Android Development] PoTi_96:
on windows, yes ;)

but linux... ^^

Swyped from my overclocked GT-I9100 using XDA Premium App
[Galaxy S II Original Android Development] phunkycow:
Great, Ive been waiting for this. More linux love. Thanks!
[Galaxy S II Original Android Development] Xero Xenith:
Excellent! Though I may not be the first to try it, I'll probably be using this (tomorrow?) to flash my first custom ROM if all goes well :D
[Galaxy S II Original Android Development] 4iedemon:
Hey Ben,

Do you think its possible to make backups of firmware using this tool? I think it'd be good for those who wants to have carrier-branded ROMS backed up for warranty purposes.
[Galaxy S II Original Android Development] Locster126:
Nice will give it a shot later.

OT:

Phunkycow u here? Left the dhd behind? Loved ur cm builds on the dhd..
[Galaxy S II Original Android Development] phunkycow:
<OT>Yeah, sold it finally and i'm a happy panda now lol :)

Good to see you here too!</OT>

(Apologies for the OT :p)
[Galaxy S II Original Android Development] Benjamin Dobell:
Heimdall 1.2.0 command line binaries are now available. Debian 32-bit, Debian 64-bit, Windows and OS X (universal) are all available.
[Galaxy S II Original Android Development] Benjamin Dobell:
Sorry, I missed this post.

Heimdall has theoretically supported dumping of firmware for quite some time. However all the devices I've ever tested it with mostly send back junk data and eventually stop responding altogether (requiring a manual reboot). As far as I can tell this is simply a result of the secondary bootloaders on devices just not supporting the functionality, however it's possible that the functionality has been finished/fixed for the SGS2.

If someone wants to test out dumping when they test out flashing that would be great. If so I recommend you enable the verbose switch so you have a better idea of what is going on.
[Galaxy S II Original Android Development] aussiebum:
Nice, thanks! Would this (theoretically) work with the GUI from v1.1?
[Galaxy S II Original Android Development] Benjamin Dobell:
Yeah, you obviously won't be able to use any functionality that isn't available from the GUI though. Because the SGS2 has a few different partitions that aren't accessible from Heimdall Frontend you won't be able to flash to them, however you can still flash kernels etc. no problems.
[Galaxy S II Original Android Development] Benjamin Dobell:
OS X users, you will need to download the latest package again. The binaries are the same but I had forgotten to update the kext so that "the interface could be claimed".
[Galaxy S II Original Android Development] winst:
$ heimdall print-pit

Heimdall v1.0.2b, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Failed to detect compatible device

I installed the latest one in OS X 10.6, restarted, and got the above result. Note that running "adb devices" does show up my SGSII properly.
[Galaxy S II Original Android Development] elban:
is your phone in download mode?
[Galaxy S II Original Android Development] jps1974:
I tried print-pit and dump and ended up with a bunch of "Error -7 whilst receiving packet." print-pit seemed to work fine but was unable to end the session.

Find verbose logs here:

print-pit

dump

For obvious reasons, I'm a little hesitant to try flashing anything ;)
[Galaxy S II Original Android Development] Benjamin Dobell:
Thanks for the details, much appreciated.

The dump log doesn't really surprise me, it's actually better than how it fails on Galaxy S. The Galaxy S downloads a heap (megabytes) of junk, I guess that it's good that it fails immediately.

Haha, no worries.

A few questions though:

Does your device reboot after the PIT information is displayed?

When you reboot does the phone boot normally or is the connect phone to PC screen displayed?

Does "heimdall close-pc-screen" also fail to end the session?

If your device boots up fine (no connect to PC screen) then that should mean the end session packet was received (and interpreted) by your phone no problems. If that's the case then it's possible Samsung have just changed the protocol so no response is expected. It never really made sense to me that you've essentially told the phone you're done and then you still send it a reboot packet.

Alternatively the syntax to end a session may have changed slightly. Someone mentioned a flash counter, maybe I'm supposed to send a packet to update the counter (although I'd rather not anyway).

Without a SGS2 I'm unable to investigate this myself but if someone is able to get me a detailed USB log of flashing with Odin or Kies then I could sort it out. I literally need the 1s and 0s sent to/from the phone. If not then donations towards getting me a SGS2 would be immensely helpful. Thanks again to those of you who have donated.

EDIT: Doh, I just realised I spelt "successful" wrong when Heimdall downloads a PIT file :p
[Galaxy S II Original Android Development] jps1974:
Well, I grew some balls and tried a full flash - worked just fine ;)

To answer your questions:

Nope

Boots up normally

Yes, see here

I made a small donation towards your new device, but I'll be happy to help you out if you give me some instructions :)

By the way, I have to use sudo, otherwise I get this:

Failed to access device. Error: -3

Thanks for all your work!
[Galaxy S II Original Android Development] AdamOutler:
Here's Linux 64 https://android-casual.googlecode.c.../CASUAL/resources/heimdall/heimdall_amd64.deb

here's Linux 32 https://android-casual.googlecode.c...c/CASUAL/resources/heimdall/heimdall_i386.deb

I've verified both of them. Windows is being a PITA though!

Can someone make a Mac package with just the command line binary?
[Galaxy S II Original Android Development] CTH-EVO:
Greeings,

I have a G900P (Samsung Galaxy S5 -- Sprint) that I had hoped to work with. I've searched for tools

for those of us whom only have access to *NIX based boxes. I was told to try Heidmall. Discovering

that it's only available for the Linux *NIX OS, I was forced to grab some spare hardware, and install

Linux on it (I'm on FreeBSD). After installing Debian (Wheezy 7.6). I downloaded the Debian 1.4 64bit

version of Heidmall && heidmall-frontend to give it a go. To my disappointment, it doesn't appear to

support my device (phone). My proceedure(s):

Install heidmall, including the frontend.

Start up heidmall-frontend from a terminal session

boot the phone to download mode (with the stock USB cable attached to the computer)

choose Utilities --> Detect (returns Device Detected)

choose Utilities -- > Download PIT --> Save as (chose filename) --> Download

Which returned the About Software --> ERROR: Failed to access device. libusb error: 4

EDIT:

OK I grabbed the wrong terminal screen (wasn't root). So I grabbed the correct terminal,

and began the whole proccess again. Again, it FAILED. Here's the output:

Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...

What can be done? What is wrong?

Thank you for all your time, and consideration.

--Chris

P.S. Phone is Stock, ROOTED, and has Philz Touch CWM.
[Galaxy S II Original Android Development] MasterCATZ:
whats the trick to get heimdall to use the files downloaded from

https://samsung-firmware.org/downlo...national)/57v1/OPS/N7105XXUFOA1/N7105OPSFNL3/

trying to go back to stock with Ubuntu OS

any tool to convert that to something heimdall will 1 click use ?
[Galaxy S II Original Android Development] infinityz:
I tried to install the 1.1 gui, restart then install 1.2 binary, restart again!

trying to launch the GUI:

Process: heimdall-frontend [6626]

Path: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend

Identifier: com.yourcompany.heimdall-frontend

Version: ??? (???)

Code Type: X86 (Native)

Parent Process: launchd [296]

Date/Time: 2011-06-02 10:14:46.589 +0100

OS Version: Mac OS X 10.6.7 (10J869)

Report Version: 6

Interval Since Last Report: 3078958 sec

Crashes Since Last Report: 23

Per-App Crashes Since Last Report: 4

Anonymous UUID: 27ECC4B9-1B78-43E1-A6D8-EBC35A65899C

Exception Type: EXC_BREAKPOINT (SIGTRAP)

Exception Codes: 0x0000000000000002, 0x0000000000000000

Crashed Thread: 0

Dyld Error Message:

Library not loaded: QtGui.framework/Versions/4/QtGui

Referenced from: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend

Reason: image not found

OSX 10.6.7
[Galaxy S II Original Android Development] jastonas:
I am an ubuntu but no dev-skills/knowledge. I would like to be able to use Heimdall. My "skills" go as far as sudo, cat, ls, gedit, apt-get upgrade -y :P

Will we be getting a 1.2.0 for us noobs?

SGSII question. When in recovery mode. How can I reboot? Any way to do via Heimdall GUI?

Made a small (sorry for small) donation. Work appreciated.
[Galaxy S II Original Android Development] infinityz:
Please ignore the post, I've found the solution here
[Galaxy S II Original Android Development] Benjamin Dobell:
Glad to hear it works. Did it say it failed to end the session like the other times though or was it 100% perfect? Sorry for all the questions!

Thanks for that. I guess something has changed in regards to the way flashing sessions are meant to be ended. If the session ended properly when you flashed maybe it's just a case of not starting a session at all unless you're actually uploading files to the device.

Thanks for the donation, it's very much appreciated! In regards to getting a capture. If you're running Windows 7 I believe USB capturing is built in, however it's probably easiest to use an evaluation of USBlyzer. Don't stress too much as I'll probably be too busy to look at it in detail for the next few weeks :(

Oops, yeah I forgot to update the udev rules to include the Galaxy S II and the Verizon Droid Charge, similar mistake to forgetting to update the OS X kext :o
[Galaxy S II Original Android Development] Benjamin Dobell:
When I get a chance I'll be releasing an updated Frontend. Unfortunately that may not be for a few weeks. However flashing the kernel, and perhaps a few other files, with the current Frontend (1.1.1) and the 1.2.0 Heimdall command line binary should work fine.

Heimdall only interacts with your device in download mode. If you're booted up normally or in recovery mode then you'll have to do it by hand or perhaps by using adb.

After a flash (in download mode) Heimdall is supposed to reboot the device (unless --no-reboot is specified) however that happens after the end session packet. If the end session packet gives an error then you'll have to reboot by hand.

Thank you very much!
[Galaxy S II Original Android Development] jps1974:
Hi Benjamin,

No problem - I can see how it is difficult to support a device you do not own :o)

After the actual uploading I didn't get any errors about ending the session - unfortunately I forgot to save the log, sorry about that :(

I actually reflashed my device using Odin because I was unable to install anything from the market after flashing with heimdall. Also, my sdcard was formatted somehow, but I have no idea whether heimdall or Samsung recovery (factory reset) is responsible. No big deal anyway as I had a backup, but I don't remember my Galaxy S 1's sdcard ever being touched by a factory reset.

Unfortunately I don't have the time right now to go though all this again, but I will when I get a chance if nobody else does. Then I will also try to capture the Odin flash using USBlyzer.
[Galaxy S II Original Android Development] Hrti:
Looking forward to the 1.2.0 frontend version so that I can remove my bootcamp partition :D
[Galaxy S II Original Android Development] The Compiler:
How exactly would I flash a PDA file with that? It doesn't have --pda in the help, and I don't really want to guess ;)

Flo
[Galaxy S II Original Android Development] jps1974:
You have to extract the .tar file, inside you will find different things like factoryfs.img, modem.bin, zImage (which is the kernel) etc. Which file is for which option is pretty self explanatory - except maybe kernel (zImage) and secondary bootloader (Sbl.bin). If in doubt, ask here or see if you can find the answer over in the original thread for Galaxy S :-)
[Galaxy S II Original Android Development] lukemo:
Help please! I have a macbook pro and osx 10.6.7. I installed heimdall 1.2.0 and I receive the "Failed to detect compatible device error" in download mode...any hint?

Thanks in advance
[Galaxy S II Original Android Development] The Compiler:
Hell, didn't even think about extracting it. :D Thanks, worked perfectly fine.
[Galaxy S II Original Android Development] Boal:
Finally, I got my 10 required posts. PITA.

Anyway: I have the same issue. kextstat shows no sign of the required kext. Is that the case for you, too?
[Galaxy S II Original Android Development] tomhoward:
How do you flash the .img files? Afaik it wants the factoryfs file in fs format.
[Galaxy S II Original Android Development] Benjamin Dobell:
.img format is used for Galaxy S II (Ext4) and .rfs is used for the original Galaxy S range. You don't need to do anything special to make it work, the secondary bootloader knows what to do for your particular device.
[Galaxy S II Original Android Development] tomhoward:
Cheers, will give the Lightning rom another go later then, I flashed the factoryfs.img and the phone locked up just before the boot animation, figured I had flashed it wrong.
[Galaxy S II Original Android Development] swatsbiz:
I had to flash from Windows with Odin, as it got to 21% upload and then threw up this error:

Exactly the same file worked perfectly with Odin ... any idea why?
[Galaxy S II Original Android Development] Benjamin Dobell:
That's the first report I've seen of this error on the Galaxy S II. However, Galaxy Tab users have reported this error with hidden.rfs and movinand.mst. I still haven't confirmed the exact reason as to why these files fail as I don't own a Galaxy Tab. However I have reason to suspect these files use slightly different file transfer syntax. For instance, Heimdall has to handle modem files slightly differently than other files as the syntax is slightly different when transferring a modem.

You don't happen to know which partition it was that failed to flash do you?
[Galaxy S II Original Android Development] swatsbiz:
I just tried to flash the updated CF-Root, here's the output:

Does that help any?

EDIT: Using the frontend I managed to flash the zimage for CF-Root successfully, so maybe I'm doing something wrong on the command line?
[Galaxy S II Original Android Development] atinm:
What command line did you use - that would help.
[Galaxy S II Original Android Development] swatsbiz:
Sorry:

Cheers!
[Galaxy S II Original Android Development] elban:
Are you sure? You seem to be flashing an md5 instead of the real tar
[Galaxy S II Original Android Development] jps1974:
I'm pretty sure what you're trying to flash is a --kernel, not a --factoryfs :-)
[Galaxy S II Original Android Development] swatsbiz:
That'll explain why the kernel wouldn't flash, but not why the factoryfs uploaded 21% then failed
[Galaxy S II Original Android Development] urbanomad:
Yes, the same for me. kextstat shows no sign of the kext for me either although it's "installed" /System/Library/Extensions but I had two /Extensions folders, the 2nd with the heimdall info.plist... I'm restarting now

kextstat still shows no heimdall kext... and naturally still says "Failed to detect compatible device" error
[Galaxy S II Original Android Development] Xero Xenith:
Many thanks, works perfectly :)

I did these, one after the other, Lite'ning 1.3 with a full wipe.

sudo heimdall flash --factoryfs factoryfs.img
sudo heimdall flash --kernel zImage

No problems on my UK SGS2, used Ubuntu 11.04 64-bit for flashing :)
[Galaxy S II Original Android Development] Benjamin Dobell:
swatsbiz, don't flash tar archives, extract the contents and flash them.

Sorry, what do you mean by two Extensions folders? What is the full path of the two folders?
[Galaxy S II Original Android Development] infinityz:
Hi, someone have tried these command line on a MAC?
[Galaxy S II Original Android Development] urbanomad:
I know, it sounds crazy but there were two Extensions folders... I deleted the 2nd one which looks like it was installed with the Heimdall 1.1.1 installer, as it was an earlier date. I kept the

/System/Library/Extensions/heimdall.kext/Contents/Info.plist

I restarted after having deleted the "extra" Extensions folder and ran kextstat again and there's no heimdall.kext showing... The current Info.plist I have is dated 01.06.11.
[Galaxy S II Original Android Development] Benjamin Dobell:
Do you remember where the Extensions folder you deleted was located?