Related
hey thanks for the reply. Unfortunately superuser was not installed by the look of it so I have no su access.
I did install terminal emulator last night but could not find any commands that worked, I think this superuser thing got left out of my install somehow.
My wife has an exact same phone so I have copied all the filed off her internal sd, but I cant find a way to put them on my phone without su access or I reckon that might fix it.
you have to have root for the reboot command to work. use an app like 'on air (wifi disk)' or dropbox to get files onto your phone...
Sent from my GT-I9000 using XDA App
I have had my TP dual booted since February and have used CWM the whole time until a few weeks ago. I read posts and saw Rev's video touting the benefits of TWRP so I decided to try it. I installed GooManager and flashed it through that along with the 0814 CM nightly, that's where my problems started.
I had issues with the Wi-Fi signal staying gray and was no longer able to open Google apps. Also, I was not impressed with TWRP. It did what it was supposed to but I preferred CWM. I am aware that the issues I had was related to dirty flashing the ROM and an issue with my gapps install, so I am not blaming TWRP for that but I want TWRP gone anyway but it won't leave. The issues I was having did go away with a clean install of the ROM and gapps.
I used fastboot to reinstall CWM and then went through and uninstalled GooManager and deleted all the TWRP files I could find, except 1. When I explore the boot folder I found the ulmage.TWRP and I read somewhere that I need to delete it. Only problem is, it "can't be deleted", so says ES. If I plug into my computer will it let me delete it that way or is it there to stay? I would prefer to not screw something up by deleting a file that shouldn't be deleted. I can boot into CWM from Moboot and its fully functional but when I reboot to recovery I go to TWRP.
Any suggestions?
su
mount -o rw,remount /boot
rm /boot/uImage.TWRP
Sent from my SAMSUNG-SGH-I717
Xfanatic said:
I have had my TP dual booted since February and have used CWM the whole time until a few weeks ago. I read posts and saw Rev's video touting the benefits of TWRP so I decided to try it. I installed GooManager and flashed it through that along with the 0814 CM nightly, that's where my problems started.
I had issues with the Wi-Fi signal staying gray and was no longer able to open Google apps. Also, I was not impressed with TWRP. It did what it was supposed to but I preferred CWM. I am aware that the issues I had was related to dirty flashing the ROM and an issue with my gapps install, so I am not blaming TWRP for that but I want TWRP gone anyway but it won't leave. The issues I was having did go away with a clean install of the ROM and gapps.
I used fastboot to reinstall CWM and then went through and uninstalled GooManager and deleted all the TWRP files I could find, except 1. When I explore the boot folder I found the ulmage.TWRP and I read somewhere that I need to delete it. Only problem is, it "can't be deleted", so says ES. If I plug into my computer will it let me delete it that way or is it there to stay? I would prefer to not screw something up by deleting a file that shouldn't be deleted. I can boot into CWM from Moboot and its fully functional but when I reboot to recovery I go to TWRP.
Any suggestions?
Click to expand...
Click to collapse
You can also delete the uimage by going to webos and deleting it using Internalz pro.
Make a backup, just in case.
All you have to do is give ES root permissions to delete the TWRP image
Please use the search
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
All you have to do is give ES root permissions to delete the TWRP image
Please use the search
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
This won't directly work, because ES doesn't know that /boot is a nonstandard partition. It has permission to remove but the partition is readonly, thus you must remount it read/write first. The easiest way I think to do that is:
mount -o rw,remount /boot
on a root terminal (local, adb, novaterm, or xterm in webOS). Then delete the file from internalz/es/root explorer or just rm command.
Sent from my SAMSUNG-SGH-I717
I mentioned ES because the OP mentioned it and its free but yet ES can be set to mount the partition as RW just like Root Explorer...
But the easiest way AFAIK is using CyBoot in webOS
I'm just offering alternatives because had the OP bothered to do any work on his own he would have found out what we both are now spoon feeding him
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
I mentioned ES because the OP mentioned it and its free but yet ES can be set to mount the partition as RW just like Root Explorer...
But the easiest way AFAIK is using CyBoot in webOS
I'm just offering alternatives because had the OP bothered to do any work on his own he would have found out what we both are now spoon feeding him
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I searched this Site and Google and all I found was that I needed to delete the ulmage file not what to do if it wouldn't go away. I asked for help because I wasn't sure what to do and did not want to mess anything up. I know the way people who ask questions is treated on XDA so making a thread was a last resort.
Thank you to those that help me.
Sent from my Galaxy Nexus using xda app-developers app
es file explorer is a must have file manager/browser however some file permission changes dont work properly. when this happens i use root explorer from "jrummy" i have the full version that came with romtoolbox pro but the free lite version will do the trick.
haxin said:
es file explorer is a must have file manager/browser however some file permission changes dont work properly. when this happens i use root explorer from "jrummy" i have the full version that came with romtoolbox pro but the free lite version will do the trick.
Click to expand...
Click to collapse
I will have to try that.
Sent from my Galaxy Nexus using xda app-developers app
Hi,
When I got my Droid, I couldn't believe all the stuff that came preinstalled with the phone, so I started deleting everything that seemed unnecessary. Given the fact that I already reflashed the phone 20 times in the last week, I made a little script to help me out. I thought I would share it with you in case it comes handy to someone.
BIG NOTE 0: There's a system part that Motorola uses to get stuff from your phone. It's called Data Collector. Whenever any app crashes, it makes quite a big dump, with your network carrier, signal level, applications installed, applications running and a lot of stuff that isn't opt-in. In fact, one of the scripts (/system/bin/bugtogo.sh) can take screenshots of your phone. I don't like being spied, so I tried to remove it all. Cannot be certain though, but I would recommend you to remove, if you like your privacy, at least, the DataCollector apks, and to empty the bugtogo.sh script from /system/bin
BIG NOTE 1: I don't use this phone in the US, so I don't know if I'm breaking part of the CDMA support. It still shows up in every settings and I don't have any reason to think it won't work, but since I can't test it in anything except GSM/UMTS, I can't know it for sure.
BIG NOTE 2: The script will install Apollo (Music Player), Nova Launcher (homescreen replacement), and Cyanogenmod's Gallery app. If you don't want them and want to keep Blur and the default gallery (the script doesn't remove the music player just in case it's needed by some other app), then don't use this script, or modify it as you wish.
BIG NOTE 3: I am not responsible for anything if this causes a mess. Worst case scenario you'll need to flash back the system partition (fastboot flash system system.img), and then reroot your phone. You have been warned.
This is what it removes:
Code:
/system/app/DataCollection.apk
/system/app/DataCollection.odex
/system/app/DataCollectorProvider.apk
/system/app/DataCollectorProvider.odex
/system/app/DataCollectorService.apk
/system/app/DataCollectorService.odex
/system/app/blur-services.apk
/system/app/blur-services.odex
/system/app/blur_facebook.apk
/system/app/blur_facebook.odex
/system/app/blur_flickr.apk
/system/app/blur_flickr.odex
/system/app/blur_kaixin001.apk
/system/app/blur_kaixin001.odex
/system/app/blur_lastfm.apk
/system/app/blur_lastfm.odex
/system/app/blur_orkut.apk
/system/app/blur_orkut.odex
/system/app/blur_photobucket.apk
/system/app/blur_photobucket.odex
/system/app/blur_picasa.apk
/system/app/blur_picasa.odex
/system/app/blur_youtube.apk
/system/app/blur_youtube.odex
/system/app/vzw_vnav_DROID4.apk
/system/app/vzwapnpermission.apk
/system/app/MyVerizon.apk
/system/app/VerizonSSOEngine.apk
/system/app/MotoVzwAtCmdPlugin.apk
/system/app/MotoVzwAtCmdPlugin.odex
/system/app/VzwController.apk
/system/app/VzwController.odex
/system/app/VzwDeviceSetup.apk
/system/app/VzwDeviceSetup.odex
/system/app/VzwEntitlementService.apk
/system/app/VzwEntitlementService.odex
/system/app/VzwPhoneService.apk
/system/app/VzwPhoneService.odex
/system/app/VCast.apk
/system/app/VCastStub.apk
/system/app/VCastTones.apk
/system/app/VCASTVideo.apk
/system/app/VmmGallery.apk
/system/app/com.motorola.android.server.ims.apk
/system/app/com.motorola.android.server.ims.odex
/system/app/com.motorola.android.settings.aplogd.apk
/system/app/com.motorola.android.settings.aplogd.odex
/system/app/VmmBackupManager.apk
/system/app/VmmBackupManager.odex
/system/app/VmmGallery.odex
/system/app/SmartActionFW.apk
/system/app/SmartActionFW.odex
/system/app/SmartActions.apk
/system/app/SmartCarDock.apk
/system/app/SmartDock.apk
/system/app/ZumoService.odex
/system/app/ZumoService.apk
/system/app/WelcomeWebtop.odex
/system/app/WelcomeWebtop.apk
/system/app/WeatherWidget.apk
/system/app/VZWInstaller.apk
/system/app/Vvm.odex
/system/app/Vvm.apk
/system/app/VSuiteApp.apk
/system/app/VRDClient.apk
/system/app/VMMServiceInterface.odex
/system/app/VMMServiceInterface.apk
/system/app/VideoSurf.apk
/system/app/Videos.apk
/system/app/VideoCalling.apk
/system/app/Swype.apk
/system/app/SocialShare.odex
/system/app/SlingBox.apk
/system/app/SocialShare.apk
/system/app/SlackerRadio.apk
/system/app/RichLocationVzW.apk
/system/app/Protips.odex
/system/app/Protips.apk
/system/app/PlusOne.apk
/system/app/PhotoEditor.odex
/system/app/PhotoEditor.apk
/system/app/OnlineAlbum.odex
/system/app/OnlineAlbum.apk
/system/app/NflMobile.apk
/system/app/Netflix.apk
/system/app/MusicStore.apk
/system/app/MotorolaAccountSetup.apk
/system/app/MotorolaAccountSetup.odex
/system/app/MotoEmailConfig.apk
/system/app/MotoDockHelperService.odex
/system/app/MotoDockHelperService.apk
/system/app/MotoConnect.odex
/system/app/MotoConnect.apk
/system/app/MotoCastDashboard.odex
/system/app/MotoCastDashboard.apk
/system/app/motoactv.apk
/system/app/MotMusic.apk
/system/app/MotGallery.apk
/system/app/MCDownloadManager.odex
/system/app/MCDownloadManager.apk
/system/app/Kindle.apk
/system/app/JunosPulsePlaceholder.apk
/system/app/IlsVzW.apk
/system/app/HuxVmmSetting.odex
/system/app/HuxVmmSetting.apk
/system/app/HuxSnCClient.odex
/system/app/HuxSnCClient.apk
/system/app/GuidedTours.apk
/system/app/GuidedTours.odex
/system/app/HelpCenter.apk
/system/app/FileManager.apk
/system/app/FileManager.odex
/system/app/Facebook.apk
/system/app/DockService.odex
/system/app/DockService.apk
/system/app/DlnaSystemService.odex
/system/app/DlnaSystemService.apk
/system/app/DLNA.odex
/system/app/DLNA.apk
/system/app/DemoMode.odex
/system/app/DemoMode.apk
/system/app/ContactIce.odex
/system/app/ContactIce.apk
/system/app/Cmas.odex
/system/app/Cmas.apk
/system/app/BuaContactAdapter.odex
/system/app/BuaContactAdapter.apk
/system/app/BlurUpdater_VZW.odex
/system/app/BlurUpdater_VZW.apk
/system/app/BlurChooser.odex
/system/app/BlurChooser.apk
/system/app/BackupRestoreConfirmation.odex
/system/app/BackupRestoreConfirmation.apk
/system/app/BackupAssistanceClient.odex
/system/app/BackupAssistanceClient.apk
/system/app/ArcVideoEditorLite.apk
/system/app/android-syncservice-app.apk
/system/app/OutOfBox.odex
/system/app/OutOfBox.apk
/system/app/FriendFeed.apk
/system/app/FriendFeed.odex
/system/framework/com.motorola.MCDownloadLibrary.services_lib.jar
/system/framework/com.motorola.MCDownloadLibrary.services_lib.odex
/system/framework/com.motorola.motoconnect_lib.jar
/system/framework/com.motorola.motoconnect_lib.odex
/system/framework/com.motorola.vzw.vmm.helper.jar
/system/framework/com.motorola.vzw.vmm.helper.odex
/system/framework/com.motorola.vzw.vmm.util.jar
/system/framework/com.motorola.vzw.vmm.util.odex
/system/framework/com.scalado.android.photoeditor.jar
/system/framework/com.scalado.caps.jar
/system/framework/com.verizon.phone.jar
/system/framework/com.verizon.phone.odex
/system/framework/com.vzw.android.gex.jar
/system/framework/com.vzw.android.gex.odex
/system/framework/com.vzw.android.hux.jar
/system/framework/com.vzw.android.hux.odex
/system/framework/com.vzw.android.jar
/system/framework/com.vzw.android.odex
/system/framework/com.vzw.android.smart.jar
/system/framework/com.vzw.android.smart.odex
Instructions:
1. Root your phone if you haven't already
2. Install Busybox from Google Play if you haven't already
2. Uncompress the zip into your internal sdcard. You should get this:
Code:
/sdcard/removecrap/Apollo.apk
/sdcard/removecrap/Gallery2.apk
/sdcard/removecrap/com.teslacoilsw.launcher-1.apk
/sdcard/removecrap/remover.sh
3. Run from a terminal on the phone, or from adb (always as root)
sh /sdcard/removecrap/remover.sh
4. Wait until the phone reboots
5. 200 extra Mb of system and a lot more free ram for your apps. Oh, and Motorola won't get another bug report from you
EDIT: Ooops, Reupdated the zip file, it was deleting one extra file (motosignature inside the framework folder)
EDIT2: Didn't catch Carrier IQ's qer binary on /xbin. Unfortunately we can't touch those binaries since they're in the randisk, so I updated the script so it removes the logfile qe generates and replaces it with a folder so it can never write the scan results again (thank you bofh.bug for the links!)
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
highlandsun said:
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Probably OTAs will fail after running the script, but fixing it is as easy as reinstalling the system partition with fastboot and then applying the OTA
Sent from my DROID4 using xda app-developers app
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
arleslie said:
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
Click to expand...
Click to collapse
Were you able to fix the script so it works for CDMA users? Or, do you know what apps breaks it?
Very nice script, thanks. Easy way to run it by using Root Browser: open as script. But as for me QuickPick is better than ICS Galerry
Sent from my DROID4 using xda app-developers app
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Tanzior said:
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Click to expand...
Click to collapse
I did again the script for the jelly bean update. This time it removes less crap, since it seems Motorola left a bit less than on previous versions. This will remove the annoying "Foreign card" warning when you boot the phone with some non-verizon sim, the acoustic warning when you turn up the volume, smart actions and so on.
IT WON'T REMOVE THE APPS. It will leave them here:
Apps: /system/app/oldapps
system binaries: /system/bin/oldbin
Framework: /system/framework/oldframework
If you encounter any problem, you can simply move back the files through adb and the phone will be like before applying the script.
NOTE: Only tested on GSM. Probably won't work on CMDA since it's missing most of the Verizon stuff. If you can identify which apps are needed for CDMA to wokr again tell me and I'll update the script accordingly.
I run the script from ADB and worked like a charm. Been using it for 24hours and no problems so far, but you never know, so use at your own risk
Code:
[email protected]:~/Documents# adb push removecrap2.sh /sdcard/removecrap2.sh
[email protected]:~/Documents# adb shell
[email protected]_maserati:/ $ su
[email protected]_maserati:/ # sh /sdcard/removecrap2.sh
It works great, thank you. Good work.
Sent from my DROID4 using xda app-developers app
Hi to all, i found two app : ModemPanicReporter.apk and ModemStatsService.apk. What they are doing ? Maybe it is necessary to remove they too ? Removing these applications will improve battery life.
Sent from my DROID4 using xda app-developers app
I've got a problem and can't seem to find a fix.
Been rooted and s-off for a couple weeks now.
I started out getting rooted through htc dev unlock and flashing Capt's recovery (the one that erased everything). I installed Viper and after some persistence a good guy talked me into s-off.
No problems.
Last night I decided to get crazy and try a new ROM. I chose Bad Boyz cause OMJ always seems like a legit person.
So to my problem in the best details possible (my apologies if all this is unnecessary)...
I did a backup (of course) and installed Bad Boyz ROM. During setup I hit a bump. HTC was restoring my setup and apps and it got stuck so I rebooted. Immediately after that I finished setup and then Google play kept giving me an "error 920".
I went into recovery and using Capt's 2.7.0.7 twrp fixed permissions. That didn't work. I restored my Viper backup. That didn't work. Using Titanium Backup I wiped Google play store data then cache. That worked!
However, one problem solved a bigger one arises.
I no longer have the ability to move files from internal sd to external.
I've tried everything I can think of. I've checked on ES File Manager it says it's R/W but fails when tried. Same with Root Explorer and FX.
I've wiped and reinstalled Viper but same problem.
I've read MassStash's thread and tried to go into system/etc/permission/platform but it already shows as rw.
So I'm stumped. Can anyone help?
Sent from my 831C using XDA Free mobile app
stovo06 said:
I've got a problem and can't seem to find a fix.
Been rooted and s-off for a couple weeks now.
I started out getting rooted through htc dev unlock and flashing Capt's recovery (the one that erased everything). I installed Viper and after some persistence a good guy talked me into s-off.
No problems.
Last night I decided to get crazy and try a new ROM. I chose Bad Boyz cause OMJ always seems like a legit person.
So to my problem in the best details possible (my apologies if all this is unnecessary)...
I did a backup (of course) and installed Bad Boyz ROM. During setup I hit a bump. HTC was restoring my setup and apps and it got stuck so I rebooted. Immediately after that I finished setup and then Google play kept giving me an "error 920".
I went into recovery and using Capt's 2.7.0.7 twrp fixed permissions. That didn't work. I restored my Viper backup. That didn't work. Using Titanium Backup I wiped Google play store data then cache. That worked!
However, one problem solved a bigger one arises.
I no longer have the ability to move files from internal sd to external.
I've tried everything I can think of. I've checked on ES File Manager it says it's R/W but fails when tried. Same with Root Explorer and FX.
I've wiped and reinstalled Viper but same problem.
I've read MassStash's thread and tried to go into system/etc/permission/platform but it already shows as rw.
So I'm stumped. Can anyone help?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Sir, simple I had same issue... When I open ES Explorer, I find the Root Explorer Option, tick it off, Exit out go to Superuser and clear any ES Explorer opinion you find. Go open ES Explorer and press back key when it asks for Root Permissions, go to Root Explorer option and tick it back on, accept Root Permissions! Then you press and hold on Root Options, It'll pop up a R/W menu where you can remount system, and external card, etc... If that doesn't do it it's got me beat!!
Sent from my 831C using XDA Premium 4 mobile app
EVOuser94 said:
Sir, simple I had same issue... When I open ES Explorer, I find the Root Explorer Option, tick it off, Exit out go to Superuser and clear any ES Explorer opinion you find. Go open ES Explorer and press back key when it asks for Root Permissions, go to Root Explorer option and tick it back on, accept Root Permissions! Then you press and hold on Root Options, It'll pop up a R/W menu where you can remount system, and external card, etc... If that doesn't do it it's got me beat!!
Sent from my 831C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
EVOuser94 you better quit calling me sir! Make me think I'm old lol.
Not sure what the issue was. Just one particular file that appeared when changing ROMs wanted to be stubborn. Finally just deleted the file and put it behind me.
Thanks to Vinchenzop from the Viper team on the HTC Max & EVO 4g lte and MassStash for assistance in helping a brother out. Think I'd still be messing with it if it weren't for them ?
Anyway problem (kinda) solved
Sent from my 831C using XDA Free mobile app
2 words for you...
Root Explorer
Has never failed to do anything I have asked it to do.
Best $3-4 bucks I;ve ever spent.
stovo06 said:
EVOuser94 you better quit calling me sir! Make me think I'm old lol.
Not sure what the issue was. Just one particular file that appeared when changing ROMs wanted to be stubborn. Finally just deleted the file and put it behind me.
Thanks to Vinchenzop from the Viper team on the HTC Max & EVO 4g lte and MassStash for assistance in helping a brother out. Think I'd still be messing with it if it weren't for them ?
Anyway problem (kinda) solved
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Lol, you could always delete the file in recovery.... But yeah, what's the kinda part about still?
Sent from my 831C using XDA Premium 4 mobile app
BD619 said:
2 words for you...
Root Explorer
Has never failed to do anything I have asked it to do.
Best $3-4 bucks I;ve ever spent.
Click to expand...
Click to collapse
Got it.
Strongly agree.
EVOuser94 said:
Lol, you could always delete the file in recovery.... But yeah, what's the kinda part about still?
Sent from my 831C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Never figured out why it wouldn't move (with ES, Root Ex, or FX Ex). So I just said f it and deleted the folder. So problem (kinda) solved lol.
Check out TheMikMik
stovo06 said:
Got it.
Strongly agree.
Never figured out why it wouldn't move (with ES, Root Ex, or FX Ex). So I just said f it and deleted the folder. So problem (kinda) solved lol.
Check out TheMikMik
Click to expand...
Click to collapse
Lol, fair enough....
Sent from my 831C using XDA Premium 4 mobile app
I'll preface this with the fact that I flash my phones regularly (HTC One M8, One and Nexus before that) but have never bothered to mess around with my daughter's Nook HD+ 32GB. So I'm relatively savvy with ADB/Fastboot and flashing, but just not with this particular device.
Issue: My daughter's Nook has become so laggy as to be unusable. I did a little research and saw that there is a "trim" bug that affects certain chips used in the Nook, though mine - with an MBG4GA -11/2012- Rev 6 chip - doesn't seem to be one noted as an issue. However, I'm a bit confused on that front as my understanding is that the trim "issue" has to do with the application of trim to the ROM, which the stock Nook does not have anyway, so the above may be irrelevant. Just trying to figure out what may be causing this.
In any event, I'm trying to get to the bottom of this general slowdown which feel a lot like Windows after its been bogged down for awhile. Is this a known issue? Is there something that can be done short of factory resetting it and watching it progressively slow down again?
I haven't bothered to flash CM on it, because my daughter loves the Barnes and Noble aspects of the Nook - the book library and the ability for it to read the books out loud - and my understanding was that if I flash CM, I'd lose all that. Am I misinformed on this point?
Many, many thanks for any insight you can provide.
It is most likely a trim issue. Trim has to do with the condition of the emmc chip, not which rom it is running. So stock can be effected to. Best solution is to go to Play Store and download the app Lagfix and run it. The trim bug is not that devices need trimming, it is with certain chips the chip will brick when trying to run trim. Since you have the safe chip there should be not issue running it. You may need to go to my HD/HD+ CWM thread linked in my signature and root stock with my universal root. I think Lagfix requires root access.
Edit: and you are right about that last point.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar, thanks a bunch for that insightful response. I'll follow your instructions and report back. Mighty kind of you to have created and all-in-one root - makes things a whole lot easier!
So everything went smoothly. I'm rooted and applied the Unknown Sources mod and Lagfix works beautifully. However, I cannot, for the life of my remove the existing Adobe AIR - a file which needs to be updated in order to play some of the games my daughter has installed. When trying to update, I get an "application already exists" error, which, apart from getting Lagfix, is what prompted my desire to root in the first place (I've read tons of complaints on the BN board from the less savvy who are pissed at BN for not allowing this app to be updated by the Google Play store). Having root, I have manually renamed the APK, Frozen it through Titanium Backup, and attempted to uninstall it through Titanium Backup. No matter what I do, I still get this error.
On my phone, with root, a simple rename of an APK kills it. Here it seems this is not so simple. Any thoughts on how to successfully update Adobe Air? Or get the damned thing fully off the tablet so I can install it from the Play Store? Thanks a bunch.
godhamba said:
leapinlar, thanks a bunch for that insightful response. I'll follow your instructions and report back. Mighty kind of you to have created and all-in-one root - makes things a whole lot easier!
Click to expand...
Click to collapse
leapinlar said:
It is most likely a trim issue. Trim has to do with the condition of the emmc chip, not which rom it is running. So stock can be effected to. Best solution is to go to Play Store and download the app Lagfix and run it. The trim bug is not that devices need trimming, it is with certain chips the chip will brick when trying to run trim. Since you have the safe chip there should be not issue running it. You may need to go to my HD/HD+ CWM thread linked in my signature and root stock with my universal root. I think Lagfix requires root access.
Edit: and you are right about that last point.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
godhamba said:
So everything went smoothly. I'm rooted and applied the Unknown Sources mod and Lagfix works beautifully. However, I cannot, for the life of my remove the existing Adobe AIR - a file which needs to be updated in order to play some of the games my daughter has installed. When trying to update, I get an "application already exists" error, which, apart from getting Lagfix, is what prompted my desire to root in the first place (I've read tons of complaints on the BN board from the less savvy who are pissed at BN for not allowing this app to be updated by the Google Play store). Having root, I have manually renamed the APK, Frozen it through Titanium Backup, and attempted to uninstall it through Titanium Backup. No matter what I do, I still get this error.
On my phone, with root, a simple rename of an APK kills it. Here it seems this is not so simple. Any thoughts on how to successfully update Adobe Air? Or get the damned thing fully off the tablet so I can install it from the Play Store? Thanks a bunch.
Click to expand...
Click to collapse
Part of the problems with BN installed apps is they are automatically reinstalled online by BN when you try to remove them. Have heard of no way of defeating that.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Part of the problems with BN installed apps is they are automatically reinstalled online by BN when you try to remove them. Have heard of no way of defeating that.
Click to expand...
Click to collapse
That's a shame because BN's version of AIR is insufficient to run many different apps.
godhamba said:
That's a shame because BN's version of AIR is insufficient to run many different apps.
Click to expand...
Click to collapse
Part of the issue might be that Air is installed as a /system app by BN and Play Store tries to install it as a traditional /data app. Try getting the new version of the Air apk file from another device, renaming the apk exactly like it is named in /system/app on BN, and use your root file manager to replace the existing apk with the new one. You may have to clear the data in /data/data for Air before it operates properly. This may not work and may lock up the system so do a CWM backup of your device first so you can restore it if need be.
Sent from my BN NookHD+ using XDA Premium HD app
I came back to post that I had replaced the APK with the latest one that I found online, and it worked perfectly, only to see you had already posted the solution! I must have picked up on your brainwaves.
BN should be ashamed of themselves for, in essence, crippling this device by not allowing the update of core apps. Why they made this a system app is beyond me (perhaps to stop unsavvy folks from deleting it).
leapinlar said:
Part of the issue might be that Air is installed as a /system app by BN and Play Store tries to install it as a traditional /data app. Try getting the new version of the Air apk file from another device, renaming the apk exactly like it is named in /system/app on BN, and use your root file manager to replace the existing apk with the new one. You may have to clear the data in /data/data for Air before it operates properly. This may not work and may lock up the system so do a CWM backup of your device first so you can restore it if need be.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse