Database Users

All Uses For ADB For NON-ROOTED Eris

I jumped the gun installed the original and the latest 2.1 leaks, so I am not rooted. I just recently learned how to use the ADB push feature in the tools of the Android SDK to install a custom boot animation and I'm stoked at how awesome it works.
I was wondering what all you can use the ADB push feature for on a NON-rooted Eris. Any help is greatly appreciated.
Thanks devs for all your hard work!

Adding custom boot images.

Thanks jcase! I was seriously hoping that there was there would be other things that I could use it for. Oh well, guess I'll just wait until the Official OTA 2.1 is released, then wait until you genius devs crack it open and get it rooted. Thanks again!

You can make a script to quickly install apps in mass.
#!/bin/sh
echo "Installing apps..."
./adb install apps/app1.apk
echo "app1 Installed."
./adb install apps/app2.apk
echo "app2 Installed."
./adb install apps/app3.apk
echo "app3 Installed."
./adb install apps/app4.apk
echo "app4 Installed."
./adb install apps/app5.apk
echo "app5 Installed."
echo "done"

how do i install ADB on my computer. I downloaded SDk and in the tools when i click or ADB or Emulator it opens and instantly disappears. im running windows 7.

interscion said:
how do i install ADB on my computer. I downloaded SDk and in the tools when i click or ADB or Emulator it opens and instantly disappears. im running windows 7.
Click to expand...
Click to collapse
....
EDIT: check your inbox interscion, I sent you a message in order to keep this thread uncluttered and on subject.

Android22 said:
....
EDIT: check your inbox interscion, I sent you a message in order to keep this thread uncluttered and on subject.
Click to expand...
Click to collapse
would you send me one too i have sdk setup and when i click adb a screen pops up and disapears ,,, help!! please please
trhanks

PM
Jimmie's 2.1 Eris said:
would you send me one too i have sdk setup and when i click adb a screen pops up and disapears ,,, help!! please please
trhanks
Click to expand...
Click to collapse
Sent, check your inbox...

I know this is an old thread, but I just got a replacement eris and i'm trying to avoid signing into the market before I root (for a completely clean install, probably doesn't matter, I'm just funny like that), in which case, I want to install 1-click root before I do anything. So, if someone could point me in the right direction to do an adb install on an un-rooted eris, that would be great.

demmo86rt said:
I know this is an old thread, but I just got a replacement eris and i'm trying to avoid signing into the market before I root (for a completely clean install, probably doesn't matter, I'm just funny like that), in which case, I want to install 1-click root before I do anything. So, if someone could point me in the right direction to do an adb install on an un-rooted eris, that would be great.
Click to expand...
Click to collapse
No need to bypass activation, skip account setup, Settings->Applications->Unknown sources, Settings->Applications->Development->USB Debugging.
Then this plus this:
Code:
adb install erisone010.apk
You are making unnecessary work for yourself - if you want a Nandroid backup of the factory ROM in a near virginal state, root the phone with OneClick (so that a custom recovery gets installed) - NOT including insallation of the engtools (or rootme, whatever it is called), and then perform a factory reset afterwards. (That will clear accounts & account data from the phone, and you can then boot to the recovery to make a backup of the virginal ROM).

bftb0 said:
No need to bypass activation, skip account setup, Settings->Applications->Unknown sources, Settings->Applications->Development->USB Debugging.
Then this plus this:
Code:
adb install erisone010.apk
You are making unnecessary work for yourself - if you want a Nandroid backup of the factory ROM in a near virginal state, root the phone with OneClick (so that a custom recovery gets installed) - NOT including insallation of the engtools (or rootme, whatever it is called), and then perform a factory reset afterwards. (That will clear accounts & account data from the phone, and you can then boot to the recovery to make a backup of the virginal ROM).
Click to expand...
Click to collapse
That's basically what I ended up doing (got impatient and didn't wait for a reply), except I did sign in to the market and picked up 1-click that way. Thanks for your reply though, to my question asked in an attempt to feed my OCD tendencies.
Sent from my FroyoEris using XDA App

Unable to Re-Root Droid 2 after Gingerbread OTA

Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker

Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?

Hope somebody comes up with an answer - same thing happened to me.

did you use the d3 root method? thats the only one that works 100% on gingerbread.

Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.

SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni

Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.

Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!

My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?

Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.

I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================

drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.

This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!

Awesome! Thanks!

Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!

Awesome!
Thanks! This worked for me as well! (after additional reboot)

Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.

Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew

awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer

It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.

Market problem after rooting 1.1.0 with nooter 1.6.24

Hello folks,
I did the kralik's (and many other, of course) root, using nooter 1.6.24 with 1.1.0 uramdisk and framework.jar. Everything worked fine, even market is working.
I returned all my programs I backed up with titanium backup pro, and all of them worked fine, even with all data back!!!
As I said above, market is working, i.e. I can download files, and I do a search on one that has updates, it will be shown, but when I tap on "my apps/download", I get the message:
"Attention - a server error has occurred. Retry, or cancel and return to the previous screen"
With that, I am not able to do a batck update as I used to, and even used the restore market link from titanium backup pro. This happens with original market (no search) as with vending.apk (with search). Both show the same error.
Has anyone seen this before????

Strange, I tried it with my manual method and it works, use the updated Vending.apk and try this through adb:
adb shell
su
rm -R /data/data/com.google.android.youtube/*
rm -R /data/data/com.android.vending/*
reboot
When it reboots relogin on both youtube and market, tell me if it worked.... I've been reading strange things about the automatic methods f*****g configs on youtube and market, I'm working on a stable script at the moment with salsichad2.

Eded,
Did it all, rebooted, relogged and nothing changed. Relinked apps with titanium backup pro, and nothing else happened.
Market is still working, anyway, so does youtube (i.e. I can access and check my channel)

I installed SalsichaNooter 0.4 I was having the same problem gmail worked but YouTube would not open and market would not search.
I did the following:
adb shell
su
rm -R /data/data/com.google.android.youtube/*
rm -R /data/data/com.android.vending/*
reboot
Click to expand...
Click to collapse
2. After that YouTube opened I entered my account info.
3. Than I downloaded one market app (search was still not working).
4. After I did that I installed vending.apk http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51
by using "adb install -r Vending.apk"
I am now able to search with the market and gmail still works.
P.S. SalsichaNooter 0.4 did get stuck on Rooted Forever screen I let it sit for 3-4 minutes and then turned off and took out card. Everything seems to be working though. Thanks,

dpippin said:
I installed SalsichaNooter 0.4 I was having the same problem gmail worked but YouTube would not open and market would not search.
I did the following:
2. After that YouTube opened I entered my account info.
3. Than I downloaded one market app (search was still not working).
4. After I did that I installed vending.apk http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51
by using "adb install -r Vending.apk"
I am now able to search with the market and gmail still works.
P.S. SalsichaNooter 0.4 did get stuck on Rooted Forever screen I let it sit for 3-4 minutes and then turned off and took out card. Everything seems to be working though. Thanks,
Click to expand...
Click to collapse
Read the first post, that has nothing to do with his problem anyway thanks for trying
---------- Post added at 10:45 PM ---------- Previous post was at 10:36 PM ----------
dpippin could you try to download something, then go into the my apps/download tab on the market?
Just to see if apeine's problem is generalized as I can't try it (it didn't happen to me when I had market) as I haven't got the market installed at the moment.

Disable OTA on the 2nd Gen Fire TV stick :

Update: It's been reported that the method works on FireOS up to and including 5.2.6.0, but does not work on 5.2.6.1
To catch a break, and avoid force fed OTA updates, run these commands from your ADB:
Code:
adb.exe uninstall -k --user 0 com.amazon.device.software.ota
adb.exe uninstall -k --user 0 com.amazon.device.software.ota.override
This will disable the OTA apps till the next factory reset. In case there is ever root, your system will be old enough to be rootable.
Once you do this, and go check for system updates, it'll generate a message "System update failed".
More details can be found in this thread.

this was patched on the tablets and if not already will likely be patched on the sticks soon as well.

krsmit0 said:
this was patched on the tablets and if not already will likely be patched on the sticks soon as well.
Click to expand...
Click to collapse
Sure, nothing lasts forever ... But even more reason to do this NOW !!!
At the moment, I have this version : Fire OS 5.2.4.1, ro.build.date=Fri Jun 9 23:01:51 UTC 2017, so not patched yet.

@bibikalka is there a way to reinstall an uninstalled APK for user 0 ?

rainman74 said:
@bibikalka is there a way to reinstall an uninstalled APK for user 0 ?
Click to expand...
Click to collapse
I don't know an easy one
But you can always do a factory reset! These operations don't actually delete anything, just flag it as unusable.

This should allow debloating the Fire TV sticks. Does anyone have a list with apps that you can safely remove? Maybe even replacing the stock launcher is possible. Although on the Fire HD 10 5th generation removing the stock launcher breaks the home button detection.

MWin123 said:
This should allow debloating the Fire TV sticks. Does anyone have a list with apps that you can safely remove? Maybe even replacing the stock launcher is possible. Although on the Fire HD 10 5th generation removing the stock launcher breaks the home button detection.
Click to expand...
Click to collapse
Yes, you can completely replace Fire Stick Launcher without root! But first ensure, that all settings are made, because you can not access certain settings anymore (again only after a factory reset).
And you must install another launcher first, e.g. AppStarter (https://github.com/sphinx02/AppStarter/releases)
1. Uninstall:
adb uninstall -k --user 0 com.amazon.device.software.ota
adb uninstall -k --user 0 com.amazon.device.software.ota.override
adb uninstall -k --user 0 com.amazon.tv.nimh
adb uninstall -k --user 0 com.amazon.tv.launcher
2. Access settings then via ADB without com.amazon.tv.launcher (Fire Stick "tank" on 5.2.4.1):
Controller:
Code:
adb shell am start -n com.amazon.tv.settings/.tv.controllers_bluetooth_devices.ControllersAndBluetoothActivity
App-Menu:
Code:
adb shell am start -n com.amazon.tv.settings/.tv.applications.ApplicationsActivity
Network:
Code:
adb shell am start -n com.amazon.tv.settings/.tv.network.NetworkActivity
Factory Reset:
Code:
adb shell am start -n com.amazon.tv.settings/.tv.FactoryResetActivity

rainman74 said:
But first ensure, that all settings are made, because you can not access certain settings anymore (again only after a factory reset).
Click to expand...
Click to collapse
Thanks! Do you know what settings are affected?
I can recommend Activity Launcher to open settings, it also allows you to open some hidden settings. See NO ROOT: Use 'Activity Launcher' to remove accounts, grant/revoke usage access.

MWin123 said:
Thanks! Do you know what settings are affected?
Click to expand...
Click to collapse
yes, because of we can't grant com.amazon.tv.permission.LAUNCHER_SETTINGS to com.amazon.tv.settings (adb -d shell pm grant com.amazon.tv.settings com.amazon.tv.permission.LAUNCHER_SETTINGS), you can't access the following settings anymore:
Account (but you'll in no way ever change your Amazon Account)
Display & Sound (so set each setting there to "automatic" before you uninstall com.amazon.tv.launcher)
Info/About (you'll not need that anyway)
Childlock (no need for that anyway, because you will not have Amazon Launcher)
Debug/ADB (so set ADB/USB to "yes" before you uninstall com.amazon.tv.launcher and you'll be fine)
MWin123 said:
I can recommend Activity Launcher to open settings, it also allows you to open some hidden settings. See NO ROOT: Use 'Activity Launcher' to remove accounts, grant/revoke usage access.
Click to expand...
Click to collapse
Thanks, I'll try that...

After installing modified "Android TV Settings" (https://forum.xda-developers.com/attachment.php?attachmentid=4255667&d=1503965469) with regular "adb install" you can access the following settings again if amazon.tv.launcher is disabled or uninstalled (non-root):
Sound (system sounds only)
Code:
com.android.tv.settings.device.sound.SoundActivity
Info/About
Code:
com.android.tv.settings.about.AboutActivity
Debug/ADB
Code:
com.android.tv.settings.system.DeveloperOptionsActivity
CEC/HDMI Control
Code:
com.android.tv.settings.system.InputsActivity
Bluetooth/Pairing
Code:
com.android.tv.settings.accessories.AddAccessoryActivity
Date/Time
Code:
com.android.tv.settings.system.DateTimeActivity
Device Name
Code:
com.android.tv.settings.name.DeviceNameSettingsActivity
Language
Code:
com.android.tv.settings.system.LanguageActivity

Do the ADB commands in post 1 work on the 2nd gen Amazon Fire TV please? (not the stick).
I have just acquired one which is non rooted and loaded with software v5.2.4.2 which I understand that I am unable to root.
Any advice greatly appreciated.

meohmy said:
Do the ADB commands in post 1 work on the 2nd gen Amazon Fire TV please? (not the stick).
I have just acquired one which is non rooted and loaded with software v5.2.4.2 which I understand that I am unable to root.
Any advice greatly appreciated.
Click to expand...
Click to collapse
Yes they do, I just tried it on mine and it worked flawlessly. Good luck!

Thanks for the prompt reply, I will have a go as soon as the wife goes out.

apologiez for hijacking your thread, these infors are very appreciated.
i 'accidently' uninstalled "com.amazon.tv.settings", any idea how i can force a factory reset? Installing the modfied "Android TV Settings" didnt help.

TV33 said:
apologiez for hijacking your thread, these infors are very appreciated.
i 'accidently' uninstalled "com.amazon.tv.settings", any idea how i can force a factory reset? Installing the modfied "Android TV Settings" didnt help.
Click to expand...
Click to collapse
this is probably not possible anymore then!
But you can try this method: http://www.aftvnews.com/how-to-unbrick-by-entering-recovery-mode-and-factory-reset-the-amazon-fire-tv/

Worked first time so thanks for all the info, now to get a vpn so I can start using it.

Hi, I need help
I have a Fire TV Stick2 (Tank), after trying Post #7 I have no choice to change the WIFI account.
Post #10 doesn't work.
Any Idea? Post #15 seems not possible for "tank"
Any advice greatly appreciated.

remoter3406 said:
Hi, I need help
I have a Fire TV Stick2 (Tank), after trying Post #7 I have no choice to change the WIFI account.
Click to expand...
Click to collapse
You will have access to wifi on Fire TV Stick2 ("tank") with this cmd as stated in post #7:
Code:
adb shell am start -n com.amazon.tv.settings/.tv.network.NetworkActivity
Post #10 doesn't work.
Click to expand...
Click to collapse
Did yo install the modified "Android TV Settings" first. The command definitely works then!
Any Idea? Post #15 seems not possible for "tank"
Any advice greatly appreciated.
Click to expand...
Click to collapse
It's possible with an Micro USB OTA adapter: https://www.amazon.de/gp/product/B00N2LSLKA/ref=oh_aui_search_detailpage?ie=UTF8&psc=1

You will have access to wifi on Fire TV Stick2 ("tank") with this cmd as stated in post #7:
Code:
adb shell am start -n com.amazon.tv.settings/.tv.network.NetworkActivity
Click to expand...
Click to collapse
First, sorry for my english. I mean WIFI is working with my WIFI repeater, but I want change it to my main WIFI router. How?
Did yo install the modified "Android TV Settings" first. The command definitely works then!
Click to expand...
Click to collapse
Yes, I installed the "apk" and it apears on TV, but no reaction. Is a adb command needed for activating?
It's possible with an Micro USB OTA adapter:
Click to expand...
Click to collapse
OK, this is the last try if I coudn't change the WIFI
Many Thanks for your quick response

remoter3406 said:
First, sorry for my english. I mean WIFI is working with my WIFI repeater, but I want change it to my main WIFI router. How?
Click to expand...
Click to collapse
I will show you a screenshot of that later this evening...
Yes, I installed the "apk" and it apears on TV, but no reaction. Is a adb command needed for activating?
Click to expand...
Click to collapse
You can't click the icon, you must access the settings of it via adb or the app "Activity Lauchner" mentioned in this thread:
Code:
adb shell am start -n com.android.tv.settings.about.AboutActivity
adb shell am start -n com.android.tv.settings.accessories.AddAccessoryActivity
adb shell am start -n com.android.tv.settings.device.sound.SoundActivity
adb shell am start -n com.android.tv.settings.name.DeviceNameSettingsActivity
adb shell am start -n com.android.tv.settings.system.DateTimeActivity
adb shell am start -n com.android.tv.settings.system.DeveloperOptionsActivity
adb shell am start -n com.android.tv.settings.system.InputsActivity
adb shell am start -n com.android.tv.settings.system.LanguageActivity

adb commands are not effective

Hello
According to the forum research if i
- perform factory reset then the previously debloated apps will be reinstalled
- they can be reinstalled by adb command adb shell cmd package install-existing com.android.something without needing to factory reset.
- disabled (frozen) apps can be enabled through adb pm enable <packagename>
I have tried al three but it does not work. the commands were correctly used.
- If i perform factory reset (tried only through twrp recovery clearing cache, dalvik,data) then after initial setup the previously debloated apps are not back (i did not try factory reset through system settings yet because i dont know how it affects magisk)
Edit: only Kids mode got reinstalled. strange!
- If i use adb command adb shell cmd package install-existing com.android.something the terminal gives back that "the app was succesfully installed to user 0" but after checking the tablet the app is nowhere. I have tried it using the newest adb fastboot toolkit which has a nice terminal UI so i can reinstall all apps at once- which apps should be present on the tablet they give back "the app was succesfully installed to user 0" (they were uninstalled from user 0 so installing to user 0 should be fine) but they are not reinstalled.
- Titanium backup had accidentally frozen two apps, one is smart things, the second it android system webview- i cannot defrost them through titanium backup. I have tried several apps but none of them defrosts back. I have tried adb command pm enable <packagename> which gives me message "package succesfully enabled" but after checking state through adb pm list packages -d or tablet app setting they are still frozen.
My samsung tablet is rooted (at least i believe rooting was succesful because root checker says that) and on stock ROM.. It is strange that none of these commands are effective.
Does anybody have any clue why?
Thank you