Just got a Galaxy S4 i9505 rotted it with Kingo Root, installed rashr went to flash something and it installed a recovery and now I get Recovery is not seandroid enforcing, but researched it up and used odin to get past that, but now everytime i try to get into recovery I get that error again.
How can I reflash a recovery that works? I have tried re-rooting again but nothing.
Now it just doenst seem to start just shows the Samgung logo and does nothing.
What exactly are you saying? That you can't boot into recovery?
Rooting has nothing to do with a recovery.
Install TWRP recovery with Odin.
You could also try flashing a bootloader or the stock rom again to make your phone boot. And root properly with CF Auto Root
I meant it like the root program I used that installed the original recovery, I have tried TWRP with odin but it says it is done but still wont boot or go into recovery
How owuld I flash the stock rom?
Was meant to click edit not double post sorry
You have to untick "Auto reboot" in odin. After twrp flashed turn off the phone and use the key combination to boot into recovery.
I think i flashed an older version of twrp cant find a link to a jar for 5.0.1
Ok i managed to get twrp working, but it still alwayss just shows the Samsung logo
Just to clarify one thing here for the audience, "Recovery is not SEAndroid Enforcing" is not an error. All custom recovery images are set to permissive mode to enable them to perform their magic. Since this is a hole in the device's security, the bootloader displays that message to let you know this. A similar message is displayed when a custom kernel is installed, except in that case the message is "Kernel is not SEAndroid Enforcing". Since this is an expected message, the only way to properly get rid of it is to not install a custom recovery or, in the case of the kernel warning, a custom kernel.
@Apexpredator12, with your S4 in its current state, you should flash your stock ROM via Odin and make sure your device is totally operational. After that, use Odin to install CF-Autoroot. DO NOT USE KINGOROOT! With CF-Autoroot you will have your S4 rooted. From there, if you wish you can install a custom recovery, though with the caveat that installing a custom recovery will result in a "Kernel is not SEAndroid Enforcing" message. As mentioned above, this is a normal message and not an error.
Ok thank you, where can I get a stock rom for the i505 only seeing custom ones
I am just so foncused I am used to the SP that was quite easy to do, the version I have is 5.0.1 the stocks I have found are 4.4 etc and just not sure what ones to use without bricking my phone again
If you have a 5.0.1 stock ROM, you can use that. If you really need earlier ROMs, you can get them from samsung-updates.com or sammobile.com.
Yeah I was looking but they seem to be .img files which I cant seem to flash with odin
sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.
Strephon Alkhalikoi said:
sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.
Click to expand...
Click to collapse
I have tried loading a .img with odin but it doesnt seem to detect them
Apexpredator12 said:
I have tried loading a .img with odin but it doesnt seem to detect them
Click to expand...
Click to collapse
You are extracting to much. You can't flash .img with Odin as far as I know. You need to flash the archive in which the .img is packed.
Lennyz1988 said:
You are extracting to much. You can't flash .img with Odin as far as I know. You need to flash the archive in which the .img is packed.
Click to expand...
Click to collapse
I have managed to get stock installed with odin everything works but I cant find CF-Autoroot for galaxy s4 i9505 version 5.0.1
Strephon Alkhalikoi said:
sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.
Click to expand...
Click to collapse
EDIT: managed to fix the twrp thanks allot for your help much appreciated.
Related
Hello!
I've flashed a stock ROM on my Samsung Galaxy S5 (SM-G900F) using ODIN 3.07 and now the phone is bootlooping. I guess It's because I need to wipe data and cache partitions and here's the problem.
My home button is not working, so I can't boot in recovery mode. Adb does NOT recognize my device. I'm only able to access download mode using a JIG.
So, is there any way to wipe those partitions or to be able to access recovery using ODIN?
Thanks in advance for your help!
That is a challenging situation! I'd try flashing the stock ROM once more, just on top of the one you already did using Odin and see if it boots this time.
If it didn't, see if Samsung kies would recognize your phone on download mode and get kies to flash the proper stock rom because I know kies does a full wipe before flashing automatically every time.
Yea, you shouldn't need to wipe anything if you use the correct tar in Odin, it should do it automatically. I would try again as stated above. Are you sure you have the correct tar file?
Thank you so much!!
The problem is that I was trying to flash an older firmware to use Towelroot. I've flashed the same firmware and now it's working again!
Now, I really need to root because I need virtual keys (hardware ones don't work) and i have to edit build.prop file.
What's the easiest way to root on a Lollipop firmware? I don't care about Knox and warranty void.
Also, I already tried CF-Auto Root but when the phone rebooted It gave me this message: "RECOVERY IS NOT SEANDROID ENFORCING" and it didn't start anymore, that's why I needed to flash the stock firmware again.
EDIT: Nevermind. I flashed TWRP using Odin and then I flashed SuperSU in the recovery. I've booted in the recovery using "adb reboot recovery". Thanks again!
Glad you got it working!
Hi Guys,
trying to flash a custom Rom on my Note 3. It is a UK model supplied by EE but is unbranded.
Flashed several phones before, just running into some issues this time round.
Got my Rom, Autoroot, CWM and Odin downloaded.
Flash Autoroot with Odin - no problem.
Flash CWM with Odin - no problem - until i try to boot into recovery anyway.
No error message etc on Odin but when i try to boot into recovery it keeps saying "cannot do normal boot" and puts me into download mode.
I can get to download mode to reflash and have tried TWRP with the same results.
It is saying "custom binary" when in download mode, and my Knox counter has tripped to 1 (phone out of warranty so not fussed).
Ive searched online and cannot find a thread where they actually manage to sort the problem.
Presumably what I want to do (install a custom Rom) is not impossible as there are so many Roms etc available for the Note 3, I am just a bit stuck as to my next step.
Any help appreciated.
Thanks
Use TWRP or Philz Recovery .
Thanks for the reply JJEgan, I tried Twrp also to the same effect. I did try Cwm first though, is this a common thing when using Cwm or have I done something wrong?
Im going to flash a stock 4.4.2 from SamUK and try again from scratch to see if it made a difference coming from 4.4.2 instead of 5.0 and then TWRP
Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet
Hi guys, to my understanding BL/CP are available in tar or zip formats and may be updated via Odin or Twrp respectively. Appreciate any advice as to differences (if any) between the two methods. TIA
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
CuBz90 said:
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
Click to expand...
Click to collapse
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Xp3riaXpr3ss said:
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Click to expand...
Click to collapse
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
CuBz90 said:
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
Click to expand...
Click to collapse
True that. I only ever return to Odin to flash official firmware in the event of soft bricks with denied access to Twrp, however, was getting confused partly due to written instructions for roms requiring BL/CP to be flashed in download mode. Thanks for clearing this up. Cheers.
my current booloader is version 1...can anybody tell me how can update it to version 4? i am using s7 edge SC02H(snapdragon) japan.
thanks
Looking for the right modem and bootloader files
Hello,
I'm running Nougat on my s7 g930f it's using the tgp rom. In preparation for an oreo upgrade I atempted to flash an odin-zip file I found on LightRom's page, thinking it would give me a modem update. This was an extremely bad idea. Now my system does still boot, but I have no signal at all, my phone number, base band, IMEI, mobile network, etc all show as unknown under settings, about phone and the various status checks. Now when I atempt to go in to odin again to flash another modem update now I'm told that the atempt has failed. I'd appreciate some help. What file do I need to get the bl and the cp file? I'm running twrp 3.2.3, and i'd like my signal back.
Thanks.
Dave.
I recently upgraded my phone software from 4.4.2 to 5.0.1 and i need to download xposed again and when i searched online it showed that i need to download twrp and i tried this method using adb
https://www.xda-developers.com/how-to-install-twrp/
but after entering the step 4 ,the command control just "showed a searching for device message" .
i had also tried via odin but recovery did'nt show up when i pressed volumeup+power+home . just a bunch of letters on the top right corner . Pls help me (i am a noob)
Forum for the 337m is here: https://forum.xda-developers.com/galaxy-s4-att
Use Odin to flash the tar version of TWRP.
could'nt boot into twrp recovery
audit13 said:
Forum for the 337m is here: https://forum.xda-developers.com/galaxy-s4-att
Use Odin to flash the tar version of TWRP.
Click to expand...
Click to collapse
i tried your method and decided to see if it was working properly and i followed the instruction for rooted devices in https://www.xda-developers.com/how-to-boot-to-recovery/
Not only it did'nt work now my phone is just displaying the samsung galaxy s4 logo with words on the top left corner that says
recovery booting. . . .
recovery is not seandroid enforcing
set warranty bit : recovery
i just also checked the twrp manager app https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
it shows "custom recovery not installed or not detected"
How did you flash TWRP? You confirmed that the model # of the phone is sgh-i337m?
I could never get the fastboot instructions in the original post to work since all Samsung phones (non-Google Play versions) I have used did not support fastboot commands.
audit13 said:
How did you flash TWRP? You confirmed that the model # of the phone is sgh-i337m?
I could never get the fastboot instructions in the original post to work since all Samsung phones (non-Google Play versions) I have used did not support fastboot commands.
Click to expand...
Click to collapse
I downloaded the .tar file from the team win website for the samsung galaxy s4 canada and i opened odin .
switched off my phone , put it in download mode (volume down+power+ home ,pressed volume up again for confirmation)
connected to computer , odin shows added , clicked AP selected the .tar file and clicked start without making any changes in the options tab . Phone restarts
Flashing TWRP with Odin on a phone running a stock ROM will replace the stock recovery; however, if auto reboot is selected in Odin, rebooting the phone after flashing TWRP will cause the stock recovery or overwrite TWRP and this is one reason some people uncheck auto reboot.
I suggest starting over by flashing the latest stock ROM from sammobile.com with Odin 3.07.
audit13 said:
Flashing TWRP with Odin on a phone running a stock ROM will replace the stock recovery; however, if auto reboot is selected in Odin, rebooting the phone after flashing TWRP will cause the stock recovery or overwrite TWRP and this is one reason some people uncheck auto reboot.
I suggest starting over by flashing the latest stock ROM from sammobile.com with Odin 3.07.
Click to expand...
Click to collapse
I have just flashed my phone with stock rom from sammobile , after that i put into download mode again and did'nt select the autoreboot . when it was completed i tried going into recovery mode without switching on my phone so i removed the battery and placed it again and pressed volume up+power+home and i still got the same things that showed up before .
Did you try flashing different versions of TWRP? I suggest starting with 2.87. You can then use TWRP itself to flash newer zip versions.
audit13 said:
Did you try flashing different versions of TWRP? I suggest starting with 2.87. You can then use TWRP itself to flash newer zip versions.
Click to expand...
Click to collapse
Thank you so much . It finally loaded twrp and i started with version 2.8.4.0 FYI .
That's great