23
[Discuss] Custom ROMs for the 7 and 7T-series

  1. devourerOfBits80
    Honeycomb May 26, 2021

    devourerOfBits80 , May 26, 2021 :
    How to setup ADB for OnePlus devices

    Phone configuration:
    1. Launch the Settings application on your device.
    2. Tap the About Phone item at the bottom of the list.
    3. Tap the Build Number item 7 times in a row. You will see an appropriate toast message and Developer Mode will be enabled.
    4. Go back to the main Settings and tap the System item.
    5. Tap the Developer Options, go there and enable the USB Debugging mode option. You will see a popup where you need to confirm your selection by clicking the OK button.
    6. Connect your device to your PC with a USB cable.
    Bridge configuration:
    1. Open up the Command Prompt/console window and launch the ADB daemon with command: adb devices. Keep in mind that on Windows, you'll need to execute this command directly from the Platform Tools folder.
    2. A popup should appear on your device's screen to allow or deny USB Debugging access. Tap the Allow always from this computer checkbox (if you never want to see this popup again) and finally tap the OK button.
    3. Now the connection should be established and you should be able to see your device's serial number in the Command Prompt/console window. If not, please re-enter the adb devices command again.
    4. You can run now any ADB and Fastboot command on your device. Have a fun.
    Popular ADB commands:
    • adb shell - launches a shell on the device;
    • adb push <local_path> <remote_path> - pushes the file from your PC to your device (note that device's internal storage has the following path: /storage/emulated/0/);
    • adb pull <remote_path> [<local_path>] - pulls the file from your device to your PC (if local path isn't specified, it will pull to the current folder);
    • adb install <path_to_file.apk> - installs the given .apk file to your device;
    • adb logcat - prints device logs in real time into the console window (use adb logcat -b radio to view radio logs).
     

    #41
  2. devourerOfBits80
    Honeycomb May 30, 2021

    devourerOfBits80 , May 30, 2021 :
    How to install the PixelExperience custom ROM

    The PixelExperience ROM is well documented on the website, so rewriting the contents doesn't make sense. In that case I'm going to give you only a few tips and organize the knowledge into points.

    Documentation for OnePlus 7T: https://wiki.pixelexperience.org/devices/hotdogb/
    Documentation for OnePlus 7T Pro: https://wiki.pixelexperience.org/devices/hotdog/

    What do you need do to install the PixelExperience ROM? It's quite easy. Go ahead these steps:
    1. Install the latest version of OxygenOS to have the latest vendor firmware version.
    2. Backup your data as any further steps will make them lost. It isn't an OTA update, so your device will be reset to the factory settings!
    3. Download the PixelExperience ROM installation package (build) file and the recovery image file. 7T: https://download.pixelexperience.org/hotdogb and 7TPro: https://download.pixelexperience.org/hotdog
    4. Make sure that you've installed the ADB (post 40) and you can debug your device (post 41).
    5. Unlock the bootloader. 7T: https://wiki.pixelexperience.org/devices/hotdogb/install/#unlocking-the-bootloader and 7TPro: https://wiki.pixelexperience.org/devices/hotdog/install/#unlocking-the-bootloader Please note that you will need to confirm the unlocking demand on your device. Use the Volume and Power buttons to select and confirm the appropriate option.
    6. Flash a custom recovery image on your device. 7T: https://wiki.pixelexperience.org/de...rily-booting-a-custom-recovery-using-fastboot and 7TPro: https://wiki.pixelexperience.org/devices/hotdog/install/#booting-a-custom-recovery-using-fastboot Use downloaded recovery image file [*.img] from the step three [3].
    7. Make the sets of partitions (slots) have the same firmware version to avoid various issues including a potential hard-brick. Copy the contents of slot a to slot b. 7T: https://wiki.pixelexperience.org/devices/hotdogb/install/#pre-install-instructions and 7TPro: https://wiki.pixelexperience.org/devices/hotdog/install/#pre-install-instructions
    8. Install the PixelExperience custom ROM. Use downloaded installation package file [*.zip] from the step three [3]. 7T: https://wiki.pixelexperience.org/devices/hotdogb/install/#installing-pixelexperience-from-recovery and 7TPro: https://wiki.pixelexperience.org/devices/hotdog/install/#installing-pixelexperience-from-recovery
    9. Lock back the bootloader. 7T: https://wiki.pixelexperience.org/devices/hotdogb/install/#post-install-instructions and 7TPro: https://wiki.pixelexperience.org/devices/hotdog/install/#post-install-instructions Please note that you will need to confirm locking demand on your device.
    10. Turn on the device, select your language and finish the configuration. You're using the PixelExperience ROM just now! Revert the backup data and "make yourself at home".
     
    Last edited: May 30, 2021

    #42
    ghostofcain, ainy and Praveen723 like this.
  3. morphvale
    Froyo May 30, 2021

    morphvale , May 30, 2021 :
    You've missed flashing of avb_custom_key for bootloader lock before step 9.
     

    #43
  4. devourerOfBits80
    Honeycomb May 30, 2021

    devourerOfBits80 , May 30, 2021 :
    I was including it in point 9, because it's related to the bootloader locking but thank you for your vigilance. :)
     

    #44
  5. GamingDoggo_
    Jelly Bean Jun 1, 2021


    #45
    MRTLima and devourerOfBits80 like this.
  6. pablofg1978
    Head Moderator Head Moderator Jun 1, 2021


    #46
  7. ghostofcain
    Marshmallow Jun 8, 2021

    ghostofcain , Jun 8, 2021 :
    **Warning stupidly long post***

    Ok so I was bored and thought I'd give it a go, so last Thursday I flashed Pixel Experience and have been using it since.

    Installation, following the instructions on the Pixel Experience website, which mirror those of @devourerOfBits80 above, was straightforward and without drama.

    First run, again no drama, I reinstalled all my apps via Google and only restored data on a couple using third party tools, everything worked reasonably out of the box.

    I wanted to install gCam, which I did using Wichaya-abdul-v2-7, and wanted to remove the lineage default app, so investigated the installed apps via ADB, wherein I encountered my first surprise. The ROM is supplied with several uneccessary Verizon and Sprint apps preinstalled which for a stripped back custom ROM was unexpected to say the least, obviously a quick cleanup with pm uninstall sorted that.

    So after my fettling I settled back and used it for nearly a week and now can provide some feedback.

    The Good....
    1. Everything seems to function, relatively error free.
    2. The device actually goes into deep sleep now, which should improve battery life
    3. Phone is relatively smooth with few obvious hangs.
    4. Patched and up to date with newish security patch
    5. Should get more regular updates.

    The Bad .....
    1. Battery life isn't what I expected, over the week I've used it accubattery is predicting a SOT over just over 8 hours as opposed to 8.5 hours on OOS11, standby life would appear to be marginally down 49 hours against 55, and mixed use down a little. In practice I find on OOS11 I plug my device in at around 11pm at about 25% unplugged at 7am. With PE I'm looking at less than 15% over the same time frame.(pictures added for comparison)
    2. Widevine has been downgraded to L1, I've tried all the normal fixes without success, but to be honest it's not a massive problem as I can't see the benefit watching HD content on a phone screen.
    3. BT, I find it often takes me 2-3 attempts to get a stable connection with my Alexa devices, whereas the connection was effortless with OOS11.
    The Ugly...
    1. Stability, I'm seeing random hangs on trying to wake the device every couple of days, and on two occasions have had to force a reboot to get it to respond.
    2. Adaptive brightness, it's really as awful as people say, taking minutes to adjust to changes in environment and then sometimes taking several minutes to stabilise. In one incident I actually had to force a reboot to be able to get the screen to reset to a useable brightness.
    It might surprise you, if you've made it this far, to hear that inspite of the quibbles I'm sticking with PE for now. The fact that it'll get updated regularly and I get a pixel experience without the awful hardware has won me over, at least until I get bored again.
     

    Attached Files:

    Last edited: Jun 8, 2021

    #47
    GamingDoggo likes this.
  8. morphvale
    Froyo Jun 8, 2021

    morphvale , Jun 8, 2021 :
    You have to manually adjust the brightness, rather than waiting for it to react on its own, so that it learns your preferences. Preferably, you should reset the adaptive brightness in device health services. For me, the first day was bad, usually in low light, now I'd say it's pretty much on par with OOS.
    Battery varies a bit, depending usually on how much I reddit but for me is a lot better than OOS. I've had as low as 0,4% in idlle per charge, havent seen this since lollipop days, and it's usually 10-11% for SOT.
    For Widevine there's a process to get L1, it involves Magisk, but must be done only once.
     

    Attached Files:


    #48