Related
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
can someone please help me , i tryed to put a new rom on my phone and ended up with it giving me and error saying firmware upgrade encountered an issue please select recovery mode in kies, ive tryed to restore in kies but when i do it ends up saying device not found and failing, i can still get onto download mode
ive tryed diffrent odins and same error all the time the last thing i tryed was full wipe and rebuild still no joy
<ID:0/005> Added!!
<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> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Help is simple you are in the wrong forum this is I9300 .
Use the report button for moving the post .
Based on your previous posts you are either not following the instructions or need a service centre repair .
jje
SAMGS4 said:
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
Click to expand...
Click to collapse
Mh, is this normal for ODIN, having a single PDA file given?
@ SAMGS4: What exactly did you do? For me it looks like you put the same file in all file selection lines.
Do you still have access to phone's UI and can check the complete device properties?
I know this is the wrong device forum but if a mod moves this topic to the proper location, the replies got moved also.
someone please help
HSishi said:
Mh, is this normal for ODIN, having a single PDA file given?
@ SAMGS4: What exactly did you do? For me it looks like you put the same file in all file selection lines.
Do you still have access to phone's UI and can check the complete device properties?
I know this is the wrong device forum but if a mod moves this topic to the proper location, the replies got moved also.
Click to expand...
Click to collapse
thanks and ive just reported the post to be moved, and also i have no access to the phone, i can get it on the download mode and when it says about firmware upgrade kies update etc
Well ... there might be another reason why you can't flash the wanted file - the DL is corrupt. But ODIN checked the md5 hash and the file passed the test.
Did you try to flash another, earlier leaked, ROM for your phone?
Does the ROM match to your country / provider code? Maybe the ROM you try to flash doesn't match exactly to the phone you have; there are various SGS4 models.
someone please help
HSishi said:
Well ... there might be another reason why you can't flash the wanted file - the DL is corrupt. But ODIN checked the md5 hash and the file passed the test.
Did you try to flash another, earlier leaked, ROM for your phone?
Does the ROM match to your country / provider code? Maybe the ROM you try to flash doesn't match exactly to the phone you have; there are various SGS4 models.
Click to expand...
Click to collapse
just tryed a new rom and pit file and heres the results
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 0)
<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/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
my phone was on the (3g) three network uk its a gt-i9505 if someone could direct me to a rom and pit file for my phone i could try would be very much appreciated
heres my LAST ODIN FLASH TRY seems to for got bit further then last time and on my phone i got a little bit of a blue loading bar then it failed
SAMGS4 said:
my phone was on the (3g) three network uk its a gt-i9505 if someone could direct me to a rom and pit file for my phone i could try would be very much appreciated
heres my LAST ODIN FLASH TRY seems to for got bit further then last time and on my phone i got a little bit of a blue loading bar then it failed
Click to expand...
Click to collapse
While flashing using odin make sure no kies programme are running in the background
U can try different cable / usb ports etc will work and try using without pit,
U should use pit file as a last option for now u try without that and do as above will work
.
I Just tried a diffrent usb port and didnt use the pit file and it got a bit futher then first time but failed again here is the results <ID:0/006> 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/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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
someone please help
i just tried diffrent usb post and made sure kies or no firewall was on , didnt use the pit file like you said and phone got bit futher then first time but still failed here the results
<ID:0/006> 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/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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
U
SAMGS4 said:
i just tried diffrent usb post and made sure kies or no firewall was on , didnt use the pit file like you said and phone got bit futher then first time but still failed here the results
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:6)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img.ext4
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Removed!!
Added!!
Click to expand...
Click to collapse
Did u close all the kies programme from the background that must be the issue
Or uninstall kies and try
There should be 3 four kies file running in the background close all from task manager try restarting pc and try
someone please help
just uninstalled kies and tryed same as before
someone please help
i have a laptop with windows xp on it should i try on this??
OTE=SAMGS4;44354942]i have a laptop with windows xp on it should i try on this??[/QUOTE]
I'd give it a try. Update the drivers before you attempt it. I'm on three as well and have flashed the same firmware without problems. Have you tried flashing a recovery and wiping the phone. Internal SD etc? Wouldn't do it any harm
someone please help
symondo12 said:
OTE=SAMGS4;44354942]i have a laptop with windows xp on it should i try on this??
Click to expand...
Click to collapse
I'd give it a try. Update the drivers before you attempt it. I'm on three as well and have flashed the same firmware without problems. Have you tried flashing a recovery and wiping the phone. Internal SD etc? Wouldn't do it any harm[/QUOTE]
hi could you please give me a link to stock rom for three please as cant find one and what recovery would i flash?? thanks?
Mh, can you get into Recovery mode? If not, flash an alternate Recovery mod first. Try PhilZ Touch Recovery. It's being flashed within DL mode, fill only PDA field.
Ah, I didn't notice yet ... you use ODIN 3.04. That's an outdated version; maybe 3.04 can't handle an I9505.
Most current version is 3.07, get it here. In this post it's said ODIN 1.85 can already deal with an I9595; try this too.
Does ODIN run with Admin rights? Maybe there's a problem with your Windows UAC.
//HSishi
http://forum.xda-developers.com/showthread.php?t=2281367
That's the link for philz recovery. Download the latest .tar and flash in O.
Boot into recovery and wipe everything including the internal SD. Make sure you back up.
By the looks of it you are flashing the latest three firmware. MEA H3G.
I'd download the firmware again. You can get it from Sammobile.com. you'll need to register an account. Think its labelled as Hutchisons 3G
someone please help
i just tryed to flash PhilZ Touch Recovery and it failed, also ive tried all the odins and the one that seems to get me the furthest is the 3.04
someone please help
anymore ideas?? pls:crying:
Have you tried another PC, one with Win 7 or 8 on it?It doesn't look like a partition problem, it seems to get further through each time but keeps failing. Might be a problem with your PC...
Oh, and I use ODIN 3.04 to flash too...
(Previous thread can be seen here)
Hi all,
Thank you for whom reads this thread. - Very recently I tried to root my Samsung Galaxy Note 3. The method I was using was the Kingo application that isn't prohibited on the forum which I now know. At this point I am unsure what to do, besides flashing this but I am unsure if this method will work. Plus I do not know how to flash this or where to even begin.
Basically in short, I tried doing the following:
Root with the Kingo root application that I got from the official site.
After I used Wanam Exposed to customize my stock ROM.
Played on my phone for a bit and then I got a random error: "Unfortunately, System Ui has stopped"
I posted a thread about this issue (without much detail on what I was doing) and I was recommended to flash these stock files which didn't work. Here is the following errors while I try to flash the file in Odin:
Code:
<ID:0/003> Added!!
<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/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point I do not know what to do. I am not hard bricked but I assume I am soft bricked because my phone will not boot into my system because of the error I posted above. If anyone can get me on the right track this would be great. Thank you.
the same thing has happened to me before and i plugged my phone into the computer and used the built in verizon upgrade center and went to the repair section
Storm.hf said:
(Previous thread can be seen here)
Hi all,
Thank you for whom reads this thread. - Very recently I tried to root my Samsung Galaxy Note 3. The method I was using was the Kingo application that isn't prohibited on the forum which I now know. At this point I am unsure what to do, besides flashing this but I am unsure if this method will work. Plus I do not know how to flash this or where to even begin.
Basically in short, I tried doing the following:
Root with the Kingo root application that I got from the official site.
After I used Wanam Exposed to customize my stock ROM.
Played on my phone for a bit and then I got a random error: "Unfortunately, System Ui has stopped"
I posted a thread about this issue (without much detail on what I was doing) and I was recommended to flash these stock files which didn't work. Here is the following errors while I try to flash the file in Odin:
Code:
<ID:0/003> Added!!
<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/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point I do not know what to do. I am not hard bricked but I assume I am soft bricked because my phone will not boot into my system because of the error I posted above. If anyone can get me on the right track this would be great. Thank you.
Click to expand...
Click to collapse
Could you please link me to the software
Sent from my GT-P5113 using xda app-developers app
I think your phone may have had firmware that was later than what you were trying to flash. From what you posted you were flashing mi9 which was the first one with initial released phones. They would explain the soft brick. Then there was update MJ7 and now there is MJE. I would suggest finding the MJ7 tar file and try that and see if that will fix the soft brick. If same results then try MJE.
Hope this helps.
Tap'n & Talk'n on my Note 3
Hello everybody
I've a great problem with my samsung galaxy s4 (i9505).
Today i buyed a new sdcard for my phone. I thought it would be a good idea to do a real clean up.
So i flashed the samsung stock recovery, stock kernel and the stock rom (from SAMMOBILE) . Worked perfectly.
Afterwards, i flashed the newest cwm recovery (6.0.4.7 touch). Worked again.
Copied my rom (aosb = android open source bam project) to the external sdcard.
I removed the external card and went to the mounts and storage entry.
Now the part, that hardly failed:
I wiped everything (every point under mounts), incl. /firmware and another point with /firmware (I think it was /firmware_dmm or something like this)
At least, i wiped the external sdcard. Because there was no, the recovery crashed (...) and rebooted.
Now i get this error: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If i flash something over ODIN (stock recovery, stock rom, custom recovery or custom rom) it ends up in a "FAIL".
Log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFND7_I9505YFGFND1_I9505XXUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
KIES doesnt find my device, but i already installed the newest samsung usb driver.
So i can't use the emergeny firmware "reset" of KIES.
If i start the phone normaly, the above error appears. Same, if i boot into recovery.
The only working thing is the downloading mode....
I also removed the battery for 15 minutes. But that changed nothing.
What can i do to "repair" my phone? Is it bricked?`
Thank you for reading
(Cant insert links to roms or images because of low post counter)
1. Reflash the firmware that u installed b4.
2. Flash TWRP or PhilzTouch using ODIN.
I still have TWRP running but I cant install anything from the micro-sd card. Before I started I used twrp for a backup it showed that it made a backup well I trusted it and didn't go look on sd card to see if it was there my mistake its not there, then I tried going with another rom I downloaded Super_S4_Odexed_NAE_v1.5.zip well it wasn't working so then i downloaded Stock-MDL-Stable-spr-TW.zip( its supposed to help for the rom downloaded) and loaded it on my sd card with my pc well i put micro-sd card in phone and it wont read it so I can install with twrp I also tried odin with stock mdl.tar and it fails, so what I need to know is how to start over with wipe and get something i need so it will read at boot up( do i need a bootloader?)and my files from sd card it reads all but my downloaded zip files
my system is a Sprint Samsung Galaxy S4
original stock was L720VPUAMDC.tar
I get this from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flash back MDC tar, it's the best base.
Sent from my SM-N900P
dr.faramroze said:
Flash back MDC tar, it's the best base.
Sent from my SM-N900P
Click to expand...
Click to collapse
I get this from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Have you tried heimdall or one click unbrick tool
Howiewowie said:
I get this from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.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> aboot.mbn
<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
Have you tried heimdall or the one click unbrick tool? One click unbrick is based on heimdall. Please try this. http://forum.xda-developers.com/showthread.php?t=1153310
ashikrobi said:
Have you tried heimdall or the one click unbrick tool? One click unbrick is based on heimdall. Please try this. http://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
it does not read my Samsung it does not show in the list and I do have drivers installed on my pc
Howiewowie said:
it does not read my Samsung it does not show in the list and I do have drivers installed on my pc
Click to expand...
Click to collapse
Download heimdall package. You will get driver in that package.
ashikrobi said:
Download heimdall package. You will get driver in that package.
Click to expand...
Click to collapse
it fails to install the driver i tried everything on resolution center also
Howiewowie said:
it fails to install the driver i tried everything on resolution center also
Click to expand...
Click to collapse
I have got this but it wont boot up
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltespr-jfltespr-sphl720.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Howiewowie said:
I have got this but it wont boot up
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltespr-jfltespr-sphl720.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Were you successful flashing the stock rom? If yes, try factory reset from recovery. You said you failed to install heimdall driver. What is the problem? Please try to run one click unbrick tool. It's easy and will guide you. You need java to use it.
ashikrobi said:
Were you successful flashing the stock rom? If yes, try factory reset from recovery. You said you failed to install heimdall driver. What is the problem? Please try to run one click unbrick tool. It's easy and will guide you. You need java to use it.
Click to expand...
Click to collapse
I was not successful flashing stock rom look above my root rom flash it failed and how can it install the unbrick tool when pc doesn't read my phone when I know my samsung drivers are on the hdd it will not even show it listed on other devices
Howiewowie said:
I was not successful flashing stock rom look above my root rom flash it failed and how can it install the unbrick tool when pc doesn't read my phone when I know my samsung drivers are on the hdd it will not even show it listed on other devices
Click to expand...
Click to collapse
Can you please upload screenshots? I do not understand, your screenshot shows odin detects your device. What really happens when you connect your device to pc?
Have you tried ##3424# menu to enable samsung diag port? Is it requesting to install qhsusb_dload driver when you connect it to pc?
i still don't get why you can't install from SD card. are you saying TWRP isn't reading from the SD card? have you tried a different memory card? because you could of just updated the recovery to a different recovery. from my experience, CWM seems to be the most dependable recovery to use.
in any case, i don't understand what you mean your PC won't detect the phone if you're able to use odin..
one other suggestion is to try using adb push to push a files from your pc directly to the phone memory. here's how to do it http://forum.xda-developers.com/showthread.php?t=2266638
Howiewowie said:
I still have TWRP running but I cant install anything from the micro-sd card. Before I started I used twrp for a backup it showed that it made a backup well I trusted it and didn't go look on sd card to see if it was there my mistake its not there, then I tried going with another rom I downloaded Super_S4_Odexed_NAE_v1.5.zip well it wasn't working so then i downloaded Stock-MDL-Stable-spr-TW.zip( its supposed to help for the rom downloaded) and loaded it on my sd card with my pc well i put micro-sd card in phone and it wont read it so I can install with twrp I also tried odin with stock mdl.tar and it fails, so what I need to know is how to start over with wipe and get something i need so it will read at boot up( do i need a bootloader?)and my files from sd card it reads all but my downloaded zip files
my system is a Sprint Samsung Galaxy S4
original stock was L720VPUAMDC.tar
I get this from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.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> aboot.mbn
<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
edit:
Are you running Odin 1.85 or 3.09?
Are you running Odin as administrator?
The computer does see your phone, so that isn't the issue.
What version of Stock S4 were you running prior to flashing Super_s4?
If it was KitKat 4.4 then you'll need to download stock 4.4 from samsung, you cannot downgrade back to 4.2 or 4.3 if your phone came as stock 4.4, sorry.
When you are booting to download mode, are you doing it from a full powered off state? Make sure the phone is fully powered down, even pull the battery and let it sit for a minute or two before you boot to download mode.
What version of twrp did you flash? Versions older than 2.7.0.1 have problems flashing kitkat roms. As an earlier poster suggested, go get CWM 6.0.4.4 (IIRC) or the newest Philz touch and try flashing from that.
Do you have a card reader and a micro-sd to sd adapter you can use on your pc, or maybe a USB-OTG adapter? If so, make sure whatever ROM you want to flash is on the root of the SD card. I have both, and I keep an old spare 2GB micro sd formatted ex-fat that I can quickly format again and copy any ROM to if I need to flash, and if that doesn't work or I can't find it, I have a USB-OTG cable and I'll use any thumb drive I may have sitting around to copy a ROM and flash that way.
wilzard said:
edit:
Are you running Odin 1.85 or 3.09?
Are you running Odin as administrator?
The computer does see your phone, so that isn't the issue.
What version of Stock S4 were you running prior to flashing Super_s4?
If it was KitKat 4.4 then you'll need to download stock 4.4 from samsung, you cannot downgrade back to 4.2 or 4.3 if your phone came as stock 4.4, sorry.
When you are booting to download mode, are you doing it from a full powered off state? Make sure the phone is fully powered down, even pull the battery and let it sit for a minute or two before you boot to download mode.
What version of twrp did you flash? Versions older than 2.7.0.1 have problems flashing kitkat roms. As an earlier poster suggested, go get CWM 6.0.4.4 (IIRC) or the newest Philz touch and try flashing from that.
Do you have a card reader and a micro-sd to sd adapter you can use on your pc, or maybe a USB-OTG adapter? If so, make sure whatever ROM you want to flash is on the root of the SD card. I have both, and I keep an old spare 2GB micro sd formatted ex-fat that I can quickly format again and copy any ROM to if I need to flash, and if that doesn't work or I can't find it, I have a USB-OTG cable and I'll use any thumb drive I may have sitting around to copy a ROM and flash that way.
Click to expand...
Click to collapse
its ok now I took my SGS4 back to Sprint they said they cant figure it out so they are giving me a brand new S4 my phone kinda burned out the screen was turning green on boot up well my insurance covered it thanks for the help
Yeah, he wasn't on MDC. The fail point he was getting meant he already had the knox bootloader.