Related
When I updated to 4.2.1 thru OTA, I have a problem finding where my game's .obb files go!?? it used to be saved in sdcard/Android/obb before 4.2 update. I searched emulated/0/Android/obb but they are not there too!!!
No one to answer me
Try /storage/emulated/legacy/Android. If you activated multi-user, there may be a '0' in the path, but I don't know for sure because I never set up multi-user.
karimaelo said:
When I updated to 4.2.1 thru OTA, I have a problem finding where my game's .obb files go!?? it used to be saved in sdcard/Android/obb before 4.2 update. I searched emulated/0/Android/obb but they are not there too!!!
Click to expand...
Click to collapse
Try on the Root folder of the SDCARD. Mine has SDCARD/0 SDCARD/LEGACY "SDCARD/OBB" & SDCARD/.Android_Secure
Hello
I have received my 4.2.2 update notification, and without prompting me it has downloaded ota to my phone. I don't want to install the update yet frankly til I'm happy with all the kernel swapping etc I'll have to do.
So I want the notification and update file removed form my phone if possible. Does anyone know how to remove it?! Seen a lot of talk of cache/ etc. but not sure if they mean a folder location for the download or not. I have wiped my cache in recovery, but don't want to click on the update incase it does still find the file.
Anyone know what I can do?
Delete the zip file with root explorer
hp420 said:
Delete the zip file with root explorer
Click to expand...
Click to collapse
I can't seem to find the file, that's whats annoying me at the minute ha ha.
Just read that the new version of kitkat will be out soon. For Note3 Verizon.
I have a rooted phone. My main concern is not to let the firmware automatically download. How do I stop it from downloading
Do you have a link to the article?
Galaxy Note 3
susieq29 said:
Just read that the new version of kitkat will be out today or tomorrow. For Note3 Verizon.
I have a rooted phone. If I want the Verzion version do I need to unroot to download it when it comes out?
Do I need to stop it from automatically downloading on my phone so nothings happens?
Can I go into Kies and get the new software and install it manually?
What do you suggest. My main concern is not to let it download automatically and do any damage to my phone.
Click to expand...
Click to collapse
IS this a trusted source? Its hard to believe Verizon will be pushing out an update anytime soon for this device.
I guess it remains to be seen!
Sent from my SM-P600 using XDA Premium 4 mobile app
susieq29 said:
Just read that the new version of kitkat will be out today or tomorrow. For Note3 Verizon.
I have a rooted phone. If I want the Verzion version do I need to unroot to download it when it comes out?
Do I need to stop it from automatically downloading on my phone so nothings happens?
Can I go into Kies and get the new software and install it manually?
What do you suggest. My main concern is not to let it download automatically and do any damage to my phone.
Click to expand...
Click to collapse
It can't install automatically without your permission (shouldn't).
My suggestion to get the update is Odin back to 100% full stock image. Then you can take whatever OTA is at your hearts desire. Then you know everything is so fresh, so clean :good:
Then we just wait for word on root ?
Sent from my SM-N900V using xda app-developers app
kickenwing13 said:
Then we just wait for word on root ?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
That's what I'm going to do. I hear a lot of interesting things about 4.4.2 - how it breaks SD Card access etc... I am VERY happy with 4.3 with the rom I've chosen and will happily await a Clean Rom 4.4 before I even think about 4.4.
I have 4.4.2 on my Nexus 7 2013 tablet and it's good - hopefully it'll mean even better battery life. Pretty happy with the 2x battery life increase after I've rooted. Here's to hoping for more in 4.4.2.
Fyi - googled and I can't find anything about 4.4 coming to Note 3 via Verizon. Back when I had Droid 1 and HTC Thunderbolt us rooters got ICS way before it came out to the carriers. lol.
OP, do you have a link?
I disabled both Knox and the OTA update in MJE by using a root file explorer (Solid Explorer) and changing file permissions to 0000 ("---------") of a couple .apk/.odex files in /system/app (followed by rebooting) :
ContainerAgent{.apk,.odex}
ContainerEventsRelayManager{.apk,.odex}
KLMSAgent{.apk,.odex}
KnoxAgent{.apk,.odex}
KnoxAttestationAgent{.apk,.odex}
KnoxStore{.apk,.odex}
SDM{.apk,.odex}
FWUpgrade{.apk,.odex}
LocalFOTA.apk
This allows them to be restored at any time by chmod'ing them back to mode 0644 ("-rw-r--r--"). I suppose this is similar to "freezing" in TiBu. The first group are Knox-related and last three are involved in the OTA, but it might be sufficient to only disable the SDM{.apk,.odex} files.
cheers
how do I disable SDM{.apk,.odex} files. using root file explorer. I found the files I do not see anyway to disable them?
susieq29 said:
how do I disable SDM{.apk,.odex} files. using root file explorer. I found the files I do not see anyway to disable them?
Click to expand...
Click to collapse
Rename them to .bak files.
If I move the file to my sd card would that do the same thing as disabling them? Would it mess up my OS not to have it in my system file.
I do not see how to rename any file? Please explain the process of renaming.
susieq29 said:
how do I disable SDM{.apk,.odex} files. using root file explorer. I found the files I do not see anyway to disable them?
Click to expand...
Click to collapse
I haven't used root explorer, but I know that both Solid Explorer and ES File Manager have a way to change the file permissions mode - usually by press-and-hold on the file name, and then select "Properties" or some such from the pop-up menu.
You can also rename them if you want as suggested above (but obviously don't delete the {.apk | .odex} suffix so you won't get the two of them confused) - for instance Foo.apk -> Foo.apk.bak and Foo.odex -> Foo.odex.bak
[Edit] Also: Some root-aware file explorers make you manually remount /system in rw mode before you do anything, and some take care of it for you. If your permission changes / renaming operations fail, it's because of that. (Solid explorer just does it for you).
susieq29 said:
If I move the file to my sd card would that do the same thing as disabling them? Would it mess up my OS not to have it in my system file.
I do not see how to rename any file? Please explain the process of renaming.
Click to expand...
Click to collapse
Usually there is a menu in your file explorer which is brought up by long-pressing on an individual file name. I would recommend you leave the files in place and either rename them or make them unreadable (mode 0000) - moving them to the SD card and back will destroy the SElinux extended attributes of the files (if any). Then a couple months from now you won't need to remember where they are. They won't do any harm just sitting there.
Do I take out work apk and put in bak instead?
Got it thanks
susieq29 said:
If I move the file to my sd card would that do the same thing as disabling them? Would it mess up my OS not to have it in my system file.
I do not see how to rename any file? Please explain the process of renaming.
Click to expand...
Click to collapse
If you have root you can download fx file manager and the root add on from the play store or a similar root file manager. This will allow you to rename the files you need. You can move or delete them if you want. All the custom ROMs remove them without issue. Another option would be to purchase Titanium Backup Pro and freeze the apps with that. That is my preferred method with a stock rooted rom because all you have to do is unfreeze them and then unroot to take the OTA. With that in mind I would heed the advice of others and stay away from KitKat until a root method is confirmed if you value having root access.
Edit @bftb0 beat me to the answer when I was typing...
Just changed it and the app became a blank. When I put back the app and took away the bak the app did not appear again it is still a blank what do I do to get it back in system tray. Right now it is a blank page?
Misterxtc said:
With that in mind I would heed the advice of others and stay away from KitKat until a root method is confirmed if you value having root access.
Click to expand...
Click to collapse
+1
There will be plenty of lemmings that rush to the sea, afraid that they are going to miss something by not downloading an update on day one.
So, wait a week or two to see if any of them make it back to shore with their root privileges still intact. Their pain will be your gain. You'll also have the benefit of reading review articles on-line that will tell you if there is anything compelling in the update; my guess is that your phone already works quite well.
.
---------- Post added at 02:38 PM ---------- Previous post was at 02:31 PM ----------
susieq29 said:
Just changed it and the app became a blank. When I put back the app and took away the bak the app did not appear again it is still a blank what do I do to get it back in system tray. Right now it is a blank page?
Click to expand...
Click to collapse
Extremely confusing and vague language "changed it", "the app became a blank". also "system tray" and "put back". Huh?
Don't use pronouns such as "it". Nobody knows which "it" you are talking about.
It is possible that your file browser needs to "refresh" it's listing after a file name change. Sometimes file managers have an explicit "refresh" in their menu, or in other cases, you just visit a different folder in the file manger and then return back to (e.g.) /system/app folder to get the refresh to occur.
Hopefully all you are doing is manipulating file names.
Titanium will not work with Note 3. It actually semi bricked my phone. I was told not to Install it. The app whose name I changed then changed back is still there the original icon is just not there. I think everything is OK but got nervous not seeing the icom
I think the icon just disappeared. I first changed the name as you suggested adding bak. The icon disappeared but it showed a blank page icon.Then I wanted to make sure I could put it back so I removed the bak. After I removed the bak then rebooted. The icon never appeared again? When I open file manager and look at it the symbol is a question mark.
bftb0 said:
+1
There will be plenty of lemmings that rush to the sea, afraid that they are going to miss something by not downloading an update on day one.
So, wait a week or two to see if any of them make it back to shore with their root privileges still intact. Their pain will be your gain. You'll also have the benefit of reading review articles on-line that will tell you if there is anything compelling in the update; my guess is that your phone already works quite well.
.
Click to expand...
Click to collapse
I learned my lesson on my last phone. It was a S3 with an unlocked bootloader. I HAD to get the update despite the warnings not to. Within 10 minutes after that I tripped knox trying to get root and the wifi stopped working. That mistake cost me $400.00 for the phone N3 I have now. Verizon was "kind" enough to give me $300.00 off any new phone despite my mistake. No more going down that road for me. Yes, I am quite happy with this phone, even with the locked bootloader.
---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------
susieq29 said:
Titanium will not work with Note 3. It actually semi bricked my phone. I was told not to Install it. The app whose name I changed then changed back is still there the original icon is just not there. I think everything is OK but got nervous not seeing the icom
Click to expand...
Click to collapse
Trust me it works fine and won't brick your phone if you use it properly. At worst you would have to Odin back to stock if you deleted important files by mistake.
I don't think anything is wrong with the system. It is OK to have a ? mark instead of the icon right?
I'm with T-Mobile if that helps or changes anything, running 4.2.2. Now, I've gotten my phone to stop bugging me to install the OTA update. But the problem is the OTA update is still downloading in the background, it's just that I'm not being bugged by my phone to update it (i.e. there's no icon showing up in the notification bar). It becomes a sort of "silent update." So why is this a problem for me?
Because I'm on T-Mobile's cheapest plan which is the 500mb data plan. Each time the OTA downloads it eats up 155mb. And twice already this billing cycle it's done it, so that's 310mb of data wasted.
There are posts saying to use Titanium Backup Pro and freezing an app called Software Update MUC, and another post referring to the file as Software Update 2.3.0.5, but on my phone (using TB Pro) there's no file starting with "Software" anything.
So how do I stop my phone from downloading the OTA all together? Please help. Thanks.
Just install the update, that will make it stop for good
Sent from my LG-D801 using Tapatalk
Sorry, forgot to mention doing that won't work. For some reason my phone doesn't properly install OTA updates. I don't mind being stuck on 4.2.2. I just want the OTA downloads to stop in the first place.
Give this a try...
If rooted, use a file manager like Root Explorer, go to System/Etc/Security, (mount R/W) and rename otacerts.zip to otacerts.zip.bak
Reboot phone.
LordLugard said:
Give this a try...
If rooted, use a file manager like Root Explorer, go to System/Etc/Security, (mount R/W) and rename otacerts.zip to otacerts.zip.bak
Reboot phone.
Click to expand...
Click to collapse
I've done that already. I renamed the file to otacerts.zip.back (instead of .bak). I assume that doesn't make any difference. I believe renaming the file is what is causing my phone to not show the OTA icon in the notification bar. But as I said, the issue for me is that my phone is still downloading the update itself.
Any other ideas?
hydra1 said:
I've done that already. I renamed the file to otacerts.zip.back (instead of .bak). I assume that doesn't make any difference. I believe renaming the file is what is causing my phone to not show the OTA icon in the notification bar. But as I said, the issue for me is that my phone is still downloading the update itself.
Any other ideas?
Click to expand...
Click to collapse
what I've done is in system/app look for lgfota.apk/odex and renamed them to .bak and reboot and no more updates
XxZombiePikachu said:
what I've done is in system/app look for lgfota.apk/odex and renamed them to .bak and reboot and no more updates
Click to expand...
Click to collapse
I don't have that file in my system/app folder. What's wrong with my phone?????
On my phone, the file listed that comes before where lgfota.apk/odex should appear is LGEIME_THEME_BLACK.odex, and the file after that file is LGGallery.apk.
hydra1 said:
I don't have that file in my system/app folder. What's wrong with my phone?????
On my phone, the file listed that comes before where lgfota.apk/odex should appear is LGEIME_THEME_BLACK.odex, and the file after that file is LGGallery.apk.
Click to expand...
Click to collapse
you can check in the system/priv-app; that's very odd for it not to be in system/app are you on stock rom/have you removed any bloat
XxZombiePikachu said:
you can check in the system/priv-app; that's very odd for it not to be in system/app are you on stock rom/have you removed any bloat
Click to expand...
Click to collapse
I don't have a system/priv-app folder, either. I'm on stock rom, but I removed as much bloat as I can, including certain apps I find no use for (e.g. double-tap, voice command, etc). Maybe this will help: I used Root Explorer's search feature and searched for "fota", and here's what I think are the most "relevant" results:
/lgdms.fota.rc
/lgdms.fota_update.rc
/etc/fota
/etc/permissions/com.lge.fota.xml
/system/framework/com.lge.fota.jar
/system/framework/com.lge.fota.odex
Does this help? Anyone?
hydra1 said:
I don't have a system/priv-app folder, either. I'm on stock rom, but I removed as much bloat as I can, including certain apps I find no use for (e.g. double-tap, voice command, etc). Maybe this will help: I used Root Explorer's search feature and searched for "fota", and here's what I think are the most "relevant" results:
/lgdms.fota.rc
/lgdms.fota_update.rc
/etc/fota
/etc/permissions/com.lge.fota.xml
/system/framework/com.lge.fota.jar
/system/framework/com.lge.fota.odex
Does this help? Anyone?
Click to expand...
Click to collapse
Did you got any solution ?
I also got the same issue. Sprint here. I have renamed all files like otacerts.zip & lgfota.apk/odex, still it downloads the damn update.
cacerts.bks updated 12-6-20
When the original search was on to repair the aging cacerts.bks file in order to get the Kindle app working again, one of the things I came across was a remark from a fellow who had located a Honeycomb ROM (Android 3.2...last stop before the format of the security certificate storage was changed) and copied the cacerts.bks file from it to his Android 2.2 device which was having problems with websites, etc.
I still can't get the method described by @tshoulihane in this thread to work for me. But his edited cacerts.bks file works really well in solving the problem.
Yesterday I managed to locate a CM 7 ROM (Honeycomb). It contains a largish cacerts.bks file (compared to ours) with 127 certificates, 17 of which have expired. These seem to be mostly for central/eastern European and Asian entities, so perhaps not that critical. Well, it's only 10 years old
It has worked for me with the Kindle app and perhaps will help with some of the websites that complain about a secure connection even though I have enabled TLS 1.2 in Opera Mobile. More testing is needed there.
For anyone who wants to try it out, it is attached below. To use, rename your current cacerts.bks file (that's in /system/etc/security) to cacerts.bks.bak or similar. Then move the new file (unzip) into the same place. Check permissions. They should be rw-r-r. Reboot.
This looks great... though when I tried to rename and copy the new cacerts file, I am getting blocked due to the lack of root permissions.
I'm running the 1.2.1 tweaked/modded rom so I thought it wouldn't be an issue. I also tracked down the supersu3.1.3 apk and sideloaded it, but it didn't help either. Wondering if you had any ideas?
xrayd2 said:
This looks great... though when I tried to rename and copy the new cacerts file, I am getting blocked due to the lack of root permissions.
I'm running the 1.2.1 tweaked/modded rom so I thought it wouldn't be an issue. I also tracked down the supersu3.1.3 apk and sideloaded it, but it didn't help either. Wondering if you had any ideas?
Click to expand...
Click to collapse
So was your SU app missing? Or did your file manager just not have root access?
Hard to know where to start. From my experience, the best-behaving SU for the NST/G is the one that comes with NookManager (attached below). It's old and the binaries are probably out of date, but you don't need anything better for the device.
You can try removing the one you have now, reboot, and install the one below. Then check that your file manager has root acccess. In ES File Explorer, for example, you have to go into settings and tick the selection for root access. It's not automatic. And even with that, you have to tick an additional box to mount /system as rw while you're working in it.
At one time the superuser app was included -- but is no longer linked, and I had overlooked it after initially flashing the rom.
Unfortunately, the su app you provided also doesn't work. When I try to delete the old cacerts.blk it looks like it's doing something, but then the file still remains. If I instead try to rename the file, I get "operation failed".
I tried to delete or rename using an app called "root browser", and also the file manager in "super manager" suite. When I try to enable the root explorer function in ES file manager , I get "sorry, test failed. This feature cannot run on your device."
When I go under Device info, the ROM name does indeed say "Tweaked Modded ROM". I assume this should mean it's rooted but I'll have to dig deeper.
I appreciate your help though!
xrayd2 said:
When I go under Device info, the ROM name does indeed say "Tweaked Modded ROM". I assume this should mean it's rooted but I'll have to dig deeper.
Click to expand...
Click to collapse
Mmm.... so the ROM came "rooted"? I've attached a root check app which I've tried on my NST. This should answer the question of root.
If root has been lost somehow, it might be possible to salvage what you have by running NookManager. If you don't want the various additions like Relaunch, you can remove those apps from the data/app folder once you've written the card and then make the other needed changes as described here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
Or, you could just use NM as-is and uninstall unwanted material afterwards. The important thing is root and a functioning SU.
Okay... turns out my device was NOT rooted after all; I had assumed the binaries were already installed. Fortunately, I was able to find a superSU 0.93 binary and root through CWM. I replaced cacerts.blk with yours, and now the kindle app works! At first I had difficulty logging in, but turns out Amazon was emailing me a one time password after every attempt. After entering the OTP I am now up and running.
My next issue is getting Pocket working -- I installed Read it Later 1.0.1 but it's not syncing.
Thanks for the link to your other post. I will sideload the apk's you recommended.
xrayd2 said:
My next issue is getting Pocket working -- I installed Read it Later 1.0.1 but it's not syncing.
Click to expand...
Click to collapse
Might not be possible. Chatter here: https://forum.xda-developers.com/showthread.php?t=1604661&page=2 goes back to 2013.
I found reference to a functioning version in 9/2016. Had hoped it was a cacerts issue but maybe pocket changed their api.
https://forum.xda-developers.com/showpost.php?p=68600731&postcount=54
Would this be what's causing my Nook to not load certain https sites?
I can get to gmail fine, but I can't for the life of me load the todoist website
Tried loading your cacerts.bks, doesn't seem like it changed anything
I had no problem getting the Todoist home page. Logging in may be another matter.
Are you using Opera Mobile and did you make the settings change for TLS 1.2?