Hello,
thank you in advance for your help.
Facts: rooted ICS 4.0.3 IMLK74K.DE_epad-9.4.2.15-20120221
Problem: Everytime when i like to open Accounts & Syncronisation (don't know the exact translation in german it's called "Kontakte & Synchronisation") the dialog suddenly quits.
I installed log viewer to check what's going on, you can see the error message in the Screenshot.
So i think the problem is, that i deleted Pcsynclauncher.apk from ASUS, my question is, can anyone tell me how to extract that file from the Stock ROM i downloaded from here or can anyone post the file on the board?
THX
DidierSchnee said:
Hello,
thank you in advance for your help.
Facts: rooted ICS 4.0.3 IMLK74K.DE_epad-9.4.2.15-20120221
Problem: Everytime when i like to open Accounts & Syncronisation (don't know the exact translation in german it's called "Kontakte & Synchronisation") the dialog suddenly quits.
I installed log viewer to check what's going on, you can see the error message in the Screenshot.
So i think the problem is, that i deleted Pcsynclauncher.apk from ASUS, my question is, can anyone tell me how to extract that file from the Stock ROM i downloaded from here or can anyone post the file on the board?
THX
Click to expand...
Click to collapse
I'm guessing you did not unlock the bootloader yet Try extracting the zip I have attached to your "C:\" , install adb on your pc then run the following command
Code:
adb push C:\PCSyncLauncher.apk /system/app
Code:
adb push C:\PCSyncLauncher.odex /system/app
Follow this guide if you need help installing ADB (http://www.theandroidsoul.com/how-to-install-adb-on-windows-full-guide/)
Thank your for your help.
Had some problems with adb push (permission denied, adb remount gave me operation failed), so i copied the files on the prime and "installed" them with the terminal!
problem solved.
DidierSchnee said:
Thank your for your help.
Had some problems with adb push (permission denied, adb remount gave me operation failed), so i copied the files on the prime and "installed" them with the terminal!
problem solved.
Click to expand...
Click to collapse
Great job thinking out-side of the box. This is how a Dev is born, hope you will join us soon
thx, but there is only one problem called time
Sent from my Transformer Prime TF201 using Tapatalk 2
And I still have that problem, even after installing files
Code:
[email protected]:/data/system/dropbox # cat *
Process: com.android.settings
Flags: 0x8be45
Package: com.android.settings v15 (4.0.3-WW_epad-9.2.2.6-20120525)
Build: asus/WW_epad/TF101G:4.0.3/IML74K/WW_epad-9.2.2.6-20120525:user/release-keys
java.lang.IllegalArgumentException: Unknown package: com.asus.pcsynclauncher
at android.os.Parcel.readException(Parcel.java:1331)
at android.os.Parcel.readException(Parcel.java:1281)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationEnabledSetting(IPackageManager.java:2423)
at android.app.ApplicationPackageManager.getApplicationEnabledSetting(ApplicationPackageManager.java:1153)
at com.android.settings.accounts.ManageAccountsSettings.updateUi(ManageAccountsSettings.java:198)
at com.android.settings.accounts.ManageAccountsSettings.onStart(ManageAccountsSettings.java:105)
at android.app.Fragment.performStart(Fragment.java:1532)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:862)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1032)
at android.app.BackStackRecord.run(BackStackRecord.java:622)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1382)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:426)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4424)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
at dalvik.system.NativeStart.main(Native Method)
1|[email protected]:/data/system/dropbox # ls -la /system/app/PCSyncLauncher.*
-rw-r--r-- root root 44092 2013-05-26 18:01 PCSyncLauncher.apk
-rw-r--r-- root root 18968 2013-05-26 18:01 PCSyncLauncher.odex
adb push didn't work for me either, so copied files randomly. I tried to find the cause but failed. My guess is that somewhere in the system must be written information about this package, but it isn't and I don't know where it should be.
Ok, now I even tried something else but still have negative result:
Code:
pm install /sdcard/Download/PCSyncLauncher.apk
pkg: /sdcard/Download/PCSyncLauncher.apk
Failure [INSTALL_FAILED_DEXOPT]
need a different version
Hi, I just took the poor decision of uninstalling the com.asus.pcsynclauncher package from my TF201 , so I am getting the same exception when trying to access accounts & sync.
I just tried the APK supplied by MasterZen88, however I get error log entries "Package com.asus.pcsynclauncher has mismatched uid: 10003 on disk, 10053 in settings" and a "dexopt failed on .... [email protected]' res = 65280" when installing, which ends up failing.
I assume it is because my ICS version is different: IML74.WW_epad-9.4.2.28-20120525
What do you think? If my assumption is correct, is there anyone that can supply me with the right APK and ODEX?
Thank you for your help.
Related
I ran the Snowball Mod without a hitch. I then tried to run the update but it won't run for some reason. The window flashes some text quickly but then closes so I'm not even really sure why it's not working. Anyone run into this or have any ideas. Thanks in advance!
I haven't had the time to try out the snowball mod, yet -- so I can't offer any advice. But, I would post the issue in the development thread, that's where the most help will be.
Swyped from my B&N Nook Tablet.
Try running it from a command line to keep it up and be able to read any text.
Also, there is a log.txt, if you post that, it can be more helpful.
Yeah I was goin to but I don't have enough posts. I was hoping someone would see it here.
Well... if you post your log.txt and start it from a command-line window rather than double clicking the update.bat, then we can take a look at what's up.
Log file says:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
Command line:
Snowball is reporting: v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an "outdate"?
Thanks a lot!
There is no v2.0.2 update package in the zip folder. I renamed v2.0.1 to v2.0.2 and ran. Not sure if this was a good thing to do or not. Any help or direction would be appreciated. Thanks.
No write permissions
Tried to install snowball mod from a macbook pro by just running the snowball.sh. Started up and the B&N stuff was all there, although it looked like it ran without a hitch.
Looked at the log file in the snowball-mod folder and saw a lot of "Read-only file system" business. The first few lines being:
unzip: can't open nook-update-package.zip, nook-update-package.zip.zip, nook-update-package.zip.ZIP^M
rm failed for nook-update-package.zip, Read-only file system^M
Installing nook-update-package...
cd: can't cd to /mnt/media/nook-update-package^M
sh: Can't open install^M
rm failed for /mnt/media/nook-update-package, No such file or directory^M
Click to expand...
Click to collapse
How do you suggest I get around that?
conundrum768 said:
I haven't had the time to try out the snowball mod, yet -- so I can't offer any advice. But, I would post the issue in the development thread, that's where the most help will be.
Swyped from my B&N Nook Tablet.
Click to expand...
Click to collapse
We need 10 legit posts before we are allowed to post in the dev forum
Robotronik said:
Tried to install snowball mod from a macbook pro by just running the snowball.sh. Started up and the B&N stuff was all there, although it looked like it ran without a hitch.
Looked at the log file in the snowball-mod folder and saw a lot of "Read-only file system" business. The first few lines being:
How do you suggest I get around that?
Click to expand...
Click to collapse
Huh... this is weird... /mnt/media should not be read-only... although, I suppose, perhaps if you had it USB mounted, it might end up read-only.
Ensure that you have Automatic USB mounting turned off before you run the script.
You can actually push this update via wifi if you mod the update.bat (or update.sh for linux users) file.
Just turn on ADB Wifi (I prefer adbWireless app) and add the following to your bat file:
Code:
echo Waiting for device...
[B]adb connect XXX.XXX.XXX.XXX:XXXX[/B]
adb wait-for-device
...
adb shell "chmod 755 /data/local/tmp/update-package.sh ; su -c /data/local/tmp/update-package.sh" >> log.txt
if exist reboot adb reboot
[B]adb connect XXX.XXX.XXX.XXX:XXXX[/B]
echo INSTALLATION SUCCESSFUL
Use your IPort given to you by your ADB Wifi app in place of XXXs. Then just run the .bat!
Run from cmd if you don't want the output to vanish right away.
cfoesch said:
Ensure that you have Automatic USB mounting turned off before you run the script.
Click to expand...
Click to collapse
Okay, that got me a little further. Now:
Extracting nook-update-package...
Archive: nook-update-package.zip
creating: nook-update-package/data/
unzip: can't set permissions of directory 'nook-update-package': Operation not permitted
unzip: exiting
Installing nook-update-package...
sh: Can't open install
Click to expand...
Click to collapse
More permissions issues...
Still posting here because I don't have the 10 total posts to go in the Dev forum...
Anyway, I did the factory reinstall, and reran the snowballmod update. It said the root was still there, so I commented out that check from the snowball.sh, reran the package and everything went swimmingly.
Now, for the update:
The terminal spits out this:
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7 KB/s (46 bytes in 0.006s)
Snowball is reporting: v2.0.2
.zipte-package-v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an 'outdate'?
Click to expand...
Click to collapse
Where the log file gives me:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
Click to expand...
Click to collapse
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
same
Robotronik said:
Still posting here because I don't have the 10 total posts to go in the Dev forum...
Anyway, I did the factory reinstall, and reran the snowballmod update. It said the root was still there, so I commented out that check from the snowball.sh, reran the package and everything went swimmingly.
Now, for the update:
The terminal spits out this:
Where the log file gives me:
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
Click to expand...
Click to collapse
I AM HAVING THE SAME PROBLEM.MYBE..I need help some plz make a better howtos for dummies m
The first thing you need to do, if you have no clue what you're doing, is post the contents of the log file in the snowballmod folder.
The ".zipte-package-v2.0.2" seems to be related to adb shell "snowball-ver" returning DOS formatted text, even though you're in a *nix. I really did not expect this to happen with the linux and osx versions of adb, but apparently, they perform the same as cygwin... (cygwin I expected, after all, the adb.exe is a windows program). I will fix the update scripts to take that into account.
Code:
unzip: can't set permissions of directory 'nook-update-package': Operation not permitted
This message is reported by unzip when it is run by a non-root user on the /mnt/media partition.
You do _NOT_ have to run snowball-update though if you've installed snowball-mod fresh with the most recent version.
robtlebel said:
I AM HAVING THE SAME PROBLEM.MYBE..I need help some plz make a better howtos for dummies m
Click to expand...
Click to collapse
The changes made to the script were posted here:
Robotronik said:
Now, for the update:
The terminal spits out this:
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7 KB/s (46 bytes in 0.006s)
Snowball is reporting: v2.0.2
.zipte-package-v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an 'outdate'?
Where the log file gives me:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
Click to expand...
Click to collapse
I had the same issue with the name of the update file being called incorrectly: ".zipte-package-v2.0.2". With that output the script is looking for a file of that name and it's not finding it. I just changed the value of the variable ${VERSION} to v2.0.2 (since that was what was being reported by Snowball as my current version) and all worked after that.
Easy to fix temporarily:
-open "update.sh" in a text editor
-go to line 66 and change
VERSION=`awk '//{ print $2 }' snowball.version`
Click to expand...
Click to collapse
to
VERSION=v2.0.2
Click to expand...
Click to collapse
or whatever version yours shows to be running (v2.0.1, etc). Something tells me it might be important to input the correct current version number in
-save and close the file and rerun it.
EDIT: or wait until cfoesch fixes the scripts
Scripts should be updated. I changed the awk program from just "//{ print $2 }" to "//{ sub('\r', '', $2); print $2 }" ... this means that it works both ways... *insert your favorite "both ways" joke here*
It should also detect if you haven't turned off automount, and warn you about it. If the nook ends up rebooting, then it would tear the USB mount and could cause file corruption. I got around it by putting things in /data rather than /mnt/media, but then realized, if it has to reboot, then it could cause trouble. So better, to just warn them that automount was on, and quit out.
It also detects better if something went wrong in the installation process, and should report that installation has failed, rather than successful under all cases.
Things may have gotten broken in the process, so keep up the bug reports.
I just can't stop Nookin' Around.........god i need to sleep
I decided to check out the update.sh script (can only go so far currently since I have the latest update).
At least for me, (Ubuntu Linux 11.10) I figured something out about the $OSTYPE call to set the $adb variable. I could echo $OSTYPE in the terminal and got a response, but could not echo it in any scripts. Ended up finding the "uname -o" call and that seems to have gotten it to work, although the printout is different.
snowball-update# echo $OSTYPE
linux-gnu
snowball-update# uname -o
GNU/Linux
Changed lines 7 & 8 and seems to have worked:
case `uname -o` in
GNU*|linux*|Linux*)
Now this last part is probably something on my end but: update.sh: 62: ./adblinux: Permission denied
Thanks again for the work (and everyone else involved in rooting/hacking these things )
Indeed. $OSTYPE seems to be specific to bash, and not all sh implementations.
If you don't mind could you do this command and give me the output? "ls -l /bin/sh" and "sh --version" Those two commands should explain exactly which implementation of sh you have. (For instance, on the NT with snowball-mod, the sh is a minimal implementation, and does not support $OSTYPE. But on most OSes I've seen sh is actually a statically linked bash, as it is the most widely used shell scripting language.)
The case on that you provided though could be a poor choice, as GNU*) would match GNU/freebsd, or GNU/openbsd, or GNU/anykernel. Sure it is unlikely, but it is possible.
The permissions issue is not entirely your end, but it is an expected artifact of extracting from a zip file. Although, is suppose performing a chmod 755 on it prior to use would be a good idea in general.
Is there a way to root the new 45.4.13 OTA that rolled out? I have tried all the root methods listed on: http://forum.xda-developers.com/showpost.php?p=20331601&postcount=5
Without any luck!
I want to add that I was rooted before applying the OTA.
stevetrooper said:
Is there a way to root the new 45.4.13 OTA that rolled out? I have tried all the root methods listed on: http://forum.xda-developers.com/showpost.php?p=20331601&postcount=5
Without any luck!
Click to expand...
Click to collapse
Wait, what? Even photon-torpedo didn't work?
any updated status with this yet?
I'm curious too...
Please keep us apprised and a system dump would be helpful from someone who has the update.
Sent from my MB855 using xda app-developers app
Shad0wguy said:
Wait, what? Even photon-torpedo didn't work?
Click to expand...
Click to collapse
Nope, tried it multiple times.
Torpedo worked for me this evening.
Sent from my MB855 using Tapatalk 2
Torpedo worked for me, AIO did not.
I still laugh when ppl are still using the AIO root when its been so unreliable in the past. The photon-torpedo method has ALWAYS worked and I don't know why people aren't using the torpedo method to root by default.
OP you must be doing something wrong because the torpedo method still works any many folks have confirmed that.
Glad to hear its still working, here is the error I get:
$ ./photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
ddxSigGiveUp: Closing log
./photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface: invalid ELF header; ignored.
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
ddxSigGiveUp: Closing log
Then looking at the log:
$ cat /var/log/Xorg.0.log
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
(WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
(WW) xf86OpenConsole: VT_GETSTATE failed: Bad file descriptor
ddxSigGiveUp: Closing log
following for further developments..
Reboot has changed the message slightly...
$ /data/tmp/photon-torpedo.sh
/data/tmp/photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
/data/tmp/photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface:
invalid ELF header; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
stevetrooper said:
Reboot has changed the message slightly...
$ /data/tmp/photon-torpedo.sh
/data/tmp/photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
/data/tmp/photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface:
invalid ELF header; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
Click to expand...
Click to collapse
You obviously have not done the root torpedo method before or else you would know that the big ole message you just copied is anticipated and you don't need to worry. You have root successfully.
Just follow this video
http://www.youtube.com/watch?v=zb3Yh_NmSBk
ericdabbs said:
You obviously have not done the root torpedo method before or else you would know that the big ole message you just copied is anticipated and you don't need to worry. You have root successfully.
Just follow this video
http://www.youtube.com/watch?v=zb3Yh_NmSBk
Click to expand...
Click to collapse
Unfortunately the script does not give me the # prompt. So when you run the install-su script it fails. I found others that had the same problem and they never figured out how to get it to work.
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface: invalid ELF header; ignored.
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
Please consult the The X.Org Foundation support at http://wiki.x.org for help.
ddxSigGiveUp: Closing log
$ ./install-su.sh Usage: mount [-r] [-w] [-o options] [-t type] device directory cp: /system/bin/su: Read-only file system Unable to chmod /system/bin/su: Read-only file system Usage: mount [-r] [-w] [-o options] [-t type] device directory rm failed for /lib/libphoton-torpedo.so, Permission denied.
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
tiny2nz said:
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
Click to expand...
Click to collapse
Thanks, I have tried with Android Terminal Emulator and adb shell from my PC, neither worked.
tiny2nz said:
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
Click to expand...
Click to collapse
That's a very valid point. After the first soak, many people they needed to use computer, not emulator, for it to work. Wonder is s/he has the right computer drivers?
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
stevetrooper said:
Thanks, I have tried with Android Terminal Emulator and adb shell from my PC, neither worked.
Click to expand...
Click to collapse
Do you have the right drivers? i.e. - do other adb commands work?
willysp said:
That's a very valid point. After the first soak, many people they needed to use computer, not emulator, for it to work. Wonder is s/he has the right computer drivers?
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
Do you have the right drivers? i.e. - do other adb commands work?
Click to expand...
Click to collapse
I downloaded the drivers from the photon torpedo thread. adb works just fine, can push the file to the photon, without any errors. I even tried adb on 2 different computers, Windows XP and the other Windows 7.
The photon-torpedo.sh is very simple:
#!/bin/bash
umask 0
LD_AUDIT="libpcprofile.so" PCPROFILE_OUTPUT="/lib/libphoton-torpedo.so" /usr/bin/X
cat /data/tmp/libphoton-torpedo.so > /lib/libphoton-torpedo.so
LD_AUDIT="libphoton-torpedo.so" /usr/bin/X
When I look in /lib the file libphoton-torpedo.so exists and has a timestamp from when I ran, so its catting the file correctly.
I don't get the # prompt, so running install-su.sh does not work.
Found this in the photon-torpedo thread in Development:
Sparky_McBurning said:
I figured out the problem and a fix.
Problem:
If /lib/libphoton-torpedo.so was not removed from /lib before the OTA update, the permissions are updated to no longer be over-writable, so the /data/tmp/photon-torpedo.sh step that 'cat's libphoton-torpedo cannot re-write the file with new permissions.
Fix:
Update photon-torpedo.sh to use a different filename for libphoton-torpedo.so. I used libphoton-torpedo2.so. No problems. Just make sure you remove any versions of libphoton-torpedo.so from /lib/ after rooting, and you won't have this problem in the future.
Click to expand...
Click to collapse
com.bn.cloud.svc permission issue: What does a healthy ''packages.xml" look like?
I'm running a rooted Nook 1.4.3, and somewhere in my customization, I've run into an odd permissions issue.
Main question: Can anyone with a Nook 1.4.3 whose B&N Shop is working paste their /data/system/packages.xml here so I can check mine against it?
Main problem: The B&N Shop can't connect to anything. Basically my device has no access to the B&N cloud.
Looking at the logs, I see this a lot:
Code:
W/ActivityManager( 1294): Unable to start service Intent { act=com.bn.cloud.IRequestHandler }: not found
Looking at logcat while the tablet boots, I see this related section:
Code:
I/PackageManagerService( 1294): /system/app/BnCloudRequestSvc.apk changed; collecting certs
W/PackageManagerService( 1294): Signature mismatch for shared user : SharedUserSetting{40597710 com.bn.cloud/10032}
E/PackageManagerService( 1294): Package com.bn.cloud.svc has no signatures that match those in shared user com.bn.cloud; ignoring!
...
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.EXECUTE_REQUEST in package com.bn.nook.drpreader
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.RECEIVE_NOTIFICATION in package com.bn.nook.drpreader
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.EXECUTE_REQUEST in package com.bn.nook.social
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.EXECUTE_REQUEST in package com.bn.nook.quickstart
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.RECEIVE_NOTIFICATION in package com.bn.nook.quickstart
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.EXECUTE_REQUEST in package com.bn.nook.reader.activities
So my best guess is that I borked something in my packages.xml so PackageManager thinks my 'BnCloudRequestSvc.apk' is wrong and completely disables the cloud service that the shop (and other com.bn.* apps) need.
I've tried wiping my dalvik cache and running 'fix_permissions' from the bootable CWM sdcard I used to root the thing, but still no luck.
I'd love to compare my packages.xml to someone who has a working shop, or hear any other suggestions anyone may have about what may be going wrong here, like why does the Package Manager say "/system/app/BnCloudRequestSvc.apk changed; collecting certs"?
Solved!
I solved this issue by doing the following:
Delete /data/system/packages.xml
Reboot -> This regenerates /data/system/packages.xml (ignore all force-closes, they are expected)
Power off
Power on with CWM SD Card, go into "advanced" and "Fix Permissions" (Built my SD Card using these instructions: http://forum.xda-developers.com/showthread.php?t=1466583)
Reboot
Once it came back up, everything was working great!(*)
(*) One small caveat-> After that last reboot, it came up with the 'Homecatcher" app doing something incredibly weird: It was flickering and I couldn't actually choose a launcher... Thankfully I happened to reorient from portrait to landscape, then back to portrait, and it came out of it and began working just fine.
Now that I have the thing working again, I've compared my prevous "broken" packages.xml to the new working packages.xml, and found that my actual original problem was that I was missing a <packace> section for the com.bn.cloud.svc library.
That wasn't *quite* all...
Noting further steps here I had to take to get everything working again after this issue... escapde.
Removing packages.xml and running 'fix permissions' isn't quite the whole story. I also had to:
Reinstall all local apps to re-request their permissions:
Code:
[in adb shell]:
for app in /data/apps/*.apk; do pm install -r $app; done
Modify the permissions of all existing downloaded books and magazines in /data/media so it matches the new B&N UID:
Code:
[in adb shell]:
busybox ps
... Find the UID that all the com.bn.* apps are running with
... In my case this was '10020', aka 'app_20'
busybox chmod 10020.10020 -R /data/media/Books/*
busybox chmod 10020.10020 -R /data/media/Magazines/*
hi guys, I hope you can help.. I really googled a lot about this, and also made many tests on my phone and waste a lot of time, but couldn't find a solution yet.. also this seems to be affecting many other people, so I don't understand how is possible nobody found a fix for that until now..
(I'm posting in general section because this seems to affect any kind of phones running cm10.1 + gapps)
the problem is that if I go to manage apps > running apps, I see Media process (DownloadService) always running! that could drain my battery and/or download data, in any case I don't see a point in having it always running, so I would like to get rid of it!
what I discovered so far is that the process is related to both gapps and Downloadprovider.apk package included in any CM10.1 build, in fact:
1. the process starts appearing only after installing the gapps (I use a very minimal 4.2 gapps package, about 10mb only)
2. if I delete Downloadprovider.apk package from /System/App, the process doesn't appear anymore
The problem is that if I delete the Downloadprovider.apk package then I start getting gapps related FC's and phone becomes unstable (and very probably will not be possible to download anymore things from the browser and/or play store)!
So what could I do to safely get rid of that process? Maybe disable or freeze some other apps/processes? But I wouldn't know what to disable exactly..
guys please help me I am really getting crazy with that! also that could help many other people :good:
thanks a lot in advance
EDIT: maybe it was related to Maps since I installed maps 7.x I don't see that process anymore!
moly82 said:
hi guys, I hope you can help.. I really googled a lot about this, and also made many tests on my phone and waste a lot of time, but couldn't find a solution yet.. also this seems to be affecting many other people, so I don't understand how is possible nobody found a fix for that until now..
(I'm posting in general section because this seems to affect any kind of phones running cm10.1 + gapps)
the problem is that if I go to manage apps > running apps, I see Media process (DownloadService) always running! that could drain my battery and/or download data, in any case I don't see a point in having it always running, so I would like to get rid of it!
what I discovered so far is that the process is related to both gapps and Downloadprovider.apk package included in any CM10.1 build, in fact:
1. the process starts appearing only after installing the gapps (I use a very minimal 4.2 gapps package, about 10mb only)
2. if I delete Downloadprovider.apk package from /System/App, the process doesn't appear anymore
The problem is that if I delete the Downloadprovider.apk package then I start getting gapps related FC's and phone becomes unstable (and very probably will not be possible to download anymore things from the browser and/or play store)!
So what could I do to safely get rid of that process? Maybe disable or freeze some other apps/processes? But I wouldn't know what to disable exactly..
guys please help me I am really getting crazy with that! also that could help many other people :good:
thanks a lot in advance
Click to expand...
Click to collapse
Maybe you have some program/app installed which uses the download manager? Some app trying to download an update outside of the regular mechanism? I don't see DownloadService running on my phone unless I instructed it to download something. Do you notice anything downloadmanager/media related in logcat? If in doubt, attach the phone to a PC, run the following commands and attach the resulting file ('attach_me.txt') here:
Code:
adb shell 'ps; echo -----------;logcat -v time -b main -b system -b events -d;echo -----------;dumpsys;' > attach_me.txt
Use the full path to adb if you need to.
This shows the currently running processes (ps), the contents of the main, system and event logs (logcat) and a snapshot of the current state of your phone (dumpsys). If there is anything there you don't want to show to the whole world edit the resulting file before attaching it here.
thanks a lot for the reply my friend
tonight at home I think I will be able to run the adb command you suggested me (in my home computer I have sdk installed)
so far I checked logcat in terminal ("logcat |grep edia" and "logcat |grep ownload") and this is what I got:
$ su
# logcat |grep edia
D/Vold ( 1197): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 1197): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/PackageParser( 1626): No actions in intent filter at /data/app/org.wikipedia-1.apk Binary XML file line #39
I/ActivityManager( 1626): Start proc android.process.media for broadcast com.android.providers.media/.MtpReceiver: pid=1765 uid=10011 gids={50011, 1015, 1023, 1024, 1028, 2001, 3003, 3007}
V/ActivityThread( 1765): android.process.media white listed for hwui
D/SystemUIService( 1701): loading: class com.android.systemui.media.RingtonePlayer
D/SystemUIService( 1701): running: [email protected]
W/ContextImpl( 1626): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1458 android.bluetooth.BluetoothHeadset.:273 android.bluetooth.BluetoothAdapter.getProfileProxy:1155 android.media.AudioService.getBluetoothHeadset:2198 android.media.AudioService.access$2800:104
W/ContextImpl( 1626): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1458 android.bluetooth.BluetoothA2dp.:160 android.bluetooth.BluetoothAdapter.getProfileProxy:1158 android.media.AudioService$AudioServiceBroadcastReceiver.onReceive:4087 android.app.LoadedApk$ReceiverDispatcher$Args.run:758
$ su
# logcat|grep ownload
I/ActivityManager( 1624): Start proc com.google.android.youtube for broadcast com.google.android.youtube/.core.transfer.DownloadService$BootReceiver: pid=2305 uid=10050 gids={50050, 3003, 1015, 1006, 1028}
W/ActivityManager( 1624): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
W/ActivityManager( 1624): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
I'm attaching also screenshots of the process I'm talking about
EDIT: I reinstalled everyting from scratch as a new build by quarx came out.. it seems that installing only cm build + minimal gapps, that process doesn't show up. Later after I installed back all my apps (via app2zip flashable zip) the process showed up again.. so probably you are right and there is a certain app using that process.. but how can I understand which one has relation with that service? maybe YouTube as i see it mentioned in logcat?
delete
i could generate the logs you asked without using the pc but using the phone terminal and multiple commands.. i'm uploading them to my dropbox links are below thanks in advance..
http://db.tt/gJLBYeT7
http://db.tt/OahQ8Zf7
http://db.tt/KPUTy4et
YAFU what happened to you?
it seems to me after I installed latest maps 7.x the media > download process is not appearing anymore in running processes.. maybe it was related to sh*tty maps??? :fingers-crossed:
I uninstalled com.android.updater, and fow a while everything was OK. Then today the battery was depleted, and after recharging the phone went into a bootloop. I had to install com.android.updater again, and after that everything went back to normal.
How did I find out it was com.android.updater? When in a bootloop, the Android system is actually already up and running. I was able to do adb logcat. There I saw that the system was looking for com.android.updater.
Code:
04-18 17:07:20.036 7445 7606 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-4
04-18 17:07:20.036 7445 7606 E AndroidRuntime: java.lang.RuntimeException: System error: connot find system app : com.android.updater
Note that I'm using the original China Stable ROM version 10.4.4.0(PFKCNXM), all stock, locked bootloader, not rooted. Except for the customization that we can do without root: Install Google services etc, and disable/uninstall packages through ADB.
I didn't want to upgrade to MIUI 11 because I've seen reports of it being slow and draining battery, and I want the NFC functionality, so I had to stick with China ROM.
I can't find that in my Mi 9T Pro (using the latest xiaomi.eu 20.3.27)
When I search Update I find pl.zdunex25.updater, com.android.dynsystem and com.google.android.configupdater and have all 3 frozen with SDMaid.
DeepAnger said:
I can't find that in my Mi 9T Pro (using the latest xiaomi.eu 20.3.27)
When I search Update I find pl.zdunex25.updater, com.android.dynsystem and com.google.android.configupdater and have all 3 frozen with SDMaid.
Click to expand...
Click to collapse
Oh I'm using the China Stable ROM version 10.4.4.0(PFKCNXM), sorry for not mentioning it earlier. I think custom ROMs might be immune to this sort of thing. Thanks, I've updated the post with my ROM info.
I uninstalled com.android.updater, and i cant restore it(. Do you can help me? I use redmi 4 and firmware miui_HMNote4Global_V8.5.6.0.MBFMIED_6f4b63e4fd_6.0. How i can restore one app whitout reinstall all?(
Brooont said:
I uninstalled com.android.updater, and i cant restore it(. Do you can help me? I use redmi 4 and firmware miui_HMNote4Global_V8.5.6.0.MBFMIED_6f4b63e4fd_6.0. How i can restore one app whitout reinstall all?(
Click to expand...
Click to collapse
Process of restoring generally depends on how did you 'uninstall' - please precisely describe how you did
I connect phone to computer with adb, click "debloater" and write com.android.updater in "custom" field, and click uninstall.
Brooont said:
I connect phone to computer with adb, click "debloater" and write com.android.updater in "custom" field, and click uninstall.
Click to expand...
Click to collapse
Still depending on how your debloater worked, try the folowing command(s):
adb shell cmd package install-existing com.android.updater
if it fails then:
adb shell pm enable com.android.updater
First make sure that adb connection is properly established:
adb devices
C:\adb_run\bin>adb devices
List of devices attached
NF8LHYVSNJZTGY7L recovery
C:\adb_run\bin>adb shell pm enable com.android.updater
adb server is out of date. killing...
* daemon started successfully *
/sbin/sh: pm: not found
C:\adb_run\bin>adb shell cmd package install-existing com.android.updater
/sbin/sh: cmd: not found
C:\adb_run\bin>
Something wrong...
Brooont said:
C:\adb_run\bin>adb devices
List of devices attached
NF8LHYVSNJZTGY7L recovery
C:\adb_run\bin>adb shell pm enable com.android.updater
adb server is out of date. killing...
* daemon started successfully *
/sbin/sh: pm: not found
C:\adb_run\bin>adb shell cmd package install-existing com.android.updater
/sbin/sh: cmd: not found
C:\adb_run\bin>
Something wrong...
Click to expand...
Click to collapse
Something wrong/strange with your adb deamon
Btw, you used certain Debloater - you should better ask in the corresponding Debloater forum/thread how to un-do
Тhanks!
wpyh said:
I uninstalled com.android.updater, and fow a while everything was OK. Then today the battery was depleted, and after recharging the phone went into a bootloop. I had to install com.android.updater again, and after that everything went back to normal.
How did I find out it was com.android.updater? When in a bootloop, the Android system is actually already up and running. I was able to do adb logcat. There I saw that the system was looking for com.android.updater.
Code:
04-18 17:07:20.036 7445 7606 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-4
04-18 17:07:20.036 7445 7606 E AndroidRuntime: java.lang.RuntimeException: System error: connot find system app : com.android.updater
Note that I'm using the original China Stable ROM version 10.4.4.0(PFKCNXM), all stock, locked bootloader, not rooted. Except for the customization that we can do without root: Install Google services etc, and disable/uninstall packages through ADB.
I didn't want to upgrade to MIUI 11 because I've seen reports of it being slow and draining battery, and I want the NFC functionality, so I had to stick with China ROM.
Click to expand...
Click to collapse
Would it be safe to disable in ADB, rather than uninstall?
Also, is it only responsible for OS updates, or does it handle things like updating the Google Play app?
hey guys..
is there any method for unrooted device..? disable commanda is not working.;
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>adb shell pm disable-user --user 0 com.android.
updater
Package com.android.updater new state: default
t-mobile_mda said:
hey guys..
is there any method for unrooted device..? disable commanda is not working.;
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>adb shell pm disable-user --user 0 com.android.
updater
Package com.android.updater new state: default
Click to expand...
Click to collapse
I would suggest not touching android.updater. it gives bootloop if disabled or uninstalled
What should we remove then