Following this tut;
http://forum.xda-developers.com/showthread.php?t=1125414
Step 5: Connect your device to your PC and start Odin3 v1.83. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
I cant get there, it doesnt go yellow. I have kies installed correctly, not sure whats wrong
New to rooting btw
However i do get this error come up;
screensnapr.*com/e/ZXruBp.png
xSirAKx said:
Following this tut;
http://forum.xda-developers.com/showthread.php?t=1125414
Step 5: Connect your device to your PC and start Odin3 v1.83. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
I cant get there, it doesnt go yellow. I have kies installed correctly, not sure whats wrong
Click to expand...
Click to collapse
Try this guide - it is tried and tested. http://forum.xda-developers.com/showthread.php?t=1075278
Cheers!
Now its working but it shows FAIL
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> PK
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Did you make sure you are in Download mode, and the drivers were installed correctly? Also, did you make sure you added the kernel file in the correct section? (without ticking any unnecessary things)
Yes.
Now it wont switch on.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Did you tick the PIT box?
Edit - sorry, just reread, you haven't. I hope..
No i didn't. I restored the original firmware but it still wont turn on normally.
Did you have kies running in the background? Make sure you end all kies applications - end process
Nope had shut kies.
Could be a cable failure. Try a different USB cable.
I only have 1 cable. I restored the kernels and it went green that it worked. But my phone doesn't work.
xSirAKx said:
I only have 1 cable. I restored the kernels and it went green that it worked. But my phone doesn't work.
Click to expand...
Click to collapse
You can get a new USB cable for a couple of bucks. I've got like 6 due to all the devices I've had over the years, and 2 of them are bad. They don't last forever.
Managed to restore device using tutorial i found on google androidcute.*com/install-android-2-3-6-gingerbread-for-samsung-galaxy-s2.html
after restoring i decided to give rooting another go.
all worked out fine, i installed rom manager after and it keeps rebooting itself after every few mins
i have cpu tuner installed too i also restored the original kernel after rooting.
xSirAKx said:
after restoring i decided to give rooting another go.
all worked out fine, i installed rom manager after and it keeps rebooting itself after every few mins
i have cpu tuner installed too i also restored the original kernel after rooting.
Click to expand...
Click to collapse
ROM Manager is the devil. I don't think it plays well with CWM. How are you rooting? If you root using a CF-Root kernel, it will auto-install the CWM app, which I believe does everything ROM Manager does.
I used S2 Root, i uninstalled rom manager though.
xSirAKx said:
I used S2 Root, i uninstalled rom manager though.
Click to expand...
Click to collapse
Is it still rebooting?
Sent from my GT-I9100 using XDA App
It was fine the past 3 hours but its just rebooted again 2 twice in the last 10mins.
xSirAKx said:
It was fine the past 3 hours but its just rebooted again 2 twice in the last 10mins.
Click to expand...
Click to collapse
Last time I had this issue, it was some app I installed, but I couldn't figure out which one. I flashed back to stock and was more selective in which apps I chose to reinstall. I've also made sure that all the apps are on phone memory instead of SD card as there was some speculation flying around that this could also contribute to this issue. Haven't had a random reboot in months now.
Related
Hey I've searched for more help but I am stuck.........
So i got a samsung fascinate for verzion.
Ran the 'One click root' ,... I have superuser
currently on DI01 and want to get to DL09
I am now trying to install clockworkmod ....
following directions from here http://forum.xda-developers.com/showthread.php?t=788099
:::
Put phone into download mode.
-Turn off phone
-Pull battery
-Press vol down button while plugging into computer
-Should show a yellow triangle
Open odin on pc
-Odin should show a yellow bar with a com port showing that it detects your phone
Click "PDA" button and select the CWMrecovery.tar you downloaded earlier
Click start
I keep getting this error
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I have rebooted my PC, tried different clockwork files [CWMrecovery.tar and CWMRecovery_DJ05_DL09.tar.md5]... searched here, read a lot of instruction, searched google and other fourms but I can not find any thing on the 'Can't open the serial(COM) port' error
i have tried with Debugging mode turned off and get the same error.
....anyone have any ideas to help?
I have flashed many roms, radios and programs to my current phone so I don't feel I am a complete noob, but this is frustrating me...I like to think I can figure most things out and this temporarily kicked my butt....and I don't like it
.
hhp_211 said:
Hey I've searched for more help but I am stuck.........
So i got a samsung fascinate for verzion.
Ran the 'One click root' ,... I have superuser
currently on DI01 and want to get to DL09
I am now trying to install clockworkmod ....
following directions from here http://forum.xda-developers.com/showthread.php?t=788099
:::
Put phone into download mode.
-Turn off phone
-Pull battery
-Press vol down button while plugging into computer
-Should show a yellow triangle
Open odin on pc
-Odin should show a yellow bar with a com port showing that it detects your phone
Click "PDA" button and select the CWMrecovery.tar you downloaded earlier
Click start
I keep getting this error
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I have rebooted my PC, tried different clockwork files [CWMrecovery.tar and CWMRecovery_DJ05_DL09.tar.md5]... searched here, read a lot of instruction, searched google and other fourms but I can not find any thing on the 'Can't open the serial(COM) port' error
i have tried with Debugging mode turned off and get the same error.
....anyone have any ideas to help?
I have flashed many roms, radios and programs to my current phone so I don't feel I am a complete noob, but this is frustrating me...I like to think I can figure most things out and this temporarily kicked my butt....and I don't like it
.
Click to expand...
Click to collapse
Have you tried a different USB port? Also re-installing the drivers might work.
Hope it helps, Good luck.
Your drivers up to date?
Sent from my SCH-I500 using XDA App
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
EDIT:
To be a tad more specific:
Download the odin patch again two more times. Either make sure you can unpack the tar, check the corresponding md5sums, or simply look at the file byte sizes to see if two are identical. Odin really freaks out if you give it bad files.
That is a good thing! Far better that than flash bad data to your pda.
Swyped w/ XDA App. When in doubt, mumble.
uslacson1 said:
Have you tried a different USB port? Also re-installing the drivers might work.
Hope it helps, Good luck.
Click to expand...
Click to collapse
zachsx said:
Your drivers up to date?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hey thanks for quick responses.
I currently have the 'Samsung_Mobile_USB_Driver_V1.3.550.0_SCH-i500_Fascinate.msi' Driver installed
I believe I had installed SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe before when I was trying to get it rooted.
I have not yet tried a different USB port... I will and get back to you...
soba49 said:
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
I have downloaded 3 different times both files, so I don't know ????
different USB port ... same result...
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
soba49 said:
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
EDIT:
To be a tad more specific:
Download the odin patch again two more times. Either make sure you can unpack the tar, check the corresponding md5sums, or simply look at the file byte sizes to see if two are identical. Odin really freaks out if you give it bad files.
That is a good thing! Far better that than flash bad data to your pda.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
When you say odin patch I guess you mean the 'CWMrecovery.tar'
I can unpack it and I have a 'recovery.bin' and a 'zImage' inside the file.
both 5081 KB in every 'CWMrecovery.tar' that I have.
Weird. My old copy from Nov. 26 is 9.93MB (10,414,130 bytes). It contains zImage and recovery.bin, each 5,202,168 bytes. I must be wrong, then.
EDIT:
Just for sake of good practice, I did look up the md5 for that file and I did download it again, and they do match. There are a lot of ways to get MD5s, I used a program called digestIT 2004 to generate it.
http://goo.gl/HELdr
ecfeb7b1633786c1ae9dfb276bfeb231 CWMrecovery.tar
I had no problems downloading it, the hosting is good. It's highly unlikely that I was right about resolving your Odin error.
Sorry I can't be more helpful. I did this once way way back when and had no issues. I did have an issue with a modem.bin packed in a tar later on, and the errors looked a lot like what you are getting now, so I assumed it was the same problem. Thanks for humoring me, and good luck.
I'm a nub.. help..
So I've been trying to follow directions here, but I feel I'm missing something very simple... I cant even get this restore started, it keeps telling me "Invalid Image Type" when i select the CWMrecovery.tar file?? help??
it could be that Kies, or other application that uses USB connection is active.
Getting an issue with Odin and upgrading to XWKE7 oh and kies is off as well unless there isnt a similar service name running in the background?
CWP UK: http://www.multiupload.com/U1WNFZ88L0
MD5: A5A59AE6374C7FC814E8901B40F7C8AA
followed the guide here and for some reason it keeps coming up with "Fail" heres the log from the left
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
any ideas ???
to note when I go into download mode it says downloading straight away dont know what its meant to say on the screen as Ive never used odin before
Thanks
anything ?
Follow the instructions to the letter you are doing something wrong .
jje
I have thats what I cant understand I will uninstall kies and give that a whirl
Try to restart computer, sometimes that helps. Hope you sort it.
Sent from my GT-I9100 using XDA Premium App
^^ Tried that alas to no avail
So I decided to spend a little 5 minutes to myself at work and decided to do it on my works laptop but it wouldn't recognize the gadget driver so I downloaded mini kies as suggested on another thread and again that didnt work, So I got the Samsung USB driver exe from one of the other guys computers in my office who has the Galaxy S and has a full version of kies (located in C:\Program Files\Samsung\Kies\USB Driver\) installed that and then followed the steps again from the previous guide and jobs a goodin.
I cant understand why it doesn't work on my home PC, all I can think of is that there is something running in the background, either my AV that's not alerting me or some silly service I have stopped or is running
PEBKAC
Hello,
since a few days my GT-P7510 reboots suddenly and falls back into the status before last reboot. That means all settings, copied files/apps are gone and all deleted files/app are restored. It looks like my memory is somehow frozen in a specific status from a few days ago.
I didn't try to root it or something like that. It start all of a sudden.
Thats what I tried so far to solve the problem:
1.Hard Reset with normal method and factory reset with the bootloader (Power button and Volume down menu). No effect at all.
2. Try to root my tab with the manual from this forum. I'm able to flash cwm. At least odin gives no error. But when I reboot cwm isnt flashed. The normal bootloader appears again. So, I have no chance to wipe my tab on this way.
3. Flash stock rom via Odin. That's when I get a Error-Message from odin an my Tab. Error-Message: http://imageshack.us/photo/my-images/822/camerazoom2012062021092.jpg/ But I dont know what it means and havent found it out so far.
I tried several stock roms, read several forums, google etc but no one seems to have a real solution.
I found one guy here http://www.galaxytabforums.net/forum/galaxy-tab-10-1-general-discussions/4260-my-gt-useless-impossible-hard-reset-delete-create-files-etc.html and one guy here in this forum: http://forum.xda-developers.com/archive/index.php/t-1576134.html who have similar problems. But as I said nothing helped yet.
Btw, the data on my tab isnt important so I wouldnt have any problem with a solution which wipes everything. The main thing is that my tab is working properly again. Hopefully one of you experts has an idea.
Thanks in advance
This is pretty weird. Maybe your filesystem is corrupted. You may try to flash a .pit file first. But it could well be a h/w problem. If it's under warranty sent it to Samsung.
Sent from my amazing 10.1 galaxy tab
I tried it with this pit-file: android_fastboot_emmc_full_p4_16G_32G.pit
But I'm not quite sure if its the right one.
In connection with this ROM: P7510XABKMP_P7510UEKMP_HOME.tar, I got those error messages:
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.img
<ID:0/009> NAND Write Start!!
<ID:0/009> bootloader.bin
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And in red on my tab:
Bct_sync_Odin: Error toNvBuBctUpdate![Err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DowloadPartition_Odin![err:0x140005]
Buildnumber of my tab is HTJ85B.UEKMP P7510UEKMP. So it should be right ROM?
From what I know, you should first use the pit without the rom. Then flash the rom. You should also try a different usb port on your pc and the tab shouldn't be in a dock or a usb hub. That's one of the reasons the flash fails.
Hello everybody!
First of all, I'm not sure about my english skills...please have mercy on me :fingers-crossed:
Here I go:
I got my S3 in August/Sept with a T-Mobile Branding. My first action was getting it rootet and flashed with an official Samsung Rom just to get rid of the branding.
Two days ago I woke up to my charging S3 only showing the "Samsung..." Bootlogo. Removed the battery, nothing changed. Tried the Volume up-HomeButton-PowerButton Combo and it only resulted in a blinking logo (the logo disappears for a few seconds). The only thing I have access to is the Download-Mode.
What I tried since then:
Flashing a new one-part-rom with Odin, this was the result:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003>*Odin*v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!*
<ID:0/003>*
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Same with a three-part-rom.
Then I tried to downgrade the bootloader with ADB. But I don't get the drivers (Universal-Naked-Drivers) running. The S3 shows up as "unknown device" at the device manager but it doesn't want to be updated with the right drivers. PdaNet also refused to install USB-Drivers.
It's like they don't recognize the S3.. Perhaps I don't have USB-Debugging enabled? I'm not sure about this, because this brick just happened from one day to another.
I installed and uninstalled the "normal Samsung USB-Driver for mobile phones" often while trying to get the other drivers running. When installed, the S3 showed up in the device manager as one of the USB-Controllers.
Installed Kies for a factory reset but it didn't recognize the S3..
This shows up in Download-Mode:
ODIN*MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
I guess it's no sudden death because it shows the product name? Also I have no idea why it has three flash counts, I just flashed it once seven month ago.
Since I never updated to Jelly Bean the S3 was running on ICS 4.0.4
Edit:
Next steps I tried:
Flashing with an older version of Odin (v.1.85) But also failed at <ID:0/003> Complete(Write) operation failed
Flashing CF-Root v.6.4 to get the recovery mode back. Failed at <ID:0/003> Complete(Write) operation failed
Flashing Resurrection Odin CheckRom EvoHD v.4. Failed at <ID:0/003> Complete(Write) operation failed
Repartition with 20120329.pit and mx.pit. Failed at <ID:0/003> Complete(Write) operation failed
I'd still appreciate any kind of help or feedback!
It sounds like partial nand failure or simple partition corruption. Search here in q&a for solutions to repartition, but if that fails then your nand is probably toast.
try flashing a pit file
not sure if it will help but..
connect it to computer..when it fails to install drivers..Turn off and Pull battery out for few secs restart..
sometimes this helps to reinstall drivers..not sure in your case of a bootloop though?
Thanks for your answers!
I tried to repartition with a PIT-File but it didn't work.
At first I tried the GT-I9300_mx_20120329.pit with this 3-part-rom:
CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
But the same error appeared.. also the error appeared so fast I don't think there happened a repartition at all?
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Second try was 3-part-rom recommended with the mx.pit-File:
CODE_I9300XXALEF_611327_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLEF_REV02_REV04_CL1147871.tar.md5 is valid.
CSC_OXF_I9300OXFALEA_613742_REV00_user_low_ship.tar.md5 is valid.
With the same result...
It's always the same error, again and again...
Any further ideas?
you are done
Only two answers one wrong PIT or partition damaged .
Two Nand damaged see how much will a new motherboard cost .
jje
Thanks again!
With the GT-I9300_mx_20120220.pit-File I got my S3 responding for the first time since it died. It showed the blue loading-bar, but it didn't move at all and Odin stopped at <ID:0/004> NAND Write Start!!
Tried this rescue-version http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 with mx.pit but of course it didn't work..
you are done
Click to expand...
Click to collapse
seems like you're right, unfortunately..
But if you have ANY idea what I could try, please post it.
Are you sure it's a NAND damage or could it be a bootloader problem? I found this thread: http://forum.xda-developers.com/showthread.php?t=1916796 but I don't understand what they are talking about yet.
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Possible Solution
xylakant said:
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Click to expand...
Click to collapse
I had a similar problem, my phone just froze in the middle of a phone call, had to pull out battery, and when i tried to turn it on, it wouldn't pass the second "SAMSUNG" logo, just stayed there forever, with the blue light (Official JB 4.1.2 - not rooted)... Anyway, after 3 days of trying, downloaded bunch of firmwares, but all of them gave me the infamous "Complete(Write) operation failed". This is how I MANAGED to revive my i9300 16Gb Int:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
2. Click on the "Reset" button in Odin (or close and re-open it), in PDA select "recovery-cwm-touch-6.0.1.2-i9300.tar", make sure only "F.Reset Time" and "Auto Reboot" are checked, and flash it. If everything goes OK, you should now have CWM instead of Stock recovery.
3. Take any microSD card, any size, and put THIS file on the root of the microSD using a card reader or whatever you prefer - but be careful, copy the zip as it is - do not unzip it.
4. Insert the memory card in the phone, enter recovery*, and select "Install zip from External Storage" and choose the file you put on the root of the card (by the way, it's a 4.0.4 downgrade bootloader), it should flash in a second, the phone will restart, and that's it!
5. Download and flash 4.0.4 Stock FW using Odin (i used "I9300XXBLH1_OXEBLF1.zip"), everything should go OK, and the phone will be bootable again.
*(my phone didn't wanted to enter recovery the old fashioned way using 3-button combo, but i managed to enter recovery from charging mode, by connecting the charger on a switched off phone, and as soon it starts charging press Vol Up + Home + Power, and when the FIRST Logo (Galaxy S III GT-I9300) appears, let go of the power button, keep pressing the Vol Up + Home, and it enters recovery).
ATRAC3 said:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
Click to expand...
Click to collapse
Odin Stuck at "Set Partition" ^^
"<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
Help ?
Did you give it the pit file? Pit is really a last resort AFTER you've ruled out sending for repair
Sent from my GT-I9300 using Tapatalk 4
I have the pit file and Checked the Box ^^
MrFraggii said:
I have the pit file and Checked the Box ^^
Click to expand...
Click to collapse
Correct PIT file ??? for your phone ??
Flashing PIT 99% kill the phone .
You require a service centre .
Warranty will depend upon their report .
jje
Have the right Pit file ^^ But odin Stuck at Set mapping
MrFraggii said:
Have the right Pit file ^^ But odin Stuck at Set mapping
Click to expand...
Click to collapse
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
JJEgan said:
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
Click to expand...
Click to collapse
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
tris16 said:
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
Click to expand...
Click to collapse
Your sense of entitlement is awe inspiring, if you searched and read you would find many people who flashed pit files to fix just a soft brick and then had to pay for a new motherboard.
So no, we won't help people wreck their phones.
Pit Files
tris16 said:
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
Click to expand...
Click to collapse
This is where i got mine.
http://forum.xda-developers.com/showthread.php?p=30547929
I've been trying to convert the firmware on my M250S to I9100. I've followed the guide to the letter and all the drivers are installed as well as Kries. I also made sure Kries was inactive while Odin was up. This is how far I get before it fails.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If anyone has any ideas I would appreciate it. I've tried everything I can think of including using different firmwares, pits, as well as versions of Odin. That's as far as I get before it fails.
How are you trying to do it? As I recall (I don't have an M250 so didn't pay crazy attention) there's two ways to convert one to an i9100. One involves Odin failing intentionally. Although, the method involving a pit file doesn't intentionally fail. If you're flashing pits and they're failing that's definitely not good... Potential brick.
Search for a guide in the s2 general section, I read one a couple weeks back which members were using with success.
You can also click the link in my signature and follow the steps there. As you're not doing a 'regular' Odin flash bear in mind some things will be a little different.
Sent from a galaxy far, far away
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Edit: I tried another computer and it worked flawlessly. So now I'm running on i9100. Although I'm having a few issues. It doesn't show my battery charging when the usb is plugged in. Also when I shut down my phone it doesn't completely shut down. It goes to a screen with a green battery. This actually happened before but I thought perhaps changing firmware would fix it. Before this the device would come back on automatically when I tried to shut it down and I read it could be the usb port so I cleaned the usb port with alcohol.
Slywolf15 said:
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Click to expand...
Click to collapse
Ah so it may not be a case of what you're trying to do, it might be a case of how the flash is set up/what hardware (pc, cable etc) you're using. In that case, use the link in my signature to troubleshoot it. Perseverance is key. Also have a look here : http://forum.xda-developers.com/showthread.php?p=45131292
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
ZivC12 said:
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
Click to expand...
Click to collapse
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Slywolf15 said:
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Click to expand...
Click to collapse
it happened to me with bad uk unbranded rom, try to flash new rom, if you cant turn on the phone switch battery