Skip to content

typo in readme #1

Description

@drbeat

hi,

the credric is moto g5 and athene is moto g4 :)
you accidently wrote g6 and g5

regards

Activity

  1. roeeh commented on Jun 9, 2017

    @roeeh
    Contributor

    Good catch!:)
    Will be fixed next week as I am currently travelling.

    Thanks

  2. drbeat commented on Jun 10, 2017

    @drbeat
    Author

    Another thing:
    I have a Moto G5 Plus and followed your blog post.
    With 'fastboot oem config fsg-id "a androidboot.foo=bar"' I managed to create the property.

    I did not follow further as I need the phone for business & private but I guess everything else should be straight forward.

  3. roeeh commented on Jun 11, 2017

    @roeeh
    Contributor

    Good to hear :) I will soon make a list of all models that people have reported to be vulnerable

  4. added a commit that references this issue on Jun 12, 2017
  5. wyjxiaoduo commented on Aug 4, 2017

    @wyjxiaoduo

    I have a G5 Plus, with 'fastboot oem config fsg-id "a androidboot.foo=bar"' I managed to create the property, but unexpectedly , after

    fastboot oem config fsg-id "a initrd=0xA2100000,1601123"
    fastboot flash foo ramdisk.cpio.gz
    fastboot continue

    the devices ran into infinite boot loops...

  6. drbeat commented on Aug 4, 2017

    @drbeat
    Author

    which ramdisk did you use?

  7. wyjxiaoduo commented on Aug 4, 2017

    @wyjxiaoduo

    I got it from boot.img in POTTER_AMZ_NPN25.137-35_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

  8. wyjxiaoduo commented on Aug 5, 2017

    @wyjxiaoduo

    Had anyone else tested moto g5 plus?

  9. drbeat commented on Aug 6, 2017

    @drbeat
    Author

    I heard the hole was fixed in the latest version. I did not try as I need the phone for business purposes.
    But if you are able to run the command
    fastboot oem config fsg-id "a androidboot.foo=bar

    and get the desired output you should be able to run root if you have a modified initram.
    you may use a different padding than in the readme as it was not tested

  10. Hitechcomputergeek commented on Apr 10, 2018

    @Hitechcomputergeek

    EDIT: moved to new issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions