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.
Related
I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Also, redownload the tar file. It could be a bad download.
jd1639 said:
Also, redownload the tar file. It could be a bad download.
Click to expand...
Click to collapse
ok will try that.
here are the messages that I am getting
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
2nd message
ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
xBeerdroiDx said:
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
Click to expand...
Click to collapse
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
If you had mf3 on, no amount of odin is going to help.
jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
You must have taken the update to MF3. Essentially, you will not be allowed to downgrade firmware back to older versions. The way Samsung is writing the bootloader is there a monotonic counter only going in one direction, up. So if the bootloader has been updated to the latest version by an OTA, you can't revert it back. Currently I believe there is no workaround, but we have some awesome devs on this site so keep your fingers crossed.
jimsond said:
I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Click to expand...
Click to collapse
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
jeffreii said:
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
Click to expand...
Click to collapse
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
jimsond said:
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
Click to expand...
Click to collapse
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
jeffreii said:
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
Click to expand...
Click to collapse
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
P.S in kies the current firmware version PDA:MF3 / PHONE:MF3 / CSC:MF3 (ATT)
jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
jd1639 said:
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
Click to expand...
Click to collapse
It look like I have mf3 So I f__k up. The phone is working
jimsond said:
It look like I have mf3 So I f__k up. The phone is working
Click to expand...
Click to collapse
Good to hear the phone is working. I wouldn't mess with it any more.
jeffreii said:
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
Click to expand...
Click to collapse
Thanks for your input I have a hard time saying on paper what was my problem. I like to talk things out and I use the link that you posted and I have root now..
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've been searching and found many threads but none that said what to do next in this situation.
I was trying out different roms and then it would not load past the sammy logo. This kept me from loading safestrap and fixing it.
I tried using odin to install stock rom.
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After that I tried different cables, usb ports, restarting the pc / phone, wiping cashe, factory reset and reinstalling kies. I made sure kies was not working in the background.
So far this is what I got from reading many different threads. Any Ideas?
I know you guys get stories like this a lot and it does get tiresome, but it would mean a lot to me if you help me out. Thanks.
So is my nand messed up? What does that mean?
Here is a thread that is similar but I don't think it will work for me.
http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867
I'll try my best to help out...I just Odin back to stock 5 minutes ago... what files are you using for Odin and what Odin version do you have?
Have you look at this thread? This help me out a lot
http://forum.xda-developers.com/showthread.php?t=2926642
stric85 said:
I'll try my best to help out...I just Odin back to stock 5 minutes ago... what files are you using for Odin and what Odin version do you have?
http://forum.xda-developers.com/showthread.php?t=2926642
Click to expand...
Click to collapse
I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5
Odin3v185
Thank you very much for your help.
Trying out the files in the thread you posted. Odin is definitely different and the stock rom probably is too.
Wow worked like a charm! Thanks bro! I guess I had the wrong files? funny because I got them from galaxys4root and I have never had a problem before.
Got a paypal? I would have been willing to pay someone to fix this. It wont be much but I want to say thanks.
darkmx-6 said:
Wow worked like a charm! Thanks bro! I guess I had the wrong files? funny because I got them from galaxys4root and I have never had a problem before.
Got a paypal? I would have been willing to pay someone to fix this. It wont be much but I want to say thanks.
Click to expand...
Click to collapse
Glad it worked! I just pointed you to the thread I used to Odin to stock on my s4, you did the rest.[emoji1] Thanks for letting me know I could be of little help!
I am afraid i have turned my galaxy tab 4 7" (sm-t230) into an expensive coaster at this point.
It doesn't do much of anything anymore. When it's booted it does nothing but show the samsung logo sparkling and when i start it into twrp just about anything i do ends with "cannot mount '/data' and not much else.
the local storage shows 0 and through the filemanager i see there are the folders but no files inside the folders.
Ofcourse i am well aware that i must've done goofed somewhere in my enthousiastic attempt to install a custom rom and the increasingly frantic attempts after that somehow resulted in the tab not booting past the samsung logo to fix it (from trying other roms to using odo in different configs to get anything on it that worked, including kernels and such) probably only added to the result which i described above. I know that, if this is irreversably killed the tablet i have only myself to blame.
But somehow i still have a sparkle of hope there is a way to fix the damage my stupidity has caused. It's still trying to boot and when i try to install for example the stockrom rom zipfile the progress bar dutyfully progresses until its end and the message "successfull" even shows in blue. When i put the tablet into download mode Odin still gives the all clear like it should but it seems like its teasing me with those things. When i boot it stops at the logo and when i go into twrp and do anything it fails to mount '/data' and some actions result in other failures to mount folders.
So.... IS there anything i can still do? (flashing the stock samsung rom wont work at all by the way, from twrp)
any help in getting any rom doing anything similar to working would be an improvement and appreciated.
So you say you've tried reinstalling the stock rom in TWRP, have you tried flashing a stock official firmware file with Odin?
thisisapoorusernamechoice said:
So you say you've tried reinstalling the stock rom in TWRP, have you tried flashing a stock official firmware file with Odin?
Click to expand...
Click to collapse
Well, no. Not through Odin. I haven't been able to find, much less download, the tar version of the one for my region. I'm in the Netherlands and so i guess i am looking for either a specifically dutch or an international or european version.
I have found the zip version for my region and spent almost 12 hours downloading it (after spending hours to find a host that would actually start the download without either survey terror or payed account registration torture.)
twrp doesn't like it though and simply fails.
[update]i cannot believe my stupidity. Your post made me wonder if the zip file contained the tar file i was looking for. It (ofcourse) did and i am now extracting it. I shall try to Odin it onto the tablet in download mode and post the results here.
I noticed the region i have isn't listed in the list you linked to. If you want it i can put it in my dropbox, google drive or onedrive for you so you can download it. the filename is T230XXU0AOD2_T230PHN0AOD3_PHN.zip and the region is the netherlands.
[/update]
deuZige said:
Well, no. Not through Odin. I haven't been able to find, much less download, the tar version of the one for my region. I'm in the Netherlands and so i guess i am looking for either a specifically dutch or an international or european version.
I have found the zip version for my region and spent almost 12 hours downloading it (after spending hours to find a host that would actually start the download without either survey terror or payed account registration torture.)
twrp doesn't like it though and simply fails.
[update]i cannot believe my stupidity. Your post made me wonder if the zip file contained the tar file i was looking for. It (ofcourse) did and i am now extracting it. I shall try to Odin it onto the tablet in download mode and post the results here.
I noticed the region i have isn't listed in the list you linked to. If you want it i can put it in my dropbox, google drive or onedrive for you so you can download it. the filename is T230XXU0AOD2_T230PHN0AOD3_PHN.zip and the region is the netherlands.
[/update]
Click to expand...
Click to collapse
It's a good thing there's no audio recording of what i shouted here the last 30 seconds to a minute. Everything seemed to go perfectly in Odo. I started the tablet in download mode, started Odo, and connected the usb cable. then clicked ap and selected the tar file and removed the tick at f.reset time. then i clicked start. heres the messages odo gave me... errr i mean odin:
Code:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0AOD2_T230PHN0AOD3_T230XXU0AOD2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> timh.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> obm.bin
<ID:0/004> loke_1st.bin
<ID:0/004> loke_2nd.bin
<ID:0/004> DTim.Primary
<ID:0/004> DTim.Recovery
<ID:0/004> DTim.CP
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> radio.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Odin showed the green square with pass and the tablet rebooted.
and didn't go further than the samsung logo.
which it show still.... i have exhausted my most vile, evil and offensive curseword vocabulary shouting (which my neighbours will probably not appreciate as it's 01:35 am right now) before starting to write this reply....
i guess i am, truely inescabably, F worded now ain't i??
i am so depressed right now i can't even tell ya.
anyway, any suggestions?
(thanks for taking the time to read my sorrows and replying by the way. it IS really appreciated.)
just another reply to mention that i tried the same as the above with the tick at f.reset time and got the same result.
staring at the samsung logo in dispair right now....
deuZige said:
just another reply to mention that i tried the same as the above with the tick at f.reset time and got the same result.
staring at the samsung logo in dispair right now....
Click to expand...
Click to collapse
Did you reboot into recovery and factory reset? That should clean things up. I had to do that every time I flashed a firmware through Odin.
Sent from my ZTE_N9511 using Tapatalk
DUHAsianSKILLZ said:
Did you reboot into recovery and factory reset? That should clean things up. I had to do that every time I flashed a firmware through Odin.
Sent from my ZTE_N9511 using Tapatalk
Click to expand...
Click to collapse
i hadn't.
no i have, and i still get no further than the samsung logo.
the recovery was nothing like twrp though and it had loads of errors. again and...
AAAAH!!
OMG!!
YESYESYES!!!!
you guys are like gods to me now. As i was typing this reply the samsung galaxy welkom screen sprang to life and is now waiting for me to configure stuff!!! It seems to have worked!!!!!!!
I will not publicly explain the circumstances (i did in a pm to poorlychosenname) but trust me when i say you have no idea how much of a good deed you guys did here today!!!
I am truely and greatly indebted to both you guys/galls and if there is anything i can do for you, now or in the future, please ask and i will do anything i can to help!!!!
I am literally in teart right now!!!
Thank you!!!!
deuZige said:
i hadn't.
no i have, and i still get no further than the samsung logo.
the recovery was nothing like twrp though and it had loads of errors. again and...
AAAAH!!
OMG!!
YESYESYES!!!!
you guys are like gods to me now. As i was typing this reply the samsung galaxy welkom screen sprang to life and is now waiting for me to configure stuff!!! It seems to have worked!!!!!!!
I will not publicly explain the circumstances (i did in a pm to poorlychosenname) but trust me when i say you have no idea how much of a good deed you guys did here today!!!
I am truely and greatly indebted to both you guys/galls and if there is anything i can do for you, now or in the future, please ask and i will do anything i can to help!!!!
I am literally in teart right now!!!
Thank you!!!!
Click to expand...
Click to collapse
No problem! Let "us" know if you get any data errors or so. My guess is that you had an messed up data partition since I've seen a few with the same thing.
If data is still messed up, flash back twrp, go to wipe, hit advanced wipe, then tick the data then hit "repair or change file systems" something like that and hit repair. Then slide the slider.
If that doesn't work... go to wipe , theb hit advanced wipe, tick data, hit "repair or change file systems" then format it to ext4
Sent from my ZTE_N9511 using Tapatalk
DUHAsianSKILLZ said:
No problem! Let "us" know if you get any data errors or so. My guess is that you had an messed up data partition since I've seen a few with the same thing.
If data is still messed up, flash back twrp, go to wipe, hit advanced wipe, then tick the data then hit "repair or change file systems" something like that and hit repair. Then slide the slider.
If that doesn't work... go to wipe , theb hit advanced wipe, tick data, hit "repair or change file systems" then format it to ext4
Sent from my ZTE_N9511 using Tapatalk
Click to expand...
Click to collapse
honestly, i have tested taking pictures, uploading them to google and i have added all new accounts where i could. That worked without error, and the picture worked, and uploaded. I am doing nothing else until i get back home tomorrow from the park where i'll be taking pictures of my son.
When those are safe, i'll do whatever you want!!!
again, i cannot express the greatness of my gratitude for this!!
[supplemental]
i must sleep now. gnight!!!
[/consciousness]
Seems like everything is working fine! No need for wiping and formatting data if you have no more issues. I guess your good to go!
Sent from my ZTE_N9511 using Tapatalk
Hey I'm sorry I never got back to you, and I feel like a total moron for forgetting to tell you to factory reset, glad @DUHAsianSKILLZ took care of things for @deuZige, I hope everything's OK going forward and I'll be happy to help if I can if it isn't.
My sister's phone is Galaxy Grand Prime and still running Android 4.4.4. I've searched over the net and there is Lollipop update already for some countries. There's still no update here in the Philippines. Can I update this device using firmwares from other countries? Thanks!
jelmerpeligrino said:
My sister's phone is Galaxy Grand Prime and still running Android 4.4.4. I've searched over the net and there is Lollipop update already for some countries. There's still no update here in the Philippines. Can I update this device using firmwares from other countries? Thanks!
Click to expand...
Click to collapse
yes you can! i'm also from the philippines and i'm currently on the Russian firmware (G530HXXUBOH5)
@jelmerpeligrino Post a screenshot of your About Phone. @morgannoobman That is a really old firmware.
Has.007 said:
@jelmerpeligrino Post a screenshot of your About Phone. @morgannoobman That is a really old firmware.
Click to expand...
Click to collapse
Here bro.
morgannoobman said:
yes you can! i'm also from the philippines and i'm currently on the Russian firmware (G530HXXUBOH5)
Click to expand...
Click to collapse
How did you do it?
jelmerpeligrino said:
Here bro.
Click to expand...
Click to collapse
Download this firmware nd the mention me. Also download Odin 3.10.xx
http://www.sammobile.com/firmwares/download/106519/G530HXCU1BPI2_G530HUUB1BPI1_TTT/
Has.007 said:
Download this firmware nd the mention me. Also download Odin 3.10.xx
http://www.sammobile.com/firmwares/download/106519/G530HXCU1BPI2_G530HUUB1BPI1_TTT/
Click to expand...
Click to collapse
If I flashed Lollipop on this device, all data stored on my device will be deleted?
And I searched the latest version of odin, it is now 3.12.3.
jelmerpeligrino said:
If I flashed Lollipop on this device, all data stored on my device will be deleted?
And I searched the latest version of odin, it is now 3.12.3.
Click to expand...
Click to collapse
No
jelmerpeligrino said:
If I flashed Lollipop on this device, all data stored on my device will be deleted?
And I searched the latest version of odin, it is now 3.12.3.
Click to expand...
Click to collapse
As @waleeds1 said, No. But I recommend you to take backup of all your data nd do a factory reset after you flash Lollipop firmware.
That way you won't get any lags or performance glitches.
Has.007 said:
As @waleeds1 said, No. But I recommend you to take backup of all your data nd do a factory reset after you flash Lollipop firmware.
That way you won't get any lags or performance glitches.
Click to expand...
Click to collapse
What are the steps on how to flash Lollipop? I already have the necessary files to begin with. Thanks!
jelmerpeligrino said:
What are the steps on how to flash Lollipop? I already have the necessary files to begin with. Thanks!
Click to expand...
Click to collapse
Make sure you've a good backup. Nd also you've Samsung USB drivers already installed in your PC.
Power off your device nd boot in download mode by pressing Volume Down + Home + Power Buttons together.
Then open Odin nd connect your phone to PC via data cable nd press volume Up key on phone, then if it shows you "Added" in Odin you're good to go.
Select the AP option nd select the firmware which you've downloaded. Now it'll take some time to verify the md5 as depending upon the speed of your PC. Once it has verified you'll be able to click on other options. So now you've to click on Start nd make sure you don't move your device or the connection doesn't cut off or your device might get hard bricked.
That's it, the flashing time would be about 4-5 minutes. After it is flashed the phone will reboot nd now you can factory reset the device properly for a clean new device.
I've told everything you needed to know.
Enjoy!
Has.007 said:
As @waleeds1 said, No. But I recommend you to take backup of all your data nd do a factory reset after you flash Lollipop firmware.
That way you won't get any lags or performance glitches.
Click to expand...
Click to collapse
The thing you said is correct but I recommend first start your phone without factory reseting @jelmerpeligrino becuase if u dont face any performance or other issues. But if u wish to factory then its still a good choice
waleeds1 said:
The thing you said is correct but I recommend first start your phone without factory reseting @jelmerpeligrino becuase if u dont face any performance or other issues. But if u wish to factory then its still a good choice
Click to expand...
Click to collapse
Yes I told that in my second post.
Actually I believe he has been using Kitkat from a long time nd for most of the apps, the things have changed. The API differences creates certain problems as it is recommended by Samsung itself to factory reset the device after Android version change.
From Kitkat to Kitkat nd Lollipop to Lollipop factory reset is not needed but for SDK changing it is needed.
Has.007 said:
Yes I told that in my second post.
Actually I believe he has been using Kitkat from a long time nd for most of the apps, the things have changed. The API differences creates certain problem as it is recommended by Samsung itself to factory reset the device after Android version change.
From Kitkat to Kitkat nd Lollipop to Lollipop factory reset is not needed but for SDK changing it is needed.
Click to expand...
Click to collapse
I didnt read that part. U got a point there mate.
Hi, I've roote my Galaxy grand prime successfully and want to upgrade to Lollipop but it doesn't work, I've tried already several files but it always ends with an error
here is the Odin Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do to make i happen
Happy new year to all of you
woris said:
Hi, I've roote my Galaxy grand prime successfully and want to upgrade to Lollipop but it doesn't work, I've tried already several files but it always ends with an error
here is the Odin Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do to make i happen
Happy new year to all of you
Click to expand...
Click to collapse
Did you download the correct firmware and are you using ap in odin if nor then you should use ap and browse for the firmware.
waleeds1 said:
Did you download the correct firmware and are you using ap in odin if nor then you should use ap and browse for the firmware.
Click to expand...
Click to collapse
Thanks for your reply, yes, I've got the correct Firmware, correct Odin settings, I even tried the Kasachstan firmware that you used but same result.
Has.007 said:
Yes I told that in my second post.
Actually I believe he has been using Kitkat from a long time nd for most of the apps, the things have changed. The API differences creates certain problems as it is recommended by Samsung itself to factory reset the device after Android version change.
From Kitkat to Kitkat nd Lollipop to Lollipop factory reset is not needed but for SDK changing it is needed.
Click to expand...
Click to collapse
Is this normal bro? I flashed it already.
waleeds1 said:
Did you download the correct firmware and are you using ap in odin if nor then you should use ap and browse for the firmware.
Click to expand...
Click to collapse
woris said:
Thanks for your reply, yes, I've got the correct Firmware, correct Odin settings, I even tried the Kasachstan firmware that you used but same result.
Click to expand...
Click to collapse
No you don't have the right firmware for your device. The baseband difference. Post a screenshot from your About Phone nd also the link of firmware you're trying to flash.
jelmerpeligrino said:
Is this normal bro? I flashed it already.
Click to expand...
Click to collapse
Yes it is normal, It is weird tho how you've two devices connected. Or maybe there's some bug in this version of Odin. Anyways all working good?
Has.007 said:
No you don't have the right firmware for your device. The baseband difference. Post a screenshot from your About Phone nd also the link of firmware you're trying to flash.
Yes it is normal, It is weird tho how you've two devices connected. Or maybe there's some bug in this version of Odin. Anyways all working good?
Click to expand...
Click to collapse
So far, it was good. The performance is better now compared to Kitkat and and the sluggishness was gone. Thanks bro!
Btw, do you have any Marshmallow ROM for this device?