[Q] Phone cycle before bootloader?! - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi all,
My collegue comes up this morning with his phone which is no more booting.
I'm used with the custom roms stuff and updating using odin and had already saw many posts about Internal SD failure. However the behaviour of his phone is really not as what i red before.
His phone is alway cycling like if the power button were stock, but it is not. Just shows I-9000M then reboot (no "S" or other stuff)
If I try to access recovery mode, it start cycling. If I go to download mode, it works (and not cycles).
So I've used Odin to install Stock Bell JL2 rom (and update the bootloader). It changed nothing.
Also tried to roll back JH2, with pit 512 and repartition, update bootloader. changed nothing!
then re-up JL2... changed nothing!
So he is leading to Bell service center now... but have you ever seen that?
Thanks!

Hey, im stuck with the EXACT same problem. Ive tried everything too. unfortunetly, i don;t have a receipt, so i can't go to bell
Still searching and asking... just hoping. lol.

Related

[Q] I9000T stuck on black screen with Orange Triangle [Help Please]

Hi all,
An unfortunate first post
I just converted from an iPhone to a Galaxy S I9000T (on Telecom New Zealand, 850Mhz) and wanted to get ahead to Android 2.2. After seeing many people doing it I felt pretty confidant
After reading a thread suggesting to go via JM8 to JPM I started down that route. I got to JM8 OK and the phone worked fine (made a call etc).
Then I went on to JPM which is where it all went bad. My network didn't work after this update so I wanted to go back to JM8 which at least worked (it was late at night).
I started the Odin3 flash but it hung. Then I find out that the JPM firmware seems to suffer from having the 3 button issue, not begin able to get to Download or Recovery modes.
When the phone powers on now it immediately goes to an black screen with an Orange Triangle in between phone and computer icons. I had seen that mode previously but was always able to get back to Download mode, but not anymore.
Is there anything I can do, or am I sheepishly visiting Samsung Service?
Thanks in advance,
Andrew
I got that thing too in my sgs and I got rid of it with... guess what.. Hairdryer! I just heated for 15sec from the backside without battery,sim card and microsd. After heatin' battery in and vol-,home+power and vóla! Download mode,ready to reflash! I've learned my lesson.. "read the instruction twice,before applying mod".
just reset the phone with odin
Use odin, put the phone in download mood by pressing vol down power and home button for three seconds, yhou should get to the download screen, plug the phone into the computer,select (Debug En) in odin and then select Phone EFS clear, press start and wait for your phone to reset. do not unplug until it says Pass.
Thanks for the post!
I can't get into Download Mode with the current firmware unfortunately. So, I waiting on a little circuit to arrive so I can try the 301k resister trick
Given my phone is the I9000T model and my carrier Telecom New Zealand (TNZ) use 850Mhz and 2100Mhz WCDMA what is the best combination (and latest Android 2.2) PDA, PHONE, CSC firmware to use?
Thanks a lot!

[Q] Phone stuck in reboot loop.

So my brand new 7 day old vibrant is not working now. yesterday i was surfing the droid store, and looking for new apps, and installed a text editor, afterwards i made a text file. and saved it, that's when things went awry, I got a force close message, so i figured no big deal, i'll just reboot the phone. Well after cycling the power, now all i get is the initial splash screen saying samsung galaxy s gt-i9000m and it blanks out, then continues an endless loop. Only way to stop it is to pull the battery. the 3 button combo for force downloading works, but the 3button combo to get the recovery menu doesnt.
Question is can my phone be fixed? is it possible to recover the data ie pics/videos i had on it? or is it borked and i need to take it to exchange it.
Technical information
Virgin Mobile Canada gt-i9000m
Hardware Revision 10.11
running Froyo from box, jp6 i believe was the version.
any help/insight you can offer would be appriciated.
I hope i didnt get one with a bad internal SD card.
i doubt that the app you downloaded had anything to do with it. I hade the same prob. kept rebooting, 3button download mode works. 3 button recovery mode didnt, you need to call bell and get it sent away basically.
out of curiosity, did you do a big file dump onto your phone prior to the dead phone issue? like put on a ton of music or movies or images?
call bell. good luck. i am still waiting for mine.
haha.. don't worry!
just reflash using Odin. for details check this out...
http://androidspin.com/2010/08/09/h...oidSPIN+|+Your+No.1+source+for+Android+news.)
oh yeah, i forgot to mention i tried that too.no go!
SD card fail. You're done.
Your Internal SD Card has failed like many other Bell Phones. Use the Search option to find for possible solutions.
Try downloading a JH2 which includes SBL and flash it (stock 2.1 for your i9000M). I believe you should also check the "Phone Bootloader Update" in Odin.
http://www.multiupload.com/EZF1IEZ34H
If that doesn't work, call it in to Bell and do me a fav and report this failure in the i9000M hardware fail poll. This is the first 10.11 fail I've seen.
Good luck.
Well after searching all over the forums, and finding some similar situations and methods used to correct them.
I've flashed my phone probably 12 times, today and nomatter whatrevision or options i use with odin, it always hangs, in some cases, I'd get past the gt-i9000m black screen, to the galaxy s splash screen, but not past there, i9000ugjh2 seems to get me the furthest along @ the boot screen.
Anyone looking to reflash to a different version, before returning i suggest using the i9000ugjh2 image since it resets the model number to gt-i9000m which, maybe be changed by some of the other firmwares/roms
anyways back to the store tomorrow, since i got snowed in today.
Good luck to anyone else, I will post information on the new hardware tomorrow, If it's 10.11 again i'll have to try and force a failure. But we'll see what we see.
This guy seemed to have been lucky and got is supposed dead I9000m working again. Here's his procedure:
http://forum.xda-developers.com/showthread.php?t=905975
Worth a shot.
update
I received my new handset yesterday, it's another 10.11
I'm going to be treating it with kid gloves for the next few days while I'm at work.
Once I get home I will again begin taxing/loading the internal memory with a large amount of data to test it's stability.
New phone details,
Virgin mobile canada (AKA Bell canada)
Hardware 10.11
Model GT-I9000M
Firmware 2.2
Baseband version I9000UGJL2
Kernel Version 2.6.32.9 - [email protected] #3
Build number FROYO.UGJL2
As for his guide, My previous phone was unable to enter recovery mode, not until i flashed the nutz outta it.
even then his guide was unable to achieve usable results.
i got the same problem , my Phone stuck in reboot loop . its happen when i use some voodoo apps in the market that change the screen i think.
i brought my phone from malaysia.
my Firmware DXJPE.

[Q] trouble with my Sasktel Galaxy S

I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)
I am also on sasktel and am an impulsive flasher (1-5 times daily) Heres an easy, fast fix. GO here:
http://www.darkyrom.com/community/index.php?threads/guide-installing-rc5-easy.2382/
go to section enabled "For GT-I9000 users only" and follow step by step. You can stop at step 2 if you want to leave your rom stock samsung or do last few steps to have darkys on there. EIther way once done you'll also have to enable the 850 band *#2263# then enable wcdma 850 option. Also you will have to manually enter your APN under network options. I use inet.stm.sk.ca for sasktel. Note that the Ficeto_JVB.zip download there includes all needed to flash (.pit file, rom, odin). THis is always my fail safe method after boot loops ( I always screw something up playing around lol).
ps: also depending how desperate you are and how trusting you are, I work at sasktels head office in the cornwall and if you wish I am sure I could take 15 mins out of my day tomorrow to do this for you, although you will not be able to get through security so you will have to trust me taking off with your phone lol. email me at [email protected] if needed.
trouble is I can't put things on SD card because I can't get it to load android
You won't be able to load eclair through Odin because JL2 installed a new SBL (secondary boot loader). Go to samfirmware.com, download JL2, and use odin to flash that. Once that's flashed it should fix your issues. Then, if you want a custom ROM, try the romkitchen (romkitchen.org).
problem solved!! turns out darkyrom did fix my phone, I couldn't push the zip file to my phone but their tar file got my phone working! Thanks for all the help
Dougustine said:
I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)
Click to expand...
Click to collapse
I loled, I've been in the same boat, wife is always asking me why I always have to mess around with stuff. Shoulda seen her face after I soft bricked the phone the first time.
Just rooted my phone
I am new to this, I can do all kinda of things with my pc but with my phone a different story lol. I don't understand when you say "Eclair". Is that a different model or is that stock. I am too from sasktel.
Android 2.1 is Eclaire, 2.2 is Froyo and 2.3 is Gingerbread... Ice cream is next 4.0
hi guys, I know this is an old post but has anyone successfully unlocked their Sasktel i9000 vibrant without paying any unlock code service? has anyone tried anything like the SGS Unlock Pro that claimed to unlock all GSM galaxy S phones but did not list Sasktel? anyways, from the sound of it is Darky's rom currently the best for i9000's? I wanted to try CM9, so i did the super 1 click root and followed the CM wiki page to push clockwork recovery to the phone through Heimdall Suite but both times i tried failed and stuck in a boot loop so both times i ended up going through Odin to fix it. (super 1 click root didnt seem to stick b/c i lost superuser after fixing the phone w/ Odin, is that normal?)
anyways i had a very unique situation, originally had a Bell i9000m but died 1 week later tried to fix it numerous times for 7-8 months ( i live in U.S., and Sammy refuse to fix it b/c i dont have a canadian address they can send it back to b.s.) anyways finally landed myself a dead i9000m w/ broken screen, so i took both apart and put the working parts together. now 1 working phone with 3 problems: 1) so it seems that it's currently locked to Sasktel (it can be done but i'm curious if there is a cheaper way or even free) 2) CM wiki suggested Heimdall push CW recovery cause boot loop (some on xda suggested flashing the phone back to 2.2 (or 2.1??) first) 3) i was playing around and click on screen update and lose my touch keys ever since (ppl also suggest flashing it back to 2.1 and reupdate the keys, but will a bell i9000m 2.1 stock rom be compatible w/ the i9000m from Sasktel?)
anyways lots of questions there but if anyone can answer anyone of these would be greatly appreciated.
thanks in advance
Update: problem 1 is taken cared of. SGS Unlock Pro worked like a charm. tested, working. other 2 problem still unsolved.

[Q] Telstra Galaxy S brick?

Hello XDA!
So, ive been in contact with someone who downloaded a galaxy S carrier froyo file i was able to nab whilst KIES was busy updating my phone and wasn't looking.
Seems that his phone may be bricked and i'd like to find out if it is and importantly, why.
So, the details are as such:
This telstra SGS was rooted and running darky's. Somehow this setup got messed up. Dont know, was never told.
Download mode was available via a jig, so my supplied files were added to odin. I currently do not know what was selected beyond PDA> telsgsfroyo.tar.md5 (think thats what i called it). As an aside, i flashed this file onto my own phone and had no issues. Also, this
So, i am told that after the flash, recovery ran its usual post odin flash commentary. the phone stayed on the S bootscreen for 5 minutes before the phone went blank. It has not responded to the power button or jig since.
Normally i would say just try 3BR/3BD as the telstra SGS has these in full working order. Also, the froyo and eclair ROMs available for my carrier are not complete firmwares, neglecting dbdata.rfs, boot.bin and sbl.bin (was under the impression the last two being neglected = good?) with a known workaround to deal with the lack of dbdata.rfs in our firmwares.
Unfortunately, and also not yet explained to me, the JIG is being used as both 3 button modes stopped working for him.
So, tldr version:
Can the phone be saved without taking it in for repair?
Was this just an odin hiccup, something ticked that shouldn't have been in odin or are the files i supplied bad. I was a little quick to remove the files from my megaupload account so ill edit this post when the reupload is done. joys of dsl and all
edit: file is on megaupload, /?d=Q9L4YYND

Need some advice with i9000M

Hi guys, I know I need to make this short but I want it to be clear anyway. This is crazy I wanted nothing to do with smartphones 3-4 days ago because all the carriers rip us off with huge bills to get them. But low and behold when my cheap flip phone died after 3 years of loyal daily work a friend of mine offered me his Galaxy S i9000m for a good price. Started playing with the device and having a strong software/computer background started having a lot of fun with all the applications and was amazed with the possibilities (Networking, ipcam whatever) that just kept multiplying until I fell upon applications that needed something called gingerbread... Anyways I can tell you I learned a ****load in 48hours...
So I installed Samsung Kies, it found me the update and put it on for me.. (2.3.3 Gingerbread) then the nightmare started. The phone would boot, and would randomly reboot a random number of times until it could finally stay on and this could last from 2-30 minutes. So I thought, I'll just do a factory reset, to realise that its "STUCK" in 2.3.3 once its updated no going back to 2.1 or 2.2 easily.
Started looking around for ways to downgrade, and EVERY SINGLE LINK redirects to these 'mass download' sites that end up saying the firmwares were taken down for copyright issues. So desperate to find something, I fell upon a multiple CSC FROYO 2.2 firmware for the i9000 and was able to flash that in download mode the phone worked fine, except for me being very curious about the fact that I lost the "M" in my model description...
So started reading this thread(Mostly because I had already realised that with this non i9000m rom I had lost the 3 button DOWNLOAD MODE which i Had before) **** : http://androidforums.com/galaxy-s-a...flashing-darky-v9-gt-i9000m-minimal-risk.html
Got it rooted, got clockwork on, never managed to get the voodoo kernel working had errors in CWM.. so I was ready to give up until my eyes caught the
"*#*#2663#*#*
Then click Touch key FW update"
Which I thought would be neat to try.
NIGHTMARE, now BACK and MENU are dead, I understand that this is because I am running a non i9000m ROM and that updating the firmware rendered them unusable.
I came accross a post : http://forum.xda-developers.com/showthread.php?t=869492
Where this problem is adressed, I pretty much understand everything that should be done to get this back on its feet (right now the phone is still working I can use it at least 75% of its functions work except no back and menu)
Where I need your help : I'm not too sure how to attack this the right way, since I can't get into download mode I understand flashing is now more complicated to accomplish and now that I know that I need a i9000m firmware how can I find that...
Sorry for the long post I know I'm a noob here but I wanted to prove I had done all my homework to get where I'm at now seeking help from you guys!
Thanks a lot
Mat
By the way : Galaxy S GT i9000m currently on a 2.2 i9000 rom, my carrier is BELL. (Canada)
So there's no way of updating to 2.3.3 using Kies?
The only thing I can think of is getting a USB jig from ebay, which makes the i9000 go to download mode instantly. Good luck!
Alright, so I used CHECK FUS, and was able to get the i9000m stock BELL firmware YAY
now the help I need is to flash it correctly and find a way to get past the no download mode problem, would be very appreciated,
thanks guys
No, similar minds Sepharite, I also thought of redoing the Kies method, and then going back again if I needed to but now Samsung Kies says "Your device does not support firmware updates through Kies" Wow.. useful app, a samsung native app can't even detect it's own fricking hardware.
Thanks
UPdate : Was able to restore the 3 button "DOWNLOAD MODE" with a little tutorial online. Now I tried flashing my i9000m with ODIN, it flashed all the way and I get a i9000M logo now but it gets to the splash S logo and keeps rebooting never gets into the actual android setup is there something I did wrong?
In Odin all I put was the "BELL i19000m stock ROM" under PDA and wrote it. The device rebooted after flash but there still seems to be something I haven't done right.
Thanks guys
Please help guys, I know some of you out there have got this stuff nailed down!
Did you flash with a 1 file ROM or a 3 file ROM?
Using the UGKG3 ROM that you can fine here:
http://forum.xda-developers.com/showthread.php?t=1102881
Place the 3 files in their respective places (PDA, PHONE, CSC), for the PIT file, select the 512 pit file that should have come with ODIN, connect the phone, wait for ID:COM to turn yellow, and press Start.
That should get you going again. You may get apps that force close, so you'll need to delete the apps data and then reinstall them.
Hey thanks a lot man ya my flash was a SINGLE FILE, I bricked it yesterday trying to flash a different ROM since I had nothing to lose, I just got it working again on the old 9000 ****ty version that my back and menu keys don't work...
Now for some reason the USB JIG doesn'T work anymore after a couple of uses... could something have been damaged by doing it many times?
And your original roms section they are all unavailable due to copyright did you check the links before sending them?
When you say get the stock roms, I was able to get the UGKG3 file, but what about the versions? When I look at the north american section of the 2.2 version
UGKC1/UGKC1/BMCKC1/Sbl
UGJL2/UGJL2/BMCJL2/Sbl
UGJK3/UGJK3/BMCJK3
which one of the three suits me?
Thanks for your help, and if I get this running and go back and update my touch key firmwares with the right "Vibrant / 9000M" roms I should get them working again?
PS : I'm also very preoccupied by the fact that the USB JIG fix doesn'T seem to pop download mode anymore because this version of the ROM that I have has Download mode not working with the 3 button method. :S I wonder whats going on, but basically if I get your ROMS working the first time It'll fix everything but if it crashes then I lose the galaxy haha
Not sure why the USB jig doesn't work anymore. I have a couple and have only tested them on my phone to make sure they work, but they did not work on a Galaxy S II that I tried it on.
I just checked and the download link for the UGKG3 ROM at multiupload (downloading from multiupload), still works (you need to enter the captcha phrase).
The site megaupload was shut down by the US gov't, so that one won't work.
EDIT: UGKC1/UGKC1/BMCKC1/Sbl is the latest Froyo release from Bell. That's what mine and my wife's gt-i9000m phones came with.
She's still running it on hers.
Ok sorry for all these posts, basically when you said UGKG3 you want me to get the 2.3.3 ROM on ? Is that right? What if I Want to put on 2.2 to be sure I have no trouble with it since I'm in all this mess because the Kies update to Gingerbread had my phone in a bad state.
Thanks a lot by the way!
Sorry your post refreshed right after I did mine. Alright cool so I'll try the one you say your wife is running, I had made myself a JIG with a stock Samsung wire, it was working fine with a 300K resistor and I decided to solder it on and then it stopped working after that.... maybe the actual "usb plug" is damaged from the soldering heat I guess I'd have to try another wire, but anyway I'll try to download the 2.2 I just got the UGKG3 3 FILE rom downloaded one of the links did work!
But I'm a little worried about 2.3.3
I'll try to see if i can download the 2.2 first.
I mean basically... these roms shouldn't jam during transfer i Guess
One other thing I see different confusing information, is it important for me to click 'update bootloader" with these stock roms since these files contain an 'SBL' ? Because both times I bricked it was with an "update bootloader checked" firmware update trying to put the ARIES 3 button method fix as a boot.bin and sbl.bin
Fanks..
Files with SBL in the name already have the bootloader included in the PDA file, so "update bootloader" should NOT be checked.
That reassures me, because the only times it did jammed was when the bootloader was checked! THanks a lot blackrose i'll go out and buy another usb cable because I destroyed mine making my JIG. And I'll try yours out. I was reading a lot on another thread and found this one guy who flashed the JL2 one to save his keys instead of the C1 you said your wife was running, whats the main difference between those two and which one should I start with?
Update : I got a new wire, flashed the KC1 version of the firmware, everything goes fine, I did a repartition with the 512 PIT, it reboots the phone, loads all files in a prompt in yellow and there are no errors that appear, the phone reboots after writing 'successful update' and then goes to the galaxy logo and jams there and does the ONE vibrate, PAUSE, 2 vibrate on a black screen forever. The advantage of having successfully flashed a 9000M ROM allows me to have access to my DOWNLOAD MODE 3 button method, but ever since I flashed that 2.2 i9000 XXJP2 (seems its a euro version) off a torrent I found on the web (When I was desperate to find a functioning 2.2 working version) it seems as though it doesn'T want to boot with any other rom than that one, because all the 9000M roms that I've tried so far flash correctly, and the logo actually changed from i9000 to i9000M on the startup, but they just don't boot.. what could be missing it doesn't seem to be much???
Thanks Mat
If any of this can help, the device was rooted, I was following the darky's mod i9000M guide so I had previously installed the CLOCKWORK MOD and that's as far as I got because my eyes caught the FIRMWARE TOUCH KEY UPDATE which ruined my keys.
Could any of this have screwed something that stops my other roms from booting?
Thanks guys I really want to get this phone up and working again as I don't have much money and am afraid I'll have to cancel with my phone company if I just can'T get this running. I am also willing to make a significant donation to whoever can help me.
You in Canada right? Where abouts?
Sent from my GT-I9000 using xda premium
Quebec province
Alright, if this can help anybody my whole problme is solved.
I flashed the ****JL2**** the KC1 did not boot, the JL2 did.
Once inside JL2, I was able to update my TOUCH KEY FIRMWARE *#*#2663#*#* and everything went back to normal
I have no idea why the KC1 does not work, bugs me out.

Categories

Resources