Database Develop

Downgrading from JPH no 3 buttons combo to JM1

Hi,
Is there a way to edit registry like in this tutorial http://mingersoft.com/blog/2010/09/samsung-galaxy-s-reclaim-the-missing-three-button-modes/ to downgrade from JPH to JM1? I don't have 3 buttons combo and I can't root the phone.

I am new to this but I dont think so through Kies, I think you will have to use Odin, download the JM1 files from www[dot]samfirmware[dot]com and adb to get in to download mode. It could be dangerous as you don't have the 3 buttons combo, but I did it and it worked first time, but do research first, and take your time.
Seams this phone is very easy to brick, un-like my HTC Desire, so be careful, the official Froyo is out soon, so it may be better to wait to see what happens with that?

amjb71 said:
I am new to this but I dont think so through Kies, I think you will have to use Odin, download the JM1 files from www[dot]samfirmware[dot]com and adb to get in to download mode. It could be dangerous as you don't have the 3 buttons combo, but I did it and it worked first time, but do research first, and take your time.
Seams this phone is very easy to brick, un-like my HTC Desire, so be careful, the official Froyo is out soon, so it may be better to wait to see what happens with that?
Click to expand...
Click to collapse
I prefer the Kies method because I tried to install the 3 buttons combo fix described in this tutorial but It didn't succeed. Anyway, I was able exiting from download mode and nothing was changed to the phone. I think that Kies is not forcing flashing something that isn't compatible like Odin and I'm not risking to brick the phone (may'be I'm wrong).
PS: I've read that Samsung people claim that recovery and download mode aren't supposed to be used by customers. False, because after the unsuccessful flash, Kies asked me to put phone in download (or recovery, I don't remember well) mode because the firmware must be recovered. Obviously I've ignored that because the phone was ok.

I did the Kies to JPH, the day after, the 3 buttons combo came out! so used Odin to go back to JM1 then did this, http://forum.xda-developers.com/showthread.php?t=785201
I have an unlocked & unbranded phone.
It was all very risky, but was ready to return phone, as I've only had it 7 days in the UK, but it all worked for me, but would not want to recommend this, I've got a fair bit of experience in flashing phones, or I could just be a bit stupid, and went for it.
There seams to be lots of different stories as to why the 3 buttons combo is missing, its just stupid, what ever the reason as it will cost Samsung more in repairs, they must know the Android community likes to do a little hacking here and there!
What ever you do, I hope all goes well!

amjb71 said:
I did the Kies to JPH, the day after, the 3 buttons combo came out! so used Odin to go back to JM1 then did this, http://forum.xda-developers.com/showthread.php?t=785201
I have an unlocked & unbranded phone.
It was all very risky, but was ready to return phone, as I've only had it 7 days in the UK, but it all worked for me, but would not want to recommend this, I've got a fair bit of experience in flashing phones, or I could just be a bit stupid, and went for it.
There seams to be lots of different stories as to why the 3 buttons combo is missing, its just stupid, what ever the reason as it will cost Samsung more in repairs, they must know the Android community likes to do a little hacking here and there!
What ever you do, I hope all goes well!
Click to expand...
Click to collapse
I don't know how to go back to JM1 using Odin. Every tutorial says I need root at least. Or having 3 buttons combo enabled.

The way I did it?
coradux said:
I don't know how to go back to JM1 using Odin. Every tutorial says I need root at least. Or having 3 buttons combo enabled.
Click to expand...
Click to collapse
This could be wrong, anyone with more experience than me please say if it is!!
To get into download mode:
What you need is the Android SDK, install then using the Command Prompt and type "adb reboot download" this will reboot the phone in download mode.
then look here www/samfirmware/com for I9000XWJM1 # and Galaxy S / .PIT File: DOWNLOAD. (512) and the Odin program.
Pit file 512
for PDA choose CODE_I9000XXJM1.tar
for PHONE choose MODEM_I9000XXJM1.tar
for CSC choose CSC_I9000OXAJM1.tar
I did not have repartition clicked the next two were, and I checked Phone Bootloader update.
I had Odin setup with all the right files and settings, then used the "adb reboot download" the phone went into download mode, and then drivers were auto installed and Odin found the phone on com7, I held my breath and went for it.
But, I would do lots of your own research through this site, I could have just been lucky? and if you have even a little doubt, don't do it and wait for Kies and the official froyo.
Hope this helps a bit!

amjb71 said:
This could be wrong, anyone with more experience than me please say if it is!!
To get into download mode:
What you need is the Android SDK, install then using the Command Prompt and type "adb reboot download" this will reboot the phone in download mode.
then look here www/samfirmware/com for I9000XWJM1 # and Galaxy S / .PIT File: DOWNLOAD. (512) and the Odin program.
Pit file 512
for PDA choose CODE_I9000XXJM1.tar
for PHONE choose MODEM_I9000XXJM1.tar
for CSC choose CSC_I9000OXAJM1.tar
I did not have repartition clicked the next two were, and I checked Phone Bootloader update.
I had Odin setup with all the right files and settings, then used the "adb reboot download" the phone went into download mode, and then drivers were auto installed and Odin found the phone on com7, I held my breath and went for it.
But, I would do lots of your own research through this site, I could have just been lucky? and if you have even a little doubt, don't do it and wait for Kies and the official froyo.
Hope this helps a bit!
Click to expand...
Click to collapse
Ok, I will give it a try. But, can you gave me a link to all this files? I am really confused by now, reading dozens of threads and I want to be sure I will use the same files you used.

Hi
here for the SDK
http://developer.android.com/sdk/index.html
and here
www.samfirmware.com
for the firmware/Odin/and pit files
I used:
I9000XWJM1 # (this has the CODE/MODEM/CSC .tar's in a zip file, password needed but on the web page)
Galaxy S / .PIT File: DOWNLOAD. (512)
Odin 1.3
this was helpful, but not a guide to this:
http://www.techlivez.com/2010/07/how-to-upgrade-galaxy-s-to-android-2-2-tutorial/
Thats about the most info I can give you, but I will say (not to be nasty) but I hold no responsibility for a bricked phone, it is easy to do, but appears even easer to brick! the new froyo may be out on the 23 of this month, so maybe wait till then to see if samsung has fixed all the problems, I'm sure you would kick yourself if you bricked it a few day before an update that fixed the problem.

[Q] Need help - My Galaxy Tab SPH-P100 Bricked

​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.

gtabspring said:
​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.

swedishcancerboi said:
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
Click to expand...
Click to collapse
Thanks for the suggestion. I think your version of galaxy tab is different with mine and I am not sure that it will work. I am really desparate for solution. This disaster started when the tab's battery is low and suddenly off and when it's charged and turned on it bricked

Point being, tabs are tabs. You will need to use the same procedure, but a different ROM that is designed for your tablet. Go there and find a ROM. There is a thread about unbricking your tablet, I think in the Android Development section that should have a link to samfirmware.com and may provide you with a ROM version that should work. something that may help: plug your tab into the charger at least overnight. I used the stock charger and cable and charged it for 12 hours or so. I did not get any indication that it was charging since the screen and softkeys would not respond, but it did charge.
Of course, I look back and I think you have an indicator, but still a good idea. Try it anyway. Can't make it worse, eh? Mine seemed hardbricked, but it wasn't. I was real close to taking it apart before I found something that works. I believe, IMO, what really fixed it is flashing ROM (PDA), Modem, and CSC files all at once. It could have been something else, but that was the last thing I did before it finally booted.
Go to samfirmware.com, create a free account, and sign in. Then go here (I think your tab is a P1010, correct?) http://www.samfirmware.com/WEBPROTECT-p1010.htm
and Download this:
1010XWKC1 ## MULTI - CSC - OXXKC1 P1WIFI 2.2.1 2011 March DOWNLOAD
(click on DOWNLOAD)
Unzip that file you just downloaded
Start ODIN
Hold VOL DOWN and plug in tab to computer
I believe 3 files should be in the .rar (you can use 7-zip to open, Google it)
the MODEM file goes in Phone.
the CSC file goes in, you guessed it, CSC
last one is PDA.
I think I just rewrote instructions that can be found in the Galaxy Tab Bible. lol. This is what I would do. It worked for me.

Password for P1000XWJJ7.rar
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.

I'm having the same problem were you able to fix it?

jairo_pena said:
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
Click to expand...
Click to collapse
try sampro.pl
see if that works.

I too require the passwords to be able to extract these files if someone would be so kind.

Copied straight from SamFirmware.com. It is right at the top of the download page.
try both of these... seems it could be either one of them
## Password is samfirmware.com
# Password is samsung-firmwares.com
Click to expand...
Click to collapse

where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website

oxbeast1210 said:
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
Click to expand...
Click to collapse
do a quick search of the dev thread for EA24 and you should be able to find the original SPH-P100 files. then you can find the EB28 and EF17 updates as well to get all the way to the official GB release.

tried the suggested file still get the error that the OP got in the first screen

oxbeast1210 said:
tried the suggested file still get the error that the OP got in the first screen
Click to expand...
Click to collapse
ok, no one likes a bricked device so let's see what we can do to help you. tell us where you are with your problem. by that i mean what model do you have, what rom were you running, what did you do or try to do that bricked your phone. i'll keep an eye on this thread looking for your response and we'll go from there.

I have the sprint p100 model room was stock rooted gingerbread.
I mailed the Tab to my brother when he got it tab battery was
completely dead and after he charged it and turned it on
he had that error
---------- Post added at 01:30 AM ---------- Previous post was at 01:29 AM ----------
thank you very much for helping me!!

can anyone help?

I have the T-Mobile version of this, but here's a guide and download files to recover your stock ROM. You can follow the entire guide if you want the Overcome ROM as well:
Guide:
http://www.teamovercome.net/p1000/?page_id=17
Downloads:
http://www.teamovercome.net/p1000/?page_id=21
Good luck!
NOTE:
Sprint modem is not listed, but you can fix that later. If you can get it to work with this guide & using the last modem file, we can go from there.

gtabspring said:
​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
try the one on teamovercome . net I have soft bricked mine but it worked after i followed their instructions there..

Has anyone EVER confirmed that overcome work for non GSM tab, for unbricking and CwM functions?
Sent from my GT-P1000 using XDA

[GUIDE] Fix an unflashable or soft bricked I9100G

Hello everybody
Due to some demand and request, I've decided to adapt my guide to the I9100G. It deserves some love too!
This is a guide dedicated to noobs, so if you're not one, I would advise to stop reading now! (altough feedback would be great! )
Yes, there have been quite a few threads about fixing a soft brick. But what I'm writting now is another solution to a different kind of problem : unflashable GSII (which also works with a soft brick of course ), which is a soft brick and a corrupted NAND rw (read/write) function.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, regarding NAND rw (NAND's read and write function being the corruption) it means that it is an issue deeper than a soft brick.
It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
BUT UNFORTUNATELY, this guide will not be able to fix a NAND r/w corruption, due to tyhe fact that I do not have either the .PIT, the bootloader or the kernel, I only have a stock ROM, which will only fix a soft brick.
As soon as I get my laptop back from RMA (this Pentium Dual core I'm using right now isn't trustworthy), I'll extract the zImage and sbl.bin from each ROM, zip it, upload it, and add the rest of the guide.
UPDATE 02/05/2012
GOOD NEWS EVERYONE!Thanks to maui75, I have the .PIT and the gingerbread bootloader! When my laptop arrives from RMA, I'll download and unzip all the packages in this thread, add the .PIT, zip, upload again, and add the rest of the guide! ​__________________________________________________
VERY IMPORTANT ANNOUNCEMENT​
I would like to first apologize for my absence. My past months have been super busy, and they don't seem to be ending anytime soon. And "anytime soon" meaning in a couple of years. And I'm actually glad that this is happening, since I've been working pretty hard to achieve the state I'm in.
This thread has evolved into something I've never imagined. Only because of YOU guys, we managed to turn a normal thread into a pretty popular and well used Guide, and it made me so happy and joyous of being apart of the XDA community. I feel proud in being a XDA nut. This whole success is just because of YOU guys.
As painful as it is to say this... I believe that I will be dropping support on this thread after the New Year, because a) I lost my Galaxy S2 in Paris in a taxi with no hope of getting it back when I went there 3 weeks ago and b) I'm probably getting a Galaxy Note 2 in the New Year, so this thread will be most likely ported and maintained over at the Note 2 forums.
I'm extremely sorry it has come this way, and I hope you guys will understand. In the following days I'll be updating the files to their latest versions, and will try to find new bootloaders and kernels, but without sources, I'm unable to do so. I'll update whatever I'll be able to
Regards and thanks to all of you that have supported me,
Rafael K.​
Click to expand...
Click to collapse
________________________________________________
IMPORTANT ANNOUNCEMENT #2
Please welcome neerajganga, your new thread maintainer (along with me)! He has been of great help, so I think he deserves this kind of announcement!​________________________________________________
IF YOU ONLY HAVE A BOOTLOOP​
Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE
__________________________________________________
Let's start with the basic files, downloads and requirements​
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary ROM (they are Gingerbread 2.3.6) : Africa (Iraq), Asia (Malaysia), Europe (Open Austria), Middle East (Saudi Arabia). (password is samfirmware.com)
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
And that is it! Let's get down to business
__________________________________________________
If your GSII has the folowing symptoms :
Bootloop
Stuck on GSII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Enters Download mode but does NOT enter recovery mode (usually means a NAND rw corruption)
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
__________________________________________________
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch
But where are the files going, you say?
.tar -> PDA
__________________________________________________
Recovering a soft bricked phone​
1) Grab the Recovery Package, and put the file in its place.
2) Turn off your phone. Enter Download mode by presing Vol. Up + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9, or other numbers)
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!​
You deserve some cake afterwards, and some rest
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to Intratech and Sammobile, for his amazing gallery of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.

Very good and useful guide. Keep up the good work!

Much simpler
Yesterday i faced a similar problem , i just flashed a kernel and got rid of this problem...

Simple and easy.
I even fixed my Galaxy S2 which was stuck in "Phone-Exclamation-Computer" icon mode. Couldnt even get into Recovery or Download mode.
My phone showed up on Odin so i just flashed it with the stock firmware.
Thanks for the guide!!

When I tried to do a small update via OTA, it got stuck on the Bootlogo.. Did a factory reset, tried to flash via ODIN, but never worked.. Odin just says Checking CS and then closes. It doesn't flash the OS.. Help guys.

WolVish said:
When I tried to do a small update via OTA, it got stuck on the Bootlogo.. Did a factory reset, tried to flash via ODIN, but never worked.. Odin just says Checking CS and then closes. It doesn't flash the OS.. Help guys.
Click to expand...
Click to collapse
What version of ODIN are you using? What fw are you flashing? Have you tried changing cables/use ports?
madbutnotstupid said:
I even fixed my Galaxy S2 which was stuck in "Phone-Exclamation-Computer" icon mode. Couldnt even get into Recovery or Download mode.
My phone showed up on Odin so i just flashed it with the stock firmware.
Thanks for the guide!!
Click to expand...
Click to collapse
No problem!
ashwinsrihari said:
Yesterday i faced a similar problem , i just flashed a kernel and got rid of this problem...
Click to expand...
Click to collapse
Then you just had a corrupt kernel

What version of ODIN are you using? What fw are you flashing? Have you tried changing cables/use ports?
Click to expand...
Click to collapse
The ones found in this very thread only.. Asian firmware. I tried with USB 3.0 USB 2.0 ports, but forgot to try a new USB cable.. It didn't recognise the device i think.
Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9, or other numbers)
Click to expand...
Click to collapse
It didn't happen with my I9100G. Maybe the cable is the culprit.

WolVish said:
The ones found in this very thread only.. Asian firmware. I tried with USB 3.0 USB 2.0 ports, but forgot to try a new USB cable.. It didn't recognise the device i think.
It didn't happen with my I9100G. Maybe the cable is the culprit.
Click to expand...
Click to collapse
Either is the cable, or the USB drivers

TBH i prefer using Toxic Rom to get out of a pickle.

triobot said:
TBH i prefer using Toxic Rom to get out of a pickle.
Click to expand...
Click to collapse
this is for i9100G..not i9100..hihi

triobot said:
TBH i prefer using Toxic Rom to get out of a pickle.
Click to expand...
Click to collapse
ODIN or not, when recovering from a soft brick, it's always better to go stock. It's safer and that can prevent discrepancies between ROMs.
Plus, that's a I9100 ROM, this is the I9100G guide

Odin 1.85 will recognize the phone if it is soft bricked too.
To be updated and have available the original firmware that i want, I verify with "checkfusdownloader". Furthermore, it is faster and easyer than Kies.
It will download the whole files to write with ODIN...

maui75 said:
Odin 1.85 will recognize the phone if it is soft bricked too.
To be updated and have available the original firmware that i want, I verify with "checkfusdownloader". Furthermore, it is faster and easyer than Kies.
It will download the whole files to write with ODIN...
Click to expand...
Click to collapse
Interesting... But does it include a 3-file package, or is it only a 1-file package?

Phistachio said:
Interesting... But does it include a 3-file package, or is it only a 1-file package?
Click to expand...
Click to collapse
...In my case it is only one file .tar.md5

maui75 said:
...In my case it is only one file .tar.md5
Click to expand...
Click to collapse
There we go It's better to flash a 3 part, since sometimes in a soft brick, a single files doesn't pass, but a 3 file pack will.

Phistachio said:
There we go It's better to flash a 3 part, since sometimes in a soft brick, a single files doesn't pass, but a 3 file pack will.
Click to expand...
Click to collapse
I agree with you and in special way for soft brick due to the wrong firmware.
I wish to add the link for all the file ( PIT, PDA, MODEM, CSC, BOOTLOADER, APBOOT) of i9100G CHN KH4, it is a little old but good to repair the chn version.
ht * tp:/ /115.com/file/dnecfzp4
To download the file push the green button... in the begin I had some problem to find all the file for the chn version.... hope will be helpfull

maui75 said:
I agree with you and in special way for soft brick due to the wrong firmware.
I wish to add the link for all the file ( PIT, PDA, MODEM, CSC, BOOTLOADER, APBOOT) of i9100G CHN KH4, it is a little old but good to repair the chn version.
ht * tp:/ /115.com/file/dnecfzp4
To download the file push the green button... in the begin I had some problem to find all the file for the chn version.... hope will be helpfull
Click to expand...
Click to collapse
Oh wow, thanks a LOT! I was looking for the .PIT and the bootloader since always! I'll download the file and upload it to mediafire to facilitate (but that'll only be up when I get home, I'm at school at the moment )
Also, when my laptop arrives, I'll download each package, and add the .PIT so people can have a full recovery (the bootloader will be in a separate download)

Phistachio said:
Oh wow, thanks a LOT! I was looking for the .PIT and the bootloader since always! I'll download the file and upload it to mediafire to facilitate (but that'll only be up when I get home, I'm at school at the moment )
Also, when my laptop arrives, I'll download each package, and add the .PIT so people can have a full recovery (the bootloader will be in a separate download)
Click to expand...
Click to collapse
Great idea...I can not do it, here mediafire does not work
In the begin I did not know the difference from the 9100G and the 9100 so I flashed the wrong rom to root I drived crazy to find the link
Now will be better

maui75 said:
Great idea...I can not do it, here mediafire does not work
In the begin I did not know the difference from the 9100G and the 9100 so I flashed the wrong rom to root I drived crazy to find the link
Now will be better
Click to expand...
Click to collapse
No problem! You already helped me like so much! Thanks a lot again!
It will be better indeed

i9100G ROMS seem to all have different pit files
I ran across a problem while trying to flash the latest ROM from India on a phone bought in China, it always failed at "MSO" and was never recoverable until I flashed back the Chinese ROM, it seems the Indian ROM pack had some different files the Chinese ROM did not have. In short the partitioning appears to be different between some of the ROMS. So is it possible to find the pit files that are connected to each ROM?

[Q] Failing to flash on the actual phone, not odin.

Hey guys, first post. And well, as the video said, I'm a noob!
So I've tried two different guides, but am currently trying to implement this one in different ways.
Now, I do all the steps in order to get the phone connected, which it finds and is successful. I was trying to install the firmware as a single package. Which on the program(odin) side. All goes well.
Now the issue is, which I can't find on the forums or with google. Once the phone boots itself up during the process and the firmware is sent to it. On the screen for a moment I see some debug looking text scroll. It shows 2 folders system/ something. But I can't quite make out the rest as it does this very quick. Regardless, I think it has something to do with access is not allowed? So it quickly skips that and the phone boots up normally. So nothing is installed, and the normal firmware with all the bloatware is just loaded back up.
Odin then just waits a few more minutes and passes it. But obviously nothing happens.
I tried rooting the phone, which was successful. But it didn't help me in attempting the above method again.
I've attempted with odin as well doing what the above guide states as well here "If archive contains only <filename>.tar.md5 select it as PDA and OPS as OPS, leave other fields EMPTY". But in doing so, adding the file to the PDA section, odin reports it's an invalid image type. Then seems all good, but I'm worried in doing it this way, in case I end up bricking the phone.
I been trying to install the firmware "S5830XWKT7_S5830OPPKS6_S5830XWKT3_HOME.tar.md5" Which is the 2.3.6 Australian one.
Any help would be appreciated as to why it's failing on the phone end of things. As the program does seem to issue to use, as it does successfully transfer everything in the first place.
Thanks guys,
Myth.

Frozen Boot Screen, Dead Tablet?

Greetings!
I've spent the past 5 or so hours trying to figure this out, and through much searching on various different forums, I'm entirely stumped. For starters, my 8.9 tablet (GT-7310, 16 GB Wi-Fi) has been on Honeycomb 3.0 since I've gotten it. Today, I had the bright idea of actually taking the plunge into an upgrade and join everyone else in the 4.0+ world. First, it prompted me to upgrade to 3.2 - this went quite smoothly, it was only a 20 MB or so download via Wi-Fi. It booted up, no problem. Then, it prompted me for a second upgrade, which was quite large, in the 300+ MB range. I downloaded this, rebooted, and now my Galaxy Tab won't progress beyond the boot screen. It was like this for hours. Tried a factory reset/cache wipe and I still have the same problem.
So, it appears that my tablet may have tricked me into assisting its suicide. What's more, I can't connect it to my PC because it won't recognize it, and the MTP USB driver always fails. For that problem I've tried everything from editing reg keys to renaming system files to test it (I'm on Windows 7 Ultimate 64-bit) Nothing. This thing is a brick, and I'm starting to have an epiphany that I may have made a grave mistake. Is this salvageable at all? All I wanted was to get this thing on at least ICS. Is it possible to somehow get the files needed on my tablet via flash drive and install it that way? Where would I go about getting such files needed?
I apologize for spilling all of this, but I guess its tough to swallow a fleeting $400 spent. I eagerly await any sort of response or help, thank you in advance!

If out boots at all it's salvageable. Not have the pc recognize it though could be a problem. Have you tired odin? See if odin will recognize it and if so flash the stock ics firmware. You can get it at sammobile.com. you'll download a zip file and extract the.tar.md5 file from it using 7-zip.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Well, I'm a bit relieved that Odin does in fact recognize the device, but every time I connect it, the device driver (MTP) won't successfully install, so Kies won't recognize it at all (though from what I gather on this forum, Kies is kind of an incompatible waste of time) I went to that site but couldn't find firmware for my model tablet (GT-P7310, United States) but found several for other countries. What steps do I take next?

WarrenOfSnares said:
Well, I'm a bit relieved that Odin does in fact recognize the device, but every time I connect it, the device driver (MTP) won't successfully install, so Kies won't recognize it at all (though from what I gather on this forum, Kies is kind of an incompatible waste of time) I went to that site but couldn't find firmware for my model tablet (GT-P7310, United States) but found several for other countries. What steps do I take next?
Click to expand...
Click to collapse
Well that's interesting? I looked too and there is no usa. Try samsung-updates.com
Edit, that doesn't look like its gong to work either. Is it an att device?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

It's not an AT&T device, it's a wireless tablet, from the first run of 8.9 tabs. It came stocked with Honeycomb 3.0 originally. The model number on the back of the device is GT-P310MA, FFC ID: A3LGTP7310.
Also, I gave Odin a go. While it recognized the device, it kept failing when I tried to use the PIT file.
This is the screen I've been stuck on for hours, the good news is that I can hold down left and power and go into that mode, but it doesn't do much of anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nothing good comes with messing with a pit file. I'd download the UK stock firmware for the 7310 and flash that in PDA In Odin. Only have auto-reboot checked. Don't know for sure if it'll work and you're on your own on this.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

I didn't mess with the pit file, only followed instructions based on a tutorial I found in the forum. It's in the same shape as it was before. I did your suggestion in Odin however, and this is what I'm working with:
I don't think my PC is reading the tablet properly, but really I have no idea.

Keep trying it. I've had to do it multiple times and for whatever reason it finally worked.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

WarrenOfSnares said:
I didn't mess with the pit file, only followed instructions based on a tutorial I found in the forum. It's in the same shape as it was before. I did your suggestion in Odin however, and this is what I'm working with:
I don't think my PC is reading the tablet properly, but really I have no idea.
Click to expand...
Click to collapse
It may also help to try a different usb port, cable, or computer.

This one was a doozy, but I finally got it to work! I had more options within my tab than I thought I did, and what's more, I got to upgrade to ICS from Honeycomb. Just had to tweak a few settings in recovery mode. D'oh! Anyway, thanks to all of you, you had the right answers, there was clearly just an option I was overlooking myself!

WarrenOfSnares said:
This one was a doozy, but I finally got it to work! I had more options within my tab than I thought I did, and what's more, I got to upgrade to ICS from Honeycomb. Just had to tweak a few settings in recovery mode. D'oh! Anyway, thanks to all of you, you had the right answers, there was clearly just an option I was overlooking myself!
Click to expand...
Click to collapse
Explain what you did exactly maybe to support others with the same issue???