Related
I just got a tmobile note 3, and I tried to flash CM 11 on it, and it keeps bootlooping and it says on the top that kernel is not seandroid enforcing. Any idea how to get the device to boot?
Pandawg said:
I just got a tmobile note 3, and I tried to flash CM 11 on it, and it keeps bootlooping and it says on the top that kernel is not seandroid enforcing. Any idea how to get the device to boot?
Click to expand...
Click to collapse
Hold the volume down button along with the home button and power it on.... should boot in to download mode and just press the volume button down to cancel... hope it works for ya
Pajar0913 said:
Hold the volume down button along with the home button and power it on.... should boot in to download mode and just press the volume button down to cancel... hope it works for ya
Click to expand...
Click to collapse
I got my phone to boot by flashing PAC-Man ROM. If I wanted to flash CM 11 or CM 12 would I have to flash TWRP for hlte? How would I go about doing so if I had to use the TWRP for hlte not for hltemto?
Pandawg said:
I got my phone to boot by flashing PAC-Man ROM. If I wanted to flash CM 11 or CM 12 would I have to flash TWRP for hlte? How would I go about doing so if I had to use the TWRP for hlte not for hltemto?
Click to expand...
Click to collapse
Oh wow, this just happened to me. So for some reason cm11 nightly isn't booting correctly for n900t. However, if you want something close to cm12 I suggest you check out dompop. ( link is below) It is android lollipop and the battery life is extremely good. However, if you really want cyanogenmod, I think you'll have to wait until someone finds out why it keeps bootlooping. It also weird because when I flashed cyanogenmod 11 my phone said the same exact thing. However when I flashed dompop the whole "Kernel is not seandroid enforcing" was gone. So i guess thats an indicator of when you flash a rom correctly. And if you really want to look into it again, I also summited a thread about this and someone gave me advice on it. (second link on the bottom.)
I wish you luck!!! and if you find a solution message me asap please
http://forum.xda-developers.com/not...dompop-0-1-3-stock-tw-lollipop-5-0-1-t2988660
http://forum.xda-developers.com/not...p-flashing-t3004663/post58223475#post58223475
Superbia Thema said:
Oh wow, this just happened to me. So for some reason cm11 nightly isn't booting correctly for n900t. However, if you want something close to cm12 I suggest you check out dompop. ( link is below) It is android lollipop and the battery life is extremely good. However, if you really want cyanogenmod, I think you'll have to wait until someone finds out why it keeps bootlooping. It also weird because when I flashed cyanogenmod 11 my phone said the same exact thing. However when I flashed dompop the whole "Kernel is not seandroid enforcing" was gone. So i guess thats an indicator of when you flash a rom correctly. And if you really want to look into it again, I also summited a thread about this and someone gave me advice on it. (second link on the bottom.)
I wish you luck!!! and if you find a solution message me asap please
http://forum.xda-developers.com/not...dompop-0-1-3-stock-tw-lollipop-5-0-1-t2988660
http://forum.xda-developers.com/not...p-flashing-t3004663/post58223475#post58223475
Click to expand...
Click to collapse
I just flahed hlte TWRP and hlte CM, and I'm running CM 11 fine right now.
There's a CM12 in the international forums that works fine on our phones. Flashed it about two weeks ago, ran it for a week, and I'll probably end up restoring my backup of it in the near future.
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.
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
Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Nairozed said:
Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Click to expand...
Click to collapse
Try use magisk 16.6 for root issues, ofc when you use custom rom you dont get full camera potential and these green flickers are just minor cosmic bugs.
"Myth" might want to read up more.
You need to flash twrp and flash the no verity file then flash the custom rom
Or even better, flash soldiers rom instead of the resurrection remix. Didnt you read that theres a camera problem?
Better use magisk for rooting btw, use the 16.6
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Nairozed said:
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Click to expand...
Click to collapse
try flash rom + gapps and boot system after that boot recovery and flash magisk 16.6 and boot system
Thanks for the advice. I flashed back to stock firmware to have the zerocam mod working perfectly. But now my lockscreen freezes after a few minutes. So I tried to deactivate my phone going into lockscreen. I get the Black screen of Death now instead when the display turns off into sleep mode. Only way out is rebootingby hard reset, power button+volume down.
What can I do?.... Thanks for Any further advice.
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/
Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)