Downgrade from 4.4.2 back to 4.3!! - Galaxy Note 10.1 (2014 Edition) General

Good News Folks!!!
I just downgraded my SM-P605 from NEE 4.4.2 back to NEE MJ9 4.3!! Knox not trigerred.
Step to downgrade from 4.4.2 back to 4.3:
1. Reboot to Download Mode (Power+Vol. Down) then Vol. Up to continue
2. Run Odin from PC (I used 3.09)
3. Uncheck Auto Reboot box
4. Check AP box, then find your NEE 4.3 MJ9 .tar firmware
5. Press Start
It takes about 2-3 minuttes until showing All threads completed.(succeed 1/failed 0) in the message box.
6. Turn off your note by holding down power button for few seconds
7. Press Vol. Up + Power button to boot into recovery
8. Wipe cache
9. Wipe user data
10. Reboot system
No SW rev failed during downgrade and Knox remains 0x0
Don't forget to hit Thanks button..

I love it. Begging for thanks without telling what you did.

I hope someone with a rooted p605 can manually save this Kitkat OTA(NEE region) file before Samsung start to lock bootloader from ability to downgrade from KK to JBean.

...

Adalean said:
What was the reason/why would you choose to downgrade back to 4.3?
Click to expand...
Click to collapse
Well, I had do install 4.3 firmware back cos there's no 4.4 firmware to flash trough Odin yet as I messed my tab trying to get s pen work after rooting. Now I'll just upgrade back to 4.4 and wait for root that doesn't break s pen.

droidan said:
Knox remains 0x0
Click to expand...
Click to collapse
KNOX trips when a non-KNOX or non-official bootloader is installed. 4.3 on the N10.1-14 had a KNOX enabled bootloader so downgrading from 4.4 wouldn't be an issue; at least for KNOX. People in other forums that moved to 4.3 from earlier s/w with non-KNOX enabled bootloaders are the ones who were freaking out because once KNOX is on a device you can't go back.
The “KNOX Warranty Void” bit (or simply KNOX bit) is used to detect if a non-KNOX kernel has been loaded on the device. It is a one-time programmable bit in e-fuse, which can only be turned from “0” to “1” (i.e. burned). If a non-KNOX boot loader or kernel has been put on the device, KNOX can no longer guarantee the security of the KNOX container. As a result, this KNOX bit will be burned to “1”, indicating that this device can no longer use the KNOX container service.​https://www.samsungknox.com/en/blog...ox-enabled-devices-and-knox-warranty-void-bit

BarryH_GEG said:
KNOX trips when a non-KNOX or non-official bootloader is installed. 4.3 on the N10.1-14 had a KNOX enabled bootloader so downgrading from 4.4 wouldn't be an issue; at least for KNOX. People in other forums that moved to 4.3 from earlier s/w with non-KNOX enabled bootloaders are the ones who were freaking out because once KNOX is on a device you can't go back.
The “KNOX Warranty Void” bit (or simply KNOX bit) is used to detect if a non-KNOX kernel has been loaded on the device. It is a one-time programmable bit in e-fuse, which can only be turned from “0” to “1” (i.e. burned). If a non-KNOX boot loader or kernel has been put on the device, KNOX can no longer guarantee the security of the KNOX container. As a result, this KNOX bit will be burned to “1”, indicating that this device can no longer use the KNOX container service.​https://www.samsungknox.com/en/blog...ox-enabled-devices-and-knox-warranty-void-bit
Click to expand...
Click to collapse
And your point is?

droidan said:
And your point is?
Click to expand...
Click to collapse
Pretty simple. Explaining to folks here who may not know what trips KNOX along with an explanation of how it works from a Samsung VP. I thought it was pretty clear.

Anyone tried on the P600? I've been stalling the update due to a bad experience with my previous p600.

elzeus said:
Anyone tried on the P600? I've been stalling the update due to a bad experience with my previous p600.
Click to expand...
Click to collapse
I guess Barry may have a good solution..
"
4.3 on the N10.1-14 had a KNOX enabled bootloader so downgrading from 4.4 wouldn't be an issue;....."

Normally and afaik you cant downgrade to an earlier android iteration. It is not possible. You can only jump to fws with the same bootloader. Not every fw get a new bootloader. Maybe with the ota of nee fw wasnt flashed the bootloader correctly. I think when you flash the same fw with Odin, you cant downgrade anymore.

hanspampel said:
Normally and afaik you cant downgrade to an earlier android iteration. It is not possible. You can only jump to fws with the same bootloader. Not every fw get a new bootloader. Maybe with the ota of nee fw wasnt flashed the bootloader correctly. I think when you flash the same fw with Odin, you cant downgrade anymore.
Click to expand...
Click to collapse
That's why I pointed it out..

Typing *#2663# and updating Wacom files did the trick for me to get the SPen to work without any hassle.
droisntns said:
Well, I had do install 4.3 firmware back cos there's no 4.4 firmware to flash trough Odin yet as I messed my tab trying to get s pen work after rooting. Now I'll just upgrade back to 4.4 and wait for root that doesn't break s pen.
Click to expand...
Click to collapse
Sent from my Samsung Galaxy Note 10.1 2014 LTE (P605)

droidan said:
Good News Folks!!!
I just downgraded my SM-P605 from NEE 4.4.2 back to NEE MJ9 4.3!! Knox not trigerred.
Step to downgrade from 4.4.2 back to 4.3:
1. Reboot to Download Mode (Power+Vol. Down) then Vol. Up to continue
2. Run Odin from PC (I used 3.09)
3. Uncheck Auto Reboot box
4. Check AP box, then find your NEE 4.3 MJ9 .tar firmware
5. Press Start
It takes about 2-3 minuttes until showing All threads completed.(succeed 1/failed 0) in the message box.
6. Turn off your note by holding down power button for few seconds
7. Press Vol. Up + Power button to boot into recovery
8. Wipe cache
9. Wipe user data
10. Reboot system
No SW rev failed during downgrade and Knox remains 0x0
Don't forget to hit Thanks button..
Click to expand...
Click to collapse
I did not want to downgrade back to 4.3 anymore. Here's why:
1. Full support for wireless printing is available for many apps
2. The Samsung clock widget in Android 4.3 has been replaced with the Nexus-like clock in Android 4.4. The font is much thinner that the previous version. It also includes a world clock, alarm, stopwatch, and a timer. The personal message feature is still available as an option.
3. The settings menu is still multi panel, with some Galaxy S5 icons. You can even resize the columns.
4. KNOX 2.0 is here, similar to the one on the S5.
KNOWN ISSUES
1. Lock screen effect does not work correctly (no ink effect)
2. I don't know if I downgrade to MK1 from ND2, will it trip KNOX? (United States version) ND2 uses KNOX 2.0.
Current build number: KOT49H.P600UEUCND2

KiwiBird97 said:
I did not want to downgrade back to 4.3 anymore. Here's why:
1. Full support for wireless printing is available for many apps
2. The Samsung clock widget in Android 4.3 has been replaced with the Nexus-like clock in Android 4.4. The font is much thinner that the previous version. It also includes a world clock, alarm, stopwatch, and a timer. The personal message feature is still available as an option.
3. The settings menu is still multi panel, with some Galaxy S5 icons. You can even resize the columns.
4. KNOX 2.0 is here, similar to the one on the S5.
KNOWN ISSUES
1. Lock screen effect does not work correctly (no ink effect)
2. I don't know if I downgrade to MK1 from ND2, will it trip KNOX? (United States version) ND2 uses KNOX 2.0.
Current build number: KOT49H.P600UEUCND2
Click to expand...
Click to collapse
I agree with you.
I believe we all like Kitkat.
Almost all the recent Samsung devices will not allow us to revert back to 4.3 after updating 4.4, EXCEPT Note 3 SM-N900W8 with earlier KK botloader. I guess that's the only variant of Note 3 that can be rooted and installed TWRP/CWM recovery without tripping knox.
I hope Chainfire may look thru this NEE P605XXUCNE2 bootloader/firmware. Hopefully, he will find something like the way he did with SM-N900W8.

hanspampel said:
Normally and afaik you cant downgrade to an earlier android iteration. It is not possible. You can only jump to fws with the same bootloader. Not every fw get a new bootloader. Maybe with the ota of nee fw wasnt flashed the bootloader correctly. I think when you flash the same fw with Odin, you cant downgrade anymore.
Click to expand...
Click to collapse
I tried 2 times(down, up, down then up again) with Odin, confirmed working.

droidan said:
I agree with you.
I believe we all like Kitkat.
Almost all the recent Samsung devices will not allow us to revert back to 4.3 after updating 4.4, EXCEPT Note 3 SM-N900W8 with earlier KK botloader. I guess that's the only variant of Note 3 that can be rooted and installed TWRP/CWM recovery without tripping knox.
I hope Chainfire may look thru this NEE P605XXUCNE2 bootloader/firmware. Hopefully, he will find something like the way he did with SM-N900W8.
Click to expand...
Click to collapse
:good:
Support for Chainfire!

droidan said:
I tried 2 times(down, up, down then up again) with Odin, confirmed working.
Click to expand...
Click to collapse
Confirmed working. Downgraded successfully. Knox 0x0.

droisntns said:
Well, I had do install 4.3 firmware back cos there's no 4.4 firmware to flash trough Odin yet as I messed my tab trying to get s pen work after rooting. Now I'll just upgrade back to 4.4 and wait for root that doesn't break s pen.
Click to expand...
Click to collapse
If you want full sd card write function that the dips at Google killed. That alone is reason enough. I see no speed or battery improvement with Kitkat, so 4.3 is the way to go, IF you want card write function for 3rd party apps.

shayind4 said:
Confirmed working. Downgraded successfully. Knox 0x0.
Click to expand...
Click to collapse
Did you downgrade on the p600?

Related

[N9005] Boot looping + unknown baseband

Hi,
After flashing the MJ6 ROM with the Universal root de la vega method (I have the old bootloader from MJ1) and flash the MJ4 modem, the camera and and wifi were not working, I tried to downgrade the modem to MJ2 with Odin to give a try.
However now I'm facing several boot loops (on first notification model screen) and when the Note succeed in corectly booting, I have an FC from system process, and some others applications.
I tried to check the phone parameters and saw that baseband was "unknown", but didn't succeed to see the screen where the IMEI is displayed because the phone is rebooting automaticaly when I try to access to this screen.
The phone is very instable : sometimes I'm not able to access to parameters with the tactil button.
In all cases the phone is auto rebooting after several minutes.
I tried several things withoot result :
- Wipe cache + factory reset
- Flash several modems
- Flash MI7 stock ROM with Odin
> no change
Actually I have :
- baseband unknown
- boot looping
- no wifi
- no sound
- no root
- acces to download mode and stock recovery is OK.
As someone have some cloues to help me?
Crystal7_Magic said:
Hi,
After flashing the MJ6 ROM with the Universal root de la vega method (I have the old bootloader from MJ1) and flash the MJ4 modem, the camera and and wifi were not working, I tried to downgrade the modem to MJ2 with Odin to give a try.
However now I'm facing several boot loops (on first notification model screen) and when the Note succeed in corectly booting, I have an FC from system process, and some others applications.
I tried to check the phone parameters and saw that baseband was "unknown", but didn't succeed to see the screen where the IMEI is displayed because the phone is rebooting automaticaly when I try to access to this screen.
The phone is very instable : sometimes I'm not able to access to parameters with the tactil button.
In all cases the phone is auto rebooting after several minutes.
I tried several things withoot result :
- Wipe cache + factory reset
- Flash several modems
- Flash MI7 stock ROM with Odin
> no change
Actually I have :
- baseband unknown
- boot looping
- no wifi
- no sound
- no root
- acces to download mode and stock recovery is OK.
As someone have some cloues to help me?
Click to expand...
Click to collapse
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
ultramag69 said:
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
Click to expand...
Click to collapse
I had the same pb ..... and flash MJ6 full and now it's OK .... so I rooted ... Knox 1 ....but everything OK I am happy
Ok, but normaly I always have the old bootloader because I do not have flash the MJ6 stock > It has been modified with universal root de la vega before flashing with Odin, and my flag is still on 0x0.
> So normaly the MJ6 I flashed should not contain the new bootloader.
It will be troublesome for me if flashing a stock MJ6 is needeed as I do not want to trigger the Knox flag.
I always have the solution to return my Note to my seller for refund, so I'm seeking for a way which do not trigger Knox
ultramag69 said:
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
Click to expand...
Click to collapse
LIPA said:
I had the same pb ..... and flash MJ6 full and now it's OK .... so I rooted ... Knox 1 ....but everything OK I am happy
Click to expand...
Click to collapse
Finaly I have decided to flash the MJ6 stock ROM and everything go ok.
I still have my knox 0x0 but will trigger to 0x1 if I try to root by now : hard decision.
Thanks for your help you two
Crystal7_Magic said:
Finaly I have decided to flash the MJ6 stock ROM and everything go ok.
I still have my knox 0x0 but will trigger to 0x1 if I try to root by now : hard decision.
Thanks for your help you two
Click to expand...
Click to collapse
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Where can I find the MJ6 firmware
ultramag69 said:
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Click to expand...
Click to collapse
It will be strange, because I succedeed to root the Note withoot triggering Knox
You have to be sure that you do not have take update from OTA or official stock ROM when you was on ROM before MJ3 (if you take stock MJ3 bootloader is altered)
yazzie said:
Where can I find the MJ6 firmware
Click to expand...
Click to collapse
You can find it on Sammobile website (create an account is needed to access to download section)
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=0#firmware
After flashing the MJ6 stock firmware to recover my baseband, I have juste noticed that wifi is not properly working.
> Wifi is blocked on activation
> Sometime the Note succeed to activate wifi and show me networks which are available, however when I'm trying to connect to one of them I got a freeze then wifi go back to activating statuts.
Any explanation?
SM-N900W8 Boot Loop
Has anyone else resolved this issue. Phone was rooted with "CF-Auto-Root-hltecan-hlteub-smn900w8" and used TWRP 2.6.3.0. Upon doing a restore with TWRP, the phone is now in this crazy loop. Phone boots but always fails prior to seeing home screen. Tried going to SamMobile and restoring original Rogers firmware with no resolution.
Any help is most appreciated.
ultramag69 said:
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Click to expand...
Click to collapse
thanks a million. i had the same problem, following my ordeal with samsung on region sim lock.
i tried the mj6, it seemed too work, for now.
will root it and see how that goes. thanks once again
Ahmads001 said:
thanks a million. i had the same problem, following my ordeal with samsung on region sim lock.
i tried the mj6, it seemed too work, for now.
will root it and see how that goes. thanks once again
Click to expand...
Click to collapse
If you flashed the stock MJ6 then you have the new anti-root bootloader. ANY attempt to root will end in Warranty void being triggered...
Unfortunately this is a problem that hasn't been fixed yet. Just a heads up to let you know you will probably trigger the warranty void.
Then again Designgears is back developing RDLV again so it might be updated soon... :fingers-crossed:
ultramag69 said:
If you flashed the stock MJ6 then you have the new anti-root bootloader. ANY attempt to root will end in Warranty void being triggered...
Unfortunately this is a problem that hasn't been fixed yet. Just a heads up to let you know you will probably trigger the warranty void.
Then again Designgears is back developing RDLV again so it might be updated soon... :fingers-crossed:
Click to expand...
Click to collapse
thanks again for usual insight.
unfortunately, the bootloop problem was back after a restart yesterday. took several loops (about 30 mins) before it started up. i had to reflash with the latest stock N9005XXUDMJ7_N9005OJVDMJ4_KSA. now im scared to restart the phone for any reason, since i cant tell if it will entre bootloop again - it gets worse with every reset.
Since the knox already tripped 0x1, i still desire to root it ASAP.
So,
1. how do i get rid of this bootloop menace, PERMANENTLY
2. how do i safely root the phone (SM-N9005)
will appreciate a lot of help.
Ahmads001 said:
thanks again for usual insight.
unfortunately, the bootloop problem was back after a restart yesterday. took several loops (about 30 mins) before it started up. i had to reflash with the latest stock N9005XXUDMJ7_N9005OJVDMJ4_KSA. now im scared to restart the phone for any reason, since i cant tell if it will entre bootloop again - it gets worse with every reset.
Since the knox already tripped 0x1, i still desire to root it ASAP.
So,
1. how do i get rid of this bootloop menace, PERMANENTLY
2. how do i safely root the phone (SM-N9005)
will appreciate a lot of help.
Click to expand...
Click to collapse
As Knox is tripped use cf-autoroot found in the original android developement section of the Note 3 forum. This will give you root...
I would also try a different region rom, I used MJ7 from the UK. It didn't cause any issues.
I had bootloops and found going to wifi, clicking on menu button, advanced.& unticking "Scanning always available" seemed to fix my bootloops but this was for my MJ1 firmware.
Otherwise can't really help anymore tonight. Gotta go to work tomorrow and its 2am here in Oz....
ultramag69 said:
As Knox is tripped use cf-autoroot found in the original android developement section of the Note 3 forum. This will give you root...
I would also try a different region rom, I used MJ7 from the UK. It didn't cause any issues.
I had bootloops and found going to wifi, clicking on menu button, advanced.& unticking "Scanning always available" seemed to fix my bootloops but this was for my MJ1 firmware.
Otherwise can't really help anymore tonight. Gotta go to work tomorrow and its 2am here in Oz....
Click to expand...
Click to collapse
thanks, and good morning.
will be back later (sorry some of us -docs- dont actually have the 'day/night' thing).
will try the wifi thing, and see what happens.
once again, thanks
Same problem here :
- Supposed to be MK2 rom (N9005XXUDMK2) and was rooted
- Recovery and download mode are OK
- Flashed several time with ODIN, including modem.bin from the same archive
- Obviously Knox is 0x01
But phone is still unuseable ....Boots up, pass the intial setting. Then error message about system not responding and reboot ...
Any help would be appreciated
Follow this it'll fix it http://forum.xda-developers.com/showthread.php?p=47014662
Sent from my SM-N9005 using XDA Premium 4 mobile app
You saved my day !!! Thanks
Crystal7_Magic said:
After flashing the MJ6 stock firmware to recover my baseband, I have juste noticed that wifi is not properly working.
> Wifi is blocked on activation
> Sometime the Note succeed to activate wifi and show me networks which are available, however when I'm trying to connect to one of them I got a freeze then wifi go back to activating statuts.
Any explanation?
Click to expand...
Click to collapse
I have the same problem
You solved your problem?
Thanks
sbdz said:
I have the same problem
You solved your problem?
Thanks
Click to expand...
Click to collapse
Hi,
Unfortunately for you no, I made a swap with a brandnew one with the seller.

HELP ON getting Galaxy note 3 n900 unroot for receiving stock updates

guys,i rooted my note 3 n900 by cf-auto root but now i want to unroot my note 3 ...so that i can receive all sorts of official software updates from samsung......PLEASE HELP ME PLEASE....i'm stucked.and tell me can i fully unroot my note 3 by getting back knox warranty...is it possible? is chainfire working on the fix to get back knox warranty? i use an international n900 variant.HELP
As far as I understood, once you have triggered knox 0x1 or the counter for flashing, the OTAs won't be available any more.
I have the same thing. Checking for OTA updates works though, if you use something like wanam which can be setup to fool the phone into thinking that it's ok. I was able to download an update with SuperUser turned off (and reboot afterwards), but couldn't install.
So actually, I just check every now and then on the forums if there's an update and then just wait for a regular download via PC and flash with ODIN. Works quite well, and by the time downloads become available via PC, you'll also already know if there are glitches with newer updates, too. Takes about a day or two compared to the OTA.
help
Mikegrmn said:
As far as I understood, once you have triggered knox 0x1 or the counter for flashing, the OTAs won't be available any more.
I have the same thing. Checking for OTA updates works though, if you use something like wanam which can be setup to fool the phone into thinking that it's ok. I was able to download an update with SuperUser turned off (and reboot afterwards), but couldn't install.
So actually, I just check every now and then on the forums if there's an update and then just wait for a regular download via PC and flash with ODIN. Works quite well, and by the time downloads become available via PC, you'll also already know if there are glitches with newer updates, too. Takes about a day or two compared to the OTA.
Click to expand...
Click to collapse
Where can I get updates via pc...link please
Tawhidz13 said:
Where can I get updates via pc...link please
Click to expand...
Click to collapse
Sammobile.com/firmwares usually has the latest firmwares. If you prefer pre-rooted firmwares just search for it right here in the forum. Before you download and install any firmware though, check that you download the right one. The latest EU fw is N9005XXUDMUJ7. But you also have to check your CSC. What happens when this is wrong, I don't know. But you may get boot loops. Just use the forums search and read through CSC, ODIN and the latest fw name. You'll find all that you need. And with the latest CF-Autoroot, rooting your phone is just a mouse click away.
Updates are available via KIES on your PC if you have rooted your phone (you will lose root and have to re-reoot though), just cannot get OTA. - I updated my rooted MJ6 to MJ7 via KIES with no issues. (KNOX 0x1) - KIES will say something like " software update might not work because of modified phone" but mine worked fine. - or alternatively try sammobile.com and manually flash the firmware yourself.
As for your KNOX, no way back currently from 0x1..
radicalisto said:
Updates are available via KIES on your PC if you have rooted your phone (you will lose root and have to re-reoot though), just cannot get OTA. - I updated my rooted MJ6 to MJ7 via KIES with no issues. (KNOX 0x1) - KIES will say something like " software update might not work because of modified phone" but mine worked fine. - or alternatively try sammobile.com and manually flash the firmware yourself.
As for your KNOX, no way back currently from 0x1..
Click to expand...
Click to collapse
I tried Kies initially, too. But Kies just told me that I would have an unsupported phone, so I went ODIN.
If I am rooted with vroot, knox not tripped will unrooting in any way trip it?

Screen not working - Unroot for warranty

My Galaxy S4 just decided to show wavy lines on the screen instead of turning on - as far as I can tell the screen and digitiser are no longer working.
**I CANNOT SEE OR DO ANYTHING ON THE SCREEN**
I have a 4.2.2 i9505 UAMDE -Stock Rom- that is rooted.
I have never flashed any other firmware to it - just rooted it.
I have Kies access and backed up my phone. Kies prompted for a firmware upgrade when I plugged in the phone.
I want to return it to stock/unroot etc so Samsung will warranty the phone without fuss (it was not dropped, just stopped working).
Some questions:
Most important:
1. Is it possible to get the phone to a state that will be warranty-ready without having a screen?
2. Do I need to Triangle away if all I have done is rooted? If so, can I do this without a working screen?
3. What is the best way to return to stock? ODIN or should I just let Kies update to latest firmware? (If either will it be enough to satisfy the first question)
4. If Kies does the update will I need access to the screen to complete it?
Thanks in advance!
1. You can flash same firmware with ODin. It will delete root access, but app will stay, so you have to uninstall it through https://play.google.com/store
2. You don't need to, unless you've made a root through Oding flash?
3. Odin
4. No, but it will udpate it to 4.3 with KNOX?
mar10o said:
1. You can flash same firmware with ODin. It will delete root access, but app will stay, so you have to uninstall it through https://play.google.com/store
2. You don't need to, unless you've made a root through Oding flash?
3. Odin
4. No, but it will udpate it to 4.3 with KNOX?
Click to expand...
Click to collapse
Thanks for the quick reply.
1. not sure which 'app will stay' you mean?
2. Actually I cannot remember how I rooted - I will have to look this up again. Something tells me cf-autoroot and maybe ODIN... All I can remember it that I still have stock ROM just with root.
4. Agree that this might not be the best idea as I am trying to stay away from KNOX but I wonder if Samsung will automatically update to the latest ROM as part of the fix?
Kies is currently sitting on backing up "preparing" for ages and ages... hope it works in the end.
Looking back I suspect I used CF-autoroot which probably mean my counter has gone up.
Any way of resetting this without a screen?
I've managed to get some screen control using adb, screencast and teamviewer.
Triangle away says:
Counter: 0
Binary: Official
System: Official
I suspect the Official comes from the fact I was running Wanam Xposed and spoofing official.
One last question -
Given all that information I should just be able to flash
4.2.2 UAMDE Stock rom from sammobile with odin
and everything will be warranty-ready?
(will this wipe all my data and programs as well? - something I WANT to happen)
It will not wipe it. On the older devices like S3, there was a special ROM for cleaning purposes with PIT file, that was repartitioning your memory. Maybe there is something like that for S4?

cannot update s5 software with kies, help?

my galaxy s5 model number is sm-g900t, android version is 4.4.2, ..not sure what other info might help, but anyway, i cannot update the software/firmware over the air because the device is rooted through steps on here and its been rooted awhile now. so anyway, i downloaded the kies 3 from the samsung site, it says all im supposed to do is plug the phone in, a box is supposed to pop up showing an update is needed......well, the kies box does pop up, but all it shows is current firmware version and shows my internal and external storage availabilty, and so on.... no auto update thing came up. so in kies i went into tools up a t the top, i hit firmware upgrade and initialization, then a smaller box pops up saying---does not support initializing, so now what? nothing else i can do in kies except move pic files around and such. i need to update the software. any advice? i attached 2 pics.....pic 1 is the initial message when phone is plugged in, #2 is when i go into tools and hit ugrade
knight1701 said:
my galaxy s5 model number is sm-g900t, android version is 4.4.2
Click to expand...
Click to collapse
Samsung has now embedded a security flag called KNOX in it's later devices. Unfortunately after you flash a package/custom ROM or whatever with a different signature than Samsungs own it trips that KNOX flag.
When your KNOX flag is tripped you can no longer update your phone via official methods. It is just the way it is, and there is nothing to be done. Once KNOX flag is tripped, there is no way to "untrip" it, so you will never be able to update via KIES again.
Im not really sure whether flashing a stock lollipop rom via odin works when KNOX is tripped, i have never tried it, so you should wait for any other member for confirmation. As far as i know, it shouldn't be a problem.
What i can tell you, if you have the time, is that you flash a ROM that is compatible with 4.4.2 (Omega v13 or AllianceROM v5.6 etc) and then flash it's ROMs lollipop update after a full wipe. It is the only thing i personally am sure about (i have done it before).
I'm by no means an expert on the matter but I'm pretty sure that if you can't get the Ota due to being rooted, then updating vIA Kies isn't going to work either.
Go to settings> about device> status
scroll to bottom of list and respond here what it says under "device status" (it's gong to say either official, or custom).
If it says official, you could unroot, maybe check that the proper drivers are installed on your computer, and try once again to apply the update via kies.
If it says custom, then knox has been tripped and I cannot help further.
The biggest issue here is that if you take the OTA update you'll lose the option to root or downgrade so you should probably use TWRP to install a ROM that's pre-rooted rather than trying to get the OTA
Akalsemann said:
Samsung has now embedded a security flag called KNOX in it's later devices. Unfortunately after you flash a package/custom ROM or whatever with a different signature than Samsungs own it trips that KNOX flag.
When your KNOX flag is tripped you can no longer update your phone via official methods. It is just the way it is, and there is nothing to be done. Once KNOX flag is tripped, there is no way to "untrip" it, so you will never be able to update via KIES again.
Im not really sure whether flashing a stock lollipop rom via odin works when KNOX is tripped, i have never tried it, so you should wait for any other member for confirmation. As far as i know, it shouldn't be a problem.
What i can tell you, if you have the time, is that you flash a ROM that is compatible with 4.4.2 (Omega v13 or AllianceROM v5.6 etc) and then flash it's ROMs lollipop update after a full wipe. It is the only thing i personally am sure about (i have done it before).
Click to expand...
Click to collapse
well i hear what your saying, but on my other phone, same setup, rooted and all.......updated just fine---did it about a month ago...updated to android 5 from 4.4.2..just plugged in the phone and boom it did its thing............on this other phone though, daughters phone, it wont work
Swimguy14 said:
I'm by no means an expert on the matter but I'm pretty sure that if you can't get the Ota due to being rooted, then updating vIA Kies isn't going to work either.
Go to settings> about device> status
scroll to bottom of list and respond here what it says under "device status" (it's gong to say either official, or custom).
If it says official, you could unroot, maybe check that the proper drivers are installed on your computer, and try once again to apply the update via kies.
If it says custom, then knox has been tripped and I cannot help further.
The biggest issue here is that if you take the OTA update you'll lose the option to root or downgrade so you should probably use TWRP to install a ROM that's pre-rooted rather than trying to get the OTA
Click to expand...
Click to collapse
ok, on the phone in question, device status says--- custom, guess that ends that..........on my phone howerver, it says official which is why i guess i was able to update mine
just download a rom for your phone from sammobile and install with odin and your done

[GT-I9506] Need help resetting my device software status

So, a few months ago I decided to root my phone with towelroot to give a try on a few root applications, as i was curious, but after that, I decided to remove through supersu it as, even with supersu, was more of a vunerability since I wasn't really using it.
Fast foward a month, I attempted to update my software and was denied with the reason that my device was custom.
Some important info:
- I'm running Android Jelly Bean 4.3, that has never been updated.
- I've attempted a factory reset through the phones recovery mode and made no difference.
- My KNOX waranty value is 0x0, and I would like to keep it that way if possible.
- Phone is factory unlocked.
Also, I've though of using Odin to flash the firmware back, but then I read that there is a possible that KNOX warranty gets triggered, even with a samsung official rom, is this true or am I safe to use it?
My objective is to have my phone back to factory settings (this means wannan xposed is out of the question), in order to be able to update my phone and keep using it, and while there is a lot of similar threads around, most of them reffer to GT-I9505 and GT-I9500 and mine is GT-I9506, which leaves me in somewhat of a doubt wether I should follow those or not.
Thank you for your time.
Diaz_ said:
So, a few months ago I decided to root my phone with towelroot to give a try on a few root applications, as i was curious, but after that, I decided to remove through supersu it as, even with supersu, was more of a vunerability since I wasn't really using it.
Fast foward a month, I attempted to update my software and was denied with the reason that my device was custom.
Some important info:
- I'm running Android Jelly Bean 4.3, that has never been updated.
- I've attempted a factory reset through the phones recovery mode and made no difference.
- My KNOX waranty value is 0x0, and I would like to keep it that way if possible.
- Phone is factory unlocked.
Also, I've though of using Odin to flash the firmware back, but then I read that there is a possible that KNOX warranty gets triggered, even with a samsung official rom, is this true or am I safe to use it?
My objective is to have my phone back to factory settings (this means wannan xposed is out of the question), in order to be able to update my phone and keep using it, and while there is a lot of similar threads around, most of them reffer to GT-I9505 and GT-I9500 and mine is GT-I9506, which leaves me in somewhat of a doubt wether I should follow those or not.
Thank you for your time.
Click to expand...
Click to collapse
Flashing a stock rom trough Odin will NOT trip Knox. So just go ahead and flash the firmware you want.
Lennyz1988 said:
Flashing a stock rom trough Odin will NOT trip Knox. So just go ahead and flash the firmware you want.
Click to expand...
Click to collapse
Alright, I assume the proccess is about the same as on the other versions.
Also, should I flash 4.4.2 instead of 5.0.1? The reason I ask is due to this thread.
Update: I flashed 4.4.2 with Odin3 3.10, and it went smooth and knox is still safe, however, for some reason, so thank you Lennyz1988 for the reassurance .
However, I'm not able to update to 5.0.1 Lolipop through OTA, as attempting to update states that im fully up to date.
My phone is running as NL (T-Mobile), factory unlocked and due to my quick research, seems that there is no official OTA update for it. Is it correct or am I looking in the wrong place to update my phone?

Categories

Resources