Develop Bugs

[Q] Stuck in boot loop, trying to return to stock, I think I need to use PIT file

Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.

i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.

edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.

invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.

Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?

invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.

Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!

invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^

Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!

invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S

Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.

invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk

Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.

Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)

mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.

mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem

same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally

woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop

[Q] N7100 stuck at boot screen after flashing stock 4.4.2

Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy

beardyweirdy said:
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
Click to expand...
Click to collapse
What happens when you try to reflash the stock 4.4.2 firmware via odin that u downloaded?

beardyweirdy said:
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
Click to expand...
Click to collapse
Have you tried flashing TWRP instead? This happened to me and got stuck on recovery boot, CWM and Philz Touch wonb't load. Flashed TWRP and worked like a charm.

I am having similar problem.
Tried to flash the TWRP Recovery from THIS via Odin.
Still phone isn't going past the Galaxy Note II logo.

Sidz4u said:
What happens when you try to reflash the stock 4.4.2 firmware via odin that u downloaded?
Click to expand...
Click to collapse
Thanks for the reply.
It processes OK and Odin says 'Pass!', but then it automatically restarts and gets stuck at the boot screen again. Still can't boot into recovery mode.

AliverMD said:
Have you tried flashing TWRP instead? This happened to me and got stuck on recovery boot, CWM and Philz Touch wonb't load. Flashed TWRP and worked like a charm.
Click to expand...
Click to collapse
Thanks for the suggestion. Just tried that, but unfortunately it just does the same thing ....

Man do this.....
Get older odin (personally my preferance nothing else)
Flash the latest stock rom that u have
It will say pass and the device will go into bootloop
Now remove battery any stick it in (just to stop bootloops)
Enter recovery (that shld be stock now)
And do a factory reset
If no recovery......get a custom one and do it
Then let the phone do its thing:good::good:
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
If u have any wifi or other issues.....flash the new bootloader. ....with AP not the BL...and done....
Hope this helps......cheers:good:

devrog17 said:
Man do this.....
Get older odin (personally my preferance nothing else)
Flash the latest stock rom that u have
It will say pass and the device will go into bootloop
Now remove battery any stick it in (just to stop bootloops)
Enter recovery (that shld be stock now)
And do a factory reset
If no recovery......get a custom one and do it
Then let the phone do its thing:good::good:
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
If u have any wifi or other issues.....flash the new bootloader. ....with AP not the BL...and done....
Hope this helps......cheers:good:
Click to expand...
Click to collapse
Thanks for the suggestion. I've tried doing just that (although not on an older version of Odin) and it hasn't helped, I can't get into recovery.
I will give flashing the Bootloader a go via the AP rather than BL when I get back from work tonight though. Cheers.

beardyweirdy said:
Thanks for the suggestion. I've tried doing just that (although not on an older version of Odin) and it hasn't helped, I can't get into recovery.
I will give flashing the Bootloader a go via the AP rather than BL when I get back from work tonight though. Cheers.
Click to expand...
Click to collapse
Yes try with older odin.......and also flashing bl via AP
Hope it helps......
DO HIT THAT THANKS BUTTON IF U FEEL I TRIED TO HELP U......

devrog17 said:
Yes try with older odin.......and also flashing bl via AP
Hope it helps......
DO HIT THAT THANKS BUTTON IF U FEEL I TRIED TO HELP U......
Click to expand...
Click to collapse
Just tried, but to no avail again. Thanks anyway. Anybody else got any suggestions as to what I might try? I'm starting to lose hope a bit here

Try to boot in recovery and do a factory reset

devrog17 said:
Try to boot in recovery and do a factory reset
Click to expand...
Click to collapse
Hi, I do appreciate you're only trying to help but, as explained numerous times in the thread, that's my whole problem.
In summary:
The phone gets stuck on the boot screen
I can't boot into recovery
I can only get into the odin download screen
Flashing a full stock rom doesn't change anything
Flashing Philz, TWRP or CW Recovery doesn't change anything
Reflashing the bootloader doesn't change anything

C
beardyweirdy said:
Hi, I do appreciate you're only trying to help but, as explained numerous times in the thread, that's my whole problem.
In summary:
The phone gets stuck on the boot screen
I can't boot into recovery
I can only get into the odin download screen
Flashing a full stock rom doesn't change anything
Flashing Philz, TWRP or CW Recovery doesn't change anything
Reflashing the bootloader doesn't change anything
Click to expand...
Click to collapse
Just to close this thread off, I've now paid to get the phone sorted at a local shop. Took them a while (think their first level support just tried all the things I'd already done), but their occasional staff member and all round guru managed to get it sorted. I don't know what he did as I didn't get the chance to speak to him. Cost me £30.

[Q] Custom Binary blocked by Reactivation Block (Help!!! Please.)

Or... "How I was dumb".
I have a Sprint Note 4 (SM-910P) that I have had rooted for the past few months. I got interested in the new update that was release this month, so I flashed back to stock, ran the updates, and re-rooted over the weekend. I also decided to activate that new "Reactivation Lock" feature (you can see where this is going).
So it occurred to me that I had not reinstalled Cerberus, so downloaded the APK and went to boot into recovery so I could install it to root. I forgot to turn off my "Reactivation Lock", so it booted to a black screen with a yellow triangle and the message: "Custom Binary blocked by Reactivation Block. Secure Fail: Recovery". Pressing the power button turns the phone off. Trying to boot into recovery produces the same error. I can still boot into download mode.
I have been doing some research on how to fix this, and have found two suggested fixes, neither of which work for me:
Fix 1 tells me to boot into download mode, pull the battery, reinsert the battery, and the phone should boot up normally. This doesn't work.
Fix 2 tells me to boot into download mode, and flash to stock with Odin. I have downloaded the stock .tar and tried to flash it with Odin 3.10. I get a fail message. (Full Disclosure: I have only tried Fix 2 on my work test PC. It is an old Vista box that is very slow. I don't know if that is a contributing factor.)
I was hoping that some of you folks had some advice for me. I have all of my data backed up, so I'm not worried about starting over with a clean slate. I'm also not worried about tripping KNOX. That ship has sailed at this point. I just want my phone back.

thescreg said:
Or... "How I was dumb".
I have a Sprint Note 4 (SM-910P) that I have had rooted for the past few months. I got interested in the new update that was release this month, so I flashed back to stock, ran the updates, and re-rooted over the weekend. I also decided to activate that new "Reactivation Lock" feature (you can see where this is going).
So it occurred to me that I had not reinstalled Cerberus, so downloaded the APK and went to boot into recovery so I could install it to root. I forgot to turn off my "Reactivation Lock", so it booted to a black screen with a yellow triangle and the message: "Custom Binary blocked by Reactivation Block. Secure Fail: Recovery". Pressing the power button turns the phone off. Trying to boot into recovery produces the same error. I can still boot into download mode.
I have been doing some research on how to fix this, and have found two suggested fixes, neither of which work for me:
Fix 1 tells me to boot into download mode, pull the battery, reinsert the battery, and the phone should boot up normally. This doesn't work.
Fix 2 tells me to boot into download mode, and flash to stock with Odin. I have downloaded the stock .tar and tried to flash it with Odin 3.10. I get a fail message. (Full Disclosure: I have only tried Fix 2 on my work test PC. It is an old Vista box that is very slow. I don't know if that is a contributing factor.)
I was hoping that some of you folks had some advice for me. I have all of my data backed up, so I'm not worried about starting over with a clean slate. I'm also not worried about tripping KNOX. That ship has sailed at this point. I just want my phone back.
Click to expand...
Click to collapse
You updated to oe1. You need to get someones oe1 backup. As far as the lock out. Im not sure. I believe you can fix it from samsung site login to the device lock page? Not even sure it exists. But once you boot you should have the security option to enter your credentials. So just look on the thread about oe1 update. Someone posted a backup.
Sent from my SM-N910P using XDA Free mobile app

Well think ice broken through the oem bs i got 3 devs looking it a workaround the get ofin up

I FIXED IT!
Here is what I did. I got home, and reread some of the stuff that I found. I was going through a step-by-step provided by Xharky.
http://forum.xda-developers.com/showpost.php?p=53920665&postcount=25
Xharky said that it didn't really matter what you flashed in Odin, that you would probably get an error and that the phone would boot normally after a battery pull. So when I tried flashing the stock .tar with Odin 3.10, it failed, but the phone didn't boot back up; wrote off that fix.
When I got home, I sat down and thought it all out. Odin 3.09 has never worked well for me, and I had never used 3.10 before today. However, I haven't had any problems with Odin 3.07. So I fired it up, and flashed CF Auto Root. Sure enough, I got a fail result in Odin. I did a battery pull and rebooted... And my phone booted right up. I promptly got into my security settings and deactivated that damn Reactivation Block.

thescreg said:
I FIXED IT!
Here is what I did. I got home, and reread some of the stuff that I found. I was going through a step-by-step provided by Xharky.
http://forum.xda-developers.com/showpost.php?p=53920665&postcount=25
Xharky said that it didn't really matter what you flashed in Odin, that you would probably get an error and that the phone would boot normally after a battery pull. So when I tried flashing the stock .tar with Odin 3.10, it failed, but the phone didn't boot back up; wrote off that fix.
When I got home, I sat down and thought it all out. Odin 3.09 has never worked well for me, and I had never used 3.10 before today. However, I haven't had any problems with Odin 3.07. So I fired it up, and flashed CF Auto Root. Sure enough, I got a fail result in Odin. I did a battery pull and rebooted... And my phone booted right up. I promptly got into my security settings and deactivated that damn Reactivation Block.
Click to expand...
Click to collapse
Awesome bro. Thats what i like to hear. A true android heart. Im on the "beat the OE1" task in my head. Im running options and scouring. Lol.
Sent from my SM-N910P using XDA Free mobile app

Yea i beat oe1 also i downgraded

pbedard have you successfully downgraded from the OE1 update back to NK2 or OB7? I took the OE1 update two days after it came out. I didn't research it didn't make a nandroid like an idiot after I updated to OE1. Once I took it I decided I didnt like it so I Odin'd the official NK2 tar it failed then i proceeded to boot twrp recovery restore my NK2 backup I had before I odin'd the offical OB7 tar to take the OE1. Then we have Bootloop. I managed to flash the bobcat rom only I didnt flash the separate theme zip with it like you're supposed to but it's been working for now, not without bugs and a fc of apps every now and then. In my about device it states software OE1, baseband OE1, android version 4.4.4, kernel version 3.10.5-AELKernel-v5.5, and build number KTU84P.N910PVPU1ANK2. I'm guessing I'm just going to have to wait until the OE1 tar is out and just deal with the stockness of it until devs get their OE1 roms out. Thanks in advance if you have any input or thoughts on this depressing matter.

I got a new phone now from sprint i made it look like a softwsre issue

pbedard said:
I got a new phone now from sprint i made it look like a softwsre issue
Click to expand...
Click to collapse
How did you get a stock recovery. Store tried to factory reset mines and when they saw TWRP they new it was rooted, so vioded. If I can get stock recovery then i can fool them, lol. If you have any let me know, thanks in advance.

I backed it up with flashify
---------- Post added at 04:48 AM ---------- Previous post was at 04:47 AM ----------
If u know gow to use it ill give u a copy im not responsible thoigh if u hurt your device

I'd be willing to try it. I know exactly what store to take it too.

christophfloor said:
I'd be willing to try it. I know exactly what store to take it too.
Click to expand...
Click to collapse
Careful. A neighbor of mine did this once. Took about a month. His replacement after a couple of weeks stopped getting signal. He called the carrier and they said the phone he sent in was found flagged by asurion. Which they sent a note to his account. So his new phone was blacklisted until he paid for the brick. Take caution. They are catching on. Not saying this will surely happen but if people keep brick returning this will only get worse. Just a heads up. I have never returned a brick but I have returned rooted.
Sent from my SM-N910P using XDA Free mobile app

flynhawn2002 said:
How did you get a stock recovery. Store tried to factory reset mines and when they saw TWRP they new it was rooted, so vioded. If I can get stock recovery then i can fool them, lol. If you have any let me know, thanks in advance.
Click to expand...
Click to collapse
Well, here's a link to a flashable stock recovery zip for OB7 that I put together for you if it would help.
It is what it is... Flash at your own peril ...
RE-EDIT:
OB7 Stock Recovery Here
This IS a flashable ZIP
I'm still looking for the OE1 OTA update zip... Anyone have it?

[Q] Any help please i have a big problem G925T

Hello friends, I have a big problem, I had my S6 edge with root in version 5.0.2, and wanted to upgrade to version 5.1.1, is the download version of SamMobile.
When the install had no error with ODIN, but when I start not pass "Samsung S6 edge powered by Android" To me this was strange to me, so I wanted to regain root, put it on, and start the cell as it should do, but when you restart to be installed on "kernel", the phone will not start, the left turned on the screen, but now with a message in red "(boot) blocked by FAP lock".
Then I went to put the original Samsung software (downloaded from SamMobile) and the same thing happened again, he would not turn on the phone, and to this day has not on, any solution would appreciate it pretty please

pablo5530 said:
Hello friends, I have a big problem, I had my S6 edge with root in version 5.0.2, and wanted to upgrade to version 5.1.1, is the download version of SamMobile.
When the install had no error with ODIN, but when I start not pass "Samsung S6 edge powered by Android" To me this was strange to me, so I wanted to regain root, put it on, and start the cell as it should do, but when you restart to be installed on "kernel", the phone will not start, the left turned on the screen, but now with a message in red "(boot) blocked by FAP lock".
Then I went to put the original Samsung software (downloaded from SamMobile) and the same thing happened again, he would not turn on the phone, and to this day has not on, any solution would appreciate it pretty please
Click to expand...
Click to collapse
Looks like you didn't disable the activation lock and unlock bootloader in developer options before attempting root. After you odin the 5.1.1 have you tried booting it into stock recovery immediately after? Try wiping the phone in there factory reset.

steve97ta said:
Looks like you didn't disable the activation lock and unlock bootloader in developer options before attempting root. After you odin the 5.1.1 have you tried booting it into stock recovery immediately after? Try wiping the phone in there factory reset.
Click to expand...
Click to collapse
hi bro, i do not remember if deselect, I think not clear, but I can not see if this down or not, because the phone does not turn on, and try to reboot in recovery mod wipe data /factory reset, and dropped it back software, but it has not worked /: ....

As the phone natzy would say "No phone for you" ?.
If you odined 5.1.1 you may be Sol, some users that did the official ota update have recovered from this by flashing stock firmware, but those that updated to 5.1.1 using Odin have not had any luck recovering from FRP lock.
Pp.

PanchoPlanet said:
As the phone natzy would say "No phone for you" .
If you odined 5.1.1 you may be Sol, some users that did the official ota update have recovered from this by flashing stock firmware, but those that updated to 5.1.1 using Odin have not had any luck recovering from FRP lock.
Pp.
Click to expand...
Click to collapse
it's ruined

tmobile galaxy s6 edge g925t, missing OS. HELP!!!

I recently rooted my galaxy s6 edge g925t and was successful, but i couldn't stop there, i wanted to upgrade to android 6.0. i spent hours searching for a custom ROM/firmware and found one that i thought would work. I installed that custom OS through TWRP installer. After i finished the installation i tried to restart the phone but it just stayed at the "Samsung Galaxy S6 EDGE" boot logo and didn't play the boot animation. I searched online for ways of unbricking the phone and i eventually got to the recovery mode and tried to wipe the internal storage. then i restarted the phone and was back to the same Samsung logo. I again tried to get back to the recovery mode, but this time i did an advanced wipe and i ended up deleting the OS. if tried installing the stock ROM/firmware via Odin but can't get it to work. Is there anything i can still do? Can anyone please help me?

What happens when you try and flash the Odin image? The Rom you flashed, did that flash a new bootloader or firmware? If so it might have messed up the partitions on the phone.

M9x3mos said:
What happens when you try and flash the Odin image? The Rom you flashed, did that flash a new bootloader or firmware? If so it might have messed up the partitions on the phone.
Click to expand...
Click to collapse
The phone doesn't accept that either.

What custom ROM did you install? And what stock ROM did you try to ODIN flash?

Also, what is happening when you do that. I gathered out didn't work, but what error comes up?

zabrador said:
What custom ROM did you install? And what stock ROM did you try to ODIN flash?
Click to expand...
Click to collapse
TyrannusRomV23.1.zip is the custom rom, and SM-G925T_1_20150327095252_d1ygbqk7km (1) is the name of the stock i tried.
also the error that ODIN shows is that it FAILed and the phone shows in red letters in the top corner "check fail. DEVICE: 3, BINARY: 1
i dont know the entire message from the phone b/c my screen is blacked out in the top corner, but thats what i can see.

micahtjosaas said:
TyrannusRomV23.1.zip is the custom rom, and SM-G925T_1_20150327095252_d1ygbqk7km (1) is the name of the stock i tried.
also the error that ODIN shows is that it FAILed and the phone shows in red letters in the top corner "check fail. DEVICE: 3, BINARY: 1
i dont know the entire message from the phone b/c my screen is blacked out in the top corner, but thats what i can see.
Click to expand...
Click to collapse
Yeah, I don't think TyrannusRom is runnable on a G925T :/
Flashing stock with ODIN should do the trick. It's hard to tell where that stock file is from, so I would try to download the latest directly from SamMobile here (this is specifically for the G925T). If it's still not working, copy/paste the error ODIN is giving you here if you can.
Also, this thread seems to suggest you might be able to just re-flash the bootloader.

THANK YOU so much!!! that worked, iv looke on sammobile before but couldn't get anything to work, thanks so much

micahtjosaas said:
THANK YOU so much!!! that worked, iv looke on sammobile before but couldn't get anything to work, thanks so much
Click to expand...
Click to collapse
No problem! Glad you're back up and running