Related
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
dereklane said:
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
Click to expand...
Click to collapse
Do you have debugging enabled?
Yeah, I enabled it after I plugged in my phone
Thread Moved. Not related to Development.
dereklane said:
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
Click to expand...
Click to collapse
if you have debugging enabled, make sure you aren't connected to your computer, that will cause it to crash. other than that i don't know
As long as you have USB debugging enabled, when a program asks for superuser permission, it will prompt you.
-------------------------------------
Sent via the XDA Tapatalk App
I had the same problem but enabled usb debugging and disconected the phone from the computer and SU is working fine again.
I have USB debugging enabled, disconnected from the PC, but I can't get Superuser to prompt (for any apps) when trying to run Autokiller. I just flashed Fresh 2.1.2 coming from FreshToast. Any help?
what version should i use on my Xperia X10a?
hi
i rooted my X10a & have the Superuser Permission install lately. when i click on the icon, it shows a blank screen. i click the menu button > preferences , it shows Action Yap & Notification. there's no apps or anything else. could someone guide me how i get it work?
thanks
For anyone having issues with SU (no matter which ROM) check the permissions on the following two binaries:
/system/bin/su
/system/xbin/su
If they're not 755, connect to the shell via ADB and change them - that's worked for several users on Fresh, my guess is that it would probably work on other ROMs as well.
ok i have some issues...
I have a Moto Blur...
and when i checked the
/system/bin/su --- it only had -r-
/system/xbin/su -- didnt have this file
do you have an idea what's wrong?
thanks
mat
Hi All,
I have updated my GS4 (I9500) from 4.2.2 to stock 4.3 (JSS15J.I9500XXUEMJ9)
All went well, I've rooted it with FC-Auto-root and that went well as well.
My problem is that I don't have adb shell access. I get permission denied every time.
I've started looking and got to the conclusion it is Samsung Knox. So I've upgraded SuperSu to the newest version (that should support Knox issues). When that didn't worked, I've installed Titanium backup and deleted all Knox apps but that didn't solve the issue.
I tried to wipe and restore factory through recovery mode, rooted it again using cwm but still, no shell access (some adb pull and adb push). I tried to run adb root, adb remount but nothing solved the issue.
The weird thing is, that for the first 2 minutes after rebooting the device, I do get adb shell access, but then suddenly the device is like 'reconnecting' and I get kicked out of the device's shell and get permission denied.
Can someone please advice? I tried looking in this forum, I seriously searched all google and couldn't find a solution.. I can't work with it without adb shell.
Thanks!
please help
cheniro said:
Hi All,
I have updated my GS4 (I9500) from 4.2.2 to stock 4.3 (JSS15J.I9500XXUEMJ9)
All went well, I've rooted it with FC-Auto-root and that went well as well.
My problem is that I don't have adb shell access. I get permission denied every time.
I've started looking and got to the conclusion it is Samsung Knox. So I've upgraded SuperSu to the newest version (that should support Knox issues). When that didn't worked, I've installed Titanium backup and deleted all Knox apps but that didn't solve the issue.
I tried to wipe and restore factory through recovery mode, rooted it again using cwm but still, no shell access (some adb pull and adb push). I tried to run adb root, adb remount but nothing solved the issue.
The weird thing is, that for the first 2 minutes after rebooting the device, I do get adb shell access, but then suddenly the device is like 'reconnecting' and I get kicked out of the device's shell and get permission denied.
Can someone please advice? I tried looking in this forum, I seriously searched all google and couldn't find a solution.. I can't work with it without adb shell.
Thanks!
Click to expand...
Click to collapse
anyone? help.. I really don't know what to do..
Thanks.
cheniro said:
anyone? help.. I really don't know what to do..
Thanks.
Click to expand...
Click to collapse
Phone setting > more > about device > Click build number 5/7 times until you see android developer sign , then press go back Developer option > turn it on on top and tick USB debugging. Open supersu app ,check if there's adb or something, click and choose Grant then save.
Didn't solve
Repulsa said:
Phone setting > more > about device > Click build number 5/7 times until you see android developer sign , then press go back Developer option > turn it on on top and tick USB debugging. Open supersu app ,check if there's adb or something, click and choose Grant then save.
Click to expand...
Click to collapse
USB debugging was on. SuperSU don't show adb as authorized apps..
In one of my tries I managed to get SuperSU to ask me to grant permission to adb, and I did. But this didn't help much as well..
I'm lost...
use this adb file. Unpack to dvire C:/ and when you do it this use this command in Cmd :
cd..
cd..
And now you have this in Cmd and write this
C:/> ( write this ) adb shell ( enter )
[email protected]:/ $ ( write this ) su (enter ) and accept on your phone supersu
Link to Adb on Zippyshare ---> http://www70.zippyshare.com/v/73912608/file.html
So I'm rooted on stock 2.66 what's the modifications I could make to enable it?
Sent from my Nexus 6P using Tapatalk
TechMillz93 said:
So I'm rooted on stock 2.66 what's the modifications I could make to enable it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This has been discussed quite a bit in the last few pages of my guide thread. Apparently 2.66 doesn't play ball with Android Pay, try 2.61 instead.
TechMillz93 said:
So I'm rooted on stock 2.66 what's the modifications I could make to enable it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I am using 2.66 and have Pay working. However after flashing the beta and booting I used
adb shell
su
rm -f -r /su/xbin_bind
Rebooted, and pay then worked.
dratsablive said:
I am using 2.66 and have Pay working. However after flashing the beta and booting I used
adb shell
su
rm -f -r /su/xbin_bind
Rebooted, and pay then worked.
Click to expand...
Click to collapse
Don't understand how did u apply adb shell?
Sent from my Nexus 6P using Tapatalk
TechMillz93 said:
Don't understand how did u apply adb shell?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Assuming you have the latest Android SDK installed, and have USB Debugging enabled in developer options (on phone.) plug phone into PC.
Open Terminal
adb devices (To make sure it sees your device.)
if device is found
then
adb shell
$su
#rm -f -r /su/xbin_bind
#exit
$exit
dratsablive said:
Assuming you have the latest Android SDK installed, and have USB Debugging enabled in developer options (on phone.) plug phone into PC.
Open Terminal
adb devices (To make sure it sees your device.)
if device is found
then
adb shell
$su
#rm -f -r /su/xbin_bind
#exit
$exit
Click to expand...
Click to collapse
So simply just flash those statements? Thanks!
Sent from my Nexus 6P using Tapatalk
TechMillz93 said:
So simply just flash those statements? Thanks!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It worked for me. You should also be able to use the terminal from TWRP if you have that installed.
dratsablive said:
Assuming you have the latest Android SDK installed, and have USB Debugging enabled in developer options (on phone.) plug phone into PC.
Open Terminal
adb devices (To make sure it sees your device.)
if device is found
then
adb shell
$su
#rm -f -r /su/xbin_bind
#exit
$exit
Click to expand...
Click to collapse
so when i put ADB devices, it cant find my device.
ive always used the pc, am i doing something wrong?
*edit - i tried it with cmd on the pc and rebooted but android pay still doesnt let me add a card
Didn't work for me either, bummer =/
Check the other threads covered much more in depth and useful
Try this. AP always works for me this way.
Step 1 Flash UPDATE-unSU.zip http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Step 2 Flash SuperSU 2.61 https://download.chainfire.eu/746/SuperSU/BETA-SuperSU-v2.61-20151207213702.zip
When you reboot make sure you select "Do not install" when TWRP offers to install root.
Note: I'm new to XDA, so I've basically made no posts so far. I tried posting this under HTC Bolt/Evo 10, but since I have not made the 10 post threshold yet, I cannot post there, so I just made the post here. If this post needs to be relocated please let me know.
After rooting my phone (HTC Bolt), I foolishly deleted some bloatware applications without backing them up. One of them was TouchPal, a preinstalled keyboard app. I didn't think this would be much of a problem because I already had it disabled in settings and was using a separate keyboard app for other purposes.
However, when I restart my phone, it always asks me to type my pin and "decrypt" the phone. I'm not sure why it does this (previous cell phone didn't), but apparently (this is only a theory) it uses this keyboard application, so I can't actually type my PIN in to decrypt my phone.
I could be completely wrong, and I might have accidentally deleted some other important file from my phone, but either way, I don't know how to fix my phone right now.
I did a bit of research and found out I was supposed to flash a ROM onto my device. However, I don't think I can even connect my device to my computer because normally I would have to enable USB debugging and file transfers.
So basically: is there a way to connect my phone to my computer that would allow me to do whatever is necessary to let me access my phone again? (also should I be flashing a completely new ROM? I should still have everything on my phone except a couple bloatware applications, so is there an easier workaround?)
Update: I got my phone to connect to my PC by booting it in recovery mode. I'll delete this thread if I can successfully flash a ROM.
Hey!
You have already rooted your phone - perfekt!
Now you can start to your bootloader and from there you can flash a twrp recovery if you haven't yet.
If you didn't, there are many tutorials how to do: google: your phone flash custom recovery via fastboot mode
If you have done this - you can easily backup your data with twrp recovery (I think twrp is the best)
After you have done this you can make a full whipe of your system.
If you have done this maybe the failure isnt anymore, but now you have no code to unlock! If the app is still not there - go to apkmirror.com and download the app(there are even system apps). Or just google "xxx.apk download"
After this you can restore your data from twrp!
Summary:
1. Flash recovery. Via fastboot mode
2. Restore your data via recovery
3. Full Wipe
4. Restart
5. If app is still not there - search for APK and install
6. Reboot to recovery (e.g. volume up and home at starting phone, google...)
7. Restore data
8. Restart to system.
I don't know if this Is work, but it's worth to try.
If this don't work: you can transfer data from phone to PC via fastboot mode and then you can flash custom ROM or stock rom,...
I hope this works!
Greets
Ksa
Ksawerion said:
Hey!
You have already rooted your phone - perfekt!
Now you can start to your bootloader and from there you can flash a twrp recovery if you haven't yet.
If you didn't, there are many tutorials how to do: google: your phone flash custom recovery via fastboot mode
If you have done this - you can easily backup your data with twrp recovery (I think twrp is the best)
After you have done this you can make a full whipe of your system.
If you have done this maybe the failure isnt anymore, but now you have no code to unlock! If the app is still not there - go to apkmirror.com and download the app(there are even system apps). Or just google "xxx.apk download"
After this you can restore your data from twrp!
Summary:
1. Flash recovery. Via fastboot mode
2. Restore your data via recovery
3. Full Wipe
4. Restart
5. If app is still not there - search for APK and install
6. Reboot to recovery (e.g. volume up and home at starting phone, google...)
7. Restore data
8. Restart to system.
I don't know if this Is work, but it's worth to try.
If this don't work: you can transfer data from phone to PC via fastboot mode and then you can flash custom ROM or stock rom,...
I hope this works!
Greets
Ksa
Click to expand...
Click to collapse
Thanks for the reply. How would I install the apk onto my device?
ztcfrank123 said:
Thanks for the reply. How would I install the apk onto my device?
Click to expand...
Click to collapse
I remember an easier way.
Maybe you can install app via ADB in recovery mode.
Therefore you need:
custom recovery
ADB tools installed on your PC
USB Driver installed
The APK downloaded from here: https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=TouchPal
If you have done this - reboot to recovery.
Navigate on your PC to the adb tools folder where adb.exe is in it. Open CMD with right click on address line.
Then write in CMD:
adb devices
If your phone is found, adb commands are working.
Then copy the APK in the folder where adb.exe is in it.
Type in CMD:
adb push xxx.apk /system/app(the address where you delete apk)
So maybe this works
So first check:
- custom recovery flashed?
- adb tools installed?
- USB driver installed?
If you have further questions, let me know.
KSA
Ksawerion said:
Type in CMD:
adb push xxx.apk /system/app(the address where you delete apk)
Click to expand...
Click to collapse
How would I find out the address where I deleted the apk? I already had adb, USB drivers, and custom recovery installed.
ztcfrank123 said:
How would I find out the address where I deleted the apk? I already had adb, USB drivers, and custom recovery installed.
Click to expand...
Click to collapse
How did you delete the files?
Nice, then boot into recovery start CMD where you adb is installed and write" adb devices"
Do you see your device?
Ksawerion said:
How did you delete the files?
Nice, then boot into recovery start CMD where you adb is installed and write" adb devices"
Do you see your device?
Click to expand...
Click to collapse
The files were deleted within the phone itself through Titanium Backup, so I have no idea where the file location is. As of now, I can adb push the apk, but I don't know where to push it to.
ztcfrank123 said:
The files were deleted within the phone itself through Titanium Backup, so I have no idea where the file location is. As of now, I can adb push the apk, but I don't know where to push it to.
Click to expand...
Click to collapse
The now try:
adb remount
adb push Xxx.apk /system/app
adb shell chmod 644 /system/app/xxx.apk
adb reboot
Ksawerion said:
The now try:
adb remount
adb push Xxx.apk /system/app
adb shell chmod 644 /system/app/xxx.apk
adb reboot
Click to expand...
Click to collapse
Sorry for the late reply.
The command "adb shell chmod 644 /system/app/xxx.apk" doesn't work for some reason. It says it is not a directory. (I changed the name from xxx to the actual apk name by the way)
ztcfrank123 said:
Sorry for the late reply.
The command "adb shell chmod 644 /system/app/xxx.apk" doesn't work for some reason. It says it is not a directory. (I changed the name from xxx to the actual apk name by the way)
Click to expand...
Click to collapse
Okay then forget this command and only try 'adb push' command, and restart phone maybe it works. Merry Christmas bre
Ksawerion said:
Okay then forget this command and only try 'adb push' command, and restart phone maybe it works. Merry Christmas bre
Click to expand...
Click to collapse
Yeah... I already tried that. Also I tried a bunch of other adb commands like deleting the file and it couldn't find the directory either .
Merry Christmas to you too!
ztcfrank123 said:
Yeah... I already tried that. Also I tried a bunch of other adb commands like deleting the file and it couldn't find the directory either .
Merry Christmas to you too!
Click to expand...
Click to collapse
Was pushing successful? What says CMD after 'adb push'?
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
I managed to flash the recovery, but adb still does not recognise the phone while in recovery mode. I am running out of options and i really need help of some dev to decompile the kernel, edit the init-rc, and to recompile the kernel, so i could flash it on the phone. I was looking at some guides, but i just don't get it how to do that
Click to expand...
Click to collapse
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Stock Rom version: G900FXXS1CPLV_G900FDBT1CPJ1_G900FXXU1CPJ1_HOME.tar.md5
Click to expand...
Click to collapse
Hi,
Why not using latest TWRP custom recovery instead of trying old/outdated and not officially supported CWM?
I have no problem with accessing to ADB from latest TWRP.
TomyVk said:
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Click to expand...
Click to collapse
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
TomyVk said:
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
Click to expand...
Click to collapse
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
TomyVk said:
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
Click to expand...
Click to collapse
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
TheFixItMan said:
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
Click to expand...
Click to collapse
Thank you, it worked. I will now try to enable the usb debugging
TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
TomyVk said:
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
Click to expand...
Click to collapse
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
TheFixItMan said:
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
Click to expand...
Click to collapse
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
TomyVk said:
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
Click to expand...
Click to collapse
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
TheFixItMan said:
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
Click to expand...
Click to collapse
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
TomyVk said:
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
Click to expand...
Click to collapse
No other than the commands I've given you
TheFixItMan said:
No other than the commands I've given you
Click to expand...
Click to collapse
Means the only chance would be to pull a rom and edit it so that adb is enabled and flash it on the device....
Well, i think i got a new hobby xD