[SOLVED] - Manually enable adb debugging from recovery

[workdowg]

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

persist.service.adb.enable=1                                                    
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

Edit: Must have had typos... It now works.

 

[gyanendra07]

same problem

hello there, how do you connect your android devices if the adb debugging is not enable? when i open cmd and type adb devices, it says no devices/emulators found even though i connect my phone via usb cable and in recovery mode. please help me with this problem. my phone is lenovo a369i.

same problem with me
i have samsung galaxy grand max SM-G7202
i installed all drivers adb present on the web but my device was not detected please help me i have very important documents on my phone

 

[Droidriven]

same problem with me

i have samsung galaxy grand max SM-G7202

i installed all drivers adb present on the web but my device was not detected please help me i have very important documents on my phone

If your device can not boot into system, ADB will not work on your Samsung device unless your device device is rooted and/or has TWRP recovery installed on the device.

Sent from my SM-S767VL using Tapatalk

 

[Cepasaccus]

I try to find a solution for my boot problem without a full wipe and I would like to look at the logs to get information why it is stuck. The behavior is that it is doing endlessly the arc animation with a little pause every sixth arc and I can't turn off with the power button. I did what is written in the fifth posting here to turn on adb. Unfortunately I have adb only in TWRP and not in the Android booting process.

Is there something wrong with what I did to enable adb? Or is adb not starting that early in the boot process and it can't work?

Samsung S5 with Lineage 16

 

[Droidriven]

I try to find a solution for my boot problem without a full wipe and I would like to look at the logs to get information why it is stuck. The behavior is that it is doing endlessly the arc animation with a little pause every sixth arc and I can't turn off with the power button. I did what is written in the fifth posting here to turn on adb. Unfortunately I have adb only in TWRP and not in the Android booting process.

Is there something wrong with what I did to enable adb? Or is adb not starting that early in the boot process and it can't work?

Samsung S5 with Lineage 16

What did you do to cause the bootloop? If you were on stock then flashed a custom ROM but did not factory reset, wipe cache and wipe dalvik cache when you flashed the ROM, that is why you are getting a bootloop. You can't flash a custom ROM over stock without wiping. If this is what you did, boot into TWRP and factory reset, wipe cache and wipe dalvik cache then see if it reboots correctly.

If this is not what caused your bootloop, try booting into TWRP, select the Wipe option then select the "advanced wipe" option, then select only the cache partition and dalvik cache, then wipe them and try rebooting.


Sent from my SM-S767VL using Tapatalk

 

[Cepasaccus]

The last thing I did before the boot loop was to install Yalp as system service. I did already wipe cache and dalvik, up- and downgrade, remove all traces of yalp by deleting packages and editing text files, wipe system partition and reinstall. I did not yet do a fresh install. I would like to avoid that if possible and thought that I could get logging information via adb.

 

[Cepasaccus]

The new nightly solved the problem.

 

[lucfig]

Hi,

I have a galaxy A20 with a broken screen.

Imanaged to boot into recovery and adb detects the device which is rooted with magisk.

But when i try the "su" command after "adb shell", it returns:

/sbin/sh: su: not found

The mount command returns:

rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1392352k,nr_inodes=348088,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=1392352k,nr_inodes=348088)
none on /sys/kernel/config type configfs (rw,relatime)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/mmcblk0p28 on /cache type ext4 (rw,seclabel,relatime,i_version)
/dev/block/mmcblk0p32 on /data type ext4 (rw,seclabel,relatime,resgid=5678,i_version,data=ordered)
/dev/block/mmcblk0p32 on /sdcard type ext4 (rw,seclabel,relatime,resgid=5678,i_version,data=ordered)

Can anyone give me a direction?

Thanks

 

[NFSP G35]

Just because the android system has su doesn't mean the same applies for recovery

 

[lucfig]

Just because the android system has su doesn't mean the same applies for recovery

So I should add su to the recovery? Is that it?
If it is the case, do you have any suggestion on how to do that?

Thanks,

 

[Droidriven]

So I should add su to the recovery? Is that it?

If it is the case, do you have any suggestion on how to do that?



Thanks,

No, you won't be able to get stock recovery to work with su. If your recovery/system has the option to mount system in stock recovery, this "might" enable the use of certain adb functions to modify system.

Other than that, you'll need a custom recovery such as TWRP to achieve what you are looking for.

Sent from my SM-S767VL using Tapatalk

 

[lucfig]

No, you won't be able to get stock recovery to work with su. If your recovery/system has the option to mount system in stock recovery, this "might" enable the use of certain adb functions to modify system.

Other than that, you'll need a custom recovery such as TWRP to achieve what you are looking for.

Sent from my SM-S767VL using Tapatalk

I'm almost sure that I have TWRP installed. But I cannot see my screen.
A long time I do not boot in recovery, but I think I flashed TWRP when I rooted the device.
And from the mount command, I dont know which is the system partition. If adb do not have root access does it become hidden?

 

[Droidriven]

I'm almost sure that I have TWRP installed. But I cannot see my screen.

A long time I do not boot in recovery, but I think I flashed TWRP when I rooted the device.

And from the mount command, I dont know which is the system partition. If adb do not have root access does it become hidden?

If you can't see the TWRP screen when you boot into recovery, that means TWRP probably didn't flash correctly.

Sent from my SM-S767VL using Tapatalk

 

[NFSP G35]

If you can't see the TWRP screen when you boot into recovery, that means TWRP probably didn't flash correctly.

Sent from my SM-S767VL using Tapatalk

He can't see the screen because it's broken

---------- Post added at 12:13 AM ---------- Previous post was at 12:11 AM ----------

I'm almost sure that I have TWRP installed. But I cannot see my screen.
A long time I do not boot in recovery, but I think I flashed TWRP when I rooted the device.
And from the mount command, I dont know which is the system partition. If adb do not have root access does it become hidden?

In adb, try just running the command:
twrp

That will tell you if your recovery is TWRP or stock. If it's TWRP, you can use that command to back up stuff

 

[lucfig]

He can't see the screen because it's broken

---------- Post added at 12:13 AM ---------- Previous post was at 12:11 AM ----------



In adb, try just running the command:
twrp

That will tell you if your recovery is TWRP or stock. If it's TWRP, you can use that command to back up stuff

Thanks. Tried and it TWRP is indeed installed. So I am bacck to the main issue. Any idea why I cannot do any of these ?

• see the system partition with the mount command
• su command returns there is no su in sbin
• cannot see or moodify the build.prop

see the system partition with the mount command

 

[NFSP G35]

Thanks. Tried and it TWRP is indeed installed. So I am bacck to the main issue. Any idea why I cannot do any of these ?

• see the system partition with the mount command
• su command returns there is no su in sbin
• cannot see or moodify the build.prop

see the system partition with the mount command

Magisk is a systemless root, meaning it doesn't modify your system partition. On some devices, modifying the system partition can result in boot loops or even a brick.
You mentioned you have a broken screen, what is your goal with this device? IOW, why are you trying to enable ADB? If it is for the purpose of backing up things that you have on the phone, then you can do that with the TWRP adb

 

[lucfig]

Magisk is a systemless root, meaning it doesn't modify your system partition. On some devices, modifying the system partition can result in boot loops or even a brick.

You mentioned you have a broken screen, what is your goal with this device? IOW, why are you trying to enable ADB? If it is for the purpose of backing up things that you have on the phone, then you can do that with the TWRP adb

I wanted to remove the lockscreen password and backup with titanium backup.
But you are right, will learn how to use the twrp command. After backing up, do you suggest any app for Android or windows to explore the backup and restore in a different device (also different model)?

Enviado de meu HD1903 usando o Tapatalk

 

[NFSP G35]

I wanted to remove the lockscreen password and backup with titanium backup.
But you are right, will learn how to use the twrp command. After backing up, do you suggest any app for Android or windows to explore the backup and restore in a different device (also different model)?

Enviado de meu HD1903 usando o Tapatalk

The donate version of Titanium has "extract from ADB backup" and "extract from Nandroid backup" options. I've never tried it, but it sounds like a potential solution in your case.

 

[lucfig]

The donate version of Titanium has "extract from ADB backup" and "extract from Nandroid backup" options. I've never tried it, but it sounds like a potential solution in your case.

You are right. Did not remember that. I already used, had a couple of issues, but in general it worked

Enviado de meu HD1903 usando o Tapatalk

 

[perrypay]

nice info

thanks. it works.

 

[Curt5654]

You should've stopped at " 'adb' is not..."



You need to first install ADB, the installer can be found via Google.
Once installed (Press 'Y' > 'ENTER' for each option during install, this should install it to the default location, i.e. "C:").
Run "cmd" and enter the command "dir" . . . you should see "adb" as the first or second <DIR> listed; if you do not, find where 'adb' is installed and navigate to its folder via the commands 'cd' and 'dir'. Once in the 'adb' dir...
Begin typing "adb shell" and you'll see something other than..