Develop Bugs

[Q] Help please odin keeps failing

for some reason while trying to return to stock, odin keeps failing while trying to flash sboot.bin. any info on a work around would be helpful.

yavimaya401 said:
for some reason while trying to return to stock, odin keeps failing while trying to flash sboot.bin. any info on a work around would be helpful.
Click to expand...
Click to collapse
Write a radio from before ma7 so like a ljc or whatever radio and then try again ....
Sent from my SPH-L900 using Xparent BlueTapatalk 2

yavimaya401 said:
for some reason while trying to return to stock, odin keeps failing while trying to flash sboot.bin. any info on a work around would be helpful.
Click to expand...
Click to collapse
I'm having the exact same problem, I tried everything I could i'm still failing at the sboot.bin
Is this what you're screen looks like?
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> param.bin
<ID:0/011> recovery.img
<ID:0/011> sboot.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Removed!!

Download an official release from samfirmware.con
Sent from my SPH-L900 using xda app-developers app

Sboot.bin won't downgrade the normal way from ma7 back to lk8/ljc etc. Garwynn has a work around for it somewhere in the dev section. I believe you need to use billards all in one revert to ljc with flash counter reset to downgrade the bootloader. This is why I didn't flash the bootloader with ma7 I just flashed the rom and modem. That way I wouldn't need to hassle around with downgrading it if I wanted to one click back to ljc instead of ma7
☆SoA: Son's of Android™☆
I like to break stuff!

Thanks for help and suggestions.
All systems are go on my phone now, I downloaded the stock file from Samsungupdates.com, then installed it thru Odin and it worked like a charm.
I did have to install it twice and it passed both time, It took to long the first time to reboot, so I deleted and did a factory reset then reinstalled the TAR.
I'm good to go

Going back to stock....I'm getting a fail

I reinstalled the drivers, reinstalled odin, re-downloaded the LJ1 MD5, used different cables, but everytime I getting this in the Odin screen
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> param.bin
<ID:0/011> recovery.img
<ID:0/011> sboot.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Removed!!
Anyone have any other method I can try to get back to complete stock. Any ideas would be appreciated.

Go to Android development and look for billiard412's thread he had a back to stock setup that works very well.

http://forum.xda-developers.com/showthread.php?t=2086769
THAT
Sent from my SPH-L900 using xda app-developers app

Tw1sted247 said:
Go to Android development and look for billiard412's thread he had a back to stock setup that works very well.
Click to expand...
Click to collapse
00mred00 said:
http://forum.xda-developers.com/showthread.php?t=2086769
THAT
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks for help and suggestions.
All systems are go on my phone now, I downloaded the stock file from Samsungupdates.com, then installed it thru Odin and it worked like a charm.

Where did you find the stock file from samsungupdates.com? I can't find it anyway. I've been stuck on this for nearly a day now. I've learned quite a bit of new stuff... more than I care to know lol. I know there is a solution to this, I just need some guidance please.

QuantumPSI said:
Where did you find the stock file from samsungupdates.com? I can't find it anyway. I've been stuck on this for nearly a day now. I've learned quite a bit of new stuff... more than I care to know lol. I know there is a solution to this, I just need some guidance please.
Click to expand...
Click to collapse
here the link to the page
http:// samsung-updates.com/device/?id=SPH-L900 (remove the spaces)
download the middle link, it should take about 2 hours, run this file thru Odin as if it were any other TAR
After you download, this is what the file should be: KIES_HOME_L900VPALJ1_L900SPTALJ1_265523_REV04_user_low_ship.tar.md5

lexvdub1 said:
here the link to the page
download the middle link, it should take about 2 hours, run this file thru Odin as if it were any other TAR
After you download, this is what the file should be: KIES_HOME_L900VPALJ1_L900SPTALJ1_265523_REV04_user_low_ship.tar.md5
Click to expand...
Click to collapse
I REALLY NEED THIS FILE CAN YOU SEND IT TO ME PLZ! THE SITE IS DOWN..I used cdma ws 3.8.0 wont read my note 2 sph-l900 even connected to the correct com and in diag mode with pda and then dm+modem+adb...never had this problem before, I even flashed lj1 and ljc stock roms and still say's FAILED..PHONE DOES NOT ANSWER! I've flashed many phones and usually all I'd have to do is change the usb cable or the com port but even then it's not working.

Doesn't get any easier than this right here:
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using xda app-developers app

[Q] Can I do a factory Reset with Odin on MK2?

Is it possible to do a factory reset with Odin? I flashed this rom http://forum.xda-developers.com/showthread.php?t=2268880 on to my phone but it's on M919UVUEMK2. Currently, my phone is soft bricked and I can only go into download mode and I can't install the clockwork recovery mod. My phone will boot to the Galaxy S4 logo and turnoff.

re: odin flash
Trong357 said:
Is it possible to do a factory reset with Odin? I flashed this rom http://forum.xda-developers.com/showthread.php?t=2268880 on to my phone but it's on M919UVUEMK2. Currently, my phone is soft bricked and I can only go into download mode and I can't install the clockwork recovery mod. My phone will boot to the Galaxy S4 logo and turnoff.
Click to expand...
Click to collapse
About the only thing you can do is start all over again and put your phone into download
mode and flash the official stock samsung 4.2.2 MDL odin flash firmware.
After that you can root and odin flash twrp or cwm custom recovery.
Here is a link for the official samsung m919 4.2.2 stock mdl firmware:
http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip
After downloading unzip and you will find the .TAR file which you
need to use with Odin in it's PDA slot.
Good luck!

How can I see my modem on my phone. I just want to be sure what the modem I have now.
Sent from my SGH-M919 using xda premium

xperia_88 said:
How can I see my modem on my phone. I just want to be sure what the modem I have now.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
In Settings/More/About device/Baseband
☞ Sent from here☜???

Thanks but it didn't work. Odin keeps say it failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Trong357 said:
Thanks but it didn't work. Odin keeps say it failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You're using a stock FW to go from 4.3 to 4.2.2 which is not possible. You have to use a 4.3 stock FW to go back to stock. Once you're on the 4.3 boot loader, you're stuck with 4.3. You can NOT downgrade to a different bootloader.
---------- Post added at 01:09 AM ---------- Previous post was at 01:05 AM ----------
Download the 4.3 FW from here, should be the first link.

Thanks but:"Hotfile has been shudown. A download link to Terafile will be presented as soon as the firmware is uploaded. We are busy uploading all files to the new host. We apologize for the inconvenience."

re: official stock m919 firmware
Trong357 said:
Thanks but:"Hotfile has been shudown. A download link to Terafile will be presented as soon as the firmware is uploaded. We are busy uploading all files to the new host. We apologize for the inconvenience."
Click to expand...
Click to collapse
Here is the identical firmware as found on SamMobile.com
This is the M919UVUEMK2_M919TMBEMK2_TMB.zip
This contains the TAR file for the official Samsung M919 MK2 4.3 stock firmware.
Here is the direct download link: https://copy.com/hzfaqBpWhinn/M919UVUEMK2_M919TMBEMK2_TMB.zip?download=1
This is a much faster mirror than the Hotfile host which SamMobile uses.
Good luck!

Thanks and thank you and to everyone else who helped. The rom installed successfully but when I tried to turn the phone on, it gets to the T-Mobile splash screen and doesn't go on from there. I left it there for nearly 30 min but it didn't load and the phone was very hot. I re-Odin the rom and tried wiping cache partition and dalvik in recovery but the phone never goes past the T-Mobile screen.

Misterjunky, sir. Thank you!. Your link helped me to unbrick. I've a working ROM now. My root is gone, wifi slightly flaky - but hey can make calls etc.!
I am on 4.3 + MK2 now. My warranty is void etc..but really thank u very much!.

Flashing stock rom with odin, "stuck" at system

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.

[Q] Phone stuck in recovery mode

Hello,
I have been trying to root my galaxy s3 sgh t999v by the root66 method. I have done this method before and then returned to stock, and now choosing to go back to a custom rom. However, this time odin has been failing and not allowing me to root my phone, I am using the right files as well as the stock cable that came with the s3. I have twrp installed by going through odin and installing that. But now it is stuck on either a boot loop or if I try installing the root66 or stock rom it will take me to the stuck in "please connect to kies " recovery mode screen..
Not sure what to do, any help is appreciated thank you

What does it say in odins message box after flashing?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
What does it say in odins message box after flashing?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T999VVLALH2_T999VYVLALH2_CL1030062_REV04_user_low_ship.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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Heres the exact message

You can't downgrade, that's why you're getting that message. So either flash the same firmware version you had last, or a newer one

Yeah, that's 4.0.4 firmware. Try a more recent build. You can get it from my firmware thread too btw. Should give you a faster download.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Okay will try the same firmware, thanks for the quick replies

I have a bit of a problem, I was on 4.4.2 but I don't see any root66 methods for 4.4.2, will I have to find another method?

Oh ok. Didn't realize you were on the latest, sorry. Flash the official firmware and then root with Towelroot. I have a thread for this in the General section.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Thanks a lot! It worked Really appreciate the help

No problem! Glad to hear it!
Sent from my SAMSUNG-SGH-I747 using Tapatalk