Database Develop

Boot loop after changing permission of etc folder

hello,
i have an galaxy note n7000, rooted with philz-cmw6.
the os was stock jelly bean 4.1.2
i was trying the airview patch given by cursed4ever by coping the xml file to etc\permission folder.
at first the file manager gave permission denied message. after searching threads i found that permission for the folder etc is to be changed on doing so i noticed that the entire folder went empty.
i copied the airview patch file and tried to reboot and since it is under infinite loop..
i can enter in the recovery mode having philz cmw6
please anyone can guide what further action should i take:crying:

u can use philz cwm install aroma file manager so u can use it in philz cwm without turning on ur phone to do copy n paste work ！
if still unable to bootup successful u can always do a factory reset n may lost all ur data ！
if u got a recent backup then just restore it ！
actually copy n paste work in etc/permission for airview won't cuz such problem...
maybe b4 doing the changes u already got bootloop issue but didn't noticed...

1. Reboot to recovery and select "fix permission"..after finish, reboot system..
Or
2. Reflash rom without any wipe..good luck
Sent from my GT-N7000 using Tapatalk 2

copy n paste work won't cuz the whole etc/permission folder to be missing ！
not sure what u've done ！

reflash the rom again without wipes if nothing else works

nokiamodeln91 said:
reflash the rom again without wipes if nothing else works
Click to expand...
Click to collapse
hello i tried to reflash the same rom with ODIN... the message came was fail... now i cant enter the recovery mode... i can enter into download mode...
the phone on start give a message"Firmware upgrade encountered an issue. please select recovery mode in kies & try again"
tried connecting to kies.... kies fails to recognize the phone.... what the hell is happening.... please help guys... i will really be greatfull...

Please tell us exactly what error message you got in ODIN.

+1.. paste the odin logs

ThaiDai said:
Please tell us exactly what error message you got in ODIN.
Click to expand...
Click to collapse
in bold letter its written fail on the top window...
i again tried to connect with ODIN now its coming Removed message again and again..

AW: Boot loop after changing permission of etc folder
I do not understand you. A snapshot please.
Sent from my GT-N7000 using xda premium

Paste odin log on down left conner..
Sent from my GT-N7000 using Tapatalk 2

ThaiDai said:
I do not understand you. A snapshot please.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i am again trying to flash via ODIN currently the the message area is displaying factoryfs.img
if this doesnt work r stops in between then i will post a snapshot... thanks for the quick replies.... it feels very good that someone is waiting to help....

ritesh.bafna88 said:
in bold letter its written fail on the top window...
i again tried to connect with ODIN now its coming Removed message again and again..
Click to expand...
Click to collapse
remove the battery and reboot into download mode ... on the bottom left corner of Odin there is a log window. copy what you get there and paste here for better understanding

current log
<ID:0/036> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N7000XXLSZ_N7000OXALSZ_906407_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/036> Odin v.3 engine (ID:36)..
<ID:0/036> File analysis..
<ID:0/036> SetupConnection..
<ID:0/036> Initialzation..
<ID:0/036> Get PIT for mapping..
<ID:0/036> Firmware update start..
<ID:0/036> cache.img
<ID:0/036> NAND Write Start!!
<ID:0/036> factoryfs.img

How long you have been stuck on factoryfs.img??
Sent from my GT-N7000 using Tapatalk 2

zai89 said:
How long you have been stuck on factoryfs.img??
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
nearly 5 to 7 mins now.... the bar is inching so i know there is progress how the message area displays hidden.img

This is the normal symptom for a bricked device.
There are many threads with information about it and the possible workaround with repartition (hg42).
I do not have the time now for more details - but luckily other members are active and will give you links etc.

nearly 5 to 7 mins now.... the bar is inching so i know there is progress how the message area displays hidden.img
Click to expand...
Click to collapse
if its reached hidden.. then its ok.. give it some time.. donot remove the cable till it says pass

ThaiDai said:
This is the normal symptom for a bricked device.
There are many threads with information about it and the possible workaround with repartition (hg42).
I do not have the time now for more details - but luckily other members are active and will give you links etc.
Click to expand...
Click to collapse
thanks for all the help.... the process is making a little progress its slow but still i know its fighting.... isnt it good sign.... if the process completes then what are the chances that the phone will boot??

ritesh.bafna88 said:
thanks for all the help.... the process is making a little progress its slow but still i know its fighting.... isnt it good sign.... if the process completes then what are the chances that the phone will boot??
Click to expand...
Click to collapse
I do not know. but until now it looks like you are not stucked at factoryfs.img.
Then it's not bricked and everything will be ok later. Good Luck.

Galaxy Gear Bricked, Odin always Fail

I've been trying to Flash V700XXUAMK7_V700OXAAMK7_HOME.tar.md5 (BTU) to my Galaxy gear, it got bricked and now I'm sitting in the "Firmware upgrade encountered an issue. Please select Recover mode in Kies & try again."
Well Kies isn't connecting to it and Odin results in a Fail no matter what I try. I've tried it on Odin 3.09, 3.07, 3.04. I've tried resetting but can't get to the download boot or any of that. I've tried different roms, I've tried Kies, and I can't find a way out.
Any help?

Try a different cable? Cheap cables can cause problems

Brendo said:
Try a different cable? Cheap cables can cause problems
Click to expand...
Click to collapse
I'm using the best cable I have.

Also try a different computer,,,

If it helps this is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> V700XXUAMK7_V700OXAAMK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

crutzulee said:
Also try a different computer,,,
Click to expand...
Click to collapse
I tried a different computer, both cords, version 3.09 and 3.07 with the same MK7 file and it throws out the same log I posted.
EDIT: 3.09 Starts to work, then it crashes.

CarbonWyre said:
I tried a different computer, both cords, version 3.09 and 3.07 with the same MK7 file and it throws out the same log I posted.
EDIT: 3.09 Starts to work, then it crashes.
Click to expand...
Click to collapse
sounds like you got a bad download on your MK7 check the file size i bet its wrong.

rob8178 said:
sounds like you got a bad download on your MK7 check the file size i bet its wrong.
Click to expand...
Click to collapse
Where do you recommend downloading it from?

rob8178 said:
sounds like you got a bad download on your MK7 check the file size i bet its wrong.
Click to expand...
Click to collapse
I redownloaded and re unzipped, same thing happened. Odin just crashed after clicking start

CarbonWyre said:
I redownloaded and re unzipped, same thing happened. Odin just crashed after clicking start
Click to expand...
Click to collapse
Has anyone gotten a solution here? I can't get Odin/Kies/Fastboot to bring this back to life. I was trying to flash Tizen and got here instead.
And minutes later Odin makes me a liar and flashes an stock android img onto the little bugger and I am back in business, thanks anyway!!

Same thing happened to me.. you will have to do one of two things. . Search for the tizen downgrade. Sorry don't have link handy. .. or flash the original tizen update not the newest nf1 then flash the nf1 after successful flash... the problem is you flashed the newest nf1 before having the tizen bootloader. .. and right now you are trying to flash android on a jacked up tizen bootloader. .. give me a min to search for you and I will post links
Sent from my SM-G900T using Tapatalk
---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------
Tizen downgrade. ...
http://forum.xda-developers.com/showthread.php?t=2776157
Oh yeah don't forget thanks
Sent from my SM-G900T using Tapatalk
---------- Post added at 01:30 AM ---------- Previous post was at 01:27 AM ----------
Flash this first... then flash NF1 ... and I hope it goes with out saying flash in oden
http://forum.xda-developers.com/showthread.php?t=2767465
Sent from my SM-G900T using Tapatalk

Very Thanks !
Thanks you !
Flash this version of Tizen is only way to back to Tizen after downgrade from Tizen to Android ( i know it isn't very clever )
I try flash many tizen firmwares but, ONLY this working.
Kies Updates doesn't work, only ODIN.

Think I've Bricked My Gear
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please

trisha3010 said:
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please
Click to expand...
Click to collapse
No need to get back to recovery or download mode. Use odin and follow instructions by @fireishott above. I have just restored my gear from the 'Firmware Upgrade Encountered a problem' screen. It should be recognised by odin 3.09. You can try another computer, and also press the power button as if you are rebooting the gear. The screen will go off then you get the 'firmware....' screen again. Ensure you have latest samsung drivers.
Good luck.

trisha3010 said:
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please
Click to expand...
Click to collapse
I used Odin3.07 and 4.2.2 stock ROM to flash first - I used PHONE option because the others didn't work (no progress in the message window). This 'faulty' flash came up with a 'UI stopped working error' when the Gear rebooted but I was able to get it into download mode now. I then used Odin 3.09 and the flashed the 4.2.2 as a PIT which worked fine!
Got there after reading through a lot of XDA threads and trying many things. But in the end, the answers were here. Thanks.
PS how I got into the mess (the firmware error message with the yellow triangle)? I was on null 23 and wanted to go back to stock rom so that I could sell the Gear. Couldn't get into download mode for Odin 3.09; I can't exactly remember what I did but I disconnected the gear midway through a seemingly failed flash and it got me to the error. Googling says use Kies but nope, it wouldn't recognise the gear even for the 'emergency firmware'. I tried a lot of things, and wasted a lot of time!

Big Thanks
chobochobo said:
I used Odin3.07 and 4.2.2 stock ROM to flash first - I used PHONE option because the others didn't work (no progress in the message window). This 'faulty' flash came up with a 'UI stopped working error' when the Gear rebooted but I was able to get it into download mode now. I then used Odin 3.09 and the flashed the 4.2.2 as a PIT which worked fine!
Got there after reading through a lot of XDA threads and trying many things. But in the end, the answers were here. Thanks.
PS how I got into the mess (the firmware error message with the yellow triangle)? I was on null 23 and wanted to go back to stock rom so that I could sell the Gear. Couldn't get into download mode for Odin 3.09; I can't exactly remember what I did but I disconnected the gear midway through a seemingly failed flash and it got me to the error. Googling says use Kies but nope, it wouldn't recognise the gear even for the 'emergency firmware'. I tried a lot of things, and wasted a lot of time!
Click to expand...
Click to collapse
Hi Everyone HUGE thanks managed to follow instructions and gear is back up and working. Just wanted to check I only flashed the tizen downgrade (ie-image 1) and this automatically rebooted the galaxy back to original settings without having to reflash the NF1 is this ok or should i flash this anyway. Many thanks again for the replies as everyone here was telling me it was beyond repair.

i was in the same situation last week kept getting same errors,decided to try different computer and went here and downloaded (http://samsung-updates.com/device/?id=SM-V700) and picked 4.2.2 btu version and went through with no error and got it back up and going

Further Problems
trisha3010 said:
Hi Everyone HUGE thanks managed to follow instructions and gear is back up and working. Just wanted to check I only flashed the tizen downgrade (ie-image 1) and this automatically rebooted the galaxy back to original settings without having to reflash the NF1 is this ok or should i flash this anyway. Many thanks again for the replies as everyone here was telling me it was beyond repair.
Click to expand...
Click to collapse
Hi everyone can't believe this but hit the reset button in the settings app and the gear has now rebooted and stuck on the Samsung screen with nothing working - odin not recognising it and even when i try to reboot in recovery mode it just keeps reverting back to same Samsung screen ... any help or suggestions would be appreciated.

solved for me
shayind4 said:
No need to get back to recovery or download mode. Use odin and follow instructions by @fireishott above. I have just restored my gear from the 'Firmware Upgrade Encountered a problem' screen. It should be recognised by odin 3.09. You can try another computer, and also press the power button as if you are rebooting the gear. The screen will go off then you get the 'firmware....' screen again. Ensure you have latest samsung drivers.
Good luck.
Click to expand...
Click to collapse
solved for me.the problem was that i didnt press the POWER button.

I had same issue after getting stuck on zimage during flashing of Tizen over Null rom. I simple flashed null rom thru odin as a phone rom and it booted back into null rom. Gear is back up and fuctioning.
Sent from my SPH-L900 using XDA Premium 4 mobile app

[Q&A] [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/2

[Q&A] [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/2
Q&A for [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/24
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/24. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Problem Flashing TWRP to T-Mobile Note 4 in ODIN...PLZ HELP
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.

Ttw626 said:
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.
Click to expand...
Click to collapse
Can you try verifying the md5 of the file from the place you downloaded TWRP from?

How do I verify it

re: odin flash issues
Ttw626 said:
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.
Click to expand...
Click to collapse
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!

bigbiff said:
Can you try verifying the md5 of the file from the place you downloaded TWRP from?
Click to expand...
Click to collapse
How do I verify it?
---------- Post added at 02:25 PM ---------- Previous post was at 02:13 PM ----------
Misterjunky said:
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!
Click to expand...
Click to collapse
Misterjunky i think relock is on in the phone ill disable it and try again i didnt think of that before thanks.

Misterjunky said:
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!
Click to expand...
Click to collapse
Great it took this time thanks alot sir :good:

@bigbiff...VZW Note 4 stock recovery image is here....
http://forum.xda-developers.com/showthread.php?p=56385923
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.4.13

nicee 5*

I accidentally wiped my sd card in twrp and now I'm having trouble downloading from a lot of apps. How can I fix this? Would I have to Odin back to a stock firmware to get it back to where it was? Titanium back up and other apps say I have insufficient space, but I know I have a good amount. I reflashed the ROM I've been on and started fresh, but I'm still having issues. Thanks in advanced.

re: titanium backup
paranoid android85 said:
I accidentally wiped my sd card in twrp and now I'm having trouble downloading from a lot of apps. How can I fix this? Would I have to Odin back to a stock firmware to get it back to where it was? Titanium back up and other apps say I have insufficient space, but I know I have a good amount. I reflashed the ROM I've been on and started fresh, but I'm still having issues. Thanks in advanced.
Click to expand...
Click to collapse
Uninstall titanium backup and re-download/install it from the play store then have titanium backup
detect backup location under preferences>backup location in settings then restart titanium backup.
Once you do that it will work fine.
Good luck!

TWRP 2.8.1.0 is not installing on my Tmo Galaxy Note 4
I don't know what's going on guys. I know I am doing everything the right way but for some reason whenever i get back to turning the phone off hitting Vol up/Home/ Power key it takes me to the android boot screen vs the twrp android boot screen.
I am using the img.tar file in odin under the pda option
I have odin set to auto re-boot
i turn the phone off and hit the command
nothing.
Using this twrp in odin
openrecovery-twrp-2.8.4.0-trltetmo.img.tar
if someone can please help me out greatly appreciated.

Is the phone rooted? With bootloader unlocked? Did u use CF auto root?
If so u can flash recovery with FLASHIFY [ https://play.google.com/store/apps/details?id=com.cgollner.flashify] from the play store. Just download the .IMG file for TWRP in the app and let it flash it.
Sent from my SM-N910T using XDA Free mobile app

Thanks for your help man I did end up figuring it out. For some reason the auto reboot was causing the issue. I had to turn that off and manually pull the battery out etc for it to work.
Worked great and I'm now running cm12

thanks for this

I'm guessing twrp 3.0.0 dosent work for the kindle fire (otter) right?

AlbGol said:
I gave you the correct file for what you need to do if you have the n910t, for more specifics look the post above me.
Here is the correct way of installing twrp 3.0 image file, straight from your existing recovery (twrp)
When you boot into your current Recovery 2.8.7.0 and click on Install - Bottom Right you'll see a Image Button - Click on this - The next Screen will show Boot and Recovery - You want to click on Recovery and Swipe to install.
Thats it. (All the phones that I did this were N910T, so was the image file for my device trltmo)
Here is the direct link for twrp 3.0 image file for 910t
https://www.androidfilehost.com/?fid=24407100847294047
Also if u have different model(carrier) just find it here and follow the steps:
http://forum.xda-developers.com/not...-utility-twrp-2-8-1-0-teamwin-t2915588/page44
Click to expand...
Click to collapse
Hey, HUGE problem here. I did this I may have totally bricked my phone. im freaking out.
Please help me
Stuck on recovery booting and cannot even get into download mode. Plugged into comp, I do get a chime .
Is it time to Jtag?
What are my options. Please help

Remove battery, install battery...use button combo to enter download mode and flash 2.87 with odin...
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw

manbat said:
Remove battery, install battery...use button combo to enter download mode and flash 2.87 with odin...
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw
Click to expand...
Click to collapse
Button combo does not work, goes to recovery booting loop. This is the problem. That's the first thing i did. I haven't seen a hard brick on any of my devices in 12 years.

Can't root or install custom recovery - help?? (Note 4 tmo)

Hi, my N910T cannot be rooted. I tried reverting to NJ7 and flashed cf auto root (right file) and it would fail near the end of the process. I tried on COD6 (build number) and it still wouldn't work. I tried installing a custom recovery, and that failed near the end as well. I tried KingRoot on NJ7 (was slightly worried about KingRoot) and it worked (temporarily.) It said failed around 56% but I used root checker and it said I had root. From there I tried using an app like rom manager to try and install and flash a custom recovery. When I booted into recovery, it said something like "Custom Binary blocked by Reactivation lock," with a yellow triangle. I tried to do it multiple times with different apps, each time having to try to revert back to stock because it would be in a boot loop. I also tried NJ7 and NIH. I fixed the custom binary thing, just want to root/install custom recovery. Can anyone help? Sorry if it was kind of hard to follow, went back and forth from time to time. Anyways, thanks! :silly:

Is your device a T3 version? Did you send it in for repairs?
Sent from my SM-N910T using Tapatalk

cyanogen_patrick said:
Hi, my N910T cannot be rooted. I tried reverting to NJ7 and flashed cf auto root (right file) and it would fail near the end of the process. I tried on COD6 (build number) and it still wouldn't work. I tried installing a custom recovery, and that failed near the end as well. I tried KingRoot on NJ7 (was slightly worried about KingRoot) and it worked (temporarily.) It said failed around 56% but I used root checker and it said I had root. From there I tried using an app like rom manager to try and install and flash a custom recovery. When I booted into recovery, it said something like "Custom Binary blocked by Reactivation lock," with a yellow triangle. I tried to do it multiple times with different apps, each time having to try to revert back to stock because it would be in a boot loop. I also tried NJ7 and NIH. I fixed the custom binary thing, just want to root/install custom recovery. Can anyone help? Sorry if it was kind of hard to follow, went back and forth from time to time. Anyways, thanks! :silly:
Click to expand...
Click to collapse
do this, odin cog2, then odin twrp and do a complete flash by going into wipe, advanced wipe then check everything off except the last one which is external sd card, reboot into your system which may take a few minutes and then try to root afterwards using the cf auto root in teks thread

No I didn't, I did that a couple months ago because the finger scanner broke. I'm certain this is the original n910t not the T3, how would I tell?

Pick_A_Name said:
Is your device a T3 version? Did you send it in for repairs?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
No I didn't, I did that a couple months ago because the finger scanner broke. I'm certain this is the original n910t not the T3, how would I tell?

xnknown said:
do this, odin cog2, then odin twrp and do a complete flash by going into wipe, advanced wipe then check everything off except the last one which is external sd card, reboot into your system which may take a few minutes and then try to root afterwards using the cf auto root in teks thread
Click to expand...
Click to collapse
Flashing recovery doesn't work either, thanks for the input though!

cyanogen_patrick said:
No I didn't, I did that a couple months ago because the finger scanner broke. I'm certain this is the original n910t not the T3, how would I tell?
Click to expand...
Click to collapse
Settings> about device> model
Sent from my SM-N910T using Tapatalk

Pick_A_Name said:
Settings> about device> model
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Hahah okay I thought there was another way. I t is an n910t. So how do it root or install recovery on it?

cyanogen_patrick said:
Hahah okay I thought there was another way. I t is an n910t. So how do it root or install recovery on it?
Click to expand...
Click to collapse
Did you try what xnunknown suggested? When in doubt it's always smart to Odin back to stock and start over.
Sent from my SM-N910T using Tapatalk

Pick_A_Name said:
Did you try what xnunknown suggested? When in doubt it's always smart to Odin back to stock and start over.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I tried on NJ7, NIH, and COD6. I didn't flash recovery/cf right as I finished flashing the firmware, I set up the device first. Thanks for the reminder though!

cyanogen_patrick said:
I tried on NJ7, NIH, and COD6. I didn't flash recovery/cf right as I finished flashing the firmware, I set up the device first. Thanks for the reminder though!
Click to expand...
Click to collapse
I'm still saying try following his instructions, which seem to be different than what you're doing.
Sent from my SM-N910T using Tapatalk

Pick_A_Name said:
I'm still saying try following his instructions, which seem to be different than what you're doing.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Okay, I will be back soon.

cyanogen_patrick said:
I tried on NJ7, NIH, and COD6. I didn't flash recovery/cf right as I finished flashing the firmware, I set up the device first. Thanks for the reminder though!
Click to expand...
Click to collapse
odin and then try odining twrp directly afterwards, somethings probably corrupted and you need to wipe the device

Pick_A_Name said:
I'm still saying try following his instructions, which seem to be different than what you're doing.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Didn't work for me.

xnknown said:
do this, odin cog2, then odin twrp and do a complete flash by going into wipe, advanced wipe then check everything off except the last one which is external sd card, reboot into your system which may take a few minutes and then try to root afterwards using the cf auto root in teks thread
Click to expand...
Click to collapse
Sorry for the long wait, completely forgot. It didn't work, thanks! Are there any other ways?

<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've figured out that the Complete(Write) operation keeps failing. Does anyone know how to fix this?

You have disabled the "Reactivation Lock" in Settings > Security??

anasmunir said:
You have disabled the "Reactivation Lock" in Settings > Security??
Click to expand...
Click to collapse
Reactivation lock effects it? I remember I factory resetted my phone and I had to bypass my reactivation lock. I tried to turn it off and it didn't work. I will try again after trying to turn reactivation lock off and I will tell you when I can. Thanks for your help!

anasmunir said:
You have disabled the "Reactivation Lock" in Settings > Security??
Click to expand...
Click to collapse
Reactivation. Lock will not shut off.

Custom Binary blocked by frp lock

So I rooted my phone and rebooted. The OEM unlock must've been disabled somehow, and now I can't get the phone to start up. I tried flashing stock firmware, and it fails with SW REV check fail device 2 binary 1.
I tried getting stock firmware from sammobile but it's always corrupted, despite me watching the download very closely and watching it finish. I tried everything right down to flashing a new bootloader and frp lock blocks all of it. I have scanned google for the past 48 hours and contacted sammobile about the corrupted zip. I haven't gotten anything back yet, but I really want to get this phone fixed asap.
2 questions:
1. what does the error SW REV check fail device 2 binary 1 mean.
2. Can I flash any official firmware or does it have to be my specific firmware, and if I force it what damages are there.
If at all possible, does anyone have a copy of the note 5 rogers (nougat) rom. So I can try to flash something not corrupted.
Any help I can get is appreciated.
On a side note, I haven't been in the rooting scene for a long time (since kitkat) what new developments should I watch out for to prevent further issues.

TheVampkid said:
So I rooted my phone and rebooted. The OEM unlock must've been disabled somehow, and now I can't get the phone to start up. I tried flashing stock firmware, and it fails with SW REV check fail device 2 binary 1.
I tried getting stock firmware from sammobile but it's always corrupted, despite me watching the download very closely and watching it finish. I tried everything right down to flashing a new bootloader and frp lock blocks all of it. I have scanned google for the past 48 hours and contacted sammobile about the corrupted zip. I haven't gotten anything back yet, but I really want to get this phone fixed asap.
2 questions:
1. what does the error SW REV check fail device 2 binary 1 mean.
2. Can I flash any official firmware or does it have to be my specific firmware, and if I force it what damages are there.
If at all possible, does anyone have a copy of the note 5 rogers (nougat) rom. So I can try to flash something not corrupted.
Any help I can get is appreciated.
On a side note, I haven't been in the rooting scene for a long time (since kitkat) what new developments should I watch out for to prevent further issues.
Click to expand...
Click to collapse
You can download the latest stock firmware update N920CXXU3CQE1 For note 5 in samupdate or samsung mobile or any other websites to fix frp lock and the error SW REV check is about the sboot file when you update your phone you update sboot too , so samsung won't let you flash older firmware with older sboot file ....

mala96 said:
You can download the latest stock firmware update
For note 5 in samupdate or any other websites to fix frp lock and the error SW REV check is about the sboot file when you update your phone you update sboot too , so samsung won't let you flash older firmware with older sboot file ....
Click to expand...
Click to collapse
I got an email back from sammobile saying they fixed the file. Downloaded it, flashed it everything works fine now.
Stuff I learned.
1. MAKE SURE YOU DO NOT TURN OFF OEM UNLOCK
2. Always keep a stock backup.
3. first thing you should re-flash bootloader.

TheVampkid said:
I got an email back from sammobile saying they fixed the file. Downloaded it, flashed it everything works fine now.
Stuff I learned.
1. MAKE SURE YOU DO NOT TURN OFF OEM UNLOCK
2. Always keep a stock backup.
3. first thing you should re-flash bootloader.
Click to expand...
Click to collapse
I hope my tips where usefull

mala96 said:
I hope my tips where usefull
Click to expand...
Click to collapse
They were, I already knew about sammobile, but I wasn't particularly trustworthy of the ones you mentioned.
Thanks though.

TheVampkid said:
They were, I already knew about sammobile, but I wasn't particularly trustworthy of the ones you mentioned.
Thanks though.
Click to expand...
Click to collapse
Good to hear that , did you get your phone install the update ???

Yep. Everything work 100%
Made this reply on the phone.

And for anyone who hasn't kept OEM unlock enabled..
Once I ran my battery down to 0% on MM. Upon charging I was FRP locked. Go figure..

mala96 said:
I hope my tips where usefull
Click to expand...
Click to collapse
Hello people. I hope I can get some advice. I seem to have done a REALLY DUMB THING and unchecked the box in developer tools and .... sigh ... turned off OEM lock (there was an instruction about unlocking the screen. I know. DUMB). But now I have a bricked brand new note 5. I am downloading the firmware that should go with my nougat 7.0 and am hoping to be able to use Odin 3.11. I tried to use the Mac version Jodin but that didnt work
Any thoughts> advice? I know ... I screwed up big time and should have known better
Thanks !!!!!

What was the firmware before you bricked it?
I'm not sure what the security is on the frp lock but I'm sure it's either a tag in firmware or checksum. If it's checksum you might be screwed unless you were running stock. Did you update the device to nougat before you turned off the oem unlock?
Try the actual odin. I'm pretty skeptical of other versions. If you need another firmware I still have mine.

TheVampkid said:
What was the firmware before you bricked it?
I'm not sure what the security is on the frp lock but I'm sure it's either a tag in firmware or checksum. If it's checksum you might be screwed unless you were running stock. Did you update the device to nougat before you turned off the oem unlock?
Try the actual odin. I'm pretty skeptical of other versions. If you need another firmware I still have mine.
Click to expand...
Click to collapse
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?

AlvinT said:
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?
Click to expand...
Click to collapse
Extract the zip and try to flash the tar.md5 file.

AlvinT said:
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?
Click to expand...
Click to collapse
You will not be able to use your phone again until you flash a complete firmware via Odin. You, me and many other are having the same problem on the latest Sprint Nougat firmware (DQF1). Heck, I had it twice yesterday until I noticed OEM Unlock was disabled.
Flash the DQF1 via odin, you won't loose personal files like photos but after that the phone will be buggy so you may want to do a factory reset.
I had to ask: https://forum.xda-developers.com/note5/help/fml-custom-binary-blocked-frp-happening-t3637070
And this guy: https://forum.xda-developers.com/note5/help/sm-n920p-frp-fap-lock-help-asap-t3637438
And you.
Fix: Flash a complete stock unmodified firmware via Odin.

TheVampkid said:
Extract the zip and try to flash the tar.md5 file.
Click to expand...
Click to collapse
When I try to extract the zip (on my mac) I get a message that says "unable to expand .... into Downloads". It could of course be a corrupted file, but I dont think so.
Any chance or way of getting to TWRP (maybe odin) and reaching my nandroid backup (which i figured was "insurance" against a screwup"? I could try to odin that, and am thinking of doing ir later
If all fails, do I just throw the phone away? I hate that idea
So, how do I get the firmware that I can flash via Odin???
As always, suggestions welcome.

AlvinT said:
So, how do I get the firmware that I can flash via Odin???.
Click to expand...
Click to collapse
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)

cachanilla86 said:
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)
Click to expand...
Click to collapse
I downloaded that file (it took a long time but I do have it) it's a zip file but when I try to open it my mac says I can;t. I have an old Pc that I installed odin with but for going back and foth and downloading my mac is much faster, (I transfer files to the PC using a USB)
I'll check to see if sammobile has a md5 for their file. But I guess I MUST havve that tar file

AlvinT said:
I downloaded that file (it took a long time but I do have it) it's a zip file but when I try to open it my mac says I can;t. I have an old Pc that I installed odin with but for going back and foth and downloading my mac is much faster, (I transfer files to the PC using a USB)
I'll check to see if sammobile has a md5 for their file. But I guess I MUST havve that tar file
Click to expand...
Click to collapse
Thanks so much but there is now NO NEED
Here's a happy ending: I went to the local NYC Sprint store, the tech guy in charge was terrific, no sermonizing, he took the phone in back and after maybe 15 minutes came back with the very recent (QE1) firmware installed
I have it back, unrooted. But WORKING
Thanks much. And I must say I found the level of service from the Sprint store guy a real relief
Al

cachanilla86 said:
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)
Click to expand...
Click to collapse
Dear, please help me to recover my note 920C. I was running khongloi rom v11 and when i rebooted phone it just got frp lock notification. so i cant reboot it or go into recovery mode. i tried to flash latest firmware from sammobile via odin 3.12.7 but it fails in last step. Please check and help ;((
<ID:0/010> 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/010> Odin engine v(ID:3.1207)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> cm.bin
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img
<ID:0/010> cache.img
<ID:0/010> hidden.img
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Frp lock bypass on galaxy note 5
First of all you have to download firmware combination file for your galaxy note 5 with the same model number as your device have. Then you can easily flash the AP file with odin3 and your phone will turn on..The user interface will appear different but you will be able to access oem unlock feature in developer options.
Then turn of the oem lock.
Then you can download stock u4 firmware with 4 files AP+CP+CSC+BL
and you have to flash all these 4 files while your phone is in download mode.
After the procedure your phone will be unlocked and you are good to go.
I hope that this article would be helpful for all those people who have got their phone blocked by frp lock

Sinankhan.official said:
First of all you have to download firmware combination file for your galaxy note 5 with the same model number as your device have. Then you can easily flash the AP file with odin3 and your phone will turn on..The user interface will appear different but you will be able to access oem unlock feature in developer options.
Then turn of the oem lock.
Then you can download stock u4 firmware with 4 files AP+CP+CSC+BL
and you have to flash all these 4 files while your phone is in download mode.
After the procedure your phone will be unlocked and you are good to go.
I hope that this article would be helpful for all those people who have got their phone blocked by frp lock
Click to expand...
Click to collapse
Is there any way you can help me with this? I've downloaded 3 different firmwares, created a combinary using the tool with each of them but every time I push them via Odin, it gives me "SW REV. CHECK FAIL. DEVICE: 6, BINARY: 1" and the other two times it was BINARY: 2 and BINARY: 4.
What am I doing wrong?
Do I just have to wait for someone to come out with something flashable?...
My RP SWREV is B:6 K:1 S:2
FRP LOCK: ON
SECURE DOWNLOAD: ENABLED