I was stupid and used the wrong root for my tablet and now I get a constant "Recovery is not seandroid enforcing" message.
Question is, i tried holding the power button down for a bout a minute straight and nothing happens, screen still wont turn off. any suggestions?
I have a Galaxy Tab s2 8.0
EDIT: got it to reboot into download mode again, but I cant find any odin flash-able stock roms that wont fail.
EveMercury said:
I was stupid and used the wrong root for my tablet and now I get a constant "Recovery is not seandroid enforcing" message.
Question is, i tried holding the power button down for a bout a minute straight and nothing happens, screen still wont turn off. any suggestions?
I have a Galaxy Tab s2 8.0
EDIT: got it to reboot into download mode again, but I cant find any odin flash-able stock roms that wont fail.
Click to expand...
Click to collapse
Which model tab s2 do you have? T713 or...
I have the SM-T710 USA
EveMercury said:
I have the SM-T710 USA
Click to expand...
Click to collapse
You need to be more specific, which carrier?
WiFi Only
EveMercury said:
WiFi Only
Click to expand...
Click to collapse
http://updato.com/firmware-archive-select-model?record=77445CD6E1FB11E69215FA163EE8F90B
ashyx said:
http://updato.com/firmware-archive-select-model?record=77445CD6E1FB11E69215FA163EE8F90B
Click to expand...
Click to collapse
Thanks, I'll update the post when I get home Monday if it works or not.
Related
Hi Guys!
Yesterday I change the Sim Card on my phone. I power off it normaly and change the SIM. When I try to boot the phone again this didn't boot.
My case is the same as in this video, but I did not try to flash the device before (In the explanation of the video, the user says that he tried to flash a custom rom, In my case it was the original rom)
I had to attach a txt with link to Youtube (sorry)
I try to Flash with Odin. Apparently Odin flash the device correctly (with de original firm). But the result is the same, don't boot.
Anyone else did the same?
Is the display turning on?
If yes, where does it hang?
If no, it's a hardbrick and your ace is dead.
Sent from my GT-S5830 using Tapatalk 2
(Frank) said:
Is the display turning on?
If yes, where does it hang?
If no, it's a hardbrick and your ace is dead.
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
Yes, the display turn on (same as you watch in the end on the vídeo); the device turn on the screen and then turn off (< 1 sec) and don't shown nothing (No Samung Logo or Galaxy ACE...) . But the phone boot in "downloading ..." mode and "RAMDUMP" mode.
Thanks for your reply :good:
gokuhs said:
Yes, the display turn on (same as you watch in the end on the vídeo); the device turn on the screen and then turn off (< 1 sec) and don't shown nothing (No Samung Logo or Galaxy ACE...) . But the phone boot in "downloading ..." mode and "RAMDUMP" mode.
Thanks for your reply :good:
Click to expand...
Click to collapse
Do you reach revovery? Home+power button. If yes, do a factory reset, and reboot. It should work.
If this doesen't help try flashing this firmware with odin XWKB7. It's 2.2.1 Froyo (4 files and multi-CSC, how to: http://droidangel.blogspot.hu/2011/05/samsung-galaxy-ace-s5830-original-stock.html), and after that flash a 2.3.6 firmware.
kmarci said:
Do you reach revovery? Home+power button. If yes, do a factory reset, and reboot. It should work.
Click to expand...
Click to collapse
No, the phone don't boot in recovery.
I like to try the first firmware in the first link (to hotfile) but it's down. Can you send me in a PM? Thanks!
gokuhs said:
No, the phone don't boot in recovery.
I like to try the first firmware in the first link (to hotfile) but it's down. Can you send me in a PM? Thanks!
Click to expand...
Click to collapse
I'm working right now, so I can not open a lot of sites. Use google, search for XWKB7. I guess, you will find a working link.
kmarci said:
I'm working right now, so I can not open a lot of sites. Use google, search for XWKB7. I guess, you will find a working link.
Click to expand...
Click to collapse
Yes, sorry I use google and I find them. And I flashed with Odin and he situation did not change. The phone don't boot. .
Tanks for your Replies!
i think as per your comments....your phone's hardware is damaged internally...as you have no try to flash a rom...how is it possible ? to brick a phone ? go to samsung service center and get it repaired...
asking said:
i think as per your comments....your phone's hardware is damaged internally...as you have no try to flash a rom...how is it possible ? to brick a phone ? go to samsung service center and get it repaired...
Click to expand...
Click to collapse
Yeah, maybe that's the right way. Bring it to the service, but do not tell them anything about odin and firmwares, even about sim card. Just tell them that you used the phone it suddenly stop responding than turn itself off, and since than you cannot turn it on... Or something like that.
Thanks guys!
This afternoon I will send the phone to Samsung to give me budget...
Thanks for your replies!
I can get it into download mode + recovery mode, but keeps rebooting at logo. tried factory wipe. completely stock.
here's a picture
]http://dl-1.va.us.xda-developers.com/2/9/2/8/2/6/9/10668416_829527553754164_1709046890_n.jpg?key=2NJxF1hr-LOFooxPNFDfCA&ts=1410111073
anybody got any idea?
just put it through odin, flashed cf root and everything ok but still just boots to samsung logo and repeats. what should i do
UrbanDesigns said:
I can get it into download mode + recovery mode, but keeps rebooting at logo. tried factory wipe. completely stock.
here's a picture
]http://dl-1.va.us.xda-developers.com/2/9/2/8/2/6/9/10668416_829527553754164_1709046890_n.jpg?key=2NJxF1hr-LOFooxPNFDfCA&ts=1410111073
anybody got any idea?
just put it through odin, flashed cf root and everything ok but still just boots to samsung logo and repeats. what should i do
Click to expand...
Click to collapse
Do any error messages appear on the stock recovery screen?
ArkThompson said:
Do any error messages appear on the stock recovery screen?
Click to expand...
Click to collapse
nope but it shows the android bot open with a red !
UrbanDesigns said:
nope but it shows the android bot open with a red !
Click to expand...
Click to collapse
Have you tried flashing stock firmware through Odin? You can find it at http://www.sammobile.com/firmwares/
ArkThompson said:
Have you tried flashing stock firmware through Odin? You can find it at http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
nope but I tried the basic root firmware, wouldn't really make a difference would it?
i know it's not a power switch issue as well because the phone only boots up when i press the button, not on its own
UrbanDesigns said:
nope but I tried the basic root firmware, wouldn't really make a difference would it?
i know it's not a power switch issue as well because the phone only boots up when i press the button, not on its own
Click to expand...
Click to collapse
What? CF-Auto-Root is just something that roots your phone. Flashing stock firmware is completely different.
Try plugging your phone into a PC and use Kies to restore your firmware to defaults.
This stupid device does not want to boot to download or recovery mode. Also it does not boot normally, it just stucks at "Samsung Galaxy S Advance GT-I9070" screen (you know).
bump
Fubseiz said:
This stupid device does not want to boot to download or recovery mode. Also it does not boot normally, it just stucks at "Samsung Galaxy S Advance GT-I9070" screen (you know).
Click to expand...
Click to collapse
Does it charge?
Tech x 125 said:
Does it charge?
Click to expand...
Click to collapse
Seems to not.
Maybe some problem with your battery check it out.Well I had the same problem but it did got to the download mode
Hey, I tried rooting my phone using Odin and my phone is now stuck in the boot screen which just has the Samsung Galaxy S6 logo and powered by android written. Meanwhile there's a small message in red at the very top which reads "RECOVERY IS NOT SEANDROID ENFORCING". right now all i want to do is to get my phone back to normal but i do not want to lose all of my files which i currently have on it because i can't afford to lose them. which would be the best way to do so?
Please help
Many thanks,
-Unidentified73
re s6
unidentified73 said:
Hey, I tried rooting my phone using Odin and my phone is now stuck in the boot screen which just has the Samsung Galaxy S6 logo and powered by android written. Meanwhile there's a small message in red at the very top which reads "RECOVERY IS NOT SEANDROID ENFORCING". right now all i want to do is to get my phone back to normal but i do not want to lose all of my files which i currently have on it because i can't afford to lose them. which would be the best way to do so?
Please help
Many thanks,
-Unidentified73
Click to expand...
Click to collapse
have you tried flashing stock firmware then do factory reset, I heard this can help,it seems like you have some currupt boot on your phone sector
unidentified73 said:
Hey, I tried rooting my phone using Odin and my phone is now stuck in the boot screen which just has the Samsung Galaxy S6 logo and powered by android written. Meanwhile there's a small message in red at the very top which reads "RECOVERY IS NOT SEANDROID ENFORCING". right now all i want to do is to get my phone back to normal but i do not want to lose all of my files which i currently have on it because i can't afford to lose them. which would be the best way to do so?
Please help
Many thanks,
-Unidentified73
Click to expand...
Click to collapse
You'll need to download the original G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5 firmware and then flash that in Odin.
After that completes then flash the twrp-3.0.2-1-zeroflte.tar.md5 file in Odin as well.
Copy the BETA-SuperSU-v2.68-20160228150503.zip file to your device and then boot to TWRP recovery and install this.
guys need help
i flashed twrp and after successful attempts to go to recovery from download mode directly, it finally went into recovery but before recovery could boot up i saw this at the top "recovery is not seandroid enforcing"
anyways twrp came online and i wiped the data, but now i cant push the dm verity file from pc via both mtp or adb
tried all usb ports, different wire, different pc.
i can create and delete folders but cant send file and without that, my phone stays in bootloop.
i can go into recovery and go into download mode
what should i do?
please reply. my hands are shaking badly
danveer said:
guys need help
i flashed twrp and after successful attempts to go to recovery from download mode directly, it finally went into recovery but before recovery could boot up i saw this at the top "recovery is not seandroid enforcing"
anyways twrp came online and i wiped the data, but now i cant push the dm verity file from pc via both mtp or adb
tried all usb ports, different wire, different pc.
i can create and delete folders but cant send file and without that, my phone stays in bootloop.
i can go into recovery and go into download mode
what should i do?
please reply. my hands are shaking badly
Click to expand...
Click to collapse
That message is fine. Been on mine since day one....
You need to go back into download mode a Odin back to stock.
EDIT: Why are you wanting to mess with dm verity ?
The Sickness said:
That message is fine. Been on mine since day one....
You need to go back into download mode a Odin back to stock.
EDIT: Why are you wanting to mess with dm verity ?
Click to expand...
Click to collapse
I flashed twrp and after that system wasnt booting up
I read in a recovery form ( http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8 that mm introduced verity checks so it can only be disabled if i flash something that disables it..and hence get out of bootloops...
I was making a mistake using adb sideload.. once i corrected the command, everything works...
P.s. its great to see a reply from a dev like you...
"RECOVERY IS NOT SEANDROID ENFORCING" is a normal message when you have a custom recovery installed. Ignore it. It simply means the recovery image did not pass the bootloader's security check; this does not affect your ability to flash ROMs or use your phone.
socal87 said:
"RECOVERY IS NOT SEANDROID ENFORCING" is a normal message when you have a custom recovery installed. Ignore it. It simply means the recovery image did not pass the bootloader's security check; this does not affect your ability to flash ROMs or use your phone.
Click to expand...
Click to collapse
CAn you please be more specific? my phone is showing "RECOVERY IS NOT SEANDROID ENFORCING" do I have to flash a stock rom first or I can flash another custom rom through odin?
Thank you
tuffmek said:
CAn you please be more specific? my phone is showing "RECOVERY IS NOT SEANDROID ENFORCING" do I have to flash a stock rom first or I can flash another custom rom through odin?
Thank you
Click to expand...
Click to collapse
Ignore it...it affects nothing
The Sickness said:
Ignore it...it affects nothing
Click to expand...
Click to collapse
sorry for asking again but i see kernel is not seandroid enforcer on the samsung screen when the phone turns on, it happened after I fleshed a custom rom. should I just wait until it loads or what do you mean it effects nothing?
thank you
tuffmek said:
sorry for asking again but i see kernel is not seandroid enforcer on the samsung screen when the phone turns on, it happened after I fleshed a custom rom. should I just wait until it loads or what do you mean it effects nothing?
thank you
Click to expand...
Click to collapse
Some kernels like stock will have that message in red. My kernels do not.
It affects nothing is pretty straight forward. Did your phone boot? Notice any issues?
It's easy to remove the warning when it goes to recovery. But that means it must be complied with that change.
The Sickness said:
Some kernels like stock will have that message in red. My kernels do not.
It affects nothing is pretty straight forward. Did your phone boot? Notice any issues?
It's easy to remove the warning when it goes to recovery. But that means it must be complied with that change.
Click to expand...
Click to collapse
My phone does not boot, it just stays at the screen galaxy s6 edge when you just turn on the phone
I also tried to falsh a stock rom but Odin says fail.
tuffmek said:
My phone does not boot, it just stays at the screen galaxy s6 edge when you just turn on the phone
I also tried to falsh a stock rom but Odin says fail.
Click to expand...
Click to collapse
Are you flashing the correct firmware?
The Sickness said:
Are you flashing the correct firmware?
Click to expand...
Click to collapse
Hmm, that is a good quesation, I got it from this link
http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
There are two downloads for T-Mobile SM-G925T Galaxy S6 Edge Stock Firmware so I will download the second one and give it a try.
tuffmek said:
Hmm, that is a good quesation, I got it from this link
http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
There are two downloads for T-Mobile SM-G925T Galaxy S6 Edge Stock Firmware so I will download the second one and give it a try.
Click to expand...
Click to collapse
Those are 5.1.......
Where you on 6.0.1? Because that is the firmware you need. Get it from Sammobile.com
The Sickness said:
Those are 5.1.......
Where you on 6.0.1? Because that is the firmware you need. Get it from Sammobile.com
Click to expand...
Click to collapse
Thanks so much dude, it worked.
tuffmek said:
Thanks so much dude, it worked.
Click to expand...
Click to collapse
Good to hear
@tuffmek:
Why did you continue to ask questions when you were told not to worry about it? The SEANDROID ENFORCING error message is inconsequential. If you install a custom recovery such as TWRP, you WILL see the "RECOVERY IS NOT SEANDROID ENFORCING" message, because custom recoveries do not pass the security check. It is NOT an issue. If you install a custom kernel, you will see a similar message. Once again it is not an issue.
I seem to be saying this a lot: If you don't know what you're doing and don't know how to fix it if something goes wrong, you should NOT be doing it in the first place. Questions like this are rather elementary and honestly should not be asked.