Hi,
i have serious problems with my S4(i9505):
I rooted it when i got it and have installed various roms so far. The last working one was "liquid smooth".
Then it begann to reboot from time to time and when the problems got worse i decided to reinstall again... now, i think my problems arrived with the 4.4 roms. I installed pacman and tried to boot, it didn't work and i think that's when my bootup sequence changed, now i have a little text in the corner saying "kernel is not seandroid enforcing. Set warranty bit : kernel"
so i thought something must be wrong with the kernel and installed various kernels, hoping to clear that message in the corner. At some point i realized that this only makes my situation worse (s4 reboots directly after booting, while bootin, while finishing up "first boot", it gets stuck in bootloops, etc).
Right now i'm not even sure if i understand the whole concept of kernels and roms anymore... so i decided to ignore the message for now and focus on getting my phone to work... i installed some roms again, some (i think the 4.2'S) seem to work, the 4.3's all crash while booting...
i managed to get liquid smooth back on it again (2.9).
Oh and i tried reinstalling stock kernel but the installation under CWM aborted.
Now i can use basic phone options again, but as soon as i flash gapps(no matter on which rom (Cyanogen, pacman, liquid smooth), the phone won't boot anymore, i re-downloaded the package several times, it's the latest one, so it should be okay...
S4 google edition of course doesn't work at all ...
Anyone an idea, how i can get google apps back ? Or basically just get my phone to work ?
Furthermore : How do i clear the message (kernel is not seandroid enforcing)? My basic goal is to have a working android 4.3 enviroment with gapps...can't be that hard ...
i spent the whole day on that, i have used searchfunction not only on this forum, so sorry if i have missed a thread stating the same problem. Plus: i need someone to talk to
EDIT:
I've installed Stock ROM, now it keeps rebooting at the point where i can set up wlan ...
Related
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
zuuus said:
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
Click to expand...
Click to collapse
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
ultramag69 said:
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
Click to expand...
Click to collapse
Hey mate, last version of firmware was the Stock Telstra SM-N9005 / TEL ROM I found on www . sammobile . com/firmwares/2/
I have tried at least 10 different ROMs with no luck, every single one does the same thing.
I did send it off to Telstra to try for a repair, they sent it back to me unrepaired due to nothing to do with the software but a 1/4mm scratch my keys made in the chrome plastic around the edge with the words "unable to be repaired due to physical damage" with a little sticker pointing to the scratch. ****ing ridiculous if you ask me.
Honestly I don't know all that much to do with the modems and csc's so it might be that causing my problems but I have tried a bunch of different ones without any change.
At my wits end here, phone is just over 30 days old and I can't use the damn thing.
try odin back to stock, then use kies to "emergency firmware restoore" Kies can be a life saver in some situation, make sure you use beta 3 version
First of all, hello all!
I'm a new member here.
So, what's the problem? Well, I recently rooted my Galaxy Tab 4 SM-T530 (WiFi only version) with Kingroot. Then I installed Cyanogenmod from the thread listed at the ROM section. All was working fine up until I decided to flash the GApps.
I chose the newest versions (both Zero and Mini for 6.0) but none of them worked.
Flashing went well. The problem was after booting.
After the first boot, I'd get caught in an endless loop of errors stating that "Unfortunately, Setup Wizard has stopped working". I couldn't do much other than rebooting. But then, I was greeted with yet another problem: it was stuck in a boot loop. Basically, after saying that it "Prepared Google App" and some others, the tab would repeat the process in an infinite loop. I left it for half an hour to do so, but the problem persisted.
Keep in mind the fact that I installed the newest version of Mini GApps package provided from that thread.
If any of you can help me out with this, I'd be very thankful, since this is the same time I install a custom ROM, and I really don't want to come back to the old Samsung ROM
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
This is from where I installed all things needed.
Try again, this time flash both zips at the same time and not doing anything in the middle of both flashes. The usual cause of the same error in my other s3 is booting the ROM up, going back to recovery, then flashing GApps.
I never did anything else. Now I wiped data/dalvik/system/cache, reflashed the ROM and now just finished reflashing both zips in TWRP (first Mini then Zero, can't do them at the same time).
Now, I'm pretty much 'fingers crossed', as this is what an error told me. Pretty much tried to flash the zips without wiping anything/reflashing the ROM. That's why I went for a clean install.
EDIT: it didn't work at all. Still caught in the same "Preparing app x" boot loop. Now I'll let it run for 6 hours and see if not my own impatience is the problem.
EDIT 2: For some reason it took ages to boot up. Now, when I finished booting, I saw that the Play Store, Quick Search Bar and the Google Services weren't working at all. I tried to manually update them, but ended up in an agonizing loop of "Unfortunately, Google Services Framework has stopped" errors. Again, this leads me into thinking that the GApps from that thread aren't working.
First post, So hey everyone
So I rooted my phone around 6 months ago with CF Auto Root, everything went fine but i was still on stock ROM. So then i found the Alliance ROM and decided to flash that because it looked cool. I flashed it using FlashFire to ensure I keep root. Everything worked and booted just fine, really smooth and of course it looked awesome. One small problem though, I could not send messages but I could receive them. Probably a SMSC (that was around 3 hours of head ache attempting to fix that) issue or because Straight Talk didn't like my phone using Android 5.0. So then I tried downgrading to Alliance 4.4.2, NOPE. That was the end of my phone :'(
Im now stuck on the Galaxy S5 screen with "Set Warranty Bit: Kernel" in the top right. No idea how to fix it and obviously knox was tripped but that isnt a huge deal to me.
I have tried the following.
1. Tried to reroot (seemed to fix a lot of issues actually)
2. Tried to reflash Alliance ROM android 5.0
3. Multiple cache and system wipes.
4. Installed TWRP through Odin but thats useless because I was dumb and deleted my back up in the system wipe
Im currently downloading stock ROM but my hope for that is fading judging that TWRP even stalls out and the phone reboots right when it attempts to flash. - well this was a bust, there are 4 freaking md5 files. when i go to flash with odin it says it a modem and then fails
What i have access to:
1. Recovery
2. Download
Is my phone already 6ft under or is it hanging on for dear life?
Edit: Should also mention that my galaxy is a SM-G902L (Straight Talks' model???). CF Auto Root for Galaxy SM-900F was used to root. So that is what i based my choice for model when installing Alliance
Ok so recent update, When I go into reboot and do system or whatever, it says there's no OS installed. I guess that would make sense why it doesn't want to boot, because there's nothing to boot into... but why cant i install any OS through odin???
Another Update: So I have no OS, I know how to flash a new OS, such as a custom ROM, but my phone refuses to accept the flash whether through odin or through TWRP.... W.T.F. Did i really look my phone down? And I guess that means that I will need to get the Straight Talk variant of Android 4.4.2 Great If anyone has the a backup and they are on straight talk, please help me out
Thanks for the help!
FIXED!!!
So after around 14-16 total hours of headaches, I have managed to bring my phone out of the grave. I read over the Straight Talk Variant Galaxy S5 thread multiple times and saw people saying that most Verizon ROMs work decently if not perfectly fine with the SM-G902L. So I downloaded M.O.A.R ROM and flashed through TWRP.
Worked like a freaking charm!! She booted right up, into the waterspout boot animation, and after a very long 5 minutes, I got to the welcome and setup screens!! I guess it was just a matter of finding the right ROM. I just find it kind of weird that it would flash Alliance just fine and then not allow it the second time...
Anyway, the very helpful thread that saved my phone
http://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-straight-talk-variant-sm-s902l-t3162340
So i i wanted to install a clean rom on my note 3 and got this a message when phone is booting.
thats how it started:
-Installed Odin , then installed TWRP then SuperSu with TWRP.
- Downloaded the LineageOS for note 3 and GAPPS, insalled it and it wasnt stable at all
Had every few minutes restarts with the message "Set warranity bit kernal" at top of the screen.
- Decided to try other rom(MagMa NX s8) , so i download older TWRP for this , installed the rom properly and then reboot
and its got stuck into this message again "Set warranity bit kernal" and didn't boot into the rom at all..
I wanted to try this ROM so hard heh..
- Now im with Resurrection REMIX which is stable and no restarts or bugs, but the message is still there when the phone is booting up.
tried so many things to fix it , could find away tried different kernals, didn't help , tried YouTube guides - none worked for me.
anyone is familiar with this issue?
arlxcvi said:
So i i wanted to install a clean rom on my note 3 and got this a message when phone is booting.
thats how it started:
-Installed Odin , then installed TWRP then SuperSu with TWRP.
- Downloaded the LineageOS for note 3 and GAPPS, insalled it and it wasnt stable at all
Had every few minutes restarts with the message "Set warranity bit kernal" at top of the screen.
- Decided to try other rom(MagMa NX s8) , so i download older TWRP for this , installed the rom properly and then reboot
and its got stuck into this message again "Set warranity bit kernal" and didn't boot into the rom at all..
I wanted to try this ROM so hard heh..
- Now im with Resurrection REMIX which is stable and no restarts or bugs, but the message is still there when the phone is booting up.
tried so many things to fix it , could find away tried different kernals, didn't help , tried YouTube guides - none worked for me.
anyone is familiar with this issue?
Click to expand...
Click to collapse
thats not an issue. Its normal if you had flashed a custom ROM. I am running RRN only for the past 4 months... that message has always been there for long time.
Hello XDA! I recently came into ownership of two Galaxy Tab 4 10.1 WiFi tablets that came factory reset with Android 5.0.2, they are the SM-T530NN variant for education as these came from a school - and I wanted to flash them with LineageOS. I had already rooted and flashed my Nexus 7 with LOS with no issues and really like it, so I figured I would do that too on these Tab 4's.
The problem I am running into is once I install LineageOS and Supersu from TWRP, the tablet reboots and can't get passed the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
I've read that this is not an error, and has something to do with the rooting process or possibly the ROM that I used itself, but nonetheless, it just sits at that error and never fully boots, hence why I can't just ignore it. My OS appeared to install with no errors. Other posts that I have researched on this forum concerning that message don't fully provide me with a solution I can replicate. However, I still have access to download mode and TWRP recovery upon boot so all does not appear to be lost.
I started with thisisapoorusernamechoice's guide (which was awesome by the way) for rooting and have kinda gone from there, trying newer version's of TWRP but am still stuck at boot.
Here are the files/versions I have used:
Odin 3.11.1
twrp-3.0.0.9_matisse_20160314-0843.tar (and 3.0.3.0)
lineage-14.1-20170319-UNOFFICIAL-matissewifi
supersu 2.79
Any help would be greatly appreciated.
***UPDATE***
Never saw any replies to this post so I decided to just try a different ROM, went for Bliss 6 to see if it would boot. Sure enough I still get the same message as before but it does boot up and is usable! Some minor things are not working like the camera app crashes upon opening, and the lock screen date and time are all smashed together - but these are minor inconveniences as these tablets will only be used for Plex, not taking pictures. Plus I still have a TWRP backup of the stock ROM should I choose to go back to that.