354
OxygenOS Open Beta 1 (Android O) for the OnePlus 5T

Thread Status:
Not open for further replies.
  1. marinobiagio Jelly Bean Jan 3, 2018


  2. carburano Jelly Bean Jan 3, 2018

    carburano, Jan 3, 2018 :
    me too. it never behaves as I selected in settings
     

    AnixOpz likes this.
  3. Rizla Jelly Bean Jan 3, 2018

    Rizla, Jan 3, 2018 :
    You'll need to side load it.
     

  4. cmpllnt Cupcake Jan 3, 2018

    cmpllnt, Jan 3, 2018 :
    Can I flash the januar build over the Dezember build without wie the phone?
     

  5. Rizla Jelly Bean Jan 3, 2018

    Rizla, Jan 3, 2018 :
    Yes
     

    cmpllnt likes this.
  6. aditya1702 Cupcake Jan 3, 2018


  7. Rizla Jelly Bean Jan 3, 2018

    Rizla, Jan 3, 2018 :
    This thread is for Oreo beta but I'll help anyway. Get oxygen updater from the play store that will get you 4.7.6.
     

  8. SP3NGL3R Froyo Jan 3, 2018

    SP3NGL3R, Jan 3, 2018 :
    Thanks. I've tried everything. Well, not a ZIP sideload, but and flash recovery TWRP.img
    with both stock TWRP and Blu_Spark TWRP

    I'm stuck at step 6. Upon Boot to Beta 1 Oreo > Reboot to Bootloader > Flash TWRP via Fastboot > Reboot into TWRP
     

  9. Rizla Jelly Bean Jan 3, 2018


  10. unmaskedfalesh Ice Cream Sandwich Jan 3, 2018

    unmaskedfalesh, Jan 3, 2018 :
    Goto flastboot mode and flash stock recovery(oneplus stock recovery).
    Reboot to stock recovery
    flash oreo beta finish initial setup
    goto fastboot flash twrp
    it should do the job
     

  11. SP3NGL3R Froyo Jan 3, 2018


    Rizla likes this.
  12. dnyaneshwar Patekar Froyo Jan 3, 2018

    dnyaneshwar Patekar, Jan 3, 2018 :
    Can I Flash New Beta 1 over earlier December Beta ?
    I am using December Beta since launch with no issues at all.
    only thing is google Camera doesn't work .
    So hopefully that is fixed in this .
     

  13. Rizla Jelly Bean Jan 3, 2018

    Rizla, Jan 3, 2018 :
    Sorry man my bad I thought you were stuck at the basics. Have you definitely got the correct blu spark twrp? Don't reboot once you flash the twrp, go straight back into recovery.

    Yes
     

  14. Polv89 Cupcake Jan 3, 2018

    Polv89, Jan 3, 2018 :
    I followed instructions, when i reboot after flash ob1 and magisk 15 and i try to boot up system, it boot blu recovery ever, why?
     

  15. G_Neit_J._Nieves-Flores_ Eclair Jan 3, 2018

    G_Neit_J._Nieves-Flores_, Jan 3, 2018 :
    so I installed google clock from play store and wiped cache on recovery.

    now the oneplus clock widget is working fine. i didn't do anything with google clock but maybe it had something to do with op's widget working idk
     

  16. polisettysd Honeycomb Jan 3, 2018

    polisettysd, Jan 3, 2018 :
    Hello friends... Happy New Year to all & I wish that 2018 will be the year to be cherished for a life time for all.

    I have activated the developer mode options... Any new features which can be enabled from within the developer level?
     

  17. Rizla Jelly Bean Jan 3, 2018

    Rizla, Jan 3, 2018 :
    Happy new year to yourself. I wouldn't be enabling anything in developer mode unless you know what you're doing. There's nothing really in there for the normal user accept advanced reboot and of course if you're wanting to unlock the bootloader and root.
     

  18. SP3NGL3R Froyo Jan 3, 2018

    SP3NGL3R, Jan 3, 2018 :
    AHHHH!!!!!! SO:
    1. from Beta1 after full factory reset. got DEV options and everything setup for ADB/FastBoot
    2. adb reboot bootloader
    3. fastboot flash recovery twrp.img
    4. ******** HERE'S WHAT IS DIFFERENT *******
    --- use the volume keys from within fastboot to reboot into recovery. BOOM!!!! BluSpark TWRP is launched.

    Thanks. Rizla. That was it.
     

    Rizla likes this.
  19. Rizla Jelly Bean Jan 3, 2018

    Rizla, Jan 3, 2018 :
    Glad you got it sorted. It is an easy step to miss as we usually all just reboot the phone once we flash our recovery.
     

  20. unmaskedfalesh Ice Cream Sandwich Jan 3, 2018

    unmaskedfalesh, Jan 3, 2018 :
    Nice you sorted it out
    but
    you could have used:
    fastboot boot recovery twrp.img
    from fastboot to boot into recovery.