Related
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
eletendre84 said:
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
Click to expand...
Click to collapse
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
mentorkyrom said:
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
Click to expand...
Click to collapse
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
eletendre84 said:
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
Click to expand...
Click to collapse
Tethering is available on CM11 just like it was on 10.2; would strongly recommend latest Philz Touch Recovery over either TWRP or CWM though. Although it is based on CWM, it has proven to be pretty much the superior recovery option for flashing any Android build number, plus it is highly customizable.
Philz Touch Recovery
this is how to downgrade
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
smuther22 said:
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
Click to expand...
Click to collapse
Do you realize that this thread hasn't been used in a couple of months? I would assume the author has no more need of advice based on the inactivity. Also, once Knox is installed, it is on the phone to stay. PERIOD. NO DOWNGRADING POSSIBLE VIA ODIN. Custom ROMs of any build are fine via custom recovery, but any attempt to change the bootloader will trigger Knox and brick the phone. Dangerous info to be posting here, especially since someone else who doesn't know better might try this.
So, i decide to root my s3 because i wanted to do some cool stuff. I got odin, got the tar file and tried flashing it. For some reason it didn't work :crying: On odin it gave me a fail. I was in download mode too. So, when i turn on my s3 it is in odin mode but it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." i did this in kies and when it was at like 99% it gives me an error. :crying:
so i tried flashing again in odin still fail, but i get on my s3 SV REV CHECK FAIL: Fused 2 > Binary 0. I have no clue what that means, So, i just want my phone to get working again i dont care about rooting anymore. JUST HELP ME FIX IT!!!!:crying:
BTW: I di root my Kindle Fire a while back so i thought I would have experience with this (i kind of do) but i guess I thought wrong.
Was your phone running a stock 4.3 AT&T ROM? What method did you use to try and root the phone?
audit13 said:
Was your phone running a stock 4.3 AT&T ROM? What method did you use to try and root the phone?
Click to expand...
Click to collapse
i think so and i tired using odin and i put the phone in download mode so i could flash the .tar file
Resistance225 said:
i think so and i tired using odin and i put the phone in download mode so i could flash the .tar file
Click to expand...
Click to collapse
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
audit13 said:
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
Click to expand...
Click to collapse
I will try to do this! Thanks for helping me though, i will keep you updated. :fingers-crossed:
audit13 said:
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
Click to expand...
Click to collapse
I installed a recovery and guess what, it started working again! All my data was still there too! Thanks i really appreciate you taking the time to help me! I also was able to succsessfully root it by using the CF auto root .tar file. Once again, thanks a ton!
Resistance225 said:
I installed a recovery and guess what, it started working again! All my data was still there too! Thanks i really appreciate you taking the time to help me! I also was able to succsessfully root it by using the CF auto root .tar file. Once again, thanks a ton!
Click to expand...
Click to collapse
Glad you got it working. We're all here to help.
hey guys,
I need help asap! I tried using the video on this website to root my tmobile S4. I downloaded Kies, Odin 3.07, ROOT_M919UVUAMDL.zip, and CWM as recovery-clockwork-touch-6.0.3.2-jfltetmo.tar, I did NOT install triangle away( i forgot). I went through the steps and passed in Odin. then, when I pulled the battery and booted in CWM i couldnt find the file so i went to the store to buy a sdcard. when I came home i re-ran through Odin and found the root zip on the external sdcard. I successfully installed the root zip and clicked reboot. my problem arose when it showed a "KERNEL IS NOT SEANDROID ENFORCING" in red, and a "SET WARANTY BIT: KERNEL" in yellow. it seems to be frozen in this screen and i can only use the CWM and Download mode. I have tried re-using Odin .
Please help!!
That's an old root method. You can either
1) flash a custom ROM and go about your business
2) Odin back to stock firmware and root with cf-auto root or towelroot
Sent from my SGH-M919 using Tapatalk
serio22 said:
That's an old root method. You can either
1) flash a custom ROM and go about your business
2) Odin back to stock firmware and root with cf-auto root or towelroot
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm sorry, I'm a Noob. but 1) where can I get a custom ROM and how do i apply it? 2) can you elaborate on your #2?
scott560 said:
I'm sorry, I'm a Noob. but 1) where can I get a custom ROM and how do i apply it? 2) can you elaborate on your #2?
Click to expand...
Click to collapse
1) You can find tons of Custom ROMs here: http://forum.xda-developers.com/galaxy-s4-tmobile/development
You usually flash them to your phone via a Custom Recovery such as CWM or TWRP. Or, is some cases you can use ODIN. Read, Read, Read, Read before your flash. It is very easy to do, but you need to understand what you are doing. All Custom ROMs come pre-rooted.
2) You can download a stock ROM from here:
http://www.sammobile.com/firmwares/
Or, you can use Kies to download and install the most recent firmware for your phone.
TowelRoot is a new option for rooting stock ROMs that are version 4.4.2 (KitKat). This method of rooting doesn't trip the Knox flag.
Here's a video: https://www.youtube.com/watch?v=ZGwMs8JPBhE
Rob
rlichtefeld said:
1) You can find tons of Custom ROMs here: http://forum.xda-developers.com/galaxy-s4-tmobile/development
You flash them to your phone via ODIN. Read, Read, Read, Read before your flash. It is very easy to do, but you need to understand what you are doing. All Custom ROMs come pre-rooted.
2) You can download a stock ROM from here:
http://www.sammobile.com/firmwares/
Or, you can use Kies to download and install the most recent firmware for your phone.
TowelRoot is a new option for rooting stock ROMs that are version 4.4.2 (KitKat). This method of rooting doesn't trip the Knox flag.
Here's a video: https://www.youtube.com/watch?v=ZGwMs8JPBhE
Rob
Click to expand...
Click to collapse
Thanks for replying however, you do not flash custom ROMs via Odin, you need a custom recovery like twrp or cwm.. Stock firmware you do flash via Odin.. And their Knox flag is already tripped, wouldn't matter
serio22 said:
Thanks for replying however, you do not flash custom ROMs via Odin, you need a custom recovery like twrp or cwm.. Stock firmware you do flash via Odin.. And their Knox flag is already tripped, wouldn't matter
Click to expand...
Click to collapse
Thanks for correcting me that most of the time you flash Custom ROMs via a Custom Recovery on the S4.
But, if I'm not mistaken you can flash Custom ROMs via ODIN as long as in the right format and you select the correct partition.
However, most of my Custom ROM history is with a HTC device, so I may be mistaken.
rlichtefeld said:
Thanks for correcting me that most of the time you flash Custom ROMs via a Custom Recovery on the S4.
But, if I'm not mistaken you can flash Custom ROMs via ODIN as long as in the right format and you select the correct partition.
However, most of my Custom ROM history is with a HTC device, so I may be mistaken.
Click to expand...
Click to collapse
It is possible but 99% of custom ROMs are not made to be flashed with Odin, in the past two years I've only seen about 1. And it is also inconvenient
Hi everyone.
Is there any way to root the Note 2 N7100 on Samsung official firmware Kitkat without tripping Knox. ??
My bootloader is ND4
My baseband is ND3
My PDA is ND4
If there is a safe method, what is it ...
I tried TR but got that my device is not supported.
My Knox is 0x0
If there isn't & I must trip Knox to root, so what's the best & safest method for rooting my N7100?? My warranty is gone long time ago anyway.
And if I'm gonna trip Knox so I prefer to have a custom recovery, what should I use? I thought of TWRP but found some complaining that 2.8.6 caused loss of signal... What should I use??
One more question, please.
Will rooting my phone & tripping Knox prevent future OTA update to the long awaited official Samsung Lollipop??
If the answer is yes is there a way around it ?? Will I be able to flash it by Odin after getting it from any where like Sammobile ?
Sorry for being long & Thanks
zoghrob said:
Hi everyone.
Is there any way to root the Note 2 N7100 on Samsung official firmware Kitkat without tripping Knox. ??
My bootloader is ND4
My baseband is ND3
My PDA is ND4
If there is a safe method, what is it ...
I tried TR but got that my device is not supported.
My Knox is 0x0
If there isn't & I must trip Knox to root, so what's the best & safest method for rooting my N7100?? My warranty is gone long time ago anyway.
And if I'm gonna trip Knox so I prefer to have a custom recovery, what should I use? I thought of TWRP but found some complaining that 2.8.6 caused loss of signal... What should I use??
One more question, please.
Will rooting my phone & tripping Knox prevent future OTA update to the long awaited official Samsung Lollipop??
If the answer is yes is there a way around it ?? Will I be able to flash it by Odin after getting it from any where like Sammobile ?
Sorry for being long & Thanks
Click to expand...
Click to collapse
Just root it as posted in sticky thread.
You don't have warranty, so just don't bother. Use odin, root and install recovery, then rom.
You can flash stock rom via odin if you want, you can install custom roms via recovery.
I'm using TWRP for 2 years and never had any problem. You can also use Philz. For normal user it doesn't really matter.
yaro666 said:
Just root it as posted in sticky thread.
You don't have warranty, so just don't bother. Use odin, root and install recovery, then rom.
You can flash stock rom via odin if you want, you can install custom roms via recovery.
I'm using TWRP for 2 years and never had any problem. You can also use Philz. For normal user it doesn't really matter.
Click to expand...
Click to collapse
Thank you very much for your help.
Actually I found no sticky threads for rooting 4.4.2. Most of the sticky threads are dating since 2012 with 4.1.2 & 4.3.
However by searching I found 2 threads for 4.4.2, one of them is
http://forum.xda-developers.com/showthread.php?t=2767604
This one uses CF-auto-root... but no mention about any custom recovery. Will I lose root or mess things up if I install TWRP after that??
The other thread is
http://forum.xda-developers.com/showthread.php?t=2730764
This one uses the typical steps that I know, custom recovery then SuperSU. But it uses Philz recovery. Can I substitute it with TWRP??
Thank you for your help & patience.
The most important question: Why do you want to root?
If you like to flash a custom rom no need for root, any custom recovery - TWRP or CWM - flashed with Odin will do.
Androidwizzard said:
The most important question: Why do you want to root?
If you like to flash a custom rom no need for root, any custom recovery - TWRP or CWM - flashed with Odin will do.
Click to expand...
Click to collapse
I'm not planning to flash custom rom right now, may be later.
I want to root to be able to use some apps that require root. Plus, having full control over my phone.
In odin you have option to choose recovery file - AP.
After flashing recovery just install superSU via recovery.
DO a backup of your device and EFS before you flash anything.
yaro666 said:
In odin you have option to choose recovery file - AP.
After flashing recovery just install superSU via recovery.
DO a backup of your device and EFS before you flash anything.
Click to expand...
Click to collapse
Thank you for your help.
I don't know how to make a backup without recovery. So I flashed TWRP 2.8.6, took a backup then installed SuperSU via TWRP.
All went well except that I lost the signal and IMEI.
I found that I flashed TWRP t03gup while I should flashed t03g.
I reflashed the correct file then flashed the modem.bin of XXUFND3.
Everything thing is back to normal again except 2 things:
The icon of my service provider shifts place to the last app page after reboot, no matter where I place it...
The phone status shows custom (expected) but stays so even after using Triangle Away.
Is it better if I flash the stock firmware then recovery then SuperSU? ?? Or flashing the modem as I did was enough to straighten things up? ?
Thank you for your patience and help.
zoghrob said:
Thank you for your help.
I don't know how to make a backup without recovery. So I flashed TWRP 2.8.6, took a backup then installed SuperSU via TWRP.
All went well except that I lost the signal and IMEI.
I found that I flashed TWRP t03gup while I should flashed t03g.
I reflashed the correct file then flashed the modem.bin of XXUFND3.
Everything thing is back to normal again except 2 things:
The icon of my service provider shifts place to the last app page after reboot, no matter where I place it...
The phone status shows custom (expected) but stays so even after using Triangle Away.
Is it better if I flash the stock firmware then recovery then SuperSU? ?? Or flashing the modem as I did was enough to straighten things up? ?
Thank you for your patience and help.
Click to expand...
Click to collapse
It should be OK just as it is now, but if you have 30min free time, you can flash stock, root, custom rom with full wipe to make sure you have everything straighten up
yaro666 said:
It should be OK just as it is now, but if you have 30min free time, you can flash stock, root, custom rom with full wipe to make sure you have everything straighten up
Click to expand...
Click to collapse
30 min or even an hour is ok by me...
I'll do it right away. Flash stock, TWRP recovery then root with SuperSU.
As for the custom rom it'll have to wait as I didn't make up my mind which Lollipop to get... I'm kinda confused about it very much. I can't decide which to get.
I'm open for suggestions. lol
Thanks a million for your support.
If you need your phone for business don't flash lollipop. Still in beta phase, so bugs are occuring often.
I use dr. ketan's V14 and it's the most stable rom I have used
yaro666 said:
If you need your phone for business don't flash lollipop. Still in beta phase, so bugs are occuring often.
I use dr. ketan's V14 and it's the most stable rom I have used
Click to expand...
Click to collapse
My phone is for personal use not for business.
But I think I'll follow your advice & give Dr. Ketan's V14 a try.
I did flash stock firmware then flashed TWRP 2.8.6 (correct file this time.. lol) then installed root.
I did backup my phone & EFS by TWRP. All is excellent now.
Now I'll backup my contacts, sms, apps & data using Titanium back up then go for Dr. ketan's rom.
Wish me luck.
Thanks.
you will be positively surprised if youhad stock the whole time.
cheers
salute
yaro666 said:
you will be positively surprised if youhad stock the whole time.
cheers
salute
Click to expand...
Click to collapse
Wow... it's awesome. ..
Thumbs up. ..
You are right.
I'm wondering right now how did I stuck to the stock firmware all the past time.
Thanks.
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