Help. OTA fails. What am I missing?

TMFGO45

Senior Member
Dec 23, 2010
192
21
0
I've been on MJE for a while, and I'm ready to OTA to the newest. So far I have completely unrooted, uninstalled xposed, and uninstalled safestrap recovery and when I reboot it still shows "custom." The only thing that remains is my modded framework-res.apk that unlocked tethering. I imagine this is the culprit? If it is, where can I find an original to put back in /system/framework? I googled with no success.

Sent from my SM-N900V using Tapatalk
 

TMFGO45

Senior Member
Dec 23, 2010
192
21
0
Do you know how to use odin? I can host up the 2 files if you want bone stock no root.
Yes I know how to use Odin but that isn't what I want to do. I just want to replace that one file so everything is stock and the custom indicator will go away, and then take the OTA.

Sent from my SM-N900V using Tapatalk
 

bmwh0r3

Senior Member
Apr 17, 2014
1,131
521
143
Millerstown, PA
The two files I have are from sammobile. You odin them and bam, youre up to date.

---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------


Was getting ready to redo my phone. I messed something up flashing themes.

---------- Post added at 09:21 PM ---------- Previous post was at 09:21 PM ----------

Dang tapatalk inverting images...
 

TMFGO45

Senior Member
Dec 23, 2010
192
21
0
The two files I have are from sammobile. You odin them and bam, youre up to date.

---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------


Was getting ready to redo my phone. I messed something up flashing themes.

---------- Post added at 09:21 PM ---------- Previous post was at 09:21 PM ----------

Dang tapatalk inverting images...
I honestly do know how to Odin all the way to the newest firmware. I'm just not interested in starting fresh again. I'd rather just OTA.

Sent from my SM-N900V using Tapatalk
 

bftb0

Senior Member
Feb 5, 2010
2,594
1,040
0
Can I pull the file I want out of a .tar? Using 7zip or Root Explorer even?
Yes you can. (Get individual files out of an Odin tarball)

In addition to getting the file back in place, make sure to set its ownership and permission modes correctly, and also inspect (ls -Z) and possibly reset the SElinux extended attributes (chcon, resetcon). Using Win-doze for unpacking tarballs will drop those attributes, increasing the odds you will get something wrong if you don't pay attention. There may also be file locking issues if you try this stuff during a full boot (instead of via safestrap recovery)

As you are finding out, OTAs are meant for 100% stock devices - they are differential patch sets, not full releases.

Worse yet, the diligent file-by-file checks that the OTA performs prior to starting the patching process halts on the first error. So you might have multiple problems beyond the framework file that you are unaware of. (You should be looking in /cache/recovery/*log* after a failed OTA to see what went wrong, BTW)

I haven't seen a detailed description of how the "attribution" processes (that can cause the "Custom" flag to be tripped) work, but there is a chance that only minor changes in the /system mount point could cause the attribution trip... meaning that there is a possibility that you will be able to put everything back & successfully take the OTA... and *still* have "Custom" show up on boot.

good luck
 

TMFGO45

Senior Member
Dec 23, 2010
192
21
0
Yes you can. (Get individual files out of an Odin tarball)

In addition to getting the file back in place, make sure to set its ownership and permission modes correctly, and also inspect (ls -Z) and possibly reset the SElinux extended attributes (chcon, resetcon). Using Win-doze for unpacking tarballs will drop those attributes, increasing the odds you will get something wrong if you don't pay attention. There may also be file locking issues if you try this stuff during a full boot (instead of via safestrap recovery)

As you are finding out, OTAs are meant for 100% stock devices - they are differential patch sets, not full releases.

Worse yet, the diligent file-by-file checks that the OTA performs prior to starting the patching process halts on the first error. So you might have multiple problems beyond the framework file that you are unaware of. (You should be looking in /cache/recovery/*log* after a failed OTA to see what went wrong, BTW)

I haven't seen a detailed description of how the "attribution" processes (that can cause the "Custom" flag to be tripped) work, but there is a chance that only minor changes in the /system mount point could cause the attribution trip... meaning that there is a possibility that you will be able to put everything back & successfully take the OTA... and *still* have "Custom" show up on boot.

good luck
Thanks for the response. I think I'm giving up on OTA hopes and will probably suck it up and start fresh. I managed the framework-res.apk. Custom icon still shows. I'm just going to Odin the newest OS version and instead of modifying anything I'm just going to use xposed exclusively. The only other thing I remember modifying is a file to get the Wifi Hotspot toggle in the drop down bar. Oh well.

Sent from my SM-N900V using Tapatalk
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone