Related
Fairly straightforward question. Is it possible to disable ART and re-enable Dalvik other than via the settings dialog, either via ADB, some sort of flashable zip or from a recovery?
I ask for two reasons. Firstly, when I flashed an experimental 4.4 build on my Galaxy Nexus, I made the mistake of enabling ART. When I restarted, because I'd stupidly flashed an incompatible gapps package, apps would force close so frequently that the constant notifications made it extremely difficult to get into the settings and turn it off again.
Secondly, I just saw a thread on Reddit where somebody was claiming that their Nexus 5 went into a bootloop after enabling ART, and they had to do a wipe to fix it.
So it seems to me it would be quite helpful to be able to disable or enable ART without having to be able to boot.
If you've found a way to fix this, I would love to know. I just turned ART on after installing a new rom, and I'm stuck in a boot loop without a recent backup.
+1
I've enabled ART on my Nexus 4 without issue. Stock ROM.
Enabling it on my 2013 Nexus 7 caused it not to boot past the boot animation anymore.
Just reflash the ROM from recovery. Wipe system and flash. Done. Dalvik will be enabled again. If your not rooted that's another matter but the OP seems to be.
theesotericone said:
Just reflash the ROM from recovery. Wipe system and flash. Done. Dalvik will be enabled again. If your not rooted that's another matter but the OP seems to be.
Click to expand...
Click to collapse
I figured flashing wiping would do it but wasn't willing to wipe if there's an easier solution.
In my case it was Xposed. I flashed the disable zip and that did it. Guess I didn't reboot fully after disabling it from in the ROM.
He said wipe system, not data. It is possible to wipe the system information and leave your data intact.
MisterEff said:
He said wipe system, not data. It is possible to wipe the system information and leave your data intact.
Click to expand...
Click to collapse
Ah yes. I mistook system as data..
I don't know if it allow to switch runtime, but it helps me to avoid bootloop after ota 4.4.2 on my Nexus 5.
To check current library
adb shell getprop persist.sys.dalvik.vm.lib
To set art one
adb shell setprop persist.sys.dalvik.vm.lib libart.so
(IRoN) said:
I don't know if it allow to switch runtime, but it helps me to avoid bootloop after ota 4.4.2 on my Nexus 5.
To check current library
adb shell getprop persist.sys.dalvik.vm.lib
To set art one
adb shell setprop persist.sys.dalvik.vm.lib libart.so
Click to expand...
Click to collapse
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
THANK YOU!!!! It worked for me
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
Thanx, it worked for me
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
It worked for me too, and I don't even use Nexus device, And done it from adb but in recovery mode with properly mounted partitions.
Thx again.
Boot into Recovery and Fix Permissions has fixed this for me (Galaxy Nexus)
EDIT: Apparently that switches it back to dalvik?!?
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
Thanks, this help save my day !
Saved my day too! HTCONE on Viper and I was able to use twrp and a USB otg drive. Thanks!
Sent from my HTCONE using Tapatalk
Quicker way to switch back to Dalvik
My phone was stuck in a bootloop because I did not have enough free space to switch to ART, making my device crash on boot. For a quick way to switch back to Dalvik, see below.
Boot into recovery ('adb reboot recovery' if possible), then mount /data and run this command:
Code:
adb shell "echo libdvm.so > /data/property/persist.sys.dalvik.vm.lib"
adb reboot
It will now be in Dalvik. Enjoy
Symptoms:
Phone stucks at boot animation screen (4 color balls rolling)
adb devices command shows device is represent.
adb logcat shows no fatal error, no obvious cause
kernel message shows no fatal error
Cause:
Content inside /data/system/sync is corrupted(?)
Fix:
Rename or remove folder /data/system/sync
Below is the full story and how I figure it out:
3 days ago when I woke up, i find that my phone was rebooting and the screen showing boot animation. After waiting a long time, I find that the phone was stuck on boot animation. I can use adb shell to connect the phone and adb logcat to retrieve the log. The log shows nothing special or fatal, just some minor errors.
My phone is rooted, unlooked and relocked bootloader, CWM Recovery 6.0.4.4
The apps I installed that have root access included, but not limited to:
Xposed FrameworkAndroid Tuner aka 3C ToolboxGravityBoxiFontXprivacyGreenifyAFWall+BusyBoxSuperSucom.avast.android.mobilesecuritycom.avast.android.antitheft (Root install)
After Googled a few hours, 99.9% of the result tell you factory reset your phone is the fix, and i am not satisfied with that. So I used CWM recovery to made a complete backup, and tinkering with the files and system.
At first I cleared cache and dalvik-cache in recovery as this is easiest, but no luck.
Then I suspect this might be a flash memory chip problem , so I boot into recovery, use adb shell to connect console, however, adb shows that device unauthorized, so I do a factory reset and reboot recovery, then adb shell again and success, and in recovery, restore /data backup. Then I use command
Code:
%path to android platform tools folder%> adb push adbkey.pub /data/misc adb/adb_keys
, then adb is authorized after reboots.
To check if the flash memory is okay, i used the command:
Code:
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/cache
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/system
The result seems fine, and no signs of hardware failure.
After reading logcat, the system seems nearly finished the booting process, and stucked at end of System service, and never signal Boot_Completed. Using Android Device Monitor, system_process main thread is still running and doing something unknown.
At this point, i think kernel and /system should be normal.
Then I suspect that the apps i installed might be the cause, I renamed the folders like:
Code:
mv /data/data /data/data.old
mv /sdcard/Android /sdcard/Android.old
mv /data/app /data/app.old
to see if the OS can boot normally, but no luck.
I also renamed many other app folders and reboot, but none of this can solve the bootloop problem.
Then I renamed /data/system and reboot, from the logcat, i can see the system is regenerating the content inside the system, and I waited for a moment, the OS booted successfully with many "xxx process stopped" error message on the screen. So at this moment I realized that content in /data/system might be the root of all evil. As Home screen is not usable with a lot of process stopped messages, I used this command to start the apps i want.
Code:
adb shell monkey -p com.yourpackage.name -c android.intent.category.LAUNCHER 1
(Need to use some game points )
Next I used command
Code:
find /data/system -mtime -3
to find out which files were altered within last 3 days. I get a list of files and folder and then I rename the folders one by one and reboot. Finally, /data/system/sync folder is confirmed as the cause of the problem.
I restored the full backup in recovery, and renamed the /data/system/sync folder to /data/system/sync.old and reboot. Phone boots normally, everything seems fine.
I don't know what, why, how exactly causing the boot problem, but the problem is solved anyway. Hope this information can help someone.
I used 40+ hrs to figure it out, and another 2+ hrs to summarize and write this.
fxxk.
Nice work!
Sent from my Nexus 5 using Tapatalk
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, what should I do for this, Thank you in advance for your Help.
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, then im trying to open bootloader but it is not responding. what should I do for this, Thank you in advance for your Help
TUPANGPUTi23 said:
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, then im trying to open bootloader but it is not responding. what should I do for this, Thank you in advance for your Help
Click to expand...
Click to collapse
Probably best to ask in your devices forums. This is for the Nexus 5, not the Samsun J2 Core.
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
s1dest3pnate said:
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
Click to expand...
Click to collapse
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Acid0057 said:
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
s1dest3pnate said:
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
Click to expand...
Click to collapse
Awesome!
Sent from my Pixel XL using Tapatalk
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
GBpfan95 said:
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
Click to expand...
Click to collapse
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
s1dest3pnate said:
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
Click to expand...
Click to collapse
Does that work even if I am locked and not rooted?
GBpfan95 said:
Does that work even if I am locked and not rooted?
Click to expand...
Click to collapse
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
I just ended up factory resetting. Most of everything is backed up anyway. Definitely learned my lesson
Could you please post the SubstratumRescue.zip? I cannot get to the directory on my phone via ADB and want to try running the script commands manually.
EDIT: Nevermind, I tracked it down on the dev's AFH page.
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
pR0wl3r said:
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
Click to expand...
Click to collapse
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
jeremywh7 said:
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
Click to expand...
Click to collapse
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
bobby janow said:
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
Click to expand...
Click to collapse
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
jeremywh7 said:
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
Click to expand...
Click to collapse
Yeah still shows an x.
Sent from my Pixel using XDA-Developers Legacy app
Thanks!
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Thanks so much mate this worked for me perfectly!
This can be done in a less manual fashion. It looks like many of you are on Windows, but I'm sure theres a way to accomplish something similar. I'm on Linux and this is how I did it.
Code:
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 echo cmd overlay disable
cmd overlay disable com.samsung.android.app.aodservice.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.smartmirroring.StatusBarIconsforSamsungextras
cmd overlay disable android.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.app.smartcapture.StatusBarIconsforSamsungextras
cmd overlay disable com.android.settings.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.lool.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.navbars.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.tiles.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.statusbars.StatusBarIconsforSamsungextras
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 adb shell cmd overlay disable
For reference, ag is very similar to grep. So the explanation is adb shell allows you to pass a command to it so it can run that command immediately. So adb shell cmd overlay list is the same as typing adb shell followed by cmd overlay list except it prints the output and immediately exits. So I take that output, grep (using ag in this case) for the enabled overlays and then programmatically disable them. xargs -n 1 says take at most one of the arguments passed to this command and append it to the rest of the line. So this calls adb shell cmd overlay disable __insert-overlay-here__ repeatedly.
I messed up good....
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first one was apparently not removing my overlays. So anyway...
My device rebooted after Chainfire, and was on the G/progress bar for like 5 mins so I knew something was up.
I decided to flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread, so I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
EDIT: Resolved. I was able to delete all overlaid apk's from /data/app.
Hi there,
Question, I got a non-rooted S8, Stock in like everything, and it runs everything fine, including Substratum!
I am wondering about one thing though after reading this thread, imagine something went wrong, what would be my options? I found the Rescue ZIP on my phone, can I apply this if needed with the original recovery from the S8? Or do I need TWRP for that?
---------- Post added at 08:44 PM ---------- Previous post was at 08:39 PM ----------
s1dest3pnate said:
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
Click to expand...
Click to collapse
Hi mate, do I read correctly, that its possible to only boot TWRP temporaly without flashing it?
I have to put the folder/files in the same folder as platform tools?
LOOKS LIKE THIS ONLY WORKS FOR 5.6.1.0 AND UP BUT YOU CAN ALWAYS TRY IF YOU WANT, THIS *SHOULD* NOT DAMAGE YOUR DEVICE
THIS DOES NOT WORK ON NEW 2018 MODELS.
You can use this method in any tools or scripts, but you must add a link to this thread in these threads, videos, etc.
Hi!
This is a guide on how to disable system apps on 7th Generation or older Fire tablets.
This guide *should* work in theory for every Fire tablet, in every version, but I only tried this is my HD 8, version 5.6.1.0.
(Also the "pm hide" command does not just hide the app, it is almost completely identical to "pm disable", only the system interprets it differently. So, yes, you will notice a good increase in performance after you do this!)
Please hit thanks if this helped, it is easier than commenting thanks...
--You'll require a PC with ADB installed.--
--------
MANUAL METHOD:
1.) I attached an APK for "Amazon Facebook Share" below,(edit: it is not displaying properly in this thread, see post #1) install it with ADB, or copy it into the device and install it manually.
2.) Reboot.
3.) Now open the command prompt, and type:
Code:
adb shell
run-as com.amazon.unifiedsharefacebook
id
4.) If the "id" command output *does not* start with "uid=2000" then you are good to go! Just run "pm hide" on every system app package you want to disable, you can find some lists in this forums. (If it does not, PM me your output or reply in this thread with the output)
5.) So, it looks like that this sheet works well.
SEMI-AUTOMATIC METHOD:
SORRY, CURRENTLY THE SEMI AUTO METHOD IS BROKEN, I'LL TRY TO FIX IT.
1.) Download the attached .ZIP and extract it, see post #30.
2.) Run the batch file, (it will reboot your device).
3.) Now continue the step #3 from above.
--------
If you try to access a disabled app, it will show an annoying warning, (like accessing "System Updates" in Device Options after disabling OTA)
Code:
The requested action is not permitted. Check Parental Controls settings and retry.
IMPORTANT- If you disable com.amazon.firelauncher, everything will work almost perfectly, but you will see the warning message I mentioned above every time you press home.
--------
Good Luck with disabling, and don't disable critical parts!
Here is the APK.
Sadly didnt work, have a Fire HD 8, 5.6.0.1
Installed it via adb install -r -d with the following error.
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Works !
works on 5.6.2.0
removed the apps from the bloatware spreadsheet
Not yet rebooted my fire hd8
Need help with my fire HD 8 running fire OS 5.6.2.0
Supersonic27543 said:
THIS IS STILL UNCONFIRMED, AND MAY OR MAY NOT WORK. BUT IT JUST WORKED FOR MY DEVICE.
Hi, I'll be unable to be in this forums for some time, maybe for a couple of months, (I will still check the forums when I can) so I'm going to leave a gift for everyone!
This guide *should* work in theory for every Fire tablet, in every version, but I only tried this is my HD 8, versions 5.6.0.1 & 5.6.1.0.
(Also the "pm hide" command does not just hide the app, it is almost completely identical to "pm disable", only the system interprets it differently. So, yes, you will notice a good increase in performance after you do this!)
-You'll require a PC with ADB installed.
1.) I attached an APK for "Amazon Facebook Share" below,(edit: it is not displaying properly in this thread, see post #1) install it with ADB, or copy it into the device and install it manually.
2.) Reboot.
3.) Now open the command prompt, and type:
Code:
adb shell
run-as com.amazon.unifiedsharefacebook
id
4.) If the "id" command output *does not* start with "uid=2000" then you are good to go! Just run "pm hide" on every system app package you want to disable, you can find some lists in this forums. (If it does not, PM me your output or reply in this thread with the output)
If you try to access a disabled app, it will show an annoying warning, (like accessing "System Updates" in Device Options after disabling OTA)
Code:
The requested action is not permitted. Check Parental Controls settings and retry.
IMPORTANT- If you disable com.amazon.firelauncher, everything will work almost perfectly, but you will see the warning message I mentioned above every time you press home.
Good Luck with disabling, and don't disable critical parts!
Click to expand...
Click to collapse
hey, I am trying to get rid of some apps on the fire HD 8 and what this post said was not working and I was hoping you could help me out...
1. when I put the apk in the storage and try to install it on my Fire it comes back and says "app not installed" but I tried to push it with ADB and still no luck...so I try my luck and try all the commands anyway and here is the script I got back:
C:\Tools\platform-tools_r28.0.0-windows\platform-tools>adb shell
[email protected]:/ $ run-as com.amazon.unifiedsharefacebook
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
1|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $
anything would help.
Thanks
Rangerclass said:
hey, I am trying to get rid of some apps on the fire HD 8 and what this post said was not working and I was hoping you could help me out...
1. when I put the apk in the storage and try to install it on my Fire it comes back and says "app not installed" but I tried to push it with ADB and still no luck...so I try my luck and try all the commands anyway and here is the script I got back:
C:\Tools\platform-tools_r28.0.0-windows\platform-tools>adb shell
[email protected]:/ $ run-as com.amazon.unifiedsharefacebook
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
1|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $
anything would help.
Thanks
Click to expand...
Click to collapse
i've copied the apk in /sdcard and then pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
t0x1cSH said:
i've copied the apk in /sdcard and then pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
Click to expand...
Click to collapse
I just got the tablet on Prime day and have not yet got the sdcard...
is there anyway i could do it without and what Tablet do you have?
mine is a Fire HD 8 7th gen running OS 5.6.2.0
thanks for the advice and hope we can figure something out.
Rangerclass said:
I just got the tablet on Prime day and have not yet got the sdcard...
is there anyway i could do it without and what Tablet do you have?
mine is a Fire HD 8 7th gen running OS 5.6.2.0
thanks for the advice and hope we can figure something out.
Click to expand...
Click to collapse
simply copy the apk on the device via usb cable in the root directory
open adb shell on your pc
run pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
then run run-as com.amazon.unifiedsharefacebook
and then check your id
t0x1cSH said:
simply copy the apk on the device via usb cable in the root directory
open adb shell on your pc
run pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
then run run-as com.amazon.unifiedsharefacebook
and then check your id
Click to expand...
Click to collapse
Thanks you so much.
I was doing /local not /sdcard because I thought that local would be it because I did not have a SD card yet.
the ID has now changed and I should be able to complete the first post.
Thank you so much for your time and help.
t0x1cSH said:
simply copy the apk on the device via usb cable in the root directory
open adb shell on your pc
run pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
then run run-as com.amazon.unifiedsharefacebook
and then check your id
Click to expand...
Click to collapse
I still get the [INSTALL_FAILED_MISSING_SHARED_LIBRARY] error
edt: not sure if I want to update if sooner or later an exploit might be found..? what do you guys think
Worked for HD7 (7th Edition) with OS 5.6.1.0
Now I can disable ("hide") further OTA updates.
Thank you very much.
Edit: I bought my HD7 last year, which came with O.S. 5.4.0.0. However, after "pm uninstall" Special Offer and a few Amazon Apps, I forgot to "pm uninstall" OTA. Consequently, it continued to get OTA updates till now.
Dan_firehd said:
Worked on HD7 (7th Edition) with OS 5.6.1.0
Now I can disable ("hide") further OTA updates.
Thank you very much.
Click to expand...
Click to collapse
It worked for HD 7? Nice :good:
vierlex said:
I still get the [INSTALL_FAILED_MISSING_SHARED_LIBRARY] error
edt: not sure if I want to update if sooner or later an exploit might be found..? what do you guys think
Click to expand...
Click to collapse
That error shows when the device does not support the APK. Is it a HD 8 2016? Also, do not update if you don't have to, 5.6.1.0 is considerably reinforced against exploits than previous versions. But if you really want to disable, it may be worth a try.
This is awesome! This worked on my 7th gen HD 8.
I followed the list of apps in this thread for what to hide (plus a little more): https://forum.xda-developers.com/hd8-hd10/general/debloat-fire-hd-2017-kindle-prime-music-t3729209
But I think I hid something important as I have a red line across the bottom of my screen now....
I know you said we need a PC with adb installed, but would this not also work with a terminal emulator?
Sent from my SAMSUNG-SM-G935A using Tapatalk
I get INSTALL_FAILED_INVALID_URI when trying to install on a Fire HD 8 2017 with 5.6.2 is it blocked in 5.6.2
I am so hoping this works for me! When I have the time to give it a try I will let you know.
getochkn said:
I get INSTALL_FAILED_INVALID_URI when trying to install on a Fire HD 8 2017 with 5.6.2 is it blocked in 5.6.2
Click to expand...
Click to collapse
I tried to link to the path /sdcard/Download/com.blabla.apk and it installed no problem.
I still cant properly hide the apps tho. All apps I try get hidden from the launcher but still exist and are active according to the settings/apps.
However, the apps cannot be run by any means...so this may work afterall.
Rollercoaster this one.
Edit: Vesion 5.6.2.0 install date: 11.07.2018
I'll post an update on the OTA check, if no automatic check is done!
You have to reinstall the apk every time you reboot, before you try the "run-as" command:
Code:
adb install -r -d .\com.amazon.unifiedsharefacebook.apk
I didn't have to rename the apk.
Yes, the apps still show up in the Settings and don't show as disabled in there, but the apps don't show in the launcher and can't be run, which is really what I'm looking for.
Badass post, Supersonic27543. You keep killin it!
I have a 2015 gen 5 OS 5.1.1 HD 8. I am trying to get it back to stock just to refresh. I try going to settings and doing a system refresh restarts and nothing.
click update shows no updates available. place up[date.bin file in the root of the device, shows update available. Then I click start update, validates update then restarts nothing.
My device is rooted and i dunno what else to do. I thought maybe its one of the packages thats disabled so I went to adb shell then su. Then ran pm list packages -d to show all disabled ones, then enabled those.
So i read that you can adb sideload an update.bin, so I go to put the device into recovery mode. Vol Down + power. Nothing Amazon screen boots then black then amazon screen then the fire screen.
tried every combination and dont know what to do.
So i've tried everything and cant seem to get it to work. Any suggestions?
Fixed
I fixed it. Guess I Messed up my recovery partition. Anyway I remembered from an old post that i had someone post the recovery file.
You must have root.
So copy recovery.img to the root of the device or /sdcard
then go to your command shell.
adb shell
su
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
dd of=$DEV if=/sdcard/recovery.img
exit
exit
adb reboot recovery
should reboot into recovery
then after downloading correct update.bin
adb sideload then filename of your update.
worked and am on my wiped device.
Thanks ...... to myself for messing it up and fixing it.