Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.
What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I used ODIN to flash (What I'm very confident is) 4.3 Stock in the same manner I flashed the custom ROM.
I feel like that isn't specific enough for you though. I used Odin3 v3.09 first and then after several failures switched to Odin3 v1.85 as demonstrated in a few tutorials I've seen.
Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Let me attempt this thread's instructions before I make more of a fool of myself. Thank you for the assistance so far. I really appreciate it.
No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Seedeh,
The errors still continued as usual even with the explicit following of the linked directions. It appears that during the process:
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
that the "NAND Write Start" step isn't really even trying to write before it fails.
Kies "Emergency Firmware Recovery" also yields no success due to "Firmware emergency recovery stopped due to GALAXY S4(SGH-I337) error. If the problem persists, please contact the Samsung service centre.", which does persist each time I attempt to do so.
If you have any more suggestions, I'd be more than happy to attempt them.
Thank you.
AmpGuitarChase said:
Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.
Click to expand...
Click to collapse
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.
John The Rhino said:
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.
Click to expand...
Click to collapse
John The Rhino,
Thank you for you assistance. I will surely give credit where credit is due
I've attempted the XDA Full Odin Tar MK2 link's instructions three times on two separate computers (one w8 and one w7) to no avail. I've triple-checked the instructions, but my Odin always fails when attempting to Complete(Write).
NAND Write Start!
sbl2.mbn
sbl3.mbn
rpm.mbn
aboot.mbn
Complete(Write) Operation Failed
All threads completed. (succeed 0 / failed 1)
Odin settings: Auto Reboot checked, F. Reset Time checked, PDA = I337MK2_Full_Odin_Tar.tar file, nothing else is checked.
Device: Dev mode activated, USB debugging active, this is all verified after a recovery-initiated factory reset, device is in download mode.
Computer(s): Samsung Android ADB Interface drivers are installed, Odin does show a yellow bar upon device connection. MicroUSB cable is the default one that came with the device, all USB ports have been tried with the same results.
I tried to be as thorough as possible with my setup. I'll see if my process is correct now just in case that will help.
[Fixing Device to Working Status w/o wifi/data permissions] Flashed AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 via Odin
Automatic Reboot via Odin
[Device is back to working status w/o data/wifi permissions (No reset has been done)]
Power off
Reboot in Recovery Mode (Volume up + Home + Power)
Wipe data/factory reset command
Wipe cache (just in case)
Reboot
[Phone is now factory reset 4.3 MK2 (WiFi/Data permissions denied still]
Enable developer options
Enable USB debugging and Screen Stay Awake during charging
Power off
Boot into download mode (Volume down + Home + Power)
Open Odin3 v1.85
Bar in Odin for COM Port is yellow
Auto reboot & F. Reset Time are both checked
Load I337MK2_Combined_Odin_Tar\I337MK2_Full_Odin_Tar.tar.md5 in PDA slot
Screenshot of Odin before "START" http://i.imgur.com/oXufVNQ.png
Odin START
Wait for Odin to check .md5 compatibility
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Back to where these points began
Apologies for the length, but again I wanted to be as thorough as possible. My WiFi still won't turn on due to permissions issues and Data is on, but no 3g/4g/LTE comes through.
Surely I'm just missing an essential step or two.
Can you offer any further advice on this matter?
Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5
The bootloader on MK2 and later is encrypted and without the key it will always fail. ODIN sees the ABOOT is locked and cannot flash the complete image. AT&T and Verizon have chosen this method to keep you off their cheaper competitors. I had to take my I337 to Best Buy Samsung experience to have it re flashed so that it would boot after a refused OTA from MDL and now it is a paperweight.
jd1639 said:
Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5
Click to expand...
Click to collapse
I don't think Odin is the issue as it flashes what I like to call "The cure-firmware" .md5 AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5) file just fine every time with no issues with Odin. Only when I try to flash that file, it works. I wish there was a way to tell what exactly is going wrong with the other files. I also can't seem to find where I located this file, but whatever it's doing works on my S4. I'd like to find either a 4.2.2 or 4.4.2 version of this stock OS that would work.
I'm beginning to wonder if it'd be more worthwhile to reroot, reset the flag binary counter, reset, and drive an hour and a half away to the closest AT&T store and see if they can fix my device. Does this sound like it may be my best course of action?
Again, thanks for all the help guys. I means a lot.
There is no way to downgrade to 4.2.2 from MK2. The bootloader is locked. Read the guide for MK2 it will help you.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Check your APN settings re enter according to correct settings posted on XDA.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Loki does not work with MF3 and up
Congrats!
Sent from my SAMSUNG-SGH-I337 using Tapatalk
AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!
John The Rhino said:
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!
Click to expand...
Click to collapse
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase
AmpGuitarChase said:
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase
Click to expand...
Click to collapse
You're welcome. I'm glad it all worked out for you. As they say in the construction business, measure twice, cut once. Well same here, except I'd recommend as do others to read thrice (3x) FLASH once. Then you'll rarely have issues. Enjoy.
i337 same issue as original post
i have done the same research as posted in this link and read exhaustively every means google XDA and all the other pages dealing with rooting and flashing my AT&T s4 i337. I have ended up in the same boat as this guy with:
Baseband version - I337UCUFNB1
Build Number - JSS15J.I337UCUEMK2
i have attempted Kingo Loki, Motochopper, Odin(4 or 5 versions) adb flash in Linux(2 builds) and Winblows 7. My original desire was to have this build
https://www.youtube.com/watch?v=mJLKX_QWSpc
which got my hopes up immensely, as having wasted days upon days several times over the course of the last 9 months rooting this i337. The guy in the vid says he was able to get UT up and running following guidance from XDA. I want to be able to flash a twrp-like dual boot recovery to my device maintaining Andy functionality using UT as a daily driver.
I have read, as reading saves phones, everything I can glean from the aforementioned posts and forms, researched this thing to death and neded up with a phone with the knox-? security message listed in the original post. I have no Idea where to go from here, but know you guys do, as like a myriad of others, I worship this site like a god.
Please help an old retired disabled veteran of most of the sandy wars in the past 25 years. All I have now are my devices which bring me some comfort to my days.
I really need your help, as I've tried seemingly all and have a semi-dead i337.
buxtor, aka, Chief
Related
Hiya, I recently tried to follow k0nane's howto on getting Froyo DK17 flashed onto my phone, but as expected, things did not go well. I managed to root my phone using the one click method, installed ClockworkMod, backed up my ROM, contacts, SMS messages, et cetera. Unfortunately, that's about the only thing that went right in my case.
Before I start, I will admit that this is the first time I'm attempting this, though I did receive much help from a friend who has already successfully flashed her phone, so if in doubt, please assume I don't know what I'm talking about!
I installed Android SDK, did the whole adb thing, and made sure my Samsung drivers were up to date (64 bit system). I then proceeded to download the file in that thread that included Odin, the new PIT, and the new modem. I then downloaded the next file that included the ROM and kernel and put the ROM in my SDcard.
Then I went about starting Odin up and loaded the files into their respective slots. The new PIT in the PIT slot, and, get this, the new modem in the PDA slot. I learned much later that the new modem should have been in the Phone slot, but let us continue. I then put my phone in download mode and connected it to the computer via USB, and Odin quickly recognized the device with a COM# in a yellow box, so I reckoned things were going pretty dandy, but alas, the following message dashed my hopes a mere three seconds after I hit START.
<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> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I hopped onto the respective IRC chat for the Samsung Epic 4G, and the kind folks there pointed out that the modem should have gone into the Phone slot, so I tried again the proper way and I still got the same failure.
My phone is now rendered inoperable because a recovery boot via presents me with a cute drawing of a phone that is connected to a computer, but a warning triangle separates the two. Same thing when I try to normally boot. Fortunately I can still access download mode, so I don't believe my phone is bricked. Interestingly enough, despite these blocks, I somehow did manage to get into the Clockworkmod recovery screen by doing some weird series of steps where I have the USB plugged in, the battery pulled, the USB pulled, then the battery and USB reconnected and at some moment there I would slide out the keyboard, then, without even touching a button, it would get into the recovery screen.
Using this weird workaround, I wiped everything and restored my backed up ROM and all that snaz, but upon rebooting the system I was again greeted warmly by the cute image of the dysfunctional marriage between my phone and computer.
So upon further advice from the folks at the IRC chat, I tried to flash my phone back to stock specifications using the DI18 and corresponding PIT file in the same method. But alas, I get the exact same result and well, at this time I'm getting a wee bit concerned. But by now, the folly of trying to flash my phone in the early hours of the morning and during Thanksgiving, no less, begins to rear its ugly head and I end up sleeping.
Cue sunrise and I'm up trying to make best of my situation, and I post a few times on k0nane's thread describing my problems, and a guy there says I should try the same process on another computer, so I do, and that fail with the same result. Then I hop onto IRC again, and the nice guys there say I should try Heimdall, so I do (after reading its readme), and lo and behold Heimdall does not seem to be able to recognize my device.
I guess my question is where one might find a problem in my procedures. I swear I did everything right and to the letter, but perhaps a new pair of eyes could be prove to be more insightful and help point out my mistakes. Granted the feeling of ruining a 500 dollar phone isn't exactly something I'd brag about to my friends, but I am rather enjoying life without a phone.
For now, anyways, haha.
------------------------------
tl;dr Odin recognizes my phone, but fails within 3 seconds with the following message
<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> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help?
It sounds like you have done a lot of research and educated yourself prior to attempting your first flash. Major props to you for that as most people don't.
My $0.02 about your issues...I had something similar happen once when I forgot to uncheck "F. Reset Time" before starting the flash. If that's not the problem then I'd try a different cable. Next step would be to try a different version of Odin, there are plenty floating around these forums.
Good luck!
hongseong said:
Hiya, I recently tried to follow k0nane's howto on getting Froyo DK17 flashed onto my phone, but as expected, things did not go well. I managed to root my phone using the one click method, installed ClockworkMod, backed up my ROM, contacts, SMS messages, et cetera. Unfortunately, that's about the only thing that went right in my case.
Before I start, I will admit that this is the first time I'm attempting this, though I did receive much help from a friend who has already successfully flashed her phone, so if in doubt, please assume I don't know what I'm talking about!
I installed Android SDK, did the whole adb thing, and made sure my Samsung drivers were up to date (64 bit system). I then proceeded to download the file in that thread that included Odin, the new PIT, and the new modem. I then downloaded the next file that included the ROM and kernel and put the ROM in my SDcard.
Then I went about starting Odin up and loaded the files into their respective slots. The new PIT in the PIT slot, and, get this, the new modem in the PDA slot. I learned much later that the new modem should have been in the Phone slot, but let us continue. I then put my phone in download mode and connected it to the computer via USB, and Odin quickly recognized the device with a COM# in a yellow box, so I reckoned things were going pretty dandy, but alas, the following message dashed my hopes a mere three seconds after I hit START.
<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> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I hopped onto the respective IRC chat for the Samsung Epic 4G, and the kind folks there pointed out that the modem should have gone into the Phone slot, so I tried again the proper way and I still got the same failure.
My phone is now rendered inoperable because a recovery boot via presents me with a cute drawing of a phone that is connected to a computer, but a warning triangle separates the two. Same thing when I try to normally boot. Fortunately I can still access download mode, so I don't believe my phone is bricked. Interestingly enough, despite these blocks, I somehow did manage to get into the Clockworkmod recovery screen by doing some weird series of steps where I have the USB plugged in, the battery pulled, the USB pulled, then the battery and USB reconnected and at some moment there I would slide out the keyboard, then, without even touching a button, it would get into the recovery screen.
Using this weird workaround, I wiped everything and restored my backed up ROM and all that snaz, but upon rebooting the system I was again greeted warmly by the cute image of the dysfunctional marriage between my phone and computer.
So upon further advice from the folks at the IRC chat, I tried to flash my phone back to stock specifications using the DI18 and corresponding PIT file in the same method. But alas, I get the exact same result and well, at this time I'm getting a wee bit concerned. But by now, the folly of trying to flash my phone in the early hours of the morning and during Thanksgiving, no less, begins to rear its ugly head and I end up sleeping.
Cue sunrise and I'm up trying to make best of my situation, and I post a few times on k0nane's thread describing my problems, and a guy there says I should try the same process on another computer, so I do, and that fail with the same result. Then I hop onto IRC again, and the nice guys there say I should try Heimdall, so I do (after reading its readme), and lo and behold Heimdall does not seem to be able to recognize my device.
I guess my question is where one might find a problem in my procedures. I swear I did everything right and to the letter, but perhaps a new pair of eyes could be prove to be more insightful and help point out my mistakes. Granted the feeling of ruining a 500 dollar phone isn't exactly something I'd brag about to my friends, but I am rather enjoying life without a phone.
For now, anyways, haha.
------------------------------
tl;dr Odin recognizes my phone, but fails within 3 seconds with the following message
<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> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help?
Click to expand...
Click to collapse
put it in the phone slot not the pda slot to bypass the pda bug
Oooh, thanks for the replies! I don't think I can get a micro USB cable right at this moment, but...
I did try the Phone method, and at first it seemed to actually start flashing, but it got stuck at factoryfs.rfs for quite a while, so I restarted the process and now it will just fail like it did before in about three seconds. Not sure what's gong on here, but it was nice to see it exhibiting some semblance of working up until it began hanging at factoryfs.rfs!
More helpful tips would be greatly appreciated!
Are you exiting Odin, disconnecting the phone, rebooting the phone into DL mode BEFORE trying to flash again? Odin will fail forever if you simply try to restart the process without the steps above.
I sure am!
I also think it has to do something with the param.lfs file since Odin always seems to fail once it encounters it (and it does so early on!).
Thanks again ^^
Ok have you tried to redownload the tar file it could be corrupted.You should be putting the whole tar file unopened in PDA leaving all the other slots empty and using the correct pit file that comes with odin.It is ok to leave the reset time option set it will not hurt anything.
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
hongseong said:
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
Click to expand...
Click to collapse
Forget about DK17 for a minute and try flashing DI18 with the new odin and pit, if that doesn't work download art3mis's DK05 extended that has the old odin and use that. Pit in pit, and the tar in pda.
Sent from my SPH-D700 using XDA App
hongseong said:
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
Click to expand...
Click to collapse
Was Re-Partition checked during any of your attempts?
For the longest time no, but then I talked to noobnl and he asked me to try to put it into both re-partition mode and phone bootloader update mode. It just hung at "DO NOT TURN OF TARGET" and that was it. He warned me that it could brick it, but I guess I got lucky and it didn't.
So yes, I did check re-partition mode, but not until I tried all aforementioned tips in every combination possible.
bubby323 said:
Forget about DK17 for a minute and try flashing DI18 with the new odin and pit, if that doesn't work download art3mis's DK05 extended that has the old odin and use that. Pit in pit, and the tar in pda.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Oh, I was trying to flash DI18 the entire time (I gave up trying to flash DK17 last night, haha ^^ But I'll try your DK05 extended tip right now! Sorry I missed this ><
Okay, so using artemis' DK05 extended package and older Odin, I get a different readout
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
But it just stalls at boot.bin forever, and I've tried this several times, so...
I think the moral of the story here is that I'm unlucky
But yeah, that's what's happened so far. Thanks for the continued help, everyone!
Read thru this thread and just thought I'd ask --- Did you pull your MicroSD card from the phone and then make an attempt to flash? While I wouldnt think it would matter, I saw on another forum that its always a good idea to pull the MicroSD before Odin --- and I've always done that. Not sure it matters, but it couldnt hurt to try. Also, you being able to get into that Download mode means all isnt lost~ Don't give up~
Do you have another PC available to attempt the flashing on? I use a Windows 7 x64 system, but I always do my flashing on a XP x86 system. Its surprising how finicky Odin can be, so it couldnt hurt to try another PC....
Or not, just a couple suggestions.
Best of luck
marsknight said:
Read thru this thread and just thought I'd ask --- Did you pull your MicroSD card from the phone and then make an attempt to flash? While I wouldnt think it would matter, I saw on another forum that its always a good idea to pull the MicroSD before Odin --- and I've always done that. Not sure it matters, but it couldnt hurt to try. Also, you being able to get into that Download mode means all isnt lost~ Don't give up~
Do you have another PC available to attempt the flashing on? I use a Windows 7 x64 system, but I always do my flashing on a XP x86 system. Its surprising how finicky Odin can be, so it couldnt hurt to try another PC....
Or not, just a couple suggestions.
Best of luck
Click to expand...
Click to collapse
I tried to do it on another laptop in the house, but I ran into the same errors, but I'll try the microSD card trick soon
Thanks for the words of encouragement! I'm continuing to work on this problem, though I am a bit anxious to see how I can live without a cell phone...
im stuck with the same problem... and the messed up thing is i used odin before on this phone with win7 64bit... now i wish i never try updating to the new modem...
spent sooo much time on this and nothing im just gonna put it away b4 i smash it with a hammer... back to win mo...
Eeek, well, I think I'm going to scale back my attempts at fixing this for the moment. I'd be flat out lying if I said this wasn't a little bit frustrating, so I'm going to just relax before I make this fiasco ruin my Thanksgiving break for me. I'm most likely going to just purchase a cheap used flip phone and see through the rest of my contract with Sprint after changing my plan accordingly (no need for a data plan with a cheapo flip phone, and CERTAINLY no need for the 10USD WiMax surcharge, ^^; ).
That isn't to say that I'm not very thankful for all y'alls help, because I am, and this forum is awesome (along with the IRC chat!). Plus, not everything is *that* bleak; I mean, now I have a device that can charge batteries AND a 16GB microSD card freed up for other uses. So, thank you for all the help, and I hope y'all have a nice day!
Odin always seems to work for me windows 7 64bit and I have the 32bit drivers for the phone maybe try to deletethe old ones and install the 32bit drivers
Sent from my SPH-D700 using XDA App
Couple of questions and suggestions. Have you tried flashing just the modem in the proper slot(phone) with the proper pit file. I WOULD SUGGEST YOU TRY IT WITH THE OLDER ODIN(not 1.6) and the older pit. Then I would suggest you try to flash the full tar for DI18 with the older odin and no pit file. I have flashed my phone dozens of times with no pit as long as its the full tar. I could be wrong but I believe the pit is for partial system flashing. The only option I have checked on the left hand side of odin is reboot fwiw. Lastly, others have hinted at it too, odin is very finicky, try and try again. Always close down odin and restart it between attempts, and rebooting the computer seems to help others, and pull the phone battery and re-enter download mode each time too. Good luck, don't give up, if you can get into download mode all is not lost.
sent from an Epic4g through the cosmos
So my Girlfriend wanted a free hotspot on her phone, so i rooted her phone without issue and looked up how to get a free hotspot, i followed this video to the T (https://www.youtube.com/watch?v=AYTis-i7HA4)
Unfortunately the phone stopped working, and double unfortunately i was being stupid as hell and didnt bother to backup the rom before installation. so i figured to fix the problem i would just flash a custom ROM on their, one that included hotspot. i THOUGHT her phone was an i9505 model s4. i ended up flashing an i9505 rom to her phone and it SEMI work (she cn sms and call but she doesnt get data and a lot of the apps dont work correctly) i tried flashing the stock rom back onto her phone using odin but it immediately fails everytime, i also tried to flash it using CWM but that also immediately fails. i really need to get her phone working and i will be checking this thread every 5 minutes or so, so if there is any more information you need from me, please ask and i will respond ASAP, i really need the phone fixed by tonight, also, if someone is willing to skype me and walk me through everything so i cna get it done ASAP, if you succesfully fix my phone ill shoot you 25 bucks (yo uwould send me an invoice from payapl or something and id pay the invoice with a credit card)
Thanks in advance guys! I definitely learned my lesson on backing things up! lol
also, this is what odin said
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNG2_L720SPTFNG2_L720VPUFNG2_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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
doubke edit: when in download mode and i have already tried to falsh using odin my phone says:
odin mode
product name sph l720t
(usual binary and system status knox stuff)
write protection enabled
emmc burst mode enabled
start [224,1440]
secure check fail: aboot
Well, first you need to make sure what phone you are using. You said you thought you had a i9505 but you tried to flash the tar file for the Sprint GS4 (SPH-L720) which is the L720VPUFNG2 (NG2) file you refer to in the Odin readout above. Finally, in your edit, in Odin Mode you are showing the product name SPH-L720T. The 720T is the triband version of the Sprint Galaxy S4. I believe the tar file for the 720T is the NG5. I am not sure what trying to Odin a NG2 tar will do to a 720T phone but it would seem you may. On the Q&A page about two threads below your thread are threads for ROMs tested on the 720T as well as an everything you need to know about the 720T thread. (http://forum.xda-developers.com/showthread.php?t=2621862). I would look at those two threads to see if you can find a ROM or tar that works on your version. I am almost positive you will find both. To be safe, if you phone is a 720T, I would probably odin back to stock with the proper tar, regroup and start over with new root and the correct ROM. (read read read read and read again before you start flashing) If it is the 9505, there is another forum for that phone. If it is actually the L720, then you have bigger problems. Start by deleting and reinstalling drivers, download the tar file again, make sure you are using a good USB cord and try again. I am still relatively new but if I can help further, let me know.
dyandell said:
Well, first you need to make sure what phone you are using. You said you thought you had a i9505 but you tried to flash the tar file for the Sprint GS4 (SPH-L720) which is the L720VPUFNG2 (NG2) file you refer to in the Odin readout above. Finally, in your edit, in Odin Mode you are showing the product name SPH-L720T. The 720T is the triband version of the Sprint Galaxy S4. I believe the tar file for the 720T is the NG5. I am not sure what trying to Odin a NG2 tar will do to a 720T phone but it would seem you may. On the Q&A page about two threads below your thread are threads for ROMs tested on the 720T as well as an everything you need to know about the 720T thread. (http://forum.xda-developers.com/showthread.php?t=2621862). I would look at those two threads to see if you can find a ROM or tar that works on your version. I am almost positive you will find both. To be safe, if you phone is a 720T, I would probably odin back to stock with the proper tar, regroup and start over with new root and the correct ROM. (read read read read and read again before you start flashing) If it is the 9505, there is another forum for that phone. If it is actually the L720, then you have bigger problems. Start by deleting and reinstalling drivers, download the tar file again, make sure you are using a good USB cord and try again. I am still relatively new but if I can help further, let me know.
Click to expand...
Click to collapse
hey man, i really appreciate the quick reply!!!! im pretty sure my phone is actually the 720T so im going to download the stock rom for that and try and flash it using odin. thanks man!
http://www.sammobile.com/firmwares/download/35324/L720TVPUBNG5_L720TSPTBNG5_XAS.zip/
Here is a link to the stock firmware for the L720T.
---------- Post added at 10:07 PM ---------- Previous post was at 10:03 PM ----------
I have been married longer than some of the people on here have been alive so I can imagine the a$$ chewing you are currently receiving.
Us guys have to watch each other's backs! Good luck and let me know if I can help some more.
dyandell said:
http://www.sammobile.com/firmwares/download/35324/L720TVPUBNG5_L720TSPTBNG5_XAS.zip/
Here is a link to the stock firmware for the L720T.
---------- Post added at 10:07 PM ---------- Previous post was at 10:03 PM ----------
I have been married longer than some of the people on here have been alive so I can imagine the a$$ chewing you are currently receiving.
Us guys have to watch each other's backs! Good luck and let me know if I can help some more.
Click to expand...
Click to collapse
"HOW AM I GOING TO CHECK MY (insert girly website here) WITHOUT MY PHONE!!!!"
lol thanks man im currently downloading it but the internet at her house is incredibly slow hahaha. so i just gotta do a lot of waiting.
so i flashed the stock rom but now i keep getting popups that services have stopped working (google search, settings, google partner setup, google.process.gapps etc.)
This is really bummin me out man. im probably going to have to smash her phone and go through insurance and pay the 200 dollars so she can get a replacement. is there nothing else i can try?
and now it wont even boot into recovery.
this is seriously pissing me off why doesnt **** ever just work right? ughhhhh
You're getting the error messages after using Odin?
I would try flashing thru Odin again.
Sent from my SPH-L720 using XDA Free mobile app
Fixed it, just forgot to clear cache and factory reset after the install, you guys are the bomb! Thanks to all those who helped me! Her phone is now working
Raidenbeats said:
Fixed it, just forgot to clear cache and factory reset after the install, you guys are the bomb! Thanks to all those who helped me! Her phone is now working
Click to expand...
Click to collapse
Glad to hear you got her phone fixed. Doesn't mean you are out of the doghouse but at least you will not be in it as long.
well I was going to flash a custom ROM for her after we got the stock one in, but all the ROMS for her model are lame as hell and are ugly as heck. and they are all google based.
Raidenbeats said:
well I was going to flash a custom ROM for her after we got the stock one in, but all the ROMS for her model are lame as hell and are ugly as heck. and they are all google based.
Click to expand...
Click to collapse
If all you originally wanted was free hotspot, take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=2621862
Use CF-AutoRoot to root, and then use either Galaxy Tools app or telephony.db edit to get free hotspot. This is a tried and true hotspot solution for the 720T. There are links/instructions for both in OP of the above thread. I can personally vouch for these. I used them to root and get free hotspot and all has been golden. No issues whatsoever.
Compared to what you've already been through with this phone, these mods should be a piece of cake.
Pro Tip: Once you've added native hotspot, add a toggle to the notification bar. There are links in the above thread to do it manually. But the easiest way to do it is with the Galaxy Tools app. There's an option in it that says "Add all Notification Toggles" that will add every imaginable toggle to the notification bar - including of course the hotspot toggle.
Hi guys. The title basically says it all. Since there is no Towelroot for the SM-G870A (typed SM-G870W in title by accident), I have to use ODIN. I follow the steps to the word and I have even tried changing PC ports and switching computers. No matter what when I click start it works for about 5 seconds until it says "Failed" in a red box. Thankfully my phone doesn't get bricked, but I still want to root my phone. Also, I'm positive I use the correct CF-AutoRoot for my phone's model. Thanks in advance! Also, I will provide any extra information if it is needed.
This is the error I get:
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
im having the same problem hopefuly there will be a fix.
I wonder why nobody is answering our questions. .. it's the 4th
thread I read with great questiona no help...
I have the same problem.
i can only boot to the android system recovery screen and to download mode.
It killed my OS and wont let me install anything.
Is there any way to get the factory updated FW to load and where can we find it, I've been looking frantically for 2 days?
drivers? version?
If your phone is already updated to lollipop you will be unable to root, no matter how badly you want to.
If you're still on KK, you can flash an older kernel, root, then upgrade to lollipop using a prerooted image.
oriel10 said:
drivers? version?
Click to expand...
Click to collapse
it was whatever the latest update was.
LRX21T.G870AUCU2BOF3
I followed every instruction in the threads exactly as stated in these forums.
Didn't get very far.
I do not care to root the phone at this point, I'd simply like to get it to work again.
If anyone could direct me to where I might find the latest stock firmware, I would very much appreciate it.
---------- Post added at 02:07 AM ---------- Previous post was at 02:02 AM ----------
also, i hunted for a program to back up my phone but all that I found only work for rooted phones...
I have a back up phone so I said screw it, these guys knows whats up, look at all these threads for rooting the g870a.
Surely they would be taking down threads that do not work anymore.
LMAO, I hated the phone to begin with and they only made it worse with each update and I was ready to put it through a wall.
Thanks in advance!
I have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping.. - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU
You are on the latest OTA of BOG5. The bootloader is completely locked down and you cannot root, downgrade, or flash anything. You are stuck with the phone as is. You will have to find the BOG5 full stock firmware .tar file and flash that through ODIN to get your phone back.
Damn!!!!
do you know any links from where i can download the BOG5 firmware from?
I am having the exact same issue. Any help is appreciated!
I am also stuck with the same issue on my S5. I attempted to flash the NCG Kernel from Android 5.0 using the file referenced in here: androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/ (sorry I can't post links yet). Now my phone can't leave recovery mode. Did you guys figure out where to get the BOG firmware or how to fix this issue?
You need to reinstall the BOG5 firmware on the S5 again. You can download it via sammobile.com You can pay £5.40 approx if your from UK and download the firmware quicker within an hour otherwise be prepared to wait 11 hours minimum for download to complete.
So I managed to get mine back working by using the VZW-G900VVRU2BOG5-20150813111348.zip firmware downloaded from Sammobile.com and flashing using Odin3.
Used the first firmware on Sammobile firmware page for model SM-G900V
Unzipped the file and flashed the .md5
Back up and running.
Hope this helps someone.
wgafsck said:
I am having the exact same issue. Any help is appreciated!
Click to expand...
Click to collapse
jac1985 said:
I am also stuck with the same issue on my S5. I attempted to flash the NCG Kernel from Android 5.0 using the file referenced in here: androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/ (sorry I can't post links yet). Now my phone can't leave recovery mode. Did you guys figure out where to get the BOG firmware or how to fix this issue?
Click to expand...
Click to collapse
smn216 said:
You need to reinstall the BOG5 firmware on the S5 again. You can download it via sammobile.com You can pay £5.40 approx if your from UK and download the firmware quicker within an hour otherwise be prepared to wait 11 hours minimum for download to complete.
Click to expand...
Click to collapse
Seriously, do none of you have even the basic, simple ability to look through these forums at all? The answer to your question is right here in the Verizon Galaxy S5 General forum:
http://forum.xda-developers.com/verizon-galaxy-s5/general
You simply scroll down to the fourth thread and see that it is this one:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
The title of the thread is literally "G900VVRU2BOG5_Factory_Odin_Tar_Image. Good Lord!
landshark68 said:
Seriously, do none of you have even the basic, simple ability to look through these forums at all? The answer to your question is right here in the Verizon Galaxy S5 General forum:
http://forum.xda-developers.com/verizon-galaxy-s5/general
You simply scroll down to the fourth thread and see that it is this one:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
The title of the thread is literally "G900VVRU2BOG5_Factory_Odin_Tar_Image. Good Lord!
Click to expand...
Click to collapse
Hey man, I am new here. I was freaking out the other night because everything I was trying was failing. I understand with a little more patience and effort I could have found this. Then again with a little more research before attempting to root I probably would have avoided the whole issue. I messed up, my bad.
Seriously, do none of you have even the basic, simple ability to look through these forums at all?
Click to expand...
Click to collapse
Same here, in fact it was my first time posting and I was also kind of lost. In any case, thanks for the lesson and the links.
wgafsck said:
Hey man, I am new here. I was freaking out the other night because everything I was trying was failing. I understand with a little more patience and effort I could have found this. Then again with a little more research before attempting to root I probably would have avoided the whole issue. I messed up, my bad.
Click to expand...
Click to collapse
Understood. It just gets very old and frustrating answering the same questions over and over again, and questions for which the answer is already readily available. Glad you got it straightened out, and that you realized more research before embarking on your adventure would have helped. When it comes to messing around with an expensive piece of hardware like these smart phones, it's best to think of the carpentry line - measure twice, cut once. Read, read, read, and make sure you know what you are doing before you do it when it comes to rooting and modding your phone.
Thanks a million! I thought my phone is toasted.
All,
I've spent the better part of the last two days trying with zero success to downgrade my Verizon Galaxy S4 SCH-I545 from 5.0.1 to 4.4.2. I've read dozens of pages on various forums, both on general instructions for the procedure as well as pages relating directly to the fault I'm seeing. In short, I get the Complete(Write) operation failed error in Odin. The reason I'm trying to do this is a general disappointment in Lollipop, it has slowed the phone down (I need to kill off all apps at least once a day just to keep performance up) and I've enjoyed none of the "benefits" of Lollipop on the phone. It's been so bad I've deliberately ignored all requests my Tab 4 makes to upgrade to Lollipop.
I've tried the firmware reflash using Odin 3.04 as well as 1.85. I've tried both versions on two different computers, one running Windows 7 Home, the other running XP. I've run them standard, and on Win7 as Administrator. Fresh reboots. The Win7 has Kies (not running) and the WinXP computer has never had Kies, just downloaded the current Samsung USB drivers. I've tried running two different firmwares downloaded from Sammobile, on each machine, with every combination I can think of. I'm using the factory USB cable plugged directly into the motherboard on each machine. I've varied the moment I plug the phone into the cable based on various recommendations, waiting until Odin is already running, or getting the phone in download mode first then plugging in, etc. I've also tried re-running the update again immediately on failure, and again after rebooting the phone back into Download mode, trying multiple times in a row without closing down Odin, and then alternately restarting everything after each failure. Basically I've tried pretty much everything I've read, and it feels like I'm following the rules of an old gypsy woman, if I update the phone at midnight while swinging a dead rooster over my head, standing on my left foot only, all will go ok. Only nothing goes ok.
This is the complete error I get in Odin 3.04:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The first four lines happen almost immediately. Then it seems to wait or hang for about 45 seconds (meanwhile one CPU maxes out), afterwards the rest of the lines pretty much spit out instantly. On the phone the display changes slightly, one little tick mark appears on the progress bar, then nothing else. The phone appears to be locked and needs a very long hold of the power button to shut off. These symptoms appear identical regardless of which computer I use, or which version of Odin I use, which makes me suspect the phone is the culprit rather than the software/hardware of either computer. I figure if I had, for example, a corrupted firmware file it would fail somewhere down the line in the install, or even after it's dumped the file to the phone.
One thing that worried me (and I NEVER found any mention of this in any directions) is the amount of available space on the phone. With the bloatware on the phone (7.07GB of "miscellaneous files"?!?) I only have 2.76GB free on the internal memory, and the firmware file is 2.4GB. I'm assuming that it all needs to copy to internal memory first. After my first failed attempts I checked space available and I had less than 2.4GB free. After clearing cache and a few apps I got it up to 2.76GB.
USB debugging is on, battery level is full or high on the phone, reactivation lock is off, the phone connects to either computer just fine and interfaces with Windows Explorer, I can see and access files on the phone via My Computer without any error.
I saw one page describing using Heimdall as a wholly different idea, it seemed MUCH more complex and my gut reaction is it looks like it would be easier to brick the phone. Is there some manual way I can dump the firmware to the phone and get it to read the file such that it doesn't require a computer?
Anything else to suggest? In general I still like the phone and don't have a great deal of interest in upgrading, but it's getting frustrating enough that I'm considering junking the phone.
Thanks in advance,
Ryan
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
GDReaper said:
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
Click to expand...
Click to collapse
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Diddler77 said:
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Click to expand...
Click to collapse
Got pissed and disconnected it after about 45 minutes. Switched to my desktop/Win7 machine. With the bigger monitor I could see that the whole time it was sitting on "Leave CS" it wasn't doing a thing, it now gave me the option to hit the 'Start' button at the bottom of the screen. I LOVE applications that don't let you resize to fit odd sized monitors (like my old Netbook).
So, I hit 'Start', and it pretty much immediately fails. Some of the error messages are differerent though, here's the whole thing:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I find most interesting is the 5th and 4th line from the bottom, Write start followed by FAIL! (Auth). I interpret it as Odin failed to get authorization from the phone to perform the write function. Any other ideas? Going to try Odin 3.10.6 next.
Diddler77 said:
Going to try Odin 3.10.6 next.
Click to expand...
Click to collapse
Yeah, same problems on both computers, both new versions of Odin. Did notice something this time around on the phone's screen that I hadn't noticed before, though it seems to happen in all versions of Odin. Two lines appear on the phone when I hit 'Start' in Odin:
START [224,1440]
SW. REV CHECK FAIL : FUSED : 8, BINARY : 6
The numbers after FUSED and BINARY are very difficult to read. Above is my best guess. Any of them may be a 0 or an 8.
Thanks!
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
GDReaper said:
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
Click to expand...
Click to collapse
That I have not tried. From what I gather I need a PIT file specific to the model. Any idea where I can get it? In terms of the end result, what's the difference between using the PIT and re-partitioning compared to what I've been trying? Like, why do both options exist?
Thanks!
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
GDReaper said:
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
Click to expand...
Click to collapse
Dont the firmwares originally come with pit files ?
Deathvirus said:
Dont the firmwares originally come with pit files ?
Click to expand...
Click to collapse
From what little I gather from the simple Odin instructions page, some firmwares are packaged with additional files. The two versions I've downloaded from sammobile for my device type only contained a single tar.md5 file when unzipped.
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader. The bootloader being locked is primarily designed to prevent root, but it also has the effect of preventing downgrades. If it didn't have that capability, users could simply flash a bootloader that could be compromised, obtain root, and remove the bloatware.
You posted your question in the International S4 forum, and international devices don't lock their bootloaders, which is why no one has really picked up on this until now. The only reason I picked up on the possibility of it being your bootloader is because I own an international device yet live in the US, so I'm acutely aware of the locked bootloaders foisted upon us by AT&T and Verizon.
It is my understanding that Odin fails after trying to flash aboot.mbn because the ROM being flashed has a bootloader that is older than the bootloader currently installed on the phone.
Some models of the s4, such as the Canadian version (sgh-i337m) can be flashed from stock LP to stock KK using Odin without issue.
You're right about the age of the bootloader being a reason why downgrading fails. You're also right that most devices can downgrade without issue. However, the OP's device is not one of them. He happens to have one of the models with a locked bootloader, and to the best of my recollection, the locked bootloader means you cannot downgrade, period.
Strephon Alkhalikoi said:
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader.
Click to expand...
Click to collapse
If this is true, I'm really ticked off. What a waste of time. You'd think that somewhere, on ANY of the forums and websites someone would have mentioned that my device is crippled in this manner. Every single site makes Odin sound like the silver bullet.
Why is there even firmware available for Verizon GS4's then?
Understand I'm not ungrateful for the advice, I do appreciate it. Just venting.
-sigh-
100% true, and it's not limited to Verizon either. AT&T also locks the bootloader. As to mentioning it, it likely is mentioned in the AT&T and Verizon S4 General forums, but you won't find that information here. As I mentioned, this is the International S4 forum, and we don't have locked bootloaders to deal with.
I know it sucks, but this is what we deal with in the US. That's why for my next device I went with a Nexus.
I don't have a PIT file for OF4 firmware on the SM-S975L (Straight Talk variant) so the downgrade failed as for OP, I'm stuck in download mode with a yellow triangle.
Yeah, Verizon released this phone to Straight Talk evidently. I'm locked tight and basically hard bricked. Wicked pissed, too. Since Kies says phone model not supported. CANNOT restore.
Nexus it probably is. This phone was a waste of money.
Or at least...that was until I found a hack that let me install the old Jellybean kernel! http://forum.xda-developers.com/gal...ariant-of4-t3279890/post64511525#post64511525
Only problem is, sure, you can get your kitkat kernel back, but I wasn't successful probably because NB1 firmware was Verizon firmware at the time of my flash so my CSC didn't work, but since they're both JellyBean I got root. But as long as they're the same carrier my hack should work. Link me your firmware, I can let you try. It'll trip the hell out of KNOX though. I used Odin 3.07. It requires some by-hand hex editing. When you gain root you can disable Knox to flash other things with SuperSU.
@LupineDream: Of course you weren't successful in changing kernels. The SM-S975L is not a CDMA (i.e. Verizon) phone, but uses T-Mobile towers. The SCH-R970G is the other Straight Talk S4 and it used Sprint as a carrier. Verizon does not allow MVNOs access to their LTE network, which is how you can tell that you're NOT on Verizon.
The bootloader on Straight Talk S4 devices is not locked down like the OP's bootloader. Otherwise it would not be possible to install custom ROMs to the device. I have a distinct feeling that your hack will not work. Not because it's incorrect as you clearly had success, but because of the locked bootloader on the device, which is designed to prevent the very thing you successfully accomplished on your Straight Talk device.
To restore your phone to working condition, download the S975L firmware from sammobile and flash it through the BL slot in Odin. Then sell it and get a Nexus.
Hey, if I found a workaround for obtaining root on the ATT variant, users of that phone now have an fstab and an (almost complete) list of partitions and mount points for a device tree. So I hope that information at least made their lives better. In knowing they can indeed flash a kernel with said workaround. The device list, fstab, and mount points are all in my root guide now. Since after reflashing the boot image by itself the device boots again and has maintained root status, though with broken WiFi which can be fixed with a custom kernel. Oh well, at least users of my phone get a custom ROM., at least if you've got the ATT variant. All the info is in my thread for ATT variants. I' don't have my stock kernel, however. But it isn't an issue as for what I've provided, I think its enough to get a custom one for the ATT variants. Still going to sell and get my Nexus. But left it with a bang I suppose. I'll hack a locked bootloader until I'm blue in the face if it means I got root. You are indeed right, though. It isn't for ME to keep around, but please note that before I was even able to flash a kernel, I had to hack it. It was displaying secure boot status and would not allow flashing of anything. I was told they where all locked. I was never able to root OF4 before because of "locked conditions" where NB1 refused to flash before my hack.
I'm going shopping soon. Maybe I'll get the Verizon variant on the side to see if I can force my way in through another one of these types of loopholes. After all, my device would not flash a kernel before I did what I did to it...I was able to disable knox and allow kernel flashing by doing so. Through SuperSU. That bit was set before I did what I did to the device. All it takes is flashing of the NB1 kernel to Verizon through tricking knox it's official firmware and enough know-how to get the system to boot well enough to be able to inject root.
My device still won't flash non-official firmware or recovery. Because of a verification check in the kernel. I tried. Sig fai on kernel. But, now that Knox can be disabled, all it takes is an if/of dd flash of modified aboot in adb and then anything is possible at that point. I looked into loki_tool for always passing signature check passed to hardware knox. And clearing out EERAM before knox gets a chance to react. Loki'fied aboots satisfy knox pretty well I'd say.
The ROM displayed there iis for the Verizon variant by the way. I found Verizon-related apks in system.img.ext4. Even without the modem, it still won't flash. Have a download, rename it, extract the tar and hex edit look through the file. Yep, that's a verizon variant ROM.
One question, however, is does hardware knox do a checksum on aboot? That would pretty much make this argument a moot point.
Ask Chainfire. He needed to know about how Knox functioned so he could get SuperSU to disable it.