Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.
nrkid9 said:
Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.
Click to expand...
Click to collapse
Use below file for rooting & once rooted successfully, switch off your phone & reboot in recovery.
http://d-h.st/J32
re: download mode
nrkid9 said:
Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.
Click to expand...
Click to collapse
Remove battery, wait 10 seconds replace battery and
hold down the volume down+power+home key at the
same time. Then the phone will go into download mode.
I have 4 sprint Note 3's I rooted with CWM for all 4 but one is "stuck" at recovery like this any time I turn it on it always tries to boot into recovery and gets stuck.
I can get into download mode. will cf auto root fix this? (trying to avoid a full odin restore)
the only thing different about this sprint note 3 that I am aware of is that its flashed to boost (if that matters it should not matter)
the other 3 went flawlessly. yes I tried to odin the cwm root a second time no change.
Thanks!!!
Thanks for the link. Just unboxed the note 3 (sprint) with version 4.3 and followed qbking77 and it was stuck on that same screen (tried it 3 times).
Your link saved me. :good::good::good:
I wonder why qbking's didn't work ... it always has in the past.
jdomadia said:
Use below file for rooting & once rooted successfully, switch off your phone & reboot in recovery.
http://d-h.st/J32
Click to expand...
Click to collapse
chickenmusket said:
Thanks for the link. Just unboxed the note 3 (sprint) with version 4.3 and followed qbking77 and it was stuck on that same screen (tried it 3 times).
Your link saved me. :good::good::good:
I wonder why qbking's didn't work ... it always has in the past.
Click to expand...
Click to collapse
Why didn't you use the specific file for your device (Note 3 Sprint): http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
thought I was...
Maybe I'm getting dumber, or maybe it's getting more confusing to root. Seems like there's a crap load of how to root this device pages and it takes a long time to figure out which one actually works. Then once I find it, I'm faced with dead links to the downloads.
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
Do you have access to a USB jig?
luqmaanki said:
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
Click to expand...
Click to collapse
same problem here did you find solution please reply
As already posted .
Try USB Recovery Jig.
Fails then service centre .
twrp
vndnguyen said:
Why didn't you use the specific file for your device (Note 3 Sprint): http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
Click to expand...
Click to collapse
i know this thread is old....but sometimes i have to access download mode, and then chose cancel in order for it to boot. usually from recovery when i tap reboot system, it brings me back to recovery. so i have to pull the battery and button combo to download mode then cancel. does this issue have any familiarity?
Someone please help I have a Samsung note edge that I just reset through the menu settings backup and reset option and phone turned off but did not fully come back on its just sitting on black Samsung Screen and on top left corner it says recovery booting set warranty bit : recovery in blue and yellow letters and I am able to got into the download screen but I press volume down just to cancel and reboot and stars coming on but gose back to same black Samung screen. Like i said I did not try rooting it or any such thing.
Wrong forum this is not EDGE model .
Download mode and flash stock rom through Odin is generic advice .
"Recovery Booting" Bootloop fix
A few months ago, my rooted Galaxy Note 3 (sm-n900t) was force closing and freezing my apps often. So I decided to boot into recovery to clear device cache. The 'recovery booting' would appear on the screen with the logo, but after 7 seconds it would reboot normally instead of opening recovery(I had version 3.2.3.0). So I did reboot recovery with Rom Toolbox and it began bootlooping with the message:
Recovery Booting....
Set Warranty Bit : recovery
It wouldn't boot normally, in recovery or download mode.
STEPS TO FIX:
1.) Let phone Bootloop until completely dead
2.) On PC downloaded (2.8.7.0) twrp file for device from twrp.me/devices
3.) Press and hold volume down + home + power until phone reboots into download mode.
4.) Plug device into PC USB where drivers are loaded.
5.) Start Odin or Samsung Tool z3x flashing tab
6.) Load twrp in AP or PDA section and flash
7.) Phone should reboot normally!
Related
i've been searching for roms, and i downloaded a rom that need to reboot, after it switched off my mobile and switched it on again, i've been stuck at the boot logo ever since. im using Kingo Android Root to root my phone, any good suggestions to help me solve this head wrenching problem?
wilsontan90 said:
i've been searching for roms, and i downloaded a rom that need to reboot, after it switched off my mobile and switched it on again, i've been stuck at the boot logo ever since. im using Kingo Android Root to root my phone, any good suggestions to help me solve this head wrenching problem?
Click to expand...
Click to collapse
you on 4.3 or 4.4.2
Same Problem
I am having the same problem. Rooted, went to install rom, followed directions and now I am stuck on Samsung Galaxy Note3 screen. How do I fix this??? I am on 4.4.2 I believe
jaythenut said:
you on 4.3 or 4.4.2
Click to expand...
Click to collapse
Boot into recovery and clear cache/dalvik
Sent from my SM-N900W8 using Tapatalk
stuck on booting
polish_pat said:
Boot into recovery and clear cache/dalvik
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
How to boot into recovery if I can't get rid of the Recovery Booting message no matter what I do??
lumaom said:
How to boot into recovery if I can't get rid of the Recovery Booting message no matter what I do??
Click to expand...
Click to collapse
What did you do before this happened, tried to root, install custom recovery/roms, update to 4.4?
booting stuck
hey_joe said:
What did you do before this happened, tried to root, install custom recovery/roms, update to 4.4?
Click to expand...
Click to collapse
I was trying to root my Galaxy Note 3, KitKat, SM-N900T with Odin 3.9. Everything went fine and I got the PASS! message. I disconnect the phone and I expected the automatic booting. That never happened. The screen started to flash the RECOVERING ROOTING (blue), RECOVERING IS NOT SEANDROID ENFORCING (red) and SET WARRANTY BIT : RECOVERY(yellow). Nothing that I did after that worked to get rid of those messages. I wonder if my new phone is bricked now or if I have a chance of recover it. Taking the battery out and putting in again plus holding all the buttons doesn't stop the messages from flashing. Please help!
lumaom said:
I was trying to root my Galaxy Note 3, KitKat, SM-N900T with Odin 3.9. Everything went fine and I got the PASS! message. I disconnect the phone and I expected the automatic booting. That never happened. The screen started to flash the RECOVERING ROOTING (blue), RECOVERING IS NOT SEANDROID ENFORCING (red) and SET WARRANTY BIT : RECOVERY(yellow). Nothing that I did after that worked to get rid of those messages. I wonder if my new phone is bricked now or if I have a chance of recover it. Taking the battery out and putting in again plus holding all the buttons doesn't stop the messages from flashing. Please help!
Click to expand...
Click to collapse
Two options -
Make sure you have the correct CF-AUTOROOT
Reflash stock
booting stuck
radicalisto said:
Two options -
Make sure you have the correct CF-AUTOROOT
Reflash stock
Click to expand...
Click to collapse
Thank you for the suggestion but no idea how to do it with a phone stuck in the booting screen. Any help on how to get rid of it? Once that is done then I can proceed with your steps.
Take the battery out, put back in (dont turn back on)and hold volume up, home and power button. It'll take you into download mode.
Then flash your stock ROM via Odin
Sent from my Nexus 5 using XDA Premium 4 mobile app
booting stuck
radicalisto said:
Take the battery out, put back in (dont turn back on)and hold volume up, home and power button. It'll take you into download mode.
Then flash your stock ROM via Odin
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried that many times. It doesn't take me to the download mode but again to the screen I mentioned. Frustrating!..
It just keeps bootlooping you mean?
Keep trying to get into download mode, might be that you're catching the power button first and powering the phone back on.
Can you get into recovery ? Volume down and power/home button.
You should be able to get to one of them at least
Sent from my Nexus 5 using XDA Premium 4 mobile app
lumaom said:
I tried that many times. It doesn't take me to the download mode but again to the screen I mentioned. Frustrating!..
Click to expand...
Click to collapse
Try this.
Remove and put battery back in, don't power on.
Hold Vol Down + Power + Home Button all at the same time until the warning message comes up then let go of the buttons. Finally press Vol Up only and you'll be in download mode. Connect phone to usb.
Flash this CF Auto root courtesy of Chainfire thru odin. Not sure if CF updated it for 4.4 but one poster said it worked for him on his Tmo.
Optionally flash a custom recovery cause you will have a stock recovery after rooting.
help me!
I had the same issue, I did as you said, but now I am stuck at RECOVERY BOOTING... RECOVERY IS NOT SEANDROID ENFORCING Set Warranty Bit: recovery.
(it never shows the orange pirate rooting guy)
however, against all judgement I tried it with the sm9005 instead of the sm900t file and it passed into the orange pirate root guy, however it gets stuck at the boot logo, do you guys have any Idea what could be wrong?
wilsontan90 said:
i've been searching for roms, and i downloaded a rom that need to reboot, after it switched off my mobile and switched it on again, i've been stuck at the boot logo ever since. im using Kingo Android Root to root my phone, any good suggestions to help me solve this head wrenching problem?
Click to expand...
Click to collapse
I've got myself stuck a couple times... both times I booted into download mode and selected reboot phone... it worked both times. As stated in another reply, make sure you pull the battery then replace and make sure you are holding home/vol/power... and make sure you get the home/vol buttons before you press and hold power.
emazzy72 said:
I've got myself stuck a couple times... both times I booted into download mode and selected reboot phone... it worked both times. As stated in another reply, make sure you pull the battery then replace and make sure you are holding home/vol/power... and make sure you get the home/vol buttons before you press and hold power.
Click to expand...
Click to collapse
i aso tried rooting my tmo note 3 with kingo and my phone is boots up but at amsung galaxy note 3 screen i get recovery booting in blue and then set warranty bit: recovery in yellow. and so far nothing wiil put it in downoad mode. HELP
I tried to root a T-Mobile Note 3 N900T 4.4.2 running a newly updated NE7 build on 4.4.2
It booted into download mode after all other methods failed, and flashed a custom recovery and said root succeeded, but then it tripped knox and when it tried to boot up it got the same error...
Booting into recovery...
Set warranty bit: Recovery
and then it would just boot loop from then on, unless I pulled the battery, held home+volumedown+power and pressed volume down to cancel and it would boot up normally but with no supersu installed or any root privileges, need to find out how to root this build
tried looking it up, can't find anything on it, please help.
SM-N900T
4.4.2
Baseband version: N900TUVUDNE7
Build Number: KOT49H.N900TUVUDNE7.DM
wilsontan90 said:
i've been searching for roms, and i downloaded a rom that need to reboot, after it switched off my mobile and switched it on again, i've been stuck at the boot logo ever since. im using Kingo Android Root to root my phone, any good suggestions to help me solve this head wrenching problem?
Click to expand...
Click to collapse
Use CF auto root. And you dont run into these issues. I dont understand why people use anything else
Sent from my SM-N9005 using XDA Premium 4 mobile app
HI there, guys! I just read the whole thread and maybe you can help me also! I'm facing a less critical, but similar problem.
I use Omega ROM (Android 4.3 yet) and just after a reboot my device is stuck at boot animation forever. The only thing I did before rebooting was freeze S Finder using Titanium Backup (after it was enabled again because Samsung updated it a few days ago) and move some apps to SD Card using Clean Master.
The critical part is that I can't enter Recovery Mode to try to solve wiping caches because my Reactivation Lock feature is enabled, so I can't access it.
Is there anything I can do except from flashing stock ROM over Omega itself? I can't lose my files on internal storage. There are pretty important ones! =/
phone stuck in the booting screen. Any help on how to get rid of it? Once that is do
phone stuck in the booting screen. Any help on how to get rid of it? Once that is done then I can proceed with your steps. what do I do?!?!?!?!
Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Any ideas?
Thank you
Go into Recovery mode (Vol Up + Home Button + Power Button) and Factory reset Data & Wipe Cache Partition...
moin786 said:
Go into Recovery mode (Vol Up + Home Button + Power Button) and Factory reset Data & Wipe Cache Partition...
Click to expand...
Click to collapse
Still get the same thing. It starts to boot to recovery then says something that fails then goes to the screen I have posted previous.
This is what first loads (pretty quick - had to reboot about 10 times to get it)
recovery booting...
SYS REV CHECK FAIL : no version
Secure : Secure Version Failure (recovery.img)
Set Warranty Bit : Recovery
norem0rz said:
Still get the same thing. It starts to boot to recovery then says something that fails then goes to the screen I have posted previous.
This is what first loads (pretty quick - had to reboot about 10 times to get it)
recovery booting...
SYS REV CHECK FAIL : no version
Secure : Secure Version Failure (recovery.img)
Set Warranty Bit : Recovery
Click to expand...
Click to collapse
What did you do prior to this? It looks like you flashed a custom recovery but Knox is terminating the boot process.
Have you tried to odin back to stock?
Sent from my Galaxy Note 3 ?
Trying to use Odin - downloading a stock ROM now.
No. You must get into download/Odin mode by pressing volume down + home + power simultaneously, then launch Odin, then connect phone to computer.
Sent from my SM-N900V using Tapatalk
norem0rz said:
yes, I was using clockwork and did something wrong...
doesn't the phone need to boot up before I can use Odin?
Click to expand...
Click to collapse
If you have a Verizon retail version of the Note 3, you can not use Clockworkmod recovery. Because your bootloader is locked. You can only use Hashcode's Safestrap (in the Development section).
cam30era said:
If you have a Verizon retail version of the Note 3, you can not use Clockworkmod recovery. Because your bootloader is locked. You can only use Hashcode's Safestrap (in the Development section).
Click to expand...
Click to collapse
+1
Which means you must be rooted first, then install Safestrap, which is a modified TWRP recovery. You can thank Verizon for that bullsh!t
Sent from my SM-N900V using Tapatalk
Thank you all - using Odin with this link http://forum.xda-developers.com/showthread.php?t=2483380
Got me back up and running.
Flash PIT - this will fix it
You need to flash the PIT with ODIN, latest version (3.09, I believe). Google for a download mirror that hosts the PIT for whichever type of note 3 you have, then flash it with odin (should work while in the invalid software screen). Then, if it doesn't reboot, just remove the battery and unplug that sucka. When it reboots, it should go back to download mode or just regular bootup. I recommend setting up adb, which makes it much easier to put the phone into whatever mode you desire with a simple dos command.
got out of it
this happened to me last night, I went into Odin mode "home, volume down, power button" instead of selecting odin mode from that menu I selected "reboot phone" (or something to that effect) My note 3 restarted......PHEW...... hope this helps someone
enable android recovery mode
SM-N90OV
ok so I once got to the point to where I could not but factory reset my phone and so I did settings > backup and restore > factory reset > YES I'M SURE!!! then my phone when into recovery mode as it should normally only to tell me that it could not enter recovery. Verizon's fault and now I cant access my recovery mode. is there a way to get back into it so I can finally flash a new rom. oh I had figured out how to get out of the boot loop thing by entering download mode and canceling. but it would be nice to be able to mess with this beast of a phone. please help me. I don't want to do something I wasn't supposed to. im not sure want to do with klms agent deals with knox right?
Em also one of the victim
hi
i am rooted (de la Vega ) safestrap installed using Jelly beans 6 & stock Rom as well. i don't know how but i am not being able to get in the recovery to format the device.
Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
What i do is getting into the download mode and only pressing Volume down to continue boot and Viola my phone restarts every time, but the thing which is pinching me is i can't able to format the phone.. Help required please.
xaneey said:
hi
i am rooted (de la Vega ) safestrap installed using Jelly beans 6 & stock Rom as well. i don't know how but i am not being able to get in the recovery to format the device.
Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
What i do is getting into the download mode and only pressing Volume down to continue boot and Viola my phone restarts every time, but the thing which is pinching me is i can't able to format the phone.. Help required please.
Click to expand...
Click to collapse
look at page one towards the bottom, the OP posted how to fix your problem
Solution
HI all
What worked for me is just ODIN
MI9 t0 MJE
and this is the beauty of ANDROID really happy to get it back..
Downloaded MJE for N900V http://www.sammobile.com/firmwares/3/?download=23535
Root through this in my case Vroot worked Kingo didn't work for me http://forum.xda-developers.com/showthread.php?t=2528707
Thn safe strap and all done
you guys and gals rock
saved my bacon ,was a little confusing to my novice self but downloaded odin to pc and ran it,downloaded clean vzw file and pit file ,plugged phone into pc and drivers loaded then ran odin and followed the steps.
Thank you very very much
Guys,
I was using the Cyanogenmod 11 for about 2 weeks and I always got the "kernel is not seandroid enforcing" message and the phone always booted up fine 90% of the times. Today I got the message saying that there was a new version of the firmware and I clicked ok for the phone to restart and begin the update process.
After that, I was stuck in the "kernel is not seandroid enforcing" message no matter what I did.
I entered the recovery mode and wiped the cache partition to see if that solved the problem. After this, I'm not able to access the recovery mode anymore and the phone is stuck on the samsung logo.
So I put it in download mode, opened Odin (It recognized the phone just fine) and flashed the original firmware in order to unbrick the phone. Got a PASS on Odin and I was still stuck on bootloop with no recovery mode.
Tried flash it again with the pit file (thought it would fix the partition) and the problem stills perssists.
I tried to run the Cyanogenmod installer and it doesn't recognize the phone anymore, saying the model is not compatible. Odin still recognizes the phone as always when I put it in download mode.
Any ideas?
Have I lost the phone ?
Thanks in advance for the help.
Best Regards
menaum said:
Guys,
I was using the Cyanogenmod 11 for about 2 weeks and I always got the "kernel is not seandroid enforcing" message and the phone always booted up fine 90% of the times. Today I got the message saying that there was a new version of the firmware and I clicked ok for the phone to restart and begin the update process.
After that, I was stuck in the "kernel is not seandroid enforcing" message no matter what I did.
I entered the recovery mode and wiped the cache partition to see if that solved the problem. After this, I'm not able to access the recovery mode anymore and the phone is stuck on the samsung logo.
So I put it in download mode, opened Odin (It recognized the phone just fine) and flashed the original firmware in order to unbrick the phone. Got a PASS on Odin and I was still stuck on bootloop with no recovery mode.
Tried flash it again with the pit file (thought it would fix the partition) and the problem stills perssists.
I tried to run the Cyanogenmod installer and it doesn't recognize the phone anymore, saying the model is not compatible. Odin still recognizes the phone as always when I put it in download mode.
Any ideas?
Have I lost the phone ?
Thanks in advance for the help.
Best Regards
Click to expand...
Click to collapse
Hi,
When you run the stock firmware through odin , you must wipe the cache an data before and after the flash.
Did you do that?
malybru said:
Hi,
When you run the stock firmware through odin , you must wipe the cache an data before and after the flash.
Did you do that?
Click to expand...
Click to collapse
I can't to that without the recovery mode, right?
I have no acess to the recovery mode.
menaum said:
I can't to that without the recovery mode, right?
I have no acess to the recovery mode.
Click to expand...
Click to collapse
Hi,
Are you sure you are trying to access it correctly?
Try holding the power button + volume up.
When the blue writing comes up , let go of all the buttons , and tap volume down.
If that still does not work , install the stock firmware again , and see if you can then get back to recovery mode.
malybru said:
Hi,
Are you sure you are trying to access it correctly?
Try holding the power button + volume up.
When the blue writing comes up , let go of all the buttons , and tap volume down.
If that still does not work , install the stock firmware again , and see if you can then get back to recovery mode.
Click to expand...
Click to collapse
Already did that, still no sucess. It enters the download mode normally but when I try to enter the recovery mode the blue text appears and then the screen goes black and the phone tries to boot and gets stuck on the samsung logo. (And yes I already tried holding the buttons until something else appears on the screen and nothing happens. )
And yes I'm trying to acess it correctly.
Thansks!
menaum said:
Already did that, still no sucess. It enters the download mode normally but when I try to enter the recovery mode the blue text appears and then the screen goes black and the phone tries to boot and gets stuck on the samsung logo. (And yes I already tried holding the buttons until something else appears on the screen and nothing happens. )
And yes I'm trying to acess it correctly.
Thansks!
Click to expand...
Click to collapse
Hi,
Do you have the knox bootloader?
What firmware are you trying to flash?
AT&T version here, same problem
malybru said:
Hi,
Do you have the knox bootloader?
What firmware are you trying to flash?
Click to expand...
Click to collapse
Quick ?: I have the AT&T s4 i337 with the same problem. Can i use the same method ? And no on the knox(saferoot) . 4.2 i believe. Thanx & sorry for butting in ! Ardonie
ardonie said:
Quick ?: I have the AT&T s4 i337 with the same problem. Can i use the same method ? And no on the knox(saferoot) . 4.2 i believe. Thanx & sorry for butting in ! Ardonie
Click to expand...
Click to collapse
Hi,
Then , you should try flashing a non-knox firmware .
Unfortunately ,I do not know AT&T firmwares.
Perhaps someone HERE can help.
I have the same issue on verizon, and searching for a solution. If you guys got any further in solving i would appreciate sharing the methods here
recovery is not Seandroid Enforcing
lorenzoraj said:
I have the same issue on verizon, and searching for a solution. If you guys got any further in solving i would appreciate sharing the methods here
Click to expand...
Click to collapse
I also have the same problem with Galaxy s4 Active (i9295)
Flashing recovery finish successfully (tried Philz,CWM, TWRP )
But afterwards no recovery exists anymore
only:
recovery is not Seandroid Enforcing
When I flash stock ROM again, the basic recovery it there - no option for applying zip files
Hi Guys,
I tried to root my S4 GT9500 using the galaxy for root dot com site and now the phone is stuck in a boot loop.
I cant even get into recovery mode. The phone just reboots continuously. I got stuck when trying to install the supersu app
and it just went downhill and the reboots started. When I try the home, power and vol up buttons keystrokes,
I cannot get into recovery mode. When I try download mode, it gets there but as soon as i hit the volume up, it reboots again
Can someone guide me to fix my mess please
I hope this has not been asked before.
akajee said:
Hi Guys,
I tried to root my S4 GT9500 using the galaxy for root dot com site and now the phone is stuck in a boot loop.
I cant even get into recovery mode. The phone just reboots continuously. I got stuck when trying to install the supersu app
and it just went downhill and the reboots started. When I try the home, power and vol up buttons keystrokes,
I cannot get into recovery mode. When I try download mode, it gets there but as soon as i hit the volume up, it reboots again
Can someone guide me to fix my mess please
I hope this has not been asked before.
Click to expand...
Click to collapse
If you can't enter in recovery mode then try to put it in download mode and flash a stock ROM. When you flash a new kernel to root your phone you must check if the kernel that you are flashing is compatible with the current android version, I mean, if you flash a kitkat kernel and you have a lollipop rom you will get bootloops for sure.
Download mode reboots also after 1 second also
akajee said:
Hi Guys,
I tried to root my S4 GT9500 using the galaxy for root dot com site and now the phone is stuck in a boot loop.
I cant even get into recovery mode. The phone just reboots continuously. I got stuck when trying to install the supersu app
and it just went downhill and the reboots started. When I try the home, power and vol up buttons keystrokes,
I cannot get into recovery mode. When I try download mode, it gets there but as soon as i hit the volume up, it reboots again
Can someone guide me to fix my mess please
I hope this has not been asked before.
Click to expand...
Click to collapse
Maybe the problem is your power button being stuck if it just shows galaxy logo and reboots every time.
Styrke said:
Maybe the problem is your power button being stuck if it just shows galaxy logo and reboots every time.
Click to expand...
Click to collapse
I agree with this. Also you said that in download mode it reboots after one second.
Or it can also be ur battery, u should try a different one
Also you can try flashing twrp recovery from odin again. Some steps may make the recovery.img broken. If you reinstall it that may work. (I faced such a problem and I solve in that way)
so it does appear to be a stuck power button because if I press home and volume down, it still goes into download mod. Let me see how I can fix that now. Thanks all.
dorian2kx said:
Or it can also be ur battery, u should try a different one
Click to expand...
Click to collapse
Battery was good, tested it on my working S4
Hi all, I recently tried to root my Telstra GalaxyTab A 8.0 (SM-T355Y) with CF AutoRoot, but must have used the wrong version. I'm now permanently stuck at the boot screen with the message "Kernel is not seandroid enforcing"
I figured I could just reboot back into download mode and re-flash, but nothing I do can get me back into download mode. I even opened the case up and disconnected the battery, hoping to force a reboot, but when I connect it back up and turn it on it goes straight to the same error message and I cannot get to either download mode or recovery mode.
Any thoughts? I've never managed to totally brick a device before.
At this point, I'd even pay for it to be repaired, as I'm crazy busy with family stuff and just want it working again.
Thanks in advance for any help.
Patrick.
patdman said:
Hi all, I recently tried to root my Telstra GalaxyTab A 8.0 (SM-T355Y) with CF AutoRoot, but must have used the wrong version. I'm now permanently stuck at the boot screen with the message "Kernel is not seandroid enforcing"
I figured I could just reboot back into download mode and re-flash, but nothing I do can get me back into download mode. I even opened the case up and disconnected the battery, hoping to force a reboot, but when I connect it back up and turn it on it goes straight to the same error message and I cannot get to either download mode or recovery mode.
Any thoughts? I've never managed to totally brick a device before.
At this point, I'd even pay for it to be repaired, as I'm crazy busy with family stuff and just want it working again.
Thanks in advance for any help.
Patrick.
Click to expand...
Click to collapse
Holding power+volume down+home doesn't work?
jedld said:
Holding power+volume down+home doesn't work?
Click to expand...
Click to collapse
Unfortunately not, I'm really confused and now totally stuck!
I just tried this again (it's been a couple of weeks since I last tried) and the actual error displayed is
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Well I've now sorted it out.
Thanks to this thread (http://forum.xda-developers.com/s7-edge/help/recovery-seandroid-enforcing-t3416719)
I just needed to hold down the buttons for an extra boot cycle (2 cycles of boot to "recovery is no seandroid enforcing", then the next boot went to download)
It all seems a bit strange, but but it did the trick and I'm back running stock.
Now to re-try rooting.
The CF Auto Root version I tried which started all this was absolutely listed for my device and version, I think I'll just go the TWRP -> supersu route this time.