Hi all, I just downloaded one of the battery widgets from the market, and as soon as when I set up my brightness to 0 from the widget, screen went black. I still hear incoming calls and the notification sounds but nothing actually appears on the screen. I tried the hardreset (volume buttons + power), and odin3 system recovery, didn't fix the problem. I know this is not a screen damaged issue because the booting animation still plays... So does anyone know how to change my brightness settings using odin3? Or any solutions?
Thank you.
If you have usb debugging turned on, adb to it and rm the apk of the app you installed and reboot
Or if rooted, go in through adb via recovery
I don't have debugging mode on nor the phone is rooted. This is annoying..
I would try to use ODIN to install clockwork recovery. Then adb to the phone and do this:
$ ./adb -d shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
# reboot
is my phone need to be rooted to perform those steps?
U r screwed. Not to be a **** bit likely if Odin won't fix it u will have to take it all the way back.
Sent from my SCH-I500 using XDA App
nitroxeno said:
I would try to use ODIN to install clockwork recovery. Then adb to the phone and do this:
$ ./adb -d shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
# reboot
Click to expand...
Click to collapse
anyone notice that the adb command sqlite3 doesn't seem to exist on our fascinates? I swear I used it by default on my droid inc, but then again I was running custom roms... is that command just not on the fascinate?
Good calk forgot all about clockwork with Odin. Good save
Sent from my SCH-I500 using XDA App
What about a hard reset?
There should be a sticky about this.
Related
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
lakeside00 said:
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
you can remove the HtcLockScreen.apk from /system/app/ and it will default to the stock android one. Problem is that is suffers from the same fate as many others where the slder is up/down and the time is jummbeled on the left side.
Oh and of course to remove/rename the file in /system/app/ you must be rooted and in recovery mode.
I'm working on how to fix the screen. Flipz did it for android 2.0 but it isn't the same fix in 2.1. If I get more info I'll post back.
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
gmelchert said:
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
Click to expand...
Click to collapse
LOL! love the step by step edits...
I have a script that makes it easy, it is just a modified version of Toast's. It cuts it down to one command input instead of three.
Any way here are the steps:
With phone on plug it into your computer. Open two command windows. Navigate one to the folder you have downloaded toasts recovery script to.
1) In the window that is at evo-recovery> type: adb reboot recovery
This boots you in to the stock recovery
2)in the same window type windows-recovery.bat (adjust for your OS)
This gets you into Amon-RA's recovery
3) Wait for the phone to get the new recovery screen. In the other command window type: adb shell mount -a
Step 3 can be adb remount or you can type adb shell then at the # type #mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system
Any way after that point you can exit adb shell back to the command prompt and push/pull anything to /system
unfortunately you can't see it right away and have to wait for reboot. Also this limits some of the apps that we can install because some will need to write to /system and cannot once rebooted.
when i try to do adb remount i get the following message: remount failed: Operation not permitted
I have search trying to find and answer and dont see much of anything. The device is listed when i do adb devices. I did do some cleanup on my sdcard and saw something about boot img in one of my searches. I'm wondering if accidentally deleted something???
you are rooted?
Sent from my HERO200 using XDA App
yeah have been rooted for months. I was using 2.2 froyo, then nandroided back to 1.5. adb remount worked fine the first time. THen i cleaned somethings off my sdcard (not sure if this matters), and since then adb remount doesnt work. if i do an 'adb shell' then su, everything works still?
edit: btw, this is not while in recovery. this is while the phone is fully booted.
the sd card is irrelevant to the remount command. Something is keeping you from having root privledges via adb. Maybe try Ruu again and then re-root and load up your rom?
it's probably the rom you are using, it my be secured connect the phone to your computer, open a command prompt, cd into the android-sdk/tools folder and enter
Code:
adb pull /default.prop
then go into the android-sdk/tools folder and open the default.prop file in wordpad or notepad++
look for the line
Code:
ro.secure=
if it is set to 1 it is secured and adb remount will not work, you can still mount the file system temporarily manually though.
make sure debugging is enabled
yeah i think it has something to do with this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
i tried to change the 1 to 0 in recovery mode, but when it booted back up again it still shows 1???
dbldown768 said:
yeah i think it has something to do with this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
i tried to change the 1 to 0 in recovery mode, but when it booted back up again it still shows 1???
Click to expand...
Click to collapse
i think those files are overwritten every time you reboot, if you really love the rom and you need rw support built into the rom, you can take a nandroid backup of that rom and use the kitchen here and add it to the rom rebuild and reflash it.
After 2 days of testing i think i have a clean solution to fix the mobile data drain by setting the preferred network mode to 1 (GSM only). No need to delete or rename anything. Just update the db that is already there .
You need a rooted device for this.
Extract the sqlite3.zip and push to your device with the following commands:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell
su (to gain root permissions)
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
reboot
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
Sure, as long as you have some sort of terminal emulator installed.
agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
with root explorer and a terminal app (eg connectbot) you can do it.
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Thanks! Mine is done. I'll report back later after I charge and give it a go.
mrkrabs said:
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
_motley said:
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
Click to expand...
Click to collapse
couldn't describe it better
2g = only poll cell if request is made that needs cell, 3g = poll all the time, which means that if you change to only 2g then it should not check for cell if you are in wifi range.
I am sure thats how the tech works if i remember my time at nokia right LOL
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
kinnerc said:
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
Click to expand...
Click to collapse
Default value is 0 (zero).
agentdax5 said:
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Click to expand...
Click to collapse
It's not about what your stats say, but what your mA drain is. i loose only a couple of % in a night (sleep).
edgemaster191 said:
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
Click to expand...
Click to collapse
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
FTFY. 10char.
I am going to have to run some logs....just not seeing any drain that would justify doing this ....will definitely keep an eye out for it though
nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
such things will be able with kernels that overwrite the default.prop
matguard said:
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
Click to expand...
Click to collapse
i was able to finally get it, i copied the splite3 to /system/bin using root explorer, ran chmod through terminal emulator then ran the final command from adb shell.
not ideal but it worked
Anyway to do this via adb? Found No Lock app in market...but I need to run the app first and enable no lock. Then it doesn't apply on boot.
I'm trying to unlock a friends phone without resetting data. Btw...this phone I'm trying to unlock is rooted. She's an idiot and forgot the pin she used and thinks she pressed the wrong pin....twice to confirm. Lol
I know its possible. I just need to find an app that runs/opens after I adb install it. And applies on boot. Or maybe a shell command to open it?
Edit:
***confirmed****
This works for pattern. I need PIN. Can anyone help?
> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
> adb reboot
Sent from my DROIDX using XDA App
andrewp3481 said:
Anyway to do this via adb? Found No Lock app in market...but I need to run the app first and enable no lock. Then it doesn't apply on boot.
I'm trying to unlock a friends phone without resetting data. Btw...this phone I'm trying to unlock is rooted. She's an idiot and forgot the pin she used and thinks she pressed the wrong pin....twice to confirm. Lol
I know its possible. I just need to find an app that runs/opens after I adb install it. And applies on boot. Or maybe a shell command to open it?
Edit:
***confirmed****
This works for pattern. I need PIN. Can anyone help?
> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
> adb reboot
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
did you try sqlite> update secure set value=0 where name='lock_pin_autolock';
edit:
if that doesnt work do this please:
> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=65536 where name='lockscreen.password_type';
sqlite> .exit
# exit
> adb reboot
that should remove all passwords on lock screen. i cant try here at work but i can once i get home if you like.
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