yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] celtichazard:
Man this suck I hve the same proble and waiting for a Jtag for repair the boot

be pattient. :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] kgk888:
Maybe you should just ease off the pedal.

/hunormus....definitely re-using that at some point
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
what is Jtag ? i will go on monday at service because in weekend u can't find operators or services open

maybe i will get a nice service guy that will say oh doesn't start (battery empty ) doesn't charge , here is another one :)

nothing works, only AT7T logo

i did not get your post

you don't have these option very often in this country... i know only one person that has these type of insurance...
[Galaxy S I9000 Q&A, Help & Troubleshooting] Amz95:
Well there is a way of getting your phone working by putting a file on your sd card but you'd have to look for that .
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
can u give a link or more details pls
[Galaxy S I9000 Q&A, Help & Troubleshooting] Nesousx:
Actually, you should try it... I've been told that flashing Intel boards with AMD firmwares allows unlimited overclocking! or not.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Mynx:
Rude ? He is right ^^

There is no easy way to tell someone he is a moron^^
[Galaxy S I9000 Q&A, Help & Troubleshooting] Darkstriker:
I'm sorry for that. It's a little bit of frustration speaking there. But I guess you have a way bigger problem. Although that post about putting the right file on the SD seems interesting (but I haven't heard of anything like that before).

But if you can, returning the phone and hoping that samsung will fix it will be the easiest fix.
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
im sure samsung can fix it :D evan by changing the sd in the phone with the correct soft will solve it, but i want to see if there is another way of doing it
[Galaxy S I9000 Q&A, Help & Troubleshooting] MomijiTMO:
Hey OP,

Don't beat yourself up. Even if you've flashed things a billion times, you could stuff up. Most of us work during the day so all of our phone tinkering is done in the night. I tend to make mistakes when I'm tired.

Check out this guy's funny story.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ice3186:
wow this is incredible

Okay so i have yet to see anyone actually try and help this guy other than tell him that is phone is screwed and he should just roll over! i havent been around here long but that just isnt right on XDA i mean seriously "samsung can fix it"?????????

Anyway, i have a Captivate running that same rom and samset 1.9 its a beautiful thing. So here are my questions to the OP.

1.)When you plug in the phone to your computer as it boots up do you hear the classic "i just connected a new device to windows sound" or not?

2.) If so does your adb command still work?

3.) have you simply tried pulling the battery and then putting it back in. hold the down volume button first and then hold the power button and down volume button together. It is the key combo that puts my phone into download mode super quick.

----i can almost promise your phone is not bricked due to the fact taht i have flashed this rom and then a vibrant rom on top of that and then a vibrant vanilla rom and then a froyo and then back to captivate stock(all with some scares in there)

4.) Just let me know what you phone is doing, i got the fact that it wont boot past ATT but let me know if any of the things above work. I hope your phone stops freaking out.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Benjamin Dobell:
If the phone can't get into download mode then it's simple, it's broken and needs to be repaired/replaced by Samsung. The only other option is to hook up JTAG and fix it manually but I don't know if anyone has even done that and the OP clearly doesn't have the knowledge of how to do this.

Now I'm not saying that he should give up trying to get into download mode, but if he has tried all the options there's little else he can do.

The very first response to this thread was myself suggesting exactly that.

All you're doing is providing possibly false hope. We don't know what the problem is so it's totally incorrect to assume that it can easily be fixed. I can assure you, first hand, that phones can get bricked to the point that they won't turn on or charge.

Rather than screwing around with the phone more it's perfectly reasonable advice to suggest sending the phone back to Samsung, to the people who actually know how to repair the phone.
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
the phone is not charging or anything. The usb doesn't respond in any way, and tryed all thing to get in download mode. But if the usb is not working any more, not charging no nothing there is little hope ...
[Galaxy S I9000 Q&A, Help & Troubleshooting] celtichazard:
The phone stll charge I wait until the on off withe screen discharge the battery and I say discarge because the phone don't turn on any more.

Then I charge arroun 4 hours the phone not display nothing but the battery turns warm/hot

And my phone turn on again on the withe screen
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
i am off to the service, fingers crossed...
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
not sure if this is too late

but if you have NOT send it out for service repair yet, try the 3 button mode

the AT&T uses a different 3 button mode than the International i9000

Captive/Fascinate uses Volume up + Voluem down + Power
[Galaxy S I9000 Q&A, Help & Troubleshooting] celtichazard:
dont work dude
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
i tried anything there is. the only fix is by samsung. I saw another i9000 user on another topic that went in service and they said that will not fix it and the only fix is to change the motherboard....so i hope they will not give me same answer, because they can order just a new sd card with the correct flash...
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
ok, news update, the first authorize service said i have to change the mother board, now i took it to samsung service, i explained what happened and they said it's repairable so i wait for good news.
[Galaxy S I9000 Q&A, Help & Troubleshooting] FadeFx:
so you told em you flashed a bad rom? if so, you probably get it repeired but you have to pay for it...
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
they already canceled guaranty, ill pay, but not for a new motherboard
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
ok so i got the final answer, the BUS is gone and they can't write it, so i ordered new mother board, 150 e or something like that and my phone will be fixed in one week. So all of u who are in the same situation, for the moment there isn't another fix.
[Galaxy S I9000 Q&A, Help & Troubleshooting] MC Mate:
fiex my phone, 140 euro mother board, and it's back :D so for any of you that have done the same mistake the only fix is the new mother board.
[Nexus One Q&A, Help & Troubleshooting] xManMythLegend:
Just recently started using GV for my voicemails (TMO)

Loved it...

My problem is that I only use my GV number for specific functions/people.

If I missed an incoming call it was easy to tell if the person was calling my cel or my GV. But with GV as my VM service I cant differentiate.

All my calls now appear in the GV app. Is there anyway to figure out which number the person is trying to reach while still using GV as my VM ?
[Nexus One Q&A, Help & Troubleshooting] XSafire:
No, and why should it? As long as they're contacting you, why does it matter which number they're dialing?
[Nexus One Q&A, Help & Troubleshooting] Blueman101:
What you cold do (just speculation) is have a forwarding app that separates via contacts, if XYZ contact calls you then it conditional forwards it to your GV voicemail other wise if ABC contact calls then it routes you to your default VM. Im not sure there is an app to do this but i cant imainge there not being a call forwarding app.
[Nexus One Q&A, Help & Troubleshooting] xManMythLegend:
Then why have 2 numbers since theyre just dialing me anyways ?:rolleyes:

Some people I will pick up for others I will send to VM. Id like to know who the new number is trying to reach my "work" persona or my "home" persona.:eek:

Ill look into call forwarding.

This would be moot if Tmo visual voicemail worked over wifi or GV had the same bubble for incoming as it does for outgoing.
[Android Software Development] yanivgal123:
I started to develope an application.

When I wanted to close the application I clicked on the home screen,

but the app is still playing in the background.

Than I tried to click on the "back" key, but nothing happend, so I've

created a key event listener for the 'back" key, and inside that

method I wrote finish();

Now my app is closing but I think it's still running in the

background, because when I go to "manage applications" I can still see

it in the "running" tab, and if I press it, I see I can click on the

"force close" to actually close the app.

What do I need to do in order to really close the app without leaving

it open (one way or another)?

Thanks, Yaniv
[Android Software Development] [funcoder]:
You does not need a Exit Button, because Android will close things up as needed.

Perhaps you should read this: click

Otherwise you can exit your app with System.exit(0) at the end of your

onDestroy() methode.
[Android Software Development] yanivgal123:
Yes, I do know that Android is closing unused apps, but I do want to put also an exit option.

And thanks, the System.exit(0) worked for me :)
[Android Software Development] bitbang3r:
How does that compare to having an Activity-extending class call finish() from the main UI thread?

Actually... now that I think about it... if you're going to call it, do you have to call finish() as the last thing you do before returning from onResume(), etc? Or is it literally a black void from which the calling thread is guaranteed to never return? If you look at the Javadocs, they merely say that calling it indicates that the Activity should be closed, with the result propagated back to the parent (if any).

I've gotten burned by Java enough times over the past 10 years to know it's dangerous to read more into Javadocs than they literally say, regardless of how commonsense and reasonable it might seem. Going by the Javadocs' literal wording, it would be perfectly reasonable for a call to finish() to simply mark the Activity as eligible for aggressive closure and recovery... then return from the call and have a trainwreck after it executes code in the following finally{} block, or between the point where you called finish() and the return from the end of the current method. It would be outrageous, make lots of developers mad, and cause huge problems... but technically not inconceivable... which is why traditionally, I end up following every call to finish() with throw new RuntimeException("WTF?!?");, just to be safe and guarantee that execution will never, ever continue beyond that point. :o
[Vibrant Q&A, Help & Troubleshooting] Okeynwachie:
btw: super noob here

ok so i am getting this error and i dont know why

i rooted my phone and when i tried to upgrade to 2.2 (using odin) i got this:

E:Can't mount /dev/block/mmcblk0p1

(Invalid argument)

E:copy_dbdata_media:Can't mount SDCARD:

it takes me to recovery mode and just stays there with 5 options (reboot, apply sd card: update.zip, wipe data/fact. reset, wipe cache, format internal sd).

the worst part is that i found out (after research, as thus i could be wrong) that i must have somehow gotten euro firmware because my up key moves down in recovery mode and my power key isnt the "ok" key used to select anything in this damn menu!!!

ive only rooted my phone...and i got the regular update.zip (saved to internal like instructed) like everyone else (i think) + tethering and set cpu (saved zip to my external sd card)

so....i cant exit recovery mode, i cant even select any of those 5 options

i can turn off my phone, but it immediately goes back to the recovery page with the error

please please please help

mom bought me this for my birthday like 3 days ago and the walkthrough seemed easy!

i will pay and bring my phone to you if you can fix it lol
[Vibrant Q&A, Help & Troubleshooting] dglowen23:
what you should do is boot into download mode and flash the stock rom.. it will unroot u but its better then not havin a fone to root at all right?

if u have troubles booting into download mode try holding down the up and down volume keys while the fones off then plug the usb cord into ur fone it shood bring u to the download mode screen.. but make sure u hold the volume buttons down before u plug it in
[Vibrant Q&A, Help & Troubleshooting] Okeynwachie:
thanks....i would really really appreciate it if you told me how exactly to flash a stock file (put it in the odin thingie? PDA, MODEM, or CSC? is this the right file: T959UVJFD.tar? please let me know
[Vibrant Q&A, Help & Troubleshooting] jdkackley:
There is a walkthrough on this site on how to use odin to flash back to stock. I believe you have the right file there. But you will probably have to flash the pit file as well. I would just to be safe. This will set everything back to stock. Odin can be picky, and make you want to cry. But relax, your still ok. You can get into recovery mode, so you should be able to access download mode. Do a little reading on the site. You should be able to find the links to odin. If you can't, pm me, I will help. I've used odin before, and even though this is scary right now, you need to stay calm. Panicking isn't goin to help. I am new on the site so I can't post links. If you can't find them, contact me, I will e-mail them to you or some thing. Good luck!
[Vibrant Q&A, Help & Troubleshooting] jordanjf86:
Did you get it figured out yet? ODIN should fix you up. Flash the stock build here http://xdaforums.com/showthread.php?t=739091 just download this, unzip it and load the pit file into the pit field and the larger file in the pda field in odin. Make sure to have this loaded into odin before plugging your phone in or it might not work. To get into download mode just power off your device and hold volume up and down then plug in your usb cable.
[Vibrant Q&A, Help & Troubleshooting] rpcameron:
If I remember correctly, /dev/block/mmcblk refers to your SD cards. mmcblk0 is the internal (16GB) SD card, and mmcblk1 is whatever extra microSD card you have installed. /dev/block/mmcblk0p1 is the first partition on your internal SD card.

What most likely happened is you messed up your Odin installation, and probably chose to "reformat partitions" when you flashed, wiping your internal card, and thus essentially making your phone unbootable in its current state.

Why you needed Odin to root is beyond me, yet so is why someone would do something that could cause irreparable harm to their device do so without understanding what they were doing. If you are going to ignore the warnings attached to flashing unsupported ROMs (such as flashing an unreleased testing ROM onto a completely different device than it was intended), then you ought to at least understand what it is that you are actually doing.

Also, what does this have to do with development? Aren't there similar posts in the Q&A forum about people who have done the same thing?
[Vibrant Q&A, Help & Troubleshooting] Shulo:
that´s SD problem 100% sure. yesterday i had this problem and solved with a newone SD card. (older was 512Mb and not working, newone is 1gb and all was ok)
[Vibrant Q&A, Help & Troubleshooting] Chalup:
Were you trying to use Eugene's files? If so you need to follow the directions in his thread.
[Vibrant Q&A, Help & Troubleshooting] BaaGi:
I got a same problem. As you said I tried start download mode. But the Android system recovery <3e> page still appearing. Firstly battery picture appear and then system recovery. Is there another way to boot into download mode?
[Vibrant Q&A, Help & Troubleshooting] Slow50:
There is the three button mode, vol up and down plus power, or if you plan to flash alot of rom's, get a jig. there is adb. also aio tools.

one of these should get you into dl mode to odin.
[Vibrant Q&A, Help & Troubleshooting] oka1:
you are in recovery mode if it says "2E" or "3E" recovery you should be able to get into download mode and then you can flash back into stock.

To get to download mode plug in you usb into the computer first. then, hold the volume keys both down then plug into the phone (while it is showing the recovery mode, in other words it is still on) if it does not work, then pull out then try again a couple of times When you plug it in leave for 2-3 secs. If this does not work or you can't get it Then, just buy a Jig from the xda member connextion2005 (mobilevideotech.com I think). they are 8 bucks and all you do in just plug it in and it will bring up the download mode. From there you can do this

Get the Odin program 1.7 or newer, get the Stock 2.1 Tar file, get the 512pit file

You can find these in the general forum in the thread called Noob guide

then

Open Odin, plug in your phone, put into download mode. connect it to the computer it will recognize might say com8 or some other number

Load the PIT file into the appropriate area and the .tar in the PDA area.

You want to check the 're-partition' box.

Now click start, let it finish, and this time your phone will load up just fine!

Then, root the phone and you can flash your new Rom.

You the super oneclick method it is easier to root then download Rom manager and now you can flash any rom you want
[Vibrant Q&A, Help & Troubleshooting] Oryon007:
Still can't mount internal SD

I've tried the above steps and was able to get out of Recovery Mode, but now I can't get the Internal SD to mount to allow me to put custom ROMs on there...any ideas??

Oryon007
[Max 4G] cmor:
Hi, this is my first post so please bear with me if I break any rules :)

I have found what I think is a clone of the Max 4G, it's dual sim so that kind of gives it away! Has anyone had any experience of these clones?
[Max 4G] j2l84u:
what is the max 4g? is it a new hd touch?
[Max 4G] basilbasil:
it's a hd+ wimax
[Max 4G] keeper18:
Yota Max 4G

Hi.

Can anybody help with hardspl with this phone?

ROM VERSION: 04.001.1 CHS

ROM DATE: 2010.08.18

RADIO VERSION: 4.16.2010

PROTOCOL VERSION BASE_W09.20_P4

CPU SAMSUNG S5PC100

I try almost everything different usb cables, computers, hardspl-s version and instructions from RUU and 4pda:( I have error number 260 ,240, 202 etc...

Only using ELFIN_HSPL_3.10 I have massage on PDA screen:

Welcome to HARET

VRAM ADDR: 0XA1300000

Creatining preloader 1:1 mapping

preloader is at0xad256000

jumping to system mode

loading spl to ram

loaded

jumping to preloader

praying........

Message is on black screen with linux logo.

THX for all sugestions.
[myTouch 3G, Magic General] lukeharley:
which is the best way of rooting the htc magic and which is the best rom to then use?
[myTouch 3G, Magic General] WoblyGoblin:
MAny pepole use cyanogen mod.
[myTouch 3G, Magic General] DonJuan692006:
Cyanogenmod in my opinion makes some of the best ROMs but it all about preference. As for rooting, boot into fastboot by turning the phone off and then back on holding the back button+power and post that info here.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] pocket_pc:
Hi guys

could any one please be so kind as to help me with a problem im having.

i have a spv m5000 on orange which i have change the mother board over with a o2 exec mother board running windows mobile 6.1 seems to be working fine no issues however i have tried to pair both my gps units with it but to no avail, i have a Holox BT-541 and a navicore BT-GPS-32354D i have tried both of them and have same problem,

my xda see's them and adds them fine but when i try to connect to one in the xda it says unable to connect or wrong passkey i have used 0000 for holox which thats what it says in the holox pdf but have also tried 1234 but i think this is a com port problem i have tried all com ports some will go in ok but still cant connect to gps i also tried this "go into TomTom and use the NMEA devices with baud rate of 38400" this did not work, before i changed mother board i had these working fine on older tomtom and original spv m5000 mother board so i dont know if this is a win mobile 6.1 problem or not i see quite a few people with same problem but no solution that worked for me any way.

i have seen thred taking about pairing before tomtom installation but not sure that will fix my issue as i think i tried to pair before i installed any way.

has any one any ideas on this any help would be really appreciated this is getting to be a pain in the rear!.

also there is an icon in the system tab "external gps" can any one tell me the correct settings in there ie for program tab and hardware tab what com port and baud rate should be and whether the manage gps auto should be ticked

many Thanks in avance for any help you can give here.

Kind regards

Daz
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] pocket_pc:
Ok found solution,

after spending way too much time on this crap! I finally found the issue as I stated I thought

it was a mobile 6.1 issue and I was right, in mobile 6.1 they have added a external GPS shortcut

in system tab it is here the problem exists.

my problem was resolved by the following procedure.

On your XDA go to Start/Settings/Connections click on Bluetooth short then add new device once it has found it

enter passkey 0000 or whatever yours is once it has made the first connection then do the following,

1. Under "device tab" click on your unit and make sure the serial port is "UNCHECKED" disabled then click save.

2. Under "Mode tab" make sure (Turn on blue tooth) and (Make this device visible to other devices) are "CHECKED" enable them.

3. Under "COM ports" select a port, I chose 0 don't think it matters but if so chose another but remember what one you choose.

4. Under "Security tab" Authentication (passkey) required "CHECK" enable it click ok to come out of Bluetooth.

5. Under "System tab" click on "External GPS short cut.

6 Under "Programs tab" select (None) for GPS program port.

7. Under "Hardware tab" select port 0 or same as you gave your Bluetooth com port and issue the "Baud rate" 115200 or lower rate.

8. Under "Access tab" Manage GPS automatically (recommended) "CHECK" enable

9. Finally check your xda is blinking a blue light and turn on your tom-tom software it should now pick it up, all done.

Final note it seems that Microsoft have made one more buggy operating system, no change there then LOL

and as a result you can't seem to use the blue tooth pairing process as intended so this is a working work around

one more thing there is a 2nd bug found and that is when you turn off your GPS unit and try to use your xda you might

find that your last page froze up here you will have to mess around with it i.e. try turning off your tom-tom software first

and then your GPS, Thanks to bill gates for yet another windows operating system that doesn't work as advertised.

Well we had Hendrix king of rock, Marley king of reggae, Elvis king of rock'n'role then there's you bill gates king of crap!

Long live the king!!!!! LOVL

A big thank you goes' out markanthonypr on xda-developers for pointing this out, nice one m8

http://xdaforums.com/archive/index.php/t-476940.html

hope this comes in handy for others "knowledge is the real king give it freely"

regards to all

Muzz