Method: Downgrade from Gingerbread (XXJVK) to Froyo (XXJPY) - Galaxy S I9000 Q&A, Help & Troubleshooting

Like many I installed the leaked version of Gingerbread on my Galaxy S when it first came out, but now Samsung have finally released Gingerbread in the UK, I would like to install the official release. But need to reinstall the official version of Froyo in order to do this via Kies.
I have had to spend quite a large amount of time looking for the process of doing this, as there seems to be conflicting information/methods out there. Also I understand Gingerbread has a new boot loader (the installed the version including the secondary boot loader) which also needs taking back to original, and I have also found that most of the guides out there always seem to leave a few questions unanswered
So after finding what appears to be the best and I believe the safest method, I thought I would post it on here for others.
Before I go into the steps on how i did this, I need to make a few points:
1) Any firmware installation carries risks. This is not approved by Samsung, and you do it entirely at your own risk....i’m no expert, I simply found a method that works for me. So if it all goes wrong, don’t come crying to me (however, after trying a different method previously, my phone would not boot, but I was able to re-flash with the leaked Gingerbread successfully).
2) Do not try this procedure if you are unable to get your Galaxy S into Recovery mode (Vol Up + Home + Power) and Download mode (Vol Down + Home + Power). A number of these phones have this issue, mine was one of them, there are guides online to fix this issue.
3) There seems to be a number of people who have issues with upgrades on Kies even when they haven’t messed with the firmware, so even if you cannot upgrade thru Kies, it doesn’t mean there has been a problem with Flashing the phone.
4) Backup your phone before flashing, as the phone will be wiped.
5) As far as I understand, this is only for the I9000 model and not for any of the other variants of this phone out there.
6) NEVER try to flash the phone without putting it into Download mode first, you will brick your phone.
------------------------------------------
First of all you will need a Windows PC, USB Cable, 2 Downloads (below)....oh and ideally a Samsung Galaxy S
Download 1 (JPU)
http://hotfile.com/dl/99955459/dea6962/I9000XXJPU.rar.html
Password: samfirmware.com
Contents when extracted:
GT-I9000-CSC-MULTI-OXAJPU.tar.md5
I9000XXJPU-REV03-PDA-low-CL747761.tar.md5
MODEM_I9000XXJPU.tar.md5
s1_odin_20100512.pit
Odin3v1.3
Download 2 (JPY)
http://www.megaupload.com/?d=EWTHLRU6
No Password
Contents when extracted:
JPY_JPY_JPY.tar
The idea is to flash with XXJPU first to get the base version of Froyo which includes the SBL, then to Flash with JPY, this will allow you to use Kies for firmware updates (ensure Kies is completely closed before starting this).
1. Download and extract the above files.
2. Power off phone, remove sim and memory card, then start up in Download Mode and plug USB cable into phone (not PC).
3. Open Odin and select the following Files:
PIT: s1_odin_20100512.pit
PDA: I9000XXJPU-REV03-PDA-low-CL747761.tar.md5
PHONE: MODEM_I9000XXJPU.tar.md5
CSC: GT-I9000-CSC-MULTI-OXAJPU.tar.md5
Ensure the following options are ticked: Re-Partition, Auto Reboot & F.Reset Time
4. Plug the USB into the PC, after a few seconds it should displayan “Added” message in Odin, then click on the ‘Start’ button.
The JPU firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
***Under no circumstances unplug the usb cable, press any buttons on the phone or generally do anything that could interrupt the process, until it has complete and the phone is full restarted***
Once this is complete, you are ready to flash the phone with the JPY version, very similar process, but please read as not all of Odin settings are the same.
5. With USB unplugged from PC, power off the phone and restart in Download mode.
6. Re-open Odin and select the following files:
PIT: s1_odin_20100512.pit
PDA: JPY_JPY_JPY.tar
Ensure the following options are Ticked: Auto Reboot & F.Reset Time (NEVER tick ‘Re-Partition’ when using a single firmware file for flashing as this could Brick your phone)
7. Plug the USB into the PC, after a few seconds it should displayan “Added” message in Odin, then click on the ‘Start’ button.
The Firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
And thats it, you should now be able to upgrade the firmware via Kies....that’s assuming Kies is working correctly, and your carrier has released it, i’m with T-Mobile UK, but bought my phone through the Carphone warehouse, and was able to update immediately.
--------------------------------------------------------------------------
I hope this has been helpful, if you have any queries, I will try to answer, but as I said I am no expert, i've simply spent alot of time looking for the best method

Just thought I should point out that xxjpy is a european version and is not carrier specific. So it shouldn't matter if your carrier has released gingerbread yet.
This method will allow kies to update your phone to the lastest european firmware.

Why the pain?
No need to go through all this downgrading palava any more. Just use *spooffw and upgrade via kies as normal...easy peasy and no flashing required.
Search for "kies spoof"
*it fools kies into thinking you're on older firmware and offers you the upgrade to current fw

Don't need to tick "update bootloader"?

No, only tick the options stated in the guide.
Also be aware that you do not tick "Re-partition" on the second flash (JPY)
Sent from my GT-I9000 using Tapatalk

Thanks for the guide! I flashed it from a branded FW (was a backup) to stock and until now it's all pink and fuzzy!

Thank you, that's what i was looking for.

I never realized there was a written guide for this.
I just posted a video yesterday on how to debrand, unroot, and then update via kies.
Thus going from any custom kernel/rom theme etc.. to:
JPU, JPY then updating your version via KIES to JVO - good for warranty purposes.

thanks for this guide

Thanks for this guide. I was on JVO (samfirmware) and wanted to downgrade to get the official latest version installed later.
It didn't fully work for me but eventually got it working.
After having flashed from JPU to JPY Kies detected the phone (did not on JPU). However, it said there is no newer firmware version available.
So I flashed I9000XXJQ3_XXJPY_DBTJS2\PDA_JQ3.tar.md5 as PDA and I9000XXJQ3_XXJPY_DBTJS2\CSC_DBT_JS2.tar.md5 as CSC which I got from samfirmware (these were the versions I used to have on my SGS originally from Kies when I was still on 2.2.1).
*edit April 2012:*
had to downgrade again and went same procedure. However, couldn't remember whether I also flashed "phone". So this time I also added I9000XXJQ3_XXJPY_DBTJS2\PHONE_JPY.tar.md5 as PHONE in addition to the files I listed above as well as I ticked re-partition and added the same pit file I used on the first two flashes.
Afterwards, Kies detected the phone and offered the upgrade. Did that and now it has PDA: JVI, PHONE: JVO, CSC: JV2 (DBT)
*edit end*

cookm75 said:
The JPU firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
Click to expand...
Click to collapse
How long is a "few minutes"? Odin has been at the following stage for just over half an hour now...
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
My phone doesn't appear to be doing anything and just has the yellow/luminous green android figure digging with "Downloading..." beneath it and "Do not turn off Target!!!" showing on the screen.
Should it be taking this long?
I have a Samsung Galaxy S I9000 that was on GB 2.3.4, but due to excessive battery draining, and the phone locking up on a black screen with the only way to recover being to remove battery, it was suggested to me at Carphone Warehouse to try flashing it back to Froyo.

No I had the same issue. From what I understand if there are no file names under the do not turn off target line and no blue progress bar on the phone then you waited too long from connection to flashing. Get everything ready and then connect the phone and start.
Nothing has been done yet at the stage you mention.
G
Sent from my GT-I9000 using XDA Premium App

Just pull out the battery, boot into download mode again and try flashing once more, it will pass successfully this time.
Sent from hell to take your soul

Thank you both gfacer & Lunchbox115.
I have now successfully flashed my phone with Froyo and then re-upgraded to Gingerbread through Kies.
I'm keeping my fingers crossed that the problems my phone was having have now been solved.

thanks, very useful information.

This may be a dumb question, but anyway... Does this whole thing works for samsung galaxy mini? If yes, do you need to unroot it if you already have it rooted.

Related

Stuck at Galaxy S logo!

Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Please Help!
- UPDATE: SOLVED!
Hi there, I'm having the same problem on my I9000B. Please help me.
This is my story, I had upgraded my 2.1 firmware to VIVO's 2.2 Froyo via KIES with the Kies Registry Patcher (used ZVV). Everything worked perfectly, but I wanted to root my I9000B so I made the terrible mistake of using CF-Root via Odin, (http://forum.xda-developers.com/showthread.php?t=788108) following the exact instructions. The kernel replacement (zImage file) was for the I9000 so I had the touchscreen problems. When the phone booted showed Samsung galaxy S GT-I9000B and then inmeadeatly the "B" dissapeared.
Because of my n000bness I tried to use the zImage file from this ROM (VIVO's) (http://forum.xda-developers.com/showthread.php?t=858483), by downloading my own .tar created file (with 7-zip) of the zImage file. Here is were things went down. I got the android - USB cable boot icon. I could not go into recovery mode but I could do download mode, so I re-flashed VIVO's ROM (the one published here) with Odin:
I used the 803 .pit file, Odin 1.3
I did not check re-partition
I selected the ROM as the PDA file and I left PHONE and CSC blank.
the ROM was downloaded to the phone and Odin did not gave me problems.
My problem here is that I get the black screen with vibrations from time to time on boot. This is exactly what happens:
The phone starts showing "Samsung galaxy S.... GT I9000B (at least shows "B")
I can get into recovery mode but the following appears:
Code:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please us UI menu for format and reboot actions.
copy default media content failed.
Then I did a factory reset, succesfully completed, tried again flashing the ROM but with Re-partition box checked (as instructed here: http://forum.xda-developers.com/showthread.php?t=723596) but the same stuff happens.
Please tell me what to do! I know it was a stupid mistake trying to fix ony the zImage file, and stupider was using CF-Root on my non-compatible device.
PS: I can get into download mode with no problems
Code:
pda i9000bvjjpa
phone i9000bvjjpa
csc i9000bzwjp3
I have exactly the same problem
but i can go into recovery mode and download mode.
the galaxy screen is I9000 and my sgs is I9000B
any ideas?
A friend of mine has the same issue on his SGS. Both recovery and download mode working.
Have you done JUST like this:
Figueiredo81 said:
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Click to expand...
Click to collapse
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Thanks!!
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Margaliini said:
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Click to expand...
Click to collapse
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Please, post the link or give me directions for the Claro's ROM. I am having the same problem here.
Thanks.
gtg2 said:
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Click to expand...
Click to collapse
worked here
thanks
thanks for the help i love you no homo !
Un Loko said:
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Click to expand...
Click to collapse
JM2 with pit method is perfect. my "E: can't mount /dev/block/mmcblk0p1" problem has finally been solved.
Thanks
This worked for me.
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
???I bought my Phone from CSpire but stuck on At&t Logo???
Samsung Galaxy s Showcase stuck on the At&t Logo...Will not let me go into Download mode??? Help please?

[Q] Have I ruined my in law's phone? Can anyone help me please?

My father in law bought a new phone SGS on O2 and I offered to unlock it as I have unlocked my husbands last week (he's was on O2 as well but in 2.1 or 2.2.1 version I think-froyo?)
Before I continue may I say I know you guys out there know so much more than me and I really need your help. I really tried to help unlocking this phone and for hours I searched and read things like reboot, download mode, recovery mode, flashing, JKV and so many other words and letter that I could not understand. Very few I understood in the end but may have messed up badly (?).
Please, I need help and please treat me as if I were your mum or even grandma. Step by step in simple normal English please.
My father in law's version is 2.3.3
I tried unlocking it the way I unlocked my husband's but didn't work. After looking for hours I thought that the best way to do it would be to downgrade from 2.3.3 (gingerbread (?)) to 2.2.1 (froyo (?)) and then unlock it.
I found this:
http://forum.xda-developers.com/showthread.php?t=1089989
and tried to follow it.
I downloaded EZRom and EZboot-Froyo-1.0.tar.md5 from the same post.
I followed:
•Download the right version from section above
•Reboot your phone into Download mode
•Connect your phone to computer
•Run EZOdin
•Select EZboot-Froyo-1.0.tar.md5 or EZboot-GingerBread-1.0.tar.md5as a PDA file in EZOdin
•Check the "Phone Bootloader Update" checkbox
•Click Start
I waited for the phone to turn off and feel the little vibration but didn't. Instead it just froze at the first screen when you turn on the phone. The black background with white letters: Samsung Galaxy...
I waited and waited and as nothing was happening I then I took the battery out. Put it back in and tried turning it on. I wouldn't it would just stop and that same screen, the black and white one.
I reread
•Wait until phone reboots and make it reboot into Recovery
SO then I remembered in the many threads I read about the recovery mode so 3 clicked vol up + button at them bottom and turn on bottom.
It gives me a few options. When I click on reboot all it does is show me the black and white screen again and nothing else. ah!!!
I took the battery off and put it back on many times, I also selected the fatory reset option and tried different buttons but nothing. Please help me.
I'm happy to phone any of you guys to help me and guide me even if it's just to put the phone back to what it was before, turning on normally, etc. I'm feeling really sad and a bit stressed as these days are supposed to be a nice time to spend with my little ones and family.
Anyway, please ask me anything.
Thank you so much in advance. I really hope I didn't do anything wrong and I'm just stuck because I'm ignorant in this matter. Thank you
I was never a fan of EZ-stuff.
That said, think you can easily solve that flashing your phone with odin and a proper rom. At this point i am unclear about what bootloaders you have on your phone since you've tried a downgrade.
Without getting into further details (sorry, at work atm). You can get tutorials easy for all of this around this forum.
I'd get Odin, get a proper stock rom from samfirmware with bootloaders included and flash it fresh from start with that. Doesn't really matter if it's froyo or ginger as long as it includes bootloaders.
You'll be left with a working phone at this point.
From here, if you still want to try to unlock it, i'd flash a kernell that would get me root (like the ChainFire one) since i find this the safest and easiest way of getting root on your phone and do a backup of your EFS partition (preferably saved in your computer or wherever outside your phone). This is very important, if you lose of mess up with this part of your phone it will be a pain.
Now, there are several ways of unlocking this phone, the only one i found to be most reliable (but not the easiest one) is to manually edit the nv_data.bin file (located in your EFS partition in hexadecimal.
There's a tut right here
http://forum.xda-developers.com/showthread.php?t=761045&highlight=unlock
Thank you so much for taking the time to reply although you are working!!! Really appreciate it.
I'll try your suggestion but I don't know how to choose the right stock rom with bootloader from samfirmware. I went to the website and registered but don't really know what to do.
I know you are working so might not be able to help me, may be someone else?
Here's where I am. Update. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.
Download Jvt From sammobile. com, you need Odin on your PC (1.7 or 1.8) plus Samsung drivers. Read there flashing guides carefully, check you have download
Mode, battery charged > 50% etc
There is also a video on youtube which shows you how to upgrade to jvt.
Sent using TCP/IP
Sounds like you've got the boot-loop problem, which means that you most likely "soft-bricked" the phone. Don't worry, this isn't that big of a deal and can be fixed with relative ease. I agree with the posters above, a clean flash with Odin will probably fix your problem and get you out of the boot-loop.
I'll go into a bit more detail with some steps (feel free to correct me if I missed anything)
1. Download Odin 1.85 here.
2. Head over to Samfirmware.com and grab the latest firmware for the phone. I recommend Gingerbread 2.3.5 (JVT).
3. Make sure your computer has the proper drivers installed so it can communicate with your Samsung Galaxy GT-I9000. If you've flashed the phone before with your computer then you probably have the drivers installed, but here's a link for them just in case: Samsung USB Drivers
4. Enter download mode on your phone, depending on your firmware, it could be Vol down + power + home OR Vol up + power + home. Pull the battery out, pop it back in, and hold those three buttons until the phone turns on.
If you can't enter download mode with the 3-button hold method, then you might have to do so via ADB with the command "reboot download".
Getting into download mode is pretty critical, as you cannot progress further without it.
5. Once you're in download mode (should see a triangle with an Android shoveling stuff in it), plug your phone into your computer's USB port and open Odin. In Odin, press "Reset" on the right hand side. Odin should be able to detect your phone (this is indicated by a yellow box on the left side). I'm using a PC, so inside the yellow box I see something like this: 0:[COM9]. On a Mac it probably says something different, but as long as you see the yellow box appear then it's all good.
If you don't see the yellow box, then there's no communication between your phone and the computer, which means that you may have to reinstall the Samsung USB drivers.
6. With the contents in the firmware package that you downloaded from Samfirmware.com extracted, load them onto Odin accordingly.
PIT: use s1_odin_20100512.pit
PDA: JVT (sometimes the PDA is labeled CODE instead)
PHONE: JVT (sometimes labeled as MODEM instead)
CSC: use HOME-MULTI-OXAJVT (should be about 9.5 MB in size)
Since your father-in-law's phone was originally 2.3.3, you shouldn't have to alter the bootloader with Odin, so leave the bootloader field empty.
7. Once you've loaded up all the necessary files, make sure Re-partition and Auto-reboot is checked. Leave the rest of the checkboxes as it.
8. Press Start. This should initialize the flashing of the new firmware. After the phone has been flashed, it should reboot automatically and should hopefully be able to get past the Galaxy S black and white logo (aka. boot loop).
9. The phone should be in working order now. I used this method to unlock my SGS: SIM Unlock on the SGS. With this method, your phone needs to be rooted, so head on over to ChainFire's thread here to install his kernal which is already rooted.
Flashing firmware can be pretty scary since nobody wants to end up with a brick that costed $400 and it seems like so much can go wrong, but hopefully the steps I've provided helped. Good luck!

[Q] Humble request from Epic noob

Hello guys,
Yes... I'm a total noob, I tried to root my phone with the wrong files and ended up bricking my phone.
My reason to root: wanted to be able to use the emulators / controllers on the market. If only I knew this was going to happen
On my attempt to reverse the situation, I did it... my phone stopped booting completely.
I figured since my phone does go onto downloading mode still, that I'd be able to return it back to normal once I educated myself a bit on the processes of flashing androids.
I have tried to find a thread similar to mine, and I have been unsuccessful to the point of utter frustration (I even considered going and getting a new phone).
Then I came across AllGamer's thread:
http://forum.xda-developers.com/showthread.php?t=1379650
I thought my search (of 8 hours by then) was done, that everything would be back to normal.
But somehow I have been unsuccessful to mimic his results on flashing the phone back to Stock.
I'm probably wrong assuming that the bootable files on the phone are missing since my stupid trials at the beginning of it all. Hence why AllGamer's instructions aren't doing it for my phone.
I have a Samsung Galaxy S GT-I9000m
This is my last resource (to which I have no right, but I figured I should try before calling it quits).
Can any of you help me fix my phone?
Did you try flashing using the three files method in ODIN? You need ODIN, a PIT File, and an original ROM that has 3 files (Phone, PDA, CSC) in it. Check the Re-Partition option and your phone should go back to the original rom.
Go to SamMobile dot com to find a Samsung ROM
As long as you have download mode then your phone is still alive.
Go to samfirmware ( or sammobile as it may have changed over now ) and get a zip file for you device which contains 3 files and a pit file.
MAKE SURE YOU GET A FIRMWARE FOR AN I900M NOT A I9000 OR AN I9000T!
Download odin and put the pit file in the pit box.
in PDA box put PDA file or it may be called CODE.
In MODEM put the MODEM file or it may be called PHONE
In the CSC box put the CSC.
make sure that repartition / auto reboot / auto F reset are ticked.
Any other boxes should be unticked.
Put your phone into download mode and connect it to the PC.
MAKE SURE YOU OPEN ODIN AND CLOSE ANY KIES SOFTWARE BEFORE CONNECTING YOUR PHONE!
a yellow box should pop up in odin saying COM XX
press the start button and let odin work its magic and voila! your phone is alive!
Good luck

Sad Story, Help me Please (DEV asking 4 help)

Okay. So I had to sell my mums SGS because we needed the money, but before i sold it, I had made a backup of the rom via CWM.
NOTE>the phone was on 2.3.5
So anyways. I bought another SGS for her the other week running 2.3.3 and i havent been able to get kies to load up on my pc so i can update it to 2.3.5. I've searched all over google and youtube. used all methods however, when i click kies, i just get a loading circle on my pc(Windows7) and then the circle stops. Kies never opens. I've reinstalled but it still won't open.
When i go into settings/aboutphone/updatephone. it says theres no update for it when it's clearly running 2.3.3
I wanna restore my mums phone with the backup however i can't update my phone to 2.3.5 to do so.
Note' I havent been able to find any versions of kies to see if they'd work
flash
try to flash stock rom via odin.............................
agree with ^, try flashing from begining.. there are many of tutorials on xda. u can try development section goodluck
MattyOnXperiaX10 said:
Okay. So I had to sell my mums SGS because we needed the money, but before i sold it, I had made a backup of the rom via CWM.
NOTE>the phone was on 2.3.5
So anyways. I bought another SGS for her the other week running 2.3.3 and i havent been able to get kies to load up on my pc so i can update it to 2.3.5. I've searched all over google and youtube. used all methods however, when i click kies, i just get a loading circle on my pc(Windows7) and then the circle stops. Kies never opens. I've reinstalled but it still won't open.
When i go into settings/aboutphone/updatephone. it says theres no update for it when it's clearly running 2.3.3
I wanna restore my mums phone with the backup however i can't update my phone to 2.3.5 to do so.
Note' I havent been able to find any versions of kies to see if they'd work
Click to expand...
Click to collapse
Okay , first go to sammobile.com and register go to firmwares and smartphones , android, GT-I9000 select your region and look for android 2.3.5 download then download Odin and unzip the firmware , you have PDA or CODE Phone or MODEM and CSC and pit file put your phone in download mode by turning it off then press the down volume button and the home button and the power button at the same time open Odin and connect your phone vi USB cable and press the pit and select the pit file then PDA and select the PDA or Code file then Phone and select Phone or Modem after that CSC then press start your phone will flash and you are on android 2.3.5 )
Thanks guys, I'll try this tonight

[Q] My Galaxy Note(SHV-E160L) is bricked...

before writing, I'm so sorry for my pooooor English.
I live in Toronto, Canada. I bought my Galaxy Note(SHV-E160L) from Korea, so change sim card from LG U+ to Rogers.
but when I sleep, Note encounter Unlimited Reboot.
so I try to repair in 3-way.
first, Factory reset. but I could make Download mode only, couldn't make Recovery mode.
so I try Samsung Kies Recovery mode, but Kies show me binery Error.
last, I want to use ODIN, but ODIN show me Error Message, too.
"Complete(write) operation failed"
What this means?
If it can't be repaired, I must send my cell phone to Korea.
I'm very embrassed...
please help me!!
and Merry Christmas for you
Is it sticking on factoryfs.img in ODIN ? this usually means its bricked which kernel where you on when you did the factory reset ?
I had a similar issue last week, stuck in odin, everything failing, I was convinced it was bricked, I manage to repair it by (no joking here) flashing a million wrong things in ODIN.... But DO NOT TRY THIS lol
try to flash a safe kernel through ODIN, and then see if it bring back recovery, then you can wipe and flash a new rom (hopefully)
otherwise there is the pit file method to revive from a brick, which works well, but loses around 3gb of internal sd space
hello
hello bro...
try this method:
download a stock gingerbread rom then go into download recovery, flash it with odin, root your phone.
from here you can install any custom rom, this is how i do when i got bootloop.
Thanks for your reply
hanzo777 said:
hello bro...
try this method:
download a stock gingerbread rom then go into download recovery, flash it with odin, root your phone.
from here you can install any custom rom, this is how i do when i got bootloop.
Click to expand...
Click to collapse
Thanks, but when I use ODIN, ODIN got a trouble..
when It start to flash, ODIN shows error message (Complete(write) operation failed)..
so even I can't try another Kernel Files..
Sigea said:
Thanks, but when I use ODIN, ODIN got a trouble..
when It start to flash, ODIN shows error message (Complete(write) operation failed)..
so even I can't try another Kernel Files..
Click to expand...
Click to collapse
Perhaps should follow closely the guide for using odin from Dr ketan should help:
http://forum.xda-developers.com/showthread.php?t=1424997
1. Installation
- Download stock ROM (should start with a GB rom), and extract it to .tar file
- Download Odin, open it
- select PDA tab and point to ROM file. Leave Re-partition, pit, CSC, Phone tab unticked.
- Switch off device, Put in download mode (Vol down + Home + Power)
- completely close kies, Anti virus if running
- Connect device to PC
- ID com port shud turn yellow (not shown in image)
Now hit Start
----
see how it goes.
Same problem as OP
Hello guys,
unfortunately, I have the same problem with my 32GB SHV-E160L as OP. Little backstory:
I bought the GNote in Korea and brought it back to my country. I successfully rooted it with one of the guides here on XDA (Tegrak kernel, no OC whatsoever). No problems so far, the phone worked for weeks and I was able to do what you can do with rooted phones. One day while surfing the net it just crashed and was stuck in a boot loop. This is where I am now.
I tried:
Go into tegrak recovery. result: It gets stuck on samsung logo, funnily the phone would establish a usb connection if plugged in (as if in download mode)
Reset from Kies. result: After beeing told by Kies to go into download mode, instead of flashing the new software it gives an error message in Korean about missing binaries (see attachment)
Flash from odin. result: the dreaded red box with "fail" appears after the NAND write command
Now, after doing my research here on XDA I found out that my emmc might have damaged partitions and I need a PIT file. Here's where I'm stuck.... I can't find a PIT file for my 32GB note, only for the N7000 or the I717. And I don't want to mess things further up... so if anyone here could provide me with a PIT file, or tell me how to fix the phone through other means I would be really grateful
Thanks in advance....
You should ask hg42 if he can make one - in his thread I read that he did this before even for other devices.
So try a pm or post in his thread. Good luck

Categories

Resources