Related
i just picked up my Note 3 the other day from verizon (SM-N900V) and i attempted to root it using Root_de_la_vega. It was my fault for not doing more research, but i thought since i wasn't going to do anything fancy other than remove all the bloat ware that it should be simple enough. Now when i use Odin (3.09) it keeps failing and now my phone is bricked and now it says i need to use the software repair assistant.I have tried downloading Kies 3 as one site suggested, but for some reason it does not recognize the device What is the quickest way to repair this? I don't care if it goes back to default. I really need to fix it ASAP! Please help!
Below is the script that shows up in odin when i try to root it:
ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> cache.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
droidstyle said:
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
Click to expand...
Click to collapse
ok, im new to this, and its my fault for jumping in the deep end without doing my proper due diligence. I dont have a good clue what you mean my MJE odin file? Are you refering to the AP file that i drop into odin?
droidstyle said:
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
Click to expand...
Click to collapse
i also tried using different versions of odin. Can you link to a good root file for SM-N900V?
When @droidstyle mentioned MJE, he is talking about the most current customer release ".tar.md5" file for use with Odin. (There have been at least three public releases so far - MI9, MJ7, and now MJE)
I *think* links for the files you want are here (section 1 of this post)
http://forum.xda-developers.com/showthread.php?t=2483380
I haven't been down the road you are travelling, so I honestly don't know if you are soft bricked (recoverable) or in worse shape than that.
If you succeed in getting things working again, let us know what steps you took.
.
theicro was
bftb0 said:
When @droidstyle mentioned MJE, he is talking about the most current customer release ".tar.md5" file for use with Odin. (There have been at least three public releases so far - MI9, MJ7, and now MJE)
I *think* links for the files you want are here (section 1 of this post)
http://forum.xda-developers.com/showthread.php?t=2483380
I haven't been down the road you are travelling, so I honestly don't know if you are soft bricked (recoverable) or in worse shape than that.
If you succeed in getting things working again, let us know what steps you took.
.
Click to expand...
Click to collapse
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Just to Add Here Are 2 Other Good Places To Look
http://forum.xda-developers.com/showthread.php?t=2576104
How To Flash in ODIN
http://forum.xda-developers.com/showthread.php?t=2543386
Root Recovery Roms
---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------
deathrage said:
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Click to expand...
Click to collapse
Download root checker from play store
thanks all for the help, and thanks for not chastising me much for my ignorance. Ill def make sure to do much much much more research before i try to do something like this again lol.
Your all back up and running with root I take it then ?
Root checker says that my device was not correctly rooted.....ill look into i more, not sure why it did not take.....it seems like verizon makes it more difficult than any other carrier to root their devices
deathrage said:
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Click to expand...
Click to collapse
The Odin factory image stuff returns everything back to 100% factory, so you shouldn't be rooted if that's all you did.
And since you didn't mention anything else, I suppose that's exactly what we should presume.
Normally when you use that Odin procedure, you are returning to square one - you need to root. Probably with kingo.
As btfb0 said.... root with KingoApp (dot) com.
drag&fly said:
As btfb0 said.... root with KingoApp (dot) com.
Click to expand...
Click to collapse
As you seem to have figured out, the more research you do, the more likely you are to succeed at stuff like this. At least you were able to recover it.
That being said, KingoApp is definitely the best/easiest way to root this phone.
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
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.
Sorry for the long post.
Got this sprint S7 as a 2nd hand unlocked phone a while back and worked quite nicely for almost a year. Now very often when I reboot it gets stuck on the LTE boot logo. While it is at it, it will burn through the battery in like 30m-1h, the phone gets very hot. This has already happened a handful of times so I try to never reboot unless very necessary. This doesn't happen on every single reboot though.
Right now it's showing the same issue. Before I've notice it'll do this for a few days and the like magic will start working again. It sucks because right now my phone is as good as dead.
The phone is not rooted and it's running stock ROM, with latest firmware and all updates(I checked for updates a couple days ago and there was none), but I don't know which exact version is at.
I've already tried rebooting into recovery and powering off and restarting from there. But no luck.
I had a strong suspicion this was due to switching sim cards (I moved a few months ago) and sometimes a "UICC unlock needed" (or sth like that) message has been shown but the phone continues to work. Today a friend mentioned it could be the battery. He said if the battery is damaged it could be causing problems on boot but I have no clue if that's true and/or how to check for it.
I'd thank anyone who could tell me how to troubleshoot this problem and find the real cause. I'm comfortable following some technical instruction to be able to grab logs from linux command line if someone taught me how.
Thanks in advance!
joel_gil said:
Sorry for the long post.
Got this sprint S7 as a 2nd hand unlocked phone a while back and worked quite nicely for almost a year. Now very often when I reboot it gets stuck on the LTE boot logo. While it is at it, it will burn through the battery in like 30m-1h, the phone gets very hot. This has already happened a handful of times so I try to never reboot unless very necessary. This doesn't happen on every single reboot though.
Right now it's showing the same issue. Before I've notice it'll do this for a few days and the like magic will start working again. It sucks because right now my phone is as good as dead.
The phone is not rooted and it's running stock ROM, with latest firmware and all updates(I checked for updates a couple days ago and there was none), but I don't know which exact version is at.
I've already tried rebooting into recovery and powering off and restarting from there. But no luck.
I had a strong suspicion this was due to switching sim cards (I moved a few months ago) and sometimes a "UICC unlock needed" (or sth like that) message has been shown but the phone continues to work. Today a friend mentioned it could be the battery. He said if the battery is damaged it could be causing problems on boot but I have no clue if that's true and/or how to check for it.
I'd thank anyone who could tell me how to troubleshoot this problem and find the real cause. I'm comfortable following some technical instruction to be able to grab logs from linux command line if someone taught me how.
Thanks in advance!
Click to expand...
Click to collapse
Have you tried reflashing the stock firmware via odin? If you could tell me which network you're using it on, I could point you to the firmware you would need. Here's a basic overview for the phones and their corresponding firmwares:
SM-G93OP- Sprint
SM-G930T- T-Mobile
SM-G930A- AT&T
SM-G930V- Verizon
SM-G930U- Universal, but you need the correct version of it for your carrier.
TheF|ipSide said:
Have you tried reflashing the stock firmware via odin? If you could tell me which network you're using it on, I could point you to the firmware you would need. Here's a basic overview for the phones and their corresponding firmwares:
SM-G93OP- Sprint
SM-G930T- T-Mobile
SM-G930A- AT&T
SM-G930V- Verizon
SM-G930U- Universal, but you need the correct version of it for your carrier.
Click to expand...
Click to collapse
Hi TheFlipSide,
I have a sprint version so I have SM-G93OP- Sprint
It is possible something might have gone wrong at some point in time but I have done factory resets before, I'm skeptical that the firmware itself could be the issue but I'm happy to give it a try.
Could you point me to the files needed to be sure I'm on the most accurate firemware (CP, BOOT, etc type of files).
Also, any issues with my phone being up to date with all the updates?
Personally I'd be happier to be able to flash sth like LineageOS but AFAIU there's not much support for this phone.
joel_gil said:
Hi TheFlipSide,
I have a sprint version so I have SM-G93OP- Sprint
It is possible something might have gone wrong at some point in time but I have done factory resets before, I'm skeptical that the firmware itself could be the issue but I'm happy to give it a try.
Could you point me to the files needed to be sure I'm on the most accurate firemware (CP, BOOT, etc type of files).
Also, any issues with my phone being up to date with all the updates?
Personally I'd be happier to be able to flash sth like LineageOS but AFAIU there's not much support for this phone.
Click to expand...
Click to collapse
You can't flash LineageOS on this phone because the bootloader is locked. You can get ODIN to flash the firmware with from here:
https://drive.google.com/file/d/0ByoIewGd_qk2MEZMb0l3Qlo4ek0/view?usp=drivesdk
Unzip it and click on the ODIN3 v3.12.7 file, you don't need to install anything it opens as an app.
Grab the firmware from here: http://updato.com/firmware-archive-select-model?record=48A2011F925C11E7963AFA163EE8F90B
Unzip it and select the files through odin:
CP in CP.
CSC in CSC.
AP in AP.
BL in BL.
Then go into options and select auto reboot and repartition, and keep everything else unchecked.
Hit start and wait for the firmware to flash.
Go into stock recovery, and wipe cache and factory reset.
Hit thanks on the posts if I helped you.
TheFlipSide thanks so much for helping me out.
Quick questions. The firmware link you sent is for SM-G930U. But AFAIK my phone is SM-G930P (Sprint model), since it even shows the Sprint animation on boot. Let me know if that was a small mistake or if theres a good reason to flash the Universal version on a sprint phone.
Also, assuming it was a small mistake I'm looking at that firmware page. Looks like the latest version for the SM-G930P comes in 3 flavors: VMU, XAS and SPR.
Do you know what those are and which one should i get?
Thanks again in advance!
joel_gil said:
TheFlipSide thanks so much for helping me out.
Quick questions. The firmware link you sent is for SM-G930U. But AFAIK my phone is SM-G930P (Sprint model), since it even shows the Sprint animation on boot. Let me know if that was a small mistake or if theres a good reason to flash the Universal version on a sprint phone.
Also, assuming it was a small mistake I'm looking at that firmware page. Looks like the latest version for the SM-G930P comes in 3 flavors: VMU, XAS and SPR.
Do you know what those are and which one should i get?
Thanks again in advance!
Click to expand...
Click to collapse
Use the SPR variant of the SM G930U firmware, as it comes without the Sprint bloat. If you still want to use the SM-G930P firmware, get it here: http://updato.com/firmware-archive-select-model?record=080CDA3799FF11E7963AFA163EE8F90B
As I said previously, you don't need to thank someone in a response post, just click the thanks button on a post which helped you.
bootlooped
TheF|ipSide said:
Use the SPR variant of the SM G930U firmware, as it comes without the Sprint bloat. If you still want to use the SM-G930P firmware, get it here: http://updato.com/firmware-archive-select-model?record=080CDA3799FF11E7963AFA163EE8F90B
As I said previously, you don't need to thank someone in a response post, just click the thanks button on a post which helped you.
Click to expand...
Click to collapse
Hi, sorry for the delay, life got in the way. So I downloaded the universal version SM-G930U (SPR) and followed the instructions and Odin failed.
Code:
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> FAIL! (Auth)
I tried to run it again after unplugging the cable and plugging it back in and it failed again:
Code:
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> FAIL! (Auth)
Now I tried to restart and it's gotten itself on a boot loop =(
It's stuck in the blue "installing system update" page only for a second, then some white text on black screen shows up, and then it goes back to the blue page, and repeats. Basically is trying to boot into recovery forever.
Trying to reboot manually to get into download mode, or anything else also doesn't work.
Halp!
joel_gil said:
Hi, sorry for the delay, life got in the way. So I downloaded the universal version SM-G930U (SPR) and followed the instructions and Odin failed.
Code:
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> FAIL! (Auth)
I tried to run it again after unplugging the cable and plugging it back in and it failed again:
Code:
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> FAIL! (Auth)
Now I tried to restart and it's gotten itself on a boot loop =(
It's stuck in the blue "installing system update" page only for a second, then some white text on black screen shows up, and then it goes back to the blue page, and repeats. Basically is trying to boot into recovery forever.
Trying to reboot manually to get into download mode, or anything else also doesn't work.
Halp!
Click to expand...
Click to collapse
You can't flash the U firmware if you are on the latest sprint firmware. Download the latest firmware from here
And follow the same directions for placing files into ODIN. You are getting the PIT error because of bootloader updates.
lvpre said:
You can't flash the U firmware if you are on the latest sprint firmware. Download the latest firmware from here
And follow the same directions for placing files into ODIN. You are getting the PIT error because of bootloader updates.
Click to expand...
Click to collapse
Hi Ivpre, thanks a lot for jumping in. So I managed to get my phone in download mode again. Also I google one more error that was showing up in the phone screen "Fuse 5 > aboot 4" (or sth like that, I can't remember exactly) and the internetz said that it was indeed due to having a version missmatch, the new one should be higher.
So I downloaded the latest G930P from sammobile site (G930PVPU5BQJ3) and got it to work again. I also found another thread to said the only thing to do is wait until a new G930U comes out.
What I don't fully get is that now that I've installed "latest" firmware. As soon as I configured the phone it said a new update is available. If I update it now, and a new version of G930U also comes out in a bit, will that mean I'll remain one version ahead? Should I not apply any updates until a new version of G930U is out? or should I try downgrading the current G930P ?
Thanks!
joel_gil said:
Hi Ivpre, thanks a lot for jumping in. So I managed to get my phone in download mode again. Also I google one more error that was showing up in the phone screen "Fuse 5 > aboot 4" (or sth like that, I can't remember exactly) and the internetz said that it was indeed due to having a version missmatch, the new one should be higher.
So I downloaded the latest G930P from sammobile site (G930PVPU5BQJ3) and got it to work again. I also found another thread to said the only thing to do is wait until a new G930U comes out.
What I don't fully get is that now that I've installed "latest" firmware. As soon as I configured the phone it said a new update is available. If I update it now, and a new version of G930U also comes out in a bit, will that mean I'll remain one version ahead? Should I not apply any updates until a new version of G930U is out? or should I try downgrading the current G930P ?
Thanks!
Click to expand...
Click to collapse
Yeah, apparently they just released a small update (QK3 maybe?) that patched an exploit. That update was just released the other day. You can take it or leave it, it shouldn't prevent you from installing the U firmware when it is updated.
If you really want to install the U firmware and can't wait, you can research PIT files, but it can lead to fully breaking the device if you mess up...personally, I would just wait. It was an old method that would work, but I'm not sure if it works on the new bootloader updates.
Hi Guys,
I'm on the same boat as joel_gil,
I've got S7 (originally purchased on sprint USA network) and now I've unlocked it using idoneapps without root.
I'm on G930PVPU5BQJ3 firmware at the moment and I'd like to flash G930U firmware which is network unlocked and not bloatware free.
I've downloaded the firmware below multiple times from sammobile.com and tried flashing using latest Odin 3.12.10 and everytime I am getting error message.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/SPR/download/G930UUES4BQL1/201542/
I have also tried XAS version as well but same result
SW check failed aboot fused 5 > binary 4 message.
I've got FRP and OEM unchecked and still its giving me same error.
I'd appreciate if you guys can have a look and help me please.
Many thanks in advance guys
tom_hungston said:
Hi Guys,
I'm on the same boat as joel_gil,
I've got S7 (originally purchased on sprint USA network) and now I've unlocked it using idoneapps without root.
I'm on G930PVPU5BQJ3 firmware at the moment and I'd like to flash G930U firmware which is network unlocked and not bloatware free.
I've downloaded the firmware below multiple times from sammobile.com and tried flashing using latest Odin 3.12.10 and everytime I am getting error message.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/SPR/download/G930UUES4BQL1/201542/
I have also tried XAS version as well but same result
SW check failed aboot fused 5 > binary 4 message.
I've got FRP and OEM unchecked and still its giving me same error.
I'd appreciate if you guys can have a look and help me please.
Many thanks in advance guys
Click to expand...
Click to collapse
You can't install the U firmware...the bootloader binary files are different. You will have to wait for the U firmware to catch up in order to install it. However, you can install the latest Sprint firmware without any issue.
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5, and how to tell the files apart can be found here
https://www.arencambre.com/blog/2018...omment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
Hello, many times i was trying to flash stock firmware from my country but i couldnt because i was getting stuck on sboot.bin.lz4 , well if you get stuck there too the solution is to flash the firmware from another version of odin. A little search on google didnt hurt me tho , so just get the version of the link bellow and Voila .. ! if you have any other problem i might can help you, post down your comments
https://download.highonandroid.com/file/Tools/ODIN/Odin3_v3.13.1.zip
Works
Thanks, this solved my issue
My question is that I'm afraid of having trouble updating with odin. I did some time ago an odin update on a 3 note and it failed. A triangle appeared on the screen and had to be brought in for technical assistance. I have all the files downloaded here for the s8, with the latest odin, but I do not know if I upgrade or not, or if I expect the OTA .... On my S8 is with ((XX1CRAP) no problems, but the pack security is February 1. And by Sammobiles 2 new updates have come out.I'm in doubt.
adrianoturbo said:
My question is that I'm afraid of having trouble updating with odin. I did some time ago an odin update on a 3 note and it failed. A triangle appeared on the screen and had to be brought in for technical assistance. I have all the files downloaded here for the s8, with the latest odin, but I do not know if I upgrade or not, or if I expect the OTA .... On my S8 is with ((XX1CRAP) no problems, but the pack security is February 1. And by Sammobiles 2 new updates have come out.I'm in doubt.
Click to expand...
Click to collapse
So what was the problem ? You installed an older version of Odin and your phone got stuck on triangle?
Shock_Weaver said:
Thanks, this solved my issue
Click to expand...
Click to collapse
Happy to help everyone everyday
adrianoturbo said:
My question is that I'm afraid of having trouble updating with odin. I did some time ago an odin update on a 3 note and it failed. A triangle appeared on the screen and had to be brought in for technical assistance. I have all the files downloaded here for the s8, with the latest odin, but I do not know if I upgrade or not, or if I expect the OTA .... On my S8 is with ((XX1CRAP) no problems, but the pack security is February 1. And by Sammobiles 2 new updates have come out.I'm in doubt.
Click to expand...
Click to collapse
I did the same, but I used the CSC instead of Home_CSC and my device was wiped clean. However, I had backed up my entire device and just did a restore after boot-up. I think the problem is from using incompatible software upgrades from different regions.
StonebridgeGr said:
So what was the problem ? You installed an older version of Odin and your phone got stuck on triangle?
Click to expand...
Click to collapse
When I had this problem, it was with note 3, and I had to take technical assistance to get back to normal, but if I remember correctly I used a rom from another location. So my fear is to make a mistake with my s8, but all I downloaded to upgrade the S8 was from the same location I'm using today.
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
I do not know it's worth upgrading the S8 to the most current software, the safe pack is from February 1, 2018. According to Sammobiles already software of month 5 for my device from my region.
It's because of the compression older version cant handle it..3.13.1 works.
strubedo said:
It's because of the compression older version cant handle it..3.13.1 works.
Click to expand...
Click to collapse
Thanks
rivare1 said:
Thanks
Click to expand...
Click to collapse
did my little guide helped you ?
i confirm it again, the version i gave above its working guys, its gonna many problems. try it
Thanks man!!
Didn't work I was already using this version of Odin.
Reaper226 said:
Didn't work I was already using this version of Odin.
Click to expand...
Click to collapse
Same here...using ODIN 3 v3.13 but still fails after sboot.bin.
Did you manage to solve it for yourself?
Reaper226 said:
Didn't work I was already using this version of Odin.
Click to expand...
Click to collapse
Tranquilo786 said:
Same here...using ODIN 3 v3.13 but still fails after sboot.bin.
Did you manage to solve it for yourself?
Click to expand...
Click to collapse
Some more info other than ' it didn't work ' would be helpful in trying to solve your issues.
Failng at sboot.bin can mean a few things.
So info like maybe a screenshot of odin,any other errors in odin, current firmware on phone, firmware trying to flash etc would helpful.
Thanks a lot! This solved my issue! A little, but big, detail lol
StonebridgeGr said:
Hello, many times i was trying to flash stock firmware from my country but i couldnt because i was getting stuck on sboot.bin.lz4 , well if you get stuck there too the solution is to flash the firmware from another version of odin. A little search on google didnt hurt me tho , so just get the version of the link bellow and Voila .. ! if you have any other problem i might can help you, post down your comments
https://download.highonandroid.com/file/Tools/ODIN/Odin3_v3.13.1.zip
Click to expand...
Click to collapse
Thank you! This was very helpful! I was having a hard time with Odin not flashing anything to my S8+ and the version 13.1 resovled the issue.
hey dude i am stuck
StonebridgeGr said:
Happy to help everyone everyday
Click to expand...
Click to collapse
Hey i looked what you said. but with my phone i get this still
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 5529 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Downgrading from Oreo to Nougat
While trying to downgrade my G950F to nougat Odin stuck at (<ID:0/004> sboot.bin <ID:0/004> FAIL!) even im using the last version V3.13.1
Y0SS3F said:
While trying to downgrade my G950F to nougat Odin stuck at (<ID:0/004> sboot.bin <ID:0/004> FAIL!) even im using the last version V3.13.1
Click to expand...
Click to collapse
You cannot downgrade firmware due to bootloader version numbers hence errors ie: Oreo to nougat