I've installed the latest Tmobile 4.4.2 Firmware via SamMobile. I came from M17 4.3. Updated via Odin to Tmobile 4.4.2, I then rooted via CF Auto root (Don't care about Knox at this point) successfully and following that flashed Philz recovery with success.
Everything is all good, as I am familiar with other devices and rooting and booting into recovery. At this point I downloaded the latest SlimKat and Lean Kernel to flash onto my system. Reboot into recovery, flash is a success, however when I reboot the system I start to get a bootloop saying Kernel is not seandroid enforcing set warranty bit: Kernel..I've tried to JUST flash SlimKat with the same results. Following this It continues to bootloop so I am forced to Odin from my PC back to Tmobile stock 4.4.2.
Can someone assist me with a solution? TLR, Custom ROMs/Kernels are not allowing me to boot due to Kernel is not seandroid enforcing set warranty bit: Kernel bootloop
My guess would be that slimkat doesn't support 4.4 bootloader yet.
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
Custom kernels will ALWAYS show that on boot.
Dev's turn off the SEANDROID permission crap because not all root apps deal with that permission properly.
Bootloop on the other hand would be a different issue doubtfully related to this.
t3tr1s_ said:
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
Click to expand...
Click to collapse
You have to read the op of the rom you're interested in. If it doesn't say it supports both bootloaders then it's most probably for 4.3 bl only.
Anthem here says it supports both bl.
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
I am not a technical person but how I understand it is that custom recovery/rom flashes doesn't load/replace the bl.
Cm and aosp-based roms were dev'd for 4.3 until a month or two ago when they start supporting both bl and even then not all roms do.
t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
Yes, it sure can.
If you're fully upgraded to the KK package completely, ex: through odin, you have to use a KK rom that has the 4.4.2/Kernel bootloader components.
If you don't fully want to commit to KK completely you can flash a KK rom that has a kernel with the older boot loader. That will allow you to go back to 4.3.
I suspect given time, 4.3 support will be slowly dropped in favor of a full KK implementation on this forum. In the transition period, be careful what you pick and choose to install.
I, like many others, have gone full KK inc. bootloader, etc for full compatibility with everything. When you go full update, you get the updated firmware and bits for the modems, etc.
Thank you very much for all your help, it was the bootloader issue. Just me not reading into things fully, very glad that I asked. I am now running Beanstalk on my Note!
Now that I have all of that cleared up, my next question is the S-PEN. I'm assuming all CM/AOSP ROMs will not support it, thus making me switch to TouchWiz. Is that true? Or are there Apps that I can still use in conjunction with my S-PEN?
As far as TouchWiz is concerned, is Xnote updated to the KK BL and compatible with our Tmobile version? I searched the thread but did not find any answer. If not, what is a suitable replacement to maintain funcionality of the S-PEN while having bloatware removed?
There are apps but it won't give you the full Samsung spen experience like on stock.
Sent from my SM-N900T using Tapatalk
As long as I have a note taking app I think i would be good to go. It's really the only feature I use.
also having this problem
Related
New to this phone and I am running 4.1.2 there is a system update a 4.3 that's already downloaded and ready to install but I wanted to make sure the update didn't install any new locks on my phone before I accept. I plan on rooting soon.
Thanks
Rich
U get knox but there are ways to still root with knox so go ahead update
High Definition Note II
Uuum hold on. If you plan to root your phone there is no point in allowing the OTA which does install KNOX. Root now and save that extra trouble.
tx_dbs_tx said:
Uuum hold on. If you plan to root your phone there is no point in allowing the OTA which does install KNOX. Root now and save that extra trouble.
Click to expand...
Click to collapse
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..
I Would Accept It.
doubledragon5 said:
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..
Click to expand...
Click to collapse
If I was in this position, I would accept the update as doubledragon5 said and move forward with root, etc. I have 4.1.2 right now and want the 4.3 update, but I'm rooted and trying to figure out how to unravel this to get to 4.3 myself.
flashred said:
If I was in this position, I would accept the update as doubledragon5 said and move forward with root, etc. I have 4.1.2 right now and want the 4.3 update, but I'm rooted and trying to figure out how to unravel this to get to 4.3 myself.
Click to expand...
Click to collapse
If your rooted, go back to bone stock MC2 like I have mentioned in a few other threads. accept the 4.3 udate from sprint, re-root using the tookit, then flash away...
doubledragon5 said:
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..
Click to expand...
Click to collapse
doubledragon5 said:
If your rooted, go back to bone stock MC2 like I have mentioned in a few other threads. accept the 4.3 udate from sprint, re-root using the tookit, then flash away...
Click to expand...
Click to collapse
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.
flashred said:
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.
Click to expand...
Click to collapse
I'm wondering the same thing. But if we root then accept the OTA won't that enable the knox counter? So that if we now, "flash away".... won't every flash be counted?
Shouldn't we root, then install the custom roms without the knox? Or do the custom roms also include the knox counter tripping mechanism?
I would like to know how this works also.
Thanks.
I just recently came from 4.1.2 rooted running a deoxided stock rom. I didn't do the OTA update to 4.3. I used the TeamRejects Deoxidexed rooted deknoxed stock rom, the updated MK4 modem, and the WiFi fix. It took about 15-20 minutes to get everything done. I needed to download Odin too for WiFi fix. I didn't run the WiFi fix till I knew there was an issue.
Not much of complaint, but I wish there was a kernel like Perseus for TouchWix based roms. The only one I found was Devil Kernel, but for whatever reason, wasn't stable with TeamReject's ROM. I didn't really care for his custom Kernel ajdustment manager and STweaks didn't work with it at all. Ideally, I prefer a stock rooted deknoxed deoxidized bare bones rom (just phone, contacts, google play) so I have a working phone and can access Google Play so I can install the apps I prefer. The closest I found was Classic Rom but it freezes on initial rom load; Plus, I'm not a fan of the colors and the few things he choose to include.
Stock 4.3 Deodexed, deknoxed, Rooted Rom Available?
lovekeiiy said:
I just recently came from 4.1.2 rooted running a deoxided stock rom. I didn't do the OTA update to 4.3. I used the TeamRejects Deoxidexed rooted deknoxed stock rom, the updated MK4 modem, and the WiFi fix. It took about 15-20 minutes to get everything done. I needed to download Odin too for WiFi fix. I didn't run the WiFi fix till I knew there was an issue.
Not much of complaint, but I wish there was a kernel like Perseus for TouchWix based roms. The only one I found was Devil Kernel, but for whatever reason, wasn't stable with TeamReject's ROM. I didn't really care for his custom Kernel ajdustment manager and STweaks didn't work with it at all. Ideally, I prefer a stock rooted deknoxed deoxidized bare bones rom (just phone, contacts, google play) so I have a working phone and can access Google Play so I can install the apps I prefer. The closest I found was Classic Rom but it freezes on initial rom load; Plus, I'm not a fan of the colors and the few things he choose to include.
Click to expand...
Click to collapse
So, you came exactly where I did except you with a different ROM. I would like to get from my 4.1.2 rooted up to 4.3 rooted stock,deodexed, deknoxed if at all possible.
flashred said:
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.
Click to expand...
Click to collapse
Sorry for not getting back sooner. I have been busy with work, and family things.Use billards return to full stock with counter reset. It installs everything including recovery, boot loader,firemware etc... Then set up your phone, when prompt accept the ota update.. Once done retoot, and flash what ever 4.3 rom you want.. The knox counter will still be there, but if you need a trip back to Sprint, go back to Full MC2 stock, knox counter will no longer be there.. Most 4.3 room do not include the Knox files so no worries there.
flashred said:
So, you came exactly where I did except you with a different ROM. I would like to get from my 4.1.2 rooted up to 4.3 rooted stock,deodexed, deknoxed if at all possible.
Click to expand...
Click to collapse
Sounds like it. The odd part, I have been able to flash Reject's stock deoxidezed deknoxed rom with no problem. I tried to flash Classic 3, but it froze on Classic's initial loading page (the one after the Samsung boot loader). I had issues another rom, but turned out it was for the international model; I wasn't paying attention where I was in the forums.
If you do what I did, you'll need to flash modem update using Odin on the PC. So, you may need to download Odin.
---------- Post added at 05:04 AM ---------- Previous post was at 04:56 AM ----------
Depending on what you like to do, you may find 4.3 MK4 more limiting, espcially on the TouchWiz side. AOSP probably more mod friendly at this point. From what I've been able to find, there is only one custom kernal for 4.3 TouchWiz which is Devil's Kernal. It's solid, but my phone was unstable. Not sure if the phone since I may have taken out something it used when I was trying to debloat the phone. Didn't care for his Kernel Tweak manager. Neither the stock or devil's kernal supports Stweaks. Neither I could figure out how to change the boat loading animation.
I have nothing against AOSP projects. I like them. But as far as I know, none support the Spen, which I like to use with web browsers. Don't use the Samnsung Spen apps. Just wasn't that impressed with them, but I see how they can be useful. Although, SketchPro is really nice with it. I just find TouchWiz is more than sufficient for my needs and stock isn't as quirky.
I currently have my SGS 3 stock rooted with TWRP 2.7 installed. The version of 4.3 I have installed doesn't contain the KNOX bootloader. I'd like to keep it that way should I decide to later move onto a custom rom. From what I've read, if KNOX is installed I won't be able to do that. Is this correct?
I've searched for 4.4 without KNOX, but I haven't been able to find anything. Does anyone here know if it is available? I don't have any major issues with the 4.3 stock rom. I did noticed that my battery drains slooowly if I'm using navigation and it's plugged in. I think that that issue may be due to the iBolt car dock I'm using. I don't think it allows anything over 1 amp for charging.
Should I just go ahead and installed a custom rom that is 4.4?
Thanks
I believe that KNOX doesn't restrict you from installing a 4.4 based ROM, but once you have KNOX you will not be able to downgrade to 4.3 or earlier release. An attempt to do so will permanently brick the phone.
stopeject said:
I believe that KNOX doesn't restrict you from installing a 4.4 based ROM, but once you have KNOX you will not be able to downgrade to 4.3 or earlier release. An attempt to do so will permanently brick the phone.
Click to expand...
Click to collapse
You can install any rom zip on knox as long as you do not downgrade the boot loader via tar files or any other method that flashes every part of the phone.
Thanks stopeject and oeyhdownsouth.
I have a T-mobile Galaxy S4, SGH-M919 running android 4.2.2 and want to upgrade to android 4.3. Okay my question is can I remove knox from the update before updating? I HATE KNOX. I saw where over at s4 mini archive they showed a way that they say it can be removed. Any ideas? Anyone tried this? Any other ways to remove??? Any help would be great. I am sorry if this has been posted or asked before, I have not seen it. http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html
Just use this. http://forum.xda-developers.com/showthread.php?t=2544612 and install a custom rom. Any reason why you want 4.3? You can install 4.4.4 which just came out. Remember to just flash modem only and not the lte modem or you will break sound. If you want to stay completely stock and not have Knox there is no way.
+1 on custom rom. Something like this: http://forum.xda-developers.com/showthread.php?t=2876946
Sorry been a little busy. I'm currently using the MDL bootloader, no knox. I hear there is performance and feature advantage to updating to a newer bootloader. The reason I am looking at 4.3 is that some people have stated that you can remove knox from the bootloader in 4.3. The people stated that they have been able to do this to the S4 mini's 4.3 bootloader. I have looked at the links you two have given me, thank you. What bootloaders are you two using? Also have you seen this as this is what got me thinking. http://forum.xda-developers.com/showthread.php?t=2549357
Bootloader has nothing directly to do with performance. Be careful what you read.
lalec said:
Bootloader has nothing directly to do with performance. Be careful what you read.
Click to expand...
Click to collapse
True. But I would prefer to be 100% knox free. So not just a knox free rom, but the bootloader as well. Staying on android 4.2.2 will do that but at the same time I would like to upgrade to a newer android version. I have seen some nice custom roms with nice performance, but they are 4.3 and newer. And this is why I am looking.
Jamessr79 said:
True. But I would prefer to be 100% knox free. So not just a knox free rom, but the bootloader as well. Staying on android 4.2.2 will do that but at the same time I would like to upgrade to a newer android version. I have seen some nice custom roms with nice performance, but they are 4.3 and newer. And this is why I am looking.
Click to expand...
Click to collapse
You can keep MDL boot loader, and flash 4.3, 4.4.2, or 4.4.4 ROMs no problem. I've got an M919 with MDL boot loader and am currently running Dirty Unicorns (4.4.4-based) ROM.
I've got all the benefit of the latest version of Android (plus many customizations!) and no Knox.
The only think that you can't do on the MDL boot loader is run a newer LTE modem... the LTE modem (non-hlos.bin) is tied to the boot loader. However the GSM modem (modem.bin) is not, so you can update that part of it. It's something to keep in mind, but the LTE modem in MDL is fine and works for me quite well even in marginal signal areas.
Marc
Frankenscript said:
You can keep MDL boot loader, and flash 4.3, 4.4.2, or 4.4.4 ROMs no problem. I've got an M919 with MDL boot loader and am currently running Dirty Unicorns (4.4.4-based) ROM.
I've got all the benefit of the latest version of Android (plus many customizations!) and no Knox.
The only think that you can't do on the MDL boot loader is run a newer LTE modem... the LTE modem (non-hlos.bin) is tied to the boot loader. However the GSM modem (modem.bin) is not, so you can update that part of it. It's something to keep in mind, but the LTE modem in MDL is fine and works for me quite well even in marginal signal areas.
Marc
Click to expand...
Click to collapse
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.
HKSpeed said:
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.
Click to expand...
Click to collapse
A stock firmware? If it contains the bootloader, it will automatically replace your existing one.
tetakpatalked from Nexus 7 flo
HKSpeed said:
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.
Click to expand...
Click to collapse
Yes, it's based off AOSP. See the Samsung home page for Dirty Unicorns here. Also the G+ Community for it.
If you are looking for a TW ROM, I had a great experience with GoldenEye v. 38 over the summer. Very stable, and everything worked, even on my ATT version S4 I337 using SafeStrap. I got sick of SafeStrap limitations and eventually bought a M919 so I could do anything I wanted ROM wise... but GoldenEye was very nice. Debloated, very stable, felt good.
Being very satisfied with my current version of Dirty Unicorns, I'll probably not change any time soon, thought I've been tempted to install SlimKat and build up the features I want. I use SlimKat on a tablet, and like it's very light footprint. Quite zippy.
Marc
tetakpatak said:
A stock firmware? If it contains the bootloader, it will automatically replace your existing one.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Just something to remember: Bootloaders (all the bad KNOX junk) CANNOT be flashed via custom recovery. So if you are flashing a stock ROM (firmware?) via custom recovery you will NOT get KNOX. If, however you decide to flash a ROM/firmware via Odin chances are very good that you will be getting a new bootloader and all the KNOX garbage it brings.
TLR
If you flash via recovery you won't get KNOX, if you flash via Odin you probably will.
Modems must also be flashed in Odin, but as far as KNOX goes, it's the bootloader you don't want.
Okay, does this mean I have knox or do not have knox.
Jamessr79 said:
Okay, does this mean I have knox or do not have knox.
Click to expand...
Click to collapse
It seems to me like you're still knox-free
tetakpatalked from Nexus 7 flo
Jamessr79 said:
Okay, does this mean I have knox or do not have knox.
Click to expand...
Click to collapse
Yup.
No Knox there.
You would see a Knox warranty line in that bootloader screen if you had it.
Cool, so it worked.
question
lordcheeto03 said:
Just something to remember: Bootloaders (all the bad KNOX junk) CANNOT be flashed via custom recovery. So if you are flashing a stock ROM (firmware?) via custom recovery you will NOT get KNOX. If, however you decide to flash a ROM/firmware via Odin chances are very good that you will be getting a new bootloader and all the KNOX garbage it brings.
TLR
If you flash via recovery you won't get KNOX, if you flash via Odin you probably will.
Modems must also be flashed in Odin, but as far as KNOX goes, it's the bootloader you don't want.
Click to expand...
Click to collapse
So what you are saying is if I flash a stock zip via custom recover no KNOX? Has this been tested? I removed knox on 4.3 but got crazy and tried 4.4.4 now random restarts.
Jamessr79 said:
So what you are saying is if I flash a stock zip via custom recover no KNOX? Has this been tested? I removed knox on 4.3 but got crazy and tried 4.4.4 now random restarts.
Click to expand...
Click to collapse
Yes, what I'm saying has been tested and confirmed 100%. There is no way to flash a KNOX-implemented bootloader (or ANY bootloader for that matter) via custom recovery. You seem to have the misconception that the KNOX apps within the ROM is what all the KNOX talk is about. If anything, it's only a small part. Now, I'm not absolutely certain of how this works as I've only followed the technical posts in the Development only forum regarding this for the first 10 or so pages, so if I say something that isn't exactly accurate, please forgive me. The basic gist is that when you hear about KNOX and why it's not necessarily wanted in the updated firmwares isn't because of a few user-removable apps; it's something at the hardware level that, when during the boot up tests and checks, it notices that there is a custom kernel or custom recovery in place instead of the expected stock kernel/recovery, it blows an e-fuse and forever after tells anyone who looks at the download mode that the device has been modified at one point or another.
About the random restarts, without knowing whether you updated from 4.3 to 4.4.4 via custom recovery or other official means, all I can say is to try a factory reset and/or use Odin to re-flash the firmware and do a factory reset after that.
lordcheeto03 said:
Yes, what I'm saying has been tested and confirmed 100%. There is no way to flash a KNOX-implemented bootloader (or ANY bootloader for that matter) via custom recovery. You seem to have the misconception that the KNOX apps within the ROM is what all the KNOX talk is about. If anything, it's only a small part. Now, I'm not absolutely certain of how this works as I've only followed the technical posts in the Development only forum regarding this for the first 10 or so pages, so if I say something that isn't exactly accurate, please forgive me. The basic gist is that when you hear about KNOX and why it's not necessarily wanted in the updated firmwares isn't because of a few user-removable apps; it's something at the hardware level that, when during the boot up tests and checks, it notices that there is a custom kernel or custom recovery in place instead of the expected stock kernel/recovery, it blows an e-fuse and forever after tells anyone who looks at the download mode that the device has been modified at one point or another.
About the random restarts, without knowing whether you updated from 4.3 to 4.4.4 via custom recovery or other official means, all I can say is to try a factory reset and/or use Odin to re-flash the firmware and do a factory reset after that.
Click to expand...
Click to collapse
Okay, I misunderstood on what you said could be flashed, but will have to take a look. Could you please point me in the right direction for that forum. As far as the misconception goes I do know that KNOX is in the bootloader. I also know that KNOX app/software is found in the rom as well. As for KNOX being in the rom Titanium Backup helps to remove most of it. Or I can just installing a custom rom that has it removed. The main reason that I had started this forum was to remove the KNOX from the bootloader. The reason I pointed to http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html in the first post is because they stated it could be done. After doing some other looking around and talking to others I tried it. Seems like it works on android 4.3, but 4.4.2 and 4.4.4. when I try to do the same it is not happy. I updated via Odin. The first time was 4.2 to 4.3 after modding the bootloader and not the rom. It works fine no KNOX lines in download mode. Still KNOX in the rom but uninstalled using Titanium Backup. Currently I am running android 4.3 on my Galaxy S4 no issues and as far as I can tell no KNOX.
Jamessr79 said:
Okay, I misunderstood on what you said could be flashed, but will have to take a look. Could you please point me in the right direction for that forum. As far as the misconception goes I do know that KNOX is in the bootloader. I also know that KNOX app/software is found in the rom as well. As for KNOX being in the rom Titanium Backup helps to remove most of it. Or I can just installing a custom rom that has it removed. The main reason that I had started this forum was to remove the KNOX from the bootloader. The reason I pointed to http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html in the first post is because they stated it could be done. After doing some other looking around and talking to others I tried it. Seems like it works on android 4.3, but 4.4.2 and 4.4.4. when I try to do the same it is not happy. I updated via Odin. The first time was 4.2 to 4.3 after modding the bootloader and not the rom. It works fine no KNOX lines in download mode. Still KNOX in the rom but uninstalled using Titanium Backup. Currently I am running android 4.3 on my Galaxy S4 no issues and as far as I can tell no KNOX.
Click to expand...
Click to collapse
Wait.... your on 4.3 or 4.2 and have been able to unlock the bootloader on them?? Everything you said above is exactly what I have seen and heard also with the addition that the signatures not matching verification checks are what is blowing the q fuse or what Knox and the Samsung / att security freak out about right?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I was on 4.2 and downloaded the stock 4.3 to my Linux pc. I then did what was stated on the s4 mini forums and was able to remove Knox from the bootloader, then the rom via titanium backup. Note as far as I know you can't remove Knox once it is already there.
Hi,
If I Flash the stock bootloader to the latest official ClockworkMod-Recovery.
Can I get back to the stock bootloader with official state?
Could anyone help since I did the same situation to another device but I totally new in using N5100.
Thank you.
You mean 4.4.2 bootloader?
Yes, I'm on 4.4.2 bootloader (Stock)
Should be official, but you'll get knox 0x1
User_99 said:
Should be official, but you'll get knox 0x1
Click to expand...
Click to collapse
Thanks for your reply..
Could you please explain How to get back official? if you have any reference ?
I'm trying to make sure if I rooted the stock 4.4.2, I can get back without any problems.
If you root your device and use 4.4.2 Rom you will be knoxed 0x1 and that can not be changed back. Also not via flashing original Stock Rom via Odin. How to do that is written in several threads here, please use forum search.
Btw, for going back only because ypu have rooted, you can easily use the unroot feature in SuperSU app. No need to reflash a Stock Rom...
User_99 said:
If you root your device and use 4.4.2 Rom you will be knoxed 0x1 and that can not be changed back. Also not via flashing original Stock Rom via Odin. How to do that is written in several threads here, please use forum search.
Btw, for going back only because ypu have rooted, you can easily use the unroot feature in SuperSU app. No need to reflash a Stock Rom...
Click to expand...
Click to collapse
Thank you for your reply.
As I'm totally new to this forum and N5100, from your point of view what is the best stable Custom ROM available with unique features?
TIA
That's a good question. Depends what you want and need. In my case a use an 4.2.2 Custom Samsung Rom with root for deleting not needed apps and be very happy. All works without any hick up. OTG, phone feature, screen mirroring, battery life.
CM based Roms are nice in point of customizing, but due the fact, that Samsungs Source Code is not fully available some features like Phone calling do not fully work, and so on. BUT it depends what YOU need. If calling is not needed, also some other features such Roms are really great.
I don't understand about unique features... As I did the custom ROM thing and found stock features more important than having a modded custom ROM.
I have 4.2.2 that is tweaked by me, without a custom kernel that is stable, fast, and gets 9 hours doing apps, and 7 hours doing 720p vids.
As for breaking status to custom, I used saferoot to root with. So custom is not set, plus you are not flashing, thus being safer.
I check and clear my flash counter with triangle away if needed.
To revert from custom ROM without a custom recovery, you can go into recovery mode when powered off, by holding the vol up button down when powering on.
From there you can clear cache, and do a factory reset. Once at the home screen enable USB debugging and shutdown, to go into factory upload, by powering on while holding the vol down button.
Having a custom recovery will simplify by formatting partition, and flashing new ROM.
Thanks for your clarification.
After using this unique device for a while and after upgrading to official Kit Kat version I really found that the device stability and using the S pen is the most important feature especially as I'm using it for managing my daily work.
Maybe if Samsung didn't upgrade to lollipop, (maybe) I may root to custom ROM but at that time the S pen still a must to me.
Sent from my GT-N5100 using XDA Free mobile app
I am currently running an OG5 based ROM, with the OB7 bootloader.
I had been keeping the OB7 bootloader, instead of upgrading to OE1/OF5, because it allowed me to go back to Kit Kat NK2, after evaluating the initial lollipop release.
Now that OG5 is out, I am pretty happy and can't imagine going back to KK.
So I've been trying to get Android Pay to allow me store a credit card and no fix has worked. I am thinking that it might be because my rom and bootloader don't match up (OB7 & OG5)?
I was going to give it a shot, but now wondering if there is any reason to keep OB7 bootloader, other than having the option to downgrade?
If I decide to go all OG5 (ROM and bootloader) is there any easier way than starting with the OTA?
Thanks,
Also curious about this. If you get it working please share what steps you took. To be honest, all I'd like to do in Android Pay would be to set up the loyalty cards.... seems as though you can input any until you've verified at least 1 credit or debit card
Also... any chance its possible to set up a card on Android Pay from another unrooted device then use as normal from your rooted phone once a card is added to your account? I don't have a secondary device to try
Sent from my SM-N910P using XDA Free mobile app
ch3ck3rs said:
Also curious about this. If you get it working please share what steps you took. To be honest, all I'd like to do in Android Pay would be to set up the loyalty cards.... seems as though you can input any until you've verified at least 1 credit or debit card
Click to expand...
Click to collapse
Do you also have the OB7/OG5 combo?
I wonder if anyone with OG5/OG5 has had any luck. from what I've read plenty of people with unlocked bootloaders have been successful.
FYI there is an app called Keyring that does a decent job with loyalty cards.
Yep. I have the same combo. Running Saintz OBAR
A lot of variables are at play here. Most root users of any device are hitting roadblocks when it comes to getting AP to load their cards. In my instance I am on OG5/OG5 running HybridX 3. I've explored nearly all of the 'fixes' out there short of flashing the stock build.prop. Some reports are saying it is checking against known good OS (ie: CM12 stable vs. CM12 nightly). Others are saying it is checking directory level instances of root (ex: system/bin/su or system/xbin/su). Still more are just unlucky and are hitting the wall for no explained reason (there is a reason I'm sure, the info provided isn't helping). What it is going to boil down to is some smart cookie is going to unlock the secret, and we're going to say 'you've got to be kidding, that was too easy'.
With Android Pay, it will block root users and I haven't found a way that gets around it on the Note 4, even with Root Cloak and No Device Check to mask root and custom ROM's to get it to work.
From what I saw, Android Pay does have SafetyNet built in to it to check if your device and your firmware match up. I ran into the same issue with running the OB7 bootloader and CM12.1 ROM which doesn't work. I'm assuming you are having a similar as me issue with using the 0B7 bootloader and a 0G5 ROM. Unfortunately, you will probably have to unroot and go back to stock to get it to work since none of the workarounds I've tried hasn't worked.
Sent from my SM-N910P using Tapatalk
ThatGuy94 said:
FYI there is an app called Keyring that does a decent job with loyalty cards.
Click to expand...
Click to collapse
I use beep and go, works with older infrared barcode scanners
I'm currently on 5.01 and OB7. I was able to get Android Pay to let me add a card by going into the settings menu in SuperSU and disabling Superuser. I entered the card info and Android Pay was set up. I used it at Toys R Us today and works perfect. I re-enabled Superuser in SuperSU and was able to still use Android Pay.
I have the same question as OP. What are the benefits of staying on OB7? I am getting ready to update to 5.1.1 using this link
http://forum.xda-developers.com/not...g-to-5-1-1-t3199881/post62794303#post62794303
Do I need to stay on OB7 to install custom roms? Can I install custom roms with OG5? I would like to eventually install a stockish rom that has Knox and Itson removed, along with all the bloatware.
Thanks!
Quick answer is OB7 allows you to go back to KK OG5 will not
dh350nwo said:
Quick answer is OB7 allows you to go back to KK OG5 will not
Click to expand...
Click to collapse
Thanks! No intention on going back to KK. So if I update to OG5, I can still flash a custom rom?
duongdn said:
Thanks! No intention on going back to KK. So if I update to OG5, I can still flash a custom rom?
Click to expand...
Click to collapse
Quick answer is yes but you'd be limited to OG5 ROMs if you flashed the stock OG5 tar. You may also get Noterized, sacs and CM12 custom ROMs. Your backups would be void.
If you instead chose to keep the OB7 bootloader, you could flash the OB7 to OG5 tar ball by tx_dbs_tx and still be be able to Odin the older tars to use the ROMs or backups you have now.
http://forum.xda-developers.com/showpost.php?p=62274955&postcount=1
There are some S6 ROM ports (not quite stable as stock) but it looks like there's a possible banding of developers to get the Note 5 ported to OG5. What's stable at the moment are the stock Note 4 ROMs with a few mods. tx_dbs_tx Hybrid X or stock OG5 ROMs have been getting props by users; use that if you're not into running stock rooted Odex.
I'm actually running stock Odex from the tar ball flash linked above, just Odin'd TWRP and rooted with Beastmode kernel and SuperSU zip in recovery, debloated and modified it.
Edit: The OG5 custom ROMs are pre-rooted. You'd only need to Odin TWRP and follow OP install instructions to install. I'd recommend the Beastmode kernel though. Some say adjust the volume level in Synapse but I do it with Viper4Android and leave the Dolby Atmos volume leveler enabled. It pumps the bass without volume too high or too low.
Sent from my SM-N910P using Tapatalk
duongdn said:
I'm currently on 5.01 and OB7. I was able to get Android Pay to let me add a card by going into the settings menu in SuperSU and disabling Superuser. I entered the card info and Android Pay was set up. I used it at Toys R Us today and works perfect. I re-enabled Superuser in SuperSU and was able to still use Android Pay.
I have the same question as OP. What are the benefits of staying on OB7? I am getting ready to update to 5.1.1 using this link
http://forum.xda-developers.com/not...g-to-5-1-1-t3199881/post62794303#post62794303
Do I need to stay on OB7 to install custom roms? Can I install custom roms with OG5? I would like to eventually install a stockish rom that has Knox and Itson removed, along with all the bloatware.
Thanks!
Click to expand...
Click to collapse
Sigh. I had great hopes this would help me but no luck i disabled superuser and still android pay says cannot vetify my device... any other thoughts? I am on 5.01 sttaight up rooted running alliance rom
cheryl
cherylbaker said:
Sigh. I had great hopes this would help me but no luck i disabled superuser and still android pay says cannot vetify my device... any other thoughts? I am on 5.01 sttaight up rooted running alliance rom
cheryl
Click to expand...
Click to collapse
Safetynet has to verify the Rom is original to the phone. If you're not using stock Android Pay will throw that message
Sent from my SM-N910P using Tapatalk
SafetyNet is just 1 part of the puzzle. If it was the only thing then the Xposed module 'No Device Check' would be enough to bypass. There are multiple checks taking place.
OG5 and non OG5 roms
samep said:
Quick answer is yes but you'd be limited to OG5 ROMs if you flashed the stock OG5 tar. You may also get Noterized, sacs and CM12 custom ROMs. Your backups would be void.
If you instead chose to keep the OB7 bootloader, you could flash the OB7 to OG5 tar ball by tx_dbs_tx and still be be able to Odin the older tars to use the ROMs or backups you have now.
http://forum.xda-developers.com/showpost.php?p=62274955&postcount=1
There are some S6 ROM ports (not quite stable as stock) but it looks like there's a possible banding of developers to get the Note 5 ported to OG5. What's stable at the moment are the stock Note 4 ROMs with a few mods. tx_dbs_tx Hybrid X or stock OG5 ROMs have been getting props by users; use that if you're not into running stock rooted Odex.
I'm actually running stock Odex from the tar ball flash linked above, just Odin'd TWRP and rooted with Beastmode kernel and SuperSU zip in recovery, debloated and modified it.
Edit: The OG5 custom ROMs are pre-rooted. You'd only need to Odin TWRP and follow OP install instructions to install. I'd recommend the Beastmode kernel though. Some say adjust the volume level in Synapse but I do it with Viper4Android and leave the Dolby Atmos volume leveler enabled. It pumps the bass without volume too high or too low.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You can run any rom under OG5 if you took full OG5 update, Ive been running all sorts of ROMs that are not OG5 and they work just fine, flash everything as normal just flash beast mode kernal or emotion kernel or AEL kernel, after flashing ROM...any exploited OG5 kernel will work.
Iceburn1 said:
You can run any rom under OG5 if you took full OG5 update, Ive been running all sorts of ROMs that are not OG5 and they work just fine, flash everything as normal just flash beast mode kernal or emotion kernel or AEL kernel, after flashing ROM...any exploited OG5 kernel will work.
Click to expand...
Click to collapse
I recall reading that but couldn't recall the steps. Makes sense. Thanks.
Edit: I wouldn't recommend Odin any tar. I believe you still cannot go backwards regarding Odin. The OG5 bootloader won't allow downgrade flash.
Sent from my SM-N910P using Tapatalk
nacron said:
Safetynet has to verify the Rom is original to the phone. If you're not using stock Android Pay will throw that message
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So your saying unless you are running stock rom and no root there is no way to get android pay to work
cheryl
In short yes. Long version is that the unit needs to be on a stock ROM with root hidden. Many users are able to get AP to work when they hide root on setup using Root Cloak and/or turning off SU. Some others have not had success doing this also. AP is checking multiple things along with root, kernel changes, Xposed installation, and other things. Safety net is only one check. Those of us that are rooted using custom ROMs with other changes are going to have to wait until a smart Dev can crack the mystery.
dh350nwo said:
In short yes. Long version is that the unit needs to be on a stock ROM with root hidden. Many users are able to get AP to work when they hide root on setup using Root Cloak and/or turning off SU. Some others have not had success doing this also. AP is checking multiple things along with root, kernel changes, Xposed installation, and other things. Safety net is only one check. Those of us that are rooted using custom ROMs with other changes are going to have to wait until a smart Dev can crack the mystery.
Click to expand...
Click to collapse
What if you went stock set it up avd than flashed back custom rom... does it do the same ssfety checks even after it is setup?
cheryl