Develop Bugs

[Q] Odin flash failure !!!

*Upgraded to official 4.3
*Flashed modified stock MK2 by jovy23 http://forum.xda-developers.com/showthread.php?t=2545711
*Tried flashing stock 4.2.2 (MDL) via Odin( tried v1.85, 3.09,3.07, just to make sure Odin is not the reason of failure)
*Flashing fails(says Aunthentication failed )
Can anyone help me fix this..please..

re: odin flash
Shafayat said:
*Upgraded to official 4.3
*Flashed modified stock MK2 by jovy23 http://forum.xda-developers.com/showthread.php?t=2545711
*Tried flashing stock 4.2.2 (MDL) via Odin( tried v1.85, 3.09,3.07, just to make sure Odin is not the reason of failure)
*Flashing fails(says Aunthentication failed )
Can anyone help me fix this..please..
Click to expand...
Click to collapse
before you odin flash, go into recovery and do a "factory reset"
and then odin flash stock mdl and you should be good to go.
Good luck!

Are you flashing roms with Odin ? You should use TWRP or CWM to flash roms, not Odin.

dklue said:
Are you flashing roms with Odin ? You should use TWRP or CWM to flash roms, not Odin.
Click to expand...
Click to collapse
No, i tried flashing official MDL firmware , i flashed that modified MK2 by jovy23 via TWRP.

Misterjunky said:
before you odin flash, go into recovery and do a "factory reset"
and then odin flash stock mdl and you should be good to go.
Good luck!
Click to expand...
Click to collapse
tried that too..but no luck

Is the colored modem line showing up in odin, correct drivers installed, maybe bad download, check md5, are you clicking the phone button in odin ? Are you
going into download mode on phone, then connect cable ?

re: flashing roms
dklue said:
Are you flashing roms with Odin ? You should use TWRP or CWM to flash roms, not Odin.
Click to expand...
Click to collapse
Your post makes me laugh. LOL
Have a happy thanksgiving!

dklue said:
Is the colored modem line showing up in odin, correct drivers installed, maybe bad download, check md5, are you clicking the phone button in odin ? Are you
going into download mode on phone, then connect cable ?
Click to expand...
Click to collapse
yes...i even flashed twrp recovery after firmware flash failure.. "kernel is not seandroid enforcing, set warranty bit : kernel" shows up at every boot up on top of the screen.

Are you on the official 4.3? With the new bootloader? You can't Odin 4.2.2 once you have the new bootloader, only Odin mk2. If you are still on mdl bootloader you should be able to
Sent from my SGH-M919 using xda app-developers app

tylerholbrook said:
Are you on the official 4.3? With the new bootloader? You can't Odin 4.2.2 once you have the new bootloader, only Odin mk2. If you are still on mdl bootloader you should be able to
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
yes, i m on new bootloader...isnt there any way around ?

I flashed with Odin and i used the one before 1.85...was it 1.83? I'm not sure, but mine failed on 1.85. Try pervious ones and make sure it's in the right pda.
Sent from my SGH-M919 using Tapatalk

Well I guess that's the problem when people have problems and don't fully explain it, just trying to help, at this point he or she probably knows more
then me....... lol

Shafayat said:
yes, i m on new bootloader...isnt there any way around ?
Click to expand...
Click to collapse
At the moment no. And I have the slightest feeling that when you did that, you tripped your Knox flash counter by trying to Odin MDL firmware while on the newest. Now since you most likely tripped it, you won't be able to reset the counter because there is no way yet and that has permanently voided your warranty for now. Once you've updated via ota or kies or Odin to 4.3 you're stuck.
Sent from my GT-I9505G using XDA Premium 4 mobile app

Shafayat said:
*Upgraded to official 4.3
*Flashed modified stock MK2 by jovy23 http://forum.xda-developers.com/showthread.php?t=2545711
*Tried flashing stock 4.2.2 (MDL) via Odin( tried v1.85, 3.09,3.07, just to make sure Odin is not the reason of failure)
*Flashing fails(says Aunthentication failed )
Can anyone help me fix this..please..
Click to expand...
Click to collapse
Its because when you flash a fireware it communicates with the new boot loader to check if its the same version or newer.
If oyu pull the tars apart and retar just the system/data/and image files it might flash.

unable to boot without 'debrick' sdcard

Hey guys
so I accidentally installed a firmware (http://forum.xda-developers.com/showthread.php?t=2282603&highlight=unbrick) and my phone got bricked (T999). I managed to get it to boot using the debrick solution with the sdcard, but I have no idea how to make it boot without the sdcard. (used http://forum.xda-developers.com/showthread.php?t=2439367).
I've tried going to the odin thread (http://forum.xda-developers.com/member.php?u=4081205) and have downloaded the T999 MD5 (both root66 and stock) files yet everytime I try to flash, odin keeps failing right after NAND WRITE.
The funny thing is, I have cyanogen installed and it works fine. it's just the boot process that's not working.
I supposed as a last resort I can leave the sd card in, but anybody know a solution?
Thanks!

Are you running CM 10.2? If you were on a 4.3 ROM, you have to find the MJC firmware.

Daoiod said:
Are you running CM 10.2? If you were on a 4.3 ROM, you have to find the MJC firmware.
Click to expand...
Click to collapse
Yea its currently on Cm 10.2. I need a separate firmware? I can't just install a stock ROM?

Megiddo2000 said:
Yea its currently on Cm 10.2. I need a separate firmware? I can't just install a stock ROM?
Click to expand...
Click to collapse
That thread specifically says to NOT flash that firmware if you're running the latest 4.3 firmware, and since you're running CM 10.2, I assume you're on firmware 4.3.
So that's why you need to flash the stock 4.3 firmware to restore your bootloader back the way it was.

Daoiod said:
That thread specifically says to NOT flash that firmware if you're running the latest 4.3 firmware, and since you're running CM 10.2, I assume you're on firmware 4.3.
So that's why you need to flash the stock 4.3 firmware to restore your bootloader back the way it was.
Click to expand...
Click to collapse
I first flashed that firmware because 10.2 wouldn't flash properly.
If I'm already running 4.3 then why do I need to flash stock 4.3.
Right now my biggest problem is that odin simply won't flash. It keeps failing after NAND WRITE.

Megiddo2000 said:
I first flashed that firmware because 10.2 wouldn't flash properly.
If I'm already running 4.3 then why do I need to flash stock 4.3.
Right now my biggest problem is that odin simply won't flash. It keeps failing after NAND WRITE.
Click to expand...
Click to collapse
Because you want to boot your phone without the SD card. According to the thread, "Currently there is NO way to downgrade from MJC firmware without a brick due to the Knox security stuff added to that firmware release."
When you flash the MD5 firmware in that thread, you attempt to downgrade, causing the brick.

Daoiod said:
Because you want to boot your phone without the SD card. According to the thread, "Currently there is NO way to downgrade from MJC firmware without a brick due to the Knox security stuff added to that firmware release."
I believe when you flash that, you attempt to downgrade, causing the brick.
Click to expand...
Click to collapse
If I flash 4.3 stock, then it's not downgrading. It's just maintaining that bootloader. Then how come the odin flash fails?
Right now I'm trying t oget my phone to boot w/o a sd card. It doesn't matter what version I have to flash. It's just that every version seems to be failing.

So you are saying that you Odin 4.3 mjc firmware and it keeps failing?
Sent from my SGH-T999 using xda app-developers app

chrisram88 said:
So you are saying that you Odin 4.3 mjc firmware and it keeps failing?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
nope. on the debrick thread, it says after being able to boot with the sd card, go to the odin thread.
the odin thread has a bunch of stock roms and instructions on how to install them.
i downloaded the stock roms and tried flashing all of them (in hopes atleast one of them would work) but they all fail

Just flash 4.3 firmware. Not a rom.
Sent from my SGH-T999 using xda app-developers app

Megiddo2000 said:
If I flash 4.3 stock, then it's not downgrading. It's just maintaining that bootloader. Then how come the odin flash fails?
Right now I'm trying t oget my phone to boot w/o a sd card. It doesn't matter what version I have to flash. It's just that every version seems to be failing.
Click to expand...
Click to collapse
Sorry, I wasn't very specific. Because you're on MJC, there's no way to downgrade. That's why none of those ROMs work.
You need to flash the 4.3 MJC firmware via Odin because when you flashed that MD5 firmware, it messed with the MJC bootloader, and the MJC firmware won't let you downgrade to a lower firmware.
So flashing the 4.3 MJC firmware will restore the MJC bootloader, unbricking your phone.

Daoiod said:
Sorry, I wasn't very specific. Because you're on MJC, there's no way to downgrade. That's why none of those ROMs work.
You need to flash the 4.3 MJC firmware via Odin because when you flashed that MD5 firmware, it messed with the MJC bootloader, and the MJC firmware won't let you downgrade to a lower firmware.
So flashing the 4.3 MJC firmware will restore the MJC bootloader, unbricking your phone.
Click to expand...
Click to collapse
For anyone who's facing this problem, I just used samsung Kies and it fixed the problem in less than 10 minutes. It boots fine w/o the sd card now.
My firmware was preserved, so I had no problems flashing newer roms.
It did, however, unroot my device, so just be prepared to redo that process.

[Q] Trying to downgrade from 4.4.2 (Cyanagenmod 11) to 4.1.2 stock (T999UVDMD5)

As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?

huz666 said:
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
Click to expand...
Click to collapse
If you are getting errors in both odin and cwm, it sounds like it is a root issue. In other words, it sounds like the apps are being denied access to root and therefor cannot flash. Both odin and cwm are able to generate logs so you can tell the reason for the fail. Personally, I would recommend flasing twrp recovery instead of cwm since it seems to simplify alot and is a little better for our device. Without knowing exactly why the flash is failing, i would just recommend to try and re-root the phone again.

Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.

Perseus71 said:
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Click to expand...
Click to collapse
Yes the phone was in downloading mode. I couldn't find any posts that thought that I would brick my phone for sure by downgrading so I thought I would try. Could I go back to the 4.3 Stock ROM with some degree of confidence?

Yes you can go back to 4.3 Stock.

Perseus71 said:
Yes you can go back to 4.3 Stock.
Click to expand...
Click to collapse
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.

huz666 said:
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
Click to expand...
Click to collapse
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk

serio22 said:
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
.
Thanks for the advice. I think I'll just quit while I'm only slightly behind now and remain on 4.3 Stock. I appreciate everyone's help and suggestions.

Downgrade from CM11 4.4.2 to 4.3 on I747
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747

You seriously need to do some reading
Sent from my SGH-T999 using Tapatalk

nitagro said:
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
Click to expand...
Click to collapse
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.

Perseus71 said:
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Click to expand...
Click to collapse
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.

nitagro said:
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
Click to expand...
Click to collapse
Please Read through this Thread. For Future Reference, all Odin Files for S3 in general are looked up by unique Keyword Root66. That thread is the right place for you to post errors or issues. If there's no 4.3 image for your phone there, you can post a request as well.
For your immediate Problem, there is a an alternate ATT StockMod Rom by @saranhai Please see this thread. Pay particular attention to the mandatory requirement of flashing a particular modem beforehand.

[Q] HELP Rooting (MK2)?? But On STOCK 4.2.2 DONT KNOW WHAT TO DO NEXT

In the begin I rooted my S4 On the MDL baseband (4.2.2) and had OUDHS recovery installed but i decided to to install Wicked_v10 (4.3) which required for to update to the 4.3 modem and i followed these steps http://forum.xda-developers.com/showthread.php?t=2544612 i followed all the steps with Odin BUT it said that it fail to Update.And it well reboot its self say back to download mode saying "firmware upgrade encountered an issue. please select recovery mode in kies & try again" so basically my phone was Soft-bricked i manage resorting it back use this thread http://forum.xda-developers.com/showthread.php?t=2258628 And soon enough my s4 was back alive:fingers-crossed: But only one problem now i take a look in my setting and i was on the MK2 Baseband As you can see in the screenshot and on top of the i get the error my notification bar saying "The device has detected an application attempting unpermitted actions and has
stopped loading. To protect your device, it is recommended you reboot." So im stuck now and i dont know what to next :crying:
should i just revert back to the MDL baseband because im not sure what to

Skitts said:
In the begin I rooted my S4 On the MDL baseband (4.2.2) and had OUDHS recovery installed but i decided to to install Wicked_v10 (4.3) which required for to update to the 4.3 modem and i followed these steps http://forum.xda-developers.com/showthread.php?t=2544612 i followed all the steps with Odin BUT it said that it fail to Update.And it well reboot its self say back to download mode saying "firmware upgrade encountered an issue. please select recovery mode in kies & try again" so basically my phone was Soft-bricked i manage resorting it back use this thread http://forum.xda-developers.com/showthread.php?t=2258628 And soon enough my s4 was back alive:fingers-crossed: But only one problem now i take a look in my setting and i was on the MK2 Baseband As you can see in the screenshot and on top of the i get the error my notification bar saying "The device has detected an application attempting unpermitted actions and has
stopped loading. To protect your device, it is recommended you reboot." So im stuck now and i dont know what to next :crying:
should i just revert back to the MDL baseband because im not sure what to
Click to expand...
Click to collapse
According to the screenshots you uploaded, you are not on MDL firmware. In fact, you are on MDB firmware. MDB was released when the T-Mobile Galaxy S4 came out. Use Odin and flash the MDL firmware (use that same restore thread again, but do NOT download the link that says Stock Tar, instead download UVUAMDL Official TAR). Flashing this should restore the baseband version from MK2 to MDL.

Vigz said:
According to the screenshots you uploaded, you are not on MDL firmware. In fact, you are on MDB firmware. MDB was released when the T-Mobile Galaxy S4 came out. Use Odin and flash the MDL firmware (use that same restore thread again, but do NOT download the link that says Stock Tar, instead download UVUAMDL Official TAR). Flashing this should restore the baseband version from MK2 to MDL.
Click to expand...
Click to collapse
Thanks i did not see that i was to busy worrying I think thats why my Wifi wasnt working , But other then that you got and suggestions why the modem MK2 gave me a error through odin ?

Skitts said:
Thanks i did not see that i was to busy worrying I think thats why my Wifi wasnt working , But other then that you got and suggestions why the modem MK2 gave me a error through odin ?
Click to expand...
Click to collapse
I'm not sure. I actually used that tutorial to upgrade my baseband and it worked just fine. Another person also had this issue as well. I told them that it could have something to do with the custom binary counter. Apparently, the phone prevents you from flashing unsigned items if the counter is high. You can reset it with an app called TriangleAway.

Vigz said:
I'm not sure. I actually used that tutorial to upgrade my baseband and it worked just fine. Another person also had this issue as well. I told them that it could have something to do with the custom binary counter. Apparently, the phone prevents you from flashing unsigned items if the counter is high. You can reset it with an app called TriangleAway.
Click to expand...
Click to collapse
Hmm could be Because I never did reset the counter when i flashed the recovery but ill give it a try.Ill tell you how it goes Thanks man for all your Help
One more thing ..... Do i have to put the "SS_DL.dll" under the odin folder like it say ?

Skitts said:
Hmm could be Because I never did reset the counter when i flashed the recovery but ill give it a try.Ill tell you how it goes Thanks man for all your Help
One more thing ..... Do i have to put the "SS_DL.dll" under the odin folder like it say ?
Click to expand...
Click to collapse
IT WORK !!!!!!!!!!!!!!!!!!!!!

your help urgent please

i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks

And here we go again...... What version software was installed before trying to update? Were you rooted?

zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....

done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS

zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?

rooted thru odin
now i can't get to OS ,just show samsung sign and loops

Flash whatever firmware u was on in odin

zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.

tried to do thru sd card ,but i get :
dm-verity verification failed

can i just go back to 5.1 lollipop with an official stock rom via odin ?

zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom

any firmware can get me back to lollipop with odin !!!

zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk

samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.

xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk

i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip