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.
Here is why I'm asking this. I have a SGS I9000b. After some wrong doing that almost bricked my phone, the screen started to show that I had and SGS I9000b and then the B would quickly vanish resting only the Samsung Galaxy S GT-I9000.
The fact is, after some effort I was able to install eclair on the phone and put it to run again, but now when I start it, it shows SGS GT-9000 to quickly be substituted by GT-9000b.
I was unable to upgrade my SGS to froyo again, and maybe this is one reason that I cant, every time I try, I get that /dev/ error.
So, What does it means when at the start screen the modle changes suddenly?
Hope I could express myself clear enough.
I came across a similar thread yesterday.
http://forum.xda-developers.com/showthread.php?p=13268587
I guess the first part of the boot screen is from the bootloader and the second part of the boot screen is from the ROM? (pls correct me if I am wrong)
So, have you tried flashing I9000B stock ROM with bootloader using Odin?
If you want to upgrade using samsung softwares, you need to have the stock rom of your phone or an official stock upgrade (can find on samfirmware or in various posts here), otherwise in order to change rom you can use odin
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.
Hi,
My dad brought me his non rooted, non modified Galaxy Tab GT-P1000 that is stuck in the famous reboot loop. That is, it reaches the samsung logo and just stays on that animation of the logo glowing and fading.
I've tried various combinations of ROMS, as well as different versions of ODIN and Heimdall. I've successfully reflashed different firmwares but the furthest i get is the samsung logo.
The device was bought out of carphone warehouse UK, for which i found the latest firmware at http://fus.nanzen.se
I can flash this with heimdall 1.1 (1.3 always asks about firmware.xml which i figure is just a way of explaining what's in the tar to save selecting the files seperately). That said, i have tried 1.3 in command line mode on linux.
I get varying results with the flashing process too.
For example, this carphone warehouse firmware flashes fine with Heimdall 1.1 but fails in Odin.
I'm really running out of ideas. I thought it was just that something had got currupt somewhere and a reflash would sort it but no such luck.
Can anyone offer any tips? I've looked around the message board but it's like playing pass the parcel with the links. It seems a lot of people fix their tabs without actually realising what it is that fixed it because they've also gone through a whole load of combinations.
I've tried ROMS from samsung firmware website. Tried JHA from early on. Tried latest 2.2 that isn't tied to a network. Tried ones in the middle. Tried flashing only dbdata. Tried re-partition.
EDIT: I've avoiding looking into rooting it as a solution because my dad is trying to fish out the receipt in case it's under warranty. If it's not i'm prepared to root it. I used to be in the android scene back in the day when the G1 came out. I've programmed applications for Android and written a uni project on it so i am quite familiar with it, just maybe a little out of date with the processes.
EDIT2: Sorry guys just realised there is a galaxy 10.1 section too...
EDIT3: And that i don't have a galaxy 10.1 anyway...i may have flashed my brain with the wrong ROM. Anyone have a "sensible brain" ROM?
Hmmm... you might get helped at the Overcome-site, look for the restock GB v5 in the tutorials...
I have the Galaxy SIII 4G
running Android 4.1.2
Locked on Telstra
Any other information needed? ask me.
So, I got my phone from a friend, and was very exited and tried rooting.
Firstly using Odin and a guide which I can't link since I'm new to the forums and can't post links, I didn't get some steps right and phone wasn't rooted, I then did a factory reset.
Went to find another guide and then found the Galaxy SIII Toolkit (Am new to forums, can't post links) and used it, I found that the version 7.0.0 didn't include support for my android version on the 4G so I tried the normal international version that wasn't for 4G, it was very similar but this may have been what had broken it. (me choosing the wrong one, stupidly) and after trying and trying, using some other things like Odin, my phone is now stuck on the "Downloading...Do not turn of the target !!" and even if I pop the battery, reset the device, try to get to recovery, and trying many other things, It just doesn't budge. When I was able to get to recovery and able to make it to Samsung galaxy SIII logo but no further,(I managed to flash CWM recovery) I tried factory resetting but it still didn't work.
As you can tell, coming from a Galaxy Nexus to a Samsung Galaxy SIII is pretty exiting, then having the phone broken within the first day of having it is very saddening (Seriously almost cried).
I need urgent help, if you need any more information on the phone, feel free to ask, even though I may not know.
Thanks :fingers-crossed:
there's a reason there are 2 different versions for the i9300 and i9305. They're 2 different phones.
http://forum.xda-developers.com/showthread.php?t=1946915
and this is a wrong section, it's for the i9300 (it says so right in the title)