T-mobile has introduced rollback protection for both kernel and bootloader. There is no going back or flashing a non signed kernel for now.
More info as this develops.
This is true, this OTA does NOT allow you to odin @eousphoros TWRP version. It also does not allow you to downgrade kernel or bootloader, this leaving you on stock until @Chainfire and @bigbiff can have a look at the OTA..This is a sad day for T Mobile users
Notice the splash screen as well, it says "RECOVERY IS NOT SEANDROID ENFORCING". Youl will get the same message when attempting to downgrade your kernel...
Bl rollback protection
so does the switch to unlock the bootloader in the developer options not have any bearing on the rollback protection?
This is great news, not more than 1 hour prior to the message getting posted i had finished loading 5.11, without greenify in rooted mode, it's already using more battery life than previously with root.. This totally stinks.
Dangit. If only I had waited 2 hours more.
bsimpson1 said:
so does the switch to unlock the bootloader in the developer options not have any bearing on the rollback protection?
Click to expand...
Click to collapse
It didn't for me. After switching that enable oem unlocking to on, I still had the above mentioned issues
Surge1223 said:
Bl rollback protection
Click to expand...
Click to collapse
Is it possible that this is fundamental to all 5.1.1 builds? The same thing happened to us on the Nexus 6. There were a few whom unknowingly downgradded their bootloaders, and ended up hard bricking their devices.
Even on reboot, in developer options, the toggle for "Allow OEM Unlock" would switch to the off position. This didn't mean that the bootloader was locked, but it did mean that you had to reset it. Most rom devs have since flipped the switch on startup.
My hope is that you will soon have working recovery and root on the latest firmware, irrespective of whether you can or cannot downgrade.
Curious, can we build a new ROM that includes the @eousphoros kernel, the OF6 system.img, and modem.bin? (without including the new OF6 kernel or the new sboot.img?)
Edit: Upon further thinking, there'd be no reason to use a different kernel, just NOT include the new bootloader, right?
Aou said:
Curious, can we build a new ROM that includes the @eousphoros kernel, the OF6 system.img, and modem.bin? (without including the new OF6 kernel or the new sboot.img?)
Edit: Upon further thinking, there'd be no reason to use a different kernel, just NOT include the new bootloader, right?
Click to expand...
Click to collapse
Here's what's interesting about that....the eousphoros leaked 5.1.1 kernel is NOT seandroid enforcing, and the new bootloader recognizes that and doesn't let you boot with it.
It also recognizes the 5.0.2 kernel is another android version and it will fail during an odin flash
bajasur said:
Here's what's interesting about that....the eousphoros leaked 5.1.1 kernel is NOT seandroid enforcing, and the new bootloader recognizes that and doesn't let you boot with it.
It also recognizes the 5.0.2 kernel is another android version and it will fail during an odin flash
Click to expand...
Click to collapse
I'm talking about for those who haven't already taken the OTA or haven't Odin'ed the new one yet.
Aou said:
I'm talking about for those who haven't already taken the OTA or haven't Odin'ed the new one yet.
Click to expand...
Click to collapse
I think if you can include the leaked 5.1.1 bootloader you might be golden
bajasur said:
I think if you can include the leaked 5.1.1 bootloader you might be golden
Click to expand...
Click to collapse
Actually, I'm just going to include system.img, boot.img, cache.img and modem.bin.
anyone know wtf cm.bin is? I can't seem to find out any info on what it is or if it should be included.
Edit: well, I upgraded from the unofficial 5.1.1 to OF6, only flashing the four partitions mentioned above. It booted fine, rebuilt the dalvik cache for all my apps, and was doing OK.... except that the fingerprint reader wasn't working and LTE was also not working. Strange. So, I rebooted.... and bootloop.
So, I boot into TWRP (because I still have that!), and wiped cache/dalvik. Stilla bootloop (immediate bootloop). Dang. Wiped cache/dalvik again. Still the same.
So, I flashed the unofficial 5.1.1 via TWRP. This time, it's stuck at the first "galaxy s6 edge" screen.
So, I've re-created my odin package again. This time without cache.img, but I included cm.bin. Let's see if I just shot myself in the foot?
Edit2: Well, it's booting again, for what it's worth... at least to the Android is Starting screen again... it'll be a few minutes...
Aou said:
Actually, I'm just going to include system.img, boot.img, cache.img and modem.bin.
anyone know wtf cm.bin is? I can't seem to find out any info on what it is or if it should be included.
Edit: well, I upgraded from the unofficial 5.1.1 to OF6, only flashing the four partitions mentioned above. It booted fine, rebuilt the dalvik cache for all my apps, and was doing OK.... except that the fingerprint reader wasn't working and LTE was also not working. Strange. So, I rebooted.... and bootloop.
So, I boot into TWRP (because I still have that!), and wiped cache/dalvik. Stilla bootloop (immediate bootloop). Dang. Wiped cache/dalvik again. Still the same.
So, I flashed the unofficial 5.1.1 via TWRP. This time, it's stuck at the first "galaxy s6 edge" screen.
So, I've re-created my odin package again. This time without cache.img, but I included cm.bin. Let's see if I just shot myself in the foot?
Edit2: Well, it's booting again, for what it's worth... at least to the Android is Upgrading screen again... it'll be a few minutes...
Click to expand...
Click to collapse
I could be wrong but I believe the bootloader may be in more than just sboot.bin, @Surge1223 would know better than I.
A quick update: It booted fine, but the fingerprint reader still borked. I was thinking that the LTE wasn't going to work again (stuck on Edge), but I think I just didn't give it enough time last go-around. The LTE cam up after turning mobile data off/on again.
The phone was going very slow, not snappy at all. So I rebooted. And, this time, no bootloop! yay. The fingerprint reader is still not working, though. The speed picked up. I'm also noticing that the brightness sensor isn't working right, perhaps?
Now the next question: Can I still downgrade?
Edit: Well, so far, it's letting me Odin back to OCG stock. The "RP SWREV:" is 1 and "Kernel RP SWREV:" is also 1. Downloading...
(I've had issues using Odin-to-stock after running the unofficial 5.1.1 update, so I might not be able to boot after this...)
Edit2: Well, it worked. I'm back on OCG stock. I can't fully boot (I can only get as far as the TMobile screen), but that's a side-effect of trying to Odin back to OCG without wiping data/cache/dalvik. If I were to do that, I'd be back on OCG stock fully. For the meantime, though, I'm going to jump back on the unofficial 5.1.1 update.
Edit3: Well, for some reason I'm not able to seamlessly boot back into the unofficial 5.1.1. I was able to flash TWRP just fine and flash the 5.1.1, but I get stuck on the "galaxy s6 edge" screen on subsequent boots. Tried formatting System/cache/dalvik. Not willing to format Data yet, though.
Older kernels often don't boot on new bootloaders. This is fairly common on Samsung devices (and also very annoying). This would in fact often halt at the "kernel is not SEAndroid enforcing" line. Rolling back bootloaders to older versions also usually doesn't work.
A rebuild of TWRP or whatever custom kernel you're using may be all there is needed. I wouldn't be scared of bootloader locks just now. On the other hand, I wouldn't flash it yet either
Chainfire said:
Older kernels often don't boot on new bootloaders. This is fairly common on Samsung devices (and also very annoying). This would in fact often halt at the "kernel is not SEAndroid enforcing" line. Rolling back bootloaders to older versions also usually doesn't work.
A rebuild of TWRP or whatever custom kernel you're using may be all there is needed. I wouldn't be scared of bootloader locks just now. On the other hand, I wouldn't flash it yet either
Click to expand...
Click to collapse
Thanks for dropping in and shedding some light on this Chainfire. We all greatly appreciate it.
Hopefully this is just a minor hiccup.
The kernel revision is in the decrypted boot.img signature, and the bootloader rollback protection is in eFuse bank. I've not yet researched any Exynos devices before, but in the past they've used the RPMB (a special, protected hardware partition on the eMMC) to store their 'fuse' bits. However, with recent hardware trends, I wouldn't be surprised if they implemented a true one-time-programmable fuse bank. This is the future of Samsung.
Alright, screw it. I'm just going to flash the full OF6. Chainfire has a very valid point. We faced this same kind of crap on the T-Mobile Galaxy S5. It wasn't really a problem with locked bootloaders, it was a problem of downgrading the kernel/recovery (or trying to downgrade the bootloader itself). He's absolutely right.
Yes, there's some chance that they've added some sort of hash-checking for flashing new binaries (essentially locking the bootloader), but I'm not terribly worried. I've been using the leaked 5.1.1 update for a while now without root, and I've been "mostly" okay with it. I'm really just waiting for Chainfire to graciously invest some of his time in finding a root for the Samsung version of Android 5.1.1. I can wait.
So, here goes taking the plunge, the full OF6 and all... 3...2...1...
Chainfire said:
Older kernels often don't boot on new bootloaders. This is fairly common on Samsung devices (and also very annoying). This would in fact often halt at the "kernel is not SEAndroid enforcing" line. Rolling back bootloaders to older versions also usually doesn't work.
A rebuild of TWRP or whatever custom kernel you're using may be all there is needed. I wouldn't be scared of bootloader locks just now. On the other hand, I wouldn't flash it yet either
Click to expand...
Click to collapse
Yea I remember the downgrading bootloaders and modem issue on many other Samsung devices kit kat on up, ie s3, s5, note 3 excluding the engineered bootloader work around. But we were still ok moving forward, but I think I'll hold off on the update to see what happens now
When I start an app - doesnt matter which, my tab restarts. Not all of the time, but many times. This started a month or so ago. Does anybody know a cure? Thanks
original or custom rom? Tried resetting to defaults?
Originaliteit or custom ROM? Its the original ROM andere have reset my T325 tot default. No succes
have you ever tried to root it or use another rom before (or was it used)? it could be a tripped knox issue, usually that causes the tablet to reboot when the knox check fails...
if not then perhaps somehow the system files got corrupted and you might just want to completely re-flash the whole stock firmware with odin or kies
Knox could be the problem. I have not rooted this tab. But i have knox disabled. Should i turn it on? Its for me such a useless app.
if you have never rooted then knox is unlikely the problem, you can try to re-enable the app though see if it helps..
-if you still get reboots I suggest doing a factory reset , then boot into download mode and re-flash the whole device using the latest firmware
In my testing there is only a few things that can make the tablet reboot and that is
1. a kernel panic similar to linux (maybe a bug in a filesystem driver ..etc)
2. knox
3. overheating when the cpu is at 100-105c it can make the tablet shut down or reboot
i have been thin king and i guess it has to do with the battery. Until the last update my T325 had loadin g troubles. I think that this also has to do with the same problem. Next week i will visit the samsung service store and see what they can do for me. If that doesnt work will i start thinking about rooting and perhaps another rom. Sometimes i wish i never bought this tab. My former (rooted) P1000 never gave troubles!
As good as the P1000 was, I don't miss mine over the Tab PRO, for starters LTE is sweet. Secondly the +1.5 (i.e. 2GBs), of RAM make for a much more pleasant experience. About the only thing the P1000 has or had going for it was some support. Likely do to the fact that it was Samy's first Phablet.
Hello Everyone,
I've been up literally all night (I know, that old line) trying to fix what happened. I bought this phone last year. It was unlocked and rooted. I never updated because it was never giving me issues. But the lagging and battery has finally got to me. So I decided to upgrade to this new rom(http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423).
It looked clean and minimal bloat, just the way I like it. However, I didn't get past updating the Bootloader. As soon as I did in Odin it went into a bootloop. Try as I might I couldn't get into recovery. Luckily I can still get into download mode. So I read up and found that I should flash the original firmware. Unfortunately it failed because I tried to upload an older version. Is there anyway I can flash this rom via odin? Sorry for the noobish questions here but it's past 8am and I've just about given up. If I see recovery is not seandroid enforcing or rev check fail s6 device 3 binary 2 I'm going to lose my mind lol. I did have TWRP installed if that makes a difference. Just can't access it. Any help would be greatly appreciated. Thanks guys
P.S. I know I used buy instead of buy but can't fix it. It was really early in the morning haha
Ok I managed to download the stock MM version for my phone. I still have bootloop issues but I'm in recovery mode at least. However not TWRP though, if I try downloading a custom recovery it says the dreaded "recovery is not seandroid enforcing" also it says Device does not have DRK. Any guesses here?
Well, I've just about given up. I've searched extensively and it appears that the fix is to download a different kernel. However, the G925T has no support yet for any custom MM kernels. I made a backup of my phone via TWRP before this whole mess but the problem is I can't get to it. And to be honest I'm not entirely sure if it's still there. Here are the steps I have taken thus far.
1. Downloaded MM Bootloader: this was the start of my issues. Started bootloop, couldn't get into recovery.
2: Attempted to download original LP firmware: Odin denied it, there was another version I download from zidroid called "downgradeable". Obviously did nothing because I was still running MM bootloader and was effectively the same thing.
3. Downloaded stock MM firmware: Finally was able to boot into recovery but it was useless as it was the stock one. Also wouldn't boot up due to "Device does not have DRK" and boots straight into download mode. Tried to download recovery but none of them worked. Kicked me back to "Recovery not Seandroid enforcing".
So this is where I'm at, I just want to get back to my old device I honestly would rather have a clunky phone than one that doesn't work at all. Is it possible to downgrade back to LP and get back into TWRP and flash my backup? Do I still have root after taking all those steps? Any help would be greatly appreciated because this has officially ruined my weekend?
I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.
try dd the mm firmware
Nickle60 said:
I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.
Click to expand...
Click to collapse
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.
Docmjldds said:
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.
Click to expand...
Click to collapse
Thanks for the reply, I don't have the box for the phone and couldn't boot it up so that was a no go. But luckily for me I decided to give that rom one more go. I flashed bootloader and modem again, then flashed TWRP, and finally installed the rom. And boom! It worked, and it's better and faster than ever. I'm not sure what all that other mess was but I am going to say I have everything I need at the moment and won't be flashing anything anytime soon. I've learned a great deal through this process though. Thanks for everyone's help.
Greetings, Picked up a referb n900T (note3) with factory 5.0 android.
I believe I did the proper procedure for rooting and custom recovery.
I unlocked first.
Used ODIN 3.10 and chainfire cf auto root-hltmo smn900 file supplied to ROOT (ok)
I then used google play to install twrp for tmob note3. (twrp 3.0) (ok)
I boot into twrp.
I installed Resurrection Remix Rom (android 6)
Now on boot up I get "Kernel is not Seandroid enforcing". Not sure what the problem could be.
I did a search and found quite a bit of info but most all of them pertain to android 4.4 etc..
Im not sure if its the root or recovery causing the problem.
It does boot into android fine though... just on initial boot up I get the warning
I downgraded twrp to 2.8 thru img file but same message
any ideas ..thanks
I guess its normal to see this.. I Odin'd back to 5.0 android and did procedure over with 2 different root programs and 2 different roms (resurrection and cm12) . I still get the warning on boot up in the upper left corner... oh well
wogeboy said:
I guess its normal to see this.. I Odin'd back to 5.0 android and did procedure over with 2 different root programs and 2 different roms (resurrection and cm12) . I still get the warning on boot up in the upper left corner... oh well
Click to expand...
Click to collapse
Yes this is normal with almost all ROM's because they are using custom kernels. That's a good thing to get that message actually. It means security on the kernel isn't being enforced. The SE part means Security Enhanced. If that is active then there are major limitations on what the kernel can do.