Database Develop

[Q] help please! stuck on at&t world phone screen

okay im getting completely frantic right now, i tried to flash the newest cognition ROM from stock 2.1 rooted from recover and it all loaded fine but i kept getting force closes com.android.phone or something and then i was like okay ill just restore my last backup and did that but now it wont boot past the at&t world phone screen and i cant get into recovery. ive read other threads about this but theyre all different situations so i wanted help for my specific situation. i love all the devs help and hard work on this site and i hope my phone is not bricked because ive only had it for about 2 weeks. so please a fast response would be appreciated, i would like to have my phone fixed by tonight thanks in advance guys oh and also i am able to get into download mode i just dont know what that does.

no one knows?

nevermind everyone i got it using odin

Just reflash use this http://forum.xda-developers.com/showthread.php?t=818439 or you can search for odin one click by DG.

Odin. You will be fine. Just search and read. Be careful what you do and try your best to understand what you are doing before you panic.
You were getting fc on cog so instead of reading and re -flashing you panicked then flashed a 2. 1 back up over 2. 2 with voodoo lagfix active. :O it is not the end of the world. I do hope you have a PC and not a MAC. Odin will flash you back to stock but you will need to search and read. Good luck
Captivate
Cog 2.2

I think I'm in a similar boat... tried to flash back to JH7 after getting tired of froyo versions that I didn't like. Now I'm stuck at the AT&T screen and nothing works... no matter what button I hold while I power the phone on, I get nothing. Any advice?
Update: I think I may have something here... found a guide talking about JTAG stuff that suggested holding both volume buttons while plugging in the USB cable... seems to have gotten me to the "downloading..." screen. That's a plus.

[Q] Black screen glowing button

Phone was flashed to 2.2, however after shutting down the phone and booting it up again, I get Black SCREEN + glowing buttons.
Device : Samsung i9000 from Bell running flashed 2.2 Rom.
I've tried following this guide :
STAGE 1 (applies only if you are coming from an earlier Froyo build)
* We are now going to flash the XWJM8 firmware again (Éclair), so make sure that you load the files for this firmware in Odin.
* In PIT, load the 502.PIT file
* For PDA, select the ‘CODE_I9000XWJM8.tar.md5’ file and for PHONE, select the ‘MODEM_I9000XXJM4.tar.md5’ file. Leave all others blank.
* Make sure that the Re-partition box is checked. All other settings should be as shown in the screenshot below.
*Sorry can't post link, forum restriction*
After stage 1, Odin says Passed, my i9000 reboots with still a black screen+ glowing buttons.
I want to start Stage 2, however I can't find the file ‘JPO_JPO_U_JPP.tar’ file.
I've looked up for solution for the last 2 days and can't seem to find a solution anywhere.
Things I've tried on my own without sucess :
Flashed again this time with a CSC from bell, I've read that sometimes without CSC flashing can't be done, but even with the CSC files, my phone is still ''bricked''
Anyone have any idea how to fix this? Ultimately, I want to go back on 2.2 but for now, I just want my phone to boot again =(.

Hate to say it but it sounds like yout internal sd card is dead like MANY OTHERS who have flashed... No way to fix except to send for repairs to bell/samsung...
Sent from my GT-I9000M using XDA App

I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.

Isn't there a way to try and access internal sd card?

Have you try doing a factory reset?

Yeah, I've tried doing so, after reading and researching online, I think this could fix my problem.
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
see reply #7
However adb doesn't even reconize the phone =/

terranq said:
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Click to expand...
Click to collapse
I diddnt specifically mean that it was the flashing that did it but it is OBVIOUS that it happened after he flashed right???
It is known that flashing will sometimes "speed up" the death of an already faulty sd card and that is what I meant by my original post...
And PS... The number of people reporting their sd cards failing on stock firmware w/ no lagfix or no previous flashes to "unofficial firmware" is WAY lower than those reporting sd card death after flashing or adding lagfixes, etc...

Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing

terranq said:
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
Click to expand...
Click to collapse
And again... I did not specifically state that it was the "flashing" that killed the OP's phone. I simply stated that this seems to happen to MANY people after they flash. NOT the same thing...
Did you come to this thread to argue or to help the OP? I simply posted a reply last night stating that it seems his internal SD card is dead so that he could prepare himself for having to send it away for repairs. I did not respond to the OP to get into an arguement with anyone over "what causes the internal SD cards to fail".

Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.

cuem said:
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
Click to expand...
Click to collapse
@cuem,
Unfortunately... If it is an actual dead internal sd card (which it seems to be since the steps you followed already did not seem to fix the issue) the only way to fix it is to send it back to Bell who in turn will send it off for warranty repair.
IF you have just purchased the phone within the last 30 days (possibly 60 if Bell is still extending the DOA return policy) and you have a receipt you can take it back to Bell and get an exchange.
Again, unfortunately these are your only options to get this fixed...
Sorry to be the bearrer of bad news...

Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......

cuem said:
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
Click to expand...
Click to collapse
Ooooooo... That is not good. The American Vibrant is NOT the same as out i9000 models.
What you need to do now is search the forums for the homemade jig thread that will force your device into download mode. Search the forums and you will find it.
Be prepared to be "handy" as you will have to build the jig from scratch...
Sent from my GT-I9000M using XDA App

Yeah, I've read about the Jig thing, I've also read about heating your phone with a hairdryer,
I'm currently trying out the hairdryer, but it doesn't work =/
Might have to try the Jig thing, which seems a little complicated with ordering since I'm running out of time =/

Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.

This has happened to me, I just flashed with an older version, for me JM5 worked fine.

cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
I had the same thing after flash and spent many hours and tried many different methods to get it back up with no success.
I'm leaving the country for Europe on January 2nd for vacation. This was the last thing I needed... Hopefully I get it back before then, but I'm not holding my breath.

cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
Well... At the very least at least the firmware is now correct so you can send it away for repair if you need to...
Sent from my GT-I9000M using XDA App

I followed this guide
http://www.tunandroid.com/content/i...du-firmware-i9000xwjpa-pour-samsung-galaxy-s/
I believe now oneclicklagfix is installed on my device, can I flash again or that'll brick my phone, how do I uninstall oneclicklagfix if I can't boot up the phone but only acesss clockwork mod menu?

[Q] Bell i9000m Official 2.2 Froyo Upgrade Question(s)

So apparently the official 2.2 Froyo is rolling out. I haven't checked yet but I will when I get home. I have some newb questions.
I got my phone and haven't touched a thing to it. Just added lots of apps. No root. No lag fix. Nothing.
My question is, if I upgrade this officially via Kies:
1) Do I lose my contacts / stuff ?
2) Do I lose my apps ?
I heard people saying that once you upgrade to do a hard reset of the phone -- why ? What happens if you don't ?
With this in mind, how and what is the best way to back up all my apps ? I haven't rooted but i DO have Titanium Back up. Would Z4root work for i9000m ? can anyone confirm ?

Funkadelick said:
So apparently the official 2.2 Froyo is rolling out. I haven't checked yet but I will when I get home. I have some newb questions.
I got my phone and haven't touched a thing to it. Just added lots of apps. No root. No lag fix. Nothing.
My question is, if I upgrade this officially via Kies:
1) Do I lose my contacts / stuff ?
2) Do I lose my apps ?
I heard people saying that once you upgrade to do a hard reset of the phone -- why ? What happens if you don't ?
With this in mind, how and what is the best way to back up all my apps ? I haven't rooted but i DO have Titanium Back up. Would Z4root work for i9000m ? can anyone confirm ?
Click to expand...
Click to collapse
1) no
2) no
3) hard resets are only if you experience a ton of lag while operating the phone
4) z4 does not work on jk4

BlackDino said:
1) no
2) no
3) hard resets are only if you experience a ton of lag while operating the phone
4) z4 does not work on jk4
Click to expand...
Click to collapse
how do you root jk4 then ? 2.1 eclair on bell i9000m

1. Phone is currently rooted. Do I have to unroot it before applying the firmware upgrade from Kies?
2. Do I have to perform a factory reset before applying the firmware upgrade?

Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.

rajesh26e4u said:
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
Click to expand...
Click to collapse
A lot of people have been complaining that their SD cards have been screwed. Luckily mine went through without any problems and hasn't given me any trouble so far.
Froyo is insane tho, before the phone used to lag a bit, now the moment i touch it it opens. No need for lag fix in my opinion, everything works blazing fast as is.
One thing to watch out for is the WIFI. It was working normally at the beginning but after 3 hours it just disconnected for no apparent reason and has trouble connecting back.
Good luck

rajesh26e4u said:
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
Click to expand...
Click to collapse
Don't panic yet...
Try this
Volume UP/Power/Home(middle button)
Factory reset/Wipe

urfase said:
1. Phone is currently rooted. Do I have to unroot it before applying the firmware upgrade from Kies?
2. Do I have to perform a factory reset before applying the firmware upgrade?
Click to expand...
Click to collapse
1. NO
2. Good idea to factory reset before and after. Can't hurt and any noncompatible
programs and data will be gone.

Videonut said:
1. NO
2. Good idea to factory reset before and after. Can't hurt and any noncompatible
programs and data will be gone.
Click to expand...
Click to collapse
1) but will it erase root upon upgrading?

bimmerboii said:
1) but will it erase root upon upgrading?
Click to expand...
Click to collapse
Yep, but for optimised result, this is a must do!
You can probably have it work without doing a factory reset, but you can encounter weird behavior, bugs and stuff!
Anyway, you might end up doing it anyway to solve the firts boot issue

I'm one of the users who upgraded to Bell Froyo (from stock FW with root and lagfix - undid the lagfix before upgrading) and then encountered the broken internal SD card issue. I ran Volume UP/Power/Home(middle button) to reformat everything and it is up again. Inside the OS, I ran the internal factory reset again. So far so good. *crossing fingers*

I updated mine last night. However I've had major problems since. Initially it would just freeze up randomly and require removing the battery to get it back up and running.
Today I decide to reset it to defaults which seemed to go fine, although shortly after getting it all setup again, some Samsung app of sorts came up with an error and had to be forcefully closed. Then I was left with a black screen and only the notification bar.
Powered off the phone and went to turn it back on, and now it just loops through the Samsung GT i9000 screen (white writing). Not even the colourful S logo comes up.
I'm able to get it into Download Mode but not Recovery Mode. I'll have to do some reading about this Odin stuff tonight. Hopefully I can revive it, otherwise I guess I'll had to send it in for repairs. No idea if Virgin Mobile repairs will go through Bell or if I take it to them directly.
This is my first Android phone and I've only had it for just over a week. I thought I was making a good decision, but now I see it has quite a defect with the internal SD card failing.

Slow after upgrade
I upgrade my phone last night ( as per bell and Samsung) It is now slower than before. Quadrant Standard has it under 900.
Any ideas how to fix it?

bimmerboii said:
1) but will it erase root upon upgrading?
Click to expand...
Click to collapse
Just use SuperOneClick after you upgrade to Froyo, I've tested and have root on JK4
http://forum.xda-developers.com/showthread.php?t=803682

I have an unlocked phone from Bell that I already upgraded to the international (or European?) JPP/JPO 2.2, what is the best way to downgrade or restore back to default firmware before using Kies to get the official update? Does factory reset restore stock firmware?

I upgraded to official Bell froyo last night ..thn rooted.But how can i Unlock now? i tried using SGS unlock app it says no unlock codes found?? Please help

God damn samsung and bell!
it seems like they're giving defected phones to their costumers!
I have the corrupted sd card too, took it to guarantee now it takes more than 1 month to fix this!
this is f-ing xmas for god's sake. i want my phone

Same problem here!
I do have 2 good samsung galaxy s vibrants from Bell, however when i got the second one i upgraded to Froyo and now i cant unlock it because i cant read the stupid file inside the phone so,
How can i go back to my previous JH2 baseband?
Or
How can i unlock JK4?
I did my unlock on the other Galaxy using the script you donwload from somewhere in this website and then connecting the phone via usb cable with debugging on and mounting sd but with froyo i dont even know where my USB settings went!!!
Thanks for your help, greatly appreciated.

ciudadbonita said:
I do have 2 good samsung galaxy s vibrants from Bell, however when i got the second one i upgraded to Froyo and now i cant unlock it because i cant read the stupid file inside the phone so,
How can i go back to my previous JH2 baseband?
Or
How can i unlock JK4?
I did my unlock on the other Galaxy using the script you donwload from somewhere in this website and then connecting the phone via usb cable with debugging on and mounting sd but with froyo i dont even know where my USB settings went!!!
Thanks for your help, greatly appreciated.
Click to expand...
Click to collapse
Have you found any solution yet?? I am thinkin to flash back orignal samsung firmware using Odin n then unlock..atleast i will be able to use the phone then

Videonut said:
Don't panic yet...
Try this
Volume UP/Power/Home(middle button)
Factory reset/Wipe
Click to expand...
Click to collapse
what if after this, it's still stuck after the s logo boot up?
does this mean i have a broken internal sd?

[Q] Stuck on logo screen suddenly. Ideas?

Hi,
Last night my Galaxy S was low on battery, and I kept trying to turn it on for it to die right away (it was working as expected I guess)
This morning after I charged my phone it wouldn't turn on at all! It loads to the logo screen, makes that jingle sound and then holds and doesn't turn on.
I can get to recovery and download mode.
I put OCLF on like 2 months ago, but haven't modded/flashed ANYTHING since. It is very bizarre how it just died.
I'm wondering what my options are now. Obviously I would rather not loose all my personal files. Since I can get into download mode, can I just flash a new firmware? I'd like FroYo anyway, but I haven't got a clue what to do.
Great start to the year – !
Cheers,
Mitch
EDIT: I just decided to try the "Clear User Cache" option and then reboot to no avail. Now I can't get back into recovery mode!?!? Download mode still works. Huhh?? Is this expected? Have I lose Recovery Mode entirely now? Crap.

seeeems like an odin flash via the download mode is the only way. There are a few tutorials on this site and even tut vids on youtube so you should be fine if you just follow everything they do (as long as it works for them of course)

How do I know what version to flash? I have read a few tutorials and they all have started with "Dial x and check you have y" etc. Obviously I can't do any of that.
What is the *safest* firmware I can flash?
My phone currently has some optus variety.
Please forgive the noodish question.
Mitch

Where are you located? And who is your provider?

Hi,
I'm in Sydney Australia and my provider is Optus.
Thanks

Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You

m1tch37 said:
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
Click to expand...
Click to collapse
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.

Sounds like you'll need to do a flash of a stock rom..
By the way, the old oclf had some issues that might lead to system corruption (unfortunately I'm not very sure exactly what it does, or whether it could lead to this problem). I'd suggest getting one of the newer lag fixes available here when you do get your phone running again

tragusman said:
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Click to expand...
Click to collapse
tragusman has got it right. Depending on what the issue is, you'll either recover nicely or your phone is toast. Flash the above stock firmware and give it a shot. Note that you'll likely loose your data and settings.
If you're new to flashing firmwares, check the great reference guide on where to find Odin and how to use it (this is the app you'll use to flash the above firmware).
http://forum.xda-developers.com/showthread.php?t=723596
After flashing, try getting into recovery mode. If you can look for an error message under the standard menu. Can't get to d/l mode? You're probably in trouble. Get into recovery and see an error msg? Post the error here or google it for a solution. No error msg? You're probably ok - restart the phone.
Good luck.

Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch

m1tch37 said:
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
Click to expand...
Click to collapse
If it's broke, you can't break it any more I've sent phones back in for support after flashing back stock firmware (flashing it after it "died").

Keeps rebooting after Darky 8.1 update

Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.

Zink6 said:
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Click to expand...
Click to collapse
try a re flash of another ROM preferably a stock ROM then start all over again, similar thing happened to me earlier, i am quite new to all this but i dont know if its the kernel or lagfix i had what caused this...
i re flashed back to froyo and then installed darkys ROM then re installed my kernel last.. all is good (for now)

worked for me first time but when i went to sgs tools to upgrade your apps ie gallery, camera, it said no busybox installed but went ahead and done fine in v8.0 and i see that cwm changed from red to green too went to market for busybox to download it but when it goes to install phone just reboots all the time mmmm...

Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.

stepsch said:
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
Click to expand...
Click to collapse
YES !!! i agree, it is a pain.. but we love our phones and we would do anything for them its always best to flash back to standard FW if you ever get a problem...

I myself experienced this. Whenever I installed a new software, it would just boot. I got fed up because darky's forums are also down and there is no discussion. flashed doc's rom. Now everything is fine.

...mh... but it's not caused by Darkys ROM. This cycling boot feature may appear at all ROM, at all lag fix actions and so on. It depends how proper you interact with phone- and ROM-features while configuring. A lil disturbance during your session (by you or battery issue or whatelse) or a not so well prepared basic from where you start and your unlimited-feature-wishlist-and-paint-it-golden-one-click-action is enough to interrupt the whole thing and run into trouble.
It was and is all the same - since DOS or C64. And it will be the same, even when iPhone is on level 12.x or Android will be able to beam you elsewhere thru the barcode scanner.
It's a game. Nothing more. And game means lot of fun - and in the beginning a certain thrill when your phone stuck first time and you are thinking: "... f*ck... bricked..."

yup same for me
cycle boot thing
didnt enable download mode before that....
can get into debug screen thou but wiping it doesnt help
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise

anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
Just tell the warranty guy darky screwed it .
OR
http://forum.xda-developers.com/showthread.php?t=853950
jje

cant even boot the phone mate
so ehm i dont get it....how can odin help me ?
is there any way of getting it into download mode still when it doesnt boot up? i heard about that JIG thing they made themself...isnt that just like the microusb cable that comes with it to the pc? i dont get it sorry if im trippin but im maddd at myself for even trying this lockscreen thing

http://forum.xda-developers.com/showthread.php?t=819551
jje

Thanks guys for all the replies. Now I did try flashing a stock rom but with no results. Was still having the same thing happening to me. If you guys can give me the link to the files you used to solve this problem, that would be great. Also just for your information I have a Bell i9000m unlocked running on fido. And NO its not an sd card failure lol.
As for DarelSteilz85, I did make one of those JIG usb for myself. It easy, just get the micro usb and strip it bare to the point you can see the pins on the usb which usually are connected to the wires and get a resister to connect one pin to another. Now for which pins, I remember it was 4 and 5 that you had to connect through the resistor but double check as I am not sure. Also the resistor has to be a certain level which I forgot so double check that also. Good luck.

http://forum.xda-developers.com/showthread.php?t=853950
What i use for problems .
jje