[Q] Unroot problem: Odin FAIL - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Apologies if this has been asked before, but I tried checking everywhere for a solution and couldn't come up with anything.
I have an AT&T Galaxy S4 I337. I rooted it, but now I want to unroot it. I used Odin 3v185 and this is what I get:
Screenshot: i.imgur.com/XRBVjH6.jpg
The white box on the bottom left says:
<ID:0/005> 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/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I've tried it multiple time with the I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 and I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 firmware. I am using the original Samsung USB cord. I've also tried it only 3 different USB ports on my computer. I am running XP. Can anyone help me?

Your on the mf3 firmware. Odin won't work. I can tell because of the "fused 2" in the Odin printout

Thanks. Is there a way to unroot it?

tcow24 said:
Thanks. Is there a way to unroot it?
Click to expand...
Click to collapse
Can you boot now? If you can unroot in super su.

tcow24 said:
Thanks. Is there a way to unroot it?
Click to expand...
Click to collapse
Yes there is, I'm guessing you are able to boot to your phone?
Here's a link and instructions you can follow. Good luck and report to us how it goes
http://forum.xda-developers.com/showthread.php?p=45340743#post45340743

It worked! Thanks JD and haremmon. I feel like an idiot for not seeing that thread.

I need some help please?
I have a Galaxy s4 rooted and I wipe the system and rebooted... I was installing a rom and did not even think anout restoring my old ones. so know I am stuck and the phone will not go into twrp, all it dose is beeps evey 3 seconds. I can get to odin download and i have downloaded stock fimware md5 files and only had one not fail on me using odin3. but it dose the same thing beeps and still can not get to recovery.. please help this is frustrating.

markdthor28 said:
I have a Galaxy s4 rooted and I wipe the system and rebooted... I was installing a rom and did not even think anout restoring my old ones. so know I am stuck and the phone will not go into twrp, all it dose is beeps evey 3 seconds. I can get to odin download and i have downloaded stock fimware md5 files and only had one not fail on me using odin3. but it dose the same thing beeps and still can not get to recovery.. please help this is frustrating.
Click to expand...
Click to collapse
pull battery,
put battery back in,
boot into odin using the physical keys (home+volume down+power),
then when it says press volume up to boot into odin, or volume down for cancel choose volume down.
Might boot up normally, i have the issue to where to recovery is messed up, all i need is the 'install-recovery.sh' but no one who has a rooted S4 running MF3 has responded to me yet..ill let you know if i fix the recovery that way.

h11wiscan said:
pull battery,
put battery back in,
boot into odin using the physical keys (home+volume down+power),
then when it says press volume up to boot into odin, or volume down for cancel choose volume down.
Might boot up normally, i have the issue to where to recovery is messed up, all i need is the 'install-recovery.sh' but no one who has a rooted S4 running MF3 has responded to me yet..ill let you know if i fix the recovery that way.
Click to expand...
Click to collapse
At this point, I don't know if you'd be able to fix it that way. The only option that many users have been doing is going to best buy with a Samsung experience area and having them reflash the MF3 firmware.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

tcow24 said:
Apologies if this has been asked before, but I tried checking everywhere for a solution and couldn't come up with anything.
I have an AT&T Galaxy S4 I337. I rooted it, but now I want to unroot it. I used Odin 3v185 and this is what I get:
Screenshot: i.imgur.com/XRBVjH6.jpg
The white box on the bottom left says:
<ID:0/005> 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/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I've tried it multiple time with the I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 and I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 firmware. I am using the original Samsung USB cord. I've also tried it only 3 different USB ports on my computer. I am running XP. Can anyone help me?
Click to expand...
Click to collapse
Mine is same issue, except my phone says: Unsupport dev_type, I am using samsung galaxy s3 I9300 with binary count 2.
Please help me to resolve this and unroot my device.

srikanthkata said:
Mine is same issue, except my phone says: Unsupport dev_type, I am using samsung galaxy s3 I9300 with binary count 2.
Please help me to resolve this and unroot my device.
Click to expand...
Click to collapse
Not trying to be rude but please go post this question under the GS3 forum. The GS3 forum can be found here http://forum.xda-developers.com/galaxy-s3

Related

SGS4 won't boot....

Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
vivelafrance said:
Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
Click to expand...
Click to collapse
where odin failed exactly?
did you try changing usb port? kies totally disabled? original usb cable?
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
vivelafrance said:
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
Click to expand...
Click to collapse
one more thing, remove battery for a couple of minutes, then try with odin 1.85
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
vivelafrance said:
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
Click to expand...
Click to collapse
i dont know if flashing pit file along with the firmware will work
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
vivelafrance said:
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
Click to expand...
Click to collapse
pit file is flashed with the firmware. choose the right pit for your device! re-partition will be checked automatically when you select the pit file.
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
vivelafrance said:
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
Click to expand...
Click to collapse
did you flash firmware with the pit file at same time and didnt work?
almost you did everything.
try to change computer if available.
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
vivelafrance said:
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
Click to expand...
Click to collapse
If you haw acess t dawnload mod you are nhot bricked pleas go and try other pc
Sent from my GT-I9505 using xda premium
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
this is surely NOT a mobile issue if you can enter into download mode.
i had the exact issue a month ago when i had note2.
if you can't try it on another pc, try :
1) uninstall skies completely
2) unisnstall usb drivers
3) reboot the pc
4) connect your s4 in download mode to your pc.
5) let your pc install freah usb drivers
6) start odin and flash
7) if still you get the same error download a different verison of the official rom and try flashing.
i followed the above procedure couple of times and was finally able to install the rom. the issue is either with the drivers or the rom.
Sent from my GT-I9500 using xda app-developers app
bricked for sure
vivelafrance said:
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
Click to expand...
Click to collapse
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Bluetoth10 said:
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Click to expand...
Click to collapse
thnx. yeah, flashing the PIT actually always worked but it was the only thing that worked! lol
DenmarkRootN00b said:
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
vivelafrance said:
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
Click to expand...
Click to collapse
good luck at least i just thought it would work by doing it in recovery but yeah... warranty is better.. if not.. then keep trying if they wont replace it
ok I FINALLY could access the stock recovery, did a full wipe and everything is back in order now, works perfectly.
THANKS to all!

Verizon Galaxy Note 3 bricked?

I think I may have bricked my phone, possibly a softbrick? I was using Odin3 v3.09 with Root de la vega for my Verizon Galaxy Note 3, Model SM-N900V. The tutorial I was using said it was for my phone, I followed all the instructions, and I got fail the first time using the stock cord that came with it so I tried again and used a regular usb 2.0 cord and got a fail the second time.
This is the text from Odin.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Root_de_la_Vega.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> cache.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the text on my phone.
Code:
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
[COLOR="Gray"]KNOX Kernal Lock: 0x0
KNOW Warranty Void: 0x0
QualCOMM SecureBoot: Enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write Protection: Enable[/COLOR]
[COLOR="Red"]Secure Check Fail: cache[/COLOR]
I am assuming I am going to need to flash the phone back to a stock firmware but I am not sure which one I should be using, or how to go about doing that exactly as well. I have rooted/unrooted phones in the past. I have also flashed my old phones as well, but I don't remember how to nor can I seem to figure it out with this phone. If someone could point me in the right direction I would greatly appreciate the help. I am trying to put the HyperDrive ROM on my phone.
Update!
I came accross this method, http://forum.xda-developers.com/showthread.php?t=2483380
I followed the instructions on flashing to stock with Odin and I didn't have any luck in getting it to work. I downloaded the MI9 tar.md5 file, and the pit file selected them in there proper spots in the program and ran it. I got this error.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and this error on my phone
SW REV CHECK FAIL : (aboot)Fused 2 > Binary 1
This should be a easy fix. Enter recovery mode by powering down the phone then holding the home button, vol up and the power button. Hold down all three buttons until you see recovery booting on the top in blue. The phone will reboot into recovery and then scroll to wipe data/factory reset with the vol down key and then press the power button and wait until it completes the reset. Now you should be good to go again. This will wipe all data but you will have your phone back.
Misterxtc said:
This should be a easy fix. Enter recovery mode by powering down the phone then holding the home button, vol up and the power button. Hold down all three buttons until you see recovery booting on the top in blue. The phone will reboot into recovery and then scroll to wipe data/factory reset with the vol down key and then press the power button and wait until it completes the reset. Now you should be good to go again. This will wipe all data but you will have your phone back.
Click to expand...
Click to collapse
When I do that I get a screen that says,
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
luckychalmz said:
When I do that I get a screen that says,
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Click to expand...
Click to collapse
You might need to flash MJE instead of MI9 with Odin.
Misterxtc said:
You might need to flash MJE instead of MI9 with Odin.
Click to expand...
Click to collapse
Do you know of anywhere that I can get that file, the link that is in the guide is saying its going to take like three days. It's only 1.3gbs so I don't see why.
luckychalmz said:
Do you know of anywhere that I can get that file, the link that is in the guide is saying its going to take like three days. It's only 1.3gbs so I don't see why.
Click to expand...
Click to collapse
Try this guide if you haven't already. I just tried and it said three hours not days. If it's slow try canceling and restarting it again. You might get a faster dl rate. http://forum.xda-developers.com/showthread.php?t=2528707
Misterxtc said:
Try this guide if you haven't already. I just tried and it said three hours not days. If it's slow try canceling and restarting it again. You might get a faster dl rate. http://forum.xda-developers.com/showthread.php?t=2528707
Click to expand...
Click to collapse
That one is definitely going faster. Thank you. I will try this one once it's finished.
luckychalmz said:
That one is definitely going faster. Thank you. I will try this one once it's finished.
Click to expand...
Click to collapse
No problem. Did you try to clear cache in recovery mode? If not give that a try and then the factory reset while you are waiting. You have nothing to loose at this point.
Misterxtc said:
No problem. Did you try to clear cache in recovery mode? If not give that a try and then the factory reset while you are waiting. You have nothing to loose at this point.
Click to expand...
Click to collapse
That fixed it, thank you. Appreciate your help.
luckychalmz said:
That fixed it, thank you. Appreciate your help.
Click to expand...
Click to collapse
Cool, I'm glad to help and direct you to the info that has been shared. Enjoy.
I know a much faster,simpler and less data-damaging wau
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
technoshima said:
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
Click to expand...
Click to collapse
You my friend, are a genius!!! I was crapping my pants thinking it was over. Thanks a bunch. And yes, it is a much, much faster download than that MJE that took forever to download.
Kudos again, my friend.
Still having issue with Samsung Write Protection
fanatic4hockey said:
You my friend, are a genius!!! I was crapping my pants thinking it was over. Thanks a bunch. And yes, it is a much, much faster download than that MJE that took forever to download.
Kudos again, my friend.
Click to expand...
Click to collapse
technoshima said:
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
Click to expand...
Click to collapse
I was able to flash the PIT file with Odin like you said which enabled me to get back to recovery, but I am still having issues with the Samsung Write protection being enabled (which is preventing me from flashing anything with Safestrap including trying to fully wipe and restart). I found out after attempting to flash my verizon note 3 that the write protection was an option that needed to be unchecked on the phone before flashing. Now I can't change it without being able to login all the way into the phone. Are there any options out there to change the write feature outside of being able to actually load the phone, like ADB?
luckychalmz said:
That fixed it, thank you. Appreciate your help.
Click to expand...
Click to collapse
Hi guys
I need some help I rooted my Verizon Note 3 and is stock on:
Odin Mode Please see attached image
When I ran these files : ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit on odin3
I got this error.
Please advice.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vampirelife said:
Hi guys
I need some help I rooted my Verizon Note 3 and is stock on:
Odin Mode Please see attached image
When I ran these files : ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit on odin3
I got this error.
Please advice.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Looks similar to what I was getting from Odin. Did you have to uncheck the write protection in your phone settings before flashing anything? Someone told me that might be the cause of what happened with mine since I didn't even hear about doing so until I had already attempted to flash my phone.
im also getting a fail just after aboot. I originally attempted to install the deodex version on kitkat and originally was still able to access safestrap.
I have tried flashing every rom i can get my hands on over odin. ive tried making a recovery from my other note 3 via safestrap and swapping the micro sd over to this one. did not show up when i went to ss recover. so i booted to recovery cleared cache. still got aboot failed(auth) so i booted to recovery again and cleared everything except data. (including system) now i cant access SS any longer. get stuck on bootload screen or get verizon sofware assistant message. still unable to flash roms via oden i have tried everything but lollipop and odin versions 3.9 3.7 3.10
im am completely lost. im almost ready to ship it to someone to fix it for me.
I'm gonna bump this in the hopes someone sees it and can help me.
luckychalmz said:
I think I may have bricked my phone, possibly a softbrick? I was using Odin3 v3.09 with Root de la vega for my Verizon Galaxy Note 3, Model SM-N900V. The tutorial I was using said it was for my phone, I followed all the instructions, and I got fail the first time using the stock cord that came with it so I tried again and used a regular usb 2.0 cord and got a fail the second time.
This is the text from Odin.
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Root_de_la_Vega.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
cache.img.ext4
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
This is the text on my phone.
Code:
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
[COLOR="Gray"]KNOX Kernal Lock: 0x0
KNOW Warranty Void: 0x0
QualCOMM SecureBoot: Enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write Protection: Enable[/COLOR]
[COLOR="Red"]Secure Check Fail: cache[/COLOR]
I am assuming I am going to need to flash the phone back to a stock firmware but I am not sure which one I should be using, or how to go about doing that exactly as well. I have rooted/unrooted phones in the past. I have also flashed my old phones as well, but I don't remember how to nor can I seem to figure it out with this phone. If someone could point me in the right direction I would greatly appreciate the help. I am trying to put the HyperDrive ROM on my phone.
Click to expand...
Click to collapse
Before you started this...what version of android were you using? You must flash the last version you had running or higher.
Get the firmware from here
http://www.sammobile.com/firmwares/database/SM-N900V/
instructions are also there
You can also try having Verizon reflash it or at the Samsung section of your local best buy
marcotheclepto said:
I'm gonna bump this in the hopes someone sees it and can help me.
Click to expand...
Click to collapse
Sent from my Note 3 via Tapatalk
donc113 said:
Before you started this...what version of android were you using? You must flash the last version you had running or higher.
Get the firmware from here
instructions are also there
You can also try having Verizon reflash it or at the Samsung section of your local best buy
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
thanks, im just jumping straight to 5.0 and hoping for the best. half hour left on the download. fingers crossed
*update* it seems the newer version was the answer for me... now to find a way to root it on lolipop... whole point was originally to get hyperdrive and get some headphone software worth using.

[Q] AT&T Galaxy S4 Soft bricked phone-can't ODIN restore

I have been searching threads for 6 hours, but haven't found anything conclusive.
I rooted my phone a while back, but today I decided to install a new custom ROM. I backed up the ROM to my external SD and installed the new one through safestrap. However, when I tried to reboot, I just got stuck on a screen that says samsung and has an open lock.
I am able to get into download mode, but not into recovery. After I boot into download mode, it says write protection:enabled (not sure that is normal, but I thought I would mention it). I open up Odin and the drivers seem to load fine. I have tried a a few versions of ODIN and two different Stock ROMs, but it fails every time. On my phone, after it fails, I get a message that says SW Rev. Check Fail: fused 2, binary: 1.
In ODIN, I get the following:
<ID:0/003> 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/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)
Can someone please help me? I'm getting kind of desperate.
Have you tried another USB cable?.
I have actually. The original cable and just another one I had. Also, tried it on 3 computers.
Should I be loading a PIT file? some places say to do it and others say not to.
marcymtz92 said:
Should I be loading a PIT file? some places say to do it and others say not to.
Click to expand...
Click to collapse
The problem is you're trying to flash mdl firmware and you're not on that version. It looks like you're on mf3. There is no Odin flashable mf3 firmware so I'd suggest you flash the nb1 tar file. See the general forum for the file. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
You are freaking amazing. That file totally worked. Thanks so much.
marcymtz92 said:
You are freaking amazing. That file totally worked. Thanks so much.
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app

SM-G900T (Tmobile) tried rooting and now wont boot! HELP PLEASE!

I followed the guide here:
http://www.tomsguide.com/us/samsung-galaxy-s5-guide,review-2821-4.html
and used Odin and according to Odin3.07 everything should have gone right, but now my phone will not boot!
Please help.
I just wanted to root it to remove tmobile bloatware and now I don't have a phone.
I think the problem is that I recently updated to Tmobiles newest OTA update (maybe 5.11??) and I am guessing that this root does not work with it.
How can I get this sucker back up and running?
Please help!
Here is the output from Odin (log)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltetmo-kltetmo-smg900t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
So no download mode ? or Recovery? Not booting as in? you hold the buttons and the phone does not start?
Do you feel a vibration?
epeglab said:
So no download mode ? or Recovery? Not booting as in? you hold the buttons and the phone does not start?
Do you feel a vibration?
Click to expand...
Click to collapse
I can get into download mode and recovery mode, I just don't know what to do.
Just download the latest stock firmware and flash using odin on download mode.
http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
Make sure that you understand which version (you should flash the same one you were currently using ) you flash and follow the steps word for word.
EDIT: Keep the cable plugged into the computer until you have reached the boot animation. (just to be safe )
EDIT 2: you might get a boot loop so just format and clear cache. (you could probably get away with clearing the cache)
You the man!
I was downloading a firmware from SamMobile, but it was going to take 6 hours to get. Your link was only 30 minutes, and now my phone is back to its original state!
Sucks that I am not rooted (not sure if you can root 5.11) but I am sooooooooooo glad to have my phone back.
YES
Thanks!!
JohnPrime said:
You the man!
I was downloading a firmware from SamMobile, but it was going to take 6 hours to get. Your link was only 30 minutes, and now my phone is back to its original state!
Sucks that I am not rooted (not sure if you can root 5.11) but I am sooooooooooo glad to have my phone back.
YES
Thanks!!
Click to expand...
Click to collapse
You can root 5.1.1. Though you have to have a patched kernel (G900W8). I usually just flash the recovery and move to different Roms.
Sent from my SM-G900W8 using Tapatalk

Asking again for some help! I've spent 30 - 40 hours on this and getting nowhere :(

I've searched the heck outta this - and tried everything. I simply don't understand why I am getting nowhere. There is some fundamental thing I must be doing wrong but I don't know what.. I am sure that minds superior to mine can fix this.... I just need someone to take pity on me....
The phone is a SM-N900W8 (Bell Canada) that was completely stock running Android 5. After a battery pull, I got Set Warranty Bit : kernel error. Or if I try to get to recovery I get Set warranty Bit : recovery. I 'should' be able to flash stock ROM and fix, correct? Well, flashing stock ROM does not work. I tried flashing a TWRP too. Nothing. I tried flashing just a recovery or a boot, even tried flashing a N900T version (I read that works on my model too). I've tried latest Odin (3.13) or earlier versions (esp. 3.09, or 3.10). Nothing. It shows a pass in ODIN, but it's still not getting past these warranty bit errors. I can not get to any recovery...
The phone remains undaunted by my feeble attempts.
I'm using the original Samsung USB cable, attached to my motherboard ports (tried different ones too) and the ODIN downloads appear to load (I get the blue bar that increases across the screen). It reboots and then we're back to the error.
I have NOT tried ticking the re-partition box - is that the way to go? Isn't there a pit file contained in the stock ROM?
Should I be trying to flash using an image on the SD card?
Help me Obi-wan....
Here's a fix to where you are
I have exact same model and was where you are
Step 1 remove battery
Step 2 hold home button power button volume button
Step 3 continue holding all 3 buttons and put battery back in voila you get to recovery
Eastcoastguido said:
I have exact same model and was where you are
Step 1 remove battery
Step 2 hold home button power button volume button
Step 3 continue holding all 3 buttons and put battery back in voila you get to recovery
Click to expand...
Click to collapse
Thanks for the reply. I have tried what you suggest - device will not boot into recovery. It says Recovery booting at top of screen followed by Set Warranty Bit: recovery....
askelly35 said:
Thanks for the reply. I have tried what you suggest - device will not boot into recovery. It says Recovery booting at top of screen followed by Set Warranty Bit: recovery....
Click to expand...
Click to collapse
Try this :
- Turn off the phone.
- Enter Download mode.
- At the first download mode screen where it says you can press Volume-down to boot normally, press volume-down to boot normally.
Does Odin show any error message ??
JJEgan said:
Does Odin show any error message ??
Click to expand...
Click to collapse
ODIN shows a pass...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2303 M
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I have now read about a eMMC Chip failure issue... maybe this is the problem?
That tends to read in Odin as Nand Write Fail .
Did it successfully flash twrp?
audit13 said:
Did it successfully flash twrp?
Click to expand...
Click to collapse
No it did not.
I have not tried to re-partition (the box has not been ticked in ODIN) - would that be something worth trying?
No not without be 100% prepared for dead phone.
Repartition you really need to know what you are doing with PIT etc.
askelly35 said:
No it did not.
I have not tried to re-partition (the box has not been ticked in ODIN) - would that be something worth trying?
Click to expand...
Click to collapse
What is the Odin error in the log window when you try to flash Odin?
You are flashing the latest stock ROM from sammobile.com in Odin?
audit13 said:
What is the Odin error in the log window when you try to flash Odin?
You are flashing the latest stock ROM from sammobile.com in Odin?
Click to expand...
Click to collapse
There was no ODIN error - it said "pass".
I was using the latest stock ROM from sammobile.com (bell Canada version for Ontario).
Try flashing again with a pit file. Without a pit file, you won't be able to re-partition.

Categories

Resources