Database Develop

[MOD] 4.1.57 deodexed framework and app files (AT&T Only)

Here are the App and Framework system files for 4.1.57 fully deodexed.
You must already have Root access in 4.1.57.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Remember to make a backup of your existing framework and app folders BEFORE you do this.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Again, backup your original system/framework and system/app files BEFORE you do this in case you want to revert back to an odexed system.
Here is the correction:
Put your phone in USB Mass Storage Device mode.
Copy the app and framework directory and their contents from the zip file to the root of your sdcard.
***Verify the copy was successful before you continue.***
Set USB mode back to None.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /dev/block/mmcblk0p12 /system
reboot

Thanks, you beat me to it!

lindsaytheflint said:
Thanks, you beat me to it!
Click to expand...
Click to collapse
I deodexed them last night, but wanted to run through some testing before I packaged them up.
Anyone feel like scripting this, go for it.

I must have done something wrong in shell... soft brick, certain it was my fault.

tl_bull said:
I must have done something wrong in shell... soft brick, certain it was my fault.
Click to expand...
Click to collapse
Not your fault... I found an error in my instructions.
cp /sdcard/frame/* /system/framework/
should be
cp /sdcard/framework/* /system/framework/

rjohnstone said:
Here are the App and Framework system files for 4.1.57 fully deodexed.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
Been running all day with these files with no issues.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Here is the correction.
Copy the app and framework directory to the root of your sdcard.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system

lpsi2000 said:
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Thx. Updated OP.
The mount commands I originally posted did work for me without any issue though.
Sent from my MB860 using XDA App

It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.

Ririal said:
It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.
Click to expand...
Click to collapse
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App

I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Edit:
Had to use usb port on the rear instead of the front when rooting.

zeyoner said:
I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Click to expand...
Click to collapse
Sounds like you don't have root access.
Do you see a $ or a # in your command prompt?

i have $ in my root access... i'm getting permission denied at when i type 'su' but im pretty sure i rooted it earlier today
edit fixed i wasnt rooted

rjohnstone said:
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah I looked it over again, should be fine.
EDIT: Nvm saw you updated.
I'm working on a new method to automate this, I'll post something when I have it working reliably.

looking for another way
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?

Very nice contribution!

Rad ryan said:
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?
Click to expand...
Click to collapse
This won't work without having root access first.
Sent from my MB860 using XDA App

I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.

Immix said:
I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.
Click to expand...
Click to collapse
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.

shawnbuck said:
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.
Click to expand...
Click to collapse
Thx for the tip.
I did use the stop command in my process and was able to prevent a reboot.
The process is so quick that I didn't see a single FC during the copy.

I think it should be mentioned in the OP that root is required.

[Q] How to fix wrong CHMOD permissions on /system

Inadvertanty I performed a 'chmod 644 /system' in an attempt to move my email.apk file over to the apps directory. Obviously this should have been a '777' but now the phone just reboots into recovery mode and will not get past it.
Is there any way to mount the filesystem and reissue the correct chmod command, or do I have to reinstall the OS?
Thanks!
Samsung Captivate
Serendipity VII-2

Try the Serendipity VII Q&A.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

texasagent said:
Inadvertanty I performed a 'chmod 644 /system' in an attempt to move my email.apk file over to the apps directory. Obviously this should have been a '777' but now the phone just reboots into recovery mode and will not get past it.
Is there any way to mount the filesystem and reissue the correct chmod command, or do I have to reinstall the OS?
Thanks!
Samsung Captivate
Serendipity VII-2
Click to expand...
Click to collapse
Using adb (and your phone in recovery, with the /system partition mounted):
adb root
adb shell
chmod 777 /system
exit
adb reboot
Hopefully that should get you there.

Thanks jmtheiss. That allowed me to get back in to change the permissions, however it still won't get past recovery mode after each reboot. Its strange that even after mounting /system, it doesn't contain a directory called 'app' anymore (or any subdirectories for that matter), just a handful of files. Looks like I have bigger issues.
Guess it's back to reloading the ROM again...
Thanks for your help!!
TexasAgent

Please post in the right sections. Should have been in Q&A

[Q] [TL][H] Xperia T. Internal storage is dead.

Welcome guys, my internal storage is dead it happend after I accidentally cleaned it (wanted to format external sd card...). I can't copy anything from PC on to it. I have no access. I'm running cm-11-20140623-NIGHTLY-mint with ClockworkModRecovery 6.x
How can I fix it?
I tried so far again cleaning it from Android level and also formating partition via recovery mode.

deywid12345 said:
Welcome guys, my internal storage is dead it happend after I accidentally cleaned it (wanted to format external sd card...). I can't copy anything from PC on to it. I have no access. I'm running cm-11-20140623-NIGHTLY-mint with ClockworkModRecovery 6.x
How can I fix it?
I tried so far again cleaning it from Android level and also formating partition via recovery mode.
Click to expand...
Click to collapse
It's an old issue with formatting your internal memory with a custom ROM, and I think it's a permission issue. Can you access ADB through recovery?
http://forum.xda-developers.com/showpost.php?p=52698386&postcount=95

Antiga Prime said:
It's an old issue with formatting your internal memory with a custom ROM, and I think it's a permission issue. Can you access ADB through recovery?
Click to expand...
Click to collapse
How can I check that? (I installed CM with tutorial step-by-step). I can use recovery mode, fastboot, my phone boot up just fine. I have read this but I don't know what I have to do. Can you tell me ? I'm depressed.

deywid12345 said:
How can I check that? (I installed CM with tutorial step-by-step). I can use recovery mode, fastboot, my phone boot up just fine. I have read this but I don't know what I have to do. Can you tell me ? I'm depressed.
Click to expand...
Click to collapse
If you install a Terminal Emulator on your phone, you might be able to avoid using ADB. Ideally you should learn how to set up ADB (google it), or read this and see if it helps you.
Let me know if you install a Terminal Emulator (and are rooted).

Antiga Prime said:
If you install a Terminal Emulator on your phone, you might be able to avoid using ADB. Ideally you should learn how to set up ADB (google it), or read this and see if it helps you.
Let me know if you install a Terminal Emulator (and are rooted).
Click to expand...
Click to collapse
I have Terminal Emulator installed and rooted yet.
What's the next step. You are my only hope to fix this man.

deywid12345 said:
I have Terminal Emulator installed and rooted yet.
What's the next step. You are my only hope to fix this man.
Click to expand...
Click to collapse
Then open Terminal Emulator and run the following commands (ignore what is in parenthesis):
Code:
su (grant access)
cd /mnt/media_rw
ls -l
Let me know what that command shows you. It should show you something similar to what I have in the attached image.

Antiga Prime said:
Then open Terminal Emulator and run the following commands (ignore what is in parenthesis):
Code:
su (grant access)
cd /mnt/media_rw
ls -l
Let me know what that command shows you. It should show you something similar to what I have in the attached image.
Click to expand...
Click to collapse
yeah it do.
Code:
drwxr -xr -x root root 1971-03-04 01:26 sdcard0
drwxrwx--- media_rw media_rw 1970-01-01 01:00 sdcard1
drwx------ media_rw media_rw 1971-03-04 01:25 usbdisk
That's what i got (can't provide you any screenshot because of not working internal mem.
(it looks like i dont have write permissions, but i have completly no clue how to fix it, just wrote that)

deywid12345 said:
yeah it do.
Code:
drwxr -xr -x root root 1971-03-04 01:26 sdcard0
drwxrwx--- media_rw media_rw 1970-01-01 01:00 sdcard1
drwx------ media_rw media_rw 1971-03-04 01:25 usbdisk
That's what i got (can't provide you any screenshot because of not working internal mem.
(it looks like i dont have write permissions, but i have completly no clue how to fix it, just wrote that)
Click to expand...
Click to collapse
Well, then you should try the following. Open the terminal again, use "su" again to grant root access, and do the following:
Code:
su
cd /mnt/media_rw
busybox chown -R 2800:2800 sdcard0
chmod 0770 sdcard0
Then either try to take a photo or create a file in your internal memory, or reboot and test your internal memory.
Edit: Just to be clear, the default user/owner for Sony internal memory is 2800, mine is set to 1023 (media_rw), as most phones should have, because I have modded the ramdisk in my kernel in order to use a certain program.

Antiga Prime said:
Well, then you should try the following. Open the terminal again, use "su" again to grant root access, and do the following:
Code:
su
cd /mnt/media_rw
busybox chown -R 2800:2800 sdcard0
chmod 0770 sdcard0
Then either try to take a photo or create a file in your internal memory, or reboot and test your internal memory.
Edit: Just to be clear, the default user/owner for Sony internal memory is 2800, mine is set to 1023 (media_rw), as most phones should have, because I have modded the ramdisk in my kernel in order to use a certain program.
Click to expand...
Click to collapse
Man it works! I ****in owe you! Worked even without rebooting phone.
Love from Poland!

deywid12345 said:
Man it works! I ****in owe you! Worked even without rebooting phone.
Love from Poland!
Click to expand...
Click to collapse
No problem. In case you're interested in learning what that just did, you might want read this and this.

Antiga Prime said:
No problem. In case you're interested in learning what that just did, you might want read this and this.
Click to expand...
Click to collapse
Thanks for all your help !
Once I saw differents privilages letters i know its about it. Back in days I was working on FreeBSD (amateur) but had to deal with things like that.

Antiga Prime said:
Well, then you should try the following. Open the terminal again, use "su" again to grant root access, and do the following:
Code:
su
cd /mnt/media_rw
busybox chown -R 2800:2800 sdcard0
chmod 0770 sdcard0
Then either try to take a photo or create a file in your internal memory, or reboot and test your internal memory.
Edit: Just to be clear, the default user/owner for Sony internal memory is 2800, mine is set to 1023 (media_rw), as most phones should have, because I have modded the ramdisk in my kernel in order to use a certain program.
Click to expand...
Click to collapse
Working with Xperia V and just fixed my sd card. Thnx :good::good::good::good:

Antiga Prime said:
No problem. In case you're interested in learning what that just did, you might want read this and this.
Click to expand...
Click to collapse
And I'm here again, anew I got same situation but I can't fix it by applying these command. Can you help me? That's what I recieve.

deywid12345 said:
And I'm here again, anew I got same situation but I can't fix it by applying these command. Can you help me?
Click to expand...
Click to collapse
Are you booted up in Android? Maybe Sdcard0 needs to be unmounted first (although I've never had to unmount it). Maybe you should try running the command from recovery when the internal memory isn't mounted (and if it is, unmount it first).

Antiga Prime said:
No problem. In case you're interested in learning what that just did, you might want read this and this.
Click to expand...
Click to collapse
Antiga Prime said:
Are you booted up in Android? Maybe Sdcard0 needs to be unmounted first (although I've never had to unmount it). Maybe you should try running the command from recovery when the internal memory isn't mounted (and if it is, unmount it first).
Click to expand...
Click to collapse
I'm running TWRP 2.8.4.1 (OmniROM 4.4) when I go to mount section and uncheck "sdcard" it doesnt get saved and on reboot it again unmounted. How do I unmount it in right way?

deywid12345 said:
I'm running TWRP 2.8.4.1 (OmniROM 4.4) when I go to mount section and uncheck "sdcard" it doesnt get saved and on reboot it again unmounted. How do I unmount it in right way?
Click to expand...
Click to collapse
I don't think I understand what you're trying to say, but you don't have to reboot in order to unmount the sdcard. All you have to do is uncheck the "sdcard" in the mount section, and then run the chown command.
Then again, how did that happen again? Did you format your sdcard0 (internal memory) again?
Run the "mount" command in Android and see if your "Sdcard0" is formatted as Vfat. If it is, you won't be able to change ownership to the partition unless you format it again in TWRP so that it changes to ext4.

Antiga Prime said:
I don't think I understand what you're trying to say, but you don't have to reboot in order to unmount the sdcard. All you have to do is uncheck the "sdcard" in the mount section, and then run the chown command.
Then again, how did that happen again? Did you format your sdcard0 (internal memory) again?
Run the "mount" command in Android and see if your "Sdcard0" is formatted as Vfat. If it is, you won't be able to change ownership to the partition unless you format it again in TWRP so that it changes to ext4.
Click to expand...
Click to collapse
Yep It happend again by formatting internal storage.
But it's working back again ! Thanks mate!
I formated it via TWRP to EXT4 then adb commands and poof, it works! God bless you.

There are so many dead question threads but the helpfulness shown here just rekindled my faith in humanity

Didn't work for me, this is the output I got:
/system/bin/sh: <stdin>[2]: cd: /mnt/media_rw:
Permission denied
Sent from my Xperia T using XDA Free mobile app

thijs84 said:
Didn't work for me, this is the output I got:
/system/bin/sh: <stdin>[2]: cd: /mnt/media_rw:
Permission denied
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
If you're having trouble to even change directories to /mnt/media_rw/, how do you know that directory exists?
Are you trying that from recovery?

[Q] "no external storage" on KitKat ROMs [Mint]

Hey guys,
I think I'm getting crazy, I tried so many things now, but somehow the internal sdcard is not working on Xperia T with KitKat ROM.
Problem:
When I open the camera app is crashes instantly. Other camera apps say they need an external storage. The gallery says "no external storage"
In the filebrowser I see a lost+found folder but can't open it or do anything (write/read).
In adb shell with su I don't even have the permission to create a folder:
Code:
255|[email protected]:/ # mkdir /storage/sdcard0/test
mkdir /storage/sdcard0/test
mkdir failed for /storage/sdcard0/test, Permission denied
I tried CM12 M10-M12, an OmniRom and AOKP build. (all KitKat based)
I'm using TWRP 2.7.1.0 first, now 2.8.0.1 (2.8.1.0 does not seem to start). I wipe everything in recovery except the external micro sd card with the ZIPs. Then install the ROM and I tried with and without GAPPs. The boot.img is flashed via fastboot.
I tried erasing partitions via fastboot.
I flased CM10.2 (JB) and I could take a photo.
I have 2 Xperia T (Mint) with unlocked bootloader here to test and I don't get it working. But my sister has one too and I installed her CM11 a few month ago and she doesn't have any problems.
WTF am I doing wrong?

Try to enter the following in terminal:
Code:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0

WhiteNeo said:
Try to enter the following in terminal:
Click to expand...
Click to collapse
It works :good: Thank you so much
It seems that it works as long as I don't wipe sdcard. Does this mean TWRP is wiping/formating the partition wrong?

qubbey said:
It works :good: Thank you so much
It seems that it works as long as I don't wipe sdcard. Does this mean TWRP is wiping/formating the partition wrong?
Click to expand...
Click to collapse
The wiping is correct, the problem is that Sony has decided for some reason to use a different user/group than the one used by default in Android (and most other phones, as far as I know). Given that Android (Linux) is a user/group/permission driven OS, if any of these don't correspond to the action performed, there will be no access.
If you format the sdcard from a custom ROM or recovery, it will use user/group 1023 (media_rw), but the kernel is set to use user 2800, therefore you will lose RW access.
This can be easily fixed by modding the kernel to use the "proper" permissions, or simply correct the user/group with a CHOWN command.

Is this common knowledge? I didn't find a thing when I was searching for a solution. But I guess it happened to lot of people.

qubbey said:
Is this common knowledge? I didn't find a thing when I was searching for a solution. But I guess it happened to lot of people.
Click to expand...
Click to collapse
It is definitely not common knowledge, but anyone compiling a kernel and having tinkered with formatting would have noticed this, as did @updateing a few months back and was actually the one who confirmed this to me a few months back when I was modding kernels to get Folder Mount to work.
It just takes a bit of troubleshooting to come to this conclusion, but since it's being asked so many times lately, someone should make it a sticky.

WhiteNeo said:
Try to enter the following in terminal:
Code:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0
Click to expand...
Click to collapse
Hi, I'm having the same problem. After putting in the above, it says: Operation NOT permitted.
What is going wrong?

*-MaCK-* said:
Hi, I'm having the same problem. After putting in the above, it says: Operation NOT permitted.
What is going wrong?
Click to expand...
Click to collapse
You might try running the command without the "-R" first, so you're able to access sdcard0 at all.
If this fails as well, try replacing /mn7/media_rw/sdcard0 with /storage/sdcard0

WhiteNeo said:
You might try running the command without the "-R" first, so you're able to access sdcard0 at all.
If this fails as well, try replacing /mn7/media_rw/sdcard0 with /storage/sdcard0
Click to expand...
Click to collapse
I'd be surprised if that works, given that the proper user/group for /storage/sdcard0 is "root:sdcard_rw", as it is set by default, and not "2800".
@*-MaCK-*:
Did you type in the "su" command first, on it's own?
Are you in fact rooted?
Does your storage have the proper file system format (ext4)?
You can check the file system format by running the command:
Code:
mount

Antiga Prime said:
I'd be surprised if that works, given that the proper user/group for /storage/sdcard0 is "root:sdcard_rw", as it is set by default, and not "2800".
@*-MaCK-*:
Did you type in the "su" command first, on it's own?
Are you in fact rooted?
Does your storage have the proper file system format (ext4)?
You can check the file system format by running the command:
Code:
mount
Click to expand...
Click to collapse
Yes, I'm rooted. And yes, I've typed in the "su"command first.
I think that my storage doesn't have the right format. I think it was vfat?
But now things have changed. After flashing a stock rom, there is only a ejected sdcar0 left. Before i could enter the sdcard0 via device/mnt..... Now, their is no mnt map, and esfile explorer doesn't show anything. It says: "SD card ejected"
It doesn't matter if the data is lost, but i realy like to have access again too the sdcard0 drive!

*-MaCK-* said:
Yes, I'm rooted. And yes, I've typed in the "su"command first.
I think that my storage doesn't have the right format. I think it was vfat?
But now things have changed. After flashing a stock rom, there is only a ejected sdcar0 left. Before i could enter the sdcard0 via device/mnt..... Now, their is no mnt map, and esfile explorer doesn't show anything. It says: "SD card ejected"
It doesn't matter if the data is lost, but i realy like to have access again too the sdcard0 drive!
Click to expand...
Click to collapse
:laugh: It seems like I have fixed it. I managed to install the latest version of TWRP and fixed the format of the sdcard to ext4.
It is formatted and working. Very happy.
After reboot the sdcard0 was visible again. Though, I could not write too it. So I put in the next in the Terminal:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0
After this, averything was normal again!
Thanx you all!:good::good::good::good:

WhiteNeo said:
Try to enter the following in terminal:
Code:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0
Click to expand...
Click to collapse
i have th same problem i write this code but it tell me busybox not found

[Q] Z3C just rooted and Titanium Backup issue

Hello there, I just rooted my Z3C 5803 phone with the exploit founded yesterday (.93 FW) and first thing I did was to install Titanium Backup because there were a lot of programs I wanted to remove for good from this device and also wanted to integrate newer versions into the Rom. Whenever I try to integrate, for example, a newer YouTube, Google Chrome, Google Play Store version into the Rom, TB seems to keep trying and trying forever.
Checking into the TB FAQ i found this:
"14. I tried to integrate system app updates or to convert user apps to system apps but it didn’t work. Why?
These features require a NAND unlocked ("S-OFF") device, in order to write to the ROM.
Depending on the software, some S-ON devices may "remember" modifications made to /system for a while, or until the next reboot. That is not enough for our purpose.
Please search the Internet for information on how to make your particular device S-OFF."
.......but, of course, for me that is Chinese. Doesn´t mean that if I´m root, I can anything I want to the Rom? If not, what do I need to make the phone S-OFF?
Hope someone could help this noob!
Thanks in advance.
Alx

http://forum.xda-developers.com/z3-compact/general/questions-belong-t2868300

Sorry, didnt know that. Will create it in that section.

Use link2sd, be careful

harrymason37 said:
Use link2sd, be careful
Click to expand...
Click to collapse
Would link2sd let me remove and integrate apps from/to the ROM of my cellphone?

S-OFF and S-ON are terms used for HTC phones if i'm not mistaken
Sent from my D5833 using XDA Free mobile app

alxtorrentazos said:
Would link2sd let me remove and integrate apps from/to the ROM of my cellphone?
Click to expand...
Click to collapse
yes, you can remove system app or convert user app into system app just make make sure you grant its superuser request

harrymason37 said:
yes, you can remove system app or convert user app into system app just make make sure you grant its superuser request
Click to expand...
Click to collapse
Thanks Harry . Never used that app before, will have to read a guide about how to do that. I always used TB for that in my old Samsung Xcover 2 phone with Jelly Bean.

alxtorrentazos said:
Hello there, I just rooted my Z3C 5803 phone with the exploit founded yesterday (.93 FW) and first thing I did was to install Titanium Backup because there were a lot of programs I wanted to remove for good from this device and also wanted to integrate newer versions into the Rom. Whenever I try to integrate, for example, a newer YouTube, Google Chrome, Google Play Store version into the Rom, TB seems to keep trying and trying forever.
Checking into the TB FAQ i found this:
"14. I tried to integrate system app updates or to convert user apps to system apps but it didn’t work. Why?
These features require a NAND unlocked ("S-OFF") device, in order to write to the ROM.
Depending on the software, some S-ON devices may "remember" modifications made to /system for a while, or until the next reboot. That is not enough for our purpose.
Please search the Internet for information on how to make your particular device S-OFF."
.......but, of course, for me that is Chinese. Doesn´t mean that if I´m root, I can anything I want to the Rom? If not, what do I need to make the phone S-OFF?
Hope someone could help this noob!
Thanks in advance.
Alx
Click to expand...
Click to collapse
hey , go to the the giefroot folder you downloaded to root your phone , then go to ''files'' folder , and then open a ''cmd window'' there (by pressing ctrl + right click) and then write copy paste these codes one after another
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
i hope it works , i had same issue and i fixed it

sorry, but I´m getting those "not found" msgs and is still the same....TB gets stuck while trying to integrate the files into the ROM
[email protected]:/data/local/tmp # ./systemrw.sh
./systemrw.sh
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xDB2AB789
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
Installing of mount.sh finished
rm failed for /data/local/tmp/memfile, No such file or directory
255|[email protected]:/data/local/tmp #

alxtorrentazos said:
sorry, but I´m getting those "not found" msgs and is still the same....TB gets stuck while trying to integrate the files into the ROM
[email protected]:/data/local/tmp # ./systemrw.sh
./systemrw.sh
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xDB2AB789
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
Installing of mount.sh finished
rm failed for /data/local/tmp/memfile, No such file or directory
255|[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
I had a similar problem until i installed dualrecovery. Now the rw permission persists after reboot.

xpsg said:
I had a similar problem until i installed dualrecovery. Now the rw permission persists after reboot.
Click to expand...
Click to collapse
But I DO have RW permissions over the system folder..............according to ES File Explorer I have "rwxr-xr-x" and those stay after I reboot my device. I can use ES File Explorer to copy files wherever I want. Root is working just fine, is just TB that cannot integrate stuff onto the ROM (neither remove, I only can freeze apps, but I want to remove them for good).

my TiBu seems to work, theres no errors. But it doesnt actually seem to work. I cant uninstall any system apps. It does the process says complete but the apps remain.
Any Solution?
Thanks

I used this tool to access rw to system http://forum.xda-developers.com/showthread.php?p=57043230
[4.4.4] Sony RIC KILLER
After that you will have write permission to system
Sent from my D5803 using XDA Free mobile app

mardrest said:
I used this tool to access rw to system http://forum.xda-developers.com/showthread.php?p=57043230
[4.4.4] Sony RIC KILLER
After that you will have write permission to system
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
I will try that once I'm at home. Weird thing is I tried to copy a file inside the system folder and it worked just fine, so, I do have permissions over the folder..........dont know

This tool dissable the sony ric protection that dissable access to /system
Sent from my D5803 using XDA Free mobile app

pw1nce said:
hey , go to the the giefroot folder you downloaded to root your phone , then go to ''files'' folder , and then open a ''cmd window'' there (by pressing ctrl + right click) and then write copy paste these codes one after another
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
i hope it works , i had same issue and i fixed it
Click to expand...
Click to collapse
This fixed my xposed framework issues! Thank you!

Yeah, that fixed the permissions to install Xposed, but that doesnt work to let Titanium Backup modify the files in the rom. MKLCF2, could you please try to integrate, let's say YOUTUBE or GOOGLE PLAY into the rom ?
I'm still at work and cannot test anything

Try
Code:
su
mount -o remount,rw /system
after that you should be able to mess around with Titanium Backup

Thanks for that tip but 2 things still happens.......I'm still unable to integrate YOUTUBE or GOOGLE PLAY newer versions into the rom AND, everytime I reboot the device is like I lose that option and I have to do the entries again on the terminal..........for example, Xposed keeps asking me "are you root?" when I try to install/update it.
Is there any other solution to this?
TIA