[Q] Moving apps 2 Ext SD 5.0.2 - Xperia Z3 Q&A, Help & Troubleshooting

According to sony, the lollipop update brings back the ability to move the apps to the SD, i move the apps but they are still in the internal memory, apps like asphalt 8 that has a single file over 1.5 gigs and i cant move it to the sd, the app control says that its on the sd bus its on the internal memory as i said, some one else got this problem?

Idk. Saw this in the threads today and figured I'd copy it for later. I have the same problem.
By running code below inside your giefroot_v?\files\ folder did the trick on .77!!
(Reboot your device for changes to take effect)
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
/system is mounted as r/w (see pics)!! lol

tweker said:
Idk. Saw this in the threads today and figured I'd copy it for later. I have the same problem.
By running code below inside your giefroot_v?\files\ folder did the trick on .77!!
(Reboot your device for changes to take effect)
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
/system is mounted as r/w (see pics)!! lol
Click to expand...
Click to collapse
That is not the solution here. That code fixes the system partition as read write, where as the user here wants to write to his SDcard.
Furthermore, the OP is on 5.0.2 not 4.4.4 and is trying to use a stock feature of lollipop. We do not know if he is even rooted.

Related

how to unroot my nexus s pls help

hello,
i need help to remove superuser and lock my nexus s
+after doing that should i get official updates?
i did see this topic
http://forum.xda-developers.com/showthread.php?t=879041
and i try this solution
ryude said:
You need to use adb to go in the file system and delete all trace of superuser and busybox. That is the only things rooting does, places those files on your phone and changes file permissions. File permissions, they won't look for, but I've had best buy scroll through the app drawer on multiple occasions looking for superuser/rom manager.
I have attached a zip containing all the files needed for adb. Since they no longer package adb with the sdk. Just open command prompt and cd to the directory containing adb. Make sure your phone has Usb Debugging enabled, then connect your phone.
You might need to download usb drivers in order for windows to recognize the device, but probably not. Once your phone is connected, do the following.
Code:
adb devices
adb shell
su
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
reboot
Click to expand...
Click to collapse
but when i write rm /system/app/Superuser.apk it say
Read-only file system
so what should i do i only get my XS unlock then install superuser using
install-superboot-windows.bat
and i never do recovery!!!!!!
so any help
i need to get my nexus like new and i should then gt updates
You can have superuser and get updates. The update will remove root though. You could always wait for the cm nightly to include 2.3.3
Sent from my Nexus S using XDA App
You have to mount the /system partition as read/write.
Easiest way is use Root Explorer.
You can also try the following from adb or terminal on the phone:
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
thanks for your reply
i used Root Explorer to mount the /system partition as read/write.
and then
i did write this codes
adb devices
adb shell
su
rm /system/app/Superuser.apk
and every thing was ok
but i have an error on those lines
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
and every time i get file not found
so what i should do???
hello, tominater12 and thank you for reply
cold you tell me how i can remove superuser and root using the update??????
i want to get my nexus s like new no root no superuser
so any one can help?
hi guys,
this is my first post in the forums, but after reading and watching many videos on how to remove it i have found a solution...my nexus s is now unrooted with no superuser...
make sure u have android sdk installed, and have usb debugging on.
restart phone into recovery
open cmd and type -
cd c:/AndroidSDK/tools/
adb shell mount /system
adb shell rm /system/app/Superuser.apk
ALL CREDITS GO TO 'TheUltraLinx' ON YOUTUBE,
who has fixed my phone to factory settings
flash oem rom and fastboot oem unlock?

[Q] Please help translate some adb instructions into terminal emulator commands

Hi
I have Huawei u8150, Android 2.2, Rooted with z4root.
I want to give widgetsoid access to toggle data using the android apn toggle.
The instructions are:
____
Just put the Widgetsoid apk on /system/app folder
Work only with ADB connected to the phone (doesn't work if you use root explorer or other apps like this) :
* Remount /system as read/write
* adb push Widgetsoid.apk /system/app/Widgetsoid.apk
* Remount /system as read-only
_____
Can someone tell me what I can type in terminal emulator window to achieve this. I can't use adb as it won't recognise my u8150 (It worked fine with my i9000)
Thanks
Kiwi
Widgetsoid website - http://jaumard.android.free.fr/widgetsoid/help_widgetsoid.php?lang=en_EN
PS: Apologies if the wrong forum, but there were only 4 specific android forums, so i thought the general forum would be the best to post this type of question in.
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
http://www.reallylinux.com/docs/files.shtml
Thanks
I had tried
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# CHMOD 777 /SYSTEM
the above works but if i try to push i get
# push
push: not found
I also tried the above then switched over to es-file explorer and was able to copy + pasted the widgetsoid.apk file from my sdcard into the /system/app directory. It correctly pasted the file, but when I clicked on widgetsoid.apk to install the apk i got an error.
"Parse Error: There is a problem parsing the package."
I wouldn't chmod /system ... just leave the permissions the same.
cp /sdcard/downloads/widgetsoid.apk /system/app/
Chmod 644 /system/app/widgetsoid.apk
No need to click install or anything like that... just reboot after copying it to /system/app.
Sent from my Droid using Tapatalk
push is an adb command. You'll want to put the apk on the sdcard then use:
cp /sdcard/Widgetsoid.apk /system/app/
That will copy it to the directory.
Nevermind, do what jeffv2 said.
THANKS! it's working now.
I had placed it in /system/app and did a reboot and it still hadn't installed
then i renamed the file from Widgetsoid2.x.apk to Widgetsoid.apk and also did chmod 644, after a reboot it has successfully installed.
I think it was the chmod 644 to the apk file that allowed it to be installed
Many thanks!

foobar'd android

Could someone pm a link to framework-res.apk from /system/frameworks/. I am stuck in a boot loop and the drive i had that file backed up to failed.
any help would greatly be appreciated
in droid explorer it shows up as android system
http://www.mediafire.com/?63798kh3vex715o
When you are going to push it follow my instructions
Copy it to the memory/or your memory card
in adb type this
Code:
adb shell
su
cp sdcard/framework-res.apk system/framework/framework-res.apk
if its not on the main memory and its on your memory card type this
Code:
adb shell
su
cp sdcard/_ExternalSD/framework-res.apk system/framework/framework-res.apk
after you do that the phone will recognize the original framework and you will be fine.
PS: Although the root exploring app sees the framework-res.apk it may not be registered with the phone and it gets fixed by pushing it using adb shell
now remember do not do adb shell cp sdcard/whatever.apk because the phone will not allow it for some reason...... FOLLOW MY INSTRUCTIONS
OMG thank you i am going crazy with this drive i am in linux now, so i'll just push this from adb in recovery...
death1246 said:
http://www.mediafire.com/?63798kh3vex715o
When you are going to push it follow my instructions
Copy it to the memory/or your memory card
in adb type this
Code:
adb shell
su
cp sdcard/framework-res.apk system/framework-res.apk
if its not on the main memory and its on your memory card type this
Code:
adb shell
su
cp sdcard/_ExternalSD/framework-res.apk system/framework-res.apk
after you do that the phone will recognize the original framework and you will be fine.
PS: Although the root exploring app sees the framework-res.apk it may not be registered with the phone and it gets fixed by pushing it using adb shell
now remember do not do adb shell cp sdcard/whatever.apk because the phone will not allow it for some reason...... FOLLOW MY INSTRUCTIONS
Click to expand...
Click to collapse
Err no... that won't work.
Code:
adb shell
su
busybox mount -o,remount -rw /system
stop
cp /sdcard/_ExternalSD/framework-res.apk /system/framework/
reboot
Will deliver a much better (working) result...
Since we're not sure how to do this, this is what i did:
Well the system was boot-looping on the kernel level so neither instructions were accurate.
I first installed the test version CWM recovery, from there I mounted system from inside recovery and then i used these commands
Code:
adb push ./framework-res.apk /sdcard/framwork-res.apk
adb shell
cp /sdcard/framework-res.apk /system/framework/
then i rebooted and crossed my fingers till it finally booted
I thought he was doing it through recovery and he knew to mount the system already...
death1246 said:
I thought he was doing it through recovery and he knew to mount the system already...
Click to expand...
Click to collapse
And the file would have gone where?
holy **** lol I seriosuly thought I put in framework folder OMFG......
bare with me it was 6am XD
EPIC FAIL ON ME lol
F.U.B.A.R.

[Q] Rooting the motorola atrix 2

i tried a few ways to root my atrix 2 but i cant. I tried super one click, lazy one click (or however its called) and i cant root it i have a mac someone help! is there another way to root the atrix 2?
I heard there was an app that can do it too. Its in this forum somewhere.
I used the manual method on my Mac with no issues, did it twice actually.
What error messages are you getting?
I'll be home in about 15 mins and I can help further
Sent from my MB865 using Tapatalk
If all else fails, you could always reflash the fkz's, than try to root again, but the problem here is that you have a mac. Perhaps borrow a friends pc, or install Windows through bootcamp. (I wouldn't recommend a Virtual Machine though).
OK so if you used a root tool in the first place then I assume that-
-You have adb set up
-You have the necessary files to push (zerg, su, superuser.apk)
If you have no idea of what I'm talking about then just look around the folders of the root tools and you'll find them.
OK, here's what you have to do:
1. Open up a terminal.
2. CD (change directory) to where you have the necessary files located, ex. "cd ~/Desktop/" if they're on the desktop
3. Enter the following commands (one line at a time):
Code:
adb shell
cd /data/local
rm ./temp/*
exit
This removes temporary files created by the root exploit.
4. Now enter these commands (again, one at a time)
Code:
adb push zerg /data/local
adb push su /data/local
adb push Superuser.apk /data/local
adb shell
cd /data/local
chmod 777 zerg
./zerg
adb shell
mount -o rw,remount /dev/null /system
cat /data/local/su > /system/bin/su
cat /data/local/Superuser.apk > /system/app/Superuser.apk
chmod 4755 /system/bin/su
chmod 4755 /system/app/Superuser.apk
reboot
I hope you understand this... good luck getting complete root.
thread moved to general forum
If you find a specific android app that can do this for you and you can post it in the OP, I will gladly move it down to its original location. Until there, it doesnt belong in the app and themes forums.
What's your android version ?
Deliberate said:
I heard there was an app that can do it too. Its in this forum somewhere.
Click to expand...
Click to collapse
Unfortunately that app seems to have only been in the market and was recently removed... I tried looking for it today. Please correct me if I'm wrong!
jpumford said:
Unfortunately that app seems to have only been in the market and was recently removed... I tried looking for it today. Please correct me if I'm wrong!
Click to expand...
Click to collapse
You're correct, the app was written by an author who made it just to make money... he never even tested it. He took it down because it didn't work.
Most important question of all here: What OS are you running on your Mac?
If you're running 2.3.6 you can't root yet. You need to downgrade to 2.3.5

problem with camera apps

In my z5 in camera 2.0 installed so in apps stopped working but when launch camera apps from app drawer works fine
Also tried to remove update but without update camera (stock apk) shows fc
I have rooted z5 dual
If you rooted, your DRM keys are gone (from unlocking bootloader). Someone reported their camera working after this hack to trick DRM keys being there:
http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
Not sure it'll fix your issue, but worth a try since you are already rooted. All else fails, factory reset.
rajdeep312 said:
In my z5 in camera 2.0 installed so in apps stopped working but when launch camera apps from app drawer works fine
Also tried to remove update but without update camera (stock apk) shows fc
I have rooted z5 dual
Click to expand...
Click to collapse
Try push deodexed Camera.apk
by ADB (download attachment and copy it to folder where ADB is :
Code:
adb push CameraCommon.apk /data/local/tmp
adb shell
su
busybox mount -o remount,rw /system
dd if=/data/local/tmp/CameraCommon.apk of=/system/priv-app/CameraCommon/CameraCommon.apk
chmod 644 /system/priv-app/CameraCommon/CameraCommon.apk
rm -rf /system/priv-app/CameraCommon/arm
rm -rf /system/priv-app/CameraCommon/arm64
RootExplorer or any other file manager :
Download CameraCommon.apk, copy-paste it to /system/priv-app/CameraCommon/CameraCommon.apk, change chmod to 644 (read write, read, read) and delete arm and arm64 folder.
Thanks you saved my z5
Siudzix said:
Try push deodexed Camera.apk
by ADB (download attachment and copy it to folder where ADB is :
Code:
adb push CameraCommon.apk /data/local/tmp
adb shell
su
busybox mount -o remount,rw /system
dd if=/data/local/tmp/CameraCommon.apk of=/system/priv-app/CameraCommon/CameraCommon.apk
chmod 644 /system/priv-app/CameraCommon/CameraCommon.apk
rm -rf /system/priv-app/CameraCommon/arm
rm -rf /system/priv-app/CameraCommon/arm64
RootExplorer or any other file manager :
Download CameraCommon.apk, copy-paste it to /system/priv-app/CameraCommon/CameraCommon.apk, change chmod to 644 (read write, read, read) and delete arm and arm64 folder.
Click to expand...
Click to collapse
I also have an issue with my Camera, if I open Camera Apps, for example Style Portrait, AR Mask, Sticker creator, Creative effect, they all force-close.
Will pushing the deodexed Camera.apk also fix my issue? And am I still able to update after pushing this update?
Thanks!
Meneer_A said:
I also have an issue with my Camera, if I open Camera Apps, for example Style Portrait, AR Mask, Sticker creator, Creative effect, they all force-close.
Will pushing the deodexed Camera.apk also fix my issue? And am I still able to update after pushing this update?
Thanks!
Click to expand...
Click to collapse
Yes deodex solve your problem
Siudzix said:
Try push deodexed Camera.apk
by ADB (download attachment and copy it to folder where ADB is :
Code:
adb push CameraCommon.apk /data/local/tmp
adb shell
su
busybox mount -o remount,rw /system
dd if=/data/local/tmp/CameraCommon.apk of=/system/priv-app/CameraCommon/CameraCommon.apk
chmod 644 /system/priv-app/CameraCommon/CameraCommon.apk
rm -rf /system/priv-app/CameraCommon/arm
rm -rf /system/priv-app/CameraCommon/arm64
RootExplorer or any other file manager :
Download CameraCommon.apk, copy-paste it to /system/priv-app/CameraCommon/CameraCommon.apk, change chmod to 644 (read write, read, read) and delete arm and arm64 folder.
Click to expand...
Click to collapse
Thank you for this, it really helped me a lot. now I could get camera and plug-ins run again after root. you just bring lots of fun back.:good:

Categories

Resources