Related
Hello guys, please help me out with this problem! I've been working on all day but my phone is still bad...
When I rooted my device BusyBox was supposedly installed by the toolkit I used to root (mskip's).
Then I installed BusyBox installer market app (Stericson's) and it said "BusyBox location could not be found". I thought it wasn't installed so I used the "smart install" with the default values, so it was installed to /system/bin and all the applets were listed as symlinked to /system/bin/busybox
After a while I realized that it was installed both in /system/xbin (by the root toolkit) and in /system/bin (by busybox installer). I used the uninstall option from the busybox installer app to remove it from /system/bin again and leave just one installation to avoid conflicts. This was not a good idea it seems. After uninstalling and rebooting, the phone started to work incorrectly, wifi doesn't work.. and most importantly, USB connection is dead with Android fully booted. the battery charges but the PC doesn't detect it. (It works on Recovery mode though).
I have an idea of what may be wrong. I think the "BusyBox installer" changed all the symlinks to system/bin/busybox, so when it was uninstalled, the phone was left without any of the applets of busybox even though the file /system/xbin/busybox is still present.
Or maybe I'm not really rooted anymore? However, the su binary is still present in /system/xbin/su but I still can't get to work commands like "mount".
How can I fix this problem? I will greatly appreciate any suggestions.
I think it might be fixed by installing busybox to /system/bin or even just copying the /system/xbin/busybox file to /system/xbin/busybox but because the phone is not working correctly I haven't been able to do that...
Here's the information I've gathered so far for you guys to PLEASE help me out with this:
SuperSU is installed and seems to works fine.
"BusyBox Free" installer app doesn't work. If I open it, it shows only black with the three buttons in the bottom but they can't be "clicked. It has been granted root permissions.
"ES File Explorer" gets root permissions but is unable to mount /system as writable (to copy the file).
In a terminal emulator application (Jack Palevich's), this is what I get:
Code:
$ which busybox
/system/xbin/busybox
$ ls
ls: not found
$ busybox ls
(works, outputs the directory content correctly)
$ mount -o remount,rw /system
mount: not found
$ busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$ su
(the terminal emulator app has root permission, but when issuing "su" command, the cursor stays inactive for several minutes and when it finally responds, the following operations are still not succesful. The "su" doesn't seem to work.
$ busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$ /system/bin/busybox --install -s /system/bin
busybox: /system/bin/zcat: Read-only file system
busybox: /system/bin/mountpoint: Read-only file system
busybox: /system/bin/nohup: Read-only file system
My plan is to make the USB work so I can use the toolkit again to restore a stock firmware and clean this mess. Oh, I have stock recovery and stock boot image if that's of any help to know it.
How can I issue the commands I need? or fix this problem?
I have basic linux experience so if you need the output of any command please let me know.
Any help is appreciated. Thank you!
... i think that flashing cwm recovery(.tar.md5) with odin and flashing a root+busybox.zip with cwm recovery should be the fastes way to fix this .... only thing is that it erease your "costum binary count" but with the "Triangel Away" app you can reset that counter ...
Thank you for the hint, enox. I'm will try to install the custom recovery now.
Thanks again enox for pointing me in the right direction. The phone is working again. I'm sharing what I did in case it helps someone in the future:
1) Installed the custom recovery 'twrp', provided by the toolkit (program_folder/recovery/recovery-twrp-2.4.3.0-GTI8190.tar) using odin with the phone in download mode.
2) Flashed this busybox uninstaller using twrp recovery. The phone wasn't working fine yet, so I continued to the following step.
3) Flashed a root+busybox.zip provided by the toolkit (program_folder/root/SuperSU-1.25-Busybox-RenameRecoveryRestore.zip) using twrp recovery.
At this point, the phone was working fine but to be sure that all symlinks were correct, I ran an additional cleaning script which you can find at the end of this post, along with my comments talking to myself while I was troubleshooting the problem.
I'll go to sleep now. Thank you.
Got a PM and I thought it would be better if I reply to it in the forum so others can benefit as well:
andr0id_n00b said:
hey i saw your problem here http://forum.xda-developers.com/showthread.php?t=2233942 and iam glad u solved your problem
can you please tell me what toolkit do you use ??
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
mskip's toolkit for Samsung Galaxy S3 Mini:
http://forum.xda-developers.com/showthread.php?t=2185700
Big thanks to him too, for providing that noob friendly yet full-featured toolkit
same with xperia mti27i
ive exactlly made the same but with my xperia mt27i android4.0 ics i dont i know what to do i dont have exp. with android so please help
Ok, I don't think I'm the only one out there that lost root after the JB OTA update today... Anybody else? I was using Voodoo OTA RootKeeper and everything.... Crap... Any news on an exploit yet?
Lost root too. Rootkeeper didn't do it's job. Now just waiting for a solution.
Not sure how useful but someone on the main JB update thread mentioned they were able to restore with a few adb commands. Apparently for some OTA keeps root but doesn't reinstall it correctly with the button and a few adb's will regain it. FWIW.
Odd, mine kept root without an issue. I'm curious why it's different for some.
Mine kept it but I did the full download and booted to stock recovery and did flash update.zip. then restored root
Sent from my DROID BIONIC using xda app-developers app
neo1738 said:
Not sure how useful but someone on the main JB update thread mentioned they were able to restore with a few adb commands. Apparently for some OTA keeps root but doesn't reinstall it correctly with the button and a few adb's will regain it. FWIW.
Click to expand...
Click to collapse
I've looked and looked for any ADB commands to fix root and cant find them, do you have a link to the post? Thanks
Ok, I've also tried Dan Rosenburg's Motochopper exploit and that didn't work either.... We might be stuck without root until a viable exploit pops up.
awaiting for root too.
Hmmm. I kept root using ota root keeper. Just selected protect root and ashed in recovery the new jb
Sent from my DROID BIONIC using xda app-developers app
have you try the razr-blade exploit?
Updated SU with stock ICS, installed Voodoo, backed up root, flashed JB and restored root. I have SU and voodoo says successful but superuser is not working. Tried, razr-blade, and MotoChopper, both a no-go.
I used Voodoo, Updated to JB, and re-rooted unsuccessfully. I've even tried to go in and restore Su manually and change it's permissions but nothing seems to be working. :/
I lost root, but you can bring it back! NOTE: This will ONLY work if you backed up root with Voodoo OTA RootKeeper prior to updating to Jelly Bean!!!
Make sure you have android debugging enabled and mount it as a media device.
Follow these instructions: (copied from another site)
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb (type "adb shell" without the quotes to log on)
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Hope this helps you guys!
Does anyone have the fixed dropbox link for the post above?
So I managed to get root back. Then I downloaded SuperSU and when I tried to update binaries, I lost root. Is there a fix for that?
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
I just googled part of the text and found the source I think
chetmichaels said:
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
I just googled part of the text and found the source I think
Click to expand...
Click to collapse
Yup, that looks right. If this ceases to work soon as well I will go ahead and upload it to my Dropbox as I still have the su file. I included that link you provided into my post above.
Frankie1588 said:
I lost root, but you can bring it back!
Follow these instructions: (copied from another site)
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Hope this helps you guys!
Click to expand...
Click to collapse
your download link is not working can you check the link.
briafalk said:
your download link is not working can you check the link.
Click to expand...
Click to collapse
Check now. I fixed the link. Sorry about that guys!
Frankie1588 said:
Check now. I fixed the link. Sorry about that guys!
Click to expand...
Click to collapse
I am stuck at steps 3 and 4, it does not seem to be working for me. I am not getting root through adb.
Hello
Is there a solution to have adb with root access with a stock kernel ?
Or the only way is to unlock the bootloader and flash an alternative kernel ?
Thanks.
Adb can access stock ROM with root rights on stock kernel.
Just type "adb su" and you'll get prompt to allow superuser access to your device. But you should be rooted in order to do this.
And having unlocked Bootloader is very necessary to flash custom kernel
Sent from my C5302 using XDA Free mobile app
My bad, I forgot that.
I was trying using "adb root" and it answers something like impossible.
Thanks !
No problem
Always there to help
Sent from my C5302 using XDA Free mobile app
To fully use the adb root function on your device it has to be rooted;
So when rooted just enter the following commands:
Adb shell >enter<
Su >enter<
- A SuperUser prompt will appear on your device press approve or ok or whatever
And you can now use adb with your phone and root rights
~~ Regards
mrjraider said:
To fully use the adb root function on your device it has to be rooted;
So when rooted just enter the following commands:
Adb shell >enter<
Su >enter<
- A SuperUser prompt will appear on your device press approve or ok or whatever
And you can now use adb with your phone and root rights
~~ Regards
Click to expand...
Click to collapse
No. Even running a shell as root I continue with:
- adb root : "adbd cannot run as root in production builds"
- adb push xxxx /system/xxxx : failed to copy 'xxxx' to '/system/xxxxx': Permission denied
I think the only way to do that is to have a rooted kernel.
Last one is because /system is Read-Only
~~ Regards
mrjraider said:
Last one is because /system is Read-Only
~~ Regards
Click to expand...
Click to collapse
Nope ...
it's rw, verified ...
oh it is RW protected ofcourse
~~ Regards
mrjraider said:
oh it is RW protected ofcourse
~~ Regards
Click to expand...
Click to collapse
? rw protected ?
Without proper root you cannot push files to /system.
I even had issues with adb pull /system
To be honest I have no idea.
~~ Regards
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
dry3333 said:
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
Click to expand...
Click to collapse
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
ajbiz11 said:
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
Click to expand...
Click to collapse
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
dry3333 said:
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
Click to expand...
Click to collapse
That's exactly what I'm referring to (The settings thing)
Lemme go find that command for you
---------- Post added at 06:00 AM ---------- Previous post was at 05:56 AM ----------
Wish I knew this existed when I was working on the L port
There's an app to do exactly what you need without looking up partitions
https://play.google.com/store/apps/details?id=com.beansoft.mount_system
Although if you want to go through terminal, here's a tutorial
http://ckirbach.wordpress.com/2012/11/27/how-to-remount-system-as-read-write-in-android/
Basically, you use grep to find the name of the system partition, then run the mount command to remount the partition you found in that precious step
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
dry3333 said:
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
Click to expand...
Click to collapse
The remount app should do exactly that
Try the command option and make your changes then reboot
ajbiz11 said:
The remount app should do exactly that
Try the command option and make your changes then reboot
Click to expand...
Click to collapse
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
dry3333 said:
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
Click to expand...
Click to collapse
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
ajbiz11 said:
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
Click to expand...
Click to collapse
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
You can remove it from the ViperROM zip and format ONLY system and reflash
That SHOULD work
That's like...the be all end all
dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
nkk71 said:
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
Click to expand...
Click to collapse
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
dry3333 said:
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
Click to expand...
Click to collapse
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
nkk71 said:
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
Click to expand...
Click to collapse
The windows drivers don't work with recovery mode (usually)
ajbiz11 said:
The windows drivers don't work with recovery mode (usually)
Click to expand...
Click to collapse
they do for me, but sometimes (after flashing a new/different version) i have to manually select the drivers, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
dry3333 said:
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
Click to expand...
Click to collapse
sure, no problem :good: :good:
if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title
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