"device has either stopped responding or has been disconnected"

resarfekim

Senior Member
Jan 26, 2011
494
105
63
"device has either stopped responding or has been disconnected"
I get this error when copying files to my phone. To internal or external storage.
Happens even in TWRP recovery.
Tried different PC, cable, files.

Copying from the phone works perfectly.
What could this be?

I did drop my phone last night from 4' (has a decent cover). Hopefully it's not a hardware issue.

Running COK1 Project Unknown rom.

Thanks!
Mike
 

samep

Senior Member
Dec 8, 2011
2,545
2,258
0
I've noticed the stock kernel tends to want the display on and unlocked to exchange files through MTD. It may even get stubborn if attempted with screen off. Rooted stock with systemless SuperSU actually gives some adb access despite saying it cannot remount adb- access denied.

If you want more freedom of file exchange or adb, try a permissive kernel like Beastmode, AEL, Emotion or Plasma kernel. Not necessarily in that order... individual preferences, experience and results may vary. If you swap kernel to permissive, you should also switch SuperSU to 2.50 or less. IIRC, a recent suggestion was less than 2.50, like SuperSU 2.49 beta.

Sent from my SM-N910P using Tapatalk
 
Last edited:
  • Like
Reactions: resarfekim

resarfekim

Senior Member
Jan 26, 2011
494
105
63
Thanks. I believe I was on the latest AEL kernel.
I wiped everything (internal, system, format data.... the works!), then installed the new CMRemix Marshmallow. File copy problem is gone (and rom is running nice (after some initial jitters)).

So I wonder why my file copy problem occurred in TWRP. Does recovery use the rom's Kernel?
 

samep

Senior Member
Dec 8, 2011
2,545
2,258
0
Thanks. I believe I was on the latest AEL kernel.
I wiped everything (internal, system, format data.... the works!), then installed the new CMRemix Marshmallow. File copy problem is gone (and rom is running nice (after some initial jitters)).

So I wonder why my file copy problem occurred in TWRP. Does recovery use the rom's Kernel?
Yes, I believe that is still the case. Although I think the stock kernel now limits more than it was before Android 5.1.1

Still hope to see more @freeza kernels in the future.

Sent from my SM-N910P using Tapatalk