Skip to content
This repository has been archived by the owner. It is now read-only.

Problems with ADB in Android 6.0.X #341

Closed
vay3t opened this issue Jan 13, 2016 · 9 comments
Closed

Problems with ADB in Android 6.0.X #341

vay3t opened this issue Jan 13, 2016 · 9 comments

Comments

@vay3t
Copy link

@vay3t vay3t commented Jan 13, 2016

I'm having problems with the debug mode. I have no RSA key in Nexus 5 and Nexus 7 (2013) wifi. on any operating system

kernel version n5: 3.4.0-gb7558f2 root(a)kali #2 android 6.0.1 MMB29S
kernel version n7: 3.4.0-g61f11d0-dirty root(a)kali #6 android 6.0.1 MMB290

@jmingov

This comment has been minimized.

Copy link
Collaborator

@jmingov jmingov commented Jan 13, 2016

Hey @vay3t,

For some reason, (still unknown), when flashing the kernel/rooting/twrp the ADB is gone (only happening in 6.0.X android version)

This is confirmed (we also suffer it), but by now, you can:

OR

  • Reinstall stock, add adb keys for the pc you will be using, then once they are added, root, TWRP and then install nethunter.

We are still not sure if is a problem with android 6, with nethunter kernel, or the mix of both.

Jaime

@jmingov jmingov changed the title Problems with ADB in nexus 5/7 Problems with ADB in Android 6.0.X Jan 13, 2016
@vay3t

This comment has been minimized.

Copy link
Author

@vay3t vay3t commented Jan 13, 2016

i have a temporal solution, it's not necessary the adb for doing the stock reset, we made an alternative solution to the RSA problem with your script, My friend @acidobinario and I modify the script so that the verification skips adb and the user have to be in fastboot mode. if you can, you can name the script "DesesperatedStockRestaurationNexusMM.sh", only it has been tested on Nexus 7.

https://github.com/acidobinario/nethunter-LRT/commit/1bca4faf1a2ac0791a16c23e1c7a523a06433b5e (sorry for the sense of humor of my argentinean friend)

edit: I realized that the problem is marshmallow. I installed a factory image and have the same problem

@binkybear

This comment has been minimized.

Copy link
Collaborator

@binkybear binkybear commented Jan 13, 2016

@vay3t - I can confirm the problem exists/existed on Marshmallow in our early testing. It's a bit silly, but for me switching cables seemed to fix the issue and also revoking authorizations.

@H8to

This comment has been minimized.

Copy link

@H8to H8to commented Jan 28, 2016

@vay3t Thanks for reporting this issue.

@ALL Any news on a workaround for Marshmallow that one can apply via terminal?
Reflashing everything is not an option. :/

Edit:
Ok, found a workaround ;)

  1. Get a second android device and connect it to your computer.
  2. Authorize it.
  3. On the Android device cp /data/misc/adb/adb_keys /sdcard/
  4. Copy the file to your computer via adb or mtp.
  5. Copy this file to your Marshmallow device
  6. On the Marshmallow terminal: cp /sdcard/adb_keys /data/misc/adb/adb_keys

This way you don't have to wait for a bugfix or reflash stock and so on.

@vay3t

This comment has been minimized.

Copy link
Author

@vay3t vay3t commented Aug 14, 2016

is possible in the installation of nethunter.zip (when it is TWRP), the installer generate a adb for android 6?

@Jinovas

This comment has been minimized.

Copy link

@Jinovas Jinovas commented Jan 3, 2017

@H8to worked like a charm for one of my nexus devices! Copied over nexus 7's adbkey to my second nexus 5 and it got it out of that damn aunuthorized state in adb.

My first nexus 5 seemed to have fixed itself and the RSA fingerprint prompt finally came up after several hours of being off. Ok, now lets try this again....

@jcadduono

This comment has been minimized.

Copy link
Collaborator

@jcadduono jcadduono commented Jan 4, 2017

I think this might be due to some devices interaction with ro.secure prop, if built in release mode and you switch that to off it has some unintended consequences probably because ro.secure=0 on a release build isn't something aosp/Google devs are testing.
It might be a good idea to also remove that change from the installer? @binkybear
I added ro.secure=1 to axon 7 kernel installer to fix USB issues as well.

@binkybear

This comment has been minimized.

Copy link
Collaborator

@binkybear binkybear commented Jan 4, 2017

Yes I belive that:

ro.secure=1

will fix issue.
I previously only changed adb.secure: cc96a68 but I think ro.secure should probably also be changed.

binkybear added a commit that referenced this issue Jan 4, 2017
@dimpol

This comment has been minimized.

Copy link

@dimpol dimpol commented Jan 25, 2017

Can we perform H8to's workaround with genymotion (can we somehow authorize the emulator and copy the keys to Nexus 6) ? I don't have a spare Android device...

@jmingov jmingov mentioned this issue May 23, 2017
Closed
@Re4son Re4son closed this Feb 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants
You can’t perform that action at this time.