So currently I'm rooted with the WebTop mod.
I'm the kind of person who likes to have directions that are exact and specific. So if somebody could write something up for me, that'd be great.
What I need to do is this:
1. Un-do webtop mod
2. Run script so I can keep root (kinda shakey on this one)
3. Update, I know how to do this
And anything else I might need to get the update and still keep root permissions on my phone.
Thanks alot.
just flash the SBF 1.26
Well thanks, ever though that wasn't exactly detailed.
What exactly would that do? Put me back to factory settings? Because I don't really want to do that, I'm sure there's an easier way.
To undo webtop mod:
If you are currently rooted and, like me, have no idea about adb, then download Root Explorer from the market. No it is not free, yes it is worth it.
Go to sdcard->webtop mod backup
take the .backup or .bak extension off all files leaving them .odex and .apk
Copy these files into the system/app folder.
Reboot.
Webtop mod undone.
As far as I know there is no way to keep root after the mod. Although I have not signed in since last night, so in 24 hours something may have changed.
Thanks alot for that, I'll try it out now, since I have Root Explorer.
And here's the root script: http://forum.xda-developers.com/showthread.php?t=1013931
I just have no idea what to do lol, so if somebody wants to explain it...
Notacop said:
To undo webtop mod:
If you are currently rooted and, like me, have no idea about adb, then download Root Explorer from the market. No it is not free, yes it is worth it.
Go to sdcard->webtop mod backup
take the .backup or .bak extension off all files leaving them .odex and .apk
Copy these files into the system/app folder.
Reboot.
Webtop mod undone.
As far as I know there is no way to keep root after the mod. Although I have not signed in since last night, so in 24 hours something may have changed.
Click to expand...
Click to collapse
Hmm. Actually I'm not sure which files to remove. Here's the ones that are in WebTop Mod Backup:
- DockProvider.apk.bak
- DockProvider.odex.bak
- DockService.apk.bak
- DockService.odex.bak
- PortalApp.apk.bak
- PortalApp.odex.bak
Notacop said:
To undo webtop mod:
If you are currently rooted and, like me, have no idea about adb, then download Root Explorer from the market. No it is not free, yes it is worth it.
Go to sdcard->webtop mod backup
take the .backup or .bak extension off all files leaving them .odex and .apk
Copy these files into the system/app folder.
Reboot.
Webtop mod undone.
As far as I know there is no way to keep root after the mod. Although I have not signed in since last night, so in 24 hours something may have changed.
Click to expand...
Click to collapse
Bump - unresolved.
Could someone help? I want to do this tonight.
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.
I'd like to block OTA updates - my very old Incredible had a way to do it either via a mod on a ROM or by removing some .apk file I believe.
Is there an .apk responsible for checking for new OTA updates that I can rename or remove?
Ideally it'd be reversible once it's known how the update affects a rooted phone. Really wish VZW would just allow you to pass on updates instead of forcing them on phones.
Also, not interested in going beyond adb root on this phone so ROMs aren't really an option, I actually think stock is fine. I'd be happy with the phone as is for the next two years until my next phone even.
I try not to delete or remove files but rather just rename them.
Disable OTA Update Notification
/system/etc/security/otacerts.zip
rename to otacerts.zip.bak and reboot.
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?
After rooting with Magisk, users of Moto G6 are faced with the “Stock Rom does not exist” error at the Restore Images step of Magisk’s OTA Upgrade Guide. However, the following suggestion was made in the discussion following issue #1870 on Magisk’s git-page:
The backups should be kept in /data (/data/stock_boot_<hash>.img.gz)
You could probably edit /sbin/.magisk/config to point to the backup you want by putting your <hash> after SHA1=
Click to expand...
Click to collapse
With Solid Explorer, I found different directories called /data in Root and in Internal Memory, but only the one in Root had a ./data/ subdirectory. Is that the one to which I should download the stock rom
ALI_RETAIL_9.0_PPSS29.118-15-11-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
which was posted in March, before the latest OTA release? Do I extract this zip, create an img.gz file from the .xml file and rename it stock_boot_<hash> before putting it there? Is <hash> blank-notation for any name that I give it, and which I then add after the “SHA1=” in /sbin/.magisk/config?
Finally, how do I edit the config file? I was able to get to it with Solid Explorer after checking the option to show hidden files in /sbin/. However, I couldn’t send this file to my computer by sharing it through email or messaging apps, as they all denied sending it. Apparently, it’s being blocked by anti-viruses. In this case, is there a safe way to transfer it to a computer, where I’ll be able to more comfortably edit it? Alternatively, if I just omit <hash> in naming stock_boot_.img.gz, can I leave config the way it is?
Best regards!