Related
So I was going to try the new Sense ROM for my I9000 and this is what happened:
I flashed the Speedmod kernel via ODIN, got into recovery - then flashed efs-backup.
After that I flashed the CM7 kernel via ODIN, did a system, cache and data format and installed the rom itself.
Now every time I turn on the phone, it gets into recovery... same happens if i press reboot system now in clockworkmod recovery
Is there still hope for me? All your help is appreciated!
this has happened to me too.
what happens is when you format system you actually format the OS on the phone. meaning that the only thing installed on the phone is the kernel.
resulting in a loop of recovery mode.
flash the rom again through recovery and see where that takes you.
if problem still persists. start whole process again
azzledazzle said:
this has happened to me too.
what happens is when you format system you actually format the OS on the phone. meaning that the only thing installed on the phone is the kernel.
resulting in a loop of recovery mode.
flash the rom again through recovery and see where that takes you.
if problem still persists. start whole process again
Click to expand...
Click to collapse
Yeah, but I did that before I flashed the ROM... Tried it again, still the same thing. (And I tried the whole thing from the beginning over and over again)
have you flashed back to froyo with 3 files and pit ?
what rom was you on before this happened, as it could be down to gingerbread bootloaders
I was on Froyo, Voodoo kernel
well just try 1 last time, make sure the FW comes in all 3 files, use 512 pit and check repartition in odin.
then take the necessary steps to get back to the sense ROM
I have a Sprint Samsung Galaxy S4 that was running JB 4.3. When I decided to root and ROM it, I read a lot. I'll tell you what I did and where I got my files so you know exactly what happened:
In Download Mode:
First I Odined UnknownForce's NAE Modem Only Firmware with No Bootloader
Then I Odined Philz Touch Recovery 6.15.6
I booted to Recovery.
I cleared Cache and Davlic Cache twice.
I did Wipe/Factory Reset twice.
Then I flashed using Rawintellect's Stock(ish) Rom.
I install Ktoonsez Kernel for Sprint Touchwiz
At this point I am running a custom rom with a custom recovery and a custom kernel. It runs great.
I have no SEAndroid messages about the kernel or recovery at this point.
I decided to upgrade to Kit Kat 4.4. I did a nandroid backup. Then I took the official Sprint MD5 update and Odin it right over my rom. It worked. When the system boots up, it is running the Touchwiz version of Kit Kat. But I don't have root.
So I go to recovery to flash CF-Auto-Root-jfltespr-jfltespr-sphl720.zip but I'm back to stock recovery. So I go to download mode and re-Odin Philz Touch Recovery 6.15.6. Then I reboot to recovery.
There is an SEAndroid Recovery Message! But it lets me into recovery and I flash the zip. Reboot.
Since I was back to stock recovery, I check the kernel in settings. It's back to stock to. So I boot back to recovery and reinstall the custom kernel. Reboot to system.
There is an SEAndroid Kernel Message now! But it lets me into the system and I have root. I run Titanium Backup and remove Knox Files according to these instructions. I used method two for rooted phones. I also use method three.
Rebooted. Still showing the SEAndroid messages.
So I booted to download mode and re-Odined the NAE Modem Only Firmware with No Bootloader. Shut down phone and rebooted.
Still have the messages! Now I'm frustrated. So I do a Nandroid Backup of the KitKat Version and restore my nandroid backup of the Stock(ish) rom.
Phone works but I still have the SEAndroid messages! So I restore my nandroid backup of Kit Kat and started researching this.
What I know:
Though the messages may cause issues and boot loops for some, it is not doing it for me.
The messages do not hurt the functioning of the system.
I know the Knox counter was tripped from 0x0 to 0x1. (I never saw the Knox counter till I did this In fact!)
I know going back to stock recovery and kernel will remove the messages.
What I want:
I know the "Kernel/Recovery is not seandroid enforcing" doesn't hurt the phone but I want the message gone. I was on a rooted phone with custom rom, recovery and kernel without these messages showing up. Something is different from the way the phone was setup before and now. I don't want to go back to stock anything.
The SEAndroid is software. Software can be removed.
How do you remove it?
I know Knox was tripped somewhere in this process. Will that cause the message to appear even if your running without a boot loader?
How can I remove the SEAndroid software so it doesn't even run? Any ideas?
When you created your backup via Philz/CWM did you make sure to set the nandroid settings to back up SE Linux context? if not that is probablye your issue.
SE Linux context?
leaderbuilder said:
When you created your backup via Philz/CWM did you make sure to set the nandroid settings to back up SE Linux context? if not that is probablye your issue.
Click to expand...
Click to collapse
I don't know what SE Linux context is? Is it something I can do now? If not, what other options do I have?
It's in the misc nandroid settings.
Too late now if you didn't do it when you created your 4.3 backup though.
Will Any Nandroid Backup Work?
My wife and I bought the exact same phones on the same day. When it came to installing the Stock(ish) rom, I did the exact same thing to her phone. She insist that I experiment on mine before I do anything to her phone.
She does not have the "Kernel/Recovery is not seandroid enforcing" messages.
Can I do a complete Nandroid back up of her system and the SE Linux Context, copy it to my SD card and install it? I know it would be an exact duplicate of her system but I have all my apps backed up with Titanium Backup so I can re-install them easily. And of course I would have to log into my Google account and delete her account. Would that put me back the way I was?
I doubt it -device id stuff in Android.
BUT there is a way to get you back most likely.
IF you didn't upgrade to NAE(or MK2) bootlader and just the modem (as you mentioned) the simplest thing to do would be to install stockish fresh.
Let it boot and then add your google account and let all the apps update - about 1/2 hour on wifi
Then load/install titanium ( if it didn't install) go to preferences and let it find/search for your backup directory and restore - you'll be asked first to 'restore device ID' choose YES and let it reboot!
Then you should be good to go. I know I've done this a few times.
Another bonus is that you'll have a fresh install to 'start from'
Titanium Backup May Hold The Key?
leaderbuilder said:
I doubt it -device id stuff in Android.
BUT there is a way to get you back most likely.
IF you didn't upgrade to NAE(or MK2) bootlader and just the modem (as you mentioned) the simplest thing to do would be to install stockish fresh.
Let it boot and then add your google account and let all the apps update - about 1/2 hour on wifi
Then load/install titanium ( if it didn't install) go to preferences and let it find/search for your backup directory and restore - you'll be asked first to 'restore device ID' choose YES and let it reboot!
Then you should be good to go. I know I've done this a few times.
Another bonus is that you'll have a fresh install to 'start from'
Click to expand...
Click to collapse
That was one thing I was worried about. When the update I did redid the recovery and kernel, did it redo the boot loader too? That was one reason I re-installed the NAE modem without bootloader a second time.
So are you saying that I re-install Stock(ish) fresh then do a COMPLETE Titanium restore and not just certain apps? Would that reset the SE Linux Context so the SEAndroid messages don't appear?
I know in the past when I have played around with roms, Titanium may prompt me to "Restore My Device ID" so that all my apps will work. If I used my wife's Nandroid backup, wouldn't it ask to restore my device ID anyway? Would that bypass the Device ID problem?
Thoughts?
EDIT: I just saw THIS in another thread! It looks like the Nandroid backup may work.
When you say you did the update I believe you are/were talking about just the firmware/modem, is that correct?
And if you added a recovery that won't affect the bootloader.
You can try the nandroid option it may work
If you have a titanium backup of your phone you'll be able to restore nearly everything after you re-flash stockish.
So if you dont' then don't user hers.
As for SE linux context as long as you MF9 Booloader and you can check by downloading this app and running it (It'll show bootloader version) then you can re-install stockish and then as above re-sync your google account which will grab your apps and other settings -wifi, hotspots email etc. (just not specific application settings)
One thing I got to thinking if you are on MF9 and just borked you restore you can always just try 'dirty flashing' stockish. Just go to recovery, wipe cache, wipe dalvik and then flash over existing ROM (don't delete data) and you might just be good to go! If not then full wipe and restore.
Again just make sure we are talking apples to apples with regard to the bootloader being MF9.
Here's an update:
I made a fresh nandroid backup of my wife's phone. Copied it to mine. Wiped the phone and installed backup. Phone worked fine but the seandroid message is still there.
Wiped phone again. Reinstalled Stockish rom. Then installed an old nandroid backup I had from January. Message till there.
Then I went crazy. I went to Odin, did a nandroid wipe and re-partioned the whole phone. (Don't not try this at home! Seriously. DON'T.) I was able to bring back the phone because I had the pit file for the partitions.
No pit file, no partitions, no phone. You will have a brick.
Then I installed the modem without the boot loader and recovery. Booted to recovery.
The message was still there.
WTF!
Installed Rom and brought phone back to life. I'm on the NAE bootloader. When I've tried to downgrade, Odin errors out.
Where does the boot loader reside? It wasn't there when I bought the phone. It was installed later so it had to go somewhere.
Thoughts anyone?
Sent from my SPH-L720 using xda app-developers app
Well right now I'd just Odin the NAE .tar. It's got all partition info and will load, boot, recovery(stock), system, data, modem/baseband. Wiping all other/old partitions.
Only thing is you'll have the knox bootloader. BUT that really isn't a big deal - you can root using the LATEST CF-Autoroot from Chainfire's thread/site. Install a custom recovery and then install just about anything (well following the devs instrucions as per their OP).
The 'knox bootloader' is more than just a simple 'boot' partition - it's an actual cmos/chip write change! That's how they know and can track if you've tripped it. So far no, that I know of, has found away around this. The boot partition - in standard terms is still editable; hence the ability to create custom recoveries.
Good luck.
My girls S4 is Sprint.. Also with the NAE bootloader and I've wondered how to get rid of this stupid boot screen.
I've Odin the thing at least 3 times and rooted with CF then installed Philz. Each time no dice.
Now my Verizon S4 automatically backs up SE Linux Context. I never noticed a setting for that in Philz. Now maybe I just missed it since her phone doesn't get flashed all that much and like I said I'm on a Verizon S4.
I figured this was just a bi product of having a Knox Bootloader and having the phone rooted/custom recovery.
I'd love to figure out how to get rid of that screen though. I'll have to do some searching. Tri Angle Away gets rid of my " custom" Splash screen at boot... It'd be nice it it also got rid of this screen on the Sprint S4. I'll at least give it a whirl but something tells me its not that easy.
Sent from my SCH-I545 using Tapatalk
running this rom and gapps. upon boot up i receive this message in the top left hand corner: kernel is not seandroid enforcing, set warranty bit: recovery.
the phone seems to function fine. Whats up with it?
It's purely cosmetic. The shop can tell at a glance it's not stock rom this way.
Would be nice to find a way of making it disappear though, just plain untidy lol
same here
i guess still no solution to this? I have an s6 & have scoured the web & this thread has been the most informative resource on this issue that i've found. I started getting "kernel not seandroid enforcing" red text ever since i upgraded to 5.1. pretty strange. I know its proly different but my last phone was m8,and there was a red warning text on boot after root too (something about being for developers only...) . But there was a a special hboot mod that when flashed would remove it. Wish it could be that simple here ha! It drives me nuts, I dont know why but it does!
I have the s5 900f. I'm not new to custom ROMs and thought I'd give one a go for the s5.
Done system backup with twrp and flashed bliss. The ROMs is but I preferred the stock. Anyway I done a full wipe and then selected the restore. All seems to go well and the restore completes. But when restart the phone it starts to boot then fails. No error message or anything. OK I know I can flash another stock rom but I had the back just how I wanted it with all my settings and customisation.
I read a lot about the partitions being changed with a custom rom which can cause a restore to fail. I will flash a stock ROM then once I get it working I will try a restore again. Do I need to flash the pit file?
OK so previously have had htcs. On those I had to flash the bootloader via fastboot and then flash the ROM from recovery. Is it right that with the s5 the bootloader is bundled and flashed with the custom ROM? So when I reflashed the backup the phone still had the bootloader from the customer ROM? Can someone confirm if that is correct or not? I know how to fix my phone but I also like to learn and under stand what happenened.
Just flash the G900F PIT file along with a stock ROM in ODIN
PIT files should be avoided there are many risks while flashing them, albeit the procedure is as easy as it gets.
I would recommend getting Titanium Backup (i have the pro version so i don't know whether what i'm about to suggest is available in the free version or not) and then using titanium to "Extract from Nandroid backup" in the Main Menu and scrolling down to Special Backup/Restore
Hi Guys, I downloaded the stock rom from sammymobile and flashed it via odin. It also reset my recovery to stock as well but was is easy enough to fix
I then made sure the reactivation lock was turned off and reflashed my recovery back and I then reflashed my original backup recovery and success!
Tp recap if anyone else has this problem....
Download and flash the original stock rom,
Boot the phone and turn off the reactivation lock (you dont need to bother with account setup)
Flash the recovery (must be the same one you used for your backup)
Flash your saved backup
Done
Hopefully this gelps someone who finds themselves in my pickle.
To be honest after coming from HTCs I never appreciated the differences when it comes to rooting, customs roms etc. I now do!
So my galaxy s4 decided not to turn on anymore and is stuck in bootloop. It is really weird the phone either gets stuck at the samsung logo or gets stuck trying to boot into recovery but just doesnt make it in. I tried installing twrp but the same result where it is stuck trying to boot into recovery but never makes it. I also tried installing stock lollipop but it still doesn't boot up. PLZ help my nexus 5 just broke and now this phone isnt working either
You're using Odin to install a stock rom? Any errors when flashing with Odin? If Odin flash was successful, did you perform a factory reset before booting the phone for the first time with the newly-flashed stock rom?Did the stock rom come from sammobile.com?
audit13 said:
You're using Odin to install a stock rom? Any errors when flashing with Odin? If Odin flash was successful, did you perform a factory reset before booting the phone for the first time with the newly-flashed stock rom?Did the stock rom come from sammobile.com?
Click to expand...
Click to collapse
So i got the stock firmware for my s4 from sammobile and used odin to install it( downloaded fine) but after it just restarted and tried to boot into recovery mode unsuccessfully. I would have tried to do a factory reset but i cant since i cant actually get into recovery mode.
Open Odin, uncheck everything except f.reset time. Flash the rom. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use the button combination to boot into recovery, factory wipe, and reboot.
audit13 said:
Open Odin, uncheck everything except f.reset time. Flash the rom. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use the button combination to boot into recovery, factory wipe, and reboot.
Click to expand...
Click to collapse
Ok ill make sure to try that when i get back home. Thx for the help and the quick reply i REALLY appreciate it .
No problem. Good luck.
audit13 said:
No problem. Good luck.
Click to expand...
Click to collapse
OMG I LOVE YOU. I dont know how unplugging the micro usb and taking the battery out made a difference(i had flashed via odin many times unsuccessfully) but i cannot thank you enough
Glad it worked for you.
We're all here to help each other out.
Cheers.
If you wnat to install twrp and you don't like Odin too much I recomend you the app TWRP manager, you just need root, it's a very simple app
I prefer flashing TWRP via Odin as it has never failed for me.
My N910G that wont boot!
If I flash the latest TWRP I can access recovery mode and flash any ZIP however when the phone reboots after the installation of the new ROM, it always eventually gets suck on the NOTE 4 Logo after booting onto the Samsung Logo. I can access the the partitions in TWRP when I go to individually wipe them. I've noticed sometimes the phone doesn't remember when tick the checkbox for "dont show this message again" the first time you've booted into TRWP.
Things I've tried:
Full restore using the latest N910G firmware. (XSA-N910GDTS1DPH1-20160728112745)
Using the PIT file for a N910G and restoring the full original firmware
Clicking "NAND Erase All" in Odin and using the PIT file for a N910G and restoring the full original firmware.
Every time I do anyone of the above options the phone reboots then goes into stock recovery where it works for a little bit then restart and eventually gets stuck on the Samsung logo or reboots and gets stuck on the Note 4 Logo.
Any help would be MUCH MUCH appreciated, if anyone can help me get the phone working again I will gladly buy them one month to samsung-firmware.org or pay them the equivalent into palpay.
SudoBen said:
My N910G that wont boot!
If I flash the latest TWRP I can access recovery mode and flash any ZIP however when the phone reboots after the installation of the new ROM, it always eventually gets suck on the NOTE 4 Logo after booting onto the Samsung Logo. I can access the the partitions in TWRP when I go to individually wipe them. I've noticed sometimes the phone doesn't remember when tick the checkbox for "dont show this message again" the first time you've booted into TRWP.
Things I've tried:
Full restore using the latest N910G firmware. (XSA-N910GDTS1DPH1-20160728112745)
Using the PIT file for a N910G and restoring the full original firmware
Clicking "NAND Erase All" in Odin and using the PIT file for a N910G and restoring the full original firmware.
Every time I do anyone of the above options the phone reboots then goes into stock recovery where it works for a little bit then restart and eventually gets stuck on the Samsung logo or reboots and gets stuck on the Note 4 Logo.
Any help would be MUCH MUCH appreciated, if anyone can help me get the phone working again I will gladly buy them one month to samsung-firmware.org or pay them the equivalent into palpay.
Click to expand...
Click to collapse
This information has something to do? Can it help you?
http://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
After installing a new Rom, remove and put back battery. Then go to Recovery and do Wipe data/factory reset and Wipe cache. Reboot and wait, it will take a few minutes before rebooting.
This will erase though all your previous data from your old Rom.
ruicc said:
This information has something to do? Can it help you?
http://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
Click to expand...
Click to collapse
Thanks for your help I tired it on two different versions of Odin and every time it fails (from all my flashing on this phone this is the only time I've seen it fail). So we might be on the right track or the phone is beyond software repair
GrippingSphere said:
After installing a new Rom, remove and put back battery. Then go to Recovery and do Wipe data/factory reset and Wipe cache. Reboot and wait, it will take a few minutes before rebooting.
This will erase though all your previous data from your old Rom.
Click to expand...
Click to collapse
I've tried doing that