Related
Here's the error I get:
Code:
<ID:0/007> Added!!
<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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.
bump
Try downloading the file again. I would also try another usb slot or even pc
Sent from my SAMSUNG-SGH-I747M
mymusicathome said:
Try downloading the file again. I would also try another usb slot or even pc
Sent from my SAMSUNG-SGH-I747M
Click to expand...
Click to collapse
Just tried it again. It keeps failing at sbl2.mbn it seems.
If it means anything, I just noticed in download mode it says
Code:
SECURE CHECK FAIL : sbl2
SevKempf said:
Here's the error I get:
Code:
<ID:0/007> Added!!
<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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.
Click to expand...
Click to collapse
I may be wrong but I don't think you can flash the stock ATT ROM on a Rogers device and vice versa. Also, the ATT ROM contains a different modem that may not work well for us on Rogers. Your best bet is to keep the ATT ROM and freeze/delete the bloatware using Titanium Backup Pro and flash the Rogers modem.
Or run a custom ROM.
Tony_YYZ said:
I may be wrong but I don't think you can flash the stock ATT ROM on a Rogers device and vice versa. Also, the ATT ROM contains a different modem that may not work well for us on Rogers. Your best bet is to keep the ATT ROM and freeze/delete the bloatware using Titanium Backup Pro and flash the Rogers modem.
Or run a custom ROM.
Click to expand...
Click to collapse
Yeah, I'm currently running CM10 but I find it has WAY too many bugs for me to use it, things constantly crashing, graphical glitches. The LED doesn't light up for anything except charging.
I originally did use TiBa to delete the bloat, no problem. Except AT&T replaces the Address Book with their own version the "AT&T Address Book" which syncs with some AT&T server every time I open it, super annoying.
Then why not try using one of the custom ICS/JB stock-based ROMs? As he said, i'm pretty sure it's impossible to flash a Rogers ROM on an AT&T device.
And.... which build of CM10 are you using? You could always try Task & Ktoonsez CM10-based ROM. Never experience a graphical glitch (though, i never did even on older CM10 builds, either), hardly ever have anything crash..... and as far as i'm aware, even in stock CM10, you actually have to go into the settings or find an app and manually set up the notification LED colors and what they blink for.
elementaldragon said:
Then why not try using one of the custom ICS/JB stock-based ROMs? As he said, i'm pretty sure it's impossible to flash a Rogers ROM on an AT&T device.
Click to expand...
Click to collapse
Where can I find one of these ROMs? I've searched for them but I haven't found anything. I asked someone and they suggested an AOSP, but I wasn't able to find any, so I used a AOKP ROM and when I booted the phone all that displayed was some 8bit looking gradient from Yellow to Purple, got worried and rebooted my phone and reinstalled Cyanogenmod.
elementaldragon said:
And.... which build of CM10 are you using? You could always try Task & Ktoonsez CM10-based ROM. Never experience a graphical glitch (though, i never did even on older CM10 builds, either), hardly ever have anything crash..... and as far as i'm aware, even in stock CM10, you actually have to go into the settings or find an app and manually set up the notification LED colors and what they blink for.
Click to expand...
Click to collapse
I installed Cyanogenmod from the ROM Manager app. This ROM, specifically.
Also, when I install a ROM, can I do it from CWM? Or do I need to install using Odin?
SevKempf said:
Where can I find one of these ROMs? I've searched for them but I haven't found anything. I asked someone and they suggested an AOSP, but I wasn't able to find any, so I used a AOKP ROM and when I booted the phone all that displayed was some 8bit looking gradient from Yellow to Purple, got worried and rebooted my phone and reinstalled Cyanogenmod.
I installed Cyanogenmod from the ROM Manager app. This ROM, specifically.
Also, when I install a ROM, can I do it from CWM? Or do I need to install using Odin?
Click to expand...
Click to collapse
That link you provided shows that it points to a Galaxy S2 ROM in the url. The link itself didn't work though when i clicked on it.
Try this ROM: http://forum.xda-developers.com/showthread.php?t=1766684
I wonder if the problem you're having is related to the build.prop
ATT have a device model name d2att while the Canadian variants have device model name d2can.
Search the forums add I think I've read something about that.
Also, even though you want to flash a Rogers Rom, make sure you use an ATT modem.
Sent from my SGH-I747M using xda premium
what can be error sbl2.mbn than use Odin ?
i try use other usb port in notebook, any versions Odin (v. 1.85; 3.4; 3.7), reinstalling the USB drivers and use stock SGS3 USB but problem steel be
Thanks
Definitely try out Task650's AOKP rom, Its very stable and has very few (if any) bugs.
nate_benji said:
Definitely try out Task650's AOKP rom, Its very stable and has very few (if any) bugs.
Click to expand...
Click to collapse
i'm use Task650's AOKP rom at that moment, but they are not support extSdCard 64Gb and then i'm try upload stok JB 4.1.1. from Odin i recive a fail massage i think truble in sbl2.mbn
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MVLDLK4_I747MOYCDLK4_538866_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl2.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tybalt said:
Also, even though you want to flash a Rogers Rom, make sure you use an ATT modem.
Click to expand...
Click to collapse
Are you suggesting that I download both stock ROMs, extract them, then do a simultaneous mix and match of the parts in ODIN?
I have the AT&T i747 but want to have the reduced Rogers bloatware.
Anonymously_Unknown said:
Are you suggesting that I download both stock ROMs, extract them, then do a simultaneous mix and match of the parts in ODIN?
I have the AT&T i747 but want to have the reduced Rogers bloatware.
Click to expand...
Click to collapse
No, just get a cwm recovery and flash a AT&T modem.
Also, there's a unbloated AT&T stock ROM, why go for Rogers?
Go to twrp or cwm website and get the recovery for d2can instead of d2att. I'm not sure but it could be the source of your issue.
Sent from my SGH-I747 using xda app-developers app
Im having similar problem and need help too
I also have this secure check fail:sbl2 problem, but what I did was diffident. installed ParanoidKangDroid custom rom and then i realized that i use allshare play from stock rom pretty much so i decided to put back to stock my GS3. I used odin 3.0.7 to do that. I download the original stock rom from sammobile exactly the puerto rico version (were i live), but as i said it gives me the sbl2 fail problem.
---------- Post added at 05:19 AM ---------- Previous post was at 05:07 AM ----------
As you see Im a noobie here and I have another question. I like ParanoidKangDroid in my device but cant install allshare play so th question is: If i flash the [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][4/6/2013] KT747 - LJ7 - KTweaker, Can I install allshare play then? if yes what do i need to install it. Is there any other 4.2.2 rom that i can use the kernel mentioned above? or is there any rom which has touchwiz integrated?
sycol65 said:
but as i said it gives me the sbl2 fail problem.
Click to expand...
Click to collapse
I had downloaded the one from the stock firmware page and flashed it with the custom recovery to eliminate that issue. What you are experiencing is a bootloader mismatch.
Can you explain me the correct entire process to do that?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
slb2.mbn error, fail
SevKempf said:
Here's the error I get:
Code:
<ID:0/007> Added!!
<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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.
Click to expand...
Click to collapse
This error is caused because a BAD USB CABLE. Please, use an original Samsung GGalaxy Cable. I had that problem with my GT-I9195. Fortunatelly it's working again.
The symptom was that i couldn't copy files from my computer to my smartphone.
I have been running a rooted version of 4.3 (UCUBMK6) with TWRP recovery for some time, and want to do the OTA update to Kitkat. So I'll need to bring it back to stock first. I ran TriangleAway and rebooted to download mode afterward. Then I followed THIS guide to flash back to stock ROM 4.2.1 "KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5".
I tried several times with Odin 3.07, but every time it fails:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I then went back into download mode and flashed the rooted UCUBMK6 ROM, which works just fine (and also took it back from TWRP to stock recovery).
Does anyone have any idea how I can get it back to a stock, unrooted ROM, so that I can run OTA? Thx!
mobidutch said:
I have been running a rooted version of 4.3 (UCUBMK6) with TWRP recovery for some time, and want to do the OTA update to Kitkat. So I'll need to bring it back to stock first. I ran TriangleAway and rebooted to download mode afterward. Then I followed THIS guide to flash back to stock ROM 4.2.1 "KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5".
I tried several times with Odin 3.07, but every time it fails:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I then went back into download mode and flashed the rooted UCUBMK6 ROM, which works just fine (and also took it back from TWRP to stock recovery).
Does anyone have any idea how I can get it back to a stock, unrooted ROM, so that I can run OTA? Thx!
Click to expand...
Click to collapse
what bootloader are you running , also this ( http://forum.xda-developers.com/showthread.php?t=2589891 ) is a great thread and may help you make sure u read second or third post i dont remember witch . also ( http://forum.xda-developers.com/showthread.php?t=2581321 )
I tried to do the same for the update to kk. 3.09 said pass but bootlooped. Had to use 1.85, now on kk. Good luck.
Sent from my Note 3...making all others drool!
mobidutch said:
I have been running a rooted version of 4.3 (UCUBMK6) with TWRP recovery for some time, and want to do the OTA update to Kitkat. So I'll need to bring it back to stock first. I ran TriangleAway and rebooted to download mode afterward. Then I followed THIS guide to flash back to stock ROM 4.2.1 "KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5".
I tried several times with Odin 3.07, but every time it fails:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I then went back into download mode and flashed the rooted UCUBMK6 ROM, which works just fine (and also took it back from TWRP to stock recovery).
Does anyone have any idea how I can get it back to a stock, unrooted ROM, so that I can run OTA? Thx!
Click to expand...
Click to collapse
Follow this. http://forum.xda-developers.com/show....php?t=2618447 .
I followed sections all sections 1 threw 3. At section 2 the link for the I317UCUBMK6-TZ-PARAM.zip did not work. I used this link instead.
http://www56.zippyshare.com/v/16559598/file.html
At section 3 don't be alarmed when it says it's downloading the update but it doesn't show percentages. It is downloading. In fact for me it automatically downloaded the 4.4.2 update instead of 4.3. It skipped it and went straight to kitkat. It took some time but I have Official KItkat 4.4.2.
Hit Thanks
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------
djbrian52 said:
I tried to do the same for the update to kk. 3.09 said pass but bootlooped. Had to use 1.85, now on kk. Good luck.
Sent from my Note 3...making all others drool!
Click to expand...
Click to collapse
Whate are you talkin about 1.85? Instead of 3.09?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
You mentioned that you used Odin 3.07. I used 3.09 with no success. Had to use version 1.85.
Sent from my Note 3...making all others drool!
djbrian52 said:
You mentioned that you used Odin 3.07. I used 3.09 with no success. Had to use version 1.85.
Sent from my Note 3...making all others drool!
Click to expand...
Click to collapse
Lol i didnt even know 3.09 was out i just have it saved on my pc & just always use 3.07 works perfect
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
help me pls
06SilveradoZ71 said:
Follow this. http://forum.xda-developers.com/show....php?t=2618447 .
I followed sections all sections 1 threw 3. At section 2 the link for the I317UCUBMK6-TZ-PARAM.zip did not work. I used this link instead.
http://www56.zippyshare.com/v/16559598/file.html
At section 3 don't be alarmed when it says it's downloading the update but it doesn't show percentages. It is downloading. In fact for me it automatically downloaded the 4.4.2 update instead of 4.3. It skipped it and went straight to kitkat. It took some time but I have Official KItkat 4.4.2.
Hit Thanks
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
[SIZE=hi, my note 2 i317 got stuck on samsung logo & cnt get it to recovery mode. as i told that i need to flash the param files but the files that is link on the thread doesn't work. & you mention about the link that works. well i click it & it says files doesnt exist. do you think you can help me find a link or if you have the files that i needed. thank you so much
Click to expand...
Click to collapse
I've not touched my phone in over a year (at least it seems that way)
I'm on an older version on Android (4.1.2) and baseband MD4
What do i need to flash one of these new roms? I haven't flashed or checked up on roms etc in a long time. So i'm kind of lost with all this new ND8 stuff.
Any help would be great, as to what i need to do in order to flash a newer rom.
zookeeper525 said:
I've not touched my phone in over a year (at least it seems that way)
I'm on an older version on Android (4.1.2) and baseband MD4
What do i need to flash one of these new roms? I haven't flashed or checked up on roms etc in a long time. So i'm kind of lost with all this new ND8 stuff.
Any help would be great, as to what i need to do in order to flash a newer rom.
Click to expand...
Click to collapse
Ignore the ND8 stuff, as that is indicitive of a newer modem and bootloader, and you would be getting yourself deep into Samsung KNOX territory. If you don't know what KNOX is, there's plenty of info on it here on XDA and on the web. All I can say is be careful with KNOX.
If you flash PhilZ recovery via ODIN and your ROM of choice and GAPPs via PhilZ, you shouls be good to go.
PhilZ DL link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
.MD5 files are for ODIN, .zip files are for later updating the recovery within the recovery.
GAPPs DL link:
http://paranoidandroid.co/gapps/
Higgs_Boson said:
Ignore the ND8 stuff, as that is indicitive of a newer modem and bootloader, and you would be getting yourself deep into Samsung KNOX territory. If you don't know what KNOX is, there's plenty of info on it here on XDA and on the web. All I can say is be careful with KNOX.
If you flash PhilZ recovery via ODIN and your ROM of choice and GAPPs via PhilZ, you shouls be good to go.
PhilZ DL link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
.MD5 files are for ODIN, .zip files are for later updating the recovery within the recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2768483
that is the rom that i'm looking to flash. It says that i need to be on ND8 or it will brick my phone. So do i need to flash a stock ND8 rom or something with the philz touch recovery?
Is there a tutorial some where for flashing PhilZ? I don't really remember how to use ODIN.
zookeeper525 said:
http://forum.xda-developers.com/showthread.php?t=2768483
that is the rom that i'm looking to flash. It says that i need to be on ND8 or it will brick my phone. So do i need to flash a stock ND8 rom or something with the philz touch recovery?
Is there a tutorial some where for flashing PhilZ? I don't really remember how to use ODIN.
Click to expand...
Click to collapse
If you have your sights on that ROM, I encourage you to read that thread's original post carefully.
There is a link where you should direct your questions regarding that ROM.
As for using ODIN, it's quite simple. Just download it and run the program from the folder directly (no installation required). Choose "PDA", find the recovery file (.MD5), and press start.
If the recovery doesn't stick, you may have to uncheck the "auto-reboot". Retry the flashing process. Once finished (should read "PASS" in green), unplug the USB remove the battery, re-insert the battery while holding Power+Vol UP+Home. That should take you into PhilZ.
Higgs_Boson said:
If you have your sights on that ROM, I encourage you to read that thread's original post carefully.
There is a link where you should direct your questions regarding that ROM.
As for using ODIN, it's quite simple. Just download it and run the program from the folder directly (no installation required). Choose "PDA", find the recovery file (.MD5), and press start.
If the recovery doesn't stick, you may have to uncheck the "auto-reboot". Retry the flashing process. Once finished (should read "PASS" in green), unplug the USB remove the battery, re-insert the battery while holding Power+Vol UP+Home. That should take you into PhilZ.
Click to expand...
Click to collapse
What version of ODIN are you using? I got "Odin-v3-09" off google and there doesn't seem to be a "PDA" option.
zookeeper525 said:
What version of ODIN are you using? I got "Odin-v3-09" off google and there doesn't seem to be a "PDA" option.
Click to expand...
Click to collapse
I use 3.07, but the "AP" option will flash it for you.
Higgs_Boson said:
I use 3.07, but the "AP" option will flash it for you.
Click to expand...
Click to collapse
Do i have to boot into download mode or something to flash the recovery?
If i just have my phone on this is all it does
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.25.0-d2lte.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..
I'm not sure what i'm doing wrong.
Yes, boot into Download Mode. Power+Vol Down+Home.
Higgs_Boson said:
Yes, boot into Download Mode. Power+Vol Down+Home.
Click to expand...
Click to collapse
Hm, it connected to the phone that time, but it failed.
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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Would it be better if i just flash a stock ND8 rom and then reflash the phone?
zookeeper525 said:
Hm, it connected to the phone that time, but it failed.
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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Would it be better if i just flash a stock ND8 rom and then reflash the phone?
Click to expand...
Click to collapse
Try ODIN 3.07 and use the PDA option. Not sure if that'll help, but give it a go.
The ND8 works great for some, and others dont like it. Personally id flash ND8 as i get better LTE signal with it. After ND8 boots flash philz recovery in odin 3.07 like he suggested.. go back to recovery and root with the philz option, under the "advanced" menu i believe, and install supersu on the stock rom. Run supersu and it will prompt you to disable knox, just hit yes. Then update to your rom of choice.
Sent from my SPH-L710 using XDA Free mobile app
Higgs_Boson said:
Try ODIN 3.07 and use the PDA option. Not sure if that'll help, but give it a go.
Click to expand...
Click to collapse
Thanks for the help. I ended up just flashing the stock ND8 run and reflashing using Auto-Root or w/e it's called. Then i flashed the "Tribute" rom and it seems to be working great.
Thanks again!
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
i had that nand courrouption thing
I NEED A KERNEL FOR KITKAT
PLEASE
aly ayman said:
i had that nand courrouption thing
I NEED A KERNEL FOR KITKAT
PLEASE
Click to expand...
Click to collapse
you want the stock Kitkat Kernel or boot.img ?
and can you explain what do you mean by nand courrouption thing
kitkat stock kernal to flash it with odin
"NAND rw corruption" as i read
problem is i see SGS4m i9192 and it restart itself- cant flash stock rom or custom recovery - when i try to get in recovery it shows twrp logo and restart
sorry for english
aly ayman said:
kitkat stock kernal to flash it with odin
"NAND rw corruption" as i read
problem is i see SGS4m i9192 and it restart itself- cant flash stock rom or custom recovery - when i try to get in recovery it shows twrp logo and restart
sorry for english
Click to expand...
Click to collapse
i can just provide you the boot.img , it contain the kernel but i dont know how to flash it with ODIN
<ID:0/003> Added!!
<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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
http://imgur.com/a/mQXAd
LOL it accepted an i9190 kernal
now what to do @[email protected]
edit: no , it didn't
aly ayman said:
LOL it accepted an i9190 kernal
now what to do @[email protected]
edit: no , it didn't
Click to expand...
Click to collapse
i think you shouldnt be flashing another model kernel , and i'm sorry i dont know how to help you , i'm not good at this flashing with ODin stuff sorry :/
i discoverd it's my ram
i ruined it by custom rom
Thanks for caring @Hedi.Karray
aly ayman said:
i discoverd it's my ram
i ruined it by custom rom
Thanks for caring @Hedi.Karray
Click to expand...
Click to collapse
what is the custom Rom that ruined it ? can u please tell me ? and how do u know its a ram problem ?