[AOSP 10.0] [2019-12-06] Quack Phh-Treble

[jwarrior319]

I followed your suggestion but still stuck at android logo.
Logs attached.
Thanks.

The reoccurring problem here is:
" CANNOT LINK EXECUTABLE "/vendor/bin/ipsec_mon": library "liblogwrap.so" not found "
and
" Abort message: 'couldn't find an OpenGL ES implementation, make sure you set ro.hardware.egl or ro.board.platform' "

It looks like the problem is the vendor partition. What stock Android version did you come from? Did you install latest stock update available?

Sent from my SM-G975U1 using XDA Labs

 

[uncleabubear]

The reoccurring problem here is:
" CANNOT LINK EXECUTABLE "/vendor/bin/ipsec_mon": library "liblogwrap.so" not found "
and
" Abort message: 'couldn't find an OpenGL ES implementation, make sure you set ro.hardware.egl or ro.board.platform' "

It looks like the problem is the vendor partition. What stock Android version did you come from? Did you install latest stock update available?

Sent from my SM-G975U1 using XDA Labs

It's a Chuwi Hi9 Air with OEM Android 8.0.0. Arm64 A-only system partition.
Please see image attached.
Thanks.

 

[hojnikb]

So i have a MT6580 devices with shipped android 8.1 go.
Treble Info says VNDK version 27.0, no system-as-root and is ARM32
Can i flash "system-quack-arm-aonly-gapps.img.xz" or is this not okay ?

 

[jwarrior319]

It's a Chuwi Hi9 Air with OEM Android 8.0.0. Arm64 A-only system partition.
Please see image attached.
Thanks.

Try grabbing the latest firmware from the official thread: https://forum.xda-developers.com/ge...9-air-64gb-mt6797-x20-deca-core-t3775682/amp/
( Named "Stock Rom Build number O00623 release-keys 20181122")
Thats the latest available. This way your vendor partition is on newest update. If that dosent work i dont think you'll be able to install android 10 GSI's, at least not aosp. I would try PHH's android 9 aosp v123 GSI. Android 10 seems to be very picky for devices that didn't get a pie update for vendor partition. There were some format/directory changes from 8 to 9.

Sent from my SM-G975U1 using XDA Labs

 

[uncleabubear]

Try grabbing the latest firmware from the official thread: https://forum.xda-developers.com/ge...9-air-64gb-mt6797-x20-deca-core-t3775682/amp/
( Named "Stock Rom Build number O00623 release-keys 20181122")
Thats the latest available. This way your vendor partition is on newest update. If that dosent work i dont think you'll be able to install android 10 GSI's, at least not aosp. I would try PHH's android 9 aosp v123 GSI. Android 10 seems to be very picky for devices that didn't get a pie update for vendor partition. There were some format/directory changes from 8 to 9.

Sent from my SM-G975U1 using XDA Labs

Thanks 9 v.123 works well. I'll stick with that.

Sent from my BKL-L09 using Tapatalk

 

[HueyT]

So i have a MT6580 devices with shipped android 8.1 go.
Treble Info says VNDK version 27.0, no system-as-root and is ARM32
Can i flash "system-quack-arm-aonly-gapps.img.xz" or is this not okay ?

Yes, should work but anything can not boot

 

[spancor]

Hello,

I have a umidigi one pro. I have tried flashing the image with TWRP (I used the arm64, a only gapps one?), I flashed it to the system partition and in TWRP there's no errors during flashing etc.
After rebooting, my umidigi boot logo comes up for a few seconds, followed by the android one, but it gets stuck here.
Anyone any ideas as to where I'm going wrong?

Thank you

 

[aljoscha81]

free post

Sry that i ask again is it possible to use ir scanner for unlock device with this gsi ?aosp they written here on xda got iris scanner driver inbuild since android 9 so device with ir iris scanner you know galaxy s8 and also s9 note9 also(my device) and got seen you got a lot devices you can use for testing so is it possible that it will working with gsi ?
I use stock android 10 for now and would straight change to a gsi if the ir iris scanner would work

 

[nicmair]

Here is what I do

1, via the flashtool (you can get from UMIDigi support pages) flash the stock ROM and allow it to boot
2, Power off phone
3, open Flashtool, load scatter file (its in the Stock ROM directory)
4, unselect all
5, scroll to system img and click the path to img file, select the phhusion img file you have download and extracted, 7zip is best)
this will change the img file path
6, click the download button
7, plug the phone in
8, when update complete, unplug the phone and power it on
9, wait...... it should boot into the initial setup screen
10, configure

for future updates, if you don't do step 1, it will apply a more recent update over an existing one, which I have found quite successful

I have found the using TWRP has been more problematic and via the Flashtool to be far more sucessfull

Hello,

I have a umidigi one pro. I have tried flashing the image with TWRP (I used the arm64, a only gapps one?), I flashed it to the system partition and in TWRP there's no errors during flashing etc.
After rebooting, my umidigi boot logo comes up for a few seconds, followed by the android one, but it gets stuck here.
Anyone any ideas as to where I'm going wrong?

Thank you

 

[JuanM2020]

Sry that i ask again is it possible to use ir scanner for unlock device with this gsi ?aosp they written here on xda got iris scanner driver inbuild since android 9 so device with ir iris scanner you know galaxy s8 and also s9 note9 also(my device) and got seen you got a lot devices you can use for testing so is it possible that it will working with gsi ?
I use stock android 10 for now and would straight change to a gsi if the ir iris scanner would work

Neither face unlock nor iris scanner is built into this gsi. You would have to flash it via twrp or whatever custom recovery you are using.

 

[spancor]

Here is what I do

1, via the flashtool (you can get from UMIDigi support pages) flash the stock ROM and allow it to boot
2, Power off phone
3, open Flashtool, load scatter file (its in the Stock ROM directory)
4, unselect all
5, scroll to system img and click the path to img file, select the phhusion img file you have download and extracted, 7zip is best)
this will change the img file path
6, click the download button
7, plug the phone in
8, when update complete, unplug the phone and power it on
9, wait...... it should boot into the initial setup screen
10, configure

for future updates, if you don't do step 1, it will apply a more recent update over an existing one, which I have found quite successful

I have found the using TWRP has been more problematic and via the Flashtool to be far more sucessfull

Thank you so much! I have flashed the stock rom multiple times using flash tool so hopefully with your instructions I can get this sorted will give it a go when I get home, and again, thank you! Really appreciate it.

EDIT: So I used the flash tool method, but have ended up with the same results, my phone is just stuck on android boot screen is it possible that I have been using the wrong system image from phhusson for my device? I don't know much about this stuff except how to flash TWRP lol so any help is very appreciated

 

[wax_77]

hi everyone,
i'have just installed latest version on my huawei p20 lite via fastboot option (no twrp)

the rom is rooted can I remove root?

 

[dotKin]

hi everyone,
i'have just installed latest version on my huawei p20 lite via fastboot option (no twrp)

the rom is rooted can I remove root?

You can go to Settings > Phh Treble Settings > Misc features > Securize

That will remove root but it may cause a bootloop, in that case just reflash the ROM and you should be able to get into the system again without losing data

 

[xVM]

Legacy SGI

Hi! I have device Teclast M30 which is Android 8.0, and I'm sure Vendor would not update his firmware or make patch for vendor.img
I've found some info here changes-in-legacy-gsis and vendor-binaries-and-vndk-dependencies

Since topic-starter has wrote at 1st post :

4. If you're on an Android 8.0 vendor, you'll need to stick to vendors with Security Patch Level before April 2019 (that's a bug of my GSI)

Does It possible to build image using Phh-treble sources and Legacy SGI ? And how?

PS: I've tried to install this AOSP.10 rom already but no success

 

[rajaumarfarooq]

Thank you so much! I have flashed the stock rom multiple times using flash tool so hopefully with your instructions I can get this sorted will give it a go when I get home, and again, thank you! Really appreciate it.

EDIT: So I used the flash tool method, but have ended up with the same results, my phone is just stuck on android boot screen is it possible that I have been using the wrong system image from phhusson for my device? I don't know much about this stuff except how to flash TWRP lol so any help is very appreciated

this happens because of missing Disable_Dm-Verity_ForceEncrypt because gsi from 205 to upwords just encrypts the vendor partition and you cant boot into system
you said you can install twrp just install the twrp and flash this file Disable_Dm-Verity_ForceEncrypt_08.18.2019 and you will be able to get it work i have attached the file also

 

[xVM]

Log of bootloop on Teclast M30

this happens because of missing Disable_Dm-Verity_ForceEncrypt because gsi from 205 to upwords just encrypts the vendor partition and you cant boot into system
you said you can install twrp just install the twrp and flash this file Disable_Dm-Verity_ForceEncrypt_08.18.2019 and you will be able to get it work i have attached the file also

Hi! Maybe you know where can I send my log of bootloop on Teclast M30? (full wipe, flash system + your script)
I've saw somewhere in forum about this ROM that I must attach logs about such problem...

 

[djlukas1983]

hi everyone,
i'have just installed latest version on my huawei p20 lite via fastboot option (no twrp)

the rom is rooted can I remove root?

How does it work? Does the camera and fingerprint sensor work?

 

[nicmair]

hmmmm... I think I flashed the Disable_Dm-Verity_ForceEncrypt once a log time ago via TWRP, but haven't had TWRP installed for a while, and regularly use the method I provided. Does this mean that the Disable_Dm-Verity_ForceEncrypt sticks, even when going back to Stock ROM?

this happens because of missing Disable_Dm-Verity_ForceEncrypt because gsi from 205 to upwords just encrypts the vendor partition and you cant boot into system
you said you can install twrp just install the twrp and flash this file Disable_Dm-Verity_ForceEncrypt_08.18.2019 and you will be able to get it work i have attached the file also

---------- Post added at 01:23 PM ---------- Previous post was at 01:19 PM ----------

Still no joy with MMS, any pointers on creating a log file to capture what might (or might not) be going on.

Some logcat data, which I knew how to comprehend it...

02-20 13:52:27.490 2357 2376 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=28514 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:53:07.548 2357 9721 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=28514 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:53:21.205 2357 2357 I ActivityManager: Killing 28576:com.google.android.apps.messaging:rcs/u0a129 (adj 985): empty #17
02-20 13:53:23.346 2357 2902 I ActivityManager: Killing 28514:com.google.android.apps.messaging/u0a129 (adj 985): empty #17
02-20 13:54:27.604 2357 2392 I ActivityManager: Start proc 30271:com.google.android.apps.messaging/u0a129 for service {com.google.android.apps.messaging/com.google.android.apps.messaging.shared.datamodel.action.execution.ActionJobService}
02-20 13:54:27.950 2357 4895 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:54:27.986 2357 3948 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:54:27.995 2357 3933 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:54:28.076 2357 2392 I ActivityManager: Start proc 30323:com.google.android.apps.messaging:rcs/u0a129 for broadcast {com.google.android.apps.messaging/com.google.android.ims.receiver.ProvisioningEventReceiver}
02-20 13:54:29.308 30271 30305 I chatty : uid=10129(u0_a129) com.google.android.apps.messaging identical 1 line
02-20 13:54:29.390 2357 3933 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:54:33.909 2357 5163 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:54:33.913 2357 5163 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:54:34.453 2357 3933 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:54:39.127 2357 3655 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:54:44.486 2357 3655 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:55:12.599 2357 3957 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:56:01.301 2357 3655 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:56:28.003 2357 3655 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:56:30.916 2357 3655 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:57:41.012 2357 3655 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=30271 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 13:57:44.371 2357 2884 I ActivityManager: Killing 30323:com.google.android.apps.messaging:rcs/u0a129 (adj 975): empty #17
02-20 13:58:04.421 2357 2504 I ActivityManager: Killing 30271:com.google.android.apps.messaging/u0a129 (adj 965): empty #17
02-20 13:58:33.255 2357 6864 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.apps.messaging/.ui.ConversationListActivity bnds=[150,1312][290,1424]} from uid 10136
02-20 13:58:33.348 2357 2392 I ActivityManager: Start proc 31651:com.google.android.apps.messaging/u0a129 for activity {com.google.android.apps.messaging/com.google.android.apps.messaging.conversation.screen.ConversationActivity}
02-20 13:58:33.748 2357 2392 I ActivityManager: Start proc 31715:com.google.android.apps.messaging:rcs/u0a129 for broadcast {com.google.android.apps.messaging/com.google.android.ims.receiver.ProvisioningEventReceiver}
02-20 14:00:10.760 2357 2377 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService (has extras) } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=31651 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 14:00:34.296 2357 8419 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService (has extras) } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=31651 uid=10129 pkg=com.google.android.apps.messaging startFg?=false
02-20 14:00:34.297 31651 31651 W BugleDataModel: ActionExecutorImpl: Action started execution, but we can't guarantee it will complete, the app may be killed. Action: class com.google.android.apps.messaging.shared.datamodel.action.SelfParticipantsRefreshAction-SelfParticipantsRefreshAction:747209854009
02-20 14:00:34.297 31651 31651 W BugleDataModel: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService (has extras) }: app is in background uid UidRecord{ac0a48a u0a129 CAC bg:+1m54s665ms idle change:cached procs:2 seq(0,0,0)}
02-20 14:00:34.297 31651 31651 W BugleDataModel: at com.google.android.apps.messaging.shared.datamodel.action.execution.ActionExecutorImpl.a(PG:97)
02-20 14:00:34.297 31651 31651 W BugleDataModel: at com.google.android.apps.messaging.shared.datamodel.action.execution.ActionExecutorImpl.a(PG:91)
02-20 14:00:46.857 19593 19626 W ProcStatsManager: No process nz.co.stuff.android.news/10168 for service com.google.firebase.messaging.FirebaseMessagingService
02-20 14:01:25.732 2357 2385 I ActivityManager: Killing 31715:com.google.android.apps.messaging:rcs/u0a129 (adj 999): empty #21
02-20 14:02:43.416 2357 2402 I PackageManager: Un-granting permission com.google.android.setupwizard.READ_DEVICE_ORIGIN from package com.google.android.apps.messaging (protectionLevel=18 flags=0x28cbbec5)
02-20 14:03:56.198 607 607 E Layer : [Surface(name=AppWindowToken{96ff7e8 token=Token{4de6d0b ActivityRecord{60757fc u0 com.google.android.apps.messaging/.conversation.screen.ConversationActivity t638}}})/@0xf9ba205 - animation-leash#0] No local sync point found
02-20 14:03:59.580 31651 31692 I WM-WorkerWrapper: Worker result SUCCESS for Work [ id=c0e248e9-12d6-4c07-89bf-bbdcbc7f98bd, tags={ com.google.android.apps.messaging.shared.datamodel.workqueue.WorkQueueWorkerShim, download_mms } ]
02-20 14:04:00.430 607 607 E Layer : [Surface(name=AppWindowToken{96ff7e8 token=Token{4de6d0b ActivityRecord{60757fc u0 com.google.android.apps.messaging/.conversation.screen.ConversationActivity t638}}})/@0xf9ba205 - animation-leash#0] No local sync point found
02-20 14:04:00.430 607 607 E Layer : [Surface(name=AppWindowToken{96ff7e8 token=Token{4de6d0b ActivityRecord{60757fc u0 com.google.android.apps.messaging/.conversation.screen.ConversationActivity t638}}})/@0xf9ba205 - animation-leash#0] No local sync point found
02-20 14:04:01.402 31651 31689 I WM-WorkerWrapper: Worker result SUCCESS for Work [ id=77fd77be-e7a5-4868-abe3-3b18581fe2e5, tags={ com.google.android.apps.messaging.shared.datamodel.workqueue.WorkQueueWorkerShim, update_unread_counter } ]
02-20 14:04:01.476 31651 31691 I WM-WorkerWrapper: Worker result SUCCESS for Work [ id=bd676956-5b8b-4b4f-9bd1-8f30d7fb7a6a, tags={ com.google.android.apps.messaging.shared.datamodel.workqueue.WorkQueueWorkerShim, update_unread_counter } ]
02-20 14:04:01.546 31651 31686 I WM-WorkerWrapper: Worker result SUCCESS for Work [ id=19ed4bb1-ba02-4fe3-8127-4d63cef7bf5c, tags={ com.google.android.apps.messaging.shared.datamodel.workqueue.WorkQueueWorkerShim, update_unread_counter } ]

If you rebooted after making the changes and it didn't work, then try clearing data for the mms app. Then make sure it has all the permissions it needs enabled. I checked your apn against what your carrier says, and everything looks perfectly correct, so I'd grab a log if it still isn't working after that.

 

[wax_77]

You can go to Settings > Phh Treble Settings > Misc features > Securize

That will remove root but it may cause a bootloop, in that case just reflash the ROM and you should be able to get into the system again without losing data

thank you very much, works

another question, there is no option to assign different ringtone to different sim (o maybe i can't find)

there is a workaround or an app?

bye

 

[PoochyX]

Do you need a Android 10 vendor so u can be heard on phone calls like there is this microphone bug on Android 10 GSIs where people don't hear me in phone calls but I can hear them...

Sent from my moto g(7) play using Tapatalk