Database Users

[Q] [request] Stock DDLA1

Hey can anyone give me flashable file of stock ddla1 galaxy Y or just tell me that can i flash any other deodexed baseband zip in my DDLA1 baseband???
SENT FROM MY GADGET OF MASS DESTRUCTION

Flashing a zip in cwm will not change your baseband - it's like flashing a custom rom zip - It maybe based on that baseband but your phone's baseband doesnt change
Therefore you can flash any rom via cwm on any baseband & it should work - the only possible issue could be loss of imei but a change of kernel normally solves that
To actually change basebands you need to flash a different stock rom firmware via odin
you can find theses on dokys thread in dev section
You can also find latest firmware on sammobile.com but you will need to use the splitter tool also on dokys thread to split the firmware into its separate parts to be able to flash it with odin

Unable to Download stock indian firmware from hotfile
My phone is bricked, and I need to install urgently a Stock Indian rom for my galaxy y.
All links for the firmwares point to Hotfile, which is not accesable currently.
Could some one please point to a download link other than hotfile, so that I can download the firmwares.
Any of the below roms would be helpful.
S5360_DDLA3_ODDLA2_DDLA2
S5360_DDLC2_ODDLA2_DDLC2
S5360_DDLE1_ODDLD1_DDLE1
S5360_DDLF2_ODDLF1_DDLF1
S5360_DDLK2_ODDLK1_DDLK1

nanoharsha said:
My phone is bricked, and I need to install urgently a Stock Indian rom for my galaxy y.
All links for the firmwares point to Hotfile, which is not accesable currently.
Could some one please point to a download link other than hotfile, so that I can download the firmwares.
Any of the below roms would be helpful.
S5360_DDLA3_ODDLA2_DDLA2
S5360_DDLC2_ODDLA2_DDLC2
S5360_DDLE1_ODDLD1_DDLE1
S5360_DDLF2_ODDLF1_DDLF1
S5360_DDLK2_ODDLK1_DDLK1
Click to expand...
Click to collapse
unfortunalty I havent got any of them but you can try a european firmwire just to get your phone booting - i dont know if you will get network but if you urgently need to try something I uploaded this on dev host
http://d-h.st/FhE

search google it.

NexuS** said:
search google it.
Click to expand...
Click to collapse
please note that all firmwire used to be on hotfile - this host site has been shut down so saying google it is not helpful as all sites would point to hotfile
thats why I uploaded the other firmwire on dev host but i dont have any others

Unable to Download stock indian firmware from hotfile
marcussmith2626 said:
please note that all firmwire used to be on hotfile - this host site has been shut down so saying google it is not helpful as all sites would point to hotfile
thats why I uploaded the other firmwire on dev host but i dont have any others
Click to expand...
Click to collapse
I tried flashing via odin using the file given. It was failing.
<ID:0/021> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXMI1.tar.md5 is valid.
<OSM> MODEM_S5360_XXMC2.tar.md5 is valid.
<OSM> CSC_S5360_OXXMD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXMI1.tar.md5 is valid.
<OSM> MODEM_S5360_XXMC2.tar.md5 is valid.
<OSM> CSC_S5360_OXXMD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Set PIT file..
<ID:0/022> DO NOT TURN OFF TARGET!!
<ID:0/022> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
AT one point I was ablee to boot into a custom Hyperion Rom after flashing it.
There were WIFI issues, so I tried reflashing kernel etc, and again, I got the below issues.
-- unable to mount /data, /sdcard, /system /cache.
I read through some posts and found out that flashing stock rom is the only way. But here I am unable to flash stock rom also. Btw I am from India, just in case any one wants to help with firmware.
PLease suggest.

nanoharsha said:
I tried flashing via odin using the file given. It was failing.
<ID:0/021> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXMI1.tar.md5 is valid.
<OSM> MODEM_S5360_XXMC2.tar.md5 is valid.
<OSM> CSC_S5360_OXXMD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXMI1.tar.md5 is valid.
<OSM> MODEM_S5360_XXMC2.tar.md5 is valid.
<OSM> CSC_S5360_OXXMD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Set PIT file..
<ID:0/022> DO NOT TURN OFF TARGET!!
<ID:0/022> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
AT one point I was ablee to boot into a custom Hyperion Rom after flashing it.
There were WIFI issues, so I tried reflashing kernel etc, and again, I got the below issues.
-- unable to mount /data, /sdcard, /system /cache.
I read through some posts and found out that flashing stock rom is the only way. But here I am unable to flash stock rom also. Btw I am from India, just in case any one wants to help with firmware.
PLease suggest.
Click to expand...
Click to collapse
are you using a pit file? its not required
did you say that firmware worked before but its not now or didnt work at all?
try using a different version of odin
try odin 1.85
what kernel did you try and flash
did you format system data and cache in cwm and then try to mount?

Dont spam
SENT FROM MY GADGET OF MASS DESTRUCTION

MohitDMO said:
Dont spam
SENT FROM MY GADGET OF MASS DESTRUCTION
Click to expand...
Click to collapse
Why do you consider that we are spamming ? This is a general thread not a development thread first of all..
And here I am unable to boot my device, and peers like marcussmith2626 are trying to help me get to use my device.
So whats spamming here. As I dont see anything irrevelant.
---------- Post added at 06:12 PM ---------- Previous post was at 06:04 PM ----------
marcussmith2626 said:
are you using a pit file? its not required
did you say that firmware worked before but its not now or didnt work at all?
try using a different version of odin
try odin 1.85
what kernel did you try and flash
did you format system data and cache in cwm and then try to mount?
Click to expand...
Click to collapse
I tried once using a pit file, and once without , deosnt change anything.
I tried the version of Odin you ve sent, but its the same result. Doesnt help. The process still fails.
I tried to flash hells fusion, and thats when things went bad. Before I was on PErcy's/WhiteXP's Kernel I suppose.
I am unable to format system data cache, because I am even uanbel to mount them, which seems to be the problem now.
Else I should be able to flash a custom rom easily.
So need to get over the unable to mount issue, rest should fall in place.

nanoharsha said:
Why do you consider that we are spamming ? This is a general thread not a development thread first of all..
And here I am unable to boot my device, and peers like marcussmith2626 are trying to help me get to use my device.
So whats spamming here. As I dont see anything irrevelant.
---------- Post added at 06:12 PM ---------- Previous post was at 06:04 PM ----------
I tried once using a pit file, and once without , deosnt change anything.
I tried the version of Odin you ve sent, but its the same result. Doesnt help. The process still fails.
I tried to flash hells fusion, and thats when things went bad. Before I was on PErcy's/WhiteXP's Kernel I suppose.
I am unable to format system data cache, because I am even uanbel to mount them, which seems to be the problem now.
Else I should be able to flash a custom rom easily.
So need to get over the unable to mount issue, rest should fall in place.
Click to expand...
Click to collapse
have you tried to actually format them? - you dont need to have them mounted to format them
all you need to do really is flash stock rom then in stock recovery not cwm select wipe data/factory reset
then you should be able to flash cwm and format system data cache and then mount them without after they have formatted without error

marcussmith2626 said:
have you tried to actually format them? - you dont need to have them mounted to format them
all you need to do really is flash stock rom then in stock recovery not cwm select wipe data/factory reset
then you should be able to flash cwm and format system data cache and then mount them without after they have formatted without error
Click to expand...
Click to collapse
I have tried both the things.
The stock rom flashing is failing via odin, the error message is as below :
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXMI1.tar.md5 is valid.
<OSM> MODEM_S5360_XXMC2.tar.md5 is valid.
<OSM> CSC_S5360_OXXMD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Set PIT file..
<ID:0/022> DO NOT TURN OFF TARGET!!
<ID:0/022> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/022> Removed!!
And I am also unable to wipe cache/data etc, because of mount issue.

nanoharsha said:
I have tried both the things.
The stock rom flashing is failing via odin, the error message is as below :
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXMI1.tar.md5 is valid.
<OSM> MODEM_S5360_XXMC2.tar.md5 is valid.
<OSM> CSC_S5360_OXXMD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Set PIT file..
<ID:0/022> DO NOT TURN OFF TARGET!!
<ID:0/022> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/022> Removed!!
And I am also unable to wipe cache/data etc, because of mount issue.
Click to expand...
Click to collapse
you didnt answer my previous question of did you manage to flash this firmwire successfully at all in the past as I havent fully tested flashing this firmeware myself - you said you flashed it before then flashed hyperion so did it flash correctly before or have you always had this error with this firmware?
try with this pit file
http://forum.xda-developers.com/attachment.php?attachmentid=1489509
The only solution I found is what iv already said
Recovery
Mounts and storage Format cache data and system (dont worry it says mount errors when you enter cwm just format them)
Download mode flash stock rom

[Q] At&t samsung galaxy s4 i337 not booting into os

Hello there! I recently had purchased a Samsung Galaxy s4. I did not really enjoy touchwiz. I really wanted Google Play Edition. Anyways, my phone is stuck in ODIN mode with a message saying "Downloading... Do not turn off target!" I know that you can enter download mode and hit cancel to boot. But, my issue is different. Listen. I got safestrap on my s4, and it worked perfectly. I backed up my phone and installed Google Play Edition on the STOCK slot. Turned out, Google Play Edition would not boot up so I went back into safestrap and added a new rom slot. Then I restored my firmware on that slot. I left the stock slot not working... Then I uninstalled safestrap at boot up, not thinking about the stock rom. THIS IS THE BIG MISTAKE. I then rebooted my phone, and I get odin with the error message. I can't get into recovery settings or safestrap of course. I am now stuck with no options on my phone. I try to go to download mode and hit cancel. This did not boot up my phone, only my Google Play Edition which was not working. Now I can't change my rom slot. All I want to do now is go back to touchwiz. I want to restore my phone, but how? I would really appreciate your help!
I was running android 4.3 jellybean on MF3 so I can't load TWRP.

AlwaysBeen said:
Hello there! I recently had purchased a Samsung Galaxy s4. I did not really enjoy touchwiz. I really wanted Google Play Edition. Anyways, my phone is stuck in ODIN mode with a message saying "Downloading... Do not turn off target!" I know that you can enter download mode and hit cancel to boot. But, my issue is different. Listen. I got safestrap on my s4, and it worked perfectly. I backed up my phone and installed Google Play Edition on the STOCK slot. Turned out, Google Play Edition would not boot up so I went back into safestrap and added a new rom slot. Then I restored my firmware on that slot. I left the stock slot not working... Then I uninstalled safestrap at boot up, not thinking about the stock rom. THIS IS THE BIG MISTAKE. I then rebooted my phone, and I get odin with the error message. I can't get into recovery settings or safestrap of course. I am now stuck with no options on my phone. I try to go to download mode and hit cancel. This did not boot up my phone, only my Google Play Edition which was not working. Now I can't change my rom slot. All I want to do now is go back to touchwiz. I want to restore my phone, but how? I would really appreciate your help!
I was running android 4.3 jellybean on MF3 so I can't load TWRP.
Click to expand...
Click to collapse
Download mf3 tar file http://forum.xda-developers.com/showthread.php?t=2504311
Run in odin, your phone should be back up and running.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
Download mf3 tar file http://forum.xda-developers.com/showthread.php?t=2504311
Run in odin, your phone should be back up and running.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.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_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.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_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.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> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know why it is failing

AlwaysBeen said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.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_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.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_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.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> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know why it is failing
Click to expand...
Click to collapse
I think you've got an incomplete flash somewhere. I don't know if this will work but try the mf3 emergency files then flash the tar file again. http://forum.xda-developers.com/showthread.php?t=2526964
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
I think you've got an incomplete flash somewhere. I don't know if this will work but try the mf3 emergency files then flash the tar file again. http://forum.xda-developers.com/showthread.php?t=2526964
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Which file do I exactly download from this link?

AlwaysBeen said:
Which file do I exactly download from this link?
Click to expand...
Click to collapse
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970

bobbigbuns said:
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970
Click to expand...
Click to collapse
I really appreciate the registering just to help me out! Do i load the pit file with the MF3 tars? Or before?

bobbigbuns said:
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970
Click to expand...
Click to collapse
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It failed =( What can I do? My phone is showing in red text: SECURE CHECK FAIL : PIT
MY BOOTLOADER IS LOCKED, IT SAYS MY WRITE PROTECTION IS ENABLED

AlwaysBeen said:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It failed =( What can I do? My phone is showing in red text: SECURE CHECK FAIL : PIT
MY BOOTLOADER IS LOCKED, IT SAYS MY WRITE PROTECTION IS ENABLED
Click to expand...
Click to collapse
Do you remember what bootloader you were on?
If you were on anything higher than MF3 you are wasting your time, as you cannot downgrade this far.
MK2 and up requires those specific Odin tars. Since the original post was in January I will assume you were on MK2 at that time.
See here: http://forum.xda-developers.com/showthread.php?t=2663545
Personally, I would just go with the NB1, since root is now out for us. Once you odin the NB1 file, grab the files needed to towelroot, root, install superuser.apk, install safestrap 3.72 and you will probably be back in business
Now... thus all said, I am having a nightmare myself... last night I was listening to music on my I337 NC1 stockly rooted, when all of a sudden it froze... so I pulled the battery (which was fully charged), put it back in, and now my phone won't power up.
Being the geek I am, I grabbed my original samsung udb cable and plugged it into my windows machine... lo-and-behold windows recognized it, but as a completely different device... Qualcom USB or something...
How can I get back to download mode? Or do I need a JTAG? :crying:

kevp75 said:
Do you remember what bootloader you were on?
If you were on anything higher than MF3 you are wasting your time, as you cannot downgrade this far.
MK2 and up requires those specific Odin tars. Since the original post was in January I will assume you were on MK2 at that time.
See here: http://forum.xda-developers.com/showthread.php?t=2663545
Personally, I would just go with the NB1, since root is now out for us. Once you odin the NB1 file, grab the files needed to towelroot, root, install superuser.apk, install safestrap 3.72 and you will probably be back in business
Now... thus all said, I am having a nightmare myself... last night I was listening to music on my I337 NC1 stockly rooted, when all of a sudden it froze... so I pulled the battery (which was fully charged), put it back in, and now my phone won't power up.
Being the geek I am, I grabbed my original samsung udb cable and plugged it into my windows machine... lo-and-behold windows recognized it, but as a completely different device... Qualcom USB or something...
How can I get back to download mode? Or do I need a JTAG? :crying:
Click to expand...
Click to collapse
Sorry to hear about your dilemma. I probably cant help, but why not try.
Question, what do you mean by stockly rooted NC1? Are using the NC1 stock rom but rooted, or are you using another rom? Did you root using the download method or the towel root? Just curious.
I take you have tried to get to download mode using these steps?
Power off the phone completely by removing its battery for 5 seconds.
Re-insert the battery back into its place.
Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.

MatthewPresley said:
Sorry to hear about your dilemma. I probably cant help, but why not try.
Question, what do you mean by stockly rooted NC1? Are using the NC1 stock rom but rooted, or are you using another rom? Did you root using the download method or the towel root? Just curious.
I take you have tried to get to download mode using these steps?
Power off the phone completely by removing its battery for 5 seconds.
Re-insert the battery back into its place.
Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.
Click to expand...
Click to collapse
yeah... tried all that.
Stock Rooted NC1 ROM
Sent from my A110 using Tapatalk

I9505 soft-bricked odin fails flashing roms

I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl3.mbn
<ID:0/008> rpm.mbn
<ID:0/008> aboot.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3
I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english

C4scade said:
I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1
In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3
I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english
Click to expand...
Click to collapse
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?

Ricardo_Is said:
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Click to expand...
Click to collapse
Sorry for my bad english but
i also got the same error with odin :
aboot.mbn
FAIL! (Auth)
got no sound and got a black screen when calling mic also not working
flashing custom roms wont fix it any way to install stock i9505 rom without odin or kies ?
's it fixable any ideas ??

Ricardo_Is said:
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Click to expand...
Click to collapse
Man, i don't think that a nandroid backup can solve a binary error.. and yes, i checked the firmware md5, it's ok, it is from sammobile.com

I'd say if you've got aboot fail then your trying to flash older rom on a phone that's had newer rom on it aka Knox already.
Sent from my GT-I9505 using xda app-developers app

Flash the ''i9505 pit'' file on odin in pda. That will fix

DONE!!!
mr.biceps said:
Flash the ''i9505 pit'' file on odin in pda. That will fix
Click to expand...
Click to collapse
Hi
I like to share how I fixed my S4 using ODIN 3.09
1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!

mgolejnik said:
Hi
I like to share how I fixed my S4 using ODIN 3.09
1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!
Click to expand...
Click to collapse
Hi there,
Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??
I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware
Or have I completely misunderstood your resolution/fix?

CarlM34 said:
Hi there,
Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??
I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware
Or have I completely misunderstood your resolution/fix?
Click to expand...
Click to collapse
But I never wrote that I had installed version 4.3 / 4. This is the version which is installed this time: I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar after this I flash CF-Auto-Root-jflte-jfltexx-gti9505.tar and now it is rooted and it is KNOX (but not for long)
Maybe I made a mistake. If so, sorry
...
I MADE MISTAKE!!! I am so sorry for that!!!
I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar it is newest version it's 4.4.2!!! I am sorry again.

I'm Also Having a problem with my samsung s4 gt-i9505 (INS)
i was trying to flash my phone with 4 files of firmware with Odin3 v3.10.6
and while flashing i got this problem
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.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> BL_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.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_I9500DDUHPE1_REV01_CL1856465_SIGNED.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_ODD_I9500ODDHOJ1_CL5979820_QB6580299_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1005)..
<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> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if you have any solution please reply

My phone resisting odin flash

my phone is bricked, it will not flash stock rom via odin, i asked on the main forum what the log meant, i was told i needed a pit file, so i got one, and tried again, but it still fails, so here is the log, please tell me what to do.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360XXMI1_S5360XEUMI1_S5360XXMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

Try Adding the pit file+the stock rom in odin and flash them together, and see if that works

did you do the download mode
Power off phone
Press and hold Home + Volume down + Power on button
Press volume up to confirm and enter download mode

i did flash the pit and stock rom together in odin, and then tried separately, and yes of course i was in download mode!!!
still no good though...

Kobro said:
i did flash the pit and stock rom together in odin, and then tried separately, and yes of course i was in download mode!!!
still no good though...
Click to expand...
Click to collapse
Try to connect mobile using SS port. i.e. the USB port with different colour in a laptop. It is also known as US 3.0 port!

Kobro said:
my phone is bricked, it will not flash stock rom via odin, i asked on the main forum what the log meant, i was told i needed a pit file, so i got one, and tried again, but it still fails, so here is the log, please tell me what to do.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360XXMI1_S5360XEUMI1_S5360XXMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It failed because you have not split the firmware first - Galaxy y does not support single file flashing
You need to split the firmware into pda modem and csc - You can do this by using splitfus2 link in my signature
However I have already split pretty much all available firmware which you can find on my firmware thread - http://forum.xda-developers.com/showthread.php?t=2568853
The one that you want based on what your odin log says will be
http://d-h.st/hOn

I screwed up flashing with odin. Plz halp!

SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.

T1geR086 said:
SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.
Click to expand...
Click to collapse
What did you flash, firmware wise? What are you trying to flash?

I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.

T1geR086 said:
I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.
Click to expand...
Click to collapse
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app

ickedmel said:
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried re downloading:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
HEROQLTE_USA_VZW.pit Tried several more times.
Errors:
"re-partition operation has failed" nearly immediately after start of ODIN flash every time.
On boot attempts it does "erase" and "System Update", reboots and comes up in Android Recovery with "Supported API: 3" and "dm-verity verification failed..."
If someone could point me I don't mind learning and figuring it out, but yeah....tad frusterated so I'm gonna smoke some cancer lol brb.

Are you using the modified odin? The original one wont work. The modified one is in the root guide.

Do what he suggests. Use the modified Odin. If that does not work try swapping cables, computers, etc...

craazy82013 said:
Are you using the modified odin? The original one wont work. The modified one is in the root guide.
Click to expand...
Click to collapse
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Will try again.
Flash BL AP CP CSC, or BL AP CP CSC +pit or AP CP CSC?
Want to make sure I at least get this right.

T1geR086 said:
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Click to expand...
Click to collapse
Does the phone even boot? USB debugging on?

craazy82013 said:
Does the phone even boot? USB debugging on?
Click to expand...
Click to collapse
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.

T1geR086 said:
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.
Click to expand...
Click to collapse
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.

craazy82013 said:
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.
Click to expand...
Click to collapse
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.

T1geR086 said:
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.
Click to expand...
Click to collapse
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother

craazy82013 said:
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother
Click to expand...
Click to collapse
Not trying to be short. Sorry if it came off that way. I appreciate hitting up a dev. I've been rather fixated on fixing this...*phone detox itch*

New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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 engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auth error instead of re-partition failure.

T1geR086 said:
New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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 engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auth error instead of re-partition failure.
Click to expand...
Click to collapse
What version of Odin are you using?

Illogi.xbone said:
What version of Odin are you using?
Click to expand...
Click to collapse
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)

Try using Odin 3.14

T1geR086 said:
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)
Click to expand...
Click to collapse
Dont think you can downgrade ph1. Bootloader supposedly changed. There is a faster download in the forum. Way faster. http://downloadmirror.co/29Uj/G930VVRU2APE1_G930VVZW2APE1_VZW.zip<br />

Illogi.xbone said:
Try using Odin 3.14
Click to expand...
Click to collapse
Ty will try. Best place to find that? Odin downloader lists odin3 3.11.2 as latest? Didn't see any 14 ending versions.