Hi Guys,
I got a problem with my Samsung Galaxy S SCH-I909
First I have tried changing it's ROM to a different one. It failed. My SGS won't turn on at all anymore. No phone,!,computer sign at all, BUT CAN still go to the Download mode.
I've tried flashing it again with the ROM for SCH-i909 itself(SCH-i909_DI13). But still it keeps on failing.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Enter CS for MD5..
<ID:0/003> Leave CS..
<ID:0/003> Enter CS for MD5..
<ID:0/003> Leave CS..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried doing it with repartition pit 512 and without repartition and to no luck. Does this mean that my phone is totally bricked? Hope somebody can help.
Thank yoU!
I got similar problem on my Galaxy S.
When Odin is on factory.rfs screen on my phone is turning blue and thats all!
Stuck on it.HELP!
I'm having the same problem and haven't been able to find a solution yet. Anyone have any ideas?
Related
Hi,
my girlfriend just came back from China with a P1000 from her friend. As the whole device was running on chinese language and for some strange reason it was not possible to enter System Setting to change the language, I decided to flash her the latest firmware and just make a fresh start. (i'm a flash veteran on my SGS since 2 years, so I know how to use Odin)
I downloaded the P1000XWJQ8 from Sammobile, fired up Odin and flashed the new ROM with repartition enabled.
The procedure went through without errors:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJQ8_P1000XXJPZ_P1000DBTJQ1_HOME.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> cache.rfs
<ID:0/003> hidden.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
At the end of it the device didn't auto-boot as expected, it just stayed there with a black screen!!!!!!
Disconnecting and reconnecting it triggers in Odin the REMOVED and the ADDED lines but nothing happens.
I cannot switch on, cannot go into download nor recovery, the device just seems to stay dead :-(
My next idea was trying to pull the battery but apparently the battery is glued to the casing, so before I do more damage, I better start asking here.
Hope someone can help, my girlfriend will kill me if I can't repair this damn thing...
EDIT: after having closed Odin on the PC I tried to connect the device again and it started to play the startup song and Win7 started to install the new drivers from the new firmware. 7 out of 9 found drivers installed correctly, 2 instead failed.
But nothing changed to the vegetarian state of the P1000
EDIT 2: now, after 12 hours wait, the device doesn't do anything anymore when I connect it to the PC, no USB connect, no sign of adding it in Odin. It seems like the charging mechanism doesn't work anymore either. The deivce appears totally dead.
Did you see my thread http://forum.xda-developers.com/showthread.php?t=1769144? This problem is totally the same as mine.
Is yours rooted? Coz it says here http://www.teamovercome.net/p1000/?page_id=17 that :
[REQUIRED FOR FROYO-BASED TABS ONLY:] Your Tab must be rooted. (Please look for SuperOneClick root method as it’s usually the safe bet! But for more information on rooting, please refer here: http://forum.xda-developers.com/showthread.php?t=812367)
Click to expand...
Click to collapse
I hope someone can help us, or else, no choice but to bring this to service center.
itenos said:
Hi,
my girlfriend just came back from China with a P1000 from her friend. As the whole device was running on chinese language and for some strange reason it was not possible to enter System Setting to change the language, I decided to flash her the latest firmware and just make a fresh start. (i'm a flash veteran on my SGS since 2 years, so I know how to use Odin)
I downloaded the P1000XWJQ8 from Sammobile, fired up Odin and flashed the new ROM with repartition enabled.
The procedure went through without errors:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJQ8_P1000XXJPZ_P1000DBTJQ1_HOME.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> cache.rfs
<ID:0/003> hidden.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
At the end of it the device didn't auto-boot as expected, it just stayed there with a black screen!!!!!!
Disconnecting and reconnecting it triggers in Odin the REMOVED and the ADDED lines but nothing happens.
I cannot switch on, cannot go into download nor recovery, the device just seems to stay dead :-(
My next idea was trying to pull the battery but apparently the battery is glued to the casing, so before I do more damage, I better start asking here.
Hope someone can help, my girlfriend will kill me if I can't repair this damn thing...
EDIT: after having closed Odin on the PC I tried to connect the device again and it started to play the startup song and Win7 started to install the new drivers from the new firmware. 7 out of 9 found drivers installed correctly, 2 instead failed.
But nothing changed to the vegetarian state of the P1000
Click to expand...
Click to collapse
MarlX said:
Did you see my thread http://forum.xda-developers.com/showthread.php?t=1769144? This problem is totally the same as mine.
Is yours rooted? Coz it says here http://www.teamovercome.net/p1000/?page_id=17 that :
I hope someone can help us, or else, no choice but to bring this to service center.
Click to expand...
Click to collapse
hey guys, are sure your gtab is P1000??
see the back cover, and chek your gtab model to make sure.
qm4n76 said:
hey guys, are sure your gtab is P1000??
see the back cover, and chek your gtab model to make sure.
Click to expand...
Click to collapse
Yes, 100% sure, my one is a P1000. As wrote in EDIT2 my device now seems to be totally dead
Hey guys need a little help here, i just bought a motherboard for my girlfriends s5, the old one seemed to overheated and died, yeah seriously. was just sitting on the bed.
I just spent $100 to get an AT&T Mobo, cracked open the phone and installed it. (The LCD is really thin, but to my suprise is really strong)
Stock Android 5.0 L, tried to to downgrade to 4.4.4, realize i cant now because of locked bootloader. trying to just restore back to Android 5 now.
Recovery mode presents " Firmware upgrade encountered an issue, Please select recovery mode in kies"
Download mode presents " SW Rev Check Fail : [aboot] fused > 4 Binary 3 "
I suppose this is because i flashed 4.4.2 in Odin the following
AP, CP, CSC
BL was NOT flashed!
Currently tried to find BL, AP, CP and CSC for 5.0 L, figure it would solve the problem
However my google-fuu leads me no awnsers, Closest thing i could find was.
theandroidsoul dot com /att-galaxy-s5-lollipop-update-odin-firmware-80652/
looks like it will flash 5.0 software, but.
My odin fails everytime i try, I have tried this on two computers, Windows 7 & 8
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
I really dont think its a driver issue., tried multiple cables.
Thanks
Recently I installed Clockwork Mod on my sisters Samasung Galaxy I8190N and attempted to flash lollipop on it. Much to my disappointment somewhere in the process I failed. Now when the phone boots I see the lollipop loading animation, but it goes no further during the boot. I can no longer access the Clockwork Mod recovery with up+power+home button. But can still access the download mode. So I tried to reinstall the 4.1.2 using odin, however with odin I get the following error when trying to flash using the PDA/AP:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> modem.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone (in download mode) it says Custom Modem Binary installed.
Any help in getting my sisters phone back to how it was before she gave it to me (default 4.1.2) would be greatly appreciated!
Edit: I realise after posting that this would of been better in the troubleshooting forum, apologies for that.
Factory reset or flash original firmware from sammobile
Hi all,
Samsung Galaxy S3 - GT-I9305. After the OS patch was getting a few issues like system randomly resting, security block popups on some apps when there never was before. One night however woke up and the phone was powered down. Now only powers up only into Samsung Logo bootloop. Cant enter recovery mode, just goes into the loop. I've got 2 ROMs from SAM mobile for my carrier, one older and one recent, as i'm unsure what my ROM is and cant check it now. Both however fail with Odin. Log listing below.
Have tried different ports, using original cable. Ideally would like to get my data back as pictures and contacts were not backed up.... Please help! Pretty desperate and haven't really found anything in forums for this situation.
Odin logs;
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
TWRP
Hello and thank you for using Q/A,
can you please try flashing TWRP via AP:
twrp-2.8.7.0-i9305.img.tar
And then please try to boot into TWRP using the known combination. Tell me, if your I9305 is booting into TWRP then.
Regards
Trafalgar Square
Thanks for reply. I tried on Odin3 1.87 and 3.10.7 both fail; log
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Option selected auto reboot via AP.
:crying:
Any other suggestions?
The thread is dead, but in case anyone is coming across the same sort of problem.. i bit the bullet and took it to a service tech. They couldn't fix it and had to replace the motherboard. So unfortunately that was the solution for me anyway. :crying:
ok so we both have note 4s and i rooted both of our phones many months ago. i put poprocks v.13 on both phones and everything worked out fine. well over time that rom became outdated so i decided to update the phones. i updated mine to N910TUVU2EPE3_N910TTMB2EPE3_N910TUVU2EPE3_HOME.tar modem and the overdrive rom. had a few hick ups but over all went fine and my phone works great. so i decided to upgrade hers tonight. i put her phone into download mode and started odin. loaded the N910TUVU2EPE3_N910TTMB2EPE3_N910TUVU2EPE3_HOME.tar.md5 and hit start. well it failed and now the phone wont do anything. no matter what i do in odin it fails. ive tried cf-auto root it fails to. phone under download mode says blocked by r/l. odin usally stays stuck on setup connection. any ideas how to get this thing working again before she kills me?
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<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..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Delete the .md5 and just leave it as .tar
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
assuming you ment delete the md5 from the name of file. it didnt work.
just tried cf-root with odin on her laptop and same result. seems like this phone is a paperweight. im completely dumb founded. we have the exact same phones and i did hers the same way as mine. hers failed on the first step and now it looks like im buying her a new phone. this thing wont do anything at all. it can go into download mode but no matter what you try to load through odin fails.
osiris999 said:
just tried cf-root with odin on her laptop and same result. seems like this phone is a paperweight. im completely dumb founded. we have the exact same phones and i did hers the same way as mine. hers failed on the first step and now it looks like im buying her a new phone. this thing wont do anything at all. it can go into download mode but no matter what you try to load through odin fails.
Click to expand...
Click to collapse
Do you use hangouts (google) or Skype (chat)?
It seems it would be easier to help via one of those mediums.
osiris999 said:
just tried cf-root with odin on her laptop and same result. seems like this phone is a paperweight. im completely dumb founded. we have the exact same phones and i did hers the same way as mine. hers failed on the first step and now it looks like im buying her a new phone. this thing wont do anything at all. it can go into download mode but no matter what you try to load through odin fails.
Click to expand...
Click to collapse
Dupe
I was finally able to fix this thing using Samsung smart switch emergency recovery.
osiris999 said:
I was finally able to fix this thing using Samsung smart switch emergency recovery.
Click to expand...
Click to collapse
Glad you got it working. Looks like reactivation lock was turned on on hers but not yours. I always keep it off on my devices as I would forget to check.
Sent from my SM-N910T using XDA Free mobile app