Database Users

[Q] Usb debugging without android (through recovery?)

Hi,
I kind of "bricked" my nexus. Kind of, because recovery is working, and I can even start the device in android. Problem is error windows pops up and I can't control a thing.
No big deal you say, but I deleted by accident the .zip of the rom I had on the device. AND USB DEBUGGING WAS OFF...
I can't transfer any file to the device, I can't start usb debugging, and every tutorial on the internet says to put the device in usb debugging -> it's bricked, that's the whole point, so WTF!
sorry, I didn't respect the unwritten rule stating you should'nt ask for help on a forum while angry furious
Hope any of you can help me...
I should add I'm really not a poweruser. I've been flashing roms for a long time following carefully the rules, but really I have no idea what I'm doing <insert meme>, so adb and stuff like that I've never used (directly).
Thanks!

Use fastboot, see the sticky that says flashing a factory image using fastboot/return to stock.
Sent from my Nexus 7(2012) that has zero issues.

Thanks for you answer.
Still, I have to turn on USB debugging
Enable usb debugging on your device (found under Settings > Developer Options)
Click to expand...
Click to collapse
I can't do that because I can't use my nexus in android.

Bipo said:
Still, I have to turn on USB debugging
I can't do that because I can't use my nexus in android.
Click to expand...
Click to collapse
USB debugging is system feature. If you cannot load system you don't need to bother about it. You can only use fastboot as writen before.

Bipo said:
Thanks for you answer.
Still, I have to turn on USB debugging
I can't do that because I can't use my nexus in android.
Click to expand...
Click to collapse
Incorrect.
Fastboot works even when there is nothing on the device save the bootloader. Follow the instructions in the flash factory thread linked above and don't apply and personal prejudices-- it does work, and is the "right" way to do things. If you use a Windows computer, then you may also need the naked fastboot drivers (which can also be found by searching).

[Q] How to sideload kernel with USB Debugging enabled?

Hi all,
I greatly need your help or some advice. I searched for more than 6h yesterday and Im surprised I couldnt find a solution to my problem.
Typical stuff : I broke the screen of my Nexus 4, that is completely stock 5.0.1. The phone is unrooted, bootloader is locked and obviously USB Debugging is disabled.
I need to backup some data from my phone : pictures, notes and if possible my contacts.
When I connect my phone via USB to my PC, I cant browse my files since my screen is locked. My screen is not responding at all, so no way I can unlock it. Only thing I can do is install new applications on my phone, but no way to launch them since I'd need to unlock my screen again.
I have installed adb and fastboot in order to try and use Android Screen Control, but I dont have USB Debugging enabled.
So I read that I could sideload a kernel that has USB Debugging enabled by default.
I got into Recovery Mode, and tried sideloading a zip file containing a Kernel found on the forum, but I always get an error saying the footer is wrong and the signature of the file didnt pass verification. I guess I can only sideload OTA updates ?
I tried fastbooting CWM recovery, that also didnt work.
adb devices command lists my 'recovery' device.
At this stage, all I need is to either be able to unlock my phone so I can access my files via USB (i tried few apps without success), or to enable USB debugging so I can connection using sideload, use Android Screen Control, reset the pattern lock, and backup my phone.
Also, USB OTG isnt enabled by default on Nexus 4, so that's another dead-end
So what are my options ? Where could I find a kernel that has USB Debug enabled, and how can I sideload it considering phone is not rooted, and bootloader is locked (unlocking it and whipping data defies the purpose).
THANK YOU for any advice!

There is nothing you can do with a locked bootloader and no custom recovery. Sorry man, but you're not going to be able to access your data.
Sent from my Nexus 9 using XDA Free mobile app

I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.

Joakim_Lind said:
I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.
Click to expand...
Click to collapse
All you need is a custom recovery to boot into to access your files. If you don't have one, download the latest version of twrp from here. http://techerrata.com/browse/twrp2/mako
Then flash that using fastboot. If you need help let us know.
Sent from my Nexus 5 using XDA Free mobile app

Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?

Joakim_Lind said:
Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?
Click to expand...
Click to collapse
You have an ancient version of twrp. Install the latest. I'm positive you don't need usb debugging enabled.
Sent from my Nexus 5 using XDA Free mobile app

Yes, you're so right! I also missed .img in the command
But what kernel would you recommend me to use so I have usb-debugging I can have usb-debugging enabled?

I am in almost completely the same situation! My N4 fell yesterday and shattered at the bottom right hand corner. No the touch screen doesn't work and there are sections of the screen that are black. However, I have...
root
cwm recovery
stock 5.0.1 kernel
windows 7
adb not working
fastboot working
usb debugging disabled
a need for usb debugging to become enabled.
I would like a kernel with usb debugging enabled and instructions on how to install it. Or if you have another fix, instructions on that.

Help with backing up N4 with cracked screen

My Nexus 4 LCD cracked upon impact today and the digitizer is damaged. I want to backup my phone before I repair the LCD, currently it is:
- Rooted
- USB Debugging is enabled from settings
- Device is set as "Camera" and not "MTP"
I want to use the tool http://forum.xda-developers.com/showthread.php?t=2786395
But I cannot tick the box for USB Debugging when using the tool, so I used the following in ADB in Recovery (TWRP)
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
Click to expand...
Click to collapse
However, the device doesn't show up. In device Manager (Control Panel) and while I'm in recovery I get "mako" with a yellow triangle
for which I cannot install any driver (I downloaded them through SDK).
I think it's a driver issue and I want to get sorted to have access to my phone, any ideas or experiences would be welcome!!
Thanks!

It's probably not showing up because camera is selected instead of MTP, but my question is why do you want to back it up.... just Repair Lcd and it should be just like it was before lcd broke....
Zmax

TecheTag said:
It's probably not showing up because camera is selected instead of MTP, but my question is why do you want to back it up.... just Repair Lcd and it should be just like it was before lcd broke....
Zmax
Click to expand...
Click to collapse
Good question, I suppose I worry that something might go wrong while disconnecting/reconnecting the mobo.

boeder9 said:
Good question, I suppose I worry that something might go wrong while disconnecting/reconnecting the mobo.
Click to expand...
Click to collapse
I have a business repairing phones.. nothing is going to happen when you disconnect the lcd and reconnect the new lcd... But if your phone has a frame I would Repair the whole frame and lcd together... Its much easier then just repairing the lcd alone
Zmax

TecheTag said:
I have a business repairing phones.. nothing is going to happen when you disconnect the lcd and reconnect the new lcd... But if your phone has a frame I would Repair the whole frame and lcd together... Its much easier then just repairing the lcd alone
Zmax
Click to expand...
Click to collapse
Well that's comforting, thank you! I'm trying to get the OEM part from LG, I found it in the market here in Saudi but it's not original, just a grade A quality LCD + frame.

boeder9 said:
Well that's comforting, thank you! I'm trying to get the OEM part from LG, I found it in the market here in Saudi but it's not original, just a grade A quality LCD + frame.
Click to expand...
Click to collapse
I use either Amazon or ebay mostly Amazon because they have prime which means you get shipping free and some items you get in 2 days so if you order it on a Friday it comes on Sunday... Its free for a month and then $99 after that or you can keep making a new email every month to beat the system
Zmax

Is there any other way to get to my files on the N4? or at least control the device with the cracked LCD?

boeder9 said:
Is there any other way to get to my files on the N4? or at least control the device with the cracked LCD?
Click to expand...
Click to collapse
Is your bootloader unlocked? If so flash twrp using fastboot. Then boot into twrp and you'll be able to copy and paste files from your device to your pc. If you can't see anything on your screen it might be a little hit and miss but it should be possible.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Is your bootloader unlocked? If so flash twrp using fastboot. Then boot into twrp and you'll be able to copy and paste files from your device to your pc. If you can't see anything on your screen it might be a little hit and miss but it should be possible.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yup bootloader is unlocked, I have twrp already but how do I choose the options in twrp? The screen doesn't respond! Also how do I copy files using twrp?

boeder9 said:
Yup bootloader is unlocked, I have twrp already but how do I choose the options in twrp? The screen doesn't respond! Also how do I copy files using twrp?
Click to expand...
Click to collapse
You don't need to choose any options (assuming you have one of the newer versions). All you have to do is boot into it. Boot into the bootloader, hit vol down twice and then power. Let it boot and plug your device into your usb cable. The device should show up on your pc.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You don't need to choose any options (assuming you have one of the newer versions). All you have to do is boot into it. Boot into the bootloader, hit vol down twice and then power. Let it boot and plug your device into your usb cable. The device should show up on your pc.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
That's the problem though, I had set it on Camera instead of MTP, so now I only get access to files like DCIM and NOT the rest of the files. Is there any way to circumvent this and have access to all the folders?

boeder9 said:
That's the problem though, I had set it on Camera instead of MTP, so now I only get access to files like DCIM and NOT the rest of the files. Is there any way to circumvent this and have access to all the folders?
Click to expand...
Click to collapse
Have you tried booting into twrp? Twrp defaults to mtp mode so I don't think it matters what you set the device to.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You don't need to choose any options (assuming you have one of the newer versions). All you have to do is boot into it. Boot into the bootloader, hit vol down twice and then power. Let it boot and plug your device into your usb cable. The device should show up on your pc.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I got into twrp, but again i had "mako" in the control panel device manager, so neither Camera nor MTP worked BUT then:
- I installed some drivers from the N4 Toolkit, namely the samsung drivers, and they worked. NOT MTP though, I am able to get into recovery and use ADB Pull commands but again for some files transfer is interrupted by "No such file or directory" that cancels the operation - so I need to somehow transfer directories/subdirectories individually..anyone can help out here?
- Other thing, though drivers are now installed correctly now, I still can't get to MTP and I think that might due to the fact that ive enabled USB Debugging. From my experience on N4 and N6 if I disable USB debugging I can use the device as MTP, if I enable it I cannot, I can only use Camera if it is enabled - so second question: can I disable USB Debugging through ADB somehow?
Thank u all!

boeder9 said:
I got into twrp, but again i had "mako" in the control panel device manager, so neither Camera nor MTP worked BUT then:
- I installed some drivers from the N4 Toolkit, namely the samsung drivers, and they worked. NOT MTP though, I am able to get into recovery and use ADB Pull commands but again for some files transfer is interrupted by "No such file or directory" that cancels the operation - so I need to somehow transfer directories/subdirectories individually..anyone can help out here?
- Other thing, though drivers are now installed correctly now, I still can't get to MTP and I think that might due to the fact that ive enabled USB Debugging. From my experience on N4 and N6 if I disable USB debugging I can use the device as MTP, if I enable it I cannot, I can only use Camera if it is enabled - so second question: can I disable USB Debugging through ADB somehow?
Thank u all!
Click to expand...
Click to collapse
Ok, I don't know the status of your device. I know with the latest twrp you can boot into it and access your device through mtp. Adb pull is a pita if you don't know the specific location and name of files. Here's what I'd do:
1. Google 15 second adb install xda. That'll install the usb drivers and fastboot with system variables set so you don't need to worry about the path to fastboot.exe.
2. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it twrp for simplicity.
3. Boot into your bootloader and open a command window in the same folder as twrp.img is in.
4. Run the command
fastboot boot twrp.img
5. You'll be booted into twrp and with your device connected to your pc you should see nexus4. From there it is as easy as copying and pasting files from your device to your pc.
When booted into recovery it makes no difference if you have usb debugging checked you not
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Ok, I don't know the status of your device. I know with the latest twrp you can boot into it and access your device through mtp. Adb pull is a pita if you don't know the specific location and name of files. Here's what I'd do:
1. Google 15 second adb install xda. That'll install the usb drivers and fastboot with system variables set so you don't need to worry about the path to fastboot.exe.
2. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it twrp for simplicity.
3. Boot into your bootloader and open a command window in the same folder as twrp.img is in.
4. Run the command
fastboot boot twrp.img
5. You'll be booted into twrp and with your device connected to your pc you should see nexus4. From there it is as easy as copying and pasting files from your device to your pc.
When booted into recovery it makes no difference if you have usb debugging checked you not
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Can't thank u enough bro..flashing the new version of twrp via fastboot wont affect any of my data right?
will try this tomorrow and report back.

boeder9 said:
Can't thank u enough bro..flashing the new version of twrp via fastboot wont affect any of my data right?
will try this tomorrow and report back.
Click to expand...
Click to collapse
No, it won't touch your data.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Ok, I don't know the status of your device. I know with the latest twrp you can boot into it and access your device through mtp. Adb pull is a pita if you don't know the specific location and name of files. Here's what I'd do:
1. Google 15 second adb install xda. That'll install the usb drivers and fastboot with system variables set so you don't need to worry about the path to fastboot.exe.
2. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it twrp for simplicity.
3. Boot into your bootloader and open a command window in the same folder as twrp.img is in.
4. Run the command
fastboot boot twrp.img
5. You'll be booted into twrp and with your device connected to your pc you should see nexus4. From there it is as easy as copying and pasting files from your device to your pc.
When booted into recovery it makes no difference if you have usb debugging checked you not
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
DUDE THIS WORKED!
One thing. The screen goes black, doesn't go to twrp but Nexus 4 shows up on my PC as MTP. Files are accessible. When I restart the device, TWRP is back to the old version I had.
Not important. Thanks a million buddy. God Speed!

boeder9 said:
DUDE THIS WORKED!
One thing. The screen goes black, doesn't go to twrp but Nexus 4 shows up on my PC as MTP. Files are accessible. When I restart the device, TWRP is back to the old version I had.
Not important. Thanks a million buddy. God Speed!
Click to expand...
Click to collapse
Glad you got it working. Twrp is your old twrp because I just had you boot into it. Not flash it. If you want to flash it, fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app

[Urgent help]Broke N4 Screen - Need to backup App Data - Rooted - Debugging Enabled

So as the title suggest, my screen is working but not recognizing touch. Basically useless.
Device is rooted, Usb debugging is enabled but RSA Key is not authorised to this pc.
Stock Lollipop with custom kernel.
Problem 1 -
I am already with CWM recovery. From what I have read from cwm recovery I must be able to get access to adb recovery mode so I can backup my app data from system but the device stills shows "Unauthorized" in recovery mode. I dont know why this is happening?
Problem 2 -
I bought the OTG USB Y Cable thinking I might be able to install a differnet kernel that support otg through external power source but then I read that most kernel require to manually enable the option in settings/tweaker app for OTG SUPPORT. I cannot do this becasue as i said my screen is not working.
Please help me out.

Does your computer recognize the phone in bootloader? If so I would suggest you flash twrp and then try booting to recovery. Then you can check if your computer recognizes it now.

theminikiller said:
Does your computer recognize the phone in bootloader? If so I would suggest you flash twrp and then try booting to recovery. Then you can check if your computer recognizes it now.
Click to expand...
Click to collapse
Yes.
Already did that and it did work.
Was able to backup few imp. data.
I just have one more question -
Is there some kernel which support otg in Lollipop without me manually going into settings/tweaker app for kernel and enabling it?
Because I cannot do it manually coz the screen is broken.

[Samsung Galaxy J5 2017 SM-530F/DS] Broken screen – a way to backup?

Screen in my J5 2017 broke and I cannot unlock it anymore so I tried to make a backup via PC. I blindly rooted my phone and installed TWRP, which went OK. Then I tried to use ADB with no avail – the device isn’t listed. I got all the drivers and everything and all what shows up in the device manager is "MTP device" so I assume that my phone is stuck in MTP mode and that’s why it is not recognised by ADB. Can anybody confirm it? Does MTP mode prevents from using ADB? Also, I don’t have USB debug mode enabled but after doing some research I found out that it won’t be necessary – I’d just need to boot into TWRP and use ADB. So the only thing keeping me from making a backup of my phone is that the device isn’t listed in ADB.

Infinitiv said:
Screen in my J5 2017 broke and I cannot unlock it anymore so I tried to make a backup via PC. I blindly rooted my phone and installed TWRP, which went OK. Then I tried to use ADB with no avail – the device isn’t listed. I got all the drivers and everything and all what shows up in the device manager is "MTP device" so I assume that my phone is stuck in MTP mode and that’s why it is not recognised by ADB. Can anybody confirm it? Does MTP mode prevents from using ADB? Also, I don’t have USB debug mode enabled but after doing some research I found out that it won’t be necessary – I’d just need to boot into TWRP and use ADB. So the only thing keeping me from making a backup of my phone is that the device isn’t listed in ADB.
Click to expand...
Click to collapse
You need to have USB debug unlocked to use ADB even in recovery

Haxomen said:
You need to have USB debug unlocked to use ADB even in recovery
Click to expand...
Click to collapse
This blog entry states otherwise (around paragraph 3). Is it model‐specific or is the blog author simply wrong?

Infinitiv said:
This blog entry states otherwise (around paragraph 3). Is it model‐specific or is the blog author simply wrong?
Click to expand...
Click to collapse
He does not say that your USB debug can be turned off. He does not even mention it

Haxomen said:
He does not say that your USB debug can be turned off. He does not even mention it
Click to expand...
Click to collapse
Yes he is. The whole point of this blog entry is that he didn’t have USB debug enabled and he worked around it to make his backup. He describes how he felt hopeless when he found out that USG debugging is disabled (see the third picture in the blog entry) and that he had to manually turn the phone:
We can't use the screen, (or an adb reboot recovery command - USB debugging is not enabled) so we'll have to pop the battery out to turn the device off.
Click to expand...
Click to collapse
So, yeah… It seems that he did everything without USB debbuging enabled. So my question still stand – is he wrong or is it model‐specific? Or maybe I’ve done something wrong?

Infinitiv said:
Yes he is. The whole point of this blog entry is that he didn’t have USB debug enabled and he worked around it to make his backup. He describes how he felt hopeless when he found out that USG debugging is disabled (see the third picture in the blog entry) and that he had to manually turn the phone:
So, yeah… It seems that he did everything without USB debbuging enabled. So my question still stand – is he wrong or is it model‐specific? Or maybe I’ve done something wrong?
Click to expand...
Click to collapse
If he managed to do it, try it yourself, maybe you will be able.

Haxomen said:
If he managed to do it, try it yourself, maybe you will be able.
Click to expand...
Click to collapse
As I stated in the first post of this thread I tried it with no avail and now I’m looking for some help from people with serious knowledge on the topic.

Infinitiv said:
As I stated in the first post of this thread I tried it with no avail and now I’m looking for some help from people with serious knowledge on the topic.
Click to expand...
Click to collapse
I tried to use adb on my J5 2016 within TWRP 3.1.1 recovery, while USB debug was off, and it worked. But it did not work on a previous, unstable TWRP version. So it is probably due to your recovery, not your phone. What TWRP are you using?

I’ve used TWRP 3.1.1 from this thread: https://forum.xda-developers.com/ga...pment/twrp-twrp-recovery-j5-pro-2017-t3668266
The thing is that my device don’t get listed in ADB no matter whichever mode it’s in – download, recovery nor "normal". And I’ve checked on several PCs.
Windows recognises my phone as unknown MTP device, so I assume that my phone has MTP mode enabled and I’m stuck with it. That shouldn’t be the case since I tried to plug it in while it’s in recovery mode, but maybe you’ll find this information useful.

Haxomen said:
What TWRP are you using?
Click to expand...
Click to collapse
I assume that since I didn’t quote you in my previous post you didn’t get any notification – fixed it now. I’ve answered your question in the post above. Any thoughts?