Related
So on my tablet, there is no option in "Application Settings" to turn on USB debug.
I have root and su access and a terminal.
Is there a command in terminal I can issue to turn USB debug on?
On my phone its saved at
/data/property/persist.service.adb.enable
Maybe its the same on your tablet?
Edit: If its in the same place this command should work.(not tested - use at own risk! - worst case scenario...wipe data).
echo 1 > /data/property/persist.service.adb.enable
Sent from my HTC Desire using XDA App
Bingo! That got me going.
Ran that command as 'su'
It didn't come back with any errors, so I assumed it worked.
Plugged into the computer, said recognize device. Listd it as a <NULL><NULL> USB Device.
Go to my My Computer, and it shows an E: drive, but cannot open it. I select to Mount my USB in the notification area and now I can see my SD card.
The code
mercianary said:
On my phone its saved at
/data/property/persist.service.adb.enable
Maybe its the same on your tablet?
Edit: If its in the same place this command should work.(not tested - use at own risk! - worst case scenario...wipe data).
echo 1 > /data/property/persist.service.adb.enable
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
_______________________________________________________________________________________________________________________
Where did you find where that is saved?
Wow! mines located there too and I can change to 1/0 by editing it through text editor program
just so you guys know. what seemed to work for me was to
go to about phone or tablet under settings
scroll to bottom where it shows build number
tap build number 7 times
developer window now shows. This works in android 4.2
This works from a terminal emulator (with root permissions) and from TWRP or any other terminal supporting recovery:
WARNING
Only use this method if you are sure the property files are located under /data/property/...
Enable adb functions:
Code:
echo 1 > /data/property/persist.service.adb.enable
echo 1 > /data/property/persist.service.debuggable
echo adb > /data/property/persist.sys.usb.config
Disable adb function:
Code:
echo 0 > /data/property/persist.service.adb.enable
echo 0 > /data/property/persist.service.debuggable
echo mass_storage > /data/property/persist.sys.usb.config
If it worked for you, a thank you is always appreciated!
okay so im creating a batch file for a little automation just mainly for rebooting the device into bootloader/recovery.. i have gotten most of the way through but at the end i would like for the batch file to stop and allow for further manual input (like i have it set to reboot the device into bootloader and then i would like the window to stop and allow me to MANUALLY input the next command such as flash/reboot/whatever) however i cant seem to find any way of doing that
HERE IS WHAT I HAVE CURRENTLY
it all works perfectly just for the issue i cant seem to work out
ECHO OFF
ECHO ============== CHANING DIRECTORY ==============
CD c:\program files (x86)\android\android-sdk\tools
TIMEOUT 2 /NOBREAK >nul
ECHO ........ Done
ECHO ============== CHECKING ADB DEVICE CONNECTION ==============
TIMEOUT 2 /NOBREAK >nul
adb devices
ECHO ........ Done
PAUSE
:MENU
ECHO.
ECHO ================== ADB MENU ==================
ECHO PRESS 1 or 2 to select your task, or 3 to EXIT.
ECHO.
ECHO 1 - Reboot Device into Bootloader [FASTBOOT]
ECHO 2 - Reboot Device into Recovery [CLOCKWORK MOD]
ECHO 3 - EXIT
ECHO.
SET /P M=Type 1, 2, or 3, then press ENTER:
IF %M%==1 GOTO BOOTLOADER
IF %M%==2 GOTO RECOVERY
IF %M%==3 GOTO EOF
:BOOTLOADER
adb reboot bootloader
GOTO FASTBOOT
:RECOVERY
adb reboot recovery
GOTO RECOVERY
:FASTBOOT
ECHO .
ECHO Waiting for device to reconnect
TIMEOUT 15 /NOBREAK >nul
ECHO ........ Done
ECHO ================== FASTBOOT ==================
ECHO manually type fastboot commands
:RECOVERY
ECHO .
ECHO Waiting for device to reconnect
TIMEOUT 15 /NOBREAK >nul
ECHO ........ Done
ECHO ================== RECOVERY ==================
ECHO Manually handle Clockwork Recovery tasks
ECHO .
ECHO .
ECHO Will automatically close in about 5 Seconds =]
TIMEOUT 5 /NOBREAK >nul
ECHO ....... bye!
I am not sur to understand exactly what you want to do, but you can do what you want in you batch file, it is what you did with for exemple :
- "Reboot Device into Bootloader [FASTBOOT]"
- "Reboot Device into Recovery [CLOCKWORK MOD]"
You have just check the choice with a number and after execute your "code".
So, if you know the "adb script" in addiction of the command you want, go to "code" it.
I remake your script and i especially add an exemple.
- "Execution" and "Code" are more clear.
- It is better for checking error.
- Now, this script is able to check if you are in "64bit" or "32bit", and check if the "ADB Tool" is in his correct way.
- Now, this script is able to check if you have connect or not your device.
- You can see the BootAnimation without "Power OFF" and then "Power ON" your phone.
- It is more beautiful, even if it is not very important.
The new "code", with your previous "started code" :
Code:
Even this topic is solved, i remove my code.
cheers for the reply.. but that was not really what i was after... i did some more googling and what i found was (in the last 2 minutes) that i needed a CMD /K at the end of the file.. which leaves the command window open and i can now enter in fastboot commands manually (for flashing etc)... i have attached the file as a.txt for anyone to use themselves if they were so inclined..
1. just make sure the directory of your adb/fastboot.exe is in the same directory as mine (CD c:\program files (x86)\android\android-sdk\tools) and change the 2 lines if necessary with note pad by opening the .txt normally as yours might be in program files or in platform-tools not tools, etc
2. change the extension to .bat and not .txt
3. chuck it in your task bar/start bar etc for quicker acess
and should be good to go =]
edit: i see the checking that the other fellow put it can do the checking for you.. but for me i knew the directory, etc
So, i did not exaclty understand your aim, but you have found it, so it is perfect.
I remake my previous script to do exactly what you want, and i always check every thing during the execution, to know the mistake when we have a problem. Because my version is for everybody, even if i think it is just for us. (Views: 45)
So if you want it, or someone else, just ask me.
ptit developer said:
So, i did not exaclty understand your aim, but you have found it, so it is perfect.
I remake my previous script to do exactly what you want, and i always check every thing during the execution, to know the mistake when we have a problem. Because my version is for everybody, even if i think it is just for us. (Views: 45)
So if you want it, or someone else, just ask me.
Click to expand...
Click to collapse
no worries mate it was my first time writing an entire script so im pretty stoked with the outcome i tried to keep it looking as real as scripts i have seen as possible.. =]
I will continue to develop this idea : "A easy way to use ADB Menu".
When i will have finish, if you want i will post a link here to it.
ptit developer said:
I will continue to develop this idea : "A esay way to use ADB Menu".
When i will have finish, if you want i will post a link here to it.
Click to expand...
Click to collapse
sure mate.. ill edit the op if you like and can sort something out?
i think the simpler nature allows for much to be automated for mundane tasks... as long as you keep the fastboot commands manual so noobs dont do anything incorrect
I will use what you want, and i will add what i post in my first answer here.
In addition of this, i will post the final "A easy way to use ADB Menu" on a new topic on other section.
And i will post news here, because i think you will look it.
i did OTA update on my mom's galaxy tab 2 7.0 today
the update seems to have worked fine with the exception that there is a yellow text overlay on the home screen
the overlay disappears when running apps or even entering "settings"
the yellow text is located in a transparent box on top of the home screen
its contents are:
PDA: P3110xxxxxxx
Phone: N/A
CSC: P3110xxxxxxxx
H/W : MP 0.600
RF Cal Date: N/A
SMD : 01P, PBA : 04N
CAMERA : N/A, FrontCAM : N/A
TSP : 17
TSK : N/A
Band : N/A, CH : N/A
UART : N/A, USB: N/A
UN : CM808Exxxxxxxx
BATT_LEVEL: 87
Wifi is turned off by default but if I turn it off I seem to have internet access no problem.
Aside from the text, the tab is still usable, but just annoying as hell.
When returning to home screen, sometimes there would be a few seconds delay before the yellow text overlay shows up
Does anyone have any idea how to fix this please?
actng said:
i did OTA update on my mom's galaxy tab 2 7.0 today
the update seems to have worked fine with the exception that there is a yellow text overlay on the home screen
the overlay disappears when running apps or even entering "settings"
the yellow text is located in a transparent box on top of the home screen
its contents are:
......
Wifi is turned off by default but if I turn it off I seem to have internet access no problem.
Click to expand...
Click to collapse
I have exactly the same problem with my friend's tab 2 7.0" (P3110). Some people were lucky enough and the fix described in this thread worked for them, but not for me, unfortunately. I still suggest you to try, though.
[SOLVED]
I've found the solution.
1) backup /efs/FactoryApp and /efs/imei
2) remove /efs/FactoryApp and /efs/imei
3) reboot
4) if device is rooted
Code:
su
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
if device is not rooted, you have to have adb tool from android sdk, after installing sdk run SDK Manager (if it doesn't start, use sdk\tools\android insted) you have to select and install Extras/Google USB Driver, then
4.1) reboot into recovery mode
4.2) install Google USB driver from driver manager (there is a guide for this but I can't post external links yet)
4.3)
Code:
adb shell
4.4) run commands:
Code:
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
This did it for me.
Question
My apologies if the question sounds silly. But trying to figure out how to execute these commands? Are these executed on the device itself? Or are they executed on a computer with the device tethered via USB? I think it is the latter, but if you could confirm, that will be appreciated. What utility is used for executing these commands?
I have Galaxy Tab 7.7, so these instructions may not work ... but I will do some trial and error once I know how to get started.
thanks in advance
ADB works only on computer.
So computer.
TabUser77 said:
My apologies if the question sounds silly. But trying to figure out how to execute these commands? Are these executed on the device itself? Or are they executed on a computer with the device tethered via USB?
Click to expand...
Click to collapse
It depends, if your device is rooted, install terminal emulator (any will do) and proceed according to the first batch of instructions in the beginning of my post. If your device is not rooted proceed according to the second part of my post, you'll have to install SDK and use adb utility from the SDK, this implies tethering your device via USB and typing those commands in adb shell environment.
I have no idea if this instructions will help with Tab 7, but if you backup everything before deleting (changing) it most probably won't do any harm. But, of course, I can't guarantee that.
AlexCzar said:
It depends, if your device is rooted, install terminal emulator (any will do) and proceed according to the first batch of instructions in the beginning of my post.
Click to expand...
Click to collapse
My bad ... did not realize that the terminal emulator is an android app .... will try this our. I have a rooted tab.
You beat me to the answer
__
Sent from my GT-I9300 using xda app-developers app
AlexCzar said:
You beat me to the answer
__
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Btw: Still searching for the solution for my Galaxy Tab 7.7 Model SCH-i815. May I ask you how you came to figuring out your solution? Anything you can do to redirect me to figuring out how to solve this problem?
Thanks in advance
I googled a lot, after all proposed solutions didn't work I sinthesized my own based on those provided - just randomly poked mentioned files and directories - deleted, changed contents and so on. Just don't forget to backup everything before you do that.
Sent from my GT-I9300 using xda app-developers app
Easy way just did it
Rooted phones only go into root explorer root
Efs
Factory app
Factory mode text file
Text editor
Change it to either on or off whatever is opisite of what is there
Save and exit might ask if you want to backup the file just say yes
Restart phone and it will go through prompts
And it will be gone
Sent from sprint note 3 rooted
AlexCzar said:
I've found the solution.
1) backup /efs/FactoryApp and /efs/imei
2) remove /efs/FactoryApp and /efs/imei
3) reboot
4) if device is rooted
Code:
su
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
if device is not rooted, you have to have adb tool from android sdk, after installing sdk run SDK Manager (if it doesn't start, use sdk\tools\android insted) you have to select and install Extras/Google USB Driver, then
4.1) reboot into recovery mode
4.2) install Google USB driver from driver manager (there is a guide for this but I can't post external links yet)
4.3)
Code:
adb shell
4.4) run commands:
Code:
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
This did it for me.
Click to expand...
Click to collapse
Worked, thank god, (and you of course). Had to realize that I needed to go in and delete everything prior to typing out the commands in the terminal emulator, but once I did, that stupid yellow text went away. Again, thanks!
First off, this may seem a noob question, but I am definitely not.
I have an Iconia A200 that now has a broken lcd screen. No display, no touch. I am able to get into the tablet from TWRP via adb, but not from Android (Jelly Bean). It seems I never enabled usb debugging when I installed the custom rooted rom.... I can access the file system and modify anything... Which files need to be modified to enable debugging in Android? Here is what I tried:
Added to default.prop and /system/build.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Edit: Must have had typos... It now works.
workdowg said:
First off, this may seem a noob question, but I am definitely not.
I have an Iconia A200 that now has a broken lcd screen. No display, no touch. I am able to get into the tablet from TWRP via adb, but not from Android (Jelly Bean). It seems I never enabled usb debugging when I installed the custom rooted rom.... I can access the file system and modify anything... Which files need to be modified to enable debugging in Android? Here is what I tried:
Added to default.prop and /system/build.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Edit: Must have had typos... It now works.
Click to expand...
Click to collapse
Ok Sounds good for you. Can you changed the title of your thread by [SOLVED]
Thanks in advance
philos64 said:
Ok Sounds good for you. Can you changed the title of your thread by [SOLVED]
Thanks in advance
Click to expand...
Click to collapse
Ooops.... :good:
How would i do this with my skyrocket? same problem, broken screen, adb disabled. Some instructions would be sweet, cause im not really clear with what you did here.
workdowg said:
First off, this may seem a noob question, but I am definitely not.
I have an Iconia A200 that now has a broken lcd screen. No display, no touch. I am able to get into the tablet from TWRP via adb, but not from Android (Jelly Bean). It seems I never enabled usb debugging when I installed the custom rooted rom.... I can access the file system and modify anything... Which files need to be modified to enable debugging in Android? Here is what I tried:
Added to default.prop and /system/build.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Edit: Must have had typos... It now works.
Click to expand...
Click to collapse
MikeMobes said:
How would i do this with my skyrocket? same problem, broken screen, adb disabled. Some instructions would be sweet, cause im not really clear with what you did here.
Click to expand...
Click to collapse
MikeMobes said:
How would i do this with my skyrocket? same problem, broken screen, adb disabled. Some instructions would be sweet, cause im not really clear with what you did here.
Click to expand...
Click to collapse
I'm going to stay general and assume that a skyrochet is a phone, you have a linux or windows pc with ADB installed (and the drivers to connect to your phone) and have TWRP or CWM Recovery installed already...
1) Start the phone in recovery mode - mine is power down and vol
2) Connect you cable to the pc and start a console terminal or cmd prompt
3) Run the following
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
Once you reboot into Android you should be able to connect via adb.
If you google vnc over adb you can get a usable but very slow vnc connection then install Andriod VNC server for a little better performance.
That's the best I can do from memory ...
workdowg said:
I'm going to stay general and assume that a skyrochet is a phone, you have a linux or windows pc with ADB installed (and the drivers to connect to your phone) and have TWRP or CWM Recovery installed already...
1) Start the phone in recovery mode - mine is power down and vol
2) Connect you cable to the pc and start a console terminal or cmd prompt
3) Run the following
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
Once you reboot into Android you should be able to connect via adb.
If you google vnc over adb you can get a usable but very slow vnc connection then install Andriod VNC server for a little better performance.
That's the best I can do from memory ...
Click to expand...
Click to collapse
I'm booted into twrp 2.6.3 and when i try to run adb devices i just get this
Code:
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
That Baker Guy said:
I'm booted into twrp 2.6.3 and when i try to run adb devices i just get this
Code:
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
Click to expand...
Click to collapse
Enter the following commands:
Code:
adb kill-server sudo ./adb start-server adb devices
The issue is your not running adb server as root.
Hello. Does possible enable accesibility and set default tts via adb shell, and edit default.prop and build.prop?
Thanks and best regards.
workdowg said:
I'm going to stay general and assume that a skyrochet is a phone, you have a linux or windows pc with ADB installed (and the drivers to connect to your phone) and have TWRP or CWM Recovery installed already...
1) Start the phone in recovery mode - mine is power down and vol
2) Connect you cable to the pc and start a console terminal or cmd prompt
3) Run the following
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
Once you reboot into Android you should be able to connect via adb.
If you google vnc over adb you can get a usable but very slow vnc connection then install Andriod VNC server for a little better performance.
That's the best I can do from memory ...
Click to expand...
Click to collapse
OMG! After my screen broke, i raged and became hulk. After 3 hours of internet-searching the hulk found your post and released me to become bruce banner again...
The thank you button was just not enough!
Sorry to resurrect a dead thread, but I need a bit more help with this. I've successfully followed these instructions to enable the adb service on my i9505 with a dead screen, however it hasn't authorised it. When I try to connect I get the following error: error: device unauthorized. Please check the confirmation dialog on your device.
Is there anyway to bypass this confirmation dialog from ADB in recovery (Philz Touch)?
Thanks.
pnz said:
Sorry to resurrect a dead thread, but I need a bit more help with this. I've successfully followed these instructions to enable the adb service on my i9505 with a dead screen, however it hasn't authorised it. When I try to connect I get the following error: error: device unauthorized. Please check the confirmation dialog on your device.
Is there anyway to bypass this confirmation dialog from ADB in recovery (Philz Touch)?
Thanks.
Click to expand...
Click to collapse
I Googled it a little and it seems to be a Samsung thing. Apparently it isn't booting to recovery. Sorry for the lack help
From my Debloated Stock Kitkat VS980 4G VZN
workdowg said:
I Googled it a little and it seems to be a Samsung thing. Apparently it isn't booting to recovery. Sorry for the lack help
From my Debloated Stock Kitkat VS980 4G VZN
Click to expand...
Click to collapse
No, I'm quite sure it is booting to my custom recovery, as I have full ADB access to that. What I'm trying to do is enable ADB access to the Android 4.4.2 proper from my custom recovery. So far following the instructions in this thread I've managed to enable ADB there, but whenever you try to connect to this phone a dialog box is meant to come up asking if you want to accept incoming ADB requests from your computer's key. Unfortunately I have no way of selecting accept (or even seeing that dialog box), so I'm hoping there's a way to bypass it.
Hey mate,
Sorry to necro-bumb the thread. I have been reading and have much similar issue to your self. Maybe some drivers that automatically enable adb, android usb or MTP without debugging enabled might be something to take a look at?
Check this thread out >>> here
Hope that might help (you and I both?)
Besides that I am still searching for a post I saw where you can edit the init-rc in the kernel (the guy explained how to extract the boot.img) and then decompile the kernel, edit the init-rc, recompile the kernel and then flash it back in recovery.
At the moment I am really stuck with a customer device that is bricked, so have a bash script and busybox binary that loads from a signed update.zip that should allow editing of the init-rc and add the lines mentioned in this thread to the build.prop and system.prop.
Fingers crossed it works for a completely stock device :fingers-crossed:
Jarmezrocks said:
Hey mate,
Sorry to necro-bumb the thread. I have been reading and have much similar issue to your self. Maybe some drivers that automatically enable adb, android usb or MTP without debugging enabled might be something to take a look at?
Check this thread out >>> here
Hope that might help (you and I both?)
Besides that I am still searching for a post I saw where you can edit the init-rc in the kernel (the guy explained how to extract the boot.img) and then decompile the kernel, edit the init-rc, recompile the kernel and then flash it back in recovery.
At the moment I am really stuck with a customer device that is bricked, so have a bash script and busybox binary that loads from a signed update.zip that should allow editing of the init-rc and add the lines mentioned in this thread to the build.prop and system.prop.
Fingers crossed it works for a completely stock device :fingers-crossed:
Click to expand...
Click to collapse
Hi mate, did you manage to get into the customers mobile? I have the same problem as I'm locked out with no access to enable USB debugging and a home button which does not work, meaning I can't load recovery mode to wipe the phone
Sent from my C6903 using XDA app
workdowg said:
Code:
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
Click to expand...
Click to collapse
Thank you, I had no clue how, but my phone's (MUCH Snail, aka MUCH W1, aka MUCH 78P01) manufacturer (China's Snail Mobile) had removed from Android's Developer Options menu the option to Enable/Disable USB Debugging.
I was looking all over the web for days, this was the only way I could effectively turn on USB debugging in my phone. Thanks!
There's only one difference, instead of performing the above steps from an ADB console window (for obvious reasons) I did it with Build.prop Editor, but first I needed to change permissions to 666 on the default.prop file (otherwise it wouldn't save my changes).
Curiously, every time I do a full reboot the default.prop file somehow is overwritten with the manufacturer's original settings - that doesn't happen when I soft reboot my device though. Any clues as to what could be reversing my changes at boot?
wmoecke said:
Thank you, I had no clue how, but my phone's (MUCH Snail, aka MUCH W1, aka MUCH 78P01) manufacturer (China's Snail Mobile) had removed from Android's Developer Options menu the option to Enable/Disable USB Debugging.
I was looking all over the web for days, this was the only way I could effectively turn on USB debugging in my phone. Thanks!
There's only one difference, instead of performing the above steps from an ADB console window (for obvious reasons) I did it with Build.prop Editor, but first I needed to change permissions to 666 on the default.prop file (otherwise it wouldn't save my changes).
Curiously, every time I do a full reboot the default.prop file somehow is overwritten with the manufacturer's original settings - that doesn't happen when I soft reboot my device though. Any clues as to what could be reversing my changes at boot?
Click to expand...
Click to collapse
Everytime you boot your phone, the root path is extracted from ramdisk which is usually bound to kernel. As a result, your modification is overwritten. In order to modify files under root path(such as default.prop), you must change the file in ramdisk.
There is many tools and tutorials about this task, I think this is a good point to google.
Addition:
The poster of this thread try to edit default.prop via adb, which is not possible to achieve, at least, for every android device I has hold.
For the unauthorized issue, It's because secure adb, which could be disabled via ro.adb.secure=0, but if there is a ro.adb.secure=1 in default.prop, modification of ramdisk is needed.
Given92 said:
Everytime you boot your phone, the root path is extracted from ramdisk which is usually bound to kernel. As a result, your modification is overwritten. In order to modify files under root path(such as default.prop), you must change the file in ramdisk.
There is many tools and tutorials about this task, I think this is a good point to google.
Addition:
The poster of this thread try to edit default.prop via adb, which is not possible to achieve, at least, for every android device I has hold.
For the unauthorized issue, It's because secure adb, which could be disabled via ro.adb.secure=0, but if there is a ro.adb.secure=1 in default.prop, modification of ramdisk is needed.
Click to expand...
Click to collapse
I had edited both default.prop AND /system/build.prop not knowing which one to use. This worked for me on JB and I used the tablet for a while after that.
From my Nexus 9
workdowg said:
I had edited both default.prop AND /system/build.prop not knowing which one to use. This worked for me on JB and I used the tablet for a while after that.
From my Nexus 9
Click to expand...
Click to collapse
In my view, the /system/build.prop works.
I am a huge noob and i dont really understand where i am inputing that code ?
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell
'adb' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>su
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>mount -o remount,rw /system
'mount' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>cd /
C:\>echo "persist.service.adb.enable=1" >> default.prop
C:\>echo "persist.service.debuggable=1" >> default.prop
C:\>echo "persist.sys.usb.config=mtp,adb" >> default.prop
C:\>echo "persist.service.adb.enable=1" >> /system/build.prop
The system cannot find the path specified.
C:\>echo "persist.service.debuggable=1" >> /system/build.prop
The system cannot find the path specified.
C:\>echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
The system cannot find the path specified.
C:\>
Getting this on S$..any1 here to help me!
HELP!
my Sony Xperia Go ST27i is locked i forgot the PIN for the screen lock. Is it possible to enable USB debugging using PC? my adb is not recognized since usb debugging is not turned on and I can't unlock my bootloader due to this. I can't boot into recovery mode as well.
hayes.asdfg said:
my Sony Xperia Go ST27i is locked i forgot the PIN for the screen lock. Is it possible to enable USB debugging using PC? my adb is not recognized since usb debugging is not turned on and I can't unlock my bootloader due to this. I can't boot into recovery mode as well.
Click to expand...
Click to collapse
Boot into a custom recovery (like TWRP) and try this in Terminal:
Code:
adb shell
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"
reboot
Now reboot to system and see if ADB is working.
If that doesn't help, try this:
Code:
adb shell
setprop persist.service.adb.enable 1
setprop persist.service.debuggable 1
setprop persist.sys.usb.config mtp,adb
reboot
BTW, you can try as many as wrong pins which would enable you to change the pin again via Google account. That's the best way..
GokulNC said:
Drain your phone charge to 0%
Then plug in your phone, but don't switch it ON.
After 15mins, use your regular key combination like power+volumeUp+volumeDown or whatever to get into bootloader menu.
Open up recovery mode or fastboot mode and do whatever you need.
If you want to enable USB debugging, try this in fastboot mode:
Code:
adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
If that doesn't help, try this:
Code:
adb shell
setprop persist.service.adb.enable 1
setprop persist.service.debuggable 1
setprop persist.sys.usb.config mass_storage,adb
reboot
BTW, you can try as many as wrong pins which would enable you to change the pin again via Google account.
Click to expand...
Click to collapse
I have a similar problem in that I can't access my phone and settings. I tried the adb shell and it goes error: device '(null)' not found.
Then I tried the
echo "persist.service.adb.enable=1" >>/system/build.prop but again no good "The system cannot find the path specified."
Does the phone really need to be drained for this to work? My phone charge though I can't see it is around 90%.
On the setprop persist.service.adb.enable 1 is says that 'setprop' is not recognized as an internal or external command, operable program or batch file.
Another question that comes to mind is whether doing factory reset removes root?