i recently rooted through the exynos bug and would like to keep root but avoid having the device status as modified or having the counter increase,
My main concern is avoiding problems if i need to use the warranty
I'd like to know if i can do any of the following while maintaining root , keeping the device unmodified and no counter increase:
1-update via Kies normally (to a version with the exynos bug fixed)
2-update via odin to a stock rom (with the exynos bug fixed)
3-update via mobile odin to a stock rom (i guess with mobile odin i can't have the exynos bug fixed via rom update)
thanks.
Why? If you are rooted you won't have warranty even if all the counters are zero
if the counters are zero (at least with the exynos bug) i can remove root easily, if necessary.
And if they're not, you can reset them at any time. I don't see the point for the hassle
temp9300 said:
i recently rooted through the exynos bug and would like to keep root but avoid having the device status as modified or having the counter increase,
My main concern is avoiding problems if i need to use the warranty
I'd like to know if i can do any of the following while maintaining root , keeping the device unmodified and no counter increase:
1-update via Kies normally (to a version with the exynos bug fixed)
2-update via odin to a stock rom (with the exynos bug fixed)
3-update via mobile odin to a stock rom (i guess with mobile odin i can't have the exynos bug fixed via rom update)
thanks.
Click to expand...
Click to collapse
I am not aware of any way to keep the status "unmodified" and keep root, as root will set it too modified anyway.
Glebun said:
Why? If you are rooted you won't have warranty even if all the counters are zero
Click to expand...
Click to collapse
depends where you are, in Europe you still have warranty with root.
chrismast said:
depends where you are, in Europe you still have warranty with root.
Click to expand...
Click to collapse
Got a source on that? The status will be "modified", pretty sure that voids the warranty
Use mobile odin and make a wipe data and cache
It will facotry reset your phone
But it changes your device status back to normal and keeps the root
Sent from my GT-I9300 using xda premium
if it's modified shouldn't there be something showing that when booting? like the yellow triangle? i have nothing like that since i got root using the exynos abuse bug.
It shows it in the download mode
Glebun said:
Got a source on that? The status will be "modified", pretty sure that voids the warranty
Click to expand...
Click to collapse
sure, Directive 1999/44/CE by the European Union or an easier to read summary
That's interesting but I think you'll have to be prepared to pay lawyer expenses and it might not be worth it.
My objective was to have root but be able to quickly and easy revert back to normal, guess it's not that easy, I'll always need some steps and a computer.
just found out that even if you unroot using the exynos abuse tool you might still keep your device status as modified.
can't use the standard update to 4.1.2, guess i'll have to try a full wipe next, maybe that will rever it back to normal.
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
The sure-fire way of rooting is by using this method. That being said, this will trip your KNOX Counter.
Now, onto Voiding Warranty vs. Tripping KNOX Counter.
Official Samsung Warranty. This document is obviously written in a legalese manner. I am not a lawyer, but have read through the warranty very carefully and feel like I have a grasp on what it covers/doesn't cover.
In my opinion, the most critical part of the warranty (as it applies to our conversation) is the following:
This Limited Warranty does not cover: ...
(g) defects or damage resulting from improper testing, operation, maintenance, installation, service, or adjustment not furnished or approved by SAMSUNG, including but not limited to installation of unauthorized software and unauthorized root access, both of which shall void this limited warranty
Click to expand...
Click to collapse
This clearly states that rooting the phone will void your warranty. Please note that this is regardless of whether KNOX is tripped. Using Towelroot (on previous versions) to gain root access technically would void your warranty just as much as using other methods. The issue is whether Samsung knows about it. That's where KNOX comes in.
KNOX is primarily Samsungs way of knowing if you've modified the software on the phone (root access or some other tampering). At startup, KNOX checks for custom low-level operating system components (bootloader, recovery, kernal, etc.). If any of these are custom, it'll trip KNOX. TowelRoot had exploited a way to obtain root access without modifying any of those items, but as you mentioned, it no longer works in 4.4.4. As far as I'm aware, all other rooting methods include using ODIN to briefly modify one of the low-level operating system components, which invariably trips KNOX.
Now, back to the main point of your questions: will voiding the warranty (by obtaining root access) screw me over? The answer is: probably not. Samsung has been known to not really care about KNOX being tripped when servicing phones. This especially is true in cases where you are claiming someone not software related. From a common-sense perspective, having root access would in no way affect the performance of the power button, so if you're claiming issues with the power button, having a tripped KNOX shouldn't affect your claim status. Although, legally, they have covered this by saying the warranty is completely voided by having root access (not just the software part of the warranty).
I would recommend, however, that before sending any phone in, that you use ODIN to revert back to the stock android. KNOX will still be tripped, but it won't technically have root access anymore.
I hope this answers your questions.
-Topher
topherk said:
The sure-fire way of rooting is by using this method. That being said, this will trip your KNOX Counter.
Now, onto Voiding Warranty vs. Tripping KNOX Counter.
Official Samsung Warranty. This document is obviously written in a legalese manner. I am not a lawyer, but have read through the warranty very carefully and feel like I have a grasp on what it covers/doesn't cover.
In my opinion, the most critical part of the warranty (as it applies to our conversation) is the following:
This clearly states that rooting the phone will void your warranty. Please note that this is regardless of whether KNOX is tripped. Using Towelroot (on previous versions) to gain root access technically would void your warranty just as much as using other methods. The issue is whether Samsung knows about it. That's where KNOX comes in.
KNOX is primarily Samsungs way of knowing if you've modified the software on the phone (root access or some other tampering). At startup, KNOX checks for custom low-level operating system components (bootloader, recovery, kernal, etc.). If any of these are custom, it'll trip KNOX. TowelRoot had exploited a way to obtain root access without modifying any of those items, but as you mentioned, it no longer works in 4.4.4. As far as I'm aware, all other rooting methods include using ODIN to briefly modify one of the low-level operating system components, which invariably trips KNOX.
Now, back to the main point of your questions: will voiding the warranty (by obtaining root access) screw me over? The answer is: probably not. Samsung has been known to not really care about KNOX being tripped when servicing phones. This especially is true in cases where you are claiming someone not software related. From a common-sense perspective, having root access would in no way affect the performance of the power button, so if you're claiming issues with the power button, having a tripped KNOX shouldn't affect your claim status. Although, legally, they have covered this by saying the warranty is completely voided by having root access (not just the software part of the warranty).
I would recommend, however, that before sending any phone in, that you use ODIN to revert back to the stock android. KNOX will still be tripped, but it won't technically have root access anymore.
I hope this answers your questions.
-Topher
Click to expand...
Click to collapse
Thank you! It does, so essentially rooting period will void the warranty (as seen in the legal jargon) whether you trip the counter or not, and you can always restore it to stock if you need to turn it back in. I was wondering the same thing, we took my gf's S4 in yesterday, and all they did was run a Sprint diagnostic and then replace the hardware, not sure if they even checked to see what she was running (although it is stock).
Any other threads you recommend, I'm still fairly new to it, been reading up on it since I had the Transformer that wouldn't update to Froyo ha, but back then there was too much coding involved, I didn't want a bricked phone because I forgot a "/" in the code somewhere. Almost everyone I know uses Cyanogenmod, also what's the deal with Titanium Backup and Safestrap?
TheNewGuy14 said:
Any other threads you recommend, I'm still fairly new to it, been reading up on it since I had the Transformer that wouldn't update to Froyo ha, but back then there was too much coding involved, I didn't want a bricked phone because I forgot a "/" in the code somewhere. Almost everyone I know uses Cyanogenmod, also what's the deal with Titanium Backup and Safestrap?
Click to expand...
Click to collapse
Thankfully, it's not nearly as easy to brick a Note 3 (at least compared to the S3... man it was tough helping people with that phone, so many bricks!).
It's considered bad form to link specific ROMs in a Q&A thread, since each ROM is catered to a different demographic (and some people might get in a huff if you neglect their favorite ROM). What I will do, however, is let you know the steps I've taken whenever I root and install a new ROM.
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Topherk,
Thanks for the reply, and sorry about the bad Juju for mentioning a specific ROM. In other news, I am probably going to re-read your article step by step, and it really puts things in perspective. I have that same build, and I also have Sprint like the video, which I didn't know that the carrier made such a big difference. I'm glad I asked before I started! I will keep you updated on what I decide to do, appreciate the help!
TheNewGuy14
:good:
*new question*
I don't remember where I read this, and I found the option on my phone. If I uninstall KNOX will that eliminate the counter, and other minor issues with KNOX?
TheNewGuy14 said:
I don't remember where I read this, and I found the option on my phone. If I uninstall KNOX will that eliminate the counter, and other minor issues with KNOX?
Click to expand...
Click to collapse
No worries about the mention of CyanogenMod (I myself am running a ROM based off of it)... I was talking from the perspective of someone giving advice. If I give you advice towards a specific ROM or two (or even a list of ROMs), it could be considered a slight towards the excluded ones.
As far as I'm aware, there are two aspects of KNOX: The low-level trigger and the system app. The low-level trigger works like I described in my previous post. I honestly don't know how the system app works, but I believe it only affects Enterprise users whose corporations require secure phones (and have their own systems in place which interact with KNOX). I beleive it was Samsung's way of trying to secure some of Blackberry's business-class users. I may be way off on this, but that's what I understand about KNOX.
Cheers!
-Topher
I think you're right they want to maintain they are the most secure phone.
Check out their official statement for Towelroot, although I can't post the link because I'm still a n00b quick Google search will bring it up though.
Sent from my SM-N900P using XDA Free mobile app
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
Yes, if you root 4.4.4 NH7 at this time with the available rooting formats, you will trip Samsung's KNOX Counter, and void the device's warranty with Samsung. So, are you going to send the device directly back to Samsung ? No, you are going to take it to a sprint service center, or ship it in to sprint. Sprint handles the warranty ? KNOX is a program that creates secure encrypted containerization of DATA so it can be sent to another location. Check this out http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
Hey OP, I have rooted my N3 using CF-Auto Root on NH7 without any problems.
It should be a walk in the park, and yes you will trip knox, but It's all good.
Now proceed with your rooting
Hi guys,
Sorry if this has already been answered several times but i have read many threads and just feel some information is dated and cannot work out if what im trying to do is possible.
I would like to root my samsung galaxy s6 edge, however i have been reading that the fingerprint scanner stops working along with call audio?
I was wondering if these are still issues? and if not then which is the best way to root without tripping knox counter?
Kind regards
usmxn
It's ok! I'll help you out!
From personal experience, Tripping KNOX gets rid of Samsung Pay functionality, however I do not know about Android Pay or Google Wallet. Tripping KNOX, though, gives you the ability to have fingerprint functionality.
(This isn't from personal experience, just from what many others have said) By not tripping KNOX, you lose fingerprint functionality(seems to be confirmed by lots of people for this), but Samsung Pay should (not 100% sure) work.
As for the call audio issues, this usually applies to the T-Mobile (SM-G925T or SM-G920T) or Canadian (SM-G925W8 or SM-G920W8) Varients of the S6 and S6 Edge. However, if you do have either of the models listed, there is a fix that you can flash.
TL;DR, Tripping KNOX = Loss of Samsung Pay + Working Fingerprint Scanner.
However NOT Tripping KNOX = Possibly working Samsung Pay + Broken Fingerprint Scanner.
I would recommend (if you don't care of Samsung Pay) to root by flashing either Unikernel via ODIN or flashing TWRP through ODIN and then flashing custom ROMS or Kernels through TWRP. (Both Methods Trips KNOX)
I do not know of a way to root without tripping KNOX, sorry! Anyways, for me, losing Fingerprint Scanner functionality is a deal breaker.
I would also recommend NOT Rooting! This is only if you don't want to lose any functionality of your device.
FQuimson23 said:
It's ok! I'll help you out!
From personal experience, Tripping KNOX gets rid of Samsung Pay functionality, however I do not know about Android Pay or Google Wallet. Tripping KNOX, though, gives you the ability to have fingerprint functionality.
(This isn't from personal experience, just from what many others have said) By not tripping KNOX, you lose fingerprint functionality(seems to be confirmed by lots of people for this), but Samsung Pay should (not 100% sure) work.
As for the call audio issues, this usually applies to the T-Mobile (SM-G925T or SM-G920T) or Canadian (SM-G925W8 or SM-G920W8) Varients of the S6 and S6 Edge. However, if you do have either of the models listed, there is a fix that you can flash.
TL;DR, Tripping KNOX = Loss of Samsung Pay + Working Fingerprint Scanner.
However NOT Tripping KNOX = Possibly working Samsung Pay + Broken Fingerprint Scanner.
I would recommend (if you don't care of Samsung Pay) to root by flashing either Unikernel via ODIN or flashing TWRP through ODIN and then flashing custom ROMS or Kernels through TWRP. (Both Methods Trips KNOX)
I do not know of a way to root without tripping KNOX, sorry! Anyways, for me, losing Fingerprint Scanner functionality is a deal breaker.
I would also recommend NOT Rooting! This is only if you don't want to lose any functionality of your device.
Click to expand...
Click to collapse
Thanks for that. I will probably have to trip knox as i want fingerprint functionality.
Have you got a link handy to a guide with download links and a how to?
usmxn said:
Thanks for that. I will probably have to trip knox as i want fingerprint functionality.
Have you got a link handy to a guide with download links and a how to?
Click to expand...
Click to collapse
Yeah, no problem.
Here's UniKernel: http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395
Download the ODIN Flashable version
ODIN: http://odindownload.com/SamsungOdin/#.VpLZkRUrLIU
Tutorial is quite easy, (This is to only root STOCK Firmware):
1. Download the files you need (UniKernel, ODIN)
2. Turn on Developer Mode (Go to Settings > About Phone, and Spam Tap the Build Number Until it says Developer Mode Turned On) And make sure to enable OEM Unlocking
3. Turn Off the Device and Boot in to Download Mode by Holding Down the Vol. Down, Home Button, and Power Button simultaneously until a cyan screen appears. Then press Vol. Up and you should see ODIN Mode in RED
4. Plug in your device to your pc and launch up ODIN.
5. Go ahead and check the box for AP and browse for the .tar file for UniKernel.
6. Click start and ODIN will begin to flash the kernel.
7. The phone should reboot and then check to see if the Kernel Version in Settings > About Phone says UniKernel.
8. If it does then you should be rooted and have SuperSU installed under Apps.
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Have not heard before that people have gotten Knox tripped by flashing Samsung firmware, you could have by mistake flashed TWRP or an non Samsung partition file etc. But atleast try a factory reset. If that does not work, you tripped Knox:/
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
notsotet said:
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
Click to expand...
Click to collapse
It's official stable release of Android Pie with region code DBT. It mess things up when I had a device with NEE as a region?
I don't know maybe I just live with this and wait for the official Nordic Android Pie update.
Tuikelo said:
It's official stable release of Android Pie with region code DBT. It mess things up when I had a device with NEE as a region?
I don't know maybe I just live with this and wait for the official Nordic Android Pie update.
Click to expand...
Click to collapse
Being that I'm in the US I can't say for sure what the issue is because I haven't gotten the official stable build yet.
I'd say just flash back to stock official 8 for your region and wait for the ota. Shouldn't be too much longer for you.
Tuikelo said:
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Click to expand...
Click to collapse
I would double check to make sure you didn't trip knox... The following steps should help do this
Completely power off off your Galaxy S9+
Restart the phone in Download Mode
Once in download mode, visually search for the words "Warranty Void" and the numbers that are on the same line.
If the numbers show “0x0” knox has not been tripped.
If the numbers show “0x1” knox has been permanently (as in you can't fix it ever on that phone because an E-Fuse has been blown) tripped
Assuming that knox is still intact then I would believe the issue (I would say 80% if I had to guesstimate) due to the mismatch between the rom file you flashed and the existing bootloader, partition, csc, etc. that you didnt flash. For example if parts of the rom are from oreo and the android OS is the pie beta this could cause problems. I am not sure if they did this or not, but it would make sense that Samsung incorporated some sort of file/firmware/version integrity check
An easy way to tell if this is the case is to get all the firmware versions to come from the same release. In effect Can you restore it back to the way it was before you flashed the device? Or if possible can you update it fully so that all the files are the same firmware? Which ever route you go will be up to you, but overall if the files all come from the same firmware version if the apps in question work this will confirm the cause.
Also double check the firmware your flashing... If it is a release before the official beta's you may run into problems. Your gonna have to go ask in the board/forum you got the file from (in the respective thread) for help or check up on known issues. Otherwise if the use of Samsung pass and secure folders is of importance to you I would revert back to the firmware you were on (before you attempted to flash the beta) and wait for the official release.
The use of mismatched firmware parts can also cause you to not get any OTA updates, so your gonna have probably flash it again properly to correct that
Lastly if I recall correctly if you have enabled OEM unlock this can cause samsung pass and secure folders to not work.
notsotet said:
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
Click to expand...
Click to collapse
The Google Pay thing is because Google Play Protect Certification Status has flagged the device as not certified. This is because we are currently using an unreleased (i.e. beta test from Samsung) firmware version. Once we are on an official release the Certification Status will revert to certified status and Google Pay will work.
The issue with Google Pay under the Android Pie beta does/should not effect Samsung Pass or Secure Folder at all. Currently on my install of the beta test version(s) Samsung Pass, Samsung Pay, Samsung Health and Secure Folder (all which rely on knox) work just fine. I am using them all the time without issue, with the exception of a few cosmetic aspects at first that have been resolved by Samsung.
he can also type "getprop" in adb shell or a terminal app and look for the warranty..
but as someone else already suggested, if you flashed a "beta" pie build that could absolutely cause it to read as custom (this wouldnt trip knox though) which would cause some issues with those apps..
if it is unnoficial/reading as custom, you should be able to check in settings > about phone > status then look for "Device Status".. I think its there in Pie..
to put into perspective, i simply disabled some apks.. im on a usa note 9 which means i couldnt root, unlock or trip knox if i wanted to but simply disabling some apps causedmine to show custom as u can see in my screenshot lol
Tuikelo said:
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Click to expand...
Click to collapse
I flashed the stable Pie update (DBT) as well and I'm not receiving that notification/error when I open Samsung pass. Flash all of the files in the zip (use HOME_CSC if you want to keep your data) and see if that helps.
Solution
I did a reload of oreo on my s9+ after doing an update to android 9 (Australian versions ) which I didn't like. My
google and Samsung pay would not work until I switched back off "OEM unlock" in "Developer tools" which erases your phone again like it did when you turned it on to load firmware with odin. The option is locked out and takes a week of being turned on to come back up.
I've successfully rooted my Galaxy Note 3 to play custom boot animations and boot audio. But now I want to try it on my main device; the Galaxy Note 20 Ultra. I only want to modify "bootsamsung.qmg", "bootsamsungloop.qmg", and try adding "PowerOn.ogg". (Is this even possible on newer Samsung phones?)
Thing is, I don't want to root this device because I still want to get security patches and updates without doing complicated flashing procedures, and I still want to get OEM support.
Is there a way to at least root the phone temporarily without voiding the software legitimacy, and still get support for updates?
(If not then guess I'll just wait till 2025 when the phone stops getting software updates)
ASEM1123 said:
I've successfully rooted my Galaxy Note 3 to play custom boot animations and boot audio. But now I want to try it on my main device; the Galaxy Note 20 Ultra. I only want to modify "bootsamsung.qmg", "bootsamsungloop.qmg", and try adding "PowerOn.ogg". (Is this even possible on newer Samsung phones?)
Thing is, I don't want to root this device because I still want to get security patches and updates without doing complicated flashing procedures, and I still want to get OEM support.
Is there a way to at least root the phone temporarily without voiding the software legitimacy, and still get support for updates?
(If not then guess I'll just wait till 2025 when the phone stops getting software updates)
Click to expand...
Click to collapse
It's a "have one's cake and eat it too" problem.
yes, you can modify phone without rooting phone.
no, you can't modify phone without losing knox/warranty.
no, you can't receive updates on modified phone.
aIecxs said:
yes, you can modify phone without rooting phone.
no, you can't modify phone without losing knox/warranty.
no, you can't receive updates on modified phone.
Click to expand...
Click to collapse
Ah, so even if it's not rooted it'll void the legitimacy when modified?
well that's a bummer
ASEM1123 said:
Ah, so even if it's not rooted it'll void the legitimacy when modified?
well that's a bummer
Click to expand...
Click to collapse
It is obvious that root is a modification of the system.
on locked bootloader no modifications allowed by secure boot chain of trust.
you already trip knox when unlocking bootloader, even if running completely stock ROM.
yeah, i was just hoping if there was a way somehow.
Thanks y'all.