Database Users

Guys need help adb is driving me crazy!!!

Right guys,
Im trying to list the apk's in /data/app through adb so i can pull one of them!
I keep getting an error opendir failed permission denied!
BUT!!! I can get into /system/app fine with no problems.
Im running darkyy's 9.5 with his new kernel. Could this be a problem?
Its strange how i can get in system/app but not data/app
I have never had this problem in the past.
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
opendir failed, Permission denied
c:\AndroidSDK\platform-tools>

zolah said:
Right guys,
Im trying to list the apk's in /data/app through adb so i can pull one of them!
I keep getting an error opendir failed permission denied!
BUT!!! I can get into /system/app fine with no problems.
Im running darkyy's 9.5 with his new kernel. Could this be a problem?
Its strange how i can get in system/app but not data/app
I have never had this problem in the past.
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
opendir failed, Permission denied
c:\AndroidSDK\platform-tools>
Click to expand...
Click to collapse
Either :
adb root
adb shell ls /data/app
or
adb shell
su
ls /data/app
Reason /system is accessible is because system is ro by default. So they allow you to browse it knowing u won't be able to do anything w/o root. Whereas /data is rw and hence they restrict you, unless you have root.
Fyi : Wrong section to ask questions.

Daneshm90 said:
Either :
adb root
adb shell ls /data/app
or
adb shell
su
ls /data/app
Reason /system is accessible is because system is ro by default. So they allow you to browse it knowing u won't be able to do anything w/o root. Whereas /data is rw and hence they restrict you, unless you have root.
Fyi : Wrong section to ask questions.
Click to expand...
Click to collapse
I am rooted with superuser...

zolah said:
I am rooted with superuser...
Click to expand...
Click to collapse
The default superuser timeout is 10 secs, either increase it or keep looking at your screen.
PS : Have you tried a an app called Mount R/W? works great.

zolah said:
I am rooted with superuser...
Click to expand...
Click to collapse
Im confused, what are you implying by that response ?
To me that statement was equivalent to "The sky is blue"

Daneshm90 said:
Im confused, what are you implying by that response ?
To me that statement was equivalent to "The sky is blue"
Click to expand...
Click to collapse
..... sigh
You was telling me that i have to have root and su to be able to poke around in /data... i said i am rooted with su obviously as im on custom rom...

zolah said:
..... sigh
You was telling me that i have to have root and su to be able to poke around in /data... i said i am rooted with su obviously as im on custom rom...
Click to expand...
Click to collapse
Yes, but by default, if u dont run
adb root....ur not running the shell in root mode
Also on most roms if u run :
adb shel
u'll see $......
when u type su
u see #
So to enter # mode u need root but still need to execute either adb root or adb shell n then su.
Hope that clears it.

install android commander and forget about command line for simple listing and coping tasks
Sent from my GT-I9000 using Tapatalk

This is what i get ...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb root
adbd cannot run as root in production builds
c:\AndroidSDK\platform-tools>adb shell
/ $ su
su
ls /data/app
ls /data/app
Permission denied
/ $ ls /data/app
opendir failed, Permission denied
/ $

zolah said:
This is what i get ...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb root
adbd cannot run as root in production builds
c:\AndroidSDK\platform-tools>adb shell
/ $ su
su
ls /data/app
ls /data/app
Permission denied
/ $ ls /data/app
opendir failed, Permission denied
/ $
Click to expand...
Click to collapse
I dont see a # anywhere in there...
Are u accepting the dialog on ur phone when u type su ?
There shud b a popup on ur phone once u do that.

Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App

woolf clubs said:
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Maybe he's trying to learn how to navigate using adb. Very useful skillset to acquire imho.
But yes for general purpose, a gui is better.

the plot thickens...
Ill fill you guys in from the start in a short story..
Updated to darkyy v9.5 from v9.3
I thought the phone went a bit funny when it loaded the first boot as on the boot animation it vibrated like crazy and the animation started again as it was going to loop but then the phone loaded...
Been using the phone a few days and everything fine and wanted to pull an app from /data/app
All the above stuff happened and it wouldnt let me.
I thought something wasnt right so i took out the battery for a few minutes and put it back in and went into download mode and plugged my phone into computer to see of odin would still recognise it ok...
My windows vista computer started installing device drivers???? ive had this phone 7 months and plugged in about 100,000,000 times lol
Odin recognised my phone so i rebooted and tried again and now it works fine...
Something weird going on there which is concerning me with it installing new drivers...
This is what i get now and used to get before when i used adb...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
FasterFix.apk
Vending.apk
com.adobe.flashplayer-1.apk
com.android.wallpapersetandsave-1.apk
com.darkyrom.darkyconfig-1.apk
com.ebproductions.android.launcher-1.apk
com.google.maps.apk
com.google.youtube.apk
org.projectvoodoo.controlapp-1.apk
circular_battery_indicator.apk
com.androidapps.spareparts.apk
com.haxor-1.apk
com.sgsinfo.apk
com.sgstoolbox.apk
de.Fr4gg0r.SGS.Tools-1.apk
neldar.bln.control.free-1.apk
ymst.android.homeswitcherfroyo-1.apk
com.android.vending-1.apk
com.handcent.nextsms-1.apk
com.keramidas.TitaniumBackup-1.apk
com.pants.sc.lite-1.apk
com.navigon.navigator_select-1.apk
org.adwfreak.launcher-1.apk
com.speedsoftware.rootexplorer-1.apk
com.anddoes.fancywidget.pro-1.apk
adw.creativethemez.gingerbread-1.apk
com.quoord.tapatalkxda.activity-1.apk
c:\AndroidSDK\platform-tools>
Thank you for all the responses by the way...
Any one have any idea what could have happened?

woolf clubs said:
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
For what i was doing no because i wanted to just quickly pull an apk, decompile it and edit something and compile it and push it back...
Daneshm90 said:
Maybe he's trying to learn how to navigate using adb. Very useful skillset to acquire imho.
But yes for general purpose, a gui is better.
Click to expand...
Click to collapse
I know how to navigate with adb very well. I just couldnt figure out why i was being blocked from entering /data/app...
I even have a video tutorial in my sig that i made showing how to use adb and its commands...
Seems a quick battery pull did the trick although i still now dont know why new drivers where auto installed on reboot to my pc

[Answered] File System read-only after permroot S-OFF

So I just rooted a Glacier out of the box using VISIONary and gfree. Did everything exactly as was supposed to: temprooted, ran gfree, permrooted with "Set system r/w after root" checked, flashed engineering bootloader. Still running stock ROM.
Whenever I try to use adb remount, it fails saying "Operation not permitted." I want to use adb push to write to the file system, but I can't do that without the remount command.
I've tried using terminal emulator to copy a file from the sd card and failed:
Code:
$ su
# cd /sdcard
# cp -f hosts /system/etc
cp: cannot create '/system/etc/hosts':File exists
I've also tried outright deleting a file and failed:
Code:
# cd /system/etc
# rm hosts
rm failed for hosts, Read-only file system
I'm stupefied.

jdkoren said:
So I just rooted a Glacier out of the box using VISIONary and gfree. Did everything exactly as was supposed to: temprooted, ran gfree, permrooted with "Set system r/w after root" checked, flashed engineering bootloader. Still running stock ROM.
Whenever I try to use adb remount, it fails saying "Operation not permitted." I want to use adb push to write to the file system, but I can't do that without the remount command.
I've tried using terminal emulator to copy a file from the sd card and failed:
Code:
$ su
# cd /sdcard
# cp -f hosts /system/etc
cp: cannot create '/system/etc/hosts':File exists
I've also tried outright deleting a file and failed:
Code:
# cd /system/etc
# rm hosts
rm failed for hosts, Read-only file system
I'm stupefied.
Click to expand...
Click to collapse
To be sure you could download a root explorer and see if you can mount R/W
Sent from my HTC Glacier using XDA Premium App

Is there a free application that does this?
Unfortunately, I won't have access to it for the next few days (someone else's phone, and he's going out of town).

the stock rom doesn't except the remount command.
I believe that astro has the remount ability in it. You might want to consider flashing a custom rom though, even if its one of the stock based ones.

option94 said:
the stock rom doesn't accept the remount command.
I believe that astro has the remount ability in it. You might want to consider flashing a custom rom though, even if its one of the stock based ones.
Click to expand...
Click to collapse
I see, thanks very much for the explanation. Is that also why the terminal commands didn't work? Does the stock ROM not allow r/w permissions even if you have superuser permission?
Since it's not my phone, I didn't flash a ROM, only ClockworkMod recovery 3.0.0.6. Next time I see him I'll ask whether he wants to do any firmware changes or not.

jdkoren said:
I see, thanks very much for the explanation. Is that also why the terminal commands didn't work? Does the stock ROM not allow r/w permissions even if you have superuser permission?
Since it's not my phone, I didn't flash a ROM, only ClockworkMod recovery 3.0.0.6. Next time I see him I'll ask whether he wants to do any firmware changes or not.
Click to expand...
Click to collapse
That's correct... I think. all I know is that the stock Rom doesn't usually play well with root lol so yes flash a custom rom
Sent from my HTC Glacier using XDA Premium App

You can make the stock rom rw, but its a pain and I dont really remember the command. Its something like
Code:
mount -o,rw remount /dev/block/mmcblk0p25 /system
That may br right, but if not it wont do any damage. just give you a syntax error.

option94 said:
You can make the stock rom rw, but its a pain and I dont really remember the command. Its something like
Code:
mount -o,rw remount /dev/block/mmcblk0p25 /system
That may b right, but if not it wont do any damage. just give you a syntax error.
Click to expand...
Click to collapse
Ah yes, I remember using that once before. I've since forgotten it since I never use it with my own phone. Alrighty, I'll mark this as answered.

Problem in Rooting DDJP6(after Indian official update)

Need Help for rooting my G3,
Baseband I5801 DDJP2
Kernel: 2.6.32.9
[email protected]#2
Build FROYO.DDJP6
I've rooted earlier, but since official update in India of DDJP6 all the applications which need root access have stopped working, now I'm unable to root or unroot again with superclick(2.1 and 1.7) as it doesn't detects my cell.
Help please, here a snapshot of root checker, it might help.
Superuser.apk -com.noshufou.android.su -version 3.0.6 is installed! System Environment PATH: /sbin /system/sbin / system/bin /system/xbin The adb binary is set to default shell user access as a standard non-root user Standard su binary location: ls -l /system/bin/su: /system/bin/su: No such file or directory Standard su binary location: ls -l /system/xbin/ su: /system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su: /sbin/su: No such file or directory Alternate su type binary location: ls -l /system/ xbin/sudo: /system/xbin/sudo: No such file or directory SU binary not found or not operating properly Results provided on your GT-I5801 device by Root Checker version 3.9 from joeykrim in the
Sent from my GT-I5801 using XDA App

Flash cf-root kernel and you get root instantly, no hassles

Thanks for reply, that was my first post here, will search about flashing that kernel, just got a question, will my phone application and data will get wiped out as I can't use titanium back up now(I'm new to flashing).
Sent from my GT-I5801 using XDA App

Also check if "usb debugging" is enabled, you need that root.
You can also try "z4root"

ashutoshbpl said:
Thanks for reply, that was my first post here, will search about flashing that kernel, just got a question, will my phone application and data will get wiped out as I can't use titanium back up now(I'm new to flashing).
Sent from my GT-I5801 using XDA App
Click to expand...
Click to collapse
No, its just a kernel, it wont wipe anything
umangsagar said:
Also check if "usb debugging" is enabled, you need that root.
You can also try "z4root"
Click to expand...
Click to collapse
z4root wont work on froyo, it uses an old exploit

Since we are talking about it, anyone has link for I5801DDJP6?
And anyone knows the changes between DDJP5 and DDJP6?

Permissions question

This may amount to a n00b question, but here goes: After rooting my Kindle(7.2.3), my GF decided she loved the new look and functionality of it so she wanted me to do the same. Hers was on 7.3, which made the process different, but I was able to do it successfully. I've already installed Market and Google Play, and am now trying to remove the ads by changing Dtcp_apk.apk to Dtcp_apk.bat. However, I keep getting an Operation Failed message. I realize this has to do with changing the permissions, but I can't for the life of me remember how to do it, or where exactly I read it when I rooted my personal Kindle. Any help would be greatly appreciated.

So...
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/app/dtcp_apk.apk /system/app/dtcp_apk.bak"
...doesn't work?

And now, my n00bness shall shine through. Haha. After I rooted the first Kindle(7.2.3), I only had to change the dtcp_apk.apk file to dtcp_apk.bat and it worked like a charm. The method you are describing, I am not familiar with. Is that something I do within a cmd window? I apologize for not knowing, I just didn't have to do it before...

Yes, those are entered from the command line. The first one remounts the system partition as read/write, allowing changes to be made to that partition. The second one simply renames the file so the system can't find it. The "su -c" part tells the shell to run the commands as the root user, needed on stock systems.

I'm guessing your file manager your using doesn't have full root access I use es file explorer and you go into settings root settings and check them all then you can rename that file you don't have to learn to use adb to do this...
Sent from my GT-P3110 using xda app-developers app

mrkhigh said:
I'm guessing your file manager your using doesn't have full root access I use es file explorer and you go into settings root settings and check them all then you can rename that file you don't have to learn to use adb to do this...
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
AHA!!!! This was exactly what I did the last time, but couldn't remember this time around. Worked like a charm. Thank you both for the responses and the help. :victory:

root for 306SH

So I'll update randomly...
boot.img and recovery.img -> https://drive.google.com/file/d/0B5QYBzdG6RuyZy1TSHc2VDVhY2M/view?usp=sharing
temp root:
Code:
adb push root /data/local/tmp
adb push wpoff /data/local/tmp
adb push fbunlock /data/local/tmp
adb push recovery.img /data/local/tmp
adb push boot.img /data/local/tmp
adb shell
$ [COLOR="Red"]chmod 755 /data/local/tmp/root[/COLOR]
$ [COLOR="Red"]chmod 755 /data/local/tmp/wpoff[/COLOR]
$ [COLOR="Red"]chmod 755 /data/local/tmp/fbunlock[/COLOR]
$ /data/local/tmp/root
...
#
defeat WP:
Code:
# /data/local/tmp/wpoff --unprotect-all
check WP status(optional):
Code:
# /data/local/tmp/wpoff --dump
If you see it's all zeroes there it means good, or if there are many 5555 it means NG.
unlock bootloader:
Code:
# /data/local/tmp/fbunlock
install TWRP and patched boot:
Code:
# dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
# dd if=/data/local/tmp/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
install SuperSU:
Code:
FLASH SUPERSU LIKE OLD DAYS
Why patch boot?
Cos MIYABI stops ptrace, some apps depends on it won't work properly.
Chinese here:
禁止转载到国内论坛，禁止用于商业用途。日版不会有的。
Note:
a. Remember to rename recovery.00X.zip to recovery.zip.00X before unzipping!
b. If you don't flash boot.img before install SuperSU, you will end up in boot loop. To restore, delete /system/xbin/daemonsu.
Attachments will be uploaded soon.

Hi tewilove, many thanks for publishing this. Amazing work! And a big time saver

tewilove tnx allot !!
hey some one know how can i put su inside in system and then to use SuperSU ?

thank you a lot

thanks but i can not use root app and super su can not install bin su
thank you for your help

tewilove said:
Tested with a 306SH with SW version S4081.
How to:
https://youtu.be/UJs7ruckGgc
This is v1, since the shell code has to be improved yet(WIP).
It only obtains temp root with kernel context. The left things are changing to init context, disable mmc_protect_part, disable miyabi LSM.
There might be v2, which solves all above, if I have time.
And it also works with many other devices.
For example, 305SH, MI4C, SH-01G.
If it keeps crashing, it should be my hard coded offsets.
PS: Please don't reshare this thread.
PS: Chinese: 请不要转载到贴吧，论坛，谢谢。
Click to expand...
Click to collapse
thank you for your help 谢谢某因幡分享

Please I'd like to know how you did that.could you be more clear, a step by step maybe?
Sent from my D6616 using XDA Free mobile app

salmanaman said:
Please I'd like to know how you did that.could you be more clear, a step by step maybe?
Sent from my D6616 using XDA Free mobile app
Click to expand...
Click to collapse
you can watch the video that tewilove make for us .. but we need to wait when some one unlock protect bcs after you restart phone root will disappear..

tewilove said:
Tested with a 306SH with SW version S4081.
Click to expand...
Click to collapse
How can I know that I got the temporary root? Is this step in the input ID?

all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted

soudara said:
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
Click to expand...
Click to collapse
yes we know about this .. i try to remount system ( with this command : busybox mount -o remount,rw /system) to get permission but my device is restart when i try .. maybe its from this write protection that @tewilove tell us .. if he can tell us how we can install su in system if its possible for now .. ?

ok so for the moment is useless ?

soudara said:
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
Click to expand...
Click to collapse
me too?maybe just kernel root??
---------- Post added at 12:48 PM ---------- Previous post was at 12:31 PM ----------
loonbg said:
yes we know about this .. i try to remount system ( with this command : busybox mount -o remount,rw /system) to get permission but my device is restart when i try .. maybe its from this write protection that tewilove tell us .. if he can tell us how we can install su in system if its possible for now .. ?
Click to expand...
Click to collapse
yea?rootxplore and xposed said no root?

I don't think that folks are understanding what "temp" root means. This solution allows you to achieve root for the current shell session. This does not install the additional binaries to allow other applications to use root access.
With that being said, I am wondering if we can use this temporary elevated access to correct the vulnerability outlined in CVE-2015-1474 affecting /system/lib/libui.so that Sharp has neglected to address in previous OTA updates. The only "corrected" libui.so that I have been able to locate was compiled for v5.0.1 so I am afraid that file would not be compatible with this earlier version of Android on the 306SH. I am not really savvy with in depth programming to be able to fully investigate this and develop a viable solution... anyone who would be able to point me in the right direction would receive many thanks. :banghead:
My apologies if this should have been posted in a separate thread.

awesom! it worked in my 306sh with root permission acquired in shell.

can you use root app and install super su ?

Write protection is keeping us from remounting /system as rw. This prevents us from doing anything that would have any type of impact on the current situation. I want to experiment with attempting to mount partitions with the device powered off... but my device is encrypted so I am unable to access the shell with device off until I perform a factory reset. I am planning on doing that tonight so hopefully I will be able to report back with more information soon.
Sent from my 306SH

soudara said:
can you use root app and install super su ?
Click to expand...
Click to collapse
No. We are working on it though.
On another note, I can't get this temp root to work.
Video of what happens is linked. (too large to attach)
https://mega.co.nz/#!blNTjbhS!p2ljioY_43xlWkpu3EWpj8LvfMVP5eushZT23KLPASk

TechInMD said:
Write protection is keeping us from remounting /system as rw.
Click to expand...
Click to collapse
So I assume, from the quoted text, you have tried mounting /system as rw while in the temp root shell session?

Yes. I tried using the mount command both directly from the root shell prompt plus I tried using busybox to mount also. There seem to be slight variations between them. Also, not sure if it is relevant but I attempted it both through adb and in terminal on the device. I can get to the root prompt but not further.
Sent from my 306SH