after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
fwberg said:
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Click to expand...
Click to collapse
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
hey nicho, thank you very much
so that was the trick. REMOVE THE BATTERY --> PRESS THE DOWNLOAD KEYS AND HOLD THEM --> THEN ENTER THE BATTERY BACK.
it costed me the whole day yesterday searching for a solution.
at least now I can continue to install a new rom
Thanks man
TWRP
during twrp it told me, there was a newer one. 2.x.x.9
so stupid me, if I had sticked to the plan, nothing would happend.
I used twrp b4 some days ago, for my samsung note 10.1 (2014) without trubbles,
I guess, I overread something
but I'm happy it is all fixed now.
thx for show ur interest
greetz, fred
thank you
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
this solved my recovery problem, i clicked thank you!!!
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
You just saved my phone i readed so much almost one week 12hours without stop before i try custom recovery,rom and so on.
But well since i decided that im ready to, and first thing i tried to do was custom recovery wich leaded to this problam Now im afraid to enter revovery mode xD
Idiots
You're really the dumbest person I've ever seen in my life. See if this is solution to some kind of problem your beast
Worked for me
Thank you.
remove the battery then press download buttons keep them pressed and put the battery back. choose volume down to continue....
Solution To Loop SM-N900P
I am new to XDA and have only been with android for 6 months but i figure this will help new comers to this issue. Power+Volume Down+Home at the same time to enter download mode. Flash CWM via ODIN. This should work to fix the loop. I found out the hard way but it only took me an hour. I am not sure if this will work if you have not already rooted your phone but it should (since this is the major step in rooting). I believe i deleted my CWM file (accidentally) when i was trying to clear space for my recovery with ROM Manager. Be sure to download the Samsung drivers if you had not already done so during the rooting process.
Hope this helps.
Gives me same error message
But after that it boots into recovery.
Should I proceed installing custom rom or is there anything else to be taken care of
Thanks!
Thank you very much,you save me a lot of trouble.
hey_joe said:
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
Click to expand...
Click to collapse
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
billygun118 said:
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
Click to expand...
Click to collapse
Which android os do you have on your phone and which cwm version did you flashed?
hey_joe said:
Which android os do you have on your phone and which cwm version did you flashed?
Click to expand...
Click to collapse
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
billygun118 said:
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
Click to expand...
Click to collapse
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
hey_joe said:
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
Click to expand...
Click to collapse
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
billygun118 said:
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
Click to expand...
Click to collapse
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
hey_joe said:
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
Click to expand...
Click to collapse
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
billygun118 said:
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
Click to expand...
Click to collapse
Just make sure reactivation lock is off.
When you first start odin, F.Reset Time and Auto Reboot are ticked off so let them be and make sure only those are checked and nothing else.
You probably know this but just to make sure, load the recovery on the AP slot before hitting start.
Related
I have an ATT galaxy s4 rooted with Towelroot. I've tried using GooManager to install TWRP but all it did was prevent me from booting into the recovery, I was able to get out of the loop by holding volume down and the home button and then hitting volume down to cancel going into download mode. Next I tried using Rom Manager to install CWM but the same thing happened. Now I can no longer boot into recovery, it just fails and goes into download mode. My question is should I just flash the stock recovery or is there a way to get a custom recovery?
Android Version, 4.4.2
Model Number, SAMSUNG-SGH-I337
Baseband Version, I337UCUFNC1
Kernel Version, 3.4.0-1125940
Build Number, KOT49H.I337UCUFNC1
Security Software Version, MDF v1.0 Release 2
I didn't know what you needed so I just put everything here, let me know if I missed something or you need to know anything else.
binavik said:
I have an ATT galaxy s4 rooted with Towelroot. I've tried using GooManager to install TWRP but all it did was prevent me from booting into the recovery, I was able to get out of the loop by holding volume down and the home button and then hitting volume down to cancel going into download mode. Next I tried using Rom Manager to install CWM but the same thing happened. Now I can no longer boot into recovery, it just fails and goes into download mode. My question is should I just flash the stock recovery or is there a way to get a custom recovery?
Android Version, 4.4.2
Model Number, SAMSUNG-SGH-I337
Baseband Version, I337UCUFNC1
Kernel Version, 3.4.0-1125940
Build Number, KOT49H.I337UCUFNC1
Security Software Version, MDF v1.0 Release 2
I didn't know what you needed so I just put everything here, let me know if I missed something or you need to know anything else.
Click to expand...
Click to collapse
Since you are on the NC1 firmware the only recovery software you can use is Safestrap 3.72. You can read more about safestrap in here.
tsonav peculiar
sway8966 said:
Since you are on the NC1 firmware the only recovery software you can use is Safestrap 3.72. You can read more about safestrap in here.
Click to expand...
Click to collapse
Thanks for the quick reply. I installed Safestrap 3.72 then hit Install Recovery, however the state still says Not Installed, also Reboot to Recovery option is greyed out. I tried going into the recovery manually with the same result as the previous 2.
You need to change selinux mode to permissive. The. Safestrap will be able to install recovery
Sent from my SGH-I337 running GPE using Tapatalk
means ynlyof
jmjoyas said:
You need to change selinux mode to permissive. The. Safestrap will be able to install recovery
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
Sorry for the noob question but I am completely new to this, how exactly do I go about changing the selinux mode to permissive?
Ok, so I used SELinuxModeChanger to change selinux to permissive, and safestrap now installed. Now when I use the button combination Volume Up, Home and Power, it still does the same thing. If I allow it to boot normally I get a red message saying Safestrap Disabled starting system in 10 seconds, then 2 options at the bottom for booting into recovery and to continue. Is this normal or did I do something wrong?
That's perfectly normal.
Due to the locked boot loader, we cannot replace the stock recovery. Safestrap works around this by being available in normal boot mode.
Safe strap originally supported ROM slots (multi boot) and would show enabled when one of the ROM slots was selected. We can only use the stock slot, so don't worry about the disabled part.
Sent from my SGH-I337 running GPE using Tapatalk
jmjoyas said:
That's perfectly normal.
Due to the locked boot loader, we cannot replace the stock recovery. Safestrap works around this by being available in normal boot mode.
Safe strap originally supported ROM slots (multi boot) and would show enabled when one of the ROM slots was selected. We can only use the stock slot, so don't worry about the disabled part.
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply and clearing that up. However I would like to know if there is any way to get back the stock recovery? It is a bit annoying that every time my phone turns off that it gets stuck in a little loop. Also this error message shows up on my phone and if anyone opens it, it immediately goes back into the loop. My mother loves playing with my phone a lot so I can see future problems coming. Anyway for me to flash the stock recovery back on?
You can uninstall recovery from the safestrap app
Sent from my SGH-I337 running GPE using Tapatalk
I did that but I am still not able to boot into the stock recovery, it just keeps getting stuck in the loop.
binavik said:
I did that but I am still not able to boot into the stock recovery, it just keeps getting stuck in the loop.
Click to expand...
Click to collapse
Check the NB1 ODIN thread and see if there's a link to just the recovery. If not you'll have to extract and flash it from the full tar with heimdall or package it in a zip or use an app or something.
DeadlySin9 said:
Check the NB1 ODIN thread and see if there's a link to just the recovery. If not you'll have to extract and flash it from the full tar with heimdall or package it in a zip or use an app or something.
Click to expand...
Click to collapse
When searching the forums I found this post http://forum.xda-developers.com/showthread.php?p=52167761. It seems like the correct stock recovery. So I just download this, go into Odin, put my phone into download mode, then what? I've never used odin before but I assume that I would need to point it to the file but not exactly sure under which slot or which options to be checked.
binavik said:
When searching the forums I found this post http://forum.xda-developers.com/showthread.php?p=52167761. It seems like the correct stock recovery. So I just download this, go into Odin, put my phone into download mode, then what? I've never used odin before but I assume that I would need to point it to the file but not exactly sure under which slot or which options to be checked.
Click to expand...
Click to collapse
Never flashed it before, but the op says to put it in the PDA slot. Just have auto robot and f.rest checked. Do not have partition checked
Sent from my Nexus 5 using XDA Free mobile app
Thanks everyone. My stock recovery is up and running again and I also now have safestrap as well. That stock recovery file worked just fine, I just had to put it under AP for odin 3.09.
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that
Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.
I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue
Hello guys, I need your help, I am really a noob in rooting and decided to give it a go with CF AUTO ROOT, and I downloaded the correct files, everything was correct, I started the method and it said "PASS" Now the phone is stuck in a bootloop and it says
recovery booting..
recovery is not seandroid enforcing
set warranty bit: recovery then restarts again, I AM COUNTING ON YOUR GOOD GRACES, PLEASE HELP ME!!!!!!
TheDon772 said:
Hello guys, I need your help, I am really a noob in rooting and decided to give it a go with CF AUTO ROOT, and I downloaded the correct files, everything was correct, I started the method and it said "PASS" Now the phone is stuck in a bootloop and it says
recovery booting..
recovery is not seandroid enforcing
set warranty bit: recovery then restarts again, I AM COUNTING ON YOUR GOOD GRACES, PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Can you put it in download mode? Have you tried the button combo (power + vol up + home) to go into recovery?
harry9991 said:
Can you put it in download mode? Have you tried the button combo (power + vol up + home) to go into recovery?
Click to expand...
Click to collapse
I can put it in download mode but it does not boot to recovery mode...
TheDon772 said:
I can put it in download mode but it does not boot to recovery mode...
Click to expand...
Click to collapse
Have you tried flashing a custom recovery from Download mode? I'd give that a go then flash a custom ROM (I assume you still want a custom ROM?)
harry9991 said:
Have you tried flashing a custom recovery from Download mode? I'd give that a go then flash a custom ROM (I assume you still want a custom ROM?)
Click to expand...
Click to collapse
I thought rooting was mandatory in order to flash custom recovery?.... Harry you look like a professional in this, please give me a step-by-step solution, since logically it seems the problem is in the recovery? Maybe I deleted it since I can't boot to it.... I have to root then flash recovery then flash rom, right?
TheDon772 said:
I thought rooting was mandatory in order to flash custom recovery?.... Harry you look like a professional in this, please give me a step-by-step solution, since logically it seems the problem is in the recovery? Maybe I deleted it since I can't boot to it.... I have to root then flash recovery then flash rom, right?
Click to expand...
Click to collapse
Recovery comes after rooting IIRC (I rooted mine ~1 year ago so it's a bit fuzzy) so if your rooting was successful then a custom recovery flash should be possible (TWRP recommended)
harry9991 said:
Recovery comes after rooting IIRC (I rooted mine ~1 year ago so it's a bit fuzzy) so if your rooting was successful then a custom recovery flash should be possible (TWRP recommended)
Click to expand...
Click to collapse
Looks like it's not successful since it's not booting to android.. It just boots the loading screen, types the sentences I put in bold, and restarts again...... What to do? Flash a stock rom via odin?
TheDon772 said:
Looks like it's not successful since it's not booting to android.. It just boots the loading screen, types the sentences I put in bold, and restarts again...... What to do? Flash a stock rom via odin?
Click to expand...
Click to collapse
Stock ROM via Odin would be the safest route IMO, make sure you use the correct stock ROM for your device (there are numerous variations)
harry9991 said:
Stock ROM via Odin would be the safest route IMO, make sure you use the correct stock ROM for your device (there are numerous variations)
Click to expand...
Click to collapse
I found a stock rom, 5.0.1 lollipop Germany (DBT), I will try. hopefully it works!!
Just Download twrp twrp-2.8.7.0-trltexx.img from https://dl.twrp.me/trltecan/ put your phone in download mode, connect to odin, select the downloaded twrp in CP and flash it. no more bootloops.
Hello,
First of all, I'm pretty new to all of these, even new to smartphone itself, so please pardon any of my misunderstanding.
Recently I've rooted my G530h, baseband number: G530HXCU1AOA2 using Kingo ROOT. The root went well I assumed since I can use SuperU and access root-only apps.
Then I proceeded to install a custom recovery for my phone, first I tried using TWRP (v2.8.7.0), flashing with Odin through download mode. After it was done, Odin showed that it was success, my phone restarted and went into a normal boot. I then turned off my phone and try to get into recovery mode (Vol Up, Home and Power), but instead my phone went into Download mode but this time straight into the Downloading scene without going through the warning one. I couldn't turn off my phone, I had to hold down Vol Down, Home and Power, the phone went into the warning scene for Download mode again, only by pressing cancel would I be able to boot normally again.
The same thing happened when I tried installing CWM.
Please help, if there is something I'm doing wrong... I can't get into the recovery mode which I tend to use for installing a custom ROM. I've also tried flashing my original stock, the stock recovery came back and worked fine, but the custom ones still have the same problem.
Thank you for your time.
Same proble for me
HI XDA members,
same problem for me, I have GGP G530H Version G530HSER1BPB1, I have try with odin and I get the pass message without any error, but when I try to bood into recovery mode I have found the same recovery mode (original by samsung ) I don't know what is the problem, I have try all the recovery found in the net, also on the russian forum (PDA) !
please any one cand give a solution, I hate the samsung firmware and I want change to CM12 or CM13 version.
Thanks
You need to directly reboot to recovery after flashing recovery for prevent the phone to reset recovery tp the stock one
D.R-Ult.Googler said:
You need to directly reboot to recovery after flashing recovery for prevent the phone to reset recovery tp the stock one
Click to expand...
Click to collapse
Done Thank you
I found a working version of CWM for my phone, the link is bellow.
https://drive.google.com/file/d/0B4SXad98IF1RX1dWNkxSQjRSU28/view
yadnen2001 said:
Done Thank you
Click to expand...
Click to collapse
u mean in odin make auto reboot off ?
OniGiRi6131 said:
u mean in odin make auto reboot off ?
Click to expand...
Click to collapse
yeah Right
And remove battery and restart on recovery mode
Hello ;D
I have a weird thing with my N910C with 6.0.1. I read a lot about similar problems but i think mine is little different.
My phone is not bootloped. It's rooted ,working normally but i can't install any custom recovery ; c
When i first try to root it with Odin using TWRP nothing really happend so i use CF-Auto-Root and at least it's rooted now.
Next I install TWRP again using TWRP Manager from Google play ,phone is still rooted and working ,but when i try to get into recovery it fails and display "Recovery is not Seandroid Enforcing"
Any suggestions how can i install TWRP or another custom recovery?
Thanks ;D
Mlodszymlody221 said:
Hello ;D
I have a weird thing with my N910C with 6.0.1. I read a lot about similar problems but i think mine is little different.
My phone is not bootloped. It's rooted ,working normally but i can't install any custom recovery ; c
When i first try to root it with Odin using TWRP nothing really happend so i use CF-Auto-Root and at least it's rooted now.
Next I install TWRP again using TWRP Manager from Google play ,phone is still rooted and working ,but when i try to get into recovery it fails and display "Recovery is not Seandroid Enforcing"
Any suggestions how can i install TWRP or another custom recovery?
Thanks ;D
Click to expand...
Click to collapse
You don't need to be worried about the message you're getting (recovery is not seandroid enforcing) it's normal
Don't install the the TWRP from the playstore you need to get the latest build from their website follow the steps and flash it through odin.. cheers
Sent from my SM-N910G using Tapatalk
Amar.B said:
You don't need to be worried about the message you're getting (recovery is not seandroid enforcing) it's normal
Don't install the the TWRP from the playstore you need to get the latest build from their website follow the steps and flash it through odin.. cheers
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
I've had this issue from installing TWRP from TWRP official app, Then I updated the firmware from Kies as a solution to the same after watching a few videos. I lost the SuperSU binaries and the root, rooted and flashed TWRP from Odin, by downloading the latest build from the TWRP website.
I got the same error message and still
Amar.B said:
You don't need to be worried about the message you're getting (recovery is not seandroid enforcing) it's normal
Don't install the the TWRP from the playstore you need to get the latest build from their website follow the steps and flash it through odin.. cheers
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
I install TWRP through odin and nothing really happens ; /
No root and no custom recovery ; /
Mlodszymlody221 said:
I install TWRP through odin and nothing really happens ; /
No root and no custom recovery ; /
Click to expand...
Click to collapse
Did you follow the steps!
1st unitck the auto reboot.
When you flash the custom recovery successfully for your device model go to recovery mode immediately.
if you reboot your device normally the stock recovery will replace the custom recovery so make sure to restart into recovery mode after installing the custom recovery via odin.
Sent from my SM-N910G using Tapatalk
Amar.B said:
Did you follow the steps!
1st unitck the auto reboot.
When you flash the custom recovery successfully for your device model go to recovery mode immediately.
if you reboot your device normally the stock recovery will replace the custom recovery so make sure to restart into recovery mode after installing the custom recovery via odin.
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Still the same :/
That's why im here ,it's really weird.
I can't go to that custom recovery no matter what im doing ,i watched lots of YT films ,read multiple guides and any of that doesn't work ;/
Only thing working is CF-Auto-Root ,but still don't know how to install recovery ; /
Mlodszymlody221 said:
Still the same :/
That's why im here ,it's really weird.
I can't go to that custom recovery no matter what im doing ,i watched lots of YT films ,read multiple guides and any of that doesn't work ;/
Only thing working is CF-Auto-Root ,but still don't know how to install recovery ; /
Click to expand...
Click to collapse
When you flashed TWRP through odin what did you get! The logcat?
It will be written like this
(Successful 1/faild 0) that means it's been installed successfully
(Successful 0/faild 1) that mean odin faild to install the recovery
Sent from my SM-N910G using Tapatalk
After you flashing recovery through odin as soon as phone begins rebooting pull your battery for at least 25 seconds. I am not sure why it works but it has worked every time i have run into this issue. Also check that you are using the latest version of odin.
Amar.B said:
When you flashed TWRP through odin what did you get! The logcat?
It will be written like this
(Successful 1/faild 0) that means it's been installed successfully
(Successful 0/faild 1) that mean odin faild to install the recovery
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
All threads completed. (succeed 1 / failed 0) ; /
After using TWRP phone doesn't boot ,Seandroid Enforcing
need to use CF again to start a phone
vegeta21232 said:
After you flashing recovery through odin as soon as phone begins rebooting pull your battery for at least 25 seconds. I am not sure why it works but it has worked every time i have run into this issue. Also check that you are using the latest version of odin.
Click to expand...
Click to collapse
unfortunately still nothing ;c
After a successful install the twrp with odin immediately pull the battery out for 10 sec then put the battery back press the volume up+home button+power button
Try this one and please make sure you are installing the correct version for your device model.
Mlodszymlody221 said:
unfortunately still nothing ;c
Click to expand...
Click to collapse
Sent from my SM-N910G using Tapatalk
Amar.B said:
After a successful install the twrp with odin immediately pull the battery out for 10 sec then put the battery back press the volume up+home button+power button
Try this one and please make sure you are installing the correct version for your device model.
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Still the same ,i think i need to go back to 5.0.1 . I have some new update last week and i think this is the problem.