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?
Related
O.K So I am new to Android just switched from the apple side of things.... DUN DUN DUN so, this is watsup, I downloaded doin rooted and downgraded firmware to 4.1.1 to unlock phone, well after unlocking phone the 4.3 ota popped up, I was half asleep inadvertanely upgraded now my phone is soft bricked I believe, I can get into download but not recovery, I have spent 3 days trying to figure this out, I have downgraded my firmware and it says pass on odin but then i get stuck in bootloop i'm guessing where it wont go past the "Samsung note 2" screen. please help me! its a very expensive paperweight and now i'm stuck with no phone, please help I have no idea what to do , all I want is a working phone I will get it factory UNLOCKED LOL!, I dont care, I just need help!
JONKEEFE said:
O.K So I am new to Android just switched from the apple side of things.... DUN DUN DUN so, this is watsup, I downloaded doin rooted and downgraded firmware to 4.1.1 to unlock phone, well after unlocking phone the 4.3 ota popped up, I was half asleep inadvertanely upgraded now my phone is soft bricked I believe, I can get into download but not recovery, I have spent 3 days trying to figure this out, I have downgraded my firmware and it says pass on odin but then i get stuck in bootloop i'm guessing where it wont go past the "Samsung note 2" screen. please help me! its a very expensive paperweight and now i'm stuck with no phone, please help I have no idea what to do , all I want is a working phone I will get it factory UNLOCKED LOL!, I dont care, I just need help!
Click to expand...
Click to collapse
I have never had your issue before but I am hoping I'm leading you in the right direction I would Google how to reset back to stock there's a lot of vids on it on YouTube but here's what I think would fix your problem
Sounds like you need to download a factory image go into download mode plug it into Odin and use the factory image to reset it back to normal, word of advise, just root it and learn about ROMs 4.3 is over rated in my opinion 4.4.2 is the newest we have on the aosp side and it is awesome, I highly recommend beanstalk 4.4.2
Also I found this in another post not sure if it applies to you but I'm sure someone else can confirm or deny
"If you update to 4.3...you WILL have a locked bootloader...and currently no good way to root..
Additionally....your KNOX flag will trip and your warranty is toast...if you attempt to root...( as of today, and until the devs can fix Sammy's latest patch)...
Beyond that...you can never go back to 4.1.2 again...
Stay on a 4.1.2 bootloader without KNOX and then you can flash every rom we have along with a full return to stock if you want...
An update to 4.3 will stop any means of going back."
Sent from my GT-N7105 using Tapatalk
No I have done a ton of research and can't figure it out, I feel like i've tried everything. I keep trying to go to stock rom, used Keis, used Odin, Used Heindal, flashed stock recovery roms, flashed stock combo roms, have like 12 counts of custom binary downloads and KNOC WARRANTY VOID : 1 and in download mode in red at the top it says in Odin Mode and then Red in the bottom after it says (in Gray) KNox warranty void: 1 and
AP SWREV A2 it then says in red again unsupported version under those....
Roms? You need a stock image for it to work totally different
Sent from my GT-N7105 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Did you thank your Developer today?
Do not try this!!!!!!!!!!!!!!!!!!!!!!!!!
Jspex said:
http://forum.xda-developers.com/showthread.php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Did you thank your Developer today?
Click to expand...
Click to collapse
Do NOT try this!!!!
I did, and i bricked my phone!!!!!! You gonna end up with expensive brick. I am noit able to do anything with my phone except for gettinh into download mode, where it says "knox warranty void:1".
Any idea what to do???
fuzio1963 said:
Do NOT try this!!!!
I did, and i bricked my phone!!!!!! You gonna end up with expensive brick. I am noit able to do anything with my phone except for gettinh into download mode, where it says "knox warranty void:1".
Any idea what to do???
Click to expand...
Click to collapse
You did the battery pull part as well? I think the trick is to have your fingers on the buttons first then slide the battery back in to force the recovery but until I try it myself I don't know for sure.
Did you thank your Developer today?
Jspex said:
You did the battery pull part as well? I think the trick is to have your fingers on the buttons first then slide the battery back in to force the recovery but until I try it myself I don't know for sure.
Did you thank your Developer today?
Click to expand...
Click to collapse
Did that right.
I have the same issue..... Had 4.3 ota.... Flashed cwm thru odin. Restarted the phone, it will not boot past the "samsung galaxy note 2" screen. Flashed stock rom thru odin, still stuck at the samsung note 2 screen. I can get into download mode with no issues whatsoever. I cannot get into recovery mode, whether stock or cwm. Nothing. Can I flash another 4.3 or 4.4 rom thru odin? I just need my phone working again..... thanks gentlemen
http://forum.xda-developers.com/show....php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Do this it works. If it does get stuck on the second Samsung logo pull the battery,
Boot into Stock recovery, and do a factory reset.
It will boot the 4.1.1 stock ROM but it will have the MK6 bootloader. You can flash TWRP or CWM thru ODIN and flash other ROMs. 4.3 ROMs is all I have tried.
I've just spent hours doing this. It's almost impossible to brick this phone. If you do brick it you have done something really really fricking stupid.
I've done a lot of stupid ****, and I have always brought it back to life.
dicksteele said:
http://forum.xda-developers.com/show....php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Do this it works. If it does get stuck on the second Samsung logo pull the battery,
Boot into Stock recovery, and do a factory reset.
It will boot the 4.1.1 stock ROM but it will have the MK6 bootloader. You can flash TWRP or CWM thru ODIN and flash other ROMs. 4.3 ROMs is all I have tried.
I've just spent hours doing this. It's almost impossible to brick this phone. If you do brick it you have done something really really fricking stupid.
I've done a lot of stupid ****, and I have always brought it back to life.
Click to expand...
Click to collapse
Yup! Fricking stupid------like upgrading from 4.3 to 4.4.1, then in recovery factory reset, and in ODIN trying to get back to 4.1.1 How stupid is that??? If YOU have done this, would you be able to reboot into recovery????? Try it.........
You probably did something wrong. Im the OP of the How to downgrade 4.3 MK6 to LJ2 and Ive done it many time over.
This is the problem i cant get into recovery mode only download, I flashed the firmware from sammobile and did all the steps but it literally wont let me into recovery to wipe the data, I'm stuck on the first samsung Galaxy Note II screen
Have you guys tried to flash cwm or twrp after flashing 4.1.1? Since all you can get into is dl mode try flashing a custom recovery them attempt the battery pull/recovery step.
Did you thank your Developer today?
Jspex said:
Have you guys tried to flash cwm or twrp after flashing 4.1.1? Since all you can get into is dl mode try flashing a custom recovery them attempt the battery pull/recovery step.
Did you thank your Developer today?
Click to expand...
Click to collapse
Agree. Get into DL mode flash TWRP from here.
http://goo.im/devs/OpenRecovery/t0lteatt
It should boot right into recovery.
---------- Post added at 07:31 AM ---------- Previous post was at 07:19 AM ----------
fuzio1963 said:
Yup! Fricking stupid------like upgrading from 4.3 to 4.4.1, then in recovery factory reset, and in ODIN trying to get back to 4.1.1 How stupid is that??? If YOU have done this, would you be able to reboot into recovery????? Try it.........
Click to expand...
Click to collapse
I personally have done it five times in the last two days. Plus ODIN'd MA4.
Actually I've done it the correct way. I have no idea what you are referring to in your post.
From a non-bootable 4.3 OTA, because I installed a mod from the theme/apps section, I flashed the LJ2 in ODIN. It did not boot. I reread the OP and saw that if it didn't boot, do a factory reset.
I flashed it again in ODIN, probably did not need to, it hung.
I pulled battery, did the power/home/up and got to stock recovery. Factory reset it boots.
Testing different scenarios I got boot loops, reflashed LJ2 and did same procedure.
I found out later from Zen all I had to do was flash a recovery and it would fix the error saying I have an error in my firmware, I need to recover using Kies. There was no need for that.
I understand you all can't get to recovery try flashing a custom recovery from ODIN like suggested above.
dicksteele said:
Agree. Get into DL mode flash TWRP from here.
http://goo.im/devs/OpenRecovery/t0lteatt
It should boot right into recovery.
---------- Post added at 07:31 AM ---------- Previous post was at 07:19 AM ----------
I personally have done it five times in the last two days. Plus ODIN'd MA4.
Actually I've done it the correct way. I have no idea what you are referring to in your post.
From a non-bootable 4.3 OTA, because I installed a mod from the theme/apps section, I flashed the LJ2 in ODIN. It did not boot. I reread the OP and saw that if it didn't boot, do a factory reset.
I flashed it again in ODIN, probably did not need to, it hung.
I pulled battery, did the power/home/up and got to stock recovery. Factory reset it boots.
Testing different scenarios I got boot loops, reflashed LJ2 and did same procedure.
I found out later from Zen all I had to do was flash a recovery and it would fix the error saying I have an error in my firmware, I need to recover using Kies. There was no need for that.
I understand you all can't get to recovery try flashing a custom recovery from ODIN like suggested above.
Click to expand...
Click to collapse
I was trying to say: even I have done this step-by-step, after battery pull out, I still canNOT boot into recovery! Even i flashed recovery into my phone via odin, after flashing 4.1.1 It just shows Galaxy Note II screen.......what is it, you are NOT getting??
fuzio1963 said:
I was trying to say: even I have done this step-by-step, after battery pull out, I still canNOT boot into recovery! Even i flashed recovery into my phone via odin, after flashing 4.1.1 It just shows Galaxy Note II screen.......what is it, you are NOT getting??
Click to expand...
Click to collapse
I can honestly say that I will be done trying to help you with this. What YOU are not getting is we are trying to help YOU fix YOUR mistake.
I understand it is frustrating when you hit a snag that leaves your phone in soft brick form but as EVERY OP states you are doing these things AT YOUR OWN RISK. Getting angry and impatient with those that are trying to help will get you nowhere fast.
Good luck fixing your phone and I really hope you get this figured out.
Did you thank your Developer today?
fuzio1963 said:
I was trying to say: even I have done this step-by-step, after battery pull out, I still canNOT boot into recovery! Even i flashed recovery into my phone via odin, after flashing 4.1.1 It just shows Galaxy Note II screen.......what is it, you are NOT getting??
Click to expand...
Click to collapse
I'm getting from every post I have read that you've done in multiple threads, you don't desire any help.
That's what I get.
EDIT : Damn Jspex beat me to it.
EDIT 2: OP, I'll PM you and give you my contact info and see if we can get you going.
As to not let one person ruin the OPs chances of fixing things here is a good way to get into recovery that does take a little know how. Its always good to know the basics of adb anyway when modding android devices.
http://forum.xda-developers.com/showthread.php?t=1853159
Did you thank your Developer today?
Jspex said:
Last resort:
http://forum.xda-developers.com/showthread.php?t=1853159
Did you thank your Developer today?
Click to expand...
Click to collapse
If your device is not being recognized try a different USB port.
Or from the command prompt;
type "adb kill-server"
then type "adb devices", adb will restart on port 5307.
No quotes of course
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.
allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.
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.
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
dameware said:
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
rlichtefeld said:
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
Click to expand...
Click to collapse
It won't read it because my phone is now too old of a device for the program (2.2.2 or whatever). Thank you very much I'm trying all this right now, finally a firmware download that doesn't take 6 hours because of horrible servers!
I will update on if this works or not, I'm guessing it will
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Lopakas said:
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Click to expand...
Click to collapse
EDIT:
Done and done! It all worked out, thank you thank you!
Now to try cyanogen and my device will be back to beast mode.
Just do what he says and you should be fine; factory reset never did anything for me :/
Let me start by saying I'm new to the Samsung world, I've had HTC android phones ever since the first Hero. That being said, I was able to update my phone to 5.1.1 and use the mostly stock OF7 kernel my phone booted up the first time, starting installing some apps, then decided to reboot it. Now it just goes into the boot screen that say Samsung and in red letters up top it says "Custom Binary blocked by FRP lock". Looking back I know I should have unlocked the bootloader when I had it booted up, but I forgot. Every time I try to flash a stock kernel in Odin, it pops up with the same message, but just says "Custom Binary (Boot) blocked by FRP lock". Is there any way to get my phone to boot up again, or will I have to wait until it's possible to download the 5.1.1 firmware? Even when that download is available will I be able to fix it?
Thanks in advance.
Are you able to flash TWRP in Odin? If you can at least get to TWRP you should be able to flash a custom ROM like Sacs23.
leatherneck6017 said:
Are you able to flash TWRP in Odin? If you can at least get to TWRP you should be able to flash a custom ROM like Sacs23.
Click to expand...
Click to collapse
Thanks for the suggestion, but I've tried flashing TWRP in Odin and it fails and says "Custom Binary (Recovery) blocked from FRP lock".
Bummer. Are you using Odin 3.10.6? If so, then I'm stumped.
leatherneck6017 said:
Bummer. Are you using Odin 3.10.6? If so, then I'm stumped.
Click to expand...
Click to collapse
Sure am, I just hope that flashing the firmware download will work when it's available. Otherwise I guess I'm screwed
How about Kies? Long shot I know...
leatherneck6017 said:
How about Kies? Long shot I know...
Click to expand...
Click to collapse
Just tried Kies and still nothing, this sucks I hate how I can't leave my phones stock
i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable
bhavstech said:
i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable
Click to expand...
Click to collapse
Yeah that would work and I should have done that before I restarted, but I forgot, and now I'm unable to get past the boot splash screen, and can' t access the stock recovery, pretty much the screen I can get to is the Download screen
bbacon said:
Let me start by saying I'm new to the Samsung world, I've had HTC android phones ever since the first Hero. That being said, I was able to update my phone to 5.1.1 and use the mostly stock OF7 kernel my phone booted up the first time, starting installing some apps, then decided to reboot it. Now it just goes into the boot screen that say Samsung and in red letters up top it says "Custom Binary blocked by FRP lock". Looking back I know I should have unlocked the bootloader when I had it booted up, but I forgot. Every time I try to flash a stock kernel in Odin, it pops up with the same message, but just says "Custom Binary (Boot) blocked by FRP lock". Is there any way to get my phone to boot up again, or will I have to wait until it's possible to download the 5.1.1 firmware? Even when that download is available will I be able to fix it?
Thanks in advance.
Click to expand...
Click to collapse
bbacon said:
Yeah that would work and I should have done that before I restarted, but I forgot, and now I'm unable to get past the boot splash screen, and can' t access the stock recovery, pretty much the screen I can get to is the Download screen
Click to expand...
Click to collapse
Did you try the new TAT file of the 5.1.1. It's posted now on here. I had the same thing but I had Asurion insurance and they sent me a new device for $200 deductible.
Mig1234 said:
Did you try the new TAT file of the 5.1.1. It's posted now on here. I had the same thing but I had Asurion insurance and they sent me a new device for $200 deductible.
Click to expand...
Click to collapse
Yup I downloaded the firmware and flashed through ODIN and its all up and running great now. Thanks for the help
bbacon said:
Yup I downloaded the firmware and flashed through ODIN and its all up and running great now. Thanks for the help
Click to expand...
Click to collapse
sorry for the bother but am a bit new to all this. am faced with exactly the same problem. What TAT file are u guys talking about and where can i download it.
Saafir said:
They mean TAR and you can find it here as well as various other threads here on sammobile.com
Click to expand...
Click to collapse
Thanks for the clarification
i have the same problem too, frp lock. i cant do anything, stuck in logo
butterfan214 said:
i have the same problem too, frp lock. i cant do anything, stuck in logo
Click to expand...
Click to collapse
Which version were u on, 5.1 or 5.0
My sm-920T t-mobile Galaxy s6 is now stuck in a boot loop on splash screen
I flashed the new note 5 kernel and firmware that just came out to it and everything was working fine until I restarted my phone and now I'm stuck in just the Samsung Galaxy s6 boot screen can't access anything but download mode do any of you have any useful info or files I may be able to flash through odin to get through this because my phone is now essentially now a locked down brick that was working awesome right before I restarted it for the first time I forget the devs. name who put out the kernel and firmware for the note 5 to work on the s6 but this damned frp block/lock has made my fully paid for s6 I just got a doorstop now and I'm so frustrated anything I'm trying to flash on odin AP. is failing and I'm just so angry. Can someone please swoop in and give me some possibly useful advice so I can get my phone to boot because it was fine..... Till the restart because just one program was f/c but I would've eventually restarted anyway so I guess once I flashed it I was doomed. DEVS PLEASE. I know someone in here has to have had the same problem and conquered it. I've tried everything in my limited repertoire. Thanks alot for any responses. I was on normal 5.1.1 s6 firmware previous was just rooted with custom recovery
Getting the same frp error. Everthing I flash through ODIN fails. Even flashing stock 5.1.1 OF7 fails. I believe it's because I was on OGA so I have to wait until the tarball for that comes out I guess. Unless anyone else has some ideas?
Try using ODIN to reload the bootloader. Google the how, there are many posts.
Hope it helps. That's what I did to get mine to work.
same-ish stuffs
So I have a new s6 on a sprint plan. Was stuck in like a boot loop with the same message in nice red letters kept coming up on the load screen. I was on OGA and had just tried to implement TWRP via the playstore. This started the boot loop. after reflashing the original rootof7.tar i had managed to get it break-free with a factory reset on TWRP(which was now working), only to have the battery die before I had a chance to do anything. after I had got it on a charger it started with the charge battery icon and the red FRP lock message. It would basically just loop there going no further unless i tried to full reset(all buttons) or download mode. Could not flash anything via odin (only recieved error messeges). Took to Bestbuy and after some shuffling around(geeksquad is terribad) I managed to get the Samsung guy to flash a stock OF7 and it works fine now. No more root or twrp and the knox reads 0x1, bu the phone is working now
tupac unincorn said:
So I have a new s6 on a sprint plan. Was stuck in like a boot loop with the same message in nice red letters kept coming up on the load screen. I was on OGA and had just tried to implement TWRP via the playstore. This started the boot loop. after reflashing the original rootof7.tar i had managed to get it break-free with a factory reset on TWRP(which was now working), only to have the battery die before I had a chance to do anything. after I had got it on a charger it started with the charge battery icon and the red FRP lock message. It would basically just loop there going no further unless i tried to full reset(all buttons) or download mode. Could not flash anything via odin (only recieved error messeges). Took to Bestbuy and after some shuffling around(geeksquad is terribad) I managed to get the Samsung guy to flash a stock OF7 and it works fine now. No more root or twrp and the knox reads 0x1, bu the phone is working now
Click to expand...
Click to collapse
can you tell me which stock rom did you use please.