Hello everyone,
I want my phone back to the way it was on android 2.1 so I can update to 2.2.
I got 2.2 on my phone before it was officially released, and had to do it with other CSC etc.
So I want my phone back to the way it was when I bought it, how will I be doing this?
I remember I had JM2 when I got it.
Thanks in advance.
EDIT:
Found this thread. http://forum.xda-developers.com/showthread.php?t=846913
Those are the ones you get when buying the phone right? So, can I just pick the JM2 and flash it?
Please help.
yes the ones in that link are official stock ROMs just flash which ever you desire and your phone is 100% original again.
Alright then, thanks.
I'm trying to find a tutorial on how to flash it, since it's been awhile. But I can only find tutorials for custom roms.
the tutorial is in the link, its relatively easy. have you downloaded the stock rom you want ?? does it come in 1 file or 3
It's still downloading it, but it's 1 file in .exe format.
The CSC's in that thread, does not include a JM2 one. Am I missing something? And what PIT file do I have to use?
im confused ??? its in .exe format ? wait till it download and then open it and make sure... if it needs a pit it should all be in there, a lot of stock roms come in just 1 .tar file.
I think it's a 7zip.
Alright, I'll just reply in this thread when there's something I need. Thanks for the help so far.
The PIT file isn't included, do I really need to use it or is it optional?
I think I have to use the 512.
just make sure re-partition is checked before you flash.
Alright.
But I think I have a little problem.
When I connect my phone, "0:[COM3]" shows up yellow in Odin. Shouldn't it be green?
Screenshot: http://i52.tinypic.com/34j4ufk.png
(I hope it's clear)
And it's just stuck there.
its supposed to be yellow.
Ok, but does it take long for it to go on?
I've tried it without the PIT file but then this happens.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
have you extracted the files ?? or did it come in 1 file ?
Procedure:
1.Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connection the phone via USB!)
2.Select the PDA/Modem/CSC/.PIT files in Odin. (For kernel flashes, only PDA is required. For FW flashes, .PIT and at least a PDA is required. Some PDAs have Modem and CSC integrated. Make sure you have the correct .PIT file. Usually 512.pit)
3.Check the "Re-Partition" checkbox.
4.Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
5.Connect your phone with your computer and wait until the drivers are installed.
6.When the drivers are installed, click Start.
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
8.You have successfully flashed your phone.
That's what I forgot, the download mode.
But the Re-partition has to be un-checked? Should it be checked or not?
check it, if you have all 3 files. and pit. then everything will be normal
Ok, it's going good so far.
You have been a great help, I really appreciate it
It did say something about having no access to multi-something. But other went fine.
good, just be sure to let it boot properly. sometimes it can take 15mins to boot up so dont panic. as long as ODIN says PASS, all is well.
I got another question.
Since it's android 2.1 and 2.2 being released. Kies should tell you that there is an update?
But Kies says: This version of the device cannot be updated.
By current firmware version it says: PDA:JM2 / PHONE:JM1 / CSC:JM1
Something wrong?
OK, I flashed to a new ROM and would now like to flash back to the stock ROM due to some issues with the new ROM, but whenever I do it, I wind right back where I started, with the flashed ROM, not the stock ROM (2.1). I may have deleted a file that is needed to get back to stock. Is there such a file? I follow all the instructionals and everything works well, it just doesn't flash back to stock?
We would need allot more details in order to pinpoint where you are going wrong.
My best guess is that you are not being recognized by odin, you are clicking start and nothing is happening. How long is the odin flash taking?
CM7
Im using Odin 3 v1.00. With the Captivate, I go into download mode and Odin recognizes it. I get the following
<ID:0/009> Added!!
Then I click start and the list expands to
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> Removed!!
It says Reset up top, but when the phone reboots, it just reboots back to the Cognition 4.1.1 that I was running
I had this exact problem last night, I was trying to flash back to stock from a I9000 ROM I had installed and it wasn't running good for me. So I did what I had done in the past, I was using the Captivate ToolBox to flash back to stock, my phone would go into Download mode, but Odin never saw it. I thought that was odd, so I tried the regular Odin flash to stock as well, using the pulling the battery and holding down vol up and down and plugging in the USB. Still Odin didn't see my phone.... I then rebooted my computer, put my phone in download mode and plugged in into my computer and for some odd reason Windows said it was installing new drivers for my device. After it completed, Odin saw my phone and I was able to flash back to stock, so you could try that, it may help you.
EDIT...Oops, sorry not the same deal I had, sorry..
Try different usb port
Make sure odin is open first
Be aware of what build tourer phone is, located under battery something like 1008. If 1010 our higher don't use one click
If box in odin turns yellow and days "com#" then you are recognized if not you are not
Phone must be in dl mode
Correct drivers must be installed
CM7
Beowulf, you commented
YYou need to supply the firmware file to flash (click on the "PDA" button, and browse to where you downloaded it--you *did* download it, right?), and optionally the ".pit" file if you need to re-partition when you flash.
I think you are right, but what would I point to in order to flash back to stock? Where would I get it? I can find what to point to if I wanted to flash to Cognition 4.1.1 or one of the other custom ROM's, but I cant seem to find what file I can download/point to in order to restore to stock ROM.
mcord11758 said:
Try different usb port
Make sure odin is open first
Be aware of what build tourer phone is, located under battery something like 1008. If 1010 our higher don't use one click
If box in odin turns yellow and days "com#" then you are recognized if not you are not
Phone must be in dl mode
Correct drivers must be installed
CM7
Click to expand...
Click to collapse
I believe I installed the correct drivers (that allow me to connect to Odin) as I do get the yellow box and it says 0:[com9]. Phone is in download mode. Also, it says 1008 under the battery.
http://www.samfirmware.com/WEBPROTECT-i897.htm
You need to create an account. Jf6 put listed bottom page
ThaRide said:
Beowulf, you commented
YYou need to supply the firmware file to flash (click on the "PDA" button, and browse to where you downloaded it--you *did* download it, right?), and optionally the ".pit" file if you need to re-partition when you flash.
I think you are right, but what would I point to in order to flash back to stock? Where would I get it? I can find what to point to if I wanted to flash to Cognition 4.1.1 or one of the other custom ROM's, but I cant seem to find what file I can download/point to in order to restore to stock ROM.
Click to expand...
Click to collapse
CM7
I wound up following teh lead that Beowulf gave me as I was using the full blown Odin and not the 1 click. When I watched videos on how to flash back to stock, I did wonder why teh version I was using looked different. I had assumed that it was just a slightly newer version.
To make a long story short. Once I used the 1 click Odin, I flashed back to stock easily. Thanks to all for your help. Much appreciated.
I need some help... Please!
I have a I9000T galaxy S phone and I soft bricked it. This is the story:
I flashed my phone using Odin with ROM JPY_JPY_JPY (downloaded form samfirmware, only file: PDA), and then flashed supermod-kernel-k13d-500hz...then I uploaded Modem UGJL2 for Froyo as an update.zip file (to get band 850 mhz for my country) and applied successfully!
My phone worked as a charm. No bricking.
Then I realized that there was a newer ROM: I9000XWJS5 with the XEN thing.
Since the ROM has the 3 files (MODEM, CSC, and PDA) and I read that it needed a different PIT, I flashed with the re-partition checkbox checked and with the 803 pit file.
It didn't get through. It got stuck at flashing sbl.bin
I had to unplug it after several minutes and I realized that it was soft bricked. It didn't work but download.
I tried to go back to JPY. After many tries and errors (changing PIT to 512 and repartitioning), finally I could flash back to JPY ROM. At the end of the process it reboots and the system get into Android system recovery <3e>. I can read at the bottom the following signs:
E: Can't mount /dev/block/stl10 (invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
If I reboot the system, it boots and I see the splash "S" moving theme, and it seems that it is booting but then it stops and it starts vibrating from time to time... then the screen goes black and nothing happens (but vibrating from time to time). It never appeared the "login screen"
Reading here and there, some advised to flash first the speedmod-kernel with the PIT 512 file and re-partitioning. I did so, and then, after boot I was able to get into Clockworkmod recovery screen. The menu is green and the version is 2.5.1.0
Someone suggested to flash to JPU ROM (that way it fixed a similar problem) but when I did so, it takes me to the beginning (the process hung at sbl.bin)...
I've been flashing and reflashing with different options these 3 ROMs (JPU, JPY, JS5) the only one that completes the flashing successfully is JPY, and eventhough it tries to boot, it fails to present the logon screen (dots for password)... JPU and JS5 hang at sbl.bin and after that, no boot... freeze. I have to flash back to JPY.
I have read tons of forums, I have learned a lot, but I believe I need deeper advices.
Thanks in advance!
Some further information. JPU, JPY, JS5 are ROMs that were downloaded from samfirmware.com... I guess that is what you mean when you advice to flash any stock ROM. Am I right?
Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!
droilfade said:
Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!
Click to expand...
Click to collapse
No... I don't have a I9000m, I do have a I9000T
When I flashed the JPY it turned a I9000, but I applied the Modem UGJL2 which adds the 850mhz band (which is the only difference between the I9000T and I9000.
Someone suggested going to JM8 (Eclair 2.1), but I have read that in some cases it produces hardbrick... what do you think?
Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.
froysm said:
Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.
Click to expand...
Click to collapse
Thank you froysm... What I see in your post is that we are going to try to flash a Darky's ROM in order to have CWM so we can flash a custom rom?
If that is so... I already have CWM... It is version 2.5.1.0 with its menu in green.
What is custom rom? are they the roms from samfirmware? I tried JPU and JS5 and they hang at slb.bin... the only one that flashes successfully is JPY, and eventhough it "runs", somehow it is not working.
In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?
Well, if you have CWM try one of the roms of the world famous romkitchen Cook a rom, download it, enter recovery mode, go to mounts & storage (and connect your phone to the computer) and select mount USB storage, put the donwloaded zip file in your phone. Then unmount, go bak to the main CWM menu, select install zip from sdcard, the choose zip from sdcard, find your rom and flash it! However... as far as i can remember i could never mount my phone with CWM 2.x so may need to flash Darky's Rom just to be able to mount your phone, put the zip file there and then reflash with the new ROM viw CWM...
jdelagarza said:
In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?
Click to expand...
Click to collapse
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.
froysm said:
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.
Click to expand...
Click to collapse
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?
jdelagarza said:
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?
Click to expand...
Click to collapse
Don't worry, that is exactly why we are here to learn from other people experience and share what we have learned.
About your issues,
I only have access to my Linux machine and heimdall says this when i ask for help (with the command
Code:
heimdall help
Usage: heimdall <action> <arguments> [--verbose] [--delay <ms>]
action: flash
arguments:
--repartition --pit <filename> --factoryfs <filename>
--cache <filename> --dbdata <filename> --primary-boot <filename>
--secondary-boot <filename> --param <filename> --kernel <filename>
--modem <filename>
So, what you have to do is navigate to the location of your files and write something like this
Code:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --dbdata dbdata.rfs --cache cache.rfs --param param.lfs --kernel zImage --primary-boot boot.bin --secondary-boot Sbl.bin --modem modem.bin
See how i reordered the files to flash leaving at the very end Sbl.bin and modem.bin?
As i told you before this will fail because of the last files, but it will allow to flash everything else. Remove your battery, put it again and try to boot your phone.
I forgot to tell you something really important!! Since the flash in going to fail it will give you the <<scary>> "Connect phone to PC" screen, but don't worry, heimdall can take care of that. Again, asking heimdall for help in the command line says something like this:
action: close-pc-screen
description: Attempts to get rid off the "connect phone to PC" screen.
And that is exactly the next step to take, write down in your command line (with the pone connected to the pc and in download mode)
Code:
heimdall close-pc-screen
And that's it, wait for the phone to boot.
This method is the one i advise when you just can enter Download Mode or when you really need to repartition.
Better? Worse? Nah, they are just really different approaches, Odin is the Samsung standard, Heimdall came to the game because it's OS X and Linux compatibility and CWM allows you to control your phone, custom kernel settings, flash updates packages with modems, boot animations , even whole roms without the need of a cable to connect your phone to a PC and other really cool stuff. Generally, since i've been in custom roms (like darky's, romkitchen, ultimate, etc) since i got this phone, i only use CWM, and when i have a big problem or i need a stock rom i use Heimdall (because i'm on Linux).
The CWM version is just fine, not all the roms are compatible with CWM 3 at the moment, so just make sure you can mount your phone in your pc with CWM. Try first the CWM option, if you can't mount it or it just don't works try the heimdall option.
The last question, I'm not saying it's 100% safe because it is not, but not only custom roms, this also can happen flashing a rom with Odin or Heimdall. Honestly i haven't heard of someone who bricked a phone in the whole thread of the romkitchen or darky's rom. I mean, it could happen, even with a perfectly stable stock rom. but it's not so common, at most, the worst thing you will encounter in your custom rom experience is a lot of Force Closes in applications (if you mix data and apps from incompatible versions) maybe a couple of boot loops, but nothing to be really scared about, just make sure you can enter Download Mode and everything will be fine.
Phew! The longest post if ever written in any forum. I hope i made everything clear, if you happen to have any other question i'll be happy to answer it (But it will have to wait for tomorrow... you know, it's midnight).
Thanks...
I'm downloading darky_heimdall.zip. As soon as it is downloaded, I will try it.
Just for your information, with CMW I tried to mount the USB and it worked!
So, now I am at a dilemma... Should I flash darky with CMW or heimdall?
Oh, if you wanted to know how I managed to install a WORKING STOCK ROM with froyo... here is the tutorial that I followed:
http://neosystm.com/2010/12/actuali...000t-a-froyo-2-2-1-xxjpy-de-forma-no-oficial/
It worked as a charm... I had Froyo 2.2.1 with JPY ROM.
The problem began when I tried to update it to JS5 ROM.
Cheers!
I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...
OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers
Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?
Hey, sorry i didn't answer sooner, let's see...
jdelagarza said:
I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...
Click to expand...
Click to collapse
Yes, you can.
jdelagarza said:
OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers
Click to expand...
Click to collapse
That specific version of Darky's rom is intended only for heimdall, so it will obviously fail. You'll see, some files can just be flashed via CWM and some can just be flashed with Odin and Heimdall, be careful and read with which tool can be flashed.
jdelagarza said:
Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?
Click to expand...
Click to collapse
As I told you on my last post, heimdall can take care of that. Just put your phone in Download Mode and write heimdall close-pc-screen. That should solve your problem.
jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
Nope, i've never found it (actually i've never needed it).
jdelagarza said:
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?
Click to expand...
Click to collapse
Try my methods first, I've tested them a lot and never had a real problem. If you want to try this, go ahead. As i told you before it's very rare to hear a phone really bricked, most of the times it's recoverable.
Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?
jdelagarza said:
Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?
Click to expand...
Click to collapse
Always, after any task completed successfully or unsuccessfully either with Heimdall or Odin, unplug your phone, reboot it, put it again in download mode and connect it. So do that again, flash, wait for the fail, unplug, reboot, download mode again, connect again and try to remove the error screen with heimdall.
I will read that post and see what i can find (I can't read it right now, sorry).
So I've downloaded the following kernels from a link here on XDA that should be swapping kernels to allow me root on my recently upgraded, stock ROGERS 2.3.3 Captivate. Odin is telling me to "Check image files !!" when I load the .tar files into the Select Intergrated Package (and yes, the one package switch is on). I opened the tar to double check it wasn't double-compressed.
What else would be giving me this problem? I'm using Odin 4.28. Curiously, it is showing my phone as detected, my phone IS in downloading mode, but Odin just says (Android) in the Title, no specific model. But it says it's found it on COM 6. <1> Added!! and Detected!!
It's when I load up the kernel tar's and try to start that it yells at me. Is this triggering anything in anyone's mind that I'm doing wrong? Or do I need to provide more info?
I am using Vista 32-bit (legit) on a Dell studioXPS. And I ran it as administrator.
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Pirateghost said:
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Click to expand...
Click to collapse
Yeah. That is def the wrong version of Odin. Download the i9000 bootloaders in my sig. Unzip it. Delete the pda.tar.md5 file. Use the included version of Odin (1.82 I think) to flash your kernel.
Alright, quick question - I accidentally flashed the phone, not the pda. I tried to flash the KH2 modem back via phone but ODIN failed. Kies is currently not detecting the phone, and so I decided to try flashing the PDA while I had it open and I would figure the modem out after. ODIN hung, so I closed it and rebooted out of downloading mode and got the Phone ! Computer error. So I figure now I have to flash back to the stock rom and start over again, but this time I would like some advice as to which step to take next. I downloaded I896UXKH2-HOMEBINARY.tar.md5 from another thread here. Can I flash this with Odin - and if so, which is the place to load it? Bootloader? PDA? Phone? CSC? I have no PIT files.
Think it goes into the pda slot. Go back to the thread t you got it from and read the first post of the thread. Also restart your computer before trying to flash again.
can someone upload the modem.zip, please thank you