Hi,
I have a rooted phone and I'm trying copy dexopt-wrapper to /system/bin but always has the error "permission denied", I'm trying do this with the adb.
When I try "adb remount" I have the error "remount failed: Operation not permitted".
I remount the /system with Root Explorer but always has the error "permission denied" when I make "adb push c:\dexopt-wrapper /system/bin".
Can anyone help me with this, I'm very confused.
P.S. I have root access with adb shell.
Help need with dexopt-wrapper (Solved)
Problem solved.
I fallow this tutorial and it works just fine.
Just one thing, when I decompile the .odex file with the Baksmali I had to use the BOOTCLASSPATH.
To Baksmali and dexopt-wrapper we need to know the BOOTCLASSPATH.
In adb just type: adb shell echo $BOOTCLASSPATH
Related
Thanks for the great job done by developers. However, I noticed mediascape was removed after root. Personally I think mediascape is nice but failed to install it from the app folder on sdcard. Searched the whole thread but didn't find a method.
I tried manually copy the mediascape.apk to /data/app, reboot, then mediascape is restored in the application drawer and can be run functionally.
Here is the details.
Connect the X10 to PC using USB debug mode.
Get the adb.exe ready (you can run it from the root step4 folder directly)
0. Copy mediascape.apk to the step4 folder.
1. Start command prompt as administrater.
2. Change to the step4 folder.
3. Run "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" without quotes.
4. Run "adb shell chmod 777 /data/app" without quotes.
5. Run "adb push mediascape.apk /data/app" no quotes.
6. Run "adb shell reboot" no quotes.
BTW: I have copied all the mediascape related files back to /system/app as well, by running "adb shell chmod 777 /system/app" and using adb push.
Seems it's not ideal as the apk is not installed but added to the X10 directly.
Any better ideas?
Try RealPlayer for Android, it's a new app, really good!
w w w.real.com/realplayer/android
Nah, nothing can beat mediascape.
anyway, how can one get timescape back?
Fuzalert2k said:
Nah, nothing can beat mediascape.
anyway, how can one get timescape back?
Click to expand...
Click to collapse
you mean timescape? or mediascape?
shvyue said:
Thanks for the great job done by developers. However, I noticed mediascape was removed after root. Personally I think mediascape is nice but failed to install it from the app folder on sdcard. Searched the whole thread but didn't find a method.
I tried manually copy the mediascape.apk to /data/app, reboot, then mediascape is restored in the application drawer and can be run functionally.
Here is the details.
Connect the X10 to PC using USB debug mode.
Get the adb.exe ready (you can run it from the root step4 folder directly)
0. Copy mediascape.apk to the step4 folder.
1. Start command prompt as administrater.
2. Change to the step4 folder.
3. Run "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" without quotes.
4. Run "adb shell chmod 777 /data/app" without quotes.
5. Run "adb push mediascape.apk /data/app" no quotes.
6. Run "adb shell reboot" no quotes.
BTW: I have copied all the mediascape related files back to /system/app as well, by running "adb shell chmod 777 /system/app" and using adb push.
Seems it's not ideal as the apk is not installed but added to the X10 directly.
Any better ideas?
Click to expand...
Click to collapse
done this and mediscape still dont apear and cant install it through astro file manager
Can you see mediascape.apk in the /data/app folder? If yes have you copied 4 mediascape files back to /system/app?
Sent from my SO-01B using Tapatalk
hmm I don't seem to have the app folder in my data folder, in my memory card can someone help me out
The data/app folder is not on your sdcard. Up one level.
Sent from my SO-01B using Tapatalk
shvyue said:
you mean timescape? or mediascape?
Click to expand...
Click to collapse
I mean timescape
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
hey is der ne way i can get mediascape running on ne othr device than x10??? just asking
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
How exactly do you do this? What do you edit... siggh
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
This worked for me. Thanks!
Fuzalert2k said:
How exactly do you do this? What do you edit... siggh
Click to expand...
Click to collapse
Turn on USB-debugging mode. Run command prompt (start->run->"cmd"). Change to your step4 directory. Enter those commands line by line.
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
op's method did not work for me but this one worked perfect
it worked now.
thanks so much for the instruction
thanksss it works
would anyone please upload *.apk and *.odex files please, since i cant find em on my x10 anymore. thanks
*.odex files
can some one please share mediascape.odex and MediascapePluginManager.odex files
Both the stock 2.1 gallery and for example doubletwist or poweramp kicks mediascapes ass when it comes to usability, I installed Z's 2.2.1 ROM a week ago and must admit that I dont miss media/timescape one bit Bottom case is that I'll rather use a semi-stable 2.2 ROM than a slow SE rom ;-)
I attempted to set the Android ash shell as default based on a thread here by:
mv /system/bin/sh /system/bin/sh0
ln -s /system/xbin/bb/ash /system/bin/sh
This did not work? Now when i attempt to open shell I see an error:
-exec '/system/bin/sh failed : No such file or directory'
I'm afraid I have screwed up. I thought about writing a small app to execute a shell command to rename the file back to "sh". Would this work? Do I have simpler options?
Any help appreciated
Thanks,
Bill F
Update
Ok, I was able to get the renamed sh file off the phone with adb pull. I renamed it to "sh" and tried to push it back using:
adb push c:\temp\sh /system/bin
but I get an error that says
failed to copy c:\temp\sh to /system/bin/sh : No such file or directory
What should I do?
Thanks,
Bill F
I, too, had a similar problem.
And were you able to fix it?
Bill F
Any answer?
I'm having the same problem. Does anyone have a solution?
bfarley59 said:
Ok, I was able to get the renamed sh file off the phone with adb pull. I renamed it to "sh" and tried to push it back using:
adb push c:\temp\sh /system/bin
but I get an error that says
failed to copy c:\temp\sh to /system/bin/sh : No such file or directory
What should I do?
Thanks,
Bill F
Click to expand...
Click to collapse
So this is probably the wrong place, but I don't see anywhere more applicable, so please move if necessary.
Bought a LG Viper for the wife today, so had to root it
I found a post elsewhere (can't post URLs yet, but it's on androidcentral) that stated how using SuperOneClick, but personally I'm a CLI kind of guy, so this is for anyone using linux (probably could easily be used on Windows, I think you'd need the "LG Universal Drivers", but )
Getting right to the point, you must have adb installed and working.
Notes: Make sure you've got USB Debugging enabled at this point. Might as well make sure "Unknown Sources" are allowed as well.
Go ahead and plug your phone in to your computer now.
Step 1) Find the device on your computer
In /etc/udev/rules.d/51-android.rules add the following (editing as root):
* Note: I had recently rooted a Kindle Fire and had other config in this file, if you do to you can just prefix the lines with a "#" and it will be ignored. You can find the vendor ID by running 'lsusb'
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666", OWNER="YOUR-USERNAME", GROUP="YOUR-USERNAME"
Reboot at this point (or restart udev and logout/in)
Step 2) Grab a copy of "rageagaintthecage" and do the following
adb push rageagainstthecage /data/local/tmp
Step 3) Shell time
adb shell
Once you're in the prompt:
chmod 755 /data/local/tmp/rageagainstthecage
/data/local/tmp/rageagainstthecage
* Note: You'll be kicked out out the prompt at this point, as expected.
Step 4) You've got temporary root (if that's all you want, stop now), otherwise let's make it permanent
adb kill-server
adb start-server
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p27 /system
adb push su /system/bin
adb shell chmod 755 /system/bin/su
Step 5) Install tools
On your phone, download "Superuser" and "Busybox Installer"
Run Busybox Installer
Step 6) Enjoy
Post up any questions, glad to help if possible
Which version of su did you use to push to the device?
The temp root has worked but when I go to install Superuser and update I get this error:
Getting exe path failed with 13: Permission denied
Any ideas? Thank.
-Shaun
When I run RATC, how long do I leave it running? I see the adb shell prompt ($) come up, but then the console feeds a line, and doesn't respond. I eventually press ^C to get back to the windows cmd prompt, but I don't know if I'm doing that too soon (it hasn't spawned all the proc it needs to yet) or if it just doesn't work.
when I type "su" into the adb shell after restarting the server, I get
[email protected]:/ $ su
su
/system/bin/sh: su: not found
I pushed a copy of su into /data/local/tmp and made it executable, but that doesn't work.
127|[email protected]:/ $ /data/local/tmp/su
/data/local/tmp/su
reloc_library[1285]: 15938 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
255|[email protected]:/ $
Any suggestions?
Hello XDA need your support.I am trying to fix a bootloop but I cannot run the ADB SHELL - exec '/system/bin/sh' failed: No such file or directory (2) - when I try to insert the sh file with adb push it sends me Cannot Copy "Read-Only" system
I know I can unlock the /system with the shell codes but my urgent question is how I can insert this sh file because android cant find it
And the most important is then the ADB SHELL is needed for fastboot commands
Any Ideas ?
Q&A for [TUT] Fix Mount System in Kitkat After Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TUT] Fix Mount System in Kitkat After Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
boot.img
Please give me M2 ,D2303, 4.4.2 , 18.3.C.0.37 boot.img
aunggyi2014 said:
Please give me M2 ,D2303, 4.4.2 , 18.3.C.0.37 boot.img
Click to expand...
Click to collapse
heres a .40 one if it helps https://drive.google.com/file/d/0B8tBozpqUuU1R0RnV3VoVXJEUWs/view
d2306 unable to update from OTA
Hi,
I've tried this method and I couldn't update my d2306 with D2306_18.0.C.1.17_PT-BR.ftf (JB) using the Update Center app (I'm really sorry for my ignorance, but this is how we update from OTA, right?). It only said that the update failed and didn't gave any log or reason why.
So I've tried to flash everything, but the kernel, again using the flashtool, as seen in androidclub. But then I got stuck in bootloop.
I've already tried to flash CWM and root from within it, and then, as my phone had come with KK already, I've flashed only the kernel. But then I can't go into custom recovery anymore, and I got the system not writable problem.
For OTA errors check this file :
/cache/recovery/fota/report
Sony ric service for KK 4.4.2 is located at /sys/kernel/security/sony_ric
Assume you have root access on your KitKat, and busybox installed.
Get ready (or compile for yourself) copymodulecrc and ric_disabler_mod.ko written by @cubeundcube from here.
Look at install_tool.sh script, there is everything you need...)
e.g., connect your device via usb......and execute from shell :
Code:
adb push files/copymodulecrc /data/local/tmp/
adb push files/ric_disabler_mod.ko /data/local/tmp/
adb shell "su -c 'chmod 0755 /data/local/tmp/copymodulecrc'"
adb shell "su -c 'chmod 0644 /data/local/tmp/ric_disabler_mod.ko'"
adb shell "/data/local/tmp/copymodulecrc /system/lib/modules/scsi_wait_scan.ko /data/local/tmp/ric_disabler_mod.ko"
adb shell "su -c 'insmod /data/local/tmp/ric_disabler_mod.ko'"
adb shell "su -c 'dd if=/data/local/tmp/ric_disabler_mod.ko of=/system/xbin/ric_disabler_mod.ko'"
adb shell "su -c 'chown root.root /system/xbin/ric_disabler_mod.ko'"
adb shell "su -c 'chmod 0644 /system/xbin/ric_disabler_mod.ko'"
Create a file 00stop_ric, with the following content:
Code:
#!/system/bin/sh
insmod /system/xbin/ric_disabler_mod.ko
Save it, copy to the /system/etc/init.d/ and set access permissions :
Code:
adb push 00stop_ric /system/etc/init.d/00stop_ric
adb shell "su -c 'chown root.root /system/etc/init.d/00stop_ric'"
adb shell "su -c 'chmod 0755 /system/etc/init.d/00stop_ric'"
Put this line at the end of the file init.qcom.post_boot.sh (located in the /system/etc/)
Code:
/system/xbin/busybox run-parts /system/etc/init.d
Test mount:
Code:
adb shell "su -c 'mount -o remount,rw /system'"
p.s
For all written above I used koush/Superuser for root access.
Please help
After rooting, my phone is showing internal storage fill. How can i fix it.