Database Users

[Q] Root Attempt after OTA - ODIN Failed (FAIL! Auth)- Secure Check Fail Cache

This has been a long day...
I previously rooted my N900V Note 3 using the Root_de_la_Vega method. Everything was fine until last night when I stupidly accepted the OTA update from Verizon. I lost root because I forgot to persist Super User. Without thinking I started to reroot using the original Root_de_la_Vega method. The ODIN attempt failed.
This is the message stream from ODIN:
<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)
Also, on the top of my Note 3 it says SECURE CHECK FAIL : cache
My phone will now only boot into ODIN download screen, and gives me the message: "Firmware upgrade encountered as issue. Please use Software Repair Assistant & try again."
My guess is that I have tried to flash/download a mismatched ROM.
Any suggestions on how to get past the ODIN boot screen and back into normal operation?
Any help would be appreciated, obviously...

Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.

NeoMagus said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
Click to expand...
Click to collapse
How/where do I find the PIT file?

http://forum.xda-developers.com/showthread.php?t=2483380

NeoMagus said:
http://forum.xda-developers.com/showthread.php?t=2483380
Click to expand...
Click to collapse
Freak man, thank you so much.
So if I wanted to get root back, I would flash the VRUBMJ7 file, and then go through the de la vega method again?

cmubigguy said:
Freak man, thank you so much.
So if I wanted to get root back, I would flash the VRUBMJ7 file, and then go through the de la vega method again?
Click to expand...
Click to collapse
NO, using the old software with new update will just brick your phone again... Dont do it.
The only root method once on the new update is not condoned by XDA at the moment but if you do some searching youre sure to find it

NeoMagus said:
NO, using the old software with new update will just brick your phone again... Dont do it.
The only root method once on the new update is not condoned by XDA at the moment but if you do some searching youre sure to find it
Click to expand...
Click to collapse
I guess I'll just wait for a safe way to root post-OTA. I can live with no root for a while. Thanks for helping out, I shot you some cash for your time and not making me feel like a complete idiot.

I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note 3

goldy253 said:
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse

goldy253 said:
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note 3
Click to expand...
Click to collapse
I just tried what rhymes with bingo, and it didn't work. It's likely because I just took the OTA straight away without using Kies or unrooting through SU. What was your unroot/re-root method?

I did a full unroot before doing and used it. When it was done it had said it failed (not supported), but supersu had actually been installed and was in the app drawer. Used it to get safestrap installed then flashed the good supersu binary from chainfire's site to get rid of the bad one

NeoMagus said:
I did a full unroot before doing and used it. When it was done it had said it failed (not supported), but supersu had actually been installed and was in the app drawer. Used it to get safestrap installed then flashed the good supersu binary from chainfire's site to get rid of the bad one
Click to expand...
Click to collapse
When I try to flash the updated SuperSU files, I get a "Failed to verify whole file signature" error and it aborts. Thoughts?

cmubigguy said:
When I try to flash the updated SuperSU files, I get a "Failed to verify whole file signature" error and it aborts. Thoughts?
Click to expand...
Click to collapse
Do you have the newest safestrap apk?
http://forum.xda-developers.com/showthread.php?t=2517610
it went thru without an issue for me might be worth posting in that thread

NeoMagus said:
Do you have the newest safestrap apk?
http://forum.xda-developers.com/showthread.php?t=2517610
it went thru without an issue for me might be worth posting in that thread
Click to expand...
Click to collapse
Do now. It turns out I needed to reboot my laptop after I installed Kango.
I'm back rooted!

I wasn't previously rooted. I took the OTA then rooted with bingo. Then installed safe strap with no problems.
Sent from my Galaxy Note 3

NeoMagus said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
Click to expand...
Click to collapse
This worked for me, I flashed the pit for MJ7 and was able to get out of soft brick

Had the same issue, resolved with .pit solution above. Can we include a note in the N900V Root de la Vega instructions? IE: If you have update to Baseband version N900VRUBMJ7, attempting to flash through Odin will fail on cache writing.

I had the exact same problem as OP. Tried to follow steps, kind of got lost.
So, I was able to unbrick the phone using Odin with VZW_32gb.pit. It boots up fine now, I'm still on MJ7. No root. So, how do you get your root back from this point? I can't use safestrap since no root. Kingo doesn't work either -- if my phone is fully booted, it can't connect to it; if I'm in vol-down/home/power mode, Kingo tries, but fails.

kalagula said:
I had the exact same problem as OP. Tried to follow steps, kind of got lost.
So, I was able to unbrick the phone using Odin with VZW_32gb.pit. It boots up fine now, I'm still on MJ7. No root. So, how do you get your root back from this point? I can't use safestrap since no root. Kingo doesn't work either -- if my phone is fully booted, it can't connect to it; if I'm in vol-down/home/power mode, Kingo tries, but fails.
Click to expand...
Click to collapse
After you install Kango, don't enter the download mode, just boot the phone as normal and make sure USB debugging is on. Attach the phone to Kango, and it will download and install the necessary drivers. Once those are done, you can attempt to root, but it likely won't take. Restart your computer, and then reattach the phone. Try to root method again, and it should work. That's what worked for me.

cmubigguy said:
Try to root method again, and it should work.
Click to expand...
Click to collapse
Yeah, mine just sits there for a while, after which it says "ROOT failed! NotSupport". Bummer!
Edit: after 5 tries, it worked. Still got the ROOT failed error, but I did get root! Thanks for your help.

[issue]WiFi Toggle Does not Work

I got my S4 these days. I have flashed XXUAME2 with Odin, rooted the phone, tried MIUI, but was not satisfied. So I restored the backup. Everything was working fina till I installed Adaway and rebooted the phone. Suddenly the wifi was not working anymore. I clicked on the wifi-witch to activate WiFi - no result. Then I rolled back the backup, installed the I9505_XXUEMJ5_MODEM, installed even the "fix". But the wifi still does not work.
Now I just want to have a normal S4 with the original rom, rooted - and working wifi.
What should I do?
Thanks a lot in advance! :highfive:

nalitox said:
I got my S4 these days. I have flashed XXUAME2 with Odin, rooted the phone, tried MIUI, but was not satisfied. So I restored the backup. Everything was working fina till I installed Adaway and rebooted the phone. Suddenly the wifi was not working anymore. I clicked on the wifi-witch to activate WiFi - no result. Then I rolled back the backup, installed the I9505_XXUEMJ5_MODEM, installed even the "fix". But the wifi still does not work.
Now I just want to have a normal S4 with the original rom, rooted - and working wifi.
What should I do?
Thanks a lot in advance! :highfive:
Click to expand...
Click to collapse
Hello mate please download this file and flash it via odin by selecting phone, and Remember to turn it off your phone manually before flashing any modem,If the problem still persist please tell me if your in old bootloader or the new bootloader and will be happy to assist you have a nice day.
To check your bootloader go to download mode and if you have an entry of Knox warranty void then you are having the new bootloader.
If you are having the old bootloader XXUB flash http://www.mediafire.com/download/48r0rgqv25s8968/GSM_Modem_XXUEMFK_and_LTE_Modem_XXUBMH1.rar file with odin by selecting phone.
If you are having the new bootloader XXUD flash http://www.mediafire.com/download/zriv6i5c01lqns6/GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK.rar file with odin by selecting phone.

First, wow, thanks for that fast reply, dude! Ok, I have 0x1, that means, I have to flash the file for the new bootloader, right?
Is there anywhere a mirror? I am in China right now and mediafire is blocked.
Cheers :highfive:

nalitox said:
First, wow, thanks for that fast reply, dude! Ok, I have 0x1, that means, I have to flash the file for the new bootloader, right?
Is there anywhere a mirror? I am in China right now and mediafire is blocked.
Cheers :highfive:
Click to expand...
Click to collapse
Sorry for any delay sir , here's another link inorder for you to download it https://dl.dropboxusercontent.com/u/17236295/MKF_modems_GSM_LTE.tar.md5.zip Credit goes to phil.o for uploading the file , and make sure to thank him here http://forum.xda-developers.com/showthread.php?p=48095149#post48095149as well, have a nice day sir

Alright, thanks. That was a quick download, thanks.
What I did:
1. turned off the phone, removed battery, inserted battery again
2. booted into the download mode
3. flashed the file with odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MKF_modems_GSM_LTE.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<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> 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> 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)
The problem is still there. I cannot turn the Wifi-switch to "ON".
What is causing this problem and what can I do?

nalitox said:
Alright, thanks. That was a quick download, thanks.
What I did:
1. turned off the phone, removed battery, inserted battery again
2. booted into the download mode
3. flashed the file with odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MKF_modems_GSM_LTE.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<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> 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> 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)
The problem is still there. I cannot turn the Wifi-switch to "ON".
What is causing this problem and what can I do?
Click to expand...
Click to collapse
What rom are you using sir? and what kind of recovery do you have? Flash a different kernel. Or do a clean wipe
---------- Post added at 04:00 PM ---------- Previous post was at 03:53 PM ----------
Repulsa said:
What rom are you using sir? and what kind of recovery do you have? Flash a different kernel. Or do a clean wipe
Click to expand...
Click to collapse
Edit: if flashing a different kernel thats not work then I think the only way to fix this would be to flash a complete official stock firmware which you can get it from here http://www.sammobile.com/firmwares/2/ or if you want a pre-rooted you can follow the instruction here.http://forum.xda-developers.com/showthread.php?t=2250824 have a nice day sir and merry christmas to you.

Cool, I saw your edit post. Thanks, dude.
What Firmware should I choose? The phone was bought in Germany from BASE. BASE is using the E-Plus network. But the phone is not branded nor carrier-locked. Should I choose the E-Plus Firmware?
Plus. How to install the Firmware? Just use Odin3 to flash it?

nalitox said:
I prefer a clean wipe. How to do that? Where can I obtain the files?
Click to expand...
Click to collapse
if you want a stock rom from samsung you can go from here http://www.sammobile.com/firmwares/2/ and if you want a pre-rooted rom you can go from here as well http://forum.xda-developers.com/showthread.php?t=2250824 Have a nice day.
Remember to follow any instruction before flashing. you have to flash the firmware via odin and select pda. And flash away. And sorry that i cannot assist you for now because ill be having a dinner with my family and hoping someone will help you to fix this problem if the problem still persist after flashing the stock firmware. Merry christmas to you n your family . And xda community

Ok, understood, thanks.:good:
I want to get a pre-rooted ROM. What version should I pick? I want to have Android 4.3 and (if possible) de-bloated. My Knox is 0x1 and I don't really care about Knox or Knox-related features.
The list here http://forum.xda-developers.com/showthread.php?t=2250824 is very long and complicated. I read through it two times and am not sure what ROM to download.
Can anyone assist, please?
Merry Christmas everyone! :highfive:

nalitox said:
Ok, understood, thanks.:good:
I want to get a pre-rooted ROM. What version should I pick? I want to have Android 4.3 and (if possible) de-bloated. My Knox is 0x1 and I don't really care about Knox or Knox-related features.
The list here http://forum.xda-developers.com/showthread.php?t=2250824 is very long and complicated. I read through it two times and am not sure what ROM to download.
Can anyone assist, please?
Merry Christmas everyone! :highfive:
Click to expand...
Click to collapse
1. Latest version android 4.3 MKE pre-rooted -> HERE
2. For de-bloat it -> HERE

Alright, I have installed this pre rooted version. Wifi works again, thanks.
One annoying issue: everytime I restart the phone, I have to activate Wifi again and re-enter the password.
Edit: Another very annoying issue: I believe that screen is not being dimmed correctly. It is always to dark, even in a very bright enviroment. Plus: the LEDs of both hardware keys are always on when the screen is on.
I just want to have the normal Samsung Stock rooted.
What am I doing wrong?

nalitox said:
Alright, I have installed this pre rooted version. Wifi works again, thanks.
One annoying issue: everytime I restart the phone, I have to activate Wifi again and re-enter the password.
Edit: Another very annoying issue: I believe that screen is not being dimmed correctly. It is always to dark, even in a very bright enviroment. Plus: the LEDs of both hardware keys are always on when the screen is on.
I just want to have the normal Samsung Stock rooted.
What am I doing wrong?
Click to expand...
Click to collapse
If you installed the pre-rooted rom and your having a problem do a factory reset bro phone settings> accounts > backup and reset >Factory reset . Or turnb off your device manually and wait a few sec hold power+volume up the same time and do it there as well, Make sure to use the odin 3.09 when your flashing ..ODIN has problems with flashing latest FW's and if WiFi doesn't work you MUST flash ROM again

Repulsa said:
.ODIN has problems with flashing latest FW's and if WiFi doesn't work you MUST flash ROM again
Click to expand...
Click to collapse
Does this mean that I have to re-flash a new ROM via the recovery?

nalitox said:
Does this mean that I have to re-flash a new ROM via the recovery?
Click to expand...
Click to collapse
No If you download the pre-rooted rom you need to flash it via odin , just like how you flash the stock rom have a nice day.
Edit: if you see a .tar inside of the file means you need to flash it via odin

Understood. Alright, since I don't want to lose all my apps and settings, I decided to flash the Wifi-Fix: XXUEMKE WiFi_FIX
I used Odin to flash this tar.
Unfortunately the Wifi has still the same issue like in the beggining.
Is there an option to flash the wifi fix in the recovery?

nalitox said:
Understood. Alright, since I don't want to lose all my apps and settings, I decided to flash the Wifi-Fix: XXUEMKE WiFi_FIX
I used Odin to flash this tar.
Unfortunately the Wifi has still the same issue like in the beggining.
Is there an option to flash the wifi fix in the recovery?
Click to expand...
Click to collapse
The question is, did u even extract the file you download ? And no you can only flash it via odin and select phone/cp
Sent from my Phone.

Hey, thanks for your help, mate!
Yap, I have extracted the file and flashed the *.tar via odin. Still no result.
Alright, to sum it up. The fix does not work for me. Why? Should I try to flash another Modem?
edit: I really want to have the phone working now. I dont care about other modifications, I just want to have the basic OS rooted. That is all. How to do this?

nalitox said:
Hey, thanks for your help, mate!
Yap, I have extracted the file and flashed the *.tar via odin. Still no result.
Alright, to sum it up. The fix does not work for me. Why? Should I try to flash another Modem?
Click to expand...
Click to collapse
If i have this problem right now,the best thing i will do is either to flash pre-rooted rom or the stock rom if there is any Fc and such . Just turn of your phone the wait a few sec and hold power+volume up in order to reach recovery and do a wipe cache and a factory reset . Hehe
Edit:you already did flash the pre rooted that joku gave u right? Reflash it and follow the step above
Sent from my Phone.

Ok, thanks.
There are no FC at all, just the wifi is the problem.
However, I will flash I9505XXUAME2_MODEM, apply the fix and hope that it will work.
Should I flash modem with odin via "PDA" oder via "PHONE"?
Another question: If I download a pre-rooted ROM and flash it via the recovery, will the new modem be included in the ROM?
Thanks again, mate.
Edit: http://d-h.st/users/DjeMBeY/?fld_id=16262#files
There is no fix for the UAME2. That sucks.

nalitox said:
Ok, thanks.
There are no FC at all, just the wifi is the problem.
However, I will flash I9505XXUAME2_MODEM, apply the fix and hope that it will work.
Should I flash modem with odin via "PDA" oder via "PHONE"?
Another question: If I download a pre-rooted ROM and flash it via the recovery, will the new modem be included in the ROM?
Thanks again, mate.
Click to expand...
Click to collapse
Download odin 3.09 its better to use it with s4.
If your gonna flash the modem always use PHONE/CP. If your flashing pre-rooted rom from djembey or samsung stock firmware always use PDA. And if you download custom rom such as omega,phoenix,golden,etc.etc then you flash that via recovery using either CWM, philz or twrp.
Edit try emj5 wifi fix if not just do a fresh install
Sent from my Phone.

[Q] N9005 revert to stock rom

Cheers!
I recently flashed CyanogenMod 11 on my N9005. The thing is i'm not happy with it and i want to revert back to a stock rom. So what i was wondering is if i have to revert to the exact old version (4.3) or i could flash a stock KitKat firmware from SamMobile and how can i do that? I read a thread where a guy bricked his phone when trying with cwm cause he had some files missing. I know most users are sick of noobs like me asking this kind of questions but i would much appreciate if someone could help me out.
Thanks

FreeeMans20 said:
Cheers!
I recently flashed CyanogenMod 11 on my N9005. The thing is i'm not happy with it and i want to revert back to a stock rom. So what i was wondering is if i have to revert to the exact old version (4.3) or i could flash a stock KitKat firmware from SamMobile and how can i do that? I read a thread where a guy bricked his phone when trying with cwm cause he had some files missing. I know most users are sick of noobs like me asking this kind of questions but i would much appreciate if someone could help me out.
Thanks
Click to expand...
Click to collapse
Follow the instructions on the link, also there is a link on that page which takes you another page how to root N9005XXUENB7 which is the latest firmware for samsung galaxy note 3 SM-N9005. Please make sure you follow the instructions carefully and you have the right model international Note 3 SM-N9005,
http://nasirtech.blogspot.co.uk/2014/03/n9005xxuenb7-android-442-kitkat.html
The above method is for bringing the phone to factory stock. If you just want to revert back to a samsung rom and your phone is rooted with custom recovery, which I presume it is, you can just flash a samsung rom of your choice there are plenty to choose from and every rom thread have instructions how to flash their rom
Hope this helps, all the best.

Cheers
vtec303 said:
Follow the instructions on the link, also there is a link on that page which takes you another page how to root N9005XXUENB7 which is the latest firmware for samsung galaxy note 3 SM-N9005. Please make sure you follow the instructions carefully and you have the right model international Note 3 SM-N9005,
The above method is for bringing the phone to factory stock. If you just want to revert back to a samsung rom and your phone is rooted with custom recovery, which I presume it is, you can just flash a samsung rom of your choice there are plenty to choose from and every rom thread have instructions how to flash their rom
Hope this helps, all the best.
Click to expand...
Click to collapse
Cheers man. I'm downloading as we speak. Hopefully i'll come back with good news.

No problem mate, I am sure the process will go butter smooth but let us know if you come across any problems , all the best.

Problem in Odin
vtec303 said:
No problem mate, I am sure the process will go butter smooth but let us know if you come across any problems , all the best.
Click to expand...
Click to collapse
So, like yesterday, Odin fails on me. At the very end. When the green loading bar is full and it seems like it's going to succeed, the last line says failed. The phone has CWM 6.0.4.7 flashed and CF AutoRoot. Any ideeas?

FreeeMans20 said:
So, like yesterday, Odin fails on me. At the very end. When the green loading bar is full and it seems like it's going to succeed, the last line says failed. The phone has CWM 6.0.4.7 flashed and CF AutoRoot. Any ideeas?
Click to expand...
Click to collapse
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005

Thanks
vtec303 said:
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005
Click to expand...
Click to collapse
Downloading as we speak. I'll give it a try when done. I'll let you know!

Same
vtec303 said:
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005
Click to expand...
Click to collapse
Same thing. This is what i'm getting every time i try to flash a ROM.Any other suggestions? Vtec303, can you please tell what are the exact steps you took to flash it? Thanks
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005AUTENB1_N9005XXUENB1_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> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)

ok sorry to hear that mate, give one more try with NB3, hopefully that should work, fingers crossed
If that fails than try this:
http://forum.xda-developers.com/showthread.php?t=2613374
That guys phone is a Hong Kong model but the files he is using to flash are compatible with international Note 3
SM N9005.
Sent from my SM-N9005 using Tapatalk

Another thing is your phone a 16GB model ?, or is it 32 or 64GB, cheers.

It's actually 32GB. I'm just after realizing. Would that be the reason why it's not working?
Sent from my SM-N9005 using xda app-developers app

Thanks
vtec303 said:
ok sorry to hear that mate, give one more try with NB3, hopefully that should work, fingers crossed
If that fails than try this:
http://forum.xda-developers.com/showthread.php?t=2613374
That guys phone is a Hong Kong model but the files he is using to flash are compatible with international Note 3
SM N9005.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thanks man. FeralFire's tutorial helped me a lot. That was the only way i could flash a custom ROM. And thanks for opening my eyes and reminding me about the size of my phone. For some reason, i got stuck to thinking that my device has only 16GB. Cheers and a big Thanks for your help!

No problem ur welcome, I am glad your phone is back online mate and I hope it stays that way , all the best, tc
Sent from my SM-N9005 using Tapatalk

[Q] S4 Soft Brick

Hey so one of my friends is having problems getting their S4 to boot. Currently she has K0T49H.L720VPUFNAE on her S4. She has no custom recovery, but did have the phone rooted. Now the device can't boot. It gets past the Samsung Galaxy S4 screen and then goes black, the blue notification light pulses, and the phone makes a beep (almost like the initial boot sound) and then just hangs there. I've tried to odin back to stock, but I receive "failed! (Auth) almost immediately after starting.
On the Samsung Galaxy S4 screen both "Kernel is not seandroid enforcing" & "Warranty bit: kernel" are displayed in the top corner.
I can boot into stock recovery & download mode.
Any help would be appreciated!

It sounds like you are trying to Odin an older version on there than NAE. You cant downgrade, only can flash the NAE tar or the newer NG2.
Download it here, and try flashing it instead. After you flash, if it still wont boot, boot into recovery mode and do a factory reset.

random45 said:
It sounds like you are trying to Odin an older version on there than NAE. You cant downgrade, only can flash the NAE tar or the newer NG2.
Download it here, and try flashing it instead. After you flash, if it still wont boot, boot into recovery mode and do a factory reset.
Click to expand...
Click to collapse
I am trying to flash NAE tar and have tried the NG2. Both result in the errors mentioned above.
I also have gone into stock recovery and performed a factory reset.

Joey43 said:
I am trying to flash NAE tar and have tried the NG2. Both result in the errors mentioned above.
I also have gone into stock recovery and performed a factory reset.
Click to expand...
Click to collapse
can you post the log from odin? Also what version of odin are you using? have you tried flashing Phil's Recovery and maybe just installing a ROM?

random45 said:
can you post the log from odin? Also what version of odin are you using? have you tried flashing Phil's Recovery and maybe just installing a ROM?
Click to expand...
Click to collapse
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<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)
There's the log. I can't install a custom recovery either. It acts like it is installing correctly, but when it reboots it is still stock recovery.

Joey43 said:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<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)
There's the log. I can't install a custom recovery either. It acts like it is installing correctly, but when it reboots it is still stock recovery.
Click to expand...
Click to collapse
what version of odin are you using?

random45 said:
what version of odin are you using?
Click to expand...
Click to collapse
Oh, sorry. I've tried both 3.07 & 3.09

Joey43 said:
Oh, sorry. I've tried both 3.07 & 3.09
Click to expand...
Click to collapse
Okay, its really strange honestly. I spent sometime looking online for possible solutions, and the only thing I can come up with is:
1. make sure you are using the usb cable that came with the phone, and that it is undamaged
2. if its a desktop, make sure the usb cable is connected on the back. if you have usb 3.0 ports try it on there
3. some people say odin and kies dont get along. I do not share this experience, but who knows, doesnt hurt to try uninstalling kies, and install phone drivers
How did this happen by the way?

random45 said:
Okay, its really strange honestly. I spent sometime looking online for possible solutions, and the only thing I can come up with is:
1. make sure you are using the usb cable that came with the phone, and that it is undamaged
2. if its a desktop, make sure the usb cable is connected on the back. if you have usb 3.0 ports try it on there
3. some people say odin and kies dont get along. I do not share this experience, but who knows, doesnt hurt to try uninstalling kies, and install phone drivers
How did this happen by the way?
Click to expand...
Click to collapse
I'm using my S3 cable since her OEM one is broken. I tried around 4 different cables since I had the same thought. I never had kies installed and I did install the drivers.
I have really awful internet stability and speed (like 100kbs) so I'm hoping that the download is just corrupted and I'm just trying to re-download it.
I honestly don't know, she gave it to her brother to look at first, whom I suspect made the issue worse. I'm usually pretty good at fixing these things and I thought that it was an easy fix since it could reach download mode. I really appreciate all the help still.

have you tried flashing a pit file?
here is a 16 GB Sprint L720 NAE pit file you can try. do that with caution, and as a last resort.
Joey43 said:
I'm using my S3 cable since her OEM one is broken. I tried around 4 different cables since I had the same thought. I never had kies installed and I did install the drivers.
I have really awful internet stability and speed (like 100kbs) so I'm hoping that the download is just corrupted and I'm just trying to re-download it.
I honestly don't know, she gave it to her brother to look at first, whom I suspect made the issue worse. I'm usually pretty good at fixing these things and I thought that it was an easy fix since it could reach download mode. I really appreciate all the help still.
Click to expand...
Click to collapse

random45 said:
have you tried flashing a pit file?
here is a 16 GB Sprint L720 NAE pit file you can try. do that with caution, and as a last resort.
Click to expand...
Click to collapse
I tried that and received a "secure check fail: PIT" error. Phone performs the same as before.

i think the phone's busted....maybe try sending it to that one place that can jtag phones?
I think this is the site, but dont hold me to it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/

random45 said:
i think the phone's busted....maybe try sending it to that one place that can jtag phones?
I think this is the site, but dont hold me to it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/
Click to expand...
Click to collapse
I got philz custom recovery finally, and was able to flash NG2 pre-rooted, but the baseband version is old and wifi/data isn't working. I'm trying to flash the NG2 Modem.tar under the phone tab in odin, but i receive fail auth still and secure check fail: apnhlos.
I'm currently pursuing .tar to flashable .zip python converters, because it seems I cannot flash anything but one specific version of philz recovery in odin, but can flash anything through custom recovery.

Joey43 said:
I got philz custom recovery finally, and was able to flash NG2 pre-rooted, but the baseband version is old and wifi/data isn't working. I'm trying to flash the NG2 Modem.tar under the phone tab in odin, but i receive fail auth still and secure check fail: apnhlos.
I'm currently pursuing .tar to flashable .zip python converters, because it seems I cannot flash anything but one specific version of philz recovery in odin, but can flash anything through custom recovery.
Click to expand...
Click to collapse
Okay, so your making some progress.

random45 said:
Okay, so your making some progress.
Click to expand...
Click to collapse
where can i get that philz recovery im goin thru the same thang

I don't have this phone anymore. Good luck.
Sent from my SM-N910P using Tapatalk

To be honest TWRP is your better option for recovery on the S4 (I was a staunch supporter of Philz on my S3) one thing you need to make sure when you flash TWRP it to uncheck the auto reboot option. When flash completes, unplug and pull battery and then boot directly into recovery, then it sticks. You may be having WiFi/data issues because of your baseband/ROM combo. Have you tried flashing the latest stock?

Need Help Device stuck After flash?
I have the sprint sph l720t model. I finally acquired root access. I tried to flash Cyogenmod. When I did, it finished and rebooted and a after reboot it says cyogen mod in a circle that just keeps on spinning. I tried to get back to my blue team win screen into recovery but no luck. I got the phone to go into download mode once. I do have backups on my SD card with all the files can I flash a backup? What can I do?? The recovery says in red kernel is not se enforcing then under that in yellow set warranty bit: kernel? Can I use odin to do something in download mode to get my device back up?? I did refash my MD.5 file again from chainfire no luck! Help? Thanks

mattzeller said:
To be honest TWRP is your better option for recovery on the S4 (I was a staunch supporter of Philz on my S3) one thing you need to make sure when you flash TWRP it to uncheck the auto reboot option. When flash completes, unplug and pull battery and then boot directly into recovery, then it sticks. You may be having WiFi/data issues because of your baseband/ROM combo. Have you tried flashing the latest stock?
Click to expand...
Click to collapse
Yes I am now running Lollipop 5.0.1. I also did finally get TWRP installed. Everything is back to normaral. I re-installed the firmware from sam mobile. I then ofcoarse, went and flashed cf-autoroot with Odin. I pulled the batterry this time and booted up into recovery. Somehow everything is working and I do have recovery somewhere in my device. I want to try another Rom but Honestly TWRP makes me nervous evertime I open the app! What should I try next. Its just like factory rom with root but not really root. Its weird. At suggestios would be cool.. Thanks

EngineManShawn said:
Yes I am now running Lollipop 5.0.1. I also did finally get TWRP installed. Everything is back to normaral. I re-installed the firmware from sam mobile. I then ofcoarse, went and flashed cf-autoroot with Odin. I pulled the batterry this time and booted up into recovery. Somehow everything is working and I do have recovery somewhere in my device. I want to try another Rom but Honestly TWRP makes me nervous evertime I open the app! What should I try next. Its just like factory rom with root but not really root. Its weird. At suggestios would be cool.. Thanks
Click to expand...
Click to collapse
You have a lot of options now that you are presumably on the latest baseband. Just download the ROM you want, copy it to your external SD card and flash in TWRP.
If you like TouchWiz I suggest Wicked X:
http://forum.xda-developers.com/showthread.php?t=3115583
It's a fairly modified TW ROM, with quite a few mods that you can apply as you see fit. The developer is fantastic, quick to support and address issues. Every time he changes devices, I change to that device, he's that good. I've been stalking him since his time developing for the S2.
If TW isn't your thing, I suggest BlissPop:
http://forum.xda-developers.com/showthread.php?p=62018060
When I'm not running Wicked X I'm running BlissPop. The only caveat is I have not been able to get data to work properly on the latest builds, but the experimental build from 9/28 that I run is flawless. If you can't find it on their page, let me know I have it up on Mega.
Neither one is better than the other, it just a matter of preference. They both have great battery life, especially when paired with Greenify.

Does any body have a back up of the stock recovery for SM-G935A

So i thought i had a back up of my stock recovery on my SD card but it seem i left it on my phone. lol
does any on have a back up of the stock recovery for S7 edge ATT (SM-G935A).
been trying to look around cant find the stock recovery keep finding a stock firmware and not recovery.
any help would be appreciated. thx. Would even donate if i worked.

bfixer117 said:
So i thought i had a back up of my stock recovery on my SD card but it seem i left it on my phone. lol
does any on have a back up of the stock recovery for S7 edge ATT (SM-G935A).
been trying to look around cant find the stock recovery keep finding a stock firmware and not recovery.
any help would be appreciated. thx. Would even donate if i worked.
Click to expand...
Click to collapse
If I'm not mistaken , the recovery is included in the firmware .

SkyAttacksX said:
If I'm not mistaken , the recovery is included in the firmware .
Click to expand...
Click to collapse
Well when flashing the different recoveries. I was trying to get working it said back up current recovery in Flashify so I did but forgot to move it to my SD card. then i flashed it thats where i was pretty sure that recoveries were different files but written the same way as roms or AP's in ODIN. but then when I went to test it out my phone is stuck in a boot loop with no recovery and I've been trying to use ODIN to try and flash a stock on but it keeps failing.

bfixer117 said:
Well when flashing the different recoveries. I was trying to get working it said back up current recovery in Flashify so I did but forgot to move it to my SD card. then i flashed it thats where i was pretty sure that recoveries were different files but written the same way as roms or AP's in ODIN. but then when I went to test it out my phone is stuck in a boot loop with no recovery and I've been trying to use ODIN to try and flash a stock on but it keeps failing.
Click to expand...
Click to collapse
What firmware were you on prior to this ?
EDIT: Also , which firmware have you tried flashing ?

SkyAttacksX said:
What firmware were you on prior to this ?
EDIT: Also , which firmware have you tried flashing ?
Click to expand...
Click to collapse
the one here: http://forum.xda-developers.com/att-galaxy-s7/how-to/g935a-root-t3410403/
then here: http://d-h.st/lQY8
tried flashing the stock firmware but get this error
<ID:0/003> 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..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)

I have also been trying to flash a stock firm ware thats when i get the error maybe someone is using a SM-G935F or some other model number for the SM-G935A if anyone have and actual stock firm ware for the SM-G935A i would greatly appreciate it. also if it is a real working stock firmware i would be willing to donate if wanted.

bfixer117 said:
I have also been trying to flash a stock firm ware thats when i get the error maybe someone is using a SM-G935F or some other model number for the SM-G935A if anyone have and actual stock firm ware for the SM-G935A i would greatly appreciate it. also if it is a real working stock firmware i would be willing to donate if wanted.
Click to expand...
Click to collapse
Sir . . those were links to root methods and an engboot . What update were you on ? June , May , April ?

SkyAttacksX said:
Sir . . those were links to root methods and an engboot . What update were you on ? June , May , April ?
Click to expand...
Click to collapse
I'm pretty sure the newest one gomy phone like 3 months ago gonna try this firmware see if it works
https://www.androidfilehost.com/?fid=24572369242688242

bfixer117 said:
I'm pretty sure the newest one gomy phone like 3 months ago gonna try this firmware see if it works
https://www.androidfilehost.com/?fid=24572369242688242
Click to expand...
Click to collapse
That is your firmware , correct . Unrar it and put it in the correct ODIN slots and flash .

PB5 and newer versions have been posted for a while now. Flash the latest and you'll be fine

Yea thanks all the help guys. Called Samsung and acted like the phone just stated doing it then she was like take it to your nearest best buy and have them reflash it so after I took it up there they used there ODIN like program and then boom! it was working.