Develop Bugs

flashplayer 10.3 not working on rooted evo

my flashplayer 10.3 isnt working never did,on rooted 2.2 evo please help,, thank you!!

Uninstall the update then uninstall flash player (the one that was part of the rom). Then navigate to system/lib and delete libflashplayer.so (I think thats the name of it but I forget) if it is still there. Then download and install flash from the market. That should fix it.

lovethyEVO said:
Uninstall the update then uninstall flash player (the one that was part of the rom). Then navigate to system/lib and delete libflashplayer.so (I think thats the name of it but I forget) if it is still there. Then download and install flash from the market. That should fix it.
Click to expand...
Click to collapse
when i try to deleted the lidflashplayer.so it say cannot be deleted the file system is ready-only, need help....

rotzie said:
when i try to deleted the lidflashplayer.so it say cannot be deleted the file system is ready-only, need help....
Click to expand...
Click to collapse
You can use either root explorer or terminal emulator. You would need titanium backup to uninstall the flash that came with the rom.
If you don't have root explorer here are the terminal commands. Press enter after each command.
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
cd system/lib
ls
After entering ls you will see a list of all the files in this directory. Look through it and find the one file that says libflashplayer.so
If you have libflashplayer.so then do these next commands
Code:
rm libflashplayer.so
mount -o ro,remount /dev/block/mtdblock3 /system
If you don't have libflashplayer.so just issue the mount command to set the system back to read-only (mount -o ro,remount /dev/block/mtdblock3 /system).

i have rootexplorer and i got i deleted,did not use titanium,but my 10.3 player sits in my apps just saying uninstalling.no date,no force stop nothing....

I had the same problem.. I deleted the app and went to explorer and deleted the folder and reinstalled.. works fine now

after the 1 click root - not able to mount some directories in root explorer?

I used the post to install the one click root for the samsung epic 4g (sprint), and it appears to have worked. However - after entering root explorer, only some of the directories allow me to edit files. I click the remount as r/w button but nothing happens. Any thoughts?

sedric1 said:
I used the post to install the one click root for the samsung epic 4g (sprint), and it appears to have worked. However - after entering root explorer, only some of the directories allow me to edit files. I click the remount as r/w button but nothing happens. Any thoughts?
Click to expand...
Click to collapse
Are you sure you granted root permissions to root explorer when it first ran? Run the superuser app from the app drawer and see if root explorer is on the list of apps that are allowed root permission.
I just tried v2.17.2 and it works fine. I tried changing the permissions on /system/xbin/busybox, it said filesystem mounted ro, then I press the mount rw button and redid the permission change, this time it worked no problem.

Thanks for your response-
yes, when i ran root explorer it asked if i wanted to grant superuser and i said yes. some folders allow it to remount, but - say the /system/bin folder - it doesnt allow it at all.

for further background, i used the automated instructions here for my root:
http://forum.xda-developers.com/showthread.php?t=1342728
i did option A like 5 times and also did option C (as i have EK02).
When opening root explorer it tells me that i have super user permissions. one thing to note- if i go to /system/xbin, i do not see a busybox directory. is there something else i should be installing?
in fact, i cant mount anything under the system directory or sub directories, but above that, i was able to change to r/w mode. i could also mount the /vendor directory right beside the /system directory...

If you were able to remount "/" as r/w then the problem isn't with root. That is basicly an "I'm a little bit pregnant situation" Either you are or you aren't.
Now if you weren't able to get root in the first place, then I'd look at the root.
As to busybox, there is no directory. There should be a file /system/xbin/busybox Also there should be a bunch of symlinks from various apps it supports to busybox.

I see - yea i did validate that busybox is not allowing for a mount or any type of change on that file/directory including busybox but the file is present. any suggestions on what else may be locking down this system directory?

I don't know if root file explorer is implemented it's own concept of ro/rw to protect you from making mistakes or it is using the system facilities. If it is using the system facilities, then once you remount /system as rw, then everything under /system is automatically rw. It is all the same partition.
I would try it from "adb shell" (do not type $ or # symbols)
Code:
$ su
# mount -o remount,rw /system /system
# cd /system/xbin
# chmod 755 busybox
If it lets you do that with no errors, then you have remounted /system/xbin as rw and the problem is with root file explorer. For that, you'd have to check with them or someone more well-versed in why that might be failing.

i appreciate your help
I went off googling the adb stuff/installed it and java's jdk stuff. then figured out how to run that adb shell stuff and validated that it worked (permissions were changed in places that this app didnt allow). knowing that the problem is actually with root explorer helps a ton.. as I just assumed it was working

[Q] How do i transfer files to GNex when in recovery mode?

So i've made a mistake. I forgot to download GAPPS but i've already done a factory reset and installed a new rom. I cant seem to mount the usb storage trough clockwork recovery. Is there a way to push the zip file to the device?? Or what should i do?
Thanx

xclusiv8 said:
So i've made a mistake. I forgot to download GAPPS but i've already done a factory reset and installed a new rom. I cant seem to mount the usb storage trough clockwork recovery. Is there a way to push the zip file to the device?? Or what should i do?
Thanx
Click to expand...
Click to collapse
If you only forgot gapps you can restart, the ROM and the phone will work fine you just won't have Google apps. Once it's on you can just copy the file like usual and return to recovery and flash it
Sent from my Galaxy Nexus using xda premium

Good question though. What IF he didnt flash the ROM, how do you get a file on the SDcard if you cant mount it in recovery?

adb push ./"filename.zip" /sdcard

Phone will boot just fine w/o GAPPS.
But you can just use adb push <FILE> <DIRECTORY>
for example:
Code:
adb push gapps.zip /sdcard/

Thanx for the help guys =)

This happens to me all the time. The Mounts section of CWM select "mount as USB" drive. Windows should see this drive and transfer away.

merge5 said:
This happens to me all the time. The Mounts section of CWM select "mount as USB" drive. Windows should see this drive and transfer away.
Click to expand...
Click to collapse
GN internal storage can't be mounted as USB - not even in recovery.
The only way I've found to push/pull files in CWM on the GN is over ADB. If the files in /sdcard/ don't appear, go into mounts and storage, and mount /data. Then try again.

/sdcard/ is nothing more than a symlink to /data/media.
I transfer files over ADB with
'adb push update.zip /data/media/'
no need to mount /data before.

just reboot open up your computer and youll see the gnex just transfer the gapps to your sd card and then reboot in recovery to flash

cmstlist said:
GN internal storage can't be mounted as USB - not even in recovery.
The only way I've found to push/pull files in CWM on the GN is over ADB. If the files in /sdcard/ don't appear, go into mounts and storage, and mount /data. Then try again.
Click to expand...
Click to collapse
Good point. I stand corrected. That was how I did it on my OG Droid. Sorry for the confusion.

bk201doesntexist said:
/sdcard/ is nothing more than a symlink to /data/media.
I transfer files over ADB with
'adb push update.zip /data/media/'
no need to mount /data before.
Click to expand...
Click to collapse
I'm not sure why but CWM on my phone used to auto mount /data and now it doesn't anymore. So to see anything from adb in recovery, I now have to go to mounts first.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
I'm not sure why but CWM on my phone used to auto mount /data and now it doesn't anymore. So to see anything from adb in recovery, I now have to go to mounts first.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
What cwm version are you on, for instance?

Latest CWM touch as of today, and also tried it with latest CWM non-touch.
Incidentally I just bumped into a caveat of transferring files to the GN in recovery mode. The permissions are set strangely when you push files over ADB in recovery, and as a result when booted into the OS I was unable to rename any of the pushed files/folders or put new files in. Since the DCIM directory was one that I'd pushed over, new photos weren't saving. And I did not have permission to change permissions.
This is pretty much a brute force method - so I rebooted into recovery again, mounted /data, did adb shell, cd sdcard, and then:
chmod -R 777 *
And upon booting back into the OS, everything works properly again.
I know that messing with permissions is usually a dangerous thing. My logic was that anything stored in /sdcard is supposed to be a file that any app would be allowed to access as long as it has SD permissions - it's been that way in every version of the OS through to 4.0.
But anyway, if there's something I should do to decrease the "unsafeness" of this situation, please advise me. I guess in theory this would give a malicious app permission to execute code from /sdcard, which would make me more vulnerable?
EDIT: Okay more to report. To see the permissions properly when booted into the OS, you have to go into /data/media rather than /sdcard (same directory but permissions appear differently).
When I went in there and typed ls -n, I found that all the files I had pushed in recovery have UID & GID of 0. All files I had created afterwards had UID & GID of 1023. That explains everything. The owner is root for files that came from ADB in recovery, and media_rw for files created in the OS.
I can use chown, but it looks like the version of chown that comes with busybox does not have -R recursion implemented. Hrm. Aha! In CWM, chown does support -R. And we're off to the races. So from recovery I did:
cd /data/media
chown -R media_rw.media_rw *

cmstlist said:
Latest CWM touch as of today, and also tried it with latest CWM non-touch.
Incidentally I just bumped into a caveat of transferring files to the GN in recovery mode. The permissions are set strangely when you push files over ADB in recovery, and as a result when booted into the OS I was unable to rename any of the pushed files/folders or put new files in. Since the DCIM directory was one that I'd pushed over, new photos weren't saving. And I did not have permission to change permissions.
This is pretty much a brute force method - so I rebooted into recovery again, mounted /data, did adb shell, cd sdcard, and then:
chmod -R 777 *
And upon booting back into the OS, everything works properly again.
I know that messing with permissions is usually a dangerous thing. My logic was that anything stored in /sdcard is supposed to be a file that any app would be allowed to access as long as it has SD permissions - it's been that way in every version of the OS through to 4.0.
But anyway, if there's something I should do to decrease the "unsafeness" of this situation, please advise me. I guess in theory this would give a malicious app permission to execute code from /sdcard, which would make me more vulnerable?
EDIT: Okay more to report. To see the permissions properly when booted into the OS, you have to go into /data/media rather than /sdcard (same directory but permissions appear differently).
When I went in there and typed ls -n, I found that all the files I had pushed in recovery have UID & GID of 0. All files I had created afterwards had UID & GID of 1023. That explains everything. The owner is root for files that came from ADB in recovery, and media_rw for files created in the OS.
I can use chown, but it looks like the version of chown that comes with busybox does not have -R recursion implemented. Hrm. Aha! In CWM, chown does support -R. And we're off to the races. So from recovery I did:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
that would explain it: i always use /data/media, didn't find any permission issues yet. thanks.

[Q] Can't copy files using ADB? (Linux)

Trying to copy over a file from my Linux machine onto my Galaxy Nexus using ADB. The file is in the platform-tools directory as well to make it easier. I am trying to execute "adb push gapps-ics-12172011.zip sdcard", but it keeps saying failed to copy 'gapps-ics-12172011.zip' to 'sdcard': Is a directory. Can someone help me out?

Code:
adb push gapps-ics-12172011.zip /sdcard
The way you had it did not specify a location, but a filename.

Thanks, I'll try this when I get home.
Sent from my Galaxy Nexus using XDA

Still did not work. Found the problem though, the sdcard was under /mnt, so I did /mnt/sdcard and it worked

glad it's working, but remember not to forget the / at the end if you are pushing files to a directory

/sdcard is just a symlink.
Stop directing people to a symlink, which may or not be available.
Folks, equivalent dir to /sdcard is /data/media.

bk201doesntexist said:
/sdcard is just a symlink.
Stop directing people to a symlink, which may or not be available.
Folks, equivalent dir to /sdcard is /data/media.
Click to expand...
Click to collapse
I am not about to start telling people to adb push to /data/media, when /sdcard works fine and is universal, symlink or not. If the symlink is missing, that is kind of their fault, not mine, and they have bigger fish to fry than adb push.

As mentioned above the issue was the lack of trailing /. This command should work:
adb push gapps-ics-12172011.zip /sdcard/

Alternate keyboard for KF 6.3.1?

aruangra said:
This approach works with non-smart keyboards.
1. Install your preferred keyboards from Market
2. Use ES file explore (with Root feature and RW mount enabled in the advanced setting) or use Root Explorer to copy the keyboard .apk file from /data/app to /system/app
3. Reboot and select the keyboard by pressing and holding at any text input box.
4. (optional) Sideload and install "Nookcolor Tools" from http://forum.xda-developers.com/showthread.php?t=868366. You will have an option to set keyboards.
So far this method does not work with
- SlideIt
- Thumb keyboard (thanks fr4nk1yn)
Click to expand...
Click to collapse
I have neither a /data/app folder nor a /system/app folder... My KF is rooted (I'm successfully using the Google Play store, permanent Live Wallpapers and Avast Mobile Security Anti-Theft with root access) so I don't really understand why I am missing those folders. I can even create them without any complaints by Windows, there are no hidden objects. Did the 6.3.1 update change the folder structure?
Can anyone help me?

Okay, while I have still no possibility to access the root level via Windows, I managed to access it with the ES File Explorer (I had to change a setting to make the root level visible).
Now I have a /system/app folder and a /data folder - but unfortunately no /data/app folder; the /data folder is empty!
Furthermore I cannot copy APK-files in the /system/app folder. I get informed that the copy process failed, if I try to. Shouldn't normally a popup of the Superuser app show up with the option to grant root access?
I'm looking forward to any help! Thanks in advance.

I don't like to push threads, but... is there really no one able to help me?

When all else fails, reinstall the ROM.

Uhm, I did not install a custom ROM. Or do you mean, that I should reinstall the stock ROM?

Oh, in that case, I'm sure its your ES File Explorer that is messed up. If you have Terminal Emulator, you can check to see what directories you actually have. Enter:
ls /system
...and...
ls /data
I'll be willing to bet you they are still there.

$ export PATH=/data/local/bin:$PATH
$ ls /system
lost+found
app
bin
build.prop
etc
fonts
framework
lib
media
tts
usr
vendor
xbin
$ ls /data
opendir failed, Permission denied
$
That's what Terminal Emulator says...
How is it possible that I can open /system without having permission for /data?

Type :
$ su
$ ls /data
Envoyé depuis mon GT-I9000 avec Tapatalk

Thanks a lot! I now can see the contents of /data via Terminal Emulator.
But how can I grant superuser permission to ES File Explorer?