• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[TREBLE][ROM][LINEAGE] Project Treble for Cedric

Search This thread

ap4ss3rby

Senior Member
Sep 9, 2015
138
28
Known issue of Moto G5 only or every phone has this problem because of some bug in ROM?

On the thread of the Android P GSI most people complaining are OnePlus 5t users, who are advised to use the MoKee ROM Vendor partition and go through slightly altered steps to get it working. On our phone on the other hand, we seem to have some issue because our /Vendor partition and bootloader seem to not like the Android P ROM. I wonder if an update to the ROM or /vendor partition fix this problem. Hope that an updated ROM will fix this issue.
 
  • Like
Reactions: crissband

mrfrantastic

Senior Member
Sep 23, 2013
293
89
I can't seem to get gapps working. Any hints? Tried booting into OS first, then flashing gapps, flashing gapps straight after GSI, also tried factory reset after flashing gapps but always end up with force closed play services. I have the xt1676. Thanks
 

James160103

Senior Member
Sep 9, 2017
172
75
London
I can't seem to get gapps working. Any hints? Tried booting into OS first, then flashing gapps, flashing gapps straight after GSI, also tried factory reset after flashing gapps but always end up with force closed play services. I have the xt1676. Thanks

Install the ROM, boot into OS, install Gapps, boot into OS again and then install the latest version of the Google Play Services from APK Mirror. Be sure to pick the correct version (Android 8.0+, ARM64, nodpi).
 
D

Deleted member 7782889

Guest
What is the recovery password? (excuse my English I'm using Google Translate)
 

TheFixItMan

Senior Member
Jul 8, 2012
7,833
4,027
London
What is the recovery password? (excuse my English I'm using Google Translate)

There isn't one - I presume you were encrypted in your previous rom and it would be your de-crypt password

However you need to remove encryption before flashing rom so ignore password request - goto wipe and select format data (option on right)
Restart back to recovery and encryption should be removed allowing you to mount data

Encryption works fine on my official 32bit twrp but unless who ever compiled the treble twrp version used my source code as a base and not the 64bit twrp or incorporated the decrypt commits from my source into their source then you will not be able to decrypt data in twrp
 
Last edited:
D

Deleted member 7782889

Guest
There isn't one - I presume you were encrypted in your previous rom and it would be your de-crypt password

However you need to remove encryption before flashing rom so ignore password request - goto wipe and select format data (option on right)
Restart back to recovery and encryption should be removed allowing you to mount data

Encryption works fine on my official 32bit twrp but unless who ever compiled the treble twrp version used my source code as a base and not the 64bit twrp or incorporated the decrypt commits from my source into their source then you will not be able to decrypt data in twrp
Thanks man
 

KalilDev

Senior Member
Sep 16, 2016
121
262
Belo Horizonte
Install the ROM, boot into OS, install Gapps, boot into OS again and then install the latest version of the Google Play Services from APK Mirror. Be sure to pick the correct version (Android 8.0+, ARM64, nodpi).

No......... You should NEVER install gapps afater booting.......... This is what causes the issue the dude is having... Flash rom, Flash magisk, Flash gapps, boot. thats it. i dont have any idea on where you guys saw that you need to boot before flashing gapps.
If you are flashing a GSI, chances are the system partition isnt the full size, and then, AND ONLY THEN, you need to flash rom, boot (This resizes the partition), go to twrp, wipe data,cache and dalvik, then flash gapps and magisk and then you are ready to use the rom.
 

KalilDev

Senior Member
Sep 16, 2016
121
262
Belo Horizonte
On the thread of the Android P GSI most people complaining are OnePlus 5t users, who are advised to use the MoKee ROM Vendor partition and go through slightly altered steps to get it working. On our phone on the other hand, we seem to have some issue because our /Vendor partition and bootloader seem to not like the Android P ROM. I wonder if an update to the ROM or /vendor partition fix this problem. Hope that an updated ROM will fix this issue.

DP5 and DP4 made some changes to the surfaceflinger. our adreno isnt starting right on it. im gonna try some things to see what i can do.
In the other hand, DP3 works 100% fine. Im gonna make a thread on how to install it
 
  • Like
Reactions: HeyImVitor

James160103

Senior Member
Sep 9, 2017
172
75
London
No......... You should NEVER install gapps afater booting.......... This is what causes the issue the dude is having... Flash rom, Flash magisk, Flash gapps, boot. thats it. i dont have any idea on where you guys saw that you need to boot before flashing gapps.
If you are flashing a GSI, chances are the system partition isnt the full size, and then, AND ONLY THEN, you need to flash rom, boot (This resizes the partition), go to twrp, wipe data,cache and dalvik, then flash gapps and magisk and then you are ready to use the rom.

Well yeah, I was writing about GSIs. The ROM won't boot when Gapps are installed straight after the ROM, you have to boot into it first and then flash Gapps. Just like you've written. I had that problem with a few other ROMs I once had installed on my device. I know you're aren't supposed to do that when flashing non-treble ROMs as it can cause problems. However, if the ROM doesn't boot that's the only option you've got, right? It does result in the Play Services crashing but that can be easily fixed as I wrote in my last post. Thanks anyway for mentioning the part about wiping data, cache and dalvik before flashing Gapps. I wonder if that also stops the Play Services from crashing.
 

KalilDev

Senior Member
Sep 16, 2016
121
262
Belo Horizonte
Well yeah, I was writing about GSIs. The ROM won't boot when Gapps are installed straight after the ROM, you have to boot into it first and then flash Gapps. Just like you've written. I had that problem with a few other ROMs I once had installed on my device. I know you're aren't supposed to do that when flashing non-treble ROMs as it can cause problems. However, if the ROM doesn't boot that's the only option you've got, right? It does result in the Play Services crashing but that can be easily fixed as I wrote in my last post. Thanks anyway for mentioning the part about wiping data, cache and dalvik before flashing Gapps. I wonder if that also stops the Play Services from crashing.

wiping it is what fixes the issue
 
  • Like
Reactions: James160103

durc12

Senior Member
Apr 2, 2012
64
10
Good night.
First of all, thanks for all developers to make it possible to have treble support in this device.
The idea I had is, that now that we have the stock oreo, is it possible to use camera2api or the drivers of motorola for camera to treble or lineage custom oreo roms (like dotOS, which currently I am).
I think we could make with this perfect roms for cedric.
Thanks for all, I wait for your reply and if you could make a flashable zip with the drivers for the oreo roms, you'll be insane good!!
 
  • Like
Reactions: HeyImVitor

fix4all

Member
Apr 23, 2012
15
0
Treble or not?

So, what are the most functional compatible Oreo GSI's for Cedric where mostly all phone features working? Searching some various GSI threads still appears many issues on hand. Wondering if it's worth exploring Treble and GSI's at this point or stick to my current daily driver VipeOS Oreo ROM that is very stable/functional.
 

lolemenos

Senior Member
So, what are the most functional compatible Oreo GSI's for Cedric where mostly all phone features working? Searching some various GSI threads still appears many issues on hand. Wondering if it's worth exploring Treble and GSI's at this point or stick to my current daily driver VipeOS Oreo ROM that is very stable/functional.
I am wondering exactly the same. Most people say that Pie GSIs don't work.
I don't get why since we have a treble compatible device we don't have our developers focus on that. If we have a good treble foundation then we can install anything each and every user wants...
 
  • Like
Reactions: [email protected]

AndroidenKalle

Senior Member
Apr 30, 2013
69
26
I am wondering exactly the same. Most people say that Pie GSIs don't work.
I don't get why since we have a treble compatible device we don't have our developers focus on that. If we have a good treble foundation then we can install anything each and every user wants...


It's better to ask how can I help (see OP) instead of bitching.

https://github.com/erfanoabdi/P_semiGSI/wiki

https://forum.xda-developers.com/g5/development/treble-how-to-install-android-p-sgsi-t3823969
 

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    Code:
    /* Your warranty is now void.
     *
     * We're not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this TREBLE
     * SUPPORT before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at us for messing up your device, we will laugh at you.
     *
     */
    Install Instruction:
    1. Flash this TWRP with treble support (thx to @CodeZero)
    2. Format /system, /data and /cache
    3. Install this Lineage treble build from Google Drive or from Transfer.sh
    4. Install any GSI system image using TWRP (Install image -> choose your system.img -> select system partition)
    5. Reboot

    Known issues:

    VoLTE is disabled
    Camera is buggy
    You tell me


    How to report bugs:
    REGISTER IT ON GITHUB WITH LOGS, OTHERWISE IT WILL BE IGNORED AND CLOSED.
    The GitHub for registering the issues is This
    Steps to do it:
    1. Check if it was already posted (duplicates will be closed)
    2. Logs should be attached (posted on gist, otherwise the issue will be closed)
    3. The title format should be: LineageTrebleBuildDate: ROMYouAreUsing: issue you are having
    4. The description should be the full log on gist (https://gist.github.com), and steps to reproduce the issue.
    5. Each issue should be posted individually
    6. DONT TAG ME HERE, OR ON TELEGRAM. I use github bot which sends me notifications when someone posts or replies to an issue
    7. IF YOU DIRTYFLASHED, MENTION IT


    Requirements for taking logs:
    1. A PC with adb and the drivers installed
    2. A phone
    How to take logs:
    1. Connect your phone to the PC
    2. Enable Android debug bridge on the developer settings
    3. Run $
      Code:
      adb devices
      on your PC shell, and if it shows your device proceed, otherwise tag an admin to help you
    4. Run $
      Code:
      adb reboot
      this will reboot your phone
    5. While it's still on the Motorola logo, run $
      Code:
      adb logcat > log
    6. Once the device boots, replicate the issue
    7. After the issue is replicated, press the CTRL and C keys simultaneously
    8. Once this is done the file log will appear in the folder you ran adb.
    9. This file contains the log.

    Where can i find GSI's ?

    https://forum.xda-developers.com/project-treble/trebleenabled-device-development
    https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list

    Wiki/FAQ
    Thanks @vache for the xda thread and contributions for treble on potter
    7
    People shouldn't be using treble roms (in their current state of stability) as daily drivers for cedric anyway, if you want voLTE just use regular roms built specifically for the device.

    they are my DD. android p even lmao. i jusut need to fix the moto actions, the cam and both P and treble roms are 100%
    4
    Take your time we are in no rush. Plus just ignore people talking about volte. We need to have a fully stable working treble foundation! Volte shouldn't be a top priority

    Sent from my Moto G (5) using Tapatalk
    4
    I need to fix Moto actions. Because of my testers not reporting stuff to me the public build has broken Moto actions