Hey, I flashed twrp 3.0.0 via odin on my s6 g920f 6.0.1 rooted device (custom kernel) and now I can't boot into recovery, my phone works well, also download mode, just recovery gives me Recovery is not seandroid enforcing and stuck there.
I know this message is normal and not concerning but it's still not booting into recovery, I flashed the wrong version?
Try reflashing stock 6.01 ROM via Odin. ?
latest official TWRP (3.0.2-0) does not support 6.0 bootloader, so that's why you are stuck on boot.
until a new fixed version is released, you can try to use 2 alternatives :
1. @arter97 version , thread here , download page here
2. idlekernel version , download page here
roydok said:
Try reflashing stock 6.01 ROM via Odin. ��
Click to expand...
Click to collapse
IDK.. my phone works pretty good, it still starts and no problem at all. only recovery isn't booting.
I don't want to format it and flash stock again just because of it.
djcristi said:
i heard that you need to flash custom kernel , that stock kernel cannot boot TWRP, because of 6.0.1 bootloader.
. I am on the same case now, looking for solution because i don't want to use custom kernel, just TWRP and root it using Supersu.
Click to expand...
Click to collapse
Actually I am running SpaceX MM kernel(auto root)... so twrp should be fine.
i edited my previous post, you have there solution.
djcristi said:
i edited my previous post, you have there solution.
Click to expand...
Click to collapse
Yeah and it worked. Also flashed xposed, when I installed greenify module it caused bootloops so I flashed xposed uninstaller, I guess no xposed for me
Related
Hi all,
I have an Galaxy Note Edge type SM-N915FY with custom rom installed: http://forum.xda-developers.com/note-edge/development/rom-micky387-rom-v1-0-t2998972
My phone is running on android 5.0.1 with kernel: 3.10.30-andrei-N915F-BOC6-v1.0
Baseband-version: N915FYXXU1BOB5
Yesterday I was trying to install the newer custom rom: http://forum.xda-developers.com/note-edge/development/rom-micky387lollifamous5-1-1v1-t3200849
To make sure this will work, I needed to flash the TWRP , after I tried to flashed this using Odin, the phone got in a Bootloop. So I flashed the older TWRP again and my phone is booting again.
So I tried to clear the cache, but then I get the error: Unable to mount \cache, I didn't know how to solve this so I reflashed the TWRP again through Odin, but still the same issue.
Do you guys know how I could install another custom rom? My phone is rooter, just to make sure.
Thanks in advance.
nobody?
notneeded said:
nobody?
Click to expand...
Click to collapse
To move on to newer custom ROMs (based on 5.1.1), you need to download and flash Stock 5.1.1, which you can download from here, then you can root it, to get the necessary files for doing so, check this thread out.
Credits for TWRP, new ROMs and the possibility of root on 5.1.1 go to micky387.
You Saved me. After I flashed the original android 5.1.1 I was able to flash TWRP and install custom rom.
Many thanks!
So i was trying to flash new 6.0.1 rom and i soft-bricked phone.... Ok then i flashed official 6.0 rom and then flashed TWRP and now i'm able to boot up the phone and use it but i cannot go into recovery for some reason. Also i get message recovery is not seandroid enforcing. Any idea how to fix this ?
lukaisailovic said:
So i was trying to flash new 6.0.1 rom and i soft-bricked phone.... Ok then i flashed official 6.0 rom and then flashed TWRP and now i'm able to boot up the phone and use it but i cannot go into recovery for some reason. Also i get message recovery is not seandroid enforcing. Any idea how to fix this ?
Click to expand...
Click to collapse
Yup, had the exact same problem, TWRP is just not officially supported for marshmallow yet. You don't have to flash the entire rom again, just open up the firmware file you extracted and look for 'recovery.img', just flash that through Odin like normal and your phone should be fine
lukaisailovic said:
So i was trying to flash new 6.0.1 rom and i soft-bricked phone.... Ok then i flashed official 6.0 rom and then flashed TWRP and now i'm able to boot up the phone and use it but i cannot go into recovery for some reason. Also i get message recovery is not seandroid enforcing. Any idea how to fix this ?
Click to expand...
Click to collapse
I had a same problem and it's solved!
TWRP 3.0.0 is not sp for Androi 6.0. Pls down TWRP 3.0.0 in after97.com. Flash it via Odin nomally , you can enter REc
tiamo2u said:
I had a same problem and it's solved!
TWRP 3.0.0 is not sp for Androi 6.0. Pls down TWRP 3.0.0 in after97.com. Flash it via Odin nomally , you can enter REc
Click to expand...
Click to collapse
It worked ! Thanks a lot
lukaisailovic said:
It worked ! Thanks a lot
Click to expand...
Click to collapse
What TWRP did you get it working with?
Hey .
i had XtreStoLite DeoMod Edition 2.4 maybe before with xposed framework installed
i did flash xposed-uninstall zip then did data and factory reset then flashed XtreStoLite DeoMod Edition 3.3.1 zip and when i reboot my phone stuck in (SAMSUNG Galaxy S6 powered by android) without anything more on the screen and nothing happens
and when i flash 2.4 back and reboot it show in red (recovery is not standard inforcing) and the rom boots with no problems
and after i have flashed bootloader and modem for mm i can't get into recovery mood anymore even after reflashing twrp
how could i fix 3.3.1 and boot to it ? please
Will you please tell us how did you solve it?
brenner650 said:
Will you please tell us how did you solve it?
Click to expand...
Click to collapse
first i forgot to install the modem and bootloader then after i installed them i did install lastest twrp (twrp-3.0.2-1-zeroflte) with odin instead of the correct one for that bootloader and modem from the rom post at the end of it (arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar) then i was be able to get into the recovery mod again and install the rom and everything worked expect it was not rooted but rooted it with cf-auto-root
I was running RR rom on my device then i wanted to change to aosp today but while flashing it got stuck at patching system image unconditionally for like an hour so i flashed the stock COS13 via fastboot.
I can flash MM based roms but no Nougat based roms (
EDIT:
I managed to fix my issue. i went back and flashed twrp 2.8.7.0 recovery and then flashed the latest firmware image. that seems to have fixed my issue. successfully flashed jgcaap's cm14.1 rom now <3
What recovery version are you using?
Re-download the zip rom and flash it again...
Spider-Vice said:
What recovery version are you using?
Click to expand...
Click to collapse
twrp.3.0.2-0 official
iPusak Gaoq™ said:
Re-download the zip rom and flash it again...
Click to expand...
Click to collapse
i can flash all MM roms. i tried to flash 2 nougat roms. both of which i had previously up and running.
Help me please!
K.rockr said:
I was running RR rom on my device then i wanted to change to aosp today but while flashing it got stuck at patching system image unconditionally for like an hour so i flashed the stock COS13 via fastboot.
I can flash MM based roms but no Nougat based roms (
EDIT:
I managed to fix my issue. i went back and flashed twrp 2.8.7.0 recovery and then flashed the latest firmware image. that seems to have fixed my issue. successfully flashed jgcaap's cm14.1 rom now <3
Click to expand...
Click to collapse
Even i'm stuck with the same issue. I flashed the latest firmware too, but it didn't help. I can flash all roms except android nougat roms. Please tell me the entire procedure. Thank you.
evdmello said:
Even i'm stuck with the same issue. I flashed the latest firmware too, but it didn't help. I can flash all roms except android nougat roms. Please tell me the entire procedure. Thank you.
Click to expand...
Click to collapse
Okay so buddy. now do exactly as i tell u okay?
1. flash the latest cm13 snapshot.
2. go to fastboot mode and flash this recovery https://www.androidfilehost.com/?fid=24367857647223599
3. reboot to the new recovery and flash this https://www.androidfilehost.com/?fid=24052804347825946
4. then you reboot to bootloader and flash twrp3.0.2-0
5. flash whichever nougat rom you want because it'll work now .
My samsung phone shows "samsung galaxy " and then just black screen . I INSTALLED CUSTOM ROOM and gapps using TWRP . When I rebooted this happend.
keni0 said:
My samsung phone shows "samsung galaxy " and then just black screen . I INSTALLED CUSTOM ROOM and gapps using TWRP . When I rebooted this happend.
Click to expand...
Click to collapse
Did you create a backup of your stock ROM before you flashed the custom ROM? If not, you should have. A prepared user always makes a backup via TWRP before making any kind of changes to the system and before flashing ROMs, that way they can restore the backup via TWRP if something goes wrong.
Can you boot into TWRP?
Droidriven said:
Did you create a backup of your stock ROM before you flashed the custom ROM? If not, you should have. A prepared user always makes a backup via TWRP before making any kind of changes to the system and before flashing ROMs, that way they can restore the backup via TWRP if something goes wrong.
Can you boot into TWRP?
Click to expand...
Click to collapse
I solve it by removing battery and then boot in recovery mode and flashed stock firmware , but I still can not install custom rom
keni0 said:
I solve it by removing battery and then boot in recovery mode and flashed stock firmware , but I still can not install custom rom
Click to expand...
Click to collapse
That is because you triggered Knox, you won't be able to flash anything custom now that Knox has been triggered. The firmware that you flashed, was it the same build number as what you had originally or is it a newer, updated firmware? If you flashed a newer firmware that has a bootloader that can't be unlocked, you will not be able to flash TWRP or custom ROMs.
Droidriven said:
That is because you triggered Knox, you won't be able to flash anything custom now that Knox has been triggered. The firmware that you flashed, was it the same build number as what you had originally or is it a newer, updated firmware? If you flashed a newer firmware that has a bootloader that can't be unlocked, you will not be able to flash TWRP or custom ROMs.
Click to expand...
Click to collapse
I do not know my old build number