Related
i was running creed's rom v2.1 and was wishing to upgrade my firmware,PDA n CSC with files in doky's thread.
i was reading about preparing phone before odin flash on internet and found that its advisable to hard reset mobile before flashing through odin..
so i got this code *2767*3855# and i entered it and after a while my phone rebooted and was stuck at boot animation with continues boot loops..
i quickly removed the back cover and removed the battery for 30 sec and put it back....tried to go into recovery mode using normal [volup]+[home]+[power] and it didint enter recovery , instead rebooted again and same..boot loops
i then assumed that my phone was bricked
i then went on to this tread for soft/hard brick http://forum.xda-developers.com/showthread.php?t=1498327
followed that link to the forum....decided to flash my phone to stock as MY PHONE COULD BOOT INTO DOWNLOAD MODE AND NOT RECOVERY
i downloaded the S5360XXXXX_S5360XXXXX_S5360XXXXX_HOME.tar.md5 file...opened odin v1.85 as admin in win7....then loaded that file onto PDA and left all other boxes to default ,,,connected my mobile via USB in recovery mode and i got the following error...i keep getting this error....no matter what i do...even earlier i tried installing doky's packages using odin and my odin gave same error...i tried both odin version....v1.85 and v1.84
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6102DDLA3_S6102ODDLA3_S6102DDLA3_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl.bin
<ID:0/005> BcmCP.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP GUYS :'(
WHAT SSHOULD I DO NOW ? :'(
IS THERE ANYWAY OUT ?
machinehead121 said:
i was running creed's rom v2.1 and was wishing to upgrade my firmware,PDA n CSC with files in doky's thread.
i was reading about preparing phone before odin flash on internet and found that its advisable to hard reset mobile before flashing through odin..
so i got this code *2767*3855# and i entered it and after a while my phone rebooted and was stuck at boot animation with continues boot loops..
i quickly removed the back cover and removed the battery for 30 sec and put it back....tried to go into recovery mode using normal [volup]+[home]+[power] and it didint enter recovery , instead rebooted again and same..boot loops
i then assumed that my phone was bricked
i then went on to this tread for soft/hard brick http://forum.xda-developers.com/showthread.php?t=1498327
followed that link to the forum....decided to flash my phone to stock as MY PHONE COULD BOOT INTO DOWNLOAD MODE AND NOT RECOVERY
i downloaded the S5360XXXXX_S5360XXXXX_S5360XXXXX_HOME.tar.md5 file...opened odin v1.85 as admin in win7....then loaded that file onto PDA and left all other boxes to default ,,,connected my mobile via USB in recovery mode and i got the following error...i keep getting this error....no matter what i do...even earlier i tried installing doky's packages using odin and my odin gave same error...i tried both odin version....v1.85 and v1.84
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6102DDLA3_S6102ODDLA3_S6102DDLA3_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl.bin
<ID:0/005> BcmCP.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP GUYS :'(
WHAT SSHOULD I DO NOW ? :'(
IS THERE ANYWAY OUT ?
Click to expand...
Click to collapse
try updating thru kies or flashing custom rom...
zeusseuz said:
try updating thru kies or flashing custom rom...
Click to expand...
Click to collapse
but sir how can i ?
odin keeps giving me that error with my phone
it cant even enter recovery mode....nor does it boot completely...just has boot loops
please suggest me a way out
budy the file you try to flash its not right.its one file and odin dont suport it for our phone.go to development section and find odin firmware packages by Docky.download yours and flash it!you are ready!report back if need more help
termagazis said:
budy the file you try to flash its not right.its one file and odin dont suport it for our phone.go to development section and find odin firmware packages by Docky.download yours and flash it!you are ready!report back if need more help
Click to expand...
Click to collapse
sir....i tried already.......and after you said so//..i just tried again.....here it is..same error
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
machinehead121 said:
sir....i tried already.......and after you said so//..i just tried again.....here it is..same error
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
so the firmware you downloaded was one file or 3 files?
termagazis said:
so the firmware you downloaded was one file or 3 files?
Click to expand...
Click to collapse
3 compressed files sir
PDA_S5360_DDLA3
MODEM_S5360_DDLA2
CSC_S5360_ODDLA2
machinehead121 said:
3 compressed files sir
PDA_S5360_DDLA3
MODEM_S5360_DDLA2
CSC_S5360_ODDLA2
Click to expand...
Click to collapse
ok just checking your steps.
so you put pda_s5360 in pda field
modem in phone field
csc in csc field
right?and you didnt check the repartition ?
At first, I think Your phone wasn't bricked, it was just a slight boot-loop.
Maybe You pressed the buttons in wrong tact.
As long as you see boot animation, the recovery and download menu 100% surely accessible.
Try again to go download monde, flash one of my packages (avoid one-file packs)!
If got boot loop, then go to recovery (follow my hints in post #2 of Odin packs topic to access recovery and download mode)
...then wipe cache and data!
Hope you succeed!
termagazis said:
ok just checking your steps.
so you put pda_s5360 in pda field
modem in phone field
csc in csc field
right?and you didnt check the repartition ?
Click to expand...
Click to collapse
yup.....exactly...all steps neatly followed as mentioned in doky's post
machinehead121 said:
yup.....exactly...all steps neatly followed as mentioned in doky's post
Click to expand...
Click to collapse
weird.try another firmware
Doky73 said:
At first, I think Your phone wasn't bricked, it was just a slight boot-loop.
Maybe You pressed the buttons in wrong tact.
As long as you see boot animation, the recovery and download menu 100% surely accessible.
Try again to go download monde, flash one of my packages (avoid one-file packs)!
If got boot loop, then go to recovery (follow my hints in post #2 of Odin packs topic to access recovery and download mode)
...then wipe cache and data!
Hope you succeed!
Click to expand...
Click to collapse
not sure about slight boot loop sir...but it was stuck on boot anim for quite a long time....
i did sir..i tried flashing only 1 of your package....modem....and same error again
and i still cant enter recovery mode....download mode is still accessible....but now....my phone is not even able to go up till boot anim :| its just stuck on samsung logo
termagazis said:
weird.try another firmware
Click to expand...
Click to collapse
i tried single packs as well sir.....like just pda...or modem......still same error.....odin aint working no matter what i do "(
machinehead121 said:
i tried single packs as well sir.....like just pda...or modem......still same error.....odin aint working no matter what i do "(
Click to expand...
Click to collapse
i mean download another firmware from doky put all files and flash.another firmware different than that you try
On SAMMOBILE there is two DDLA1 packs, one of them (named S5360DDLA1_S5360ODDLA1_ODD.rar ) contains 4 or 5 files.
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-S5360&r=2#regiona
Download and flash it, with the bootloader part as well!
Put "DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5" to the bootloader, and the other parts as usual (PDA, MODEM, CSC)
PIT and repartition NOT NEEDED!
termagazis said:
i mean download another firmware from doky put all files and flash.another firmware different than that you try
Click to expand...
Click to collapse
ok sir...it is gonna take time for me to download the packages again...
or should i just just take my phone to samsung service centre ?
Doky73 said:
On SAMMOBILE there is two DDLA1 packs, one of them (named S5360DDLA1_S5360ODDLA1_ODD.rar ) contains 4 or 5 files.
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-S5360&r=2#regiona
Download and flash it, with the bootloader part as well!
Put "DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5" to the bootloader, and the other parts as usual (PDA, MODEM, CSC)
PIT and repartition NOT NEEDED!
Click to expand...
Click to collapse
oh i searched that file and iam downloading it now sir
gonna try this one too *fingers crossed*
is this a serious issue sir ?
btw, Kies has to be closed when flashing via Odin!
doky73 said:
btw, kies has to be closed when flashing via odin!
Click to expand...
Click to collapse
omg...sir i wanna thank you alotttttttttttttt !!
It worked :d
hell your awesome sir ! :d
hats off to you.
Wish i could do something more than pressing thanks button..but i can wish goodluck for you and your future projects =)
once again thanks alot sir !
...........
please help me someone i had the stock el29 system and tried to root it with this
http://forum.xda-developers.com/showthread.php?t=1433101&highlight=el29+root
but it froze at factoryfs.im so im waited 25 mins then tried doing the odin manually by putting the file in myself then it went all the way to rqt_close then nothing it stuck.
i need to get rooted cause i want this rom but i will take anything now rooted non rooted i just want my phone fixed.
http://forum.xda-developers.com/showthread.php?t=1512419&highlight=fd24
it (auto root) made my phone say "firmware upgrade encountered and issue. please select recovery mode in kies & try again.
my first device. i couldnt connect to odin and computer wouldnt recognize device so i took it to sprint and they gave me a replacement.
i figured it was a bad download or something so i downloaded it again today and it messed this phone up to only this phone connects to pc and is recognized but when i try to upload the rom on the regular odin and not the one click it stuck at rqt_close and im confused as to what to do now. i dont even have to be rooted anymore i just want a rom on this phone i was out of a phone for 5 days for that Rom and its messed me over again.
1st time it stuck at factoryfs.img then i got replacement and it stuck at modem and then i took out battery after it was froze for like 25 mins. please help me!!!
Have you tried a different USB cable and/or computer?
yes ive tried a different cable but i only have this one computer. its recognizable through odin and my computer im a little dissapointed though. ive been flashing roms for 2 yrs almost and this has never happened to me
TamiaSky said:
yes ive tried a different cable but i only have this one computer. its recognizable through odin and my computer im a little dissapointed though. ive been flashing roms for 2 yrs almost and this has never happened to me
Click to expand...
Click to collapse
Can you get into recovery mode?
no i cant get into recovery just that dreadful notice but i can get into download mode, so thats a good thing im guessing.
i get all the way to the end to rqt_close then it says my device has been removed like odin is kicking me out or something. i dont unplug my phone or anything but it gets all the way to the end then says removed then failed
You get that message whenever ODIN doesn't complete a download. It doesn't mean much, other than the previous download didn't complete.
Is ODIN flashing anything or does it just stop right away?
If you are using regular ODIN, can you double-check you are using the PDA slot and not the Phone slot?
sfhub knows WAY more about Odin then I do but did you also try to Odin a different stock build to see what happens?
sfhub said:
You get that message whenever ODIN doesn't complete a download. It doesn't mean much, other than the previous download didn't complete.
Is ODIN flashing anything or does it just stop right away?
If you are using regular ODIN, can you double-check you are using the PDA slot and not the Phone slot?
Click to expand...
Click to collapse
ive tried the auto packages and doing it manually and when i did it manually i made sure tat it was the pda slot and i unchecked the re-partition when it popped up as well then after looking around on the internet still i used one of the 7-zip packages and used the pit file with it and checked re-partition and still nothing. odin gets all the way to the end right after modem and then sticks on rqt_close then says removed now it just did this
<ID:0/006> 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/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> recovery.bin
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006>
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
i really hope you guys can help me. im so serious if i get this fixed ill never try to root this phone again. i dont wanna have to get another replacement phone.
MeWarning said:
sfhub knows WAY more about Odin then I do but did you also try to Odin a different stock build to see what happens?
Click to expand...
Click to collapse
no ive only been trying the el29 one the rooted one, then i tried the el29 that was just stock and not rooted.
Is this the NoData or Full version you are flashing?
Try the NoData if you are using the Full.
I'm curious, you were on ICS before. Did you happen to do a wipe/factory restore or nandroid restore using ICS kernel and custom recovery?
TamiaSky said:
no ive only been trying the el29 one the rooted one, then i tried the el29 that was just stock and not rooted.
Click to expand...
Click to collapse
Well first if you look in the reference section B in the one you've been trying to Odin(http://forum.xda-developers.com/showthread.php?t=1433101&highlight=el29+root) there's separate tar files for the modem, kernel, and rom. Why don't you try doing each one one at a time to see if anything will succeed.
And if that doesn't work try to Odin one of the leaked stock ICS builds sfhub has also.
This is what happens when I do it manually without the auto package.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.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> recovery.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
then it freezes
sfhub said:
Is this the NoData or Full version you are flashing?
Try the NoData if you are using the Full.
I'm curious, you were on ICS before. Did you happen to do a wipe/factory restore or nandroid restore using ICS kernel and custom recovery?
Click to expand...
Click to collapse
its the full, and ive never been on ics
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.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> recovery.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
now i will try the no data and see what happens.
thanks guys for helping me with this. the no data is downloading right now and i looked on my computer i tried to flash the ek02 sorry, i forgot that one.
TamiaSky said:
thanks guys for helping me with this. the no data is downloading right now and i looked on my computer i tried to flash the ek02 sorry, i forgot that one.
Click to expand...
Click to collapse
No problem, just let us know how it goes.
Don't worry about flashing the NoData version, you don't have the issue I was thinking you might.
Why don't you just flash the modem by itself and see if that works. As the previous poster mentioned, it is in the 2nd post reference section.
If it doesn't work, then just flash the kernel by itself. It should work, and then your phone shouldn't complain about the last flash failing and theoretically should boot. Basically you have completed flashing everything but the modem.
If it still doesn't boot, then ODIN flash CWM only and then flash the modem from recovery. This will increment your ODIN flash count, but it is better than a phone not working.
sfhub said:
Don't worry about flashing the NoData version, you don't have the issue I was thinking you might.
Why don't you just flash the modem by itself and see if that works. As the previous poster mentioned, it is in the 2nd post reference section.
If it doesn't work, then just flash the kernel by itself. It should work, and then your phone shouldn't complain about the last flash failing and theoretically should boot. Basically you have completed flashing everything but the modem.
If it still doesn't boot, then ODIN flash CWM only and then flash the modem from recovery.
Click to expand...
Click to collapse
so once i flash the modem then how will i know if it worked or not am i jus supposed to try turning my phone on? or do i reflash the auto package after flashing the modem?
TamiaSky said:
so once i flash the modem then how will i know if it worked or not am i jus supposed to try turning my phone on? or do i reflash the auto package after flashing the modem?
Click to expand...
Click to collapse
Just flash the modem. The reboot option should be checked. When it is done flashing the modem, it should reboot. If it hangs like before, boot back into ODIN DL mode and flash just the kernel.
The individual components are 7zip self-extractors, so you double-click on them to get the .tar.md5 file. All the .tar.md5 files can go into the PDA slot (including the modem). No need to use the Phone slot.
sfhub said:
Just flash the modem. The reboot option should be checked. When it is done flashing the modem, it should reboot. If it hangs like before, boot back into ODIN DL mode and flash just the kernel.
The individual components are 7zip self-extractors, so you double-click on them to get the .tar.md5 file. All the .tar.md5 files can go into the PDA slot (including the modem). No need to use the Phone slot.
Click to expand...
Click to collapse
Sfhub,I noticed that a while ago in your directions about having the modem in the PDA slot. Why is it not done in the Phone spot anymore? Just curious is all.
MeWarning said:
Sfhub,I noticed that a while ago in your directions about having the modem in the PDA slot. Why is it not done in the Phone spot anymore? Just curious is all.
Click to expand...
Click to collapse
When you package a modem.bin inside of a .tar.md5 it can flash in both the PDA and Phone slot. It is simpler for the instructions to ask people to always use the PDA slot.
If you flash a modem.bin file itself, then it must go in the Phone slot. If you flash the wrong file in the Phone slot, your phone won't boot. That is why I package things so people always use the PDA slot.
The reason I said "stuck" is because I don't know if it is actually stuck. I am worried because as with my worst fear is bricking my phone. Here is a screenshot of what I am seeing:
(never mind cant post links yet) It looks like this:
(a bunch of stuff)
recover.img
system.img.ext4
then that is where it ends. There is no error message or anything. It would lead me to believe that it is still working. What do I do?
It has not said anything else yet so I dont know what to do. Its been like this for about 10 minutes and not saying anything. I cant imagine it actually taking this long for "system.img.ext4" to get added. Did I do something wrong or what?
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Perseus71 said:
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
Here you go. As far as the version goes I was running the latest version of cyanogenmod. If anyone knows the simplist way to back to stock or even just put another rom on please tell me. I would really just like to gain use of my phone back.
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Perseus71 said:
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Click to expand...
Click to collapse
There is not anything. It just keeps running. I left have left it running since I made this post and still had not moved on. I am a little confused to what you are saying. Could you make it a little more simple or provide links? Thanks.
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Perseus71 said:
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Click to expand...
Click to collapse
Don't know if it helps but I rooted the device around november. I don't remember the version. Due to how long ago it was I remember very little details. I flashed something with odin and thats what I remember. In november I rooted it and put a ROM on it and left it alone till now. So what ever the latest update was in November as what I had. By the way thanks so much for the help. I was really nervous and you are giving me hope. Pardon grammer errors. Typing this on nexus 7 and not use to keyboard
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Perseus71 said:
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Click to expand...
Click to collapse
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
If your talking about the screen I just referred to it says:
odin mode
Product name: SGH-t999
Custom binary download: Yes (1 counts)'
Current binary: Samsung official
Qualcomm secure Secureboot: Enable
Warrenty bit: 0
Bootloader Rp swrev: 1
griffsbrown said:
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
Click to expand...
Click to collapse
My bad, I meant Downloading mode. Its the same thing.
Perseus71 said:
My bad, I meant Downloading mode. Its the same thing.
Click to expand...
Click to collapse
Oh alright I edited my last post with the info so check that
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Perseus71 said:
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Click to expand...
Click to collapse
Alright doing that now. Long download time but I will post back with results later.
griffsbrown said:
Alright doing that now. Long download time but I will post back with results later.
Click to expand...
Click to collapse
Make sure to put the phone in download mode and connecting before launching Odin.
Perseus71 said:
Make sure to put the phone in download mode and connecting before launching Odin.
Click to expand...
Click to collapse
Ok back with results. Download time was a lot shorter then expected. It is the exact same problem as the reason I started this post. It gets to a certain point and just stops loading. That point is "system". The logs I posted already in the thread apply to this as well. When I was first trying it never got further then around 5% but right now with this new method you gave me to try it froze around 40%. Any ideas? Also If its worth mentioning I am using odin3 v1.85
EDIT: For the first time it actually said "fail!". The logs look something like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUEMJC.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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(Also if its worth mentioning I switched to Odin3 V3.09 for the sake of seeing if it made a difference
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Perseus71 said:
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Click to expand...
Click to collapse
Froze at the same place. I can post screenshots now so:
http://puu.sh/7I88Y.png
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Perseus71 said:
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Click to expand...
Click to collapse
Ok done. What next?
Try to Flash a custom Recovery via Odin this time. If that goes successful, please flash any custom Rom of your choice via that Custom Rom. I know you are wanting to go back to stock. I need the phone to boot first so I can check something.
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
UPDATE
Was able to flash stock 5.1.1. Even stock firmware, still rebooted every minute even in safe mode.
Ended up flashing stock 5.1.1 and run the same root and also flash twrp to the device. Nonetheless It still reboots every minute, even in safe mode. Below is the recovery.txt and also attached is a photo of where it's stuck because of rebooting. I swear it's something with the cellular...
recovery.txt
Where it stuck due to rebooting every minute
Update 2
The reboot does not occur in twrp or download mode
Update 3
Following Koops second method
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
Click to expand...
Click to collapse
After the stock flash, booting up hangs on the sprint loading screen, dims, then restarts (only first time star. then ting up after flash) goes through setup, but again reboots every minute. The bars at the top sometime show up and sometime don't show up.
Also every reboot, i turned on voice assistant and "system update" is said every time.
At this point im open to any suggestions. If it's not fixed today ill most likely have to go buy an s5 off of amazon.
UPDATE
Got the phone through setup. Baseband and software version is unknown and notification of "Checking device status" is constant. Even after flashing stock 5.1.1. After about a minute, the device status becomes official.
Might try this:
technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
UPDATE
forum.hovatek.com/thread-116.html
Tried using these methods to fix the baseband issue yet still havent fixed it.
UPDATE Finale
For some reason Koops stock firmware didn't work with my phone. I'e uploaded the firmware that did in case others run into the same issue.
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Thank you everyone who helped!
Pictures of device info added below for specific info
Also if it helps I had flashed twrp before anything. I forget specifically if I did anything in twrp that may have helped or not.
http://imgur.com/vUmjfbX
http://imgur.com/CXql8Li
http://imgur.com/2dUJ1om
x1xmadex1x said:
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
Click to expand...
Click to collapse
Flash back to stock via Odin and install twrp then flash THIS version of SuperSU. Unlike the normal version, this one will not install in the system thus lowering the risk of breaking your device(s)
Flash failed
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Still rebooting
I flashed the newest one, the one linked and yet it still reboots after about a minute...cant get past the "Optimizing app" part now...it reboots before it can finish.
It seems like it reboots when trying to get signal....my bars come up but no reception..then just reboots...
Helpful info?
If it helps, I used this to root it:
autoroot.chainfire.eu
samsung SM-G920P zerofltespr zerofltespr universal7420 exynos5 LMY47X.G920PVPU3BOJ7 5.1.1
Like i said i uninstalled super su, reinstalled, than ran that through odin again and it crashed.
x1xmadex1x said:
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Click to expand...
Click to collapse
What do you have ticked under options?
1619415 said:
What do you have ticked under options?
Click to expand...
Click to collapse
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
x1xmadex1x said:
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
Click to expand...
Click to collapse
Try doing it this time without rooting
1619415 said:
Try doing it this time without rooting
Click to expand...
Click to collapse
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on
koop1955 said:
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Click to expand...
Click to collapse
Correct tar and successful, but doesnt solve my problem...still rebooting a minute to being turned on even in safe mode
Updated main
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
1619415 said:
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
Click to expand...
Click to collapse
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
I am having a very similar issue, can't seem to figure out how to fix it.
x1xmadex1x said:
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
Click to expand...
Click to collapse
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
1619415 said:
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
Click to expand...
Click to collapse
My knox counter is tripped and the galaxy s6 doesnt have a removeable battery...it says it has a charge..i dont think the battery is the issue...
x1xmadex1x said:
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on
Click to expand...
Click to collapse
After it flashes, boot to STOCK recovery and perform a data wipe/factory reset. My guesses are you have stale leftovers from previous ROM/build and the system can't find what it is looking for and terminates.
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
koop1955 said:
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
Click to expand...
Click to collapse
Thank you, will try that in a little.
What about a "PIT" file?
Hey there awesome people!
I have been weeping over my N3N refusing to accept Stock firmware I was downloading.
I followed these steps to flash the stock firmware I would download:
Flashing STOCK firmware (via ODIN):
Put phone off / battery pull
Download ODIN (this one or whichever is newest at the time you read this)
Open up ODIN (as Administrator on Windows PC)
Press and HOLD DOWN the Volume Down [AND] the Home buttons. THEN Press the POWER button. On the screen it will show, press Volume UP to go to DOWNLOAD mode
Plug your phone into the PC and ODIN will show you (in the log) that a device has been Added!
Click the AP button and navigate to your downloaded firmware.
Let ODIN finish the MD5 check and then press START to start flashing
So, at this point, your ODIN will either be showing PASS or FAIL.
If it shows PASS, you're good to go. Skip to Installing a recovery.
If it shows FAIL, read the Log (displayed in the program's left hand side) and observe this:
Code:
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Before showing FAIL!, the last thing it should've listed should be hidden.img
If yours didn't show this, it probably didn't flash the phone upto this point. What we want is for the boot.img, recovery.img, system.img, modem.bin and cache.img to have been flashed to the phone.
When it shows FAIL!, it means that the bootloader it is trying to flash is older than what the phone already has. You will probably find that you are stuck here when you're coming from LL to KK or JB, or from a newer KK to an older one.
Fear not It still worked!
What we do now is just flash a recovery to the phone (we will be replacing the stock recovery that stock ROM comes with), (or root it) and we'll be good to go.
Installing a custom recovery:
Download a recovery (I use TWRP Materialized )
Unzip it and re-open your ODIN (if your ODIN was still open, hit the RESET button)
Do a battery pull on the phone, and boot into DOWNLOAD mode again.
Connect the phone to the PC. ODIN should show in the Log that a device has been added.
Click AP button and navigate to where your Custom recovery is.
After ODIN finishes MD5 check, hit START and let the Custom recovery be flashed.
After this is done, boot into recovery by holding down the Volume Up [AND] Home buttons then pressing Power button.
Go into recovery and wipe Data, Cache and Dalvik (factory reset) and reboot the phone.
BOOM! You'll see the Samsung logo doing its thing and we'll be good to go!
Leave a thanks if this helps :highfive:
Shoutout to @rihawi who pointed this trick out in this post!
boydee said:
What we do now is just flash a recovery to the phone (we will be replacing the stock recovery that stock ROM comes with), (or root it) and we'll be good to go.
Click to expand...
Click to collapse
Okay. I had the Odin Fail because I was trying to downgrade to a firmware with earlier bootloader and as you described I installed TWRP. But now I still get the same error in Odin when trying to install this firmware even with TWRP in place... What should I do?
mcpossity said:
Okay. I had the Odin Fail because I was trying to downgrade to a firmware with earlier bootloader and as you described I installed TWRP. But now I still get the same error in Odin when trying to install this firmware even with TWRP in place... What should I do?
Click to expand...
Click to collapse
List for the steps you're taking to install. I fear that we might have gotten lost somewhere along the way.
The idea is to FIRST install the firmware, THEN install TWRP, then reboot (TWRP should be the last thing you install.)
boydee said:
List for the steps you're taking to install. I fear that we might have gotten lost somewhere along the way.
The idea is to FIRST install the firmware, THEN install TWRP, then reboot (TWRP should be the last thing you install.)
Click to expand...
Click to collapse
Your post title says "for downgrade". So I have a firmware with, let's say, bootloader binary version 3 installed. I want to downgrade to an older firmware which has bootloader binary version 2. I can't just flash the older firmware, because Odin fails. So I was following your guide to install TWRP to somehow downgrade through that, but it doesn't work.
When it shows FAIL!, it means that the bootloader it is trying to flash is older than what the phone already has. You will probably find that you are stuck here when you're coming from LL to KK or JB, or from a newer KK to an older one.
Click to expand...
Click to collapse
This is where I'm at right now.
mcpossity said:
Your post title says "for downgrade". So I have a firmware with, let's say, bootloader binary version 3 installed. I want to downgrade to an older firmware which has bootloader binary version 2. I can't just flash the older firmware, because Odin fails. So I was following your guide to install TWRP to somehow downgrade through that, but it doesn't work.
This is where I'm at right now.
Click to expand...
Click to collapse
That's okay! it's perfectly fine for it to FAIL!
Flash it again and copy/paste the ODIN Log here for me to see and advise on what you should do next.
Cheers! :highfive:
odin fail
xda-developers LOGIN REGISTER search plus
Join the Experts
Post Preview:
i used odin3 v3.12.7
this is what appears on the log tab.
Added
Odin engine v(ID:3.1207)
File analysis
setupconnection
initialization
get pit for mapping
firmware update start
NAND write start
Singledownload
sboot.bin
cm.bin
Fail
Complete(write) operation failed
all threats completed. (success 0/ failed 1)
how can i fix this. please help..
please send me message @
[email protected]
facebook- fed refalbor
please. i badly need your help. i am using samsung j7 2016 (j710gn)
Fai always on installing at same way you said
Dear xdas .. I trying the same to download the firmware for the Gt-N5100 at the same steps you explain before but always failed , note that I try that to try resolve the wifi problem after last update, so cannot install firmware and that is the result of ODIN, please let me know if any result here:<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.1207)..
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
not helpful. you only flashed the recovery and not the whole system file. flashing the system file will took you a minute while the error on takes less than a second.
After i do the odin recovery it showed PASS . but after that phone tried to restart and the samsung logo came on thrice flashing and gone OFF . Now the phone is in dead mode. Please help me to help to resolve this. My phone is samsung note 2(GT7105)
hi, if i flash firmware via odin, programs and files on internal memory will erase or not? thanks
Hi, i was flashing an older version of android to my Samsung Galaxy S7 Edge, using odin, i entered all the files in Odin and it was working fine up until it was almost finished and i accidentally bumped my phone and Odin displayed a FAIL immediately... lol wow i am such a idiot. I disconnected, reconnected, tried to re-run Odin again, it told me it failed right away so theres no fixing it with Odin anymore. I tried restarting phone, i somehow got it to restart but it doesnt show samsung logo or anyting, i just see a Recovery Booting... in the top left corner of screen in tiny letters... i can get it into download mode but nothing else. I dont know what to do, somebody help me out here. How do i fix this??
Cyclone53 said:
Hi, i was flashing an older version of android to my Samsung Galaxy S7 Edge, using odin, i entered all the files in Odin and it was working fine up until it was almost finished and i accidentally bumped my phone and Odin displayed a FAIL immediately... lol wow i am such a idiot. I disconnected, reconnected, tried to re-run Odin again, it told me it failed right away so theres no fixing it with Odin anymore. I tried restarting phone, i somehow got it to restart but it doesnt show samsung logo or anyting, i just see a Recovery Booting... in the top left corner of screen in tiny letters... i can get it into download mode but nothing else. I dont know what to do, somebody help me out here. How do i fix this??
Click to expand...
Click to collapse
Hello, I got a very similar issue on my phone. I spent more than a week trying to find a solution and everytime I got a FAIL. This morning I got a PASS! here is what I did:
_ Use odin v3.12.7 with administrator priviledges.
_ In options I checked: Autoreboot, Re-Partition, F.Reset Time and Phone Bootloader Update.
_ I loaded BL, AP, CP and CSC Files (it was CSC and not Home_CSC).
_ I started the phone in transfert mode (home, volume down and start button). And then press volume up to activate the transfer mode.
_ I connected the phone to the computer and the Phone appeared in ID:COM.
_ I pressed "Start".
And this time the transfer did not fail. It took several minutes and then the phone rebooted and I got the welcome screen as good as new.
I don't know if it worked because I selected "Re-partition" and "phone bootloader update" this time or if it's because I downloaded the lastest stock rom from samsung I was able to find at present (maybe both). But I am so happy now.
Good luck to you and BE CAREFUL because Re-Partition and updating the bootloader could definitely brick your phone...
Secure boot fail
Im getting a secure boot fail after update. Ive tr8ed just AP and odin says boot fail. Phone says secure boot fail. And ive tried all ap,bl,csc,cp and i get from odin re partition fail and again on phone secure boot fail. Is there a way to maybe bypass secure boot. Oem is not optional and it will fail trying the combo rom for factory binary as well. Before the update i was ablento flash everything basically regardless of csc and verison.
Hello,
I downgrade and i tried many stock ROMs (marshmallow and lollipop) and checke all youtube videos, nothing is working. I always i got error. So i want to ask if with your instructions you managed to install stock marshmallow ROM from stock nougat on A510F just because you additionally chose "Re-Partition" and "Phone Bootloader Update" ?
Thanks.
zool_80 said:
Hello, I got a very similar issue on my phone. I spent more than a week trying to find a solution and everytime I got a FAIL. This morning I got a PASS! here is what I did:
_ Use odin v3.12.7 with administrator priviledges.
_ In options I checked: Autoreboot, Re-Partition, F.Reset Time and Phone Bootloader Update.
_ I loaded BL, AP, CP and CSC Files (it was CSC and not Home_CSC).
_ I started the phone in transfert mode (home, volume down and start button). And then press volume up to activate the transfer mode.
_ I connected the phone to the computer and the Phone appeared in ID:COM.
_ I pressed "Start".
And this time the transfer did not fail. It took several minutes and then the phone rebooted and I got the welcome screen as good as new.
I don't know if it worked because I selected "Re-partition" and "phone bootloader update" this time or if it's because I downloaded the lastest stock rom from samsung I was able to find at present (maybe both). But I am so happy now.
Good luck to you and BE CAREFUL because Re-Partition and updating the bootloader could definitely brick your phone...
Click to expand...
Click to collapse
boydee said:
That's okay! it's perfectly fine for it to FAIL!
Flash it again and copy/paste the ODIN Log here for me to see and advise on what you should do next.
Cheers! :highfive:
Click to expand...
Click to collapse
hello guys, sorry, i'm new here.. i've just faced the problem with my phone.. idk why my phone was stuck, i've tried to remove the battery and tried to restart, it seemed the same, just stuck on samsung logo. i tried to enter to recovery mode, it failed. i've tried to install the original stockrom and it's failed..
here the problem and condition:
1. stuck on samsung logo
2. can't enter recovery mode
3. only download mode can be use
i've tried the stockrom but in odin said...:
<ID:0/021> 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/021> Odin engine v(ID:3.1101)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> SingleDownload.
<ID:0/021> spl.img
<ID:0/021> NAND Write Start!!
<ID:0/021> sboot.bin
<ID:0/021> sboot2.bin
<ID:0/021> param.lfs
<ID:0/021> boot.img
<ID:0/021> recovery.img
<ID:0/021> system.img
<ID:0/021> cache.img
<ID:0/021> hidden.img
<ID:0/021> SPRDCP.img
<ID:0/021> FAIL!
<ID:0/021>
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what should I do?
need help, please.. thanks
a few days ago my Samsung bootloop, I found a solution. Download the latest firmware for your Samsung, which is suitable for your country. enter download mode, just flash AP, later he will install and reboot. when rebooted later if it isn't mistaken it appears no modem / radio (I forgot). enter download mode again, flash CP only. then device will reboot and enter recovery default. in recovery select wipe factory. and my samsung will reset again. I hope this helps you.
hi my problem is this
<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/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 952 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> spl.img
<ID:0/008> sboot.bin
<ID:0/008> sboot2.bin
<ID:0/008> param.lfs
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i cant flash stock firmware for my samsung galaxy core prime, smg360hu but it stucks at system.img then fails always. help me please
Hi,
Just decided to use Odin v3.14 to update my Australian spare Samsung SM-G900iwith Indian G900IDDS1CSA1 firmware as it was a later build, seemed to proceed OK but finished with <OSM> All threads completed. (succeed 1 / failed 1.
It had previously been updated to G900IDVU1CQJ2_G900ITEL1CQJ2_G900IDVU1CQJ2_HOME.tar.md5 which was working perfectly.
<ID:0/003> Added!!
<ID:1/004> 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/003> Odin engine v(ID:3.1401)..
<ID:1/004> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:1/004> File analysis..
<ID:0/003> Total Binary size: 2496 M
<ID:1/004> Total Binary size: 2496 M
<ID:1/004> SetupConnection..
<ID:0/003> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> NAND Write Start!!
<ID:1/004> SingleDownload.
<ID:1/004> aboot.mbn
<ID:1/004> sbl1.mbn
<ID:1/004> rpm.mbn
<ID:1/004> tz.mbn
<ID:1/004> sdi.mbn
<ID:1/004> NON-HLOS.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img.ext4
<ID:1/004> cache.img.ext4
<ID:1/004> hidden.img.ext4
<ID:1/004> modem.bin
<ID:0/003> Complete(Write) operation failed.
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)
Click to expand...
Click to collapse
Can I retain the updated build and just use ODIN to replace what failed?
Any suggestions GREATLY APPRECIATED.
Cheerz
Hello, there is 'firmware upgrade encountered an issue' thing on my samsung. I plugged to pc and pc sees the device but odin stuck at initialzation or fail. Any suggestion?
G Morn Folks I m stuck in the same situation thought different phone mode. this is M205F. Odine FAILS @ Recovery.img
Background
Latest Stock ROM of Samsung Maisk Rooted nd TWRPed. Wanted to downgrade to ANdroid 9 from 10 after realizing severe restrictions of the latter.
Odin 14x ( wtith Chinese verbiage @ start up screen ) used and used 2 Versions of stock ROMs.
Tried AP solo & AP + HOME_CSC COmbos
Both FAIL and leave me with ocean blue screen message "an error has occured while updating the deivce software..Use he emergency recovery function in the smart switch sw." and smart switch isnt recognizing my mob either.
Where do I go from here ?