Related
Well I just had my phone replaced today due to a bad proximity sensor. I got home and decided to update it to EB18 with root from this thread. Well Odin crashed on me. I tried again and selected Odin3 1.61, selected the pit and tar, selected repartition (per instructions) and clicked start. I let it sit for 30 minutes and still no response. This is the response from Odin and the phone is in download mode with no blue progress bar. Odin is recognizing the phone when I connect it to the computer.
<ID:0/005> Added!!
<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!!
Click to expand...
Click to collapse
The 1 + power button puts me in download mode. Whenever I just press the power button I see an icon that is a cell phone + caution + computer. I've tried two different cables (one even worked 100% on my old phone), different USB ports and different computers. I tried the stock tar/pit and even the Samsung update app for 2.2. I still cannot Odin this phone successfully. Anyone have any other ideas?
Try Odin again, as long as you can get into Download Mode, you are NOT bricked.
Be sure to follow EXACT instructions.
If it was bricked it wouldn't turn.on at all. Its like that cause it doesn't have anything to.boot up. Try downloading the tar file again.
Sent From My Evo Killer!
Well you guys must have brought me some luck. I tried Odin1.7 and it seems to be successfully flashing DI18 rom. *crosses fingers*
Edit: After hours of trying it finally flashed successfully to DI18 but will not flash to any other version (EB13 Extended will just sit at "Set PIT file..").
Are you using a pit file? Of it flashed to di18 and wont to eb13 then try redownloading the tar file. Might be a bad download
Sent From My Evo Killer!
musclehead84 said:
Are you using a pit file? Of it flashed to di18 and wont to eb13 then try redownloading the tar file. Might be a bad download
Sent From My Evo Killer!
Click to expand...
Click to collapse
Yep I'm using the .pit that was included with the EB13 Extended archive. I followed the instructions and checked Re-Partition and then it sits at:
<ID:0/005> Added!!
<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!!
Click to expand...
Click to collapse
If I use other stock roms (EB13, DI18, DK28) I will used s1_odin_20100512.pit or victory_8G_100528.pit and follow instructions and NOT click Re-Partition and I get
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-DI18-8Gb-REL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Another odd thing is if the phone is turned off and I connect it to the USB cable, it will boot into the Android system recovery (2e) automatically.
I'm at a loss on why this will not flash. I had zero problems with my last phone (other than the stupid proximity sensor) and this replacement phone just wants to fight me.
Don't use the pit file when trying for the regular eb13 file. Sometimes the pit file causes mine to fail so I quit using them. Try that once.
Sent From My Evo Killer!
Still no go. Keeps failing at params.lfs. I've tried 2 computers, 3 different usb cables, multiple usb ports. I don't know what to do.
Re-Partition checked = Sits at Set Pit File and then nothing.
Re-partition unchecked and with or without pit file = automatic failure.
I spent the last few hours and $35 replacing this phone for nothing.
I appreciate the advice though.
Well I finally got EB13 installed. I pulled out an old netbook and installed the Samsung drivers.
1. Started up Odin3 1.61
2. Removed battery from phone
3. Connected USB cable to phone
4. Connected USB cable to netbook
5. Power + 1
6. Added s1_odin_20100512.pit
7. Added SPH-D700-EB13-8GB-REL.tar.md5
Funky but I finally have a working Epic 4G. I ain't even going to try to root this bastard.
I believe EB13 extended is already rooted.
Mugen678 said:
I believe EB13 extended is already rooted.
Click to expand...
Click to collapse
I opted to go for the stock EB13 instead of the extended.
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
So my phone got ran over, and I shelled out $150 on the deductible for a replacement. I rooted and put TWRP on immediately. I did a full wipe: data, system, cache, and dalvik, and attempted to flash BeanStalk ROM only to get some error that said something like "can't install from the binary". I wanted to try some other ROM, but for some reason mounting USB storage didn't work. So I just ODINed back to stock...which also didn't work. I get the following every time I try to ODIN a ROM
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> mf9fullupgrade.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
After trying to use ODIN, booting normally or booting into recovery gives me a screen that says "firmware upgrade encountered and issue. Please select recovery mode in Kies and & try again" (I installed kies but the recovery mode doesn't find my device).
However, I CAN use ODIN to flash custom recoveries like TWRP or philz, so I'm not without hope. I just don't know what to do.
When I ODIN a recovery on and boot into it, the phone says "RECOVERY IS NOT SEANDROID ENFORCING" if that helps.
THINGS I'VE TRIED
Different USB ports
Different USB cables
Uninstalling/reinstalling drivers
Various ROMS
Different versions of ODIN (settled on 3.09)
Were you on 4.3/MJA or 4.2.2/MF9 when you attempted to install the ROM?
I'd try putting the stock MF9 recovery on and do a factory reset from there. Then Odin the firmware on.
It sounds like you have the 4.3 bootloader which means you also can not install any previous bootloader. This is why you get a fail when sending aboot.mbn. Though you should be able to flash philz recovery and install a different rom. (i'm on the 4.3 bootloader and running 4.2.2) but you loose the ability to run a stock kernel. Hope this helps
skippwhy said:
So my phone got ran over, and I shelled out $150 on the deductible for a replacement. I rooted and put TWRP on immediately. I did a full wipe: data, system, cache, and dalvik, and attempted to flash BeanStalk ROM only to get some error that said something like "can't install from the binary". I wanted to try some other ROM, but for some reason mounting USB storage didn't work. So I just ODINed back to stock...which also didn't work. I get the following every time I try to ODIN a ROM
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> mf9fullupgrade.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
After trying to use ODIN, booting normally or booting into recovery gives me a screen that says "firmware upgrade encountered and issue. Please select recovery mode in Kies and & try again" (I installed kies but the recovery mode doesn't find my device).
However, I CAN use ODIN to flash custom recoveries like TWRP or philz, so I'm not without hope. I just don't know what to do.
When I ODIN a recovery on and boot into it, the phone says "RECOVERY IS NOT SEANDROID ENFORCING" if that helps.
THINGS I'VE TRIED
Different USB ports
Different USB cables
Uninstalling/reinstalling drivers
Various ROMS
Different versions of ODIN (settled on 3.09)
Click to expand...
Click to collapse
wilsonwa said:
It sounds like you have the 4.3 bootloader which means you also can not install any previous bootloader. This is why you get a fail when sending aboot.mbn. Though you should be able to flash philz recovery and install a different rom. (i'm on the 4.3 bootloader and running 4.2.2) but you loose the ability to run a stock kernel. Hope this helps
Click to expand...
Click to collapse
Right before I left for class I started up the MJA full restore and I came back to a working phone! Thank god. I love the false sense of accomplishment that comes from fixing your own mistake.
Grab this tar (it's zipped, so unzip and use tar.md5..) and try it in Odin. It's the full MJA.
Also make sure to run Odin 'As administrator'
My galaxy s4 i9506 is stuck on a Firmware upgrade encountered an issue. I was flashing a rom onto the phone with odin and for some reason it failed and now I cant turn on phne
I went to sammobile and downloaded the version for Ireland but it had vodafone and I am on O2. I tried and it failed again. Not sure if the phones region is Ireland. I have tried everything and the phone turns on with the samsung logo and then nothing?? I can get it into download mode but cannot load any stock rom onto it
Can anyone help?
funkyirishman said:
My galaxy s4 i9506 is stuck on a Firmware upgrade encountered an issue. I was flashing a rom onto the phone with odin and for some reason it failed and now I cant turn on phne
I went to sammobile and downloaded the version for Ireland but it had vodafone and I am on O2. I tried and it failed again. Not sure if the phones region is Ireland. I have tried everything and the phone turns on with the samsung logo and then nothing?? I can get it into download mode but cannot load any stock rom onto it
Can anyone help?
Click to expand...
Click to collapse
Hi mate
Try to do a factory reset from recovery mode see if it helps you get pass the boot logo...if do a factory reset and try to flash again...region would not be a problem to boot up..
MAX 404 said:
Hi mate
Try to do a factory reset from recovery mode see if it helps you get pass the boot logo...if do a factory reset and try to flash again...region would not be a problem to boot up..
Click to expand...
Click to collapse
I cant even get the phone to go into recovery mode. Every time I press vol down and power button it comes up with the Firmware upgrade encountered an issue. Please select recovery in Kies and try again. I can get it to download mode but everything I try to load up fails. When I get it to turn on and press the volume key down it does not boot up
?
funkyirishman said:
I cant even get the phone to go into recovery mode. Every time I press vol down and power button it comes up with the Firmware upgrade encountered an issue. Please select recovery in Kies and try again. I can get it to download mode but everything I try to load up fails. When I get it to turn on and press the volume key down it does not boot up
?
Click to expand...
Click to collapse
Alright. Try this:
When you get the message "Please select recovery in Kies and try again" connect your phone to Odin.
Odin should recognize your phone (mine was detected).
ReFlash your Firmware.
Report back for any further errors.
All the best!
Mandark52 said:
Alright. Try this:
When you get the message "Please select recovery in Kies and try again" connect your phone to Odin.
Odin should recognize your phone (mine was detected).
ReFlash your Firmware.
Report back for any further errors.
All the best!
Click to expand...
Click to collapse
Managed to get it to a reset and all is well except the below now
Tried to load firmware update and failed and ended up doing a factory reset. However now I have the Unfortunately Samsung keyboard has stopped working and I cannot access any keyboard. I went into application manager and cleared data and also forced closure and still pop up keeps coming up
Also cleared cache and dalvik and same thing. Turned it off and on still same pop up. Tried loading up the latest firmware from Sammy mobile for vodafone but I am on O2
http://www.sammobile.com/firmwares/d.../GT-I9506/VDI/
This failed and did reset again and same pop up keeps appearing. Cannot load any other keyboard from Play store as I cannot access keyboard to search or set up email account??
Any other options or fix
funkyirishman said:
Managed to get it to a reset and all is well except the below now
Tried to load firmware update and failed and ended up doing a factory reset. However now I have the Unfortunately Samsung keyboard has stopped working and I cannot access any keyboard. I went into application manager and cleared data and also forced closure and still pop up keeps coming up
Also cleared cache and dalvik and same thing. Turned it off and on still same pop up. Tried loading up the latest firmware from Sammy mobile for vodafone but I am on O2
http://www.sammobile.com/firmwares/d.../GT-I9506/VDI/
This failed and did reset again and same pop up keeps appearing. Cannot load any other keyboard from Play store as I cannot access keyboard to search or set up email account??
Any other options or fix
Click to expand...
Click to collapse
When you tried to flash stock rom again what error you got ( Odin Logs)?
If you flash a stock rom from one carrier or other should not be a problem you only would be missing at most specific bloatware from one of the carriers , the phone should work fine...
Easiest way out is Factory reset and Flash stock rom again....
MAX 404 said:
When you tried to flash stock rom again what error you got ( Odin Logs)?
If you flash a stock rom from one carrier or other should not be a problem you only would be missing at most specific bloatware from one of the carriers , the phone should work fine...
Easiest way out is Factory reset and Flash stock rom again....
Click to expand...
Click to collapse
Not sure need to check but I downloaded the latest firmware(not lollilop) and used latest Odin and then gets nearly up to complete and then goes red and status as Failed. Will post details later
This is the log from Odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUCNI1_I9506VFGCNI2_I9506XXUCNI1_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..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/006> Added!!
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Size)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Bought a Note 5, and now sold my phone, but buyer wants it back to stock. I rooted the phone with King Root, worked without a hitch, and have never run an ROM's, just ran stock 5.1.1 OTA update. I've restore phones in the past back to stock, never had problem like this.
I tried (3) versions of Odin, different ports on my PC, couple of different USB drivers. Odin 9 and 10 but immediately failed using stock firmware file. I then tried Odin 1.85 using Pit / JFLTE_USA_ATT_16G, and another stock firmware file, and had success / passed. But according to directions, I was suppose to unplug the USB cable at Pass, and at Samsung logo remove the battery. I wasn't paying attention, and while connecting, the phone booted without issue to new phone / account menu. I then restarted the phone, and it was still showing Samsung with the unlocked padlock symbol, suggesting it still was rooted. I then tried to run Odin 1.85 files again, this time around it would get part way through and Fail. Now it seems Odin might have bricked my phone, now it just goes to screen saying "Firmware upgraded encountered an issue. Please select recovery mode in Kies& try again.". I've used Kies in the past to back up phones, update firmware a few times, but never had much luck with the app when it came to recovery. I've tried different cables, different ports, same results.
Any suggestions as where to go from here, or what to try next? I have been unable to get the phone in download mode via home, vol. up, and pwr button.
Before the above issue, I was able to see the device in "This PC", I can see both the device storage, and my SD card. Now my PC not recognizing the phone when plugged in.
Galaxy S4 AT&T SGH-I337
Was at Android 5.1.1
Baseband version: I337UCUGOK2
Odin 3.10 1st attempt fail:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Odin flash failed because of a bootloader issue as indicated by the aboot.mbn error. Either the rom is not for the phone or the bootloader in the rom is older than the bootloader in the phone.