late on updates : april 2017 - Samsung Galaxy S8 Questions and Answers

Hey guys;
I have an s8 that i bought used, it didn't get any updat since april 2017 ( before i had it), what could be the cause of that
And how can i upgrade to oreo without breaching knox ?
Thank you

Probably down to it being a carrier branded firmware but even then it's a long time. Where are you from if you don't mind me asking? Or it was rooted previously, does stuff like s-health work fine and what not?
If it comes to it you can flash firmware via Odin software which update phone without tripping knox

My knox status

The apps works fine, and i am actually on Orange morocco, but i dont know the origin of the phone

sofir786 said:
Probably down to it being a carrier branded firmware but even then it's a long time. Where are you from if you don't mind me asking? Or it was rooted previously, does stuff like s-health work fine and what not?
If it comes to it you can flash firmware via Odin software which update phone without tripping knox
Click to expand...
Click to collapse
I have few more questions
Wouuld the odin manipulation trip my knox
How can i keep my parameters and app with odin
Would the phone get OTAs after the upgrade.?

Related

[Q] De-brand i9505 4.2.2 using official 4.3 without tripping Knox?

I've a i9505, unfortunately it's branded (but no locked) in T-Mobile. I'd love to install 4.3 on it, but T-Mobile hasn't released it, so it's unavailable in Kies.
I would like to know if it's possible to use official (non-branded) firmware and _not_ to trip Knox (as it voids warranty in Poland). I've went through most of Knox-related threads, but I fail to see clear indication of 1) if it's possible 2) how to do that.
Also, does anyone knows if, after de-branding the phone, I'll be able to upgrade from 4.3 to 4.4 (for example) without tripping Knox?
Any comments will be appreciated.
Bump, anyone?
Stasheck said:
Bump, anyone?
Click to expand...
Click to collapse
1. If u still having Knox 0x0 and android 4.2.2 only u have to root ur phone and delete the apps branded.
2. If u dont have updates in Kies is better. Don't void ur warranty and enjoy with ur 4.2.2 firmware.
OK, my point is to get Android 4.3 and not trip Knox - T-Mobile hasn't released 4.3 yet, and god knows when they do that.
Alternative question: is there a way to install official 4.3 without installing Knox bootloader?
i'v been looking around for the same thing, but i dont think thats possible without installing a custom made ROM
OK, let's try to put it another way: given that I have 4.2.2, do I risk losing warranty when I install CWM and some de-KNOXed 4.3 using Odin? Or Triangle Away will just work, and I'll be able to flash default software in case I need to service the phone?

Rooted with RDLV, Knox 0x0. But, what now?

I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Pierre118 said:
I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Click to expand...
Click to collapse
Somebody show me the way? Just flash the BTU with Odin? I don't mind tripping knox.
Pierre118 said:
I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Click to expand...
Click to collapse
1. You should read the thread on how to update the system using Mobile Odin PRO without losing knox 0x0. Also keep in mind that you need to stop both ROM and security automatic updates in order to avoid having the knox flag triggered.
2. Also check http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=VOD#firmware
3. If you really want to change CSC away from VOD and for instance to BTU you should probably do that first at MI7 level (from your current MI7 VOD to MI7 BTU) if you want maximum safety and to be able to root again with knox 0x0. You might also need an app to help you checking/changing CSC, look around for threads discussing that specific topic.
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Pierre118 said:
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Click to expand...
Click to collapse
You do not need to use a firmware with the original CSC, BUT:
- you should try to do as much of the changes as possible on OLDER versions with the old bootloader (so that you can still root and keep knox 0x0)
- writing a ROM with a different CSC will very often NOT change your effective CSC - many ROMs are multi-CSC and you might keep existing CSC on the new ROM; in order to finalize the change you will need to use a program that forces the CSC change (and you will see that the CSC was changed since it will totally wipe the user data in the phone - like a full factory reset)
- you should also be aware that some changes might mess things on your phone, so instead of jumping to the first change you can think-off you should first try to read more around here.
xclub_101 said:
You do not need to use a firmware with the original CSC, BUT:
- you should try to do as much of the changes as possible on OLDER versions with the old bootloader (so that you can still root and keep knox 0x0)
- writing a ROM with a different CSC will very often NOT change your effective CSC - many ROMs are multi-CSC and you might keep existing CSC on the new ROM; in order to finalize the change you will need to use a program that forces the CSC change (and you will see that the CSC was changed since it will totally wipe the user data in the phone - like a full factory reset)
- you should also be aware that some changes might mess things on your phone, so instead of jumping to the first change you can think-off you should first try to read more around here.
Click to expand...
Click to collapse
Thanks for your helpful reply. I will take your advice and will read more around here before I do things I don't understand. I'm rooted now at firmware MI7, with 0x0 Knox. I did a lot of reading before I took that step. I will take time before I do the next one.
Pierre118 said:
Thanks for your helpful reply. I will take your advice and will read more around here before I do things I don't understand. I'm rooted now at firmware MI7, with 0x0 Knox. I did a lot of reading before I took that step. I will take time before I do the next one.
Click to expand...
Click to collapse
Don't forget to disable automatic updates and security updates. Especially read the thread on Mobile Odin PRO and updating while keeping knox 0x0. (CSC is almost irrelevant in most cases - as long as 3G/4G from your provider is correctly detected; if you are rooted with knox 0x0 you will ALWAYS want to update the ROM manually under YOUR control and not when Samsung or your carrier wants to update your phone).
xclub_101 said:
Don't forget to disable automatic updates and security updates. Especially read the thread on Mobile Odin PRO and updating while keeping knox 0x0. (CSC is almost irrelevant in most cases - as long as 3G/4G from your provider is correctly detected; if you are rooted with knox 0x0 you will ALWAYS want to update the ROM manually under YOUR control and not when Samsung or your carrier wants to update your phone).
Click to expand...
Click to collapse
What do you freeze in titanium backup so it won't update.
Dattack said:
What do you freeze in titanium backup so it won't update.
Click to expand...
Click to collapse
Software Update (also Samsung Hub Update, but that is just since I never use the Samsung Hub). Right now I did not freeze the Security Policy Update but I am tempted - but on that I first disabled automatic security updates somewhere in settings.
Pierre118 said:
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Click to expand...
Click to collapse
In fact N9005VFGDMJ1 and N9005VFGBMI1 are from the same CSC

[Q] Haven't ever been able to upgrade firmware on Note 3 since purchase - what's up?

Hola,
Got my Note 3 a while back, and I'm getting itchy firmware fingers!
Maybe I'm being stupid - but so far I haven't had any luck in 'automatically' finding updated firmwares - still sitting on the MHN one that was installed when I bought the phone back on November.
Am I doing anything wrong? Do I need to root to be able to update the firmware? KIES says I'm on the latest... Not a network locked phone - have used t-mob, orange and currently a 3 sim.
Halp!
Hup we go!
No updates have ever come through either OTA or KIES... why me!
pipohippo said:
Hup we go!
No updates have ever come through either OTA or KIES... why me!
Click to expand...
Click to collapse
mate why dont you update via pc odin then ? and you dont need root to upgrade via kies
here try this for guide
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
get your firmware from here
http://www.samfirmware.com/
pipohippo said:
Hup we go!
No updates have ever come through either OTA or KIES... why me!
Click to expand...
Click to collapse
Maybe you should post more details - for instance what version of Note 3 do you have (ideally you want to know the original code, something like N9005ZWE or N9005ZKEBTU, which identifies a N9005 for UK) and what firmware are you right now. And eventually what have you asked when originally asked about the country where you are (for the license agreement). If the combinations above get very weird you also need to know your effective CSC, but that could be a longer shot.
Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)
pipohippo said:
Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)
Click to expand...
Click to collapse
No my friend as I said before updating via odi n dsnt require root... great now you can just download 4.4.2 firmware for your note 3 and update
Sent from my SM-N900 using Tapatalk
pipohippo said:
Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)
Click to expand...
Click to collapse
N9005ZKEBTU seems to be be EU-British unlocked N9005 - I would assume that you also picked UK when asked about the license agreement.
N9005XXUBMHN is a very interesting version of the firmware that is not even listed here:
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=BTU#firmware
You seem to have a fairly recent firmware and for the moment there is no 4.4.2 version of the BTU sub-region.
I am guessing that the firmware is actually way old, so it's not listed! Assuming the firmwares are in alphabetical order!
MHx < MJx
All UK aye - good to know that the phone is actually unlocked though I'll have a look on SamMobile and grab a nice 4.3 firmware - not ready for KitKat yet!
xclub_101 said:
N9005ZKEBTU seems to be be EU-British unlocked N9005 - I would assume that you also picked UK when asked about the license agreement.
N9005XXUBMHN is a very interesting version of the firmware that is not even listed here:
-
You seem to have a fairly recent firmware and for the moment there is no 4.4.2 version of the BTU sub-region.
Click to expand...
Click to collapse
pipohippo said:
I am guessing that the firmware is actually way old, so it's not listed! Assuming the firmwares are in alphabetical order!
MHx < MJx
All UK aye - good to know that the phone is actually unlocked though I'll have a look on SamMobile and grab a nice 4.3 firmware - not ready for KitKat yet!
Click to expand...
Click to collapse
Hmm, for some reason I was thinking MK instead of MH, indeed your firmware is unusual! But please be aware that those old firmware versions are the only ones that can be safely rooted without triggering the knox warranty flag. Which reminds me - if you go to download mode do you see any reference to knox?
Knox Kernal Lock: 0x0
Knox Warranty Void: 0x0
I am guessing that is kind of good right?
final clarification - rooting has the possibility of triggering knox warranty shizzle, but just doing a 'standard' firmware update (even via odin) should keep things fine right?
xclub_101 said:
Hmm, for some reason I was thinking MK instead of MH, indeed your firmware is unusual! But please be aware that those old firmware versions are the only ones that can be safely rooted without triggering the knox warranty flag. Which reminds me - if you go to download mode do you see any reference to knox?
Click to expand...
Click to collapse
pipohippo said:
Knox Kernal Lock: 0x0
Knox Warranty Void: 0x0
I am guessing that is kind of good right?
final clarification - rooting has the possibility of triggering knox warranty shizzle, but just doing a 'standard' firmware update (even via odin) should keep things fine right?
Click to expand...
Click to collapse
Correct, standard Odin update WITH THE RIGHT FIRMWARE will be fine.
IMHO your absolute best path from this point would be something like this:
- save whatever you need to save to the cloud or eventually on the external microSD (just in case)
- disable reactivation lock; disable any updates and security updates in the current ROM; stop mobile data and WiFi; keep all updates off and all network off until the very last step of the entire procedure
- using normal Odin and download mode install oldest BTU firmware you can get - MI7 in the link I provided above; that update should go without any problem; reboot and check everything is OK (and stop again any network or update if re-enabled); this step is only needed in order to get you on the EXACT same path that the huge majority of the people around (including me) have used with URDLV; it might be possible to skip this and still have everything working 100% (and this is quite very likely but I have not tested it);
- using Universal Root de la Vega (URDLV) and the same MI7 from above you will generate a N9005XX____MI7_HOME_VEGA.tar.md5 file which then you will again write with normal Odin and in download mode; this will get you rooted on MI7 with knox 0x0 ; you can read more about this in the URDLV thread
- then using Mobile Odin Pro (NOT normal Odin / download mode) and the most recent 4.3 version available for BTU you can update to MJ7 or MK2 - while keeping root and knox 0x0!
Read for more details on the last step this thread:
http://forum.xda-developers.com/showthread.php?t=2522729
Also note that Mobile Odin Pro will also let you update to 4.4 and keep root and knox 0x0, so it is not a bad investment. Also note that at this point there is no other way to root with knox 0x0 once you got past a certain firmware, nor is it possible to go back before the version of your bootloader (so in other words the above procedure also would guarantee that you can get back to MI7 if for instance you do not like MK2, something you would never otherwise be able to do).
As my signature shows - MJ7 / MK2 are currently very solid versions (and if you are rooted you can get amazing battery life and performance) and I would strongly suggest avoiding any upgrade towards 4.4 in the immediate future.

De-branding without tripping KNOX counter

Hi all,
I have a simpple question: is it possible to flash Samsung stock ROM (official for same country, via Odin) to carrier branded phone version without tripping KNOX counter??
Sorry for possible duplicated question, but after a lot of searches I'm still unable to find clear and reliable answer (
Thank you very much in advance for any help or suggestions!
Best regards,
Lubos
BubuLK said:
Hi all,
I have a simpple question: is it possible to flash Samsung stock ROM (official for same country, via Odin) to carrier branded phone version without tripping KNOX counter??
Sorry for possible duplicated question, but after a lot of searches I'm still unable to find clear and reliable answer (
Thank you very much in advance for any help or suggestions!
Best regards,
Lubos
Click to expand...
Click to collapse
I'm hunting for a way to debrand in the first place. I have a H3G (Three UK) branded phone and I've not had an update since I got it on March 8th. Still on the February security release.
0verdaflow said:
nope you cant do that ....
Click to expand...
Click to collapse
There's a number of threads stating that using Odin will not trip Knox if you flash any other firmware. I was planning on replacing mine with BTU firmware as it is more up to date as well.
If you flash official firmware with Odin you won't trip Knox.
cfhuk said:
There's a number of threads stating that using Odin will not trip Knox if you flash any other firmware. I was planning on replacing mine with BTU firmware as it is more up to date as well.
Click to expand...
Click to collapse
I'm in a similar position. I'm thinking about flashing another stock to my EE UK S7 Edge. I'm also still on Feb security release and really want to be receiving updates sooner.
Sent from my SM-T815 using XDA-Developers mobile app
You can easily flash ANY stock firmware with odin without issues. Images are available at sammobile and other sources. I´ve debranded my vodafone version to DBT

Which firmware to use?

Hi,
My brother has bought a S7 edge AT&T model for me from USA which was rooted. I am not able to update the firmware to nougat as it was unlocked and cannot be updated in India using the local carrier. I wanted a small bit of help. I am planning to update the firmware for the first time ever on any handset, hence I am completely unaware of the process. Though I can see the guide, but I have the following questions if anyone can answer
Which is the best firmware to be used in India (would be helpful if you can provide with the thread link for the firmware)
Does it harm the mobile in any manner like lower battery life?
Is it difficult to update the firmware? What are the chances of me bricking it?
It seems that the original firmware has changed and the Samsung Pay is not working. How would I know if this is because the knox is tripped? I downloaded the Knox Status app and it shows warranty is valid, does this mean knox is not tripped? If so, I would like to update the firmware which would not trip the knox.
How does the back up work? Do I have to reinstall all the applications after firmware update?
My reason of updating the firmware is only have the latest features on the original firmware. Not for any specific modified features that I am looking out for.
Thanks for the help.
Regards,
Chandrahas Sampat
try this
https://forum.xda-developers.com/att-s7-edge/how-to/updated-935u-935a-live-links-pi3-t3501686
clean flash i would recommend restore apps via smart switch or any 3rd party apps

Categories

Resources