OTA rootkeeper reports that I have root permission granted (all 5 status are checked). Titanium Backup reports that it has been granted superuser permissions.
I can not get back to my machine that has all my rooting software installed until after the holidays. I need to prevent the 6.2.1 OTA update from breaking root. I read that you all are having success doing this by either renaming OTASilentInstall.apk to OTASilentInstall.bak or freezing the app with Titanium Backup. I have tried both now with no success.
I used File Explorer ES to navigate to /system/apps where I found OTASilentInstall.bak and tried to perform the rename operation, but it reported back: operation failed. I launched Titanium Backup and navigated to OTASilentInstall and selected it, but I do not see any option to "freeze" this app. I would rather rename the .apk to .bak but either solution would be great right now so that I can turn my wireless back on.
Can someone tell me how to rename the file (or save an edited hosts file for that matter) without tethering to ADB? How do I "freeze" OTASilentInstall using Titanium Backup?
gruuvin said:
I used File Explorer ES to navigate to /system/apps where I found OTASilentInstall.bak and tried to perform the rename operation, but it reported back: operation failed.
Click to expand...
Click to collapse
Have you enabled 'root mode' in ES File Explorer settings? You must make sure that ES has root permissions. And also make sure that read/write permission is enabled for the folder/file where OTASilentInstall.apk is located. You can change this with ES as well if you've completed the first step.
hachiueno said:
Have you enabled 'root mode' in ES File Explorer settings? You must make sure that ES has root permissions. And also make sure that read/write permission is enabled for the folder/file where OTASilentInstall.apk is located. You can change this with ES as well if you've completed the first step.
Click to expand...
Click to collapse
That was it! Duh -- noob mistake! Thank you very much! For some reason I thought it was a 'Root Explorer' by default and I had given it these permissions on install, and then never thought it was settings switchable!
I had to enable 'Root Explorer' and then subsequently enable 'mount file system' (as writable) in ES File Explorer settings.
You're very welcome! Glad it worked out for you!
It appears that freezing/renaming the otasilentinstall will not prevent the auto update to 6.2.1.
I'm pretty sure that the only way that this is working is not because of OTARootkeeper which doesn't stop the update at all, but rather the fact that the OP is has not registered their Kindle Fire. You don't get the update if your device is not registered.
In that case, you don't need to do anything as you won't get pushed (or pulled as it might actually be the case) the update.
cmbeid said:
It appears that freezing/renaming the otasilentinstall will not prevent the auto update to 6.2.1.
Click to expand...
Click to collapse
Yes it does. I'm still keeping my wifi off.
Amazon devs aren't daft. I bet they watch these forums too!
gruuvin said:
Yes it does. I'm still keeping my wifi off.
Click to expand...
Click to collapse
Oh no it doesn't....
I did everything that was advised (including the above) and I still got the update and lost root.
bus_ter said:
Oh no it doesn't....
I did everything that was advised (including the above) and I still got the update and lost root.
Click to expand...
Click to collapse
Sorry, I meant yes it does appear that way (our methods don't work).
Related
I rooted my a500 successfully and have super user access. problem is, I still can't rename system apps or uninstall them. I tried using variety of file explorers including root explorer. any suggestions??
anybody? this is driving me nuts
jaya500 said:
anybody? this is driving me nuts
Click to expand...
Click to collapse
Get Titanium Backup and you can uninstall anything on the device. Becareful what you get rid of though.
if you want to give root explorer a shot again, when in the folder there should be a button up top that says "Mount R/W" ... press it, and it should change to "Mount R/O" when its showing mount r/o it means your folder is read/write enabled so at that point you should be able to change / delete / whatever you want on that folder.
give it a whirl, i suspect that was your issue. if not, then give titanium a shot but be careful either way
Hogmeister said:
if you want to give root explorer a shot again, when in the folder there should be a button up top that says "Mount R/W" ... press it, and it should change to "Mount R/O" when its showing mount r/o it means your folder is read/write enabled so at that point you should be able to change / delete / whatever you want on that folder.
give it a whirl, i suspect that was your issue. if not, then give titanium a shot but be careful either way
Click to expand...
Click to collapse
I used root explorer. It is stuck on r/o. I click r/w and no change. I used titanium backup and phone.apk wasn't listed. I really want to fix this battery drain
"Get Titanium Backup and you can uninstall anything on the device. Becareful what you get rid of though."
Does anybody have good suggestions for what apps can safely be removed?
If you don't have busybox installed a lot of "root" apps will fail to operate, since you haven't mentioned it, it is the first thing that springs to my mind...
jaya500 said:
I used root explorer. It is stuck on r/o. I click r/w and no change. I used titanium backup and phone.apk wasn't listed. I really want to fix this battery drain
Click to expand...
Click to collapse
Check superuser applist and see if root explorer is listed
If not, then maybe you denied root access
Alejandrissimo said:
Check superuser applist and see if root explorer is listed
If not, then maybe you denied root access
Click to expand...
Click to collapse
1) You have not actually rooted the device -or-
2) Go to the superuser app and check the deny app list
3) Don't delete system app, instead, rename them is better
Hi,
If your like me and you have had some problems with android market on your Kindle Fire (yes,I got one for christmas and its already rooted ) by following a guide with Vending.apk and though you can browse the market, it is stuck on Starting Download, I have found a solution to the problem... All you need to do is get a new file:bit.ly/tlWjSn
This file is simply an updated version to the Vendor.apk other tutorials provide.
All you do is the following(presuming you have rooted, got root explorer and GO launcher):
1.Copy the file to kindle at an easy to access location.
2.Long-Hold the file and tap move.
3.Navigate to / then system then app.
4.Set it to R/W mount (top left)
5.Paste the file.
6.Set the permissions like all other files(tick first 2 in first row, first 1 in second row and first 1 in third row then tap ok)
7.Reboot the device
8.Go onto GO launcher and add it to the screen (tap the list thing bottom middle of the screen,then tap Add. then select Application followed by Market)
9.Done! Enjoy!
Not sure if I should start a new thread or not.
I'm rooted and have SU. I have confirmed this by running Titainium Backup.
Market stopped working after the latest Kindle update. After I re-rooted, I tried re-installing vender.apk, but it still crashes upon launching it. Also, I am running Go Launcher EX.
When I browse folders while connected to a computer (using Win7), the system folder is hidden.
I never installed Root Explorer on the Fire. Is there a way for me to download and install it directly, or will I need to side load it? I assume if it's in the Market I'll need to side load.
leebo said:
Not sure if I should start a new thread or not.
I'm rooted and have SU. I have confirmed this by running Titainium Backup.
Market stopped working after the latest Kindle update. After I re-rooted, I tried re-installing vender.apk, but it still crashes upon launching it. Also, I am running Go Launcher EX.
When I browse folders while connected to a computer (using Win7), the system folder is hidden.
I never installed Root Explorer on the Fire. Is there a way for me to download and install it directly, or will I need to side load it? I assume if it's in the Market I'll need to side load.
Click to expand...
Click to collapse
Unfortunately you will as far as I know, but for $3.99, it is VERY useful when rooting or installing app's. market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en
Check it out. If you run into anymore problems feel free to PM me as it's easier
Hello guys, I have a little question related to market app that maybe has been already answered so I won't start a new thread.
I have my KF with 6.2.1 rooted and with the full android market installed (EX launcher and so on).
Usually the market works fine, but I always get errors ( process com.android.vending has stopped unexpectedly) and consequent force closes even if I can download stuff and apps. Basically, it happens whenever the market takes an action.
Is it a known issue or ir it "normal" ?
Thank you all in advance.
For me, I am having problems copying the Vending.apk to /system/app folder. I follow the steps in that tutorial but when I paste the.apk in the folder nothing happens. Help??
Got it rooted last night, and I'm using file expert since my cheap ass doesn't want to buy root explorer.
sengokubattosai said:
For me, I am having problems copying the Vending.apk to /system/app folder. I follow the steps in that tutorial but when I paste the.apk in the folder nothing happens. Help??
Got it rooted last night, and I'm using file expert since my cheap ass doesn't want to buy root explorer.
Click to expand...
Click to collapse
I'm afraid that without Root Explorer you can't change the /system/app folder permissions from R/O to R/W, therefore you can't paste anything in that folder.
Chiwaz said:
I'm afraid that without Root Explorer you can't change the /system/app folder permissions from R/O to R/W, therefore you can't paste anything in that folder.
Click to expand...
Click to collapse
File expert gives you that option too though.
if ur rooted but it wont paste or read and write in root explorer then ur su wasnt pushed properly in ur root process! When i rooted my kindle i deleted my old su and did the whole root process from scratch when i got the new root process. The whole thing went smooth and su showed up in apps when done but it wasnt totally rooted as i couldnt read or write in root explorer. Jcase told me that when the adb command for pushing the su wasnt done right thats what happens. he fixed it for me, great guy.
that was me though
Hi!
I'm trying to enable Ad Hoc mode on an Acer A500 running OTA ICS. I installed the Acer USB drivers; rooted it with blackthund3r_ICS_Root 6.0; checked it with Root Checker Basic; installed ADB on my Win7 PC; and checked that "ADB devices" reponds with a device ID; and obtained the WPA_supplicant file mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1625962
Every time I try to copy the new WPA_supplicant file to /system/bin, it fails. Also, copying WPA_supplicant with Root Explorer fails, even with the partition mounted RW.
Help! What am I missing?
TIA.
tlyonstlyons said:
Hi!
I'm trying to enable Ad Hoc mode on an Acer A500 running OTA ICS. I installed the Acer USB drivers; rooted it with blackthund3r_ICS_Root 6.0; checked it with Root Checker Basic; installed ADB on my Win7 PC; and checked that "ADB devices" reponds with a device ID; and obtained the WPA_supplicant file mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1625962
Every time I try to copy the new WPA_supplicant file to /system/bin, it fails. Also, copying WPA_supplicant with Root Explorer fails, even with the partition mounted RW.
Help! What am I missing?TIA.
Click to expand...
Click to collapse
You're not missing anything. The root method, does not give you true 100% System R-W access. Not with the stock bootloader. What you can try,
Copy your wpa file to the internal memory (remember where it is) (also long press and select copy)
Then run the included app "a500 Remounter" and select the System R-W option. (this was installed when you rooted) Then quickly go to your file manager, and set /System to R-W and try to paste your wpa file there.
You;ll have to play with this to get it going. Might have to do it a couple of times. This was a big pain, as I had to be very quick when doing things, as the R-W went away quickly.
I know you tried this a couple of times, but try it again. Also, make sure you;re using his version6 root app. It's a little better.
It's the reason why I moved to the ver3 hacked bootloader&kernel combo.
Your R-W usually goes away after you close the file manager app.
Hurray!
Thank you Moscow Desire. Being quick seems to have done the trick.
But here's a tip for others: Es File Explorer, in spite of claiming otherwise, doesn't seem to allow changing file permissions.
tlyonstlyons said:
Thank you Moscow Desire. Being quick seems to have done the trick.
But here's a tip for others: Es File Explorer, in spite of claiming otherwise, doesn't seem to allow changing file permissions.
Click to expand...
Click to collapse
Yeah, another one that doesn't work well with the stock bootloader/root method is File Explorer HD. It just plain refuses. (hadn't used ES FE in a long time, so completely forgot about that one). Root Explorer is a little more reliable.
Glad you got it changed.
Also, when I was running stock and ver2 bootloader, I noticed I had to run the root program again to get R-W. Doesn't hurt anything, just had to run it again. But with ver3 bootloader w/altered boot.img, no problems. All explorer programs seem to work like they should.
Moscow Desire said:
Yeah, another one that doesn't work well with the stock bootloader/root method is File Explorer HD. It just plain refuses. (hadn't used ES FE in a long time, so completely forgot about that one). Root Explorer is a little more reliable.
Glad you got it changed.
Also, when I was running stock and ver2 bootloader, I noticed I had to run the root program again to get R-W. Doesn't hurt anything, just had to run it again. But with ver3 bootloader w/altered boot.img, no problems. All explorer programs seem to work like they should.
Click to expand...
Click to collapse
Hmm I'd never had to rush to get remounted rw and having to press it in root explorer is a bug in RE. If you remount rw from cold THEN load Root Explorer it will show /system as already mounted rw
Sent from my Iconia A500 using Tapatalk 2
blackthund3r said:
Hmm I'd never had to rush to get remounted rw and having to press it in root explorer is a bug in RE. If you remount rw from cold THEN load Root Explorer it will show /system as already mounted rw
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
Maybe on some systems it does. I brought this up a few weeks ago. Maybe it's tablet specific.
After a week or so, the Remounter failed to change System to R-W. It claimed it did, but Root explorer still showed R-O. You couldn't change it. No other changes were made to the OS.
Ver6 did the same under ver2 bootloader with stock kernel. You had to be quick to do the changes, as the other user said. It's not a fluke.
Other known oddities,,,
File Explored HD would not recognize it. Failed to change System to R-W, Updating to Ver3 BL and kernel fixed this.
Of course it's a damn fine tool. It works well for most people. And we're thankful you take a part in development. Wish more would get involved.
Just got the phone, updated to MDL. Stock root and TWRP recovery.
SU is installed. Downloaded and checked root with Root Checker - root affirmed.
Only mod so far is Hotspot with the MDL Odexed through TWRP.
Installed ES File Explorer, and it wont allow me to delete or rename system files (specifically ui sounds).
ES asked for and was given SU permission.
I am only good enough with Android as far as I can follow instructions in these forums - I know nothing beyond that.
Any ideas what the problem may be? I was considering getting Root Explorer, if that will work, but I dont want to drop the 3.99 if the problem is elsewhere or can be fixed.
Thanks for your help.
(And what I am currently trying to accomplish is silencing the camera (or more specifically, editing/saving the feature.xml file to allow menu switching of sound : http://forum.xda-developers.com/showthread.php?t=2261789 - it wont let me save the text edited file - I assume it;s the same problem that wont let me delete/rename.)
Thanks. Without you guys I'd be straight Sprint/Samsung stock - aint nobody got time for that.
DevonSloan said:
Just got the phone, updated to MDL. Stock root and TWRP recovery.
SU is installed. Downloaded and checked root with Root Checker - root affirmed.
Only mod so far is Hotspot with the MDL Odexed through TWRP.
Installed ES File Explorer, and it wont allow me to delete or rename system files (specifically ui sounds).
ES asked for and was given SU permission.
I am only good enough with Android as far as I can follow instructions in these forums - I know nothing beyond that.
Any ideas what the problem may be? I was considering getting Root Explorer, if that will work, but I dont want to drop the 3.99 if the problem is elsewhere or can be fixed.
Thanks for your help.
(And what I am currently trying to accomplish is silencing the camera (or more specifically, editing/saving the feature.xml file to allow menu switching of sound : http://forum.xda-developers.com/showthread.php?t=2261789 - it wont let me save the text edited file - I assume it;s the same problem that wont let me delete/rename.)
Thanks. Without you guys I'd be straight Sprint/Samsung stock - aint nobody got time for that.
Click to expand...
Click to collapse
Maybe try renaming the extensions of those files to ".bak"
Hope it helps bud
****'ll Buff Out
Goose0121 said:
Maybe try renaming the extensions of those files to ".bak"
Hope it helps bud
****'ll Buff Out
Click to expand...
Click to collapse
Thanks, but that was actually the first thing I tried - it brings up the rename dialogue, but then after change and "ok", nothing is changed. Same with Astro and Root File Manager.
Thanks, though.
Anyone else?
Try pressing Menu and then going to "Root Explorer" and then "Mount R/W"
From there, make sure the path shows RW instead of RO. Click ok.
Exit out of ES File Manager and come back in and check the Root Explorer Mount R/W again to see if RW stuck. If it did, try to see if you can delete.
apexcell said:
Try pressing Menu and then going to "Root Explorer" and then "Mount R/W".
Click to expand...
Click to collapse
Clicked on root explorer and it gave a (paraphrased) "ES File Explorer has been given superuser privileges for interactive shell" (or something close to that), but I cant find "Mount R/W" anywhere.
And trying various things keeps giving me "device not supported" errors. Again, a paraphrase as the message isnt on screen long enough for me to get the exact wording.
Thanks again for the help.
Is this what comes up when you click on root explorer?
apexcell said:
Is this what comes up when you click on root explorer?
Click to expand...
Click to collapse
No. Nothing opens up. Same settings menu screen, there is just the message that appears below, then disappears, about "superuser permission granted.
I also have same issue where it tells me superuser access has been granted. However, about 15 seconds later I get another message saying "Sorry, test failed. This feature can not run on your phone."
Hmm, that's definitely not right. Try going to the Application manager, to ES File Explorer, Clear data, Uninstall, then re-installing it through Play Store. See if it still does that.
You should definitely get that screen when you go to root explorer.
cap167 said:
I also have same issue where it tells me superuser access has been granted. However, about 15 seconds later I get another message saying "Sorry, test failed. This feature can not run on your phone."
Click to expand...
Click to collapse
That is exactly what is happening with me.
Thanks Apex - doing that now.
UPDATE:
Nope. clear, uninstall, reboot, reinstall, reboot... and still getting the same results. Bah.
Does Solid Explorer also fail to be able to delete?
https://play.google.com/store/apps/details?id=pl.solidexplorer
Thanks Apex. Solid Explorer worked. Thank you for not giving up on the ideas.
While I am glad I found a solution to deleting the files, I remain a bit concerned about the ES File Explorer problem. It make me think other problems exist that I just haven't hit yet.
Case closed!
Great, glad that worked out for you.
I can't delete any system apps with it anymore, does anybody else have the same problem or even a fix for it?
Working fine on 6.01 for me, Did you try uninstalling and reinstalling it?
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
case-sensitive said:
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
Click to expand...
Click to collapse
hey guys, "system less root"
That would modify system... Just freeze the apps.
geoff5093 said:
That would modify system... Just freeze the apps.
Click to expand...
Click to collapse
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
tech_head said:
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
Click to expand...
Click to collapse
Pretty sure you lose Android Pay with this method though, just FYI if you care about that.
But if you are running Xposed you broke it anyway. There is a way to get it working.
You will need to remove the empty su files you just created to be able to add cards.
You will need to use a Xposed module to hide modifications to the system so that the device check comes back clean.
It's a pain, but if you want Xposed, TiBu, ES and Android Pay, that is the price.
Sent from my Nexus 6P using Tapatalk
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
WizeGuyDezignz said:
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
Click to expand...
Click to collapse
Doesn't work. Apps restore themselves.