[Q] Odin gets stuck while flashing - Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl

I tried to flash my Galaxy Y with Odin but it always gets stuck at 'boot.img', after which I power off the phone. The phone is working fine but even after repeating the process the same thing happens. What should I do?

entermetallica said:
I tried to flash my Galaxy Y with Odin but it always gets stuck at 'boot.img', after which I power off the phone. The phone is working fine but even after repeating the process the same thing happens. What should I do?
Click to expand...
Click to collapse
Dude this problem related with flashing kernal which kernal u hav inastalled.
Sent from my GT-S5360 using xda app-developers app

[email protected] said:
Dude this problem related with flashing kernal which kernal u hav inastalled.
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
I haven't installed any kernel.

entermetallica said:
I tried to flash my Galaxy Y with Odin but it always gets stuck at 'boot.img', after which I power off the phone. The phone is working fine but even after repeating the process the same thing happens. What should I do?
Click to expand...
Click to collapse
just simply disconnect your phone, put off your battery, put in your battery again, enter download mode, and try to flash again

May be Kies interfering
this may be due to kies interfering with the COM connection... you check by pressing Ctrl+Alt+Del and end each Kies process through task manager and try flashing again...

Catalyste said:
this may be due to kies interfering with the COM connection... you check by pressing Ctrl+Alt+Del and end each Kies process through task manager and try flashing again...
Click to expand...
Click to collapse
Also all adb connections must also be stopped
Sent from my GT-S5360 using xda premium

Similar issue here guys.. My phone was stuck at the boot image after rebooting from a custom ROM (JellyBlast 3.0), I couldn't get into recovery mode as well. In download mode Odin (1.84 and 1.85) detects the phone and while trying to flash with stock DDLF2 I get the below:
<ID:0/048> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360DDLF2_S5360ODDLF1_S5360DDLF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/048> Odin v.3 engine (ID:48)..
<ID:0/048> File analysis..
<ID:0/048> SetupConnection..
<ID:0/048> Initialzation..
<ID:0/048> Get PIT for mapping..
<ID:0/048> Firmware update start..
<ID:0/048> sbl.bin
<ID:0/048> BcmCP.img
<ID:0/048>
<ID:0/048> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what might be wrong - all drivers are installed and Kies is not running.

xdroid_noob said:
Similar issue here guys.. My phone was stuck at the boot image after rebooting from a custom ROM (JellyBlast 3.0), I couldn't get into recovery mode as well. In download mode Odin (1.84 and 1.85) detects the phone and while trying to flash with stock DDLF2 I get the below:
<ID:0/048> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360DDLF2_S5360ODDLF1_S5360DDLF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/048> Odin v.3 engine (ID:48)..
<ID:0/048> File analysis..
<ID:0/048> SetupConnection..
<ID:0/048> Initialzation..
<ID:0/048> Get PIT for mapping..
<ID:0/048> Firmware update start..
<ID:0/048> sbl.bin
<ID:0/048> BcmCP.img
<ID:0/048>
<ID:0/048> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what might be wrong - all drivers are installed and Kies is not running.
Click to expand...
Click to collapse
Issue fixed, tried another set of FW from doky77's page - the complete set with PDA, Modem and CSC files. The whole process took less than a minute. And bingo, I have unbricked my phone the first time.

Download firmware packages .again and try sometimes it will work....dont worry.......if it stucks on boot.img.......ex:in samsung logo ...remove the battery ....and start the phone in recovery mode using 3button combo.......in recovery mode use wipe data/factory reset after its completed and then wipe cache....after rebbooot system...it will surely work....i have xperienced this bug....if i helped pls tap helped
Sent from my GT-S6102 using xda app-developers app

xdroid_noob said:
Issue fixed, tried another set of FW from doky77's page - the complete set with PDA, Modem and CSC files. The whole process took less than a minute. And bingo, I have unbricked my phone the first time.
Click to expand...
Click to collapse
Hmm so I need 3 blanks filled in in order to flash my SGY?
I only have one file once extracted. Firmware for Sammobile.com

Use doky's thread for downloading firmwares not sammobile....Galaxy Y might not install the whole partition properly from a single tar file from sam mobile....
The doky's Firmwares have a higher chance of proper installation..
Sent from my GT-S5360 using xda app-developers app

I had softbrick with my galaxy Y..
what i do is to get offical firmware which got seperate file for modem,pda,csc..and also need pit file..
i flash it through ODIN and bring my phone alive back..

xdroid_noob said:
Similar issue here guys.. My phone was stuck at the boot image after rebooting from a custom ROM (JellyBlast 3.0), I couldn't get into recovery mode as well. In download mode Odin (1.84 and 1.85) detects the phone and while trying to flash with stock DDLF2 I get the below:
<ID:0/048> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360DDLF2_S5360ODDLF1_S5360DDLF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/048> Odin v.3 engine (ID:48)..
<ID:0/048> File analysis..
<ID:0/048> SetupConnection..
<ID:0/048> Initialzation..
<ID:0/048> Get PIT for mapping..
<ID:0/048> Firmware update start..
<ID:0/048> sbl.bin
<ID:0/048> BcmCP.img
<ID:0/048>
<ID:0/048> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what might be wrong - all drivers are installed and Kies is not running.
Click to expand...
Click to collapse
this had happened me before.
later i came to know about sgy that our sgy can't flash using a single .tar file in modem.
So you should flash it using three files in PDA, MODEM& CSC.
You will get all these files from 'doky73's thread.
Sent from my GT-S5360 using xda app-developers app

Solution: Add PIT file
abyisforyou said:
this had happened me before.
later i came to know about sgy that our sgy can't flash using a single .tar file in modem.
So you should flash it using three files in PDA, MODEM& CSC.
You will get all these files from 'doky73's thread.
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
For any of those who are reading this in the future with the same problem, add the PIT file for your device too and it should work. It worked fort me.

Catalyste said:
this may be due to kies interfering with the COM connection... you check by pressing Ctrl+Alt+Del and end each Kies process through task manager and try flashing again...
Click to expand...
Click to collapse
this worked. many thanks

Related

PLEASE HELP - Phone soft bricked after ICS LPY

Hi All,
So, I was one of those people who last night decided I needed to have clean install for my newly LPY ICS flashed through odin PC. Obviously, I had not read the warning threads only after my phone got stuck on format and then rebooted and got stuck on logo did I visit XDA and saw the new warning Anyhow, what I had flashed was a rooted version of LPY ICS. Now, I have access to download mode but when I tried to reflash through Odin PC I get a failed attempt with this message !!!
**Edit: I don't think I did use repartition...I usually never do....this all started after me trying to clean install via CWM from official rooted LPY it got stuck on formatting then rebooted and was on logo forever so I proceeded to use Odin flashing LPY failed, tried all methods posted here besides flashing kernel Abyuss note 4.2 from in PDA as someone here suggested but since I can't find one that works with Odin I just reflash LC1 rooted stock multiple times but no luck it fails and NAND Write Start which is almost at the end of flashing.
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:13)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Can't open the specified file. (Line: 1876)
All threads completed. (succeed 0 / failed 1)
Can anyone please help. I have no idea what I should do I even tried flashing stock ICS LPY but at 3/4 of the way it would also fail!!!
jwais said:
Hi All,
So, I was one of those people who last night decided I needed to have clean install for my newly LPY ICS flashed through odin PC. Obviously, I had not read the warning threads only after my phone got stuck on format and then rebooted and got stuck on logo did I visit XDA and saw the new warning Anyhow, what I had flashed was a rooted version of LPY ICS. Now, I have access to download mode but when I tried to reflash through Odin PC I get a failed attempt with this message !!!
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help. I have no idea what I should do I even tried flashing stock ICS LPY but at 3/4 of the way it would also fail!!!
Click to expand...
Click to collapse
Did you backup your previous from ..if you did just go into recovery and restore it
Sent from my GT-N7000 using xda premium
You are making one huge mistake : you have the box "re-partition" selected. Uncheck that option and you should be good to go.
P_
jwais said:
Hi All,
So, I was one of those people who last night decided I needed to have clean install for my newly LPY ICS flashed through odin PC. Obviously, I had not read the warning threads only after my phone got stuck on format and then rebooted and got stuck on logo did I visit XDA and saw the new warning Anyhow, what I had flashed was a rooted version of LPY ICS. Now, I have access to download mode but when I tried to reflash through Odin PC I get a failed attempt with this message !!!
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help. I have no idea what I should do I even tried flashing stock ICS LPY but at 3/4 of the way it would also fail!!!
Click to expand...
Click to collapse
Try to flash gingerbread rom from http://forum.xda-developers.com/showthread.php?t=1535025 i would try this one "N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)" because it a full wipe.
Here is how to solve.
1.flash stck GB rom
2.wipe data/cache from stock recovery.
3.now flash stock ics.
4.then flash another rom/ root kernel
Sent from my GT-N7000 using xda premium
awesome-member said:
Here is how to solve.
1.flash stck GB rom
2.wipe data/cache from stock recovery.
3.now flash stock ics.
4.then flash another rom/ root kernel
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
That' the safest way.
Sent from my Galaxy Note
Thanks guys, I tried reflashing stock GB lc1 and it stoped on odin pc sayig failed and I did not repartition this time. Tried reflashing stock ICS LPY with no luck...it fails.
If anyone has another option please let me know...I cannot access recovery only download mode when I try to access recovery it gives me " firmware upgrade failed encountered an issue. Please select recovery mode in kies & try gain" .....
jwais said:
Thanks guys, I tried reflashing stock GB lc1 and it stoped on odin pc sayig failed and I did not repartition this time. Tried reflashing stock ICS LPY with no luck...it fails.
If anyone has another option please let me know...I cannot access recovery only download mode.....
Click to expand...
Click to collapse
Try to find the pit file and use it with repartition checked.
Sent from my GT-N7000 using XDA
just to be sure,
did u kill all kies processes?
aww
jwais said:
Hi All,
So, I was one of those people who last night decided I needed to have clean install for my newly LPY ICS flashed through odin PC. Obviously, I had not read the warning threads only after my phone got stuck on format and then rebooted and got stuck on logo did I visit XDA and saw the new warning Anyhow, what I had flashed was a rooted version of LPY ICS. Now, I have access to download mode but when I tried to reflash through Odin PC I get a failed attempt with this message !!!
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help. I have no idea what I should do I even tried flashing stock ICS LPY but at 3/4 of the way it would also fail!!!
Click to expand...
Click to collapse
idk how to i wish i could man
Kill KiesHelper.exe and KiesPDLR.exe and try to flash again
Yup killed all kies processes. Reflashing stock LC1 one last time with odin pc as suggested....pray for me
I had this similar issue. I had to completely un install Kies and then Odin worked without issue
Sent from my GT-N7000 using xda premium
i slashed my knees open, knelt with salt and lemon on the ground. i can't do this for long.... is your note ok (i hope i do not have to do some other kind of rituals for the flash procedure to work for you).
Ok guys after trying to reflash second time stock GB LC1 with odin pc this is what I get:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/013> Removed!!
It goes almost all the way but then somehow stops at the nand write part. Anyone has any clue?
Did you completely uninstall kies? It's worth a shot...
Sent from my GT-N7000 using xda premium
Uninstalling Kies right now...will try again flashing. Thanks!
take out your battery, restart the pc... and try another cable if possible.
make sure all firewalls and/or antivirus softwares are disabled. if it helps, run odin as administrator.
while you do that, i shall make a bonfire and prepare to dance around naked around the flame and chant the songs my great ancestors has been singing since time immemorial.
Ok, I think I found a pattern for the failed attempts during flashing...it always stalls and fails during the NAND Write Start.....anyone has any clue as to why?
Maybe it sounds stupid but what version of Odin do yo use?

Firmware upgrade encountered an issue.

So my gs4 seems to be soft bricked. I was trying to reroot my phone and it failed in the middle of rooting and now when I try to turn it on, it goes to a screen saying firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. What do I do? Do I just flash stock firmware onto the phone with odin?
xTrooge said:
So my gs4 seems to be soft bricked. I was trying to reroot my phone and it failed in the middle of rooting and now when I try to turn it on, it goes to a screen saying firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. What do I do? Do I just flash stock firmware onto the phone with odin?
Click to expand...
Click to collapse
yes your best option
Blackwolf10 said:
yes your best option
Click to expand...
Click to collapse
any links to a fast download? found one but it goes 360 kb/s max.
xTrooge said:
any links to a fast download? found one but it goes 360 kb/s max.
Click to expand...
Click to collapse
good you can think of your options while it is downloading :laugh:
no sorry i am not that familiar with this thread but on stock firmware threads usually people leave mirrors of other sites so try that
So just tried it, heres what i get from odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L720_MDC_Stock_Nodata.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
fml
xTrooge said:
So just tried it, heres what i get from odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L720_MDC_Stock_Nodata.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
fml
Click to expand...
Click to collapse
ahhhh seems your rooting has made a few problems you don't have a pit partition so odin can't do anything about it
you can try kies don't know if it will help seems you will have to service it i guess
Blackwolf10 said:
ahhhh seems your rooting has made a few problems you don't have a pit partition so odin can't do anything about it
you can try kies don't know if it will help seems you will have to service it i guess
Click to expand...
Click to collapse
where do i get the pit? kies is pretty useless seeing as how it can only recover if i backed it up
xTrooge said:
where do i get the pit? kies is pretty useless seeing as how it can only recover if i backed it up
Click to expand...
Click to collapse
pit file usually comes with the stock Rom you get 3 files from the zip right ?
but i wouldn't want to try that and i would defently read a thread about pit before doing anything
BTW what's your device model ?
the only thing i can think of is you used a wrong rooting methood for it
Blackwolf10 said:
pit file usually comes with the stock Rom you get 3 files from the zip right ?
but i wouldn't want to try that and i would defently read a thread about pit before doing anything
BTW what's your device model ?
the only thing i can think of is you used a wrong rooting methood for it
Click to expand...
Click to collapse
nvm just fixed it. i just had to use a different usb port and restart my comp.
xTrooge said:
nvm just fixed it. i just had to use a different usb port and restart my comp.
Click to expand...
Click to collapse
hah that works the best glad you didn't have to use Pit

[Q] GT-I9505 maybe bricked beyond repair

Hello all,
First I must congratulate all of you technically minded people who've guided me through rooting and custom rom-ing my G1, S2 and now S4, but it seems now that I have a phone beyond repair.
Background
I have a GT-I9505 from the 3 network [h3g] here in the uk.
A couple of months ago I used CF auto root to give root privileges to install ad-away to remove those pesky advertisments yet all was not well.
Around once a week main core processes would hang or crash the phone completely and when the phone was rebooted or powered on, it would hang on the 3 logo.
Booting into recovery and wiping cache and data would fix it, as would a re-flash of the CF auto root using Odin.
A week ago, after a call, the phone hanged - i did a hard reset, removing the battery but the phone was stuck on the 3 logo screen again.
After becoming annoyed by this happening every week i decided to revert to stock rom.
What I have done
I flashed I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 via Odin.
Odin said it was successful although the phone still wouldn't boot.
I went into recovery mode and attempted to wipe data and cache, but wiping of the cache failed.
Repeated efforts led me to flashing a PIT file with the above ROM and again ODIN said it was a success, but still the phone hung on the 3 logo.
Booting into stock recovery, again the phone failed to wipe cache,
How my GT-I9505 is now in a worse state
After stock recovery failing to write cache i downloaded TeamWin recovery and flashed it to my phone and attempted to write cache. Again failed.
Now i did something stupid - i saw in the recovery menu something along the lines of "reset permissions", thinking this would let me delete the cache I applied it and proper bricked my phone.
I cannot boot into recovery - I am stuck on the TeamWin logo.
I'm not sure the battery is charging. (Grey battery icon with a 'refresh style' logo, no animated charging(
I can boot into ODIN mode.
Since this, I've been reading around and tried GT-I9505-Factory-Firmware-Full-Wipe-DBT
When attempting this, Odin gives:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> aboot.mbn
<ID:0/025> NAND Write Start!!
<ID:0/025> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode says
ODIN MODE
Product name: GT-I9505
Current Binary: Custom
System Status: Custom
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
START [224, 1440]
But of course, the blue bar to show progress has barely started.
When trying to write stock rom with PIT file, Odin v3.07 displays this:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.img
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
hen flashing just the pit Odin says
<ID:0/025> Removed!!
<ID:0/025> Added!!
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> RQT_CLOSE !!
<ID:0/025> RES OK !!
<ID:0/025> Removed!!
and phone reboots to samsung screen but progresses no further.
So this is real squeaky bum time and i really don't want to do anything else without advice as a true hard brick is not something I want nor can afford.
I've used the original white USB cable and other official samsung cables, I've tried different usb ports and computers with ODIN, all with the same results.
If anyone has any suggestions on how to unbrick this marvellous yet expensive phone, I will be truly and forever grateful and may buy you a pint if you're ever in Nottingham or perhaps do some statistics for you!!
Hsve you tried just the pit and repartition on its own, and then trying from there to flash the rom? I've read others who had success this way
Sent from my GT-I9505 using XDA Premium 4 mobile app
MrBrickedPhone said:
Hello all,
First I must congratulate all of you technically minded people who've guided me through rooting and custom rom-ing my G1, S2 and now S4, but it seems now that I have a phone beyond repair.
Background
I have a GT-I9505 from the 3 network [h3g] here in the uk.
A couple of months ago I used CF auto root to give root privileges to install ad-away to remove those pesky advertisments yet all was not well.
Around once a week main core processes would hang or crash the phone completely and when the phone was rebooted or powered on, it would hang on the 3 logo.
Booting into recovery and wiping cache and data would fix it, as would a re-flash of the CF auto root using Odin.
A week ago, after a call, the phone hanged - i did a hard reset, removing the battery but the phone was stuck on the 3 logo screen again.
After becoming annoyed by this happening every week i decided to revert to stock rom.
What I have done
I flashed I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 via Odin.
Odin said it was successful although the phone still wouldn't boot.
I went into recovery mode and attempted to wipe data and cache, but wiping of the cache failed.
Repeated efforts led me to flashing a PIT file with the above ROM and again ODIN said it was a success, but still the phone hung on the 3 logo.
Booting into stock recovery, again the phone failed to wipe cache,
How my GT-I9505 is now in a worse state
After stock recovery failing to write cache i downloaded TeamWin recovery and flashed it to my phone and attempted to write cache. Again failed.
Now i did something stupid - i saw in the recovery menu something along the lines of "reset permissions", thinking this would let me delete the cache I applied it and proper bricked my phone.
I cannot boot into recovery - I am stuck on the TeamWin logo.
I'm not sure the battery is charging. (Grey battery icon with a 'refresh style' logo, no animated charging(
I can boot into ODIN mode.
Since this, I've been reading around and tried GT-I9505-Factory-Firmware-Full-Wipe-DBT
When attempting this, Odin gives:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> aboot.mbn
<ID:0/025> NAND Write Start!!
<ID:0/025> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode says
ODIN MODE
Product name: GT-I9505
Current Binary: Custom
System Status: Custom
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
START [224, 1440]
But of course, the blue bar to show progress has barely started.
When trying to write stock rom with PIT file, Odin v3.07 displays this:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.img
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
hen flashing just the pit Odin says
<ID:0/025> Removed!!
<ID:0/025> Added!!
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> RQT_CLOSE !!
<ID:0/025> RES OK !!
<ID:0/025> Removed!!
and phone reboots to samsung screen but progresses no further.
So this is real squeaky bum time and i really don't want to do anything else without advice as a true hard brick is not something I want nor can afford.
I've used the original white USB cable and other official samsung cables, I've tried different usb ports and computers with ODIN, all with the same results.
If anyone has any suggestions on how to unbrick this marvellous yet expensive phone, I will be truly and forever grateful and may buy you a pint if you're ever in Nottingham or perhaps do some statistics for you!!
Click to expand...
Click to collapse
Go to this website
You will learn how to unbrick your soft bricked s4
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Lalssa said:
Go to this website
You will learn how to unbrick your soft bricked s4
Click to expand...
Click to collapse
Been there - all methods do not work:
Cannot boot into recovery
Odin is not flashing ROMs with or without PIT
MrBrickedPhone said:
Been there - all methods do not work:
Cannot boot into recovery
Odin is not flashing ROMs with or without PIT
Click to expand...
Click to collapse
http://m.ibtimes.co.uk/samsung-galaxys4-gti9500-gti9505-unbrick-softbrick-hardbrick-469557.html
If didnt work try again
angus_mcfisher said:
Hsve you tried just the pit and repartition on its own, and then trying from there to flash the rom? I've read others who had success this way
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, yes I've tried just flashing the PIT, then the rom with all variations e.g. unticking auto-reboot in ODIN, hard reset, boot into ODIN mode, then attempting to flash the ROM.
ODIN will flash the PIT but refuses to flash the ROM
Fail (WP)
I'm assuming (WP) is some kind of write protection
MrBrickedPhone said:
Thanks for the reply, yes I've tried just flashing the PIT, then the rom with all variations e.g. unticking auto-reboot in ODIN, hard reset, boot into ODIN mode, then attempting to flash the ROM.
ODIN will flash the PIT but refuses to flash the ROM
Fail (WP)
I'm assuming (WP) is some kind of write protection
Click to expand...
Click to collapse
Download another version of odin
Lalssa said:
Download another version of odin
Click to expand...
Click to collapse
I've just tried it with ODIN v3.04 and v1.85, with combinations of PIT alone with no auto reboot followed by flashing the rom along with doing both at once and unfortunately even though ODIN writes the PIT it fails to write the ROM.
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025>
<ID:0/025> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It appears to be a non-standard brickage to say the least i'm afraid.
MrBrickedPhone said:
I've just tried it with ODIN v3.04 and v1.85, with combinations of PIT alone with no auto reboot followed by flashing the rom along with doing both at once and unfortunately even though ODIN writes the PIT it fails to write the ROM.
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025>
<ID:0/025> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It appears to be a non-standard brickage to say the least i'm afraid.
Click to expand...
Click to collapse
Try flashing using heimdall you can find some interesting tutorials if you google it
Lalssa said:
Try flashing using heimdall you can find some interesting tutorials if you google it
Click to expand...
Click to collapse
Thanks, reading up on it now. Will report back when i've learned enough to attempt to flash things
MrBrickedPhone said:
Thanks, reading up on it now. Will report back when i've learned enough to attempt to flash things
Click to expand...
Click to collapse
Using Heimdall:
As with ODIN, writing the PIT is completed.
Alas, Heimdall cannot write ANY partitions from the extracted .tar files from the GT-I9505-Factory-Firmware-Full-Wipe-DBT ROM.
It does seem that the flash memory is write protected - it certainly cannot be written to.
If I were in this situation I would do the following:
Download latest PhilZ recovery for i9505.
Flash this in PDA section of Odin.
Boot to recovery and go to mounts and storage.
Format system, data, cache, preload (and format SD card if there's nothing important you need like photos etc)
You now have a TOTALLY clean device.
Boot to download mode and flash MGA stock firmware with Odin.
I would download the MGA firmware from Sammobile as these are untouched stock firmware files.
If flash is successful boot to recovery (it will now be stock) and wipe data factory reset.
Now reboot.
Hopefully you should be good to go
P.S If once again Odin fails on nand write start the you probably have a corrupt nand and I hate to say it but a whole board replacement might be needed.
Good luck mate!
Sent from my GT-I9505 using XDA Premium HD app
Have you tried to flash the pit + stock firmware with the re-partition box checked?
BTW, be careful using Heimdall. I've hardbricked my phone to the point that I cannot go to recovery and download mode while using that tool. It was impossible to turn the phone off and charge the phone as well. I didn't know what caused it (probably incorrect bootloader/pit) but as a result I needed a board replacement. Luckily Samsung replaced it for free as they cannot revive the phone anymore lol.
Obagleyfreer said:
If I were in this situation I would do the following:
Download latest PhilZ recovery for i9505.
Flash this in PDA section of Odin.
Boot to recovery and go to mounts and storage.
Format system, data, cache, preload (and format SD card if there's nothing important you need like photos etc)
You now have a TOTALLY clean device.
Boot to download mode and flash MGA stock firmware with Odin.
I would download the MGA firmware from Sammobile as these are untouched stock firmware files.
If flash is successful boot to recovery (it will now be stock) and wipe data factory reset.
Now reboot.
Hopefully you should be good to go
P.S If once again Odin fails on nand write start the you probably have a corrupt nand and I hate to say it but a whole board replacement might be needed.
Good luck mate!
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for taking the time to provide the advice, I've tried flashing PhilZ recovery via ODIN and it tells me it has been successful, however when i try to boot into recovery it appears it's not flashed at all as I get stuck on the previous recovery TeamWin loading screen - it looks as if the nand maybe corrupted after all.
chickentuna said:
Have you tried to flash the pit + stock firmware with the re-partition box checked?
BTW, be careful using Heimdall. I've hardbricked my phone to the point that I cannot go to recovery and download mode while using that tool. It was impossible to turn the phone off and charge the phone as well. I didn't know what caused it (probably incorrect bootloader/pit) but as a result I needed a board replacement. Luckily Samsung replaced it for free as they cannot revive the phone anymore lol.
Click to expand...
Click to collapse
Yes, I've attempted to flash the pit + correct stock firmware with the re-partition box checked and while it writes the pit, Odin starts to write the firmware then fails about halfway through.
Perhaps, reading between the lines, it would be better for me if indeed I hard bricked the phone to a state where the recovery and download mode are not accessible as then it would not be obvious I had invalidated the warranty by previously rooting the phone and would get a free replacement!
Thanks for taking the time to reply.
MrBrickedPhone said:
Yes, I've attempted to flash the pit + correct stock firmware with the re-partition box checked and while it writes the pit, Odin starts to write the firmware then fails about halfway through.
Perhaps, reading between the lines, it would be better for me if indeed I hard bricked the phone to a state where the recovery and download mode are not accessible as then it would not be obvious I had invalidated the warranty by previously rooting the phone and would get a free replacement!
Thanks for taking the time to reply.
Click to expand...
Click to collapse
Damn that's quite unfortunate. Sorry mate, I'm out of ideas. I wouldn't actually advise to hard brick the phone intentionally because as far as I know there's still hope as you can still access download mode.
Well if you can't really flash anything it's probably best to just hard brick the phone to the point that the Samsung guys wouldn't be able to revive it then send the phone for repairs than having to send it in it's current state because they'll most likely find out that you've modified your phone. Again I strongly suggest not to do it.
Good luck. Hope you fix it soon buddy.
Sent from my GT-I9505 using Tapatalk 4
Download Kies and install samsung drivers with it. Click on tools tab and click emergency firmware restore. Type in your phone model e.g GT-I9505 and then type in your Serial Number (can be found in the battery compartment of the phone) Kies will then ask you to go to download mode and then it will start downloading firmware and installing it on your device.
The write protection enabled message suggests to me that you've previously had one of the stock firmwares with the new bootloader. Have you had MH8 on there?
If you're desperate you could always try flashing MH8 firmware. The new bootloader won't let you downgrade to an older firmware giving a message as above.
Sent from my GT-I9505 using Tapatalk 4
Had this issue
Hey There, i had this issue last night infact, i had bricked my phone, recovery not accessible and download mode only possible by plugging it in and then starting it, try this put your phone into download mode, via plugging it in then turning it on, when it is in download mode flash PhilZ recovery via the PDA option then turn it off after flashing by taking out the battery (after it has rebooted and flashed), then plug it in again, launch into recovery and wipe/format etc.. install a new MH8 stock firmware (with the new bootloader) then you should be okay.
It should be noted that i did these step and it worked, except i didn't ever install a new rom and kept stock and i used a nandroid backup instead of installing the stock rom
You say twrp logo shows up. Does it start adb ? Maybe u can remount partitions as RW with terminal . manually wipe it. And then try adb sideload to install a .zip
All I can think of as every other suggestions seem to have been mentioned.
Sent from my GT-I9505G using xda app-developers app

Unable to root s4 i9505 v4.3

I'm having problems rooting my s4 i9505 v4.3
I'm using odin v3.07 when I run cf auto root md5 file it shows Failed
this is the error I get:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 is valid.
<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> Get PIT for mapping..
<ID:0/005> Removed!!
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
please Help!!!
v-2cdele said:
I'm having problems rooting my s4 i9505 v4.3
I'm using odin v3.07 when I run cf auto root md5 file it shows Failed
this is the error I get:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 is valid.
<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> Get PIT for mapping..
<ID:0/005> Removed!!
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
please Help!!!
Click to expand...
Click to collapse
Make sure you got Autoreboot & F. Reset Time CHECKED and put the .tar.md5 file in de PDA tab
Make sure Samsung Kies is NOT running check Task Manager to kill Kies processes
BillvanHalen said:
Make sure you got Autoreboot & F. Reset Time CHECKED and put the .tar.md5 file in de PDA tab
Make sure Samsung Kies is NOT running check Task Manager to kill Kies processes
Click to expand...
Click to collapse
I done that already I even restarted my pc and still the same..
v-2cdele said:
I done that already I even restarted my pc and still the same..
Click to expand...
Click to collapse
Change usb port...
LiMunnn said:
Change usb port...
Click to expand...
Click to collapse
And if that dosn't work ... change USB cable :fingers-crossed:
LiMunnn said:
Change usb port...
Click to expand...
Click to collapse
I tried that as well but no luck.... =(
Please help me root my phone......huhu
v-2cdele said:
<ID:0/005> Get PIT for mapping..
<ID:0/005> Removed!!
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
These lines seem as if you were checking the "Re-partition" box in Odin. Be sure this is unchecked!
Anyway, two ads: 1) Be sure you are using correct cf-auto-root file for your i9505 and not for i9500. 2) Use the odin version found inside the cf-auto-root zip, it is, version 1.85, instead of 3.0x; in some forums people say 3.0x gives errors for cf-root.
jaswinky said:
These lines seem as if you were checking the "Re-partition" box in Odin. Be sure this is unchecked!
Anyway, two ads: 1) Be sure you are using correct cf-auto-root file for your i9505 and not for i9500. 2) Use the odin version found inside the cf-auto-root zip, it is, version 1.85, instead of 3.0x; in some forums people say 3.0x gives errors for cf-root.
Click to expand...
Click to collapse
I didn't put a check on the re-partition box I even tried the odin 1.85 version still no luck....
are you using the latest version of cf-root? had the same problem...
Sent from my GT-I9505 using xda app-developers app
cuker8 said:
are you using the latest version of cf-root? had the same problem...
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Yup, is there any difference if my phone is lock from my mobile provider?
v-2cdele said:
I didn't put a check on the re-partition box I even tried the odin 1.85 version still no luck....
Click to expand...
Click to collapse
And same error in odin? sorry, no ideas... except trying the method to flash 4.3 with root using a pit file (repartition) ando wiping data (factory reset).

SM-N900 Stuck on Samsung Logo & Can't access Recovery Mode!

Hi!
When I try to reboot into Recovery Mode, it says: "System is updating...", and when it reaches something like 25%, it says: "Error"!
I tried to flash stock rom with Odin 30.7 and 30.9, but they both stop at either "ConnectionSetup" or "nand write start"!
The rom I tried: TGY-N9005ZSUGOH3-20150904101408_2
You have an n900 or n9005? File looks like it is for the n9005.
audit13 said:
You have an n900 or n9005? File looks like it is for the n9005.
Click to expand...
Click to collapse
I tried N900XXUCMK2_N900ODDCMK1_INU this time, but it's no use!
Both Odin 3.07 and 3.12.5 say: Fail.
Here's 3.07's log:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900XXUCMK2_N900ODDCMK1_N900DDUCMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<<-N9005ZSUGOH3-20150904101408_2 m >>>
Thats wrong for your model .
<<<ID:0/006> Can't open the serial(COM) port. >>>
Thats a fail on connection .
Try and recover your phone through KIES lets hope flashing the wrong firmware has done no damage .
JJEgan said:
Try and recover your phone through KIES lets hope flashing the wrong firmware has done no damage .
Click to expand...
Click to collapse
It says: "SM-N900 does not support initializing"
Where can I find the right firmware, so I flash it with Odin?
Oliver Q said:
It says: "SM-N900 does not support initializing"
Where can I find the right firmware, so I flash it with Odin?
Click to expand...
Click to collapse
Boot to download mode to find phone model .
Firmware is on sammobile or samsung-updates .com
IT WORKED!
I searched for my phone model firmware on sammobile, downloaded it then flashed it with Odin 3.12.5 and it worked!
Thanks, everybody, you guys are just awesome!

Categories

Resources