Hi.
Today, during the installation of a custom rom (liquid death, coming from lineage), i accidentally checked the wipe internal storage box so i reinstalled the last marshmallow stock firmware and twrp with odin.
Then i downloaded the rom again and flashed it with twrp, but during boot always appear a message saying "kernel is not seandroid enforcing", then the device starts normally.
How can i fix this error?
Thank you for your help and sorry for my bad english.
Hello
Same problem here
Does someone have a solution ?
Thx
Me too
m21an said:
Hi.
Today, during the installation of a custom rom (liquid death, coming from lineage), i accidentally checked the wipe internal storage box so i reinstalled the last marshmallow stock firmware and twrp with odin.
Then i downloaded the rom again and flashed it with twrp, but during boot always appear a message saying "kernel is not seandroid enforcing", then the device starts normally.
How can i fix this error?
Thank you for your help and sorry for my bad english.
Click to expand...
Click to collapse
Same here on custom ROM.its all to do with the bootloader but I have the correct cpk2 one installed
m21an said:
Hi.
Today, during the installation of a custom rom (liquid death, coming from lineage), i accidentally checked the wipe internal storage box so i reinstalled the last marshmallow stock firmware and twrp with odin.
Then i downloaded the rom again and flashed it with twrp, but during boot always appear a message saying "kernel is not seandroid enforcing", then the device starts normally.
How can i fix this error?
Thank you for your help and sorry for my bad english.
Click to expand...
Click to collapse
Did you fix your problem ? I am having the same one. I appreciate any kind of help
Same issue.
medogan said:
Did you fix your problem ? I am having the same one. I appreciate any kind of help
Click to expand...
Click to collapse
Anyone find a fix?
katrsx said:
Anyone find a fix?
Click to expand...
Click to collapse
Just flash supersu and it will go away.
Not seandroid enforcing
ashyx said:
Just flash supersu and it will go away.
Click to expand...
Click to collapse
Does this error effect functionality? Like some apps are "not optimized for my device" error?
Related
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Improper recovery.
samelaryan said:
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Click to expand...
Click to collapse
BAM1789 said:
Improper recovery.
Click to expand...
Click to collapse
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
xBeerdroiDx said:
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
Click to expand...
Click to collapse
I did that and it worked thank you :good:
samelaryan said:
I did that and it worked thank you :good:
Click to expand...
Click to collapse
thats what we're all here for, buddy
Status 7: installation aborted.
xBeerdroiDx said:
thats what we're all here for, buddy
Click to expand...
Click to collapse
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
perceptorz said:
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
Click to expand...
Click to collapse
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
xBeerdroiDx said:
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
Click to expand...
Click to collapse
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
perceptorz said:
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
Click to expand...
Click to collapse
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
xBeerdroiDx said:
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
Click to expand...
Click to collapse
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
perceptorz said:
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
Click to expand...
Click to collapse
I would take up this situation in the correct forum. The more we discuss your device issues the more likey you are to download the wrong file or use a procedure not designed for your device software.
If you came from stock, flashed a rom and are stuck at the samsung logo, boot into recovery, wipe data and cache. Reboot to see if that helped. If not, seek advice in the N7000 forum. Cheers
Thanks for the guidance.
Hello Everybody,
i am using this rom 4.3 from a while ago and i wanted to change it to the 4.4 rom
i decided to flash Omni 4.4.2 new rom from this url
http://forum.xda-developers.com/showthread.php?t=2487526
As per the installation instructions i went to download TWRP ver. 2.6.3.1 from here
http://techerrata.com/browse/twrp2/t03g
and i installed it through Odin, and when i tried flashing the rom through TWRP it says successful when i do factory reset and when i try to format data it says failed and when i try to flash the rom it says failed
it keep saying
e:/ unable to find partition size for "/data"
am not developer or expert, but i used to flash many roms for all my past android devices and this is my first time to see such error
well, the device still working when i exit TWRP and do system reboot my rom boot up normally and the device is perfectly working on my phonix 4.3 rom
but i noticed that Odin can not detect my device on the downloading mode anymore but it still can detect it if the device is turned on
So, could you guys advise about what exactly i had missed or damaged here? can i flash other roms? or recovery?
please give me some help here in deep details as am really new to such errors
Thanks a lot in advance and Happy New year for everybody
hey guys, any updates?
I m having the same problem, ay solution?
Mee too: http://forum.xda-developers.com/showpost.php?p=69313945&postcount=45
Mohamedloza said:
hey guys, any updates?
Click to expand...
Click to collapse
Jotapoggi said:
I m having the same problem, ay solution?
Click to expand...
Click to collapse
You still have the problem?
Sent from my Xiaomi Mi 5 using XDA Labs
hi friends
LG G3 D855 - Android 5.0-ROOT
I want to install the CUSTOMROM. I installed TWRP. I restart the phone, I see Secure Booting Error! Cause: boot verify certification.
Then the phone turns off, the warning light starts to burn ...
I wear again, remove the battery, the phone works.
-
I want to Twrp to install custom ROMs ..
1. I installed Kitkat
2-Root
3-I installed TWRP.
4-Phone I rebooted, it s work for the ... (TWRP working)
5-. I install custom ROMs and bump with TWRP
6- I restart the phone, I got the error again (Secure Booting Error! Cause: boot verify certification.)
I restart the phone, remove the battery, but I always get the same error.
I install android 5.0 with Lgtools, phone is working. But I want to install custom ROM. How do I make
????
i believe the error may be with the kernal. boot into twrp and try flashing one of these and report back
->http://forum.xda-developers.com/lg-g3#kernels
kp_q said:
i believe the error may be with the kernal. boot into twrp and try flashing one of these and report back
->http://forum.xda-developers.com/lg-g3#kernels
Click to expand...
Click to collapse
when i install TWRP , ı have Secure boot error
ftekinsen said:
when i install TWRP , ı have Secure boot error
Click to expand...
Click to collapse
????????????
??? help pls
i fix it i can help about this topic anybody ...
Please post your solution; I just rooted and flashed TWRP, and now I cannot reboot into recovery.
FIXED
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
ftekinsen said:
i fix it i can help about this topic anybody ...
Click to expand...
Click to collapse
Would love to hear the fix. Happening to me today.
Thanks!
How to fix it? Can you tell me the step?
I really have the problem like you, want use custom rom but can't reboot in recovery mode
ftekinsen said:
i fix it i can help about this topic anybody ...
Click to expand...
Click to collapse
hey i have this issue on att g3 installed twrp through auto rec now boots to security error screen. how can i fix this?
Since you have twrp just flash a kernel or a new rom through twrp.
Cool thanks man. I was kinda stuck there. I couldn't get my pc to see the phone, had to wait for a micro sd card to put the kernel on. Thanks a lot
Sent from my LG-D850 using XDA Free mobile app
Hello Friend
I just have same problem like you + the when I connect the G3 to my computer it did not recognize it
many tanks for your help
This worked for me
this - http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
LG G3 LS990 - ZVB - Rooted + TWRP - Flash Stock Recovery Only
Hi, I am looking for flashing stock recovery on my LG G3 Sprint LS990. I believe the same method will work. I am currently running on stock ZVB ROM rooted and TWRP installed as recovery. In the download folder for LS990-ZVB http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVB, there is no recovery image file, but in ZVA folder there is. I am just wondering if I can flash ZVA folder's recovery image using Flashify to my ZVB ROM LS990 and if that will work.
My LS990 is rooted and currently have TWRP. i get secure boot error when the phone reboots after accepting Android updates installation that come automatically. I believe installing stock recovery will resolve this issue and allow to install Android updates I do not want to going back to stock completely, that will unroot my phone and again I have do all these staffs.
Anyone can help to advise, will be appreciated. Thanks.
Worked for me
It's not english, it is portuguese Brazil, but it works.
youtube.com/watch?v=gHAA5e2FQbU&index=1&list=LLtlXyuPzN6skeex-P2apfrQ
autorec does the job for me.... thanks dev
Secure Boot Error 1003
ftekinsen said:
i fix it i can help about this topic anybody ...
Click to expand...
Click to collapse
Ian having this issue I really would like help resolving.
Hey guys i have an issue i was using Community build nougat and i got the ota update through the system update which was about 113mb i tried it thinking it would only reboot in twrp modified one, well it did reboot but since then i can't reboot my mob everytime im rebooting its rebooting in twrp. i had freedom os on my internal storage i've flashed it again but in vain when rebooting its booting to twrp anyone has an idea what i need to do now?
please close thread i found my answer
House_Maniac said:
please close thread i found my answer
Click to expand...
Click to collapse
How did you fix this? I have the same issue.
Beukhof1 said:
How did you fix this? I have the same issue.
Click to expand...
Click to collapse
I downloaded the full zip and also ive flashed twrp again via fastboot
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.