So i got a tab s 8.4 lte
rooted it
it disabled knox and tripped my knox warranty
then i installed kitkat sd fix
now i have undone the sd fix and unrooted my phone
but it didnt ask me to reenable knox
so will i get ota updates now or not
You can check by clicking 'update now'.
It says that the software on your device has been modified by an unauthorised way
Please visit the service centre
That means you can't.
I don't know whether knox bit is checked or some changes in the ROM. To make sure you could try to re-flash full stock ROM. But my bet would be, that you can't OTA with knox tipped.
So can anyone tell me how i can flash an incremental ota update via odin
or can i do so via TWRP
or is my last hope just flashing a full custom rom
just download the official firmware of your device and flash it with odin... after that if got any OTA update it will run. OTA only run with stock official firmware. no matter if you got knox 0x1 or not.
Just flashed TWRP
I think i'll flash a custom rom instead
BTW is your Selamba rom stable edan????????????
What does OTA require exactly? I am on stock ROM, rooted, skyhigh kernel. No OTA. Is it the kernel preventing OTA?
Instead of using Odin, you can as well use Kies, it does the update automatically.
But OTA is most convenient.
Pallavgarg10 said:
Just flashed TWRP
I think i'll flash a custom rom instead
BTW is your Selamba rom stable edan????????????
Click to expand...
Click to collapse
It just a basic rom. 1.0.2 is stable. Or try the new one by THEDEVIOUS1
Sent from my SM-T705 using Tapatalk
Pallavgarg10 said:
So can anyone tell me how i can flash an incremental ota update via odin
or can i do so via TWRP
or is my last hope just flashing a full custom rom
Click to expand...
Click to collapse
KIES. Don't forget KIES. We all hate it but it works when you want everything back to stock. I don't think the Knox bit alone will prevent you from getting OTA updates.
mhannigan said:
KIES. Don't forget KIES. We all hate it but it works when you want everything back to stock. I don't think the Knox bit alone will prevent you from getting OTA updates.
Click to expand...
Click to collapse
Apparently it does
Pallavgarg10 said:
So can anyone tell me how i can flash an incremental ota update via odin
or can i do so via TWRP
or is my last hope just flashing a full custom rom
Click to expand...
Click to collapse
It's always been my understanding from previous versions of tabs/Android that once you have installed a custom recovery, OTAs will fail. Download sure but fail to install.
pibach said:
What does OTA require exactly? I am on stock ROM, rooted, skyhigh kernel. No OTA. Is it the kernel preventing OTA?
Instead of using Odin, you can as well use Kies, it does the update automatically.
But OTA is most convenient.
Click to expand...
Click to collapse
Kernel will trip Knox, as well as flashing a custom rom or installing a custom recovery (safestrap is ok). A custom kernel or pretty much any customizations will stop ota updates unless you do them via Odin as suggested. If knox doesnt block ota, you can Odin to stock ncg, take ota flash back to NCG kernel to reroot on towelroot and then flash new official ota kernel to keep root while ota updated. Personally I went to ne9 and ran back to ncg.. Won't be flashing anything until android L. NE9 was worthless, just killed root.
Related
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all
I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
gaww said:
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
Click to expand...
Click to collapse
Yep DONT UPDATE IF YOU DONT WANT ANY CHANGES!
edit; I think there will be a patch soon enough though
zz1049 said:
Yep DONT UPDATE IF YOU DONT WANT ANY CHANGES!
edit; I think there will be a patch soon enough though
Click to expand...
Click to collapse
I would not think of "updating" and get stuck with KNOXed bootloader. Absent that, i do not see why reverting would be a problem, but I have read otherwise.
That was my reason for asking.
gaww said:
I would not think of "updating" and get stuck with KNOXed bootloader. Absent that, i do not see why reverting would be a problem, but I have read otherwise.
That was my reason for asking.
Click to expand...
Click to collapse
Reason being is that the boot loader does not permit loading the old version of android onto it. If you update and then tried to flash the old Raum 4.3 it will cause errors and will ask you to reinstall the firmware, which is basically just the recovery part. 4.3 will flash this part of the image but then the rest of it will have problems. A lot of custom ROMs have been out there that run on 4.3 kernels but are running 4.4 ROMs and these are really actually 4.3. In those cases you can easily revert to stock 4.3. However, if you have updated then through Samsung software it will update the boot loader and you will no longer be able to revert.
For AT&T it is available to river, or at least reflash 4.4. I'm sure this will be fixed in time however at this point there is a lock or warning that has not been cracked basically. (Knox counter etc,)
gaww said:
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
Click to expand...
Click to collapse
This is what I've read: if you update to official 4.4.2, you cannot flash back to official 4.3 in Odin. Likewise, if you updated to official 4.3, you cannot Odin back to official 4.2.2. If you try to, you'll soft brick. The Knox-secured bootloaders prevent Odin from successfully flashing a previous version.
Now, if you do this and therefore soft-brick, you need to pull the battery and re-enter Odin mode. Then you must Odin-flash a custom recovery (luckily there are some Odin-flashable recovery files out there). Then, after another battery pull, you need to manually boot into your custom recovery and flash a custom rom (or restore a Nandroid). This will save your soft brick.
What we don't know, because it hasn't been released yet, is if the official 4.4.2 tar file would successfully flash in Odin if you already have the 4.4.2 Knox bootloader.
My galaxy siii was rooted before kitkat was out, and I have been using it until now and have not yet update to KitKat yet because AT&T is not part of it any more.
How do I get KitKat on my phone? Do I have to unroot the phone and put it back into AT&T mode to download or what should I do?
this might help.
remember:READREADREAD
BACKUPBACKUPBACKUP
http://forum.xda-developers.com/showthread.php?t=1802160
good luck
err on the side of kindness
You will need to unroot your phone and have the stock recovery.
Thank you for both replies gentleman
audit13 said:
You will need to unroot your phone and have the stock recovery.
Click to expand...
Click to collapse
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Id recommend flashing the 4.3 firmware via Odin to begin with. Its starting to seem like a lot of people who even just have to unroot are having problems with the ota. I think Odin flashing stock 4.3 will give the best chance of a successful update.
mwrobe1 said:
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Click to expand...
Click to collapse
I am having this issue. I rooted on 4.3 and removed Google books and newsstand. I then uprooted and did a factory reset , so everything in download mode says "official" but the apps were still missing so I downloaded them from the play store. My question is will this let me get the OTA now or do I have to push the apps to the /system directory somehow? Also if I flash the 4.3 ODIN tar file, will it trip my warranty bit? It's at 0 right now and want to keep it that way until my warranty is up.
The firmware shouldn't trip the bit, but I can't promise that. Im sure its confirmed one way or the other in its thread though.
As for those apps, they'd have to be system apps, so just installing normally won't help. More importantly though, they would also need to be the same version that was originally built into the firmware. The apps you mentioned have seen many updates and using the current versions will not work.
I got the phone 2 weeks ago and it came with 4.3 installed on it. Would I be able to use the current version and just push them to /system/app with titanium backup? I am trying to get the OTA without tripping any warranty or security measures.
I have S4 with MDL bootloader, was running GE based roms...and now want to restore it to STOCK and upgrade to latest firmware. Giving it away to my father so want to make completely stock with ability to receive OTAs .
Last night flashed via Oden stock 4.2.2 (MDL) rom, modem, and restored counter to (0). Tried to upgrade from the phone to the latest firmware, but getting the error (Processing Failed). Installed Kies 2.x.x and it would not recognized the device. Please Help to install latest stock 4.4.4 rom with (0) counter
Is the error when it tries to update or when checking for updates?
when checking for updates from the phone it self, but Kies also fails to connect to the phone.
You may want to try again later. Also does your computer recognize it at all?
serio22 said:
You may want to try again later. Also does your computer recognize it at all?
Click to expand...
Click to collapse
Yes, I've installed sam. drivers ... Odin, MTP and PTP works fine... Bootloader shows Samsung Rom, (0) counter...
T1001 said:
Yes, I've installed sam. drivers ... Odin, MTP and PTP works fine... Bootloader shows Samsung Rom, (0) counter...
Click to expand...
Click to collapse
what baseband are you on?
serio22 said:
what baseband are you on?
Click to expand...
Click to collapse
MDL baseband
T1001 said:
MDL baseband
Click to expand...
Click to collapse
Hmm well not sure what the problem is then. Try to update to 4.3 via odin and then give the ota a try and see it'll work
serio22 said:
Hmm well not sure what the problem is then. Try to update to 4.3 via odin and then give the ota a try and see it'll work
Click to expand...
Click to collapse
What about bootloader? and setting the counter to 0? 4.3 will flash new bootloader with KNOX and then I'll never be able to restore to 100% stock, or I'm wrong?!
For your phone to be stock right now it would have to be on NK2 firmware. Nothing wrong with that.
Knox only matters for the first 12 months, after that it's your phone not Samsung's.
Pp.
T1001 said:
What about bootloader? and setting the counter to 0? 4.3 will flash new bootloader with KNOX and then I'll never be able to restore to 100% stock, or I'm wrong?!
Click to expand...
Click to collapse
As long as you don't root it or modify it in anyway, you'll always be 100 percent stock
PanchoPlanet said:
For your phone to be stock right now it would have to be on NK2 firmware. Nothing wrong with that.
Knox only matters for the first 12 months, after that it's your phone not Samsung's.
Pp.
Click to expand...
Click to collapse
If I flash latest firmware via Odin, will it get OTAs in the future?
Not if your rooted /custom recovery and debloated, as you remove all the T-Mobile and Samsung bloat you will not get any ota updates, ( I haven't in16 months ) . I run stock /debloated /rooted.
You can run stock rooted or find a stable custom rom to use.
Pp.
Fixed it.
Re flashed the firmware via Odin again, cleared cache and data before first boot and thats fixed it!
This is a public service announcement to save people headaches. RTFM. You cannot ever now, or in the past, take an OTA with a custom recovery. You must always have a stock recovery and system to do so. Period. If you do install a custom recovery, freeze the update center with Titanium, Rom Toolbox, or the like, so that you will remember you have a custom recovery and not accidentally take an update.
I hope this helps someone out there
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Grizzie said:
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Click to expand...
Click to collapse
.this is referring to stock software updates, unless it's updates of the rom, which you won't even receive if you're on a custom rom...to update a custom rom, you just download the updated version, or the OTA if the rom is so capable, and flash it in twrp like the first version you downloaded
Grizzie said:
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Click to expand...
Click to collapse
Wait for a flashable zip for TWRP. You can revert to stock to take an OTA. Being rooted is not a problem per se, it's the custom recovery and having non stock roms. In theory you could flash the stock recovery and bootloader and then take an OTA. However, not having stock system/apps could likely create havoc
In case you do happen to try and install it, here's a fix for your bootloops: http://forum.xda-developers.com/showthread.php?p=60117595