[AOSP 8.1] [2019-03-06] Phh-Treble

Search This thread

ronypfd

Member
Dec 19, 2018
13
0
and what can i do about the fact that its stuck on boot screen ? i flashed oreo firmware on my phone then installed this oreo gsi then boot img and flashed magisk and no verity but still no luck its still on boot screen and it is on this screen for an hour now.. Other Gsi's do the same.. how can i fix this?

I´ve the same problem, but for me is that i cant use twrp recovery so i patched the stock boot.img and flash it using fastboot instead of Qfil (i have levono k5 play smartphone and trying with AOSP 9.0), then i boot my phone and it cant pass the google boot setting, cant search wi-fi network and when i try to omit it stay in a screen that say something like final information, so i tryed with this rom and the same problem so i intalled gsi havocOS and it works great, i think is cause it dont have gapps. Before i flashed that patched boot image everything was working great.

I could stay using havocOS but i need the gapps and as i was saying i cant install it, so if you or someone have the solution i will thank.

I´m not a native speaker, im learning yet.
 

I1V1A1N

Senior Member
Sep 12, 2016
207
39
github.com
I´ve the same problem, but for me is that i cant use twrp recovery so i patched the stock boot.img and flash it using fastboot instead of Qfil (i have levono k5 play smartphone and trying with AOSP 9.0), then i boot my phone and it cant pass the google boot setting, cant search wi-fi network and when i try to omit it stay in a screen that say something like final information, so i tryed with this rom and the same problem so i intalled gsi havocOS and it works great, i think is cause it dont have gapps. Before i flashed that patched boot image everything was working great.

I could stay using havocOS but i need the gapps and as i was saying i cant install it, so if you or someone have the solution i will thank.

I´m not a native speaker, im learning yet.

There is this .I use it successfully.
https://4pda.ru/forum/index.php?showtopic=774072&st=720#entry60100798
 

kirpi_e

Member
Nov 15, 2011
46
3
blackview 9500 pro..
Adaway can not sense root.. within
Rooted with Magisk.

It goes well on Arrow Os 8.1 version but that does not have MTK patches so no gsm working..

any advise?
 

Parabellum23

Member
Jul 28, 2019
26
1
Known mess:
- A-only should use https://android-review.googlesource.com/q/hashtag:"non-ab-boot-gsi"+(status:open OR status:merged) instead of dm-verity hacks
- the dm-verity work-around is also needed on A/B, so other patches are missing, for some other reason
- On A/B devices, this system.img effectively transforms the device into a userdebug build. This means adb root works!
adb root should work on A-only later too, though it requires that the OEM includes https://android-review.googlesource.com/q/topic:move-adbd-to-system+(status:open+OR+status:merged)
This can probably be worked-around by moving adbd inside a /system/etc/init/xxx.rc
- ADB auth is totally disabled at the moment on A/B, this is bad, but useful for debugging.
- Huawei (for instance Mate 9) doesn't declare android.hardware.fingerprint. This ROM does it for them, but this need to be better implemented
- SuperSU and Magisk screws with SELinux policy. DO NOT USE SuperSU OR Magisk WITH THIS ROM

I dont get how to flash the NON VERITY HACKS for A only. What and how to flash this https://android-review.googlesource.com/q/hashtag:"non-ab-boot-gsi"+
 

robneymcplum

Senior Member
Oct 22, 2007
737
154
midlands
is there any chance the MTK fixes done on the AOSP 9 rom can be done on this AOSP 8 also? If I flash this I cant get incoming sms or data so cant log in to google, but can on the AOSP 9 version. And I just prefer android 8 thats all.
 

Chaos Storm

Member
May 20, 2010
38
10
Delta
@phhusson , I just wanted to mention that the Treble build of 8.1 AOSP Go works perfectly on my BlackView BV5500. Originally it came with 8.1 and was very slow. (MT6580 isn't that powerful) However with your 8.1 Go build, this things is actually usable and fast now!

The only issues are that this phone and others that have "Legacy Treble" can be glitchy. I had to download the original ROM for this and flash the original boot and recovery, then it would complain upon boot that something was corrupted, advise me to format/erase which I did, then kick me to fastboot and only then could I flash he ROM. Very weird, but it works!

I've posted my ported version of TWRP for the BV5500 on NeedRom for anyone who has that phone or has another MT6580 phone they want to port TWRP to.
 
  • Like
Reactions: lirka83

akirasek

New member
Dec 12, 2019
1
0
Google Player Service also blocked?

Anyone running into this issue using v13 AOSP 8.1 A/B Arm64 gapps img on Google Pixel XL

Edit: not sure why the picture is like that using xda app

Hi,

I somehow find this thread when searching for GMS certification error device information.

In addition to the "device is not certified" warning and user can't sign-in to GApps limitation, do you experience the same limitation on Google Player Service such as Firebase and FCM? These are more backend services comparing to GApps Sing-in but I would like to know what will happen on the apps which have a dependency on Google Player services when the device is not certified.
 

liam_davenport

Senior Member
Apr 17, 2014
5,494
4,953
26
Wakefield
Hi,

I somehow find this thread when searching for GMS certification error device information.

In addition to the "device is not certified" warning and user can't sign-in to GApps limitation, do you experience the same limitation on Google Player Service such as Firebase and FCM? These are more backend services comparing to GApps Sing-in but I would like to know what will happen on the apps which have a dependency on Google Player services when the device is not certified.

Sorry I sold my Pixel XL a long time ago and cannot help you with this.
 
Oct 22, 2018
16
8
Is there any way to install the GSI Aosp ROM via TWRP "adb sideload" command? I have tried but I get the error zip file is corrupt. I cannot use the simple method of moving the file into the device storage as so TWRP can use because I get the error of driver "This device cannot start. (Code 10)" .
 

Thejayyadav

Senior Member
Nov 12, 2016
75
24
Siwan
Is there any way to install the GSI Aosp ROM via TWRP "adb sideload" command? I have tried but I get the error zip file is corrupt. I cannot use the simple method of moving the file into the device storage as so TWRP can use because I get the error of driver "This device cannot start. (Code 10)" .
By extracting downloaded file you will get an img file. Now flash that img file via twrp to system.
 
  • Like
Reactions: Spaceminer

Top Liked Posts

  • There are no posts matching your filters.
  • 437
    WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!

    The goal of this ROM is to provide full Treble-compatible hardware support, and nothing else.
    This means that hardware which DON'T have Treble API won't be supported, like Essential's external camera.
    No feature will be added. This will ease forward porting to new Android versions, which is the very goal of Project Treble :)

    My hope is that other ROM developers will use this ROM as a basis to construct more advanced ROM.

    For a list of supported devices, consult and fill https://github.com/phhusson/treble_experimentations/wiki

    How to flash:
    Follow instructions available at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/

    Changelog
    v29 (2019-03-06):
    - March security patch
    - Fix MT6739 incoming SMS and mobile data

    v27 (2019-01-08):
    - January security patch
    - arm32_binder64 variant
    - Minor stuff

    v25 (2018-09-07)
    - September security patch
    - [Mi 6X/Mi Pad 4] Fix backlight
    - [Mi Mix 2S] Disable fingerprint button behaviour
    - [Galaxy S9/Note 9]
    - Fix (some) MTK incoming call
    - Fix a2dp on some devices
    - Fix boot on some devices

    v23 (2018-08-07):
    - August security patch
    - Fixes tethering on some Qualcomm devices (Thanks @notsyncing)
    - Enable Ambient Display for everyone
    - Add an off-computer flasher (first step towards OTA)
    - Fixes MTP
    - Fixes fingerprint on Moto devices
    - Change Huawei quick charge based on device (Thanks @Dil3mm4 )
    - Fixes camera on Moto devices
    - Fix notches height for some devices (Thanks @tadiT7)

    v22 (2018-07-03):
    - July security patches
    - Fixes Samsung Galaxy S9 fingerprint enrollment
    - Fix in-call audio for Pixel 2
    - Disable night mode on some MTK for which it is very slow
    - Fix wifi tethering on some configurations

    v21 (2018-06-27):
    - [OnePlus 6] Fix booting on A slot
    - [OnePlus 6] Fix userdata filesystem size
    - [OnePlus 6] Include a framework-res overlay (fixes auto backlight, improve battery-life, ...)
    - Fix status bar height for notches on various devices (Thanks @tadiT7)
    - [Samsung Galaxy S9 Qualcomm] Fix backlight
    - Fix webview in Android Go variant
    - Fix audio jack for some devices
    - Fix H264 encoding on Huawei (Thanks @OldDroid)
    - Fix backlight on some SDM845 devices (Xiaomi Mi Mix 2S, Xiaomi Mi8)

    v20 (2018-06-07):
    - June Android security patch level
    - New experimental FLOSS variant (check sources for list of apps)
    - [OnePlus6] Fixes backlight
    - [OnePlus6] Partial support for DnD slider
    - Fixes bug on some A/B devices where device would stop booting after several success

    v19 (2018-06-03):
    - Huawei fast charge (Thanks @flex1911 and @OldDroid)
    - Fix MTK TrustKernel TEE (those devices will need to factory reset!)
    - Support 32bits Android 8.0 devices
    - Rewrite Security Patch Level for Android 8.1 devices, and A/B devices as well. Should fix boot for some devices.
    - Enable GPU profiling on Huawei devices to fix UI glitches
    - Fixed Modded Google Camera installation
    - Use round icons
    - Enable doze
    - New Android Go variant
    - On Huawei devices add "Swipe fingerprint for notifications" option
    - Releases are now compressed with xz. Uncompress before flashing.

    v18 (2018-05-14):
    - Update to Android Security Patch level 2018-05-01
    - Disable HW keystore on mediatek devices using trustedkernel, until it is fixed
    - Re-enable Huawei navigation keys (Thanks @LuK1337 and OpenKirin team)
    - Fixes android build version/security patch level (might lead to stuck on bootanimation some devices)
    - Enable NightMode for everyone
    - Enable automatic backlight with Huawei Mate 9 settings on Huawei devices
    - Remove unnecessary warning on boot (if you still get it, it means it is useful, to tell me!)
    - Include android.system.net.netd, fixes data connection for several Qualcomm devices

    v17: (2018-04-24)
    - Fixes multimedia from SDCard
    - Fixes in-call audio for Qualcomm devices
    - Fixes in-call earpiece/speaker for Foxconn/Qualcomm devices (Razer Phone, Sharp Aquos S2, ...)
    - Fixes signal level for Huawei devices (Thanks to OpenKirin team)
    - Fixes boot on some A-only devices (HTC U11+, Xperia XZ1 at least)
    - Report vendor's security patch level instead of framework security patch level
    - Fix fsck for f2fs (Thanks @flex1911 and @LuK1337)

    v16: (2018-04-05)
    - Fixes MTP access to sdcard
    - v15 was missing graphical glitches fix. Applied it again.
    - Resize /system to maximum size on first boot

    v15: (2018-04-03)
    - Update to 2018-04-01 security patches
    - Fixes FAT sdcards
    - Fixes some USB-C headphones on some devices
    - Fix Essential PH-1 boot

    v14: (2018-03-26)
    - Fixes Galaxy S9(+) backlight control

    v13: (2018-03-23)
    - Disable Android's fake touches, which made unlocking hard
    - Fixes Galaxy S9 boot and WiFi
    - Make system.img back to 1.5GB
    - Disable again adb auth, to help debugging

    v12: (2018-03-05)
    - Updated to security patch 2018-03-01
    - Various stability, behind-the scene, changes
    - Fixes camera on MTK devices
    - Support ARM32 devices
    - Supports HW button backlight

    v11: (2018-02-20):
    - Fixes bluetooth on Kirin 970 devices (Thanks @LuK1337)
    - Fixes sdcard on Huawei devices
    - Includes nfc-nci.conf, should fix NFC on some devices
    - Show real Android version (Thanks @LuK1337)
    - Enable ADB authentification

    v10: (2018-02-18)
    - Android 8.1 !
    - Includes versioned vndk, so devices running both 8.1 and 8.0 should work

    v9: (2018/01/15)
    - Include the compositing fixes for Kirin 970
    - Crude support for Huawei fingerprint gestures (click = home, left = back, right = voice assistant, up = quick settings, down = notifications, long press = recent apps)

    v8: (2018/01/14)
    - Huawei compositing fixes (fixes various graphical glitches)
    - Various su SELinux fixes

    v7: (2017/12/30)
    - Fixes various regressions (APNs, A/B, vanilla, fingerprint ...)
    - Fixes dev/input requirement (not useful to any real-life product yet, afaik)
    - Fixes some not-installable applications from Play Store
    - Fixed substratum in phh's superuser

    v6: (2017/12/19)
    - Major code clean-up. Please report regressions
    - Fixes random reboot on Huawei devices
    - Optionally includes SU (you need to install phh's SuperUser from F-Droid/Play Store)

    v5: (2017/12/14)
    - Fixes FDE decryption (SystemUI was crashing in loop)
    - Use a real list of APNs
    - Include Chrome and Gboard (fixes IME crash when trying to input a symbol)
    - Fixes SEPolicy for Hardware Overlay Picker (should fix crash of Hardware Overlay Picker on startup)

    v4: (2017/12/10)
    - Fixes sdcard in MTP
    - Fixes Dual-SIM
    - Includes hardware-specific overlays:
    - Enable 4G selection in networks
    - Bigger status bar on Essential PH-1
    - Enable navigation bar on HTC U11+

    v3: (2017/12/04)
    - Fixes sdcard in MTP build fail, so will be fixed in next release
    - New variant including gapps

    v2: (2017/11/26)
    - Fix wifi tethering
    - Fix F2FS userdata
    - Fix sdcard
    - Fix fingerprint (Huawei)

    Download:
    https://github.com/phhusson/treble_experimentations/releases/download/v29

    Want to chat about this project? Go to Freenode IRC, #phh-treble.
    IRC: irc://irc.freenode.net/#phh-treble
    WebIRC: http://webchat.freenode.net/?channels=#phh-treble&uio=d4
    Matrix: #freenode_#phh-treble:matrix.org

    Other chatrooms:
    Telegram https://t.me/phhtreble

    Thanks @MishaalRahman and @Exelios for the huge kickstart help

    Thanks to all my donators:
    - @Exelios

    - @fargonaz
    - @VictorM86
    - @howdid
    - @heatfire
    - @ohwarumbloss
    - @RexGoogolplex
    - @abhas.abhia
    - @Emoclaw
    - @Sebianoti
    - @DocRambone
    - @egandt
    - @Blackbird1997
    - @Burakki
    - @josdehaes
    - @TheUndertaker21

    Thanks to the following companies:
    - Huawei, for a Huawei View 10
    - Blackview, for a Blackview A20

    PS: Yes the name sucks, but I'm clueless about a name
    114
    How to know if your phone is supported:

    - Does your OEM provides a stock Oreo ROM?
    No ===> Your phone is not supported
    - Run Treble Check on stock Oreo ROM. Does it say Treble is supported?
    No ===> Your phone is not supported

    If all answers are yes, then your phone MIGHT be supported.
    Test it, and report the result!
    76
    Build script available at https://github.com/phhusson/treble_experimentations/blob/master/build.sh

    Current status:

    Over-all:

    Xperia XZ1:
    - Broken camera (because of Sony's DRM)

    Huawei Mate 9 Pro and Honor 9:
    - Fingerprint sensor should have "home" behaviour
    - software keys should be disabled

    Known end-user problems (WON'T BE FIXED in this ROM):
    - No exfat
    70
    Known mess:
    - A-only should use https://android-review.googlesource.com/q/hashtag:"non-ab-boot-gsi"+(status:open OR status:merged) instead of dm-verity hacks
    - the dm-verity work-around is also needed on A/B, so other patches are missing, for some other reason
    - On A/B devices, this system.img effectively transforms the device into a userdebug build. This means adb root works!
    adb root should work on A-only later too, though it requires that the OEM includes https://android-review.googlesource.com/q/topic:move-adbd-to-system+(status:open+OR+status:merged)
    This can probably be worked-around by moving adbd inside a /system/etc/init/xxx.rc
    - ADB auth is totally disabled at the moment on A/B, this is bad, but useful for debugging.
    - Huawei (for instance Mate 9) doesn't declare android.hardware.fingerprint. This ROM does it for them, but this need to be better implemented
    - SuperSU and Magisk screws with SELinux policy. DO NOT USE SuperSU OR Magisk WITH THIS ROM
    31
    There, I released my first Android 8.1 version.
    Overall, I consider it less stable than 8.0, but I think it should be usable.

    For the known limitations:
    - On MTK, camera doesn't work
    - On Huawei, I could get Huawei stock app to run

    And Download manager is still broken, so you still have to kill play store every time you want to download an app...

    Dirty flash should work, but I barely tested it.

    It took me a lot of effort, so please enjoy :)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone