Database Users

[Q] Galaxy Y Bricked

Hi,
I am completely new in phone flashing. I met some troubles with my Galaxy Y device.
I will explain the details and hope someone can give me guidelines to fix it.
I have a Galaxy Y that freezes at logo screen when powered up.
We can access Download mode, but not Recovery one.
Initially it had an official rom that has not been modified.
I get trouble with it with a boot loop.
So, I went to Recovery Mode and did a wipe Data. This worked once and then I get boot loop problem 2 days later.
I tried again to wipe data through Recovery mode, but now with out result.
So I decided to flash it … Odin failed and now it stays frozen at the logo screen when powered up.
For the flashing:
- I try on 3 different PC (1 Win7 and 2 XP) and tried different USB ports
- For the drivers, I tried by installing Kies_2.3.3.12085_7_5 and by installing USB drivers only (SAMSUNG_USB_Driver_for_Mobile_Phones.exe)
- I tried a lot of time, with and without restarting Odin
- I tried with Odin 1.83, 1.84 and 1.85 ( I know that 1.84 and 1.85 support S5360 model)
- And I tried using different ROMs
The communication between Odin and the device seems correct (I can see the yellow highlight when connecting the device in Download mode)
I tried some Doky’s packages from here http://forum.xda-developers.com/showthread.php?p=21846620:
- S5360_XXKK6_OXXKK2_XXKK5
- S5360_XXKL3_OXXKL1_XXKL3
- S5360_XXLF3_OXXLF3_XXLF3
I tried also some other packages containing only one file and one dll (retrieved from here as example http://www.tsar3000.com/Joomla/inde...laxy-y-firmwares&catid=55:samsung&Itemid=82):
- S5360XXKL3_LUXKJ1_Luxembourg_Android_2.3.6
- S5360TAJKK3_TLPKK3_Austria_Android_2.3.6
- S5360LUHKJ2_PSNKJ2_Argentina_Personal_Android_2.3.6
- S5360XXLA2_S5360OXXLA2_EUR
- S5360XXKL3_S5360OXXKL1_EUR
I tried also this package, as I saw that some people were able to unbrick there device with it:
GalaxyS5360_DDLA1_2.3.6
This last package contains totoro_0623.pit file. So I tried with and without Re-Partition checked.
I tried also to download totoro_0623.pit file again from other locations and the .pit file with other packages from the previous lists, but without success (Odin always fails).
On point that can be perhaps important is then when flashing, with Odin, the CSC package alone it always succeeds.
The same, when flashing only BOOT package (taken from GalaxyS5360_DDLA1_2.3.6), is it always successful.
I tried also to flash different couples of BOOT and CSC packages and it is always successful.
Unfortunately, I am completely new in this domain and I do not know the purpose of each package (BOOT, PDA, MODEM and CSC).
So, I do not know what to do now ... Perhaps someone can have some advices or guidelines to help.
Thanks again.
Yacy.

refer to youtube watch with video TUT

yabyuh22 said:
refer to youtube watch with video TUT
Click to expand...
Click to collapse
Thank you very much, Tabyuh22, for your advice.
Unfortunately, I did a lot of search already (xda forum and google), but unfortunately without success.
The only unbrick tutorial I found, related to Galaxy Y, is flashing GalaxyS5360_DDLA1_2.3.6 packages with Odin. I tried this already, but unfortunately, it was not successful (Odin flash fails, except if I flash, BOOT and CSC packages only, as explained previously).
Perhaps you have in mind a specific link that I can try?
Thanks again.
Yacy.

Most probably, the Odin you downloaded is a corrupt one, or maybe you're using an older version. Try the one from Doky73's thread.

sorry but i believe its the Odin,
try the v1.85 and do not use a pit file,
very well detailed question,
thanks

can you post screenshot for odin after "Fail" and/or all text in Message area
and I will help I've unbricked my phone just today

Thank you very much for your advice and help.
In fact, I tried already to download Odin 1.85 from different sources. I just tried again, but unfortunately I get the same bad result.
What I find strange is that the flash is successful when using the CSC package only.
I do not know how to put images in the post, so I attached 2 .jpg snapshots of Odin failure and success.
Here is Odin's log when failure (when trying to flash PDA, MODEM and CSC packages):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXLF3.tar.md5 is valid.
<OSM> MODEM_S5360_XXLF3.tar.md5 is valid.
<OSM> CSC_S5360_OXXLF3.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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And here is Odin's log when success (when trying to flash CSC package only):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXLF3.tar.md5 is valid.
<OSM> MODEM_S5360_XXLF3.tar.md5 is valid.
<OSM> CSC_S5360_OXXLF3.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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> csc.rfs
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
Thanks again for your help.
Yacy

Just choose PDA and It's required file and live Phone and CSC alone then you'l be able to boot into Recovery mod

Mohamed.Anwar said:
Just choose PDA and It's required file and live Phone and CSC alone then you'l be able to boot into Recovery mod
Click to expand...
Click to collapse
It seems it is what I did. The result is in the Failed snapshot I attached.
Do you see any thing wrong in this snapshot and the associated logs?
(I tried also to flash PDA or PHONE alone, but failed. It is successful only if I flash CSC alone)
Thanks again.
Yacy.

Try data/cache wipe after flash,maybe it helps
MANY GREEEEETZ!!!

Alright, now when you downloaded the firmware package, there would be 4 different .tar files - BOOT_something.tar, PDA_something.tar, CSC_something.tar and MODEM_something.tar. Sometimes, there is one more, DefaultCalDataBOOT_something.tar, which i use in place of BOOT. Try flashing that in place of BOOT file. Still if it dosen't work, flash the PIT file along. Make sure the PIT's right. Our device's pit is "totoro_0623.pit".

CALIBAN666 said:
Try data/cache wipe after flash,maybe it helps
Click to expand...
Click to collapse
I imagine we can do this only by accessing Recovery Mode.
Unfortunately, I cannot access this mode, but the Download one only

anasdcool71 said:
Alright, now when you downloaded the firmware package, there would be 4 different .tar files - BOOT_something.tar, PDA_something.tar, CSC_something.tar and MODEM_something.tar. Sometimes, there is one more, DefaultCalDataBOOT_something.tar, which i use in place of BOOT. Try flashing that in place of BOOT file. Still if it dosen't work, flash the PIT file along. Make sure the PIT's right. Our device's pit is "totoro_0623.pit".
Click to expand...
Click to collapse
The only package I get containing BOOT file is GalaxyS5360_DDLA1_2.3.6. This package contains:
- BOOT_S5360DDLA1_REV05.tar.md5
- DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5
-PDA_S5360DDLA1_REV05.tar.md5
-MODEM_S5360DDLA1_REV05.tar.md5
-GT-S5360-MULTI-CSC-ODDLA1.tar.md5
Flashing BOOT_S5360DDLA1_REV05.tar.md5 alone is successful and here is Odin’s log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOT_S5360DDLA1_REV05.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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> BcmBoot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
Flashing DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5 alone fails and here is Odin’s log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> DefaultCalDataWithBoot_S5360DDLA1_REV05.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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> BcmBoot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> HEDGE_NVRAM8_RF_LE.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Selecting totoro_0623.pit alone fails and here is Odin’s log:
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The remark when flashing DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5 alone, I can see on the device the progress bar increasing, but it fails before the end.
(I do not have this at all when trying to flash PDA or MODEM files)
Thanks again.
Yacy.

Possible solution : That what I did
Keep ODIN alive don't close it then try changing USB ports and use man ports ( in the back if you're using Desktop PC ) and flash only pit and PDA if it didn't worked restart download mode
then check if you could boot into Recovery mod

Flash some kernel.tar in place of PDA file....
Then you'll be able to boot into recovery and then install any rom ....!!!!

Sorry for the late answer, as I was not available these days.
And thank you for your guide lines.
Mohamed.Anwar said:
Possible solution : That what I did
Keep ODIN alive don't close it then try changing USB ports and use man ports ( in the back if you're using Desktop PC ) and flash only pit and PDA if it didn't worked restart download mode
then check if you could boot into Recovery mod
Click to expand...
Click to collapse
I tried this operation again many times, but I always get flash failure
The_animaToR said:
Flash some kernel.tar in place of PDA file....
Then you'll be able to boot into recovery and then install any rom ....!!!!
Click to expand...
Click to collapse
I had a look to the Development area and tried to flash different kernels.
Unfortunately, I get failures again.
What is different now is that
1/ Odin hangs at the steps below:
<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> boot.img
<ID:0/003> NAND Write Start!!
Click to expand...
Click to collapse
2/ In the phone, “custom bin down” counter is now uncremented.
Its value is 10 (it was zero, before trying to flash kernels from custom roms).
Do you have any other idea?
Does an alternative tool to flash the device exist?
Is there a way (perhaps by using Android design tools) to get more information about why the flash does not work (a more precise error message)?
Thanks again for your help.
Yacy.

Hi try this one ,hope it helps

denniz05 said:
Hi try this one ,hope it helps
Click to expand...
Click to collapse
Hello Yacy, I'm sorry I have no Idea about your problem. I just wanted to ask if you got your issue solved?
Actually, I bought my SGY about 3 weeks ago and I was going through problems of Flashing. I'm also interested in Flashing with a Custom ROM.
And I'm Totally new to Android. If you got the problem sorted out, can you tell me a DETAILED and CLEAR TUT for flashing one?

asd
please give me a link about galaxy y duos bricked please.

yacy said:
Hi,
I am completely new in phone flashing. I met some troubles with my Galaxy Y device.
I will explain the details and hope someone can give me guidelines to fix it.
I have a Galaxy Y that freezes at logo screen when powered up.
We can access Download mode, but not Recovery one.
Initially it had an official rom that has not been modified.
I get trouble with it with a boot loop.
So, I went to Recovery Mode and did a wipe Data. This worked once and then I get boot loop problem 2 days later.
I tried again to wipe data through Recovery mode, but now with out result.
So I decided to flash it … Odin failed and now it stays frozen at the logo screen when powered up.
For the flashing:
- I try on 3 different PC (1 Win7 and 2 XP) and tried different USB ports
- For the drivers, I tried by installing Kies_2.3.3.12085_7_5 and by installing USB drivers only (SAMSUNG_USB_Driver_for_Mobile_Phones.exe)
- I tried a lot of time, with and without restarting Odin
- I tried with Odin 1.83, 1.84 and 1.85 ( I know that 1.84 and 1.85 support S5360 model)
- And I tried using different ROMs
The communication between Odin and the device seems correct (I can see the yellow highlight when connecting the device in Download mode)
I tried some Doky’s packages from here http://forum.xda-developers.com/showthread.php?p=21846620:
- S5360_XXKK6_OXXKK2_XXKK5
- S5360_XXKL3_OXXKL1_XXKL3
- S5360_XXLF3_OXXLF3_XXLF3
I tried also some other packages containing only one file and one dll (retrieved from here as example http://www.tsar3000.com/Joomla/inde...laxy-y-firmwares&catid=55:samsung&Itemid=82):
- S5360XXKL3_LUXKJ1_Luxembourg_Android_2.3.6
- S5360TAJKK3_TLPKK3_Austria_Android_2.3.6
- S5360LUHKJ2_PSNKJ2_Argentina_Personal_Android_2.3.6
- S5360XXLA2_S5360OXXLA2_EUR
- S5360XXKL3_S5360OXXKL1_EUR
I tried also this package, as I saw that some people were able to unbrick there device with it:
GalaxyS5360_DDLA1_2.3.6
This last package contains totoro_0623.pit file. So I tried with and without Re-Partition checked.
I tried also to download totoro_0623.pit file again from other locations and the .pit file with other packages from the previous lists, but without success (Odin always fails).
On point that can be perhaps important is then when flashing, with Odin, the CSC package alone it always succeeds.
The same, when flashing only BOOT package (taken from GalaxyS5360_DDLA1_2.3.6), is it always successful.
I tried also to flash different couples of BOOT and CSC packages and it is always successful.
Unfortunately, I am completely new in this domain and I do not know the purpose of each package (BOOT, PDA, MODEM and CSC).
So, I do not know what to do now ... Perhaps someone can have some advices or guidelines to help.
Thanks again.
Yacy.
Click to expand...
Click to collapse
hey just see http://forum.xda-developers.com/showthread.php?t=1465800

Help, Phone Says " Firmare Upgrade encountered an issue, Please use Software Repair

Help, Phone Says " Firmare Upgrade encountered an issue, Please use Software Repair
Hey Guys,
I have no clue what happened, Phone is stuck in ODIN Mode,
I am in odin 3.09, downloaded the pit file and the latest MJE firmware and i get to this step.
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help a lost soul...
Justin

Install pit by itself. Restart in recovery and factory wipe. Then install firmware
If I helped hit thanks!!

I did the pit file, not it stays locked at Samsung Galaxy Note 3 screen.
2swizzle said:
Install pit by itself. Restart in recovery and factory wipe. Then install firmware
If I helped hit thanks!!
Click to expand...
Click to collapse

Pit File - HLTE_USA_VZW_32G.PIT
PDA - MI9/MJ7/MJE (none work)
I am running odin as an administrator. I just can't get this thing to download to the phone... am i doing something wrong..
I put the phone in download mode.
Ive Done :
Download the MJE Stock Firmware 1.3 GB and extract it once...
Download latest ODIN 3.09...
In your device go into Download mode(Vol Down+Home Button+Power Button) and again Volume Up for Download mode...
Right click ODIN and open as administrator...
Now connect your device to PC and check the status in ODIN as Connected... (COM 5)
Make sure that only Auto Reboot and F.Reset Time are checked in ODIN...
Click on AP and select the extracted file from MJE firmware...
After checking the MD5 file...Click on START and wait I get the following error
-<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> 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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
is there something I am missing?
Thanks in advance!

Looks like you are trying to install I9 in your second post. Unless you were on i9 to start with you cannot downgrade. At the top of your post you refer to MJE. That is probably the reason.
Sent from my SM-N900V using Tapatalk

ive tried them all.. still no luck... verizon is sending me a new phone... it should load through odin, it doesn't nothing..

Well the issue was I was running ODIN in my VMWare Windows 7 Virtual Machine. I got my new phone today from verizon, for ****s i hooked it up to my old Windows XP machine and it went with out a hitch. I unplugged it was 75% so they can have it showing ODIN MODE..
Thanks for all the help...

Flashig Lollipop problem.

Hi guys,
I have a Note 3 N900 and I tried to flash the lollipop firmware from sammobile site following the steps provided:
Instructions
1.Extract (unzip) the firmware file
2.Download Odin v3.09
3.Extract Odin zip-file
4.Open Odin v3.09
5.Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
6.Connect phone and wait until you get a blue sign in Odin
7.Add the firmware file to AP / PDA
8.Make sure re-partition is NOT ticked
9.Click the start button, sit back and wait a few minutes
I followed the steps from 1 to 9 (at 8 I added the firmware ONLY to AP) and I clicked start. In 2 seconds my electric power went down (**** happens) so now on my phone I have the following msg: FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN kIES & TRY AGAIN".
In kies my device is not suported ,. Emergency firmware recovery doesnt work.
What can I do?
Thank you
*Furthermore I downloaded 4.4.2 firmware N900XXUDND1_N900SERDNC4_N900XXUDNC1_HOME.tar and I tried to flash and I got same error:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900XXUEBOA6_N900SEREBOA6_N900XXUEBNL6_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> 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> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

EugenN said:
Hi guys,
I have a Note 3 N900 and I tried to flash the lollipop firmware from sammobile site following the steps provided:
Instructions
1.Extract (unzip) the firmware file
2.Download Odin v3.09
3.Extract Odin zip-file
4.Open Odin v3.09
5.Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
6.Connect phone and wait until you get a blue sign in Odin
7.Add the firmware file to AP / PDA
8.Make sure re-partition is NOT ticked
9.Click the start button, sit back and wait a few minutes
I followed the steps from 1 to 9 (at 8 I added the firmware ONLY to AP) and I clicked start. In 2 seconds my electric power went down (**** happens) so now on my phone I have the following msg: FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN kIES & TRY AGAIN".
In kies my device is not suported ,. Emergency firmware recovery doesnt work.
What can I do?
Thank you
*Furthermore I downloaded 4.4.2 firmware N900XXUDND1_N900SERDNC4_N900XXUDNC1_HOME.tar and I tried to flash and I got same error:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900XXUEBOA6_N900SEREBOA6_N900XXUEBNL6_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> 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> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
hi
The firmware 4.4.2 doesn't flash also?
you can try with Odin V3.10

As far as I know 3.09 it's the last version....

EugenN said:
As far as I know 3.09 it's the last version....
Click to expand...
Click to collapse
have you got a PIT file of your device?

I dont have any PIT file

EugenN said:
I dont have any PIT file
Click to expand...
Click to collapse
Try to find PIT file for N900 (ask on another thread)
and flash the rom with PIT file
Re-repartition ticked

[Q] Requesting a PIT file for SM-T530NU

I've done everything to restore to stock firmware. I used odin-v3.10.6 and Kies 3. They both stop at 4%. My firmware is T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip. But I can flash TWRP-2.8.7 via Odin just fine. But I am running out of ideas.
T530NUUEU1BOE5_T530NUXAR1BOE5_HOME.tar.md5 (2,225,735,835 bytes)
MD5: 5358d7e9247803a164d9a8cbc713bc55
T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip (1,351,979,593 bytes)
MD5: 5c910ca3b4599971669cddf445fef8dc
This is why I'm requesting a PIT file or another solution.
Thanks
Sakui

sakui23 said:
I've done everything to restore to stock firmware. I used odin-v3.10.6 and Kies 3. They both stop at 4%. My firmware is T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip. But I can flash TWRP-2.8.7 via Odin just fine. But I am running out of ideas.
T530NUUEU1BOE5_T530NUXAR1BOE5_HOME.tar.md5 (2,225,735,835 bytes)
MD5: 5358d7e9247803a164d9a8cbc713bc55
T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip (1,351,979,593 bytes)
MD5: 5c910ca3b4599971669cddf445fef8dc
This is why I'm requesting a PIT file or another solution.
Thanks
Sakui
Click to expand...
Click to collapse
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file

thisisapoorusernamechoice said:
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file
Click to expand...
Click to collapse
Some reason TWRP-v2.8.7 can't mount /system when I do a wipe. Is there a way to do it manually and wipe it myself?
Thanks
Sakui

sakui23 said:
Some reason TWRP-v2.8.7 can't mount /system when I do a wipe. Is there a way to do it manually and wipe it myself?
Thanks
Sakui
Click to expand...
Click to collapse
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .

thisisapoorusernamechoice said:
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file
Click to expand...
Click to collapse
I tried everything you said and I got no where. TWRP complained that the file system was read only.

repey6 said:
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .
Click to expand...
Click to collapse
I'm trying it right now. I'm just confused why Odin stops at system.img.ext4. Is the partition corrupt because its read only? But I installed a custom ROM (BlissPOP) and it worked fine.

sakui23 said:
I tried everything you said and I got no where. TWRP complained that the file system was read only.
Click to expand...
Click to collapse
In TWRP 2870 you need uncheck checkbox on Mount button

repey6 said:
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .
Click to expand...
Click to collapse
Service firmware [SM-T530NUUEU1BOE5_XAR_SERVICE_LP.zip] didn't work. It stopped at 4% again. But I have 5.0.1 and not 4.4. TWRP won't let me check "system" under mount.

It stopped at 4% again
Click to expand...
Click to collapse
What is 4% ? Where ? I dont understand this .

repey6 said:
What is 4% ? Where ? I dont understand this .
Click to expand...
Click to collapse
That's where Kies 3 stopped at. It stops in system.img.ext4 [Odin-v3.10.6] at the beginning of it. But it does process it but very little of it.

sakui23 said:
That's where Kies 3 stopped at. It stops in system.img.ext4 [Odin-v3.10.6] at the beginning of it. But it does process it but very little of it.
Click to expand...
Click to collapse
Why Kies . Close it . Use only Odin with him guide . Go to dounload mode . Connect to PC . In Odin download unpack service firmware (BL , AP , CSC ) to their button . And start . Please copy Odin log to me .

Odin v1.85
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_XAR_T530NUXAR1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.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..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The newer version don't spit out an error. Just sits there.

Stop Kies and delete from processes . Stop antivirus .

sakui23 said:
Odin v1.85
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_XAR_T530NUXAR1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.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..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The newer version don't spit out an error. Just sits there.
Click to expand...
Click to collapse
Correct, kies is awful don't use it. Also use Odin v3.10 or 3.09, not 1.85

Boy, do I feel very stupid...
It was the cords. I had 2 extension USB cords attached to the cord for the Tab 4 and used a different USB port.
Now, the service and the regular firmware works now.
Thanks for everything.
Sakui

stock firmware of a300f for a300f/ds

hello, this is my first post, so take it easy on me, I have an SM-a300f/ds and I rooted the phone, it was on 5.0.2, it worked fine but after a restart the phone did not boot up and I cannot enter recovery, the only choice I have is download mode (bootloader). And I found out this issue exist. now in order to make the phone work again i need to install the stock firmware and i download one, it was "4.4.4 Russia" from sammobile, the result was fail. the phone was bought in Iraq, so could it have been the "country/carrier" thing that it failed?
<ID:0/005> 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/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
now i wonder if the firmware for A300f is the same as A300f/ds
if A300f/ds has different firmware then where can i find it, your help is appreciated.
note: i also own a gti9300 and i have flashed thousands of roms.

hawre96 said:
hello, this is my first post, so take it easy on me, I have an SM-a300f/ds and I rooted the phone, it was on 5.0.2, it worked fine but after a restart the phone did not boot up and I cannot enter recovery, the only choice I have is download mode (bootloader). And I found out this issue exist. now in order to make the phone work again i need to install the stock firmware and i download one, it was "4.4.4 Russia" from sammobile, the result was fail. the phone was bought in Iraq, so could it have been the "country/carrier" thing that it failed?
<ID:0/005> 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/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
now i wonder if the firmware for A300f is the same as A300f/ds
if A300f/ds has different firmware then where can i find it, your help is appreciated.
note: i also own a gti9300 and i have flashed thousands of roms.
Click to expand...
Click to collapse
Did u unplug the phone while it was downloading?
If not flash twrp through odin, then enter in recovery (you should able to do this) and wipe data, cache, dalvik and system, then flash the stock firmware

DeadSquirrel01 said:
Did u unplug the phone while it was downloading?
If not flash twrp through odin, then enter in recovery (you should able to do this) and wipe data, cache, dalvik and system, then flash the stock firmware
Click to expand...
Click to collapse
I did not unplugged it after rooting it, however the problem was solved a while ago by restarting the phone after an hour of leaving it, thank you for your help

hawre96 said:
I did not unplugged it after rooting it, however the problem was solved a while ago by restarting the phone after an hour of leaving it, thank you for your help
Click to expand...
Click to collapse
No problem, I'm happy u solved the problem