I don't seem to be able to Odin stock OB7 or stock NK2. When I attempt to Odin either I get this on Odin:
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and get this on the download screen:
UDC START
SW REV CHECK FAIL : [tz]Fused 3>Binary 1
[4]eMMC write fail: TZ
Right now I'm running HYBRID_OB7sbl_SPT_N910PVPU4COG5 unrooted. Any potential help with what I've done would be great. Thanks guys.
Cant go back. Period.
Sent from my SM-N910P using Tapatalk
I have the same problem. Updated the phone with the latest from Sprint / Samsung, then tried to root and got into a boot loop. I can get into download mode and recovery. Trying to flash a ROM with CWM recovery fails too.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Read frezzas stockish thread.
Sent from my SM-N910P using Tapatalk
It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.
After blowing nearly an entire day....
To start off my phone was stock / rooted, I then installed the latest update via Kies (OE1, wanted the Stagefreight patch) and attempted to re-root my phone which I then found was stuck in a boot loop. I got lazy, updates had been going well on the Note 4 and I failed to come to XDA to see if there were any problems rooting it, turns out there is :crying: and I couldn't get Kies to recover it, and factory reset didn't work either. To recover I tried to use ODIN to flash OB7 and received the above results, I tried a few other stock ROMs and got the same problem.
At this point I was about ready to chuck my phone out the door until I noticed a comment saying that once you flash OE1 you can't go back and the only option is to flash an AOSP ROM such as Notirized. I downloaded Notorized, following the OP directions step by step and I now have my phone back! So far I like this ROM, so maybe this was fate
http://forum.xda-developers.com/not...-noterized-rom-super-speedy-reliable-t3099382
Thanks XDA! Now if I only had come here first and saved myself an entire day of grief! (Took away from my time playing Elite Dangerous! lol).
Thanks man. I appreciate the response and the explanation. I thought it was an issue with the bootloader, but I was confused about what I had done. I did wind up wiping everything clean and flashing your custom OB7/OG5 rom tar. Thanks for putting that together. I definitely should have updated everything sooner. I appreciate the advice on the OG5 bootloader as well. Have a great weekend.
tx_dbs_tx said:
It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.
Click to expand...
Click to collapse
Related
I had encryption on my phone due to company emails. I flashed bootloader and modem to 4.3 (I747UCUEMJB) in order to enjoy the latest custom ROMs.
However, after installing 5-6 of custom ROMs, I am always asked to "enter your PIN or password to encrypt the memory". No matter what I enter, the phone always restarts and goes back to the prompt asking me to enter PIN or password.
I did factory reset and cache/etc. wipes every time I flash. I thought encryption should be erased by those resets/wipes. BTW - I use TWRP as recovery.
What I would like to know, is there a way for me to get a stock 4.3 ROM to install using ODIN? Hopefully that will also install the stock recovery, which may be able to help me really do a clean factory reset/data wipe.
Any thoughts? Thanks.
You can find pre rooted stock rom from herehttp://forum.xda-developers.com/showthread.php?t=1739426
hope that helps
BTW, I have tried using ODIN to get back to 4.1.2: I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar file.
However, ODIN is giving "Fail (Auth)" errors. I suppose this is because I have flashed the bootloader and modem to a much higher version and there is no way to go back?
Harsh99132 said:
You can find pre rooted stock rom from herehttp://forum.xda-developers.com/showthread.php?t=1739426
hope that helps
Click to expand...
Click to collapse
Nope. these I747ATTDLK3 images won't work because once you flash these new 4.3 bootloader (I747UCUEMJB), you cannot go back to early stock ROMs. The only way is to find the 4.3 stock ROMs for ODIN, which is no where to find on the internet.
Here is the error from ODIN when I tried the I747ATTDLK3 image:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have run KK ROMs with a stock 4.1.2 bootloader with no problems at all. Updating to 4.3 isn't necessary in my opinion.
AT&T never released a stock 4.3 ROM that can be flashed via Odin. AT&T released 4.3 as an OTA update.
At this point, you may be better off flashing a custom recovery such as Philz Touch and flash a KK ROM.
audit13 said:
I have run KK ROMs with a stock 4.1.2 bootloader with no problems at all. Updating to 4.3 isn't necessary in my opinion.
AT&T never released a stock 4.3 ROM that can be flashed via Odin. AT&T released 4.3 as an OTA update.
At this point, you may be better off flashing a custom recovery such as Philz Touch and flash a KK ROM.
Click to expand...
Click to collapse
Wow. CWM recovery (Philz Touch) + CyanogenMod 10 Nightly Builds for SGH-I747 solved my problem! I can finally use my phone now!
Thank you so much!
zhangla said:
Wow. CWM recovery (Philz Touch) + CyanogenMod 10 Nightly Builds for SGH-I747 solved my problem! I can finally use my phone now!
Thank you so much!
Click to expand...
Click to collapse
That's great. Why stop at CM10? Try some 4.4.2-based ROMs like Cyanfox or Valiudus. Both are great and I love the dark theme for Validus.
Need to warranty my Note 3 due to hardware camera problem. I unlocked my factory 4.3 bootloader, installed TWRP, and went to W03 Slim 8.5. I have never ran the official 4.4.2 update which I believe implies my bootloader is still the 4.3 version.
I launched ODIN 3.07, and flashed the N900TUVUBMI7 rom from this page: AndroidRootz
Everything appears to have ran in ODIN successfully:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The phone boots up with no warnings on the Samsung splash and then gets to the white T-Mobile 4G LTE splash and just hangs there. I've tried reflashing the firmware from ODIN with the same result.
What should I do? Should I flash up to the 4.4.2 version? The phone is going back regardless so I don't care about anything other than getting this to boot up so I can exchange it.
Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.
negativefx said:
Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.
Click to expand...
Click to collapse
Try wiping /data or a factory reset in recovery.
Have you tried re-downloading the 4.3 firmware. Sometimes this can happen from a bad download.
Shawn said:
Try wiping /data or a factory reset in recovery.
Click to expand...
Click to collapse
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!
happened to almost everyone, I had to odin v3.09 and run 2 times... the 1st time it said it was successful, but stuck at the Samsung screen, the 2nd time booted up just fine..
on my link I have odin and the new firmware, old firmware my stock not rooted roms... all u need for my stock not rooted is chainfire superuser app, then download busybox, your done,
look on my signature for any files needed, also uploading the Samsung driver.. no kies needed.
negativefx said:
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!
Click to expand...
Click to collapse
No problem, I used to forget to wipe when I put my phones back to stock with Odin.
I'm currently running an AOSP rom 4.4.2...what are the steps to flash the 4.3 stock rom touchwiz??
4.4.2 is out? newest firmware available atm is nk3 4.4.2
anyway
1. d/l firmware file from sammobile.com
2. boot to download mode
3. run odin and plug phone into pc(if you have a mac your on your own from here as i have a pc and not a mac)
4. load file you just d/led(in tar.md5 format) into the pda slot(i'm assuming you have odin 3.07)
5. click start and wait to profit.
you can also d/l 4.3 firmware from same site if you really want it.
good luck
I meant I have a AOSP custom rom its regular google not touchwiz
Sent from my SM-N900T
right. thats how you restore stock touchwiz though. it's pretty simple.
will I lose root?..so if I have this current baseband which is MI7..does that mean that I still have 4.3 bootloader?
Sent from my SM-N900T
yeah you will lose root. but you can reroot it afterwards. and yes if you flash the 4.3 firmware it'll keep the 4.3 bootloader or should anyway. might want to wait on someone else to chime in here on the bootloader and baseband though as i am not really sure. i just upgraded from a note 2 to my note 3. and i run nk3 on my note 3. it's fine with all the roms i have tryed so far though. no issues at all.
I'll wait a lil bit cause someone just told me that since I'm on 4.4.2 custom aosp rom I won't be able to revert back to 4.3 Touch wiz
Sent from my SM-N900T
i'd just go with the nk3 firmware. it's 4.4.2 stock touchwiz. works great. but thats me. hehe
this is my android version and that is my baseband..im soo confused
View attachment 3079890
Sent from my SM-N900T
ok. your baseband and bootloader are 4.3, but your custom rom is a 4.4.2 rom. if you install the nk3 firmware. you'll have stock touchwiz 4.4.2 with the nk3 baseband and bootloader along with the csc file. and a bunch of otherstuff. it will all be upgraded. instead of having a custom 4.4.2 rom you'll be on the newest stock touchwiz version which is nk3.
nk3 can be rooted. you can install a custom recovery and still reinstall custom roms.
if that makes sense.
that's wat I was looking for, thanks dude..this is my version of ODIN that I have..this is what I used to root the phone when I first got it last year
View attachment 3079899
Sent from my SM-N900T
1.8.5 will work. been so long since i seen that version. just add the tar.md5 file to the pda slot. click start and profit
is it better to upgrade ODIN to tge latest version or just stick with 1.85?
Sent from my SM-N900T
I'm running stock bootloader from launch when I got the phone in 2013. Currently running 4.4.2 updated via Mexican firmware leak back in early spring. I need to update to NF4 bootloader. I keep getting error in Odin when I try to flash NF4. Do I need to be on NF1 before I can flash NF4?
re: baseband
llsektorll said:
I'm running stock bootloader from launch when I got the phone in 2013. Currently running 4.4.2 updated via Mexican firmware leak back in early spring. I need to update to NF4 bootloader. I keep getting error in Odin when I try to flash NF4. Do I need to be on NF1 before I can flash NF4?
Click to expand...
Click to collapse
You don't need to be on NF1 or any other baseband version in order to update
to the NF4 baseband.
Here is the direct download link for ODIN in case you need it, this version works
best for me: https://dl.dropboxusercontent.com/u/45687485/Odin85.zip
Be sure you have the latest Samsung USB driver installed which can be found here:
http://tinyurl.com/nlnegmj and be sure to use the original samsung usb cable which
came with your phone for best results.
Good luck!
Misterjunky said:
You don't need to be on NF1 or any other baseband version in order to update
to the NF4 baseband.
Here is the direct download link for ODIN in case you need it, this version works
best for me: https://dl.dropboxusercontent.com/u/45687485/Odin85.zip
Be sure you have the latest Samsung USB driver installed which can be found here:
http://tinyurl.com/nlnegmj and be sure to use the original samsung usb cable which
came with your phone for best results.
Good luck!
Click to expand...
Click to collapse
Thanks I'll try right now. I was using 3.09 which may be causing a problem.
Edit:
I'm getting the following error.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_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)
Click to expand...
Click to collapse
I'm using the N900W (Canadian). Not the N900T. I futhermore I can flash the Canadian Firmware NB7 with no issues.
I had Cynagenmod 4.4.4 on my S4. I wanted to unroot it as the release is buggy. So I went to a link on how to unroot at S4 phones and followed the steps and now I cant get it to unroot and its now stuck in a boot loop. I have tried ODIN multiple times and this is what I get.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Removed!!
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. My phone is a paperweight right now.
Its also giving me a check fail on the phone itself.
Start [224,1140]
SW Rev. Check Fail: 4, Binary : 1
Snakedoktor said:
Its also giving me a check fail on the phone itself.
Start [224,1140]
SW Rev. Check Fail: 4, Binary : 1
Click to expand...
Click to collapse
Your trying to flash the wrong firmware? What was your phone BEFORE you rooted? 4.2.2? 4.3?
The Sickness said:
Your trying to flash the wrong firmware? What was your phone BEFORE you rooted? 4.2.2? 4.3?
Click to expand...
Click to collapse
It was December of last year. I dont honestly remember. I know I was at 4.4.4 when it was rooted. Just looked it up November of last year was 4.3
Snakedoktor said:
It was December of last year. I dont honestly remember. I know I ad 4.4.4 when it was rooted.
Click to expand...
Click to collapse
If you got it in Dec then it was 4.3. If it was 4.4.4 when you rooted meant you took a OTA?
The Sickness said:
If you got it in Dec then it was 4.3. If it was 4.4.4 when you rooted meant you took a OTA?
Click to expand...
Click to collapse
It was an update via cynogen mod that updated it to 4.4.4. It does look like it had 4.3 like you said. Did I download the wrong file?
Snakedoktor said:
It was an update via cynogen mod that updated it to 4.4.4. It does look like it had 4.3 like you said. Did I download the wrong file?
Click to expand...
Click to collapse
Yes you DL the wrong file. Im not too familar with Cynogen. So if it did update you to 4.4.4, you need to Odin the Official 4.4.4 Firmware
Cyanogen 4.4.4 won't require you to flash stock 4.4.4 because it does not update firmware If you had official 4.3 firmware when you flashed cm then you need to flash at least 4.3 firmware. That's why you are getting the error, you were trying to flash 4.2.2. You have the option of flashing 4.3 MK2, 4.4.2 NB4, or 4.4.4 NH7. You might as well flash NH7
One other thought: Just because the CM you are running has some bugs, perhaps another ROM would be a better experience than the bloated Samsung stock.
I'm very happy on Dirty Unicorns, but I've been thinking to try a very basic Slimkat or something like that, then theme it with Themer, and add any apps/functions needed.
Maybe something like that would work for you?
Marc
Anyone know how to do this? I thought it would be simple..just flash the stock firmware from Odin while in download mode. However when I tried that, Odin failed to flash the firmware for some reason. I'm on P600 with CM12 by Rayman.
C2Q said:
Anyone know how to do this? I thought it would be simple..just flash the stock firmware from Odin while in download mode. However when I tried that, Odin failed to flash the firmware for some reason. I'm on P600 with CM12 by Rayman.
Click to expand...
Click to collapse
Try flashing with another odin version, if you are on 3.09 try with 3.07, happened to me before & 3.07 did the trick
lsherif said:
Try flashing with another odin version, if you are on 3.09 try with 3.07, happened to me before & 3.07 did the trick
Click to expand...
Click to collapse
I tried with ODIN 3.07 and it's still failing
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Nevermind I think it was the firmware. I downloaded a newer firmware and it started flashing.