OK, for those on any cupcake or donut build, I've included instruction to get the new Maps 3.2.0 and the new YouTube app from Eclair (Android 2.0).
1. Download the zip file. View attachment 2.0_Apps.zip
2. Extract and place Maps.apk and YouTube.apk on the root of your SDCard
I'm using CyanogenMod 4.2.2 with CM-Recovery 1.4
In CM 4.2.2 the apps are found in /system/app ***while the phone is on and operation, if it's off or in recovery the symlink won't be active so please make sure your phone is completely booted. Don't do this from Recovery Console***
If you're using a different rom... go through your phone and locate Maps.apk and YouTube.apk update the links below accordingly
Windows users (with ADB working)
1. Open a CMD (command promt window)
Type:
- adb remount
- adb shell
- rm /system/app/Maps.apk
- rm /system/app/YouTube.apk
- cd /sdcard
- cp Maps.apk /system/app
- cp YouTube.apk /system/app
Phone Users:
1. Open a Terminal Window:
2. Type the following:
- su
- mount /system -o remount,rw
- rm /system/app/Maps.apk
- rm /system/app/YouTube.apk
- cd /sdcard
- cp Maps.apk /system/app
- cp YouTube.apk /system/app
You don't need to reboot... Apps will show up immediately in your menu. (You'll need to put them back on your Home Screen if you had them there though)
You're done... enjoy!
Is this the new maps with turn by turn?
You might want to change from
rm /system/app/Maps.apk
rm /system/app/Youtube.apk
to
mv /system/app/Maps.apk /sdcard/Maps.apk.old
mv /system/app/Youtube.apk /sdcard/Youtube.apk.old
the youtube app isn't all that stable and it never hurts to keep a backup, also I believe you need to remove any .obex files for maps and youtube to avoid problems although I didn't see any under CM 4.2.2
edit: I also believe these don't work on 1.5 might be worth pointing out in the OP
persiansown said:
Is this the new maps with turn by turn?
Click to expand...
Click to collapse
No just the one from the sholes dump, its faster to load and has layers for wikipedia, latitude and things like that
edit: more info here http://forum.xda-developers.com/showthread.php?t=574329
will this in a Hero rom? thanks!
Moved to apps location
might have to give this a shot
Totally doesn't work for me:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\DamianV>adb remount
remount succeeded
C:\Users\>adb shell
# rm /system/app/maps.apk
rm /system/app/maps.apk
rm failed for /system/app/maps.apk, No such file or directory
# rm /system/app_s/Maps.apk
rm /system/app_s/Maps.apk
rm failed for /system/app_s/Maps.apk, No such file or directory
# cp Maps.apk /system/app
cp Maps.apk /system/app
cp: cannot stat 'Maps.apk': No such file or directory
# cp Maps.apk /system/app
cp Maps.apk /system/app
cp: cannot stat 'Maps.apk': No such file or directory
#
I tried a few different variations.
remember to remount first and make sure you have the correct directories.
some roms uses system/app, some roms uses data/app_s
NguyenHuu said:
remember to remount first
Click to expand...
Click to collapse
Yeah I did do that...odd
do u have the origional file.. i made a booboo and didnt back up. forgot to backup origional file.
can u use a file explorer and browse and double check which directories the files are actually in? i see you tried both system/app and app_s. and i see you have lowercase for maps.apk. it could be uppercase, case sensitive.
for example your first cmd #rm /system/app/maps.apk, it should be Maps.apk
also for the copying part you need to do adb push, dont do it from shell. if you do from shell it would have to be from sdcard to that directory. i noticed in your log you didnt change directory to sdcard.
IronCross1788 said:
do u have the origional file.. i made a booboo and didnt back up. forgot to backup origional file.
Click to expand...
Click to collapse
Hahah yeah I made the same mistake--was getting 'Cross-Linked' errors so I said ehh fudge it and just wiped the original out. After that I was able to get the new Maps.apk loaded up though and DAMN, definitely an improvement
I thought these apps wouldnt work on anything below android 1.6?
If you're having trouble finding the app and want to check the directory you're in you can use ls (that's LS) to list the contents of the current directory. ROMs store things in different places so if you haven't already try....
adb remount
adb shell
cd /data/
ls
At that point see if you have app, app_s, app-private etc then if you do you can ....
cd app or app_s etc
Then do..
ls Maps.apk (this is case-sensitive)
If you get nothing do
cd ..
That'll take you back one directory, so if you're in /data/app it'll put you in /data
With those few commands you can probably find it. I don't use Linux enough to know what if there's a 'find' command available in console. The other option that might be quicker would be to find the .zip of the ROM you're using, create a new folder for it, move the .zip file to the new folder and then extract it there. That way you can browse through directories more easily or use Windows / OS X / Linux search functions to find Maps.apk
Phew...
Dyonas said:
If you're having trouble finding the app and want to check the directory you're in you can use ls (that's LS) to list the contents of the current directory. ROMs store things in different places so if you haven't already try....
adb remount
adb shell
cd /data/
ls
At that point see if you have app, app_s, app-private etc then if you do you can ....
cd app or app_s etc
Then do..
ls Maps.apk (this is case-sensitive)
If you get nothing do
cd ..
That'll take you back one directory, so if you're in /data/app it'll put you in /data
With those few commands you can probably find it. I don't use Linux enough to know what if there's a 'find' command available in console. The other option that might be quicker would be to find the .zip of the ROM you're using, create a new folder for it, move the .zip file to the new folder and then extract it there. That way you can browse through directories more easily or use Windows / OS X / Linux search functions to find Maps.apk
Phew...
Click to expand...
Click to collapse
Sound advise, one last thing for anyone who didn't know the remount command is
mount -o rw,remount /system (assuming your apps are in /system/app)
so full instructions for a CyanogenMod install from the sd card would be as follows
- su
- mount -o rw,remount /system
- cd /sdcard
- mv /system/app/Maps.apk /sdcard/Maps.apk.old
- mv /system/app/YouTube.apk /sdcard/Youtube.apk.old
- cp Maps.apk /system/app
- cp YouTube.apk /system/app
To revert back to old apps if you decide you don't like the new ones
- su
- mount -o rw,remount /system
- cd /sdcard
- cp Maps.apk.old /system/app/Maps.apk
- cp Youtube.apk.old /system/app/Youtube.apk
Breakthecycle2 said:
Totally doesn't work for me:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\DamianV>adb remount
remount succeeded
C:\Users\>adb shell
# rm /system/app/maps.apk
rm /system/app/maps.apk
rm failed for /system/app/maps.apk, No such file or directory
# rm /system/app_s/Maps.apk
rm /system/app_s/Maps.apk
rm failed for /system/app_s/Maps.apk, No such file or directory
# cp Maps.apk /system/app
cp Maps.apk /system/app
cp: cannot stat 'Maps.apk': No such file or directory
# cp Maps.apk /system/app
cp Maps.apk /system/app
cp: cannot stat 'Maps.apk': No such file or directory
#
Click to expand...
Click to collapse
If you have a2sd, try mapping to /system/sd/app or /system/sd/app_s
Make sure you remount before doing so.
hey guys!
for those who are having problems...
I just put the apk files in my sdcard and then upgraded it using ASTRO.. it worked fine!
yeah well every1 is doing this mad confusing lmfao i just installed with appsinstaller and it worked like a charm lol why is everything always confusing
Enjoying my galaxy gear but a bit upset that there isn't an easy way to add custom ringtone sounds or notification sounds to the smartwatch. Has anyone figured out a way to add custom sounds to the gear for notifications? Would love to be able to do this myself. Thanks in advance!
yes, there is a way...but unfortunately it requires the device to be rooted first
you can push any custom ringtones using adb commands
adb remount
adb push *.ogg /system/media/audio/alarms/
adb push *.ogg /system/media/audio/notifications/
adb push *.ogg /system/media/audio/ringtones/
adb push *.ogg /system/media/audio/ui
adb remount didnt work for me, i couldn't run adb as root in a production build. i also needed to remount / & /system as rw
so what i did:
mount -ro remount,rw /
mount -ro remount,rw /system
mkdir /tmp1 (temp staging folder)
then push my files to the /tmp1 dir:
adb push filename.ogg /tmp1
(using wildcard on adb command line didnt work for me)
then in a root shell
cp /tmp1/* /system/media/audio/notifications etc whatever dir you want.
to copy all ogg files to the folder.
once you've copied all the files, type in reboot in a shell and the ringtone & notification list in settings will update. viola!
and remember, if you want your ringtone to loop: use your favourite tag editor (I used foobar2000 on Windows), add a tag/field called “ANDROID_LOOP”, and set it to “true”.
without this tag it will not loop.
I am in the position of having to manually apply the defult sepolicy patch, init,?*init_shell?* and?*recovery?*permissive, and as the title states when using the supolicy tool to modify my supplieded sepolicy it is not being produced and on closer inspection throwing an error. I have attached both the images and the sepolicy file I am trying to applie these change to.
Have I been doing something wrong or is the file corrupted??
If you need more info just ask
Note: when I first tried it inside an adb shell it reported a segumentation fault, but I was unable to reproduce that condition to be provided with as a screen shot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: I at least can say that the possibility of a corrupt file is now smaller becuse I am able to run dumpav and dump its contents to a txt file and then do afb pull back to pc. So amyone know any way to applie the defult P atchs needed to sysyemless root?
@Chainfire Since this is your binary files, you should know the most about it.
Commands to gain application root on emulator
Code:
adb shell df #Check Available Space
adb shell mount -o remount,rw /system
adb push su /system/bin/su
adb shell chmod 0755 /system/bin/su
adb push su /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb shell su --install
adb shell "su --daemon&"
adb install superuser.apk
adb install rootcheck.apk
I then proceed to patch the sepolicy file with the following commands
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out" #There is no sepolicy_out file
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out
So what am I able to do?
Are you able to
A) Help me debug the problem
Or
B) Patch the sepolicy file and post the output back to me/here
Matt07211 said:
...
Click to expand...
Click to collapse
Works fine on my device... could be an x86 specific issue? Unfortunately I don't have any x86 devices to test with.
Thanks for that. Yes, I am trying to patch the policy for my armv8 (arm64) cpu device (just realised, but would trying to patch the sepolicy from one architecture using the supolicy for a different architecture have new the problem?, if so I feel dumb). And since I didn't have a spare device devce that met the requirements, I resorted to use the already setup emulator in my Windows installation.
I had proceeded to root and run the supolicy tool for which nothing out-putted (tried different directorys), I then created a new sub-directory, test, in /data/local/tmp and chmod it with read and write permissions. I tried again and failed, I then ran a dumpav in the sepolicy I was trying to patch and outputted it to /data/local/tmp/test/dumpav.txt which worked.
I am just wondering why it didn't work for me .
Thanks again for the sepolic_out file, I really do apperciate it.
Ah you're saying the segmentation fault occurred on the emulator? That's interesting. Might be reproducable on my end.
Note: look at my first image with cms in the foreground and near the bottom of the command window you should see the segfault message, around second last command or so.
To reproduce that segfault (hopefully):
1) https://software.intel.com/en-us/android/articles/android-44-kitkat-x86-emulator-system-image Download the system image from here (had to direct download instead of sdk as internet was running through profile and ask wouldn't work through it)
2) used the 2.78 SuperSu zip and run above commands to gain root
3) run above commands to try and modify sepolicy (it doesn't produce anything)
4) start an adb shell and then run the commands inside the shell. Know the outputs shown was segfault the first time running the commands, every time afterwards it would show the error in the above screenshots
If you figure out what cause the segfault can you please tell me ?
Matt07211 said:
Note: look at my first image with cms in the foreground and near the bottom of the command window you should see the segfault message, around second last command or so.
To reproduce that segfault (hopefully):
1) https://software.intel.com/en-us/android/articles/android-44-kitkat-x86-emulator-system-image Download the system image from here (had to direct download instead of sdk as internet was running through profile and ask wouldn't work through it)
2) used the 2.78 SuperSu zip and run above commands to gain root
3) run above commands to try and modify sepolicy (it doesn't produce anything)
4) start an adb shell and then run the commands inside the shell. Know the outputs shown was segfault the first time running the commands, every time afterwards it would show the error in the above screenshots
If you figure out what cause the segfault can you please tell me ?
Click to expand...
Click to collapse
Before I go do all this, can you make sure the issue persists with the v2.78 SR1 version from the BETA thread ? Some issues with supolicy were fixed in that release.
Started with a fresh emulator and the newest SuperSu and ran these commands to gain root (I am placing everything as described in update-binary in the right places just to eliminate one thing, missing dependencies)
Code:
adb shell df
adb shell mount -o remount,rw /system
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell ln -s /system/etc/install-recovery.sh /system/bin/install-recovery.sh
adb shell chmod 0755 /system/etc/install-recovery.sh
adb push su /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb push su /system/bin/.ext/.su
adb shell chmod 0755 /system/bin/.ext/.su
adb push su /system/xbin/daemonsu
adb shell chmod 0755 /system/xbin/daemonsu
adb push su /system/xbin/sugote
adb shell chmod 0755 /system/xbin/sugote
adb push supolicy /system/xbin/supolicy
adb shell chmod 0755 /system/xbin/supolicy
adb push libsupol.so /system/lib/libsupol.so
adb shell chmod 0644 /system/lib/libsupol.so
adb push 99SuperSUDaemon /system/etc/init.d/99SuperSUDaemon
adb shell chmod 0755 /system/etc/init.d/99SuperSUDaemon
adb shell su --install
adb shell "su --daemon&"
adb install superuser.apk
adb install rootcheck.apk
No everything should be in place, and we now can eliminate one thing (supolicy not finding needed dependencies)
Opened up SuperSu and let it install/update binary (succesful)
I then proceeded to patch the sepolicy file like so
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
I then did "ls" in the directory and no file out-putted. So I went into a shell and ran
Code:
supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out
And it throw the error shown in the image below. First time running that command in shell it says stopped, but the second time it says stopped as well as segfault.
Keep in mind I am trying to patch a sepolicy file that originates from an armv8 cpu (arm64) on an x86 Intel emulator.
Any more info needed? I am happy to help @Chainfire
So, I think it has something to do with your emulator image (perhaps its too old ?)
I took SuperSU's ZIP file and extracted it, changed to that folder, then:
(note that my adb shell to my emulator image has # root by default)
Code:
adb push c:\download\sepolicy /data/local/tmp/sepolicy
adb push x86\. /data/local/tmp/.
adb shell
cd /data/local/tmp
chmod 0755 supolicy
LD_LIBRARY_PATH=/data/local/tmp:$LD_LIBRARY_PATH ./supolicy --file sepolicy sepolicy_out
exit
Resulting in:
Code:
supolicy v2.78 (ndk:x86) - Copyright (C) 2014-2016 - Chainfire
Patching policy [sepolicy] --> [sepolicy_out] ...
- Success
So, I'm really not sure what might be going on with your setup, but I don't think its SuperSU itself, but rather the emulator.
Note that to use supolicy --file, you only need supolicy and libsupol.so, you don't even need root.
Chainfire said:
So, I think it has something to do with your emulator image (perhaps its too old ?)
I took SuperSU's ZIP file and extracted it, changed to that folder, then:
(note that my adb shell to my emulator image has # root by default)
Resulting in:
So, I'm really not sure what might be going on with your setup, but I don't think its SuperSU itself, but rather the emulator.
Note that to use supolicy --file, you only need supolicy and libsupol.so, you don't even need root.
Click to expand...
Click to collapse
Hmm, I really don't know what is wrong, I will try exactly what you have done later today, to see If can reproduce the output. If it doesn't work then we can pin it down to the emulator itself. What emulator image did you use?
I also realise that so emulator are rooted in the sense that web shell has root acess, just wasn't sure what dependices supolicy had at the time.
Matt07211 said:
Hmm, I really don't know what is wrong, I will try exactly what you have done later today, to see If can reproduce the output. If it doesn't work then we can pin it down to the emulator itself. What emulator image did you use?
I also realise that so emulator are rooted in the sense that web shell has root acess, just wasn't sure what dependices supolicy had at the time.
Click to expand...
Click to collapse
I created an API 22 Google Nexus x86_64 AVD in Android Studio
I should be able to try that in about 20-30 mins after I download it, I was using api level 19, Intel's emulator image.
I ran these commands on the Intel api 19 x86 emulator image.
Code:
adb push libsupol.so /system/lib/libsupol.so
adb shell chmod 0644 /system/lib/libsupol.so
adb push /system/xbin/supolicy
adb shell chmod 0755 /system/xbin/supolicy
adb push supolicy /data/local/tmp/supolicy
adb shell chmod 0755 /data/local/tmp/supolicy
adb push sepolicy /data/local/tmp/sepolicy
adb shell
cd /data/local/tmp
chmod 0755 supolicy
LD_LIBRARY_PATH=/data/local/tmp:$LD_LIBRARY_PATH ./supolicy --file sepolicy sepolicy_out
and it results in the error(shown in screenshot)
Code:
libsepol.policydb_read: policydb magic number 0x464c457f does not match expected magic number 0xf97cff8c or 0xf97cff8d
-Failure!
I then tried it on the Intel x86_64 api 22 emulator image (running the same commands as the first one, resulting in a succes, with the file being outputted as the sepolicy_out.
So as you have stated @Chainfire , it looks like a problem with the emulator itself, and most likely not the supolicy tool.
Chainfire said:
So, I think it has something to do with your emulator image (perhaps its too old ?)
I took SuperSU's ZIP file and extracted it, changed to that folder, then:
(note that my adb shell to my emulator image has # root by default)
Code:
adb push c:\download\sepolicy /data/local/tmp/sepolicy
adb push x86\. /data/local/tmp/.
adb shell
cd /data/local/tmp
chmod 0755 supolicy
LD_LIBRARY_PATH=/data/local/tmp:$LD_LIBRARY_PATH ./supolicy --file sepolicy sepolicy_out
exit
Resulting in:
Code:
supolicy v2.78 (ndk:x86) - Copyright (C) 2014-2016 - Chainfire
Patching policy [sepolicy] --> [sepolicy_out] ...
- Success
So, I'm really not sure what might be going on with your setup, but I don't think its SuperSU itself, but rather the emulator.
Note that to use supolicy --file, you only need supolicy and libsupol.so, you don't even need root.
Click to expand...
Click to collapse
@Chainfire, I'm trying to patch sepolicy for a Samsung device running Nougat, so that Supersu can be installed in system mode. Could you confirm if the --sdk=24 parameter is required?
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out --sdk=24"
Thanks, appreciate your time.
ashyx said:
@Chainfire, I'm trying to patch sepolicy for a Samsung device running Nougat, so that Supersu can be installed in system mode. Could you confirm if the --sdk=24 parameter is required?
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out --sdk=24"
Thanks, appreciate your time.
Click to expand...
Click to collapse
Yes it is.
System mode hasn't been tested at all on 7.0 though. I'm not sure anybody has been able to get it to work at this point.
If you do, let me know and with the steps
Chainfire said:
Yes it is.
System mode hasn't been tested at all on 7.0 though. I'm not sure anybody has been able to get it to work at this point.
If you do, let me know and with the steps
Click to expand...
Click to collapse
Hmm wasn't aware of the lack of support for system mode in nougat, any plans to implement?
It seems system mode root renders the device unbootable according to reports from my tester.
Question, if I modify the supersu script to mount su.img from /system am I likely to hit issues?
Seems a strange query I know.
Reason is we have a Samsung device that for some reason will not boot from a source built custom Nougat kernel. Not sure if this is related to AVB yet or something else.
However we can get a half assed TWRP to boot with the stock kernel.
Only problem is, no matter what, only /system can be mounted and accessed with write permission due to permission denied issues with the rest of partitions. Pretty sure this is an SELinux issue.
Meaning systemless root cannot be installed as normal. No access to /data or /cache.
I can patch the boot.img ramdisk manually for systemless, but for root to work I would need to push su.img to system and mount it from there.
Is it possible to still mount su.img from system if I modify the ramdisk init as required?
The other avenue is to flash su.img to /data or /cache via ODIN.
If it was flashed to /cache would supersu automatically pick up its location and copy it to /data or would a flag need to be set?
Just trying to keep my options open here.
ashyx said:
Hmm wasn't aware of the lack of support for system mode in nougat, any plans to implement?
It seems system mode root renders the device unbootable according to reports from my tester.
Click to expand...
Click to collapse
It is on my list of things to test/fix, but that list is long and full of terrors.
Question, if I modify the supersu script to mount su.img from /system am I likely to hit issues?
Is it possible to still mount su.img from system if I modify the ramdisk init as required?
Click to expand...
Click to collapse
I think that could work, yes.
The other avenue is to flash su.img to /data or /cache via ODIN.
If it was flashed to /cache would supersu automatically pick up its location and copy it to /data or would a flag need to be set?
Just trying to keep my options open here.
Click to expand...
Click to collapse
SuperSU should pick it up from /cache. Alternatively, try SuperSU's FRP mode, which stores a copy of the needed files in the boot-image and re-creates /data/su.img as needed.
Chainfire said:
It is on my list of things to test/fix, but that list is long and full of terrors.
I think that could work, yes.
SuperSU should pick it up from /cache. Alternatively, try SuperSU's FRP mode, which stores a copy of the needed files in the boot-image and re-creates /data/su.img as needed.
Click to expand...
Click to collapse
Thanks, great info as always. Finally managed to root the damn thing by adding a short script to the init which copies su.img to cache.
However FRP mode sounds like a more elegant solution if I can work out how to implement it in the Ramdisk.
Much appreciate your input.
ashyx said:
So, I think it has something to do with your emulator image (perhaps its too old ?)
...
Could you confirm if the --sdk=24 parameter is required?
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out --sdk=24"
Thanks, appreciate your time.
Click to expand...
Click to collapse
Yea believe it was segfaulting due to the Android version, I think I was using KitKat and it wasn't working, bumped up to lollipop and above and it worked fine
Oh, the SDK parameter, never heard of it, what does it do? Geuss I'll Google that then.
ashyx said:
Thanks, great info as always. Finally managed to root the damn thing by adding a short script to the init which copies su.img to cache.
However FRP mode sounds like a more elegant solution if I can work out how to implement it in the Ramdisk.
Much appreciate your input.
Click to expand...
Click to collapse
I did the same thing for my device, add a little script to move it to data. Had no other way to get it to a locked down device without TWRP. Hehe. Good job
Can you please tell me how to manually patch init by supersu ?
I've googled a lot, but haven't found a way to manually patch init by supersu.
My model is Honor v10, there isn't a custom recovery, so i have to make a boot.img with supersu inside to get root.