Related
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
This is a UNOFFICIAL build of LineageOS for the Samsung Galaxy Core Plus.
It's not ready yet and has some bugs in it which could cause problems to some users.
The ROM will only work on the SM-G350 Version of the Phone (without any Numbers/Letters behind).
This ROM could be used for daily use now (though you should look at the list of what doesn't work first).
Known Bugs
Camera sometimes switches to green-purple. The resulting picture doesn't have the weird color, but it may be flipped and/or distorted at the edges.
Video Recording
Codecs (some work, some don't. I tested MP4 and AVI, both work. I should really make a list...)
Installation Instructions
Special thanks to @Giovix92 for making this tutorial!
Requirements:
1: A computer with Windows.
2: An Internet connection.
3: A backup of your phone data (contacts, photo, music, videos, and other).
4: About 300 MB free space on your SD card.
5: Phone charged at least 80%.
Download links are below
I do NOT take any responsibility for bricked devices!
Let's start!
1: Download the Samsung USB Drivers.
2: Download the ODIN3. (Only for Windows)
3: Download the TWRP Odin package to your desktop and download the LineageOS 13 zip to your SD card.
4: Make a backup of your files, because the storage will be wiped. (External SD card will not be wiped)
5: Reboot your phone in to the Download mode (Volume Down- , Home- and Power button). Press the Volume Up button when asked. Then open the ODIN3 and connect your phone to your PC.
6: Press AP and choose the TWRP Odin package (recovery.tar) and make sure re-partition is NOT ticked. "Auto-Reboot" should not be ticked either, otherwise you will need to be quick to boot into the recovery immediately after flashing.
7: Press start! Wait a few seconds. Then your phone will be rebooted. Now you can disconnect the cable and power off your phone.
8: Boot your phone in to the TWRP Recovery (Volume Up-, Home- and Power button).
9: Go to Wipe, and Swipe to Factory Reset.
10. After wiping go to the home screen by pressing the home button.
11: Go to Install. Choose the "external_sd" from the top bar. (It says "Storage: Internal Storage (xxxxMB)" by default)
12: Choose the LineageOS 13 ZIP and Swipe to Confirm Flash. Make sure you don't power off while flashing!
13: After the zip has been flashed choose "Reboot System".
14: Wait 5-15 minutes to boot the phone. If the phone keeps booting take out the battery and do a Factory Reset again.
15: When the phone boots the first time, go through the Setup Wizard and you are ready to use your phone!
If there was something you didn't understand, please don't hesitate to ask
Changelog
23-01-2021:
Security patches until April of 2019
Updated Chromium from 67.0.3396.87 to 87.0.4280.101
Disabled latinimegoogle (which is compiled against an incompatible instruction set and results in crashes)
Fix offline charging
Old Changelogs:
02-05-2019:
Include all security patches up to January 2019 (and most of February and March, except for the PNG vulnerability)
NFC
Fix up some of the codecs (h264 and ac3, which should enable you to watch most videos)
Remove Gello (the old, bloated Browser) in favour of Jelly
Using way less hacks than previously (again)
05-04-2018:
Include all security patches up to March 2018
SELinux is now enforcing
OTA Updates the third (now using the internal Updater)
Using way less hacks than previously
24-05-2017:
Now compile with newest toolchain (Commit)
Fix SD Card (Device commit, Kernel commit)
Removed PMEM from the kernel (as this saves some RAM) (Commit)
OTA Updates (Commit)
18-04-2017:
Switch to LineageOS
4 Months of Security Patches
10-04-2017:
Fixed GApps (through a modified WebView)
07-04-2017:
Fixed Network (Commit)
Enabled permissive SELinux (Patch, Commit)
10-10-2016:
Bringup
Downloads
Samsung USB Drivers
Odin v3.09
Odin v3.11.1
TWRP 3
TWRP 2.8.1.0
lineage-13.0-20210123-UNOFFICIAL-cs02.zip
Sources
Device tree
Kernel tree
Proprietary files
WebView
Thanks To/Credits
Thanks to ...
... androidlover5842, ishantvivek, SandPox, ZIM555 and everyone else working on Samsung's hawaii-Boards
... berkantkz and santeri3700 for teaching me the basics of ROM developing
First Version of CM 13 is up
First! Good rom man!
Inviato dal mio ASUS_Z00A utilizzando Tapatalk
Hey !
i was happy when i saw that cm13 was out for our galaxy core plus so now i'm downloading it. After i will flash it if you want i can be a beta tester.
Thanks for this rom !
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
I installed it and for me the bigest problem is the wifi.
gaetano76le said:
Hey !
i was happy when i saw that cm13 was out for our galaxy core plus so now i'm downloading it. After i will flash it if you want i can be a beta tester.
Thanks for this rom !
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
I installed it and for me the bigest problem is the wifi.
Click to expand...
Click to collapse
Still working on that.
I just noticed that the sound sometimes "breaks" and sounds like damaged speakers (just for a part of a second, nothing permanent). I don't know if this is a software problem or just my phone. Can someone confirm that? It sometimes happens when doing a call or pressing random numbers at the Dialer. It also seems to happen only with standard sound level or higher.
I'll check it after I fixed (or tried to fix) Internet and SD Card
This is the same on stock when listening YT idk why it happens.
For the sdcard fix check if there are correct mounts for vold.fstab or framework
BTW. Videoplayback isnt working good on YT on Internet browser and is glitched too on chrome.
TimSchumi said:
I just noticed that the sound sometimes "breaks" and sounds like damaged speakers (just for a part of a second, nothing permanent). I don't know if this is a software problem or just my phone. Can someone confirm that? It sometimes happens when doing a call or pressing random numbers at the Dialer. It also seems to happen only with standard sound level or higher.
I'll check it after I fixed (or tried to fix) Internet and SD Card
Click to expand...
Click to collapse
bump
@TimSchumi
http://forum.xda-developers.com/s7582/development/rom-cm13-0-galaxy-s-duos-2-trend-plus-t3307986
Maybe talk with this guys to allow to use their source? Will be easier to fix rom and you will can to support them too
So, any changes about the network?
QGM said:
bump
@TimSchumi
http://forum.xda-developers.com/s7582/development/rom-cm13-0-galaxy-s-duos-2-trend-plus-t3307986
Maybe talk with this guys to allow to use their source? Will be easier to fix rom and you will can to support them too
Click to expand...
Click to collapse
Thanks for searching :good:
I'll write to developer and ask for the fix!
john_sdr said:
So, any changes about the network?
Click to expand...
Click to collapse
Not now, still working on it. I don't even know where to search.
something about the vpn? or maybe something isnt compatible with cm13?
I searched on google and disable the firewall could be a solution.
john_sdr said:
something about the vpn? or maybe something isnt compatible with cm13?
Click to expand...
Click to collapse
Seems to be a more general problem. I'll look through the device/kernel/vendor trees of similiar devices for a fix.
SpYneX_ said:
I searched on google and disable the firewall could be a solution.
Click to expand...
Click to collapse
Could you test it?
TimSchumi said:
Seems to be a more general problem. I'll look through the device/kernel/vendor trees of similiar devices for a fix.
Could you test it?
Click to expand...
Click to collapse
How could you even disable a device's firewall?
Well, i just red here "https://forums.oneplus.net/threads/official-cm13-nightly-builds-rolling-out-for-opo.411202/page-103" that its may be fault of the recovery. I dont think that we all got the same twrp though, is something you can test? i used santori's twrp, i had it flashed quite a time. maybe an update or a modification will solve that issue
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Hey, I'm new here at xda forums. I just installed this ROM on my galaxy core plus, and it works great. My phone is now super snappy. But many features don't work as of now, the bluetooth actually worked for me, I didnt expect it to after reading the post. When will these bugs be fixed, and more importantly how can I follow so that I can get my hands on the new release as soon as it gets out? Thanks a lot!
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
john_sdr said:
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Click to expand...
Click to collapse
I also could try to make CM Recovery first, and if it won't work, I'll give TWRP a try.
Abiti7 said:
Hey, I'm new here at xda forums. I just installed this ROM on my galaxy core plus, and it works great. My phone is now super snappy. But many features don't work as of now, the bluetooth actually worked for me, I didnt expect it to after reading the post. When will these bugs be fixed, and more importantly how can I follow so that I can get my hands on the new release as soon as it gets out? Thanks a lot!
Click to expand...
Click to collapse
I still need to search what causes the Internet and SD Card to fail. Bluetooth does work, only Bluetooth Calls, Car connection and other devices are untested.
You can subscribe to this thread or subscribe to the DevDB project, to get a notification if it's updated. To get updates on your Smartphone, you could install XDA Legacy (Tapatalk) or XDA Labs (just called XDA) from Play Store.
john_sdr said:
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Click to expand...
Click to collapse
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
CM Recovery didn't fix the problem. And I somehow can't get TWRP to boot.
XOS Chameleon ROM
HI GUYS
MY ALL ROM PORTED WITH NEW PORTING METHOD
HERE MY ROM COLLECTION to U007
google drive folder
LIST:
AICP 11 ( im just ported but not tested yet)
AMIGO OS ( first boot take long time because the rom deodexing yourself [ ~15-20min]
FIRA OS
FLYME OS 6
IPHONE 7 ROM reworked
LineAge OS ( im just ported but not tested yet)
PAC-ROM (everything works)
Resurrection Remix REWORKED (FM fixed and now everything works)
Star OS
XOS v2 REWORKED with new porting method
Working:
Wi-Fi
Bluetooth
GPS
Camera
Camera FOCUS fixed
Loud speaker
Microfone
Sim card
Memcard
Etc.....
DOWNLOAD
REWORKED WITH NEW PORTING METHOD
Download
Wipe all
Flash ROM from TWRP Recovery
Reboot and Enjoy!
I waiting replies.
Flyme OS 6
download
Install TWRP
Requirements: -MTK VCOM driver ( If you dont know how install, search it in google)
How install TWRP?
1.) Download this rar https://drive.google.com/open?id=0B4vXL_-A5tC2RUw3OU0ybHZSZ3M
2.) Extract it
3.) Open SP Flashtool and open the scatter file
4.) Connect your phone to pc
5.) Press download button
6.) Turn off your device , waiting few second and turn on. ( The sp flastool start working)
Congratulation !
You successfully installed TWRP recovery for your U007.
can i change language to german/english?
i cant add my google accounts pls fix that or say how to solve the problem!
sisxgame said:
How install TWRP?
1.) Download this rar https://drive.google.com/open?id=0B4vXL_-A5tC2RUw3OU0ybHZSZ3M
2.) Extract it
3.) Open SP Flashtool and open the scatter file
4.) Connect your phone to pc
5.) Press download button
6.) Turn off your device , waiting few second and turn on. ( The sp flastool start working)
Congratulation !
You successfully installed TWRP recovery for your U007.
Click to expand...
Click to collapse
why i cannot add google accounts on this rom error by communiation with google-servers
---------- Post added at 05:54 PM ---------- Previous post was at 05:23 PM ----------
sisxgame said:
OSX Chameleon ROM
Working:
Wi-Fi
Bluetooth
GPS
Camera
Camera FOCUS fixed
Loud speaker
Microfone
Sim card
Memcard
Etc.....
Not Working:
SystemUi Flashtorch toggle
Download
https://drive.google.com/file/d/0B4vXL_-A5tC2YmJmVW5vMEJfcDA/view
Wipe all
Flash from TWRP Recovery
Reboot Enjoy
I waiting replies.
Click to expand...
Click to collapse
nice that you said me that you have a rom but support would be very nice...
DarkXLord20 said:
why i cannot add google accounts on this rom error by communiation with google-servers
---------- Post added at 05:54 PM ---------- Previous post was at 05:23 PM ----------
nice that you said me that you have a rom but support would be very nice...
Click to expand...
Click to collapse
Hi
the googleplay working perfectly in my phone
the rom dont buggy
I think
1) wipe all in TWRP (wipe/advanced wipe and check Dalvik, system, Cache, Data )
2) Reinstall Rom
3) Int he first boot up. In xaccount settings , select the other country.
Reply if it works.
sisxgame said:
Hi
the googleplay working perfectly in my phone
the rom dont buggy
I think
1) wipe all in TWRP (wipe/advanced wipe and check Dalvik, system, Cache, Data )
2) Reinstall Rom
3) Int he first boot up. In xaccount settings , select the other country.
Reply if it works.
Click to expand...
Click to collapse
i meant google not xacc
DarkXLord20 said:
i meant google not xacc
Click to expand...
Click to collapse
yes i know but possible it is influence google account.
Just try it what i written
sisxgame said:
Hi
the googleplay working perfectly in my phone
the rom dont buggy
I think
1) wipe all in TWRP (wipe/advanced wipe and check Dalvik, system, Cache, Data )
2) Reinstall Rom
3) Int he first boot up. In xaccount settings , select the other country.
Reply if it works.
Click to expand...
Click to collapse
doesnt work for me
DarkXLord20 said:
doesnt work for me
Click to expand...
Click to collapse
Ok
i will test the download link and the rom
and maybe tomorrow this bug will fixed.
all the best bro
sisxgame said:
Ok
i will test the download link and the rom
and maybe tomorrow this bug will fixed.
all the best bro
Click to expand...
Click to collapse
i will try it tomorrow because i have no school so enough time to test it tomorrow
hello, can i easily return to the original rom ?
wojtekll said:
hello, can i easily return to the original rom ?
Click to expand...
Click to collapse
Sure.
1. method: Make TWRP backup of the stock rom. (all data and app restorable)
2.method: Use SP Flashtool and flash stock rom from pc
sisxgame said:
XOS Chameleon ROM
Working:Wi-Fi
Bluetooth
GPS
Camera
Camera FOCUS fixed
Loud speaker
Microfone
Sim card
Memcard
Etc.....
Not Working:Flashlite toggle
Download flashlite app from googleplay
(i will try fix it)
Download
V2
https://drive.google.com/open?id=0B4vXL_-A5tC2UXd3UjNGM2MxMTg
Wipe all
Flash ROM from TWRP Recovery
Reboot and Enjoy!
I waiting replies.
Click to expand...
Click to collapse
Would this rom work with ulefone u007 pro?
androidia said:
Would this rom work with ulefone u007 pro?
Click to expand...
Click to collapse
Unfortunately no. Becouse u007 pro have diffrent chipset.
(u007=MT6580 ; u007 pro=MT6735 )
Sorry bro.
Welcome, rom works very well, I had to just turn off the screen soft keys, now it's time for more tests. I do not know it is possible to the middle button works as on the original rom, after holding the last show running programs - now opens google.
wojtekll said:
Welcome, rom works very well, I had to just turn off the screen soft keys, now it's time for more tests. I do not know it is possible to the middle button works as on the original rom, after holding the last show running programs - now opens google.
Click to expand...
Click to collapse
If you want the original keymap ,
1) replace keylayout folder (stock to port) in system/usr/
I not tested the method, but should work.
(If i will have some time i test it)
Waiting the reply.
Unfortunately, after the copying of the original rom all of the buttons stopped working : o after the restoration folder rom chameleon also nothing worked. I had to restore the rom because no buttons work even power and vol up and down. Unless I did something wrong (I was copying the program es explorer)
wojtekll said:
Unfortunately, after the copying of the original rom all of the buttons stopped working : o after the restoration folder rom chameleon also nothing worked. I had to restore the rom because no buttons work even power and vol up and down. Unless I did something wrong (I was copying the program es explorer)
Click to expand...
Click to collapse
I make a flashable zip and upload it.
Patience bro.
I wonder whether that has changed an entry in the file build.prop with "qemu.hw.mainkeys = 0" to "qemu.hw.mainkeys = 1" has not caused a problem ?
This is my first post
Disclaimer: flash your own risk
Fully stable miui 9 by eko kodok
I am not the developer of this ROM
Instruction : reboot to recovery
Wipe (data system cache)
all with ex4( f2fs not supported)
unmount system
Flash miui 9
Flash gapps ( arm,5.11,pico,)
For updating :clean flash recommended for latest version gapps and super su included however you can change your root method after fist boot
Bugs : you tell me
Download 7.9.15::laugh::laugh:https://drive.google.com/file/d/0B9dI9Lbtzh2uYms5blg1UVFXNTQ/view?usp=drivesdk
Download 7.10.12(latest bug fixed):https://drive.google.com/file/d/0B9dI9Lbtzh2uNVlUZ01CM2txS3M/view?usp=drivesdk (gapps included super su included )
Change log second post
Press thanks if helped :good:
Credit: eko kodok for everything
And me for informing :laugh:
Android version :5.1.1
ROM status :stable
MIUI version :9 (7.10.12)
Highlights
Optimization - Hide free and incompatible themes in the list of the purchased items (10-10)
System
Fix - Auto brightness getting too dark compared to the previous version (10-10)
Fix - Download warning pops up repeatedly in Google Play/Gmail (10-10)
Phone
Optimization - Vibration no longer affects the features which reduce ringer volume when the phone is lifted or flipped to silence (10-10)
Themes
Optimization - Hide free and incompatible themes in the list of the purchased items (10-10)
Other
New - "Apps" support updates now (10-11)
And many more fixes enjoy
Note: it will comes with miui Chinese recovery but twrp is still there you can select recovery to go twrp from the Chinese recovery (the only English is that "recovery" you can find it easily ) how ever it will help us to patch based ota flasheble
Can you please share the original source? Thank you.
Screenshot
Please provide screenshots
xda_borj said:
Can you please share the original source? Thank you.
Click to expand...
Click to collapse
I told u buddys its not my ROM
This rom developed by eko kodok he is not going to upload on xda
masvk97 said:
Please provide screenshots
Click to expand...
Click to collapse
Bro this is same miui9 as pawan miui but its stable and zero bugs
pattanirijukvk said:
Bro this is same miui9 as pawan miui but its stable and zero bugs
Click to expand...
Click to collapse
rom is not booting bro.
any help for me???
ChaRun6 said:
rom is not booting bro.
any help for me???
Click to expand...
Click to collapse
First boot will take upto 15 mnts and if u formated data as f2fs you have to format data as ext4
pattanirijukvk said:
First boot will take upto 15 mnts and if u formated data as f2fs you have to format data as ext4
Click to expand...
Click to collapse
in ext4 and waited for 30mns.
Noting is happening bro
ChaRun6 said:
in ext4 and waited for 30mns.
Noting is happening bro
Click to expand...
Click to collapse
I don't have any problems try w/o gapps
who knows - not working menu for developer, home button, menu and recent apps
zhekacrazy said:
who knows - not working menu for developer, home button, menu and recent apps
Click to expand...
Click to collapse
Its working everything
pattanirijukvk said:
Its working everything
Click to expand...
Click to collapse
thank you. going to flash another
pattanirijukvk said:
I don't have any problems try w/o gapps
Click to expand...
Click to collapse
i just flashed rom noting else and tried many times
ChaRun6 said:
i just flashed rom noting else and tried many times
Click to expand...
Click to collapse
Are you using 32bit recovery then you have to mount system after wiping
the little things-not changing the profile picture, and the region. the region only China
zhekacrazy said:
the little things-not changing the profile picture, and the region. the region only China
Click to expand...
Click to collapse
Thanks for the review
The region only effect in mi apss
And the profile picture I'll look into it
always rollback fresh after restart
Link is updated look in op
Wipe everything f2fs not supported u have to format data and cache as ext4
After wiping everything unmount system
Flash ROM and gapps
pattanirijukvk said:
Are you using 32bit recovery then you have to mount system after wiping
Click to expand...
Click to collapse
we have to mount or unmount system plz be clear.
Alright, after way too long, I've finally gotten oreo working well enough to test. Please note:
These are beta quality, not suitable for daily usage yet.
Known issues will be listed. Anything not listed should work (but not everything has been tested).
Tested with opengapps micro arm64 8.1.
If you would like to test nougat upgrades, please let me know how that goes. I have only done a clean install so far. Keep in mind that you will need to flash oreo gapps, as gapps persistence does not work across versions.
Sources
Device
Kernel
Vendor
Prerequisites
All oreo builds require an updated TWRP to flash:
tulip-twrp-7.1-3.2.3-r2.img
Build 2018-10-12
Known issues:
SELinux is permissive.
Bluetooth MAC address is bogus.
AOKP Oreo:
aokp_tulip_oreo_UNOFFICIAL_2018-10-12.zip
MD5: 53946f9c4ae8833b91a324bd824d7b8a
Lineage Oreo:
lineage_tulip_oreo_UNOFFICIAL_2018-10-12.zip
MD5: ee2596eb998994714f20fc90f2968190
Build 2018-10-11
Known issues:
Camera does not work (black preview, will not take pics).
SELinux is permissive.
Bluetooth MAC address is bogus.
AOKP Oreo:
aokp_tulip_oreo_UNOFFICIAL_2018-10-11.zip
MD5: 2d94e29de8e1cec4d63f6bb7a6c8c054
Lineage Oreo:
lineage_tulip_oreo_UNOFFICIAL_2018-10-11.zip
MD5: 46c31ef9585b5f43c0096508f3d5a9ca
Build 2018-10-10
Known issues:
Camera does not work (black preview, will not take pics).
Fingerprint sensor not functional.
Battery charging LED not working.
SELinux is permissive.
Bluetooth MAC address is bogus.
AOKP Oreo:
aokp_tulip_oreo_UNOFFICIAL_2018-10-10.zip
MD5: d18580e66fc8e1a3282b97f4e8fff965
Lineage Oreo:
lineage_tulip_oreo_UNOFFICIAL_2018-10-10.zip
MD5: 45a4bea38fa6fd75497a756e5342cea9
Thank you very much for your work!
Will test the upgrade from 14.1 with LOS Version as soon as available.
you da man - will test
Thank you....I tought this phone was dead
Thank you....I tought this phone was completly forgeten, and that´s such a pitty as it is such a good phone
I am very glad to finally see a test build... I have been waiting forever. I am definitely going to test this out and give you some feedback! I already know the fingerprint sensor is going to be a downside for me as everybody in my house likes to look at me typing my pin lol. But, anyways I am greatly appreciative of you finally releasing a test build. Thank you.
Thank you sir!!
Updated TWRP (3.2.3-0): Doesn't recognize external microSD card
tdm said:
Alright, after way too long, I've finally gotten oreo working well enough to test.
Prerequisites
All oreo builds require an updated TWRP to flash:
tulip-twrp-7.1-3.2.3-r1.img
Click to expand...
Click to collapse
Hi tdm. I flashed the updated TWRP (3.2.3-0) but when I try to backup the partitions (system, boot, data, cache) the recovery only recognizes the internal storage but it doesn't recognize the external microSD card (which has a bigger storage size). I am attaching some "screenshots".
Thanks in advance.
Regards
LeonardoGC said:
Hi tdm. I flashed the updated TWRP (3.2.3-0) but when I try to backup the partitions (system, boot, data, cache) the recovery only recognizes the internal storage but it doesn't recognize the external microSD card (which has a bigger storage size). I am attaching some "screenshots".
Thanks in advance.
Regards
Click to expand...
Click to collapse
Okay thanks I'll look into it Monday. In the mean time use internal storage or side load.
Here is a list of bugs!
You may already be aware
I know this is Beta and you are still working on it.
[TWRP BUGS AS OF NOW]
- Not Recognizing External SD Card [Fixed As Of 10/09/2018]
- It Says That Gapps Is Already Installed Onto The System... But, It Still Flashes Gapps Regularly
[Not Sure If This Is A TWRP Bug Or System Bug... So, I Will Put It In Both Bug Lists!]
[BUGS AS OF NOW] (My Testing)
- Privacy Guard (system installed root), Magisk, and SuperSU do not work, encrypts device every time.
- If you click the home button and then click square (recent apps) button and click the app you just closed out of, it crashes SystemUI and then when you unlock the phone again it will be back in the app but... You are stuck in there no matter how many times you click the home button... stuck! (Just click recent apps (square button) crash the SystemUI and you will be out!) [Fixed As Of 10/09/2018] [tdm's Local Sources Were Out Of Sync!]
- It Says That Gapps Is Already Installed Onto The System... But, It Still Flashes Gapps Regularly
[Not Sure If This Is A TWRP Bug Or System Bug... So, I Will Put It In Both Bug Lists!]
- If you go to recent apps inside of any app it crashes SystemUI (Recent Apps Meaning Square Button On Navbar) [Fixed As Of 10/09/2018] [tdm's local sources were out of sync!]
- First boot and every reboot, Device Fingerprint mismatch [Fixed As Of 10/09/2018] [tdm's local sources were out of sync!]
- No Charging Notification Light! (Not really a bug... Just not yet implemented... I think!) [Fixed As Of 10/11/2018]
- In the settings, it says finish setting up Pixel Device
- Have to repeatedly keep clicking flashlight button for it to turn on! You only need to do this once though. [Fixed As Of 10/09/2018]
- In the slide down quick settings if you hold down the WiFi icon and turn it on... it doesn't really turn on lol (Not To Be Petty!) [Irrelevant As WiFi Is Working!]
[End Of Bug List]
Other than that it is pretty great... the navbar vibrations feel really nice
The settings look amazing compared to 7.0
The Power Off and Restart Menu... Just Beautiful!
NewbieGamingYT said:
I was literally just about to post the same exact thing. Luckily I have a computer... and I didn't want to redownload so I flashed the old TWRP and copied AOKP Oreo and Gapps and Magisk onto my pc and then installed the new TWRP and copied them onto the internal storage and flashed that way... But, it does suck for users without a PC.
---------- Post added at 07:55 AM ---------- Previous post was at 07:53 AM ----------
Just noticed this when flashing Gapps... it says that Gapps is already installed onto the system... But, it still flashes Gapps regularly.
---------- Post added at 08:10 AM ---------- Previous post was at 07:55 AM ----------
Here is a list of bugs after 5 minutes
You may already be aware
I know this is Beta and you are still working on it.
- WiFi doesn't work which wasn't mentioned above.
- If you go to recent apps inside of any app it crashes SystemUI (Recent Apps Meaning Square Button On Navbar)
- First boot, Device Fingerprint mismatch
- In the settings, it says finish setting up Pixel Device
- Have to repeatedly keep clicking flashlight button for it to turn on! You only need to do this once though.
- In the slide down quick settings if you hold down the WiFi icon and turn it on... it doesn't really turn on lol (Not To Be Petty!)
Other than that it is pretty great... the navbar vibrations feel really nice
The settings look amazing compared to 7.0
I can't really do much without WiFi though!
The Power Off and Restart Menu... Just Beautiful!
Going back to AOKP 7.1 until an update is released... all-in-all really great so far!
Click to expand...
Click to collapse
That's odd. WiFi should work and the recents button should also work. I'll have to look into that tomorrow. Maybe I screwed up my device sources somehow.
tdm said:
That's odd. WiFi should work and the recents button should also work. I'll have to look into that tomorrow. Maybe I screwed up my device sources somehow.
Click to expand...
Click to collapse
The exact mismatch it says on first boot is:
Title: Android System
(It Doesn't Say Title or Details!)
Details: A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches NMF26V.
OK Button.
---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------
tdm said:
That's odd. WiFi should work and the recents button should also work. I'll have to look into that tomorrow. Maybe I screwed up my device sources somehow.
Click to expand...
Click to collapse
Also, after re-installing AOKP 8.1 a second time the WiFi seems to be working... maybe just a bug there!
tdm said:
Recents button should also work. I'll have to look into that tomorrow.
Click to expand...
Click to collapse
The recents button works fine... as long as you are not in a app... If you click it inside of a app it crashes the SystemUI!
report errors with logcat please
Enviado desde mi K88 mediante Tapatalk
juniorgerman said:
report errors with logcat please
Enviado desde mi K88 mediante Tapatalk
Click to expand...
Click to collapse
Don't even know what that is!
Guide:https://wiki.lineageos.org/logcat.html
NewbieGamingYT said:
Don't even know what that is!
Click to expand...
Click to collapse
Enviado desde mi K88 mediante Tapatalk
There is my logcat and radio.
Backup to PC and ADB not working on updated TWRP
LeonardoGC said:
Hi tdm. I flashed the updated TWRP (3.2.3-0) but when I try to backup the partitions (system, boot, data, cache) the recovery only recognizes the internal storage but it doesn't recognize the external microSD card (which has a bigger storage size). I am attaching some "screenshots".
Thanks in advance.
Regards
Click to expand...
Click to collapse
I usually make backups using the external microSD card, so the problem mentioned above stopped me temporarily. I didn´t know how to do a backup to the PC but I investigated. If someone else wants to know how to make/restore a backup to/from the PC here is the procedure:
You need to have installed ADB on your PC.
You need to enter in recovery mode and connect the phone to PC with the USB cable.
There are two backup & restore commands: adb backup --twrp / adb restore filename.ab
Enter the one you need in the command prompt.
In the command prompt a message will tell you to unlock the device and swype to confirm the backup/restore action.
@tdm It looks like in the updated TWRP there is no connection with ADB. When I tried to make a backup with the "adb backup --twrp" command I got the following message:
adb: unable to connect for backup: no devices/emulators found
Also the result of the "adb devices" command is an empty list where there should be a device or devices.
Finally (this probable is only informational) after ejecting (on Windows) the "USB device" (the phone) I get this string inside the message:
Device "Google Nexus ADB Interface"
Regards
I got several of the issues fixed today:
* sdcard in twrp.
* recents crashing systemui.
* vendor mismatch warning.
The last two had already been fixed, but my local sources were out of sync.
I'll do another build tomorrow with the above.
Worked on fingerprint sensor most of the day today. It's proving to be a major pain, just like the camera.
tdm said:
I got several of the issues fixed today:
I'll do another build tomorrow with the above.
Click to expand...
Click to collapse
Dang, I was hoping you would do a build today! I've really been itching for some Oreo!
New builds are up.
TWRP r2 has the sdcard fix. Note that I've been building with toybox instead of busybox. This seems to work fine, except for one thing: gapps install and persistence requires data to be decrypted because it wants access to /data/local/tmp for temp files. I'll look into this and either fix it or switch back to busybox.
AOKP and Lineage 10/10 have both been uploaded. Recents button should work and vendor mismatch should be gone. I'm continuing to work on camera and fingerprint sensor.
Enjoy!
hey guys want to write this guide to show you steps and fixes to get Android 10 working good on our dead htc u11+ (working with both QuackPhh and Havoc releases from treble project)
1. flash stock PIE rom, you can find it here: https://androidfilehost.com/?w=search&s=2Q4DIMG you must flash it from download mode by placing the .zip inside SD card after preparing it with RUU Decryption Tool.
2. install TWRP (this version: https://github.com/sabpprook/androi...es/download/0.0.1/twrp-3.3.1-0-ocm_190501.img ) with fastboot using this command: fastboot flash recovery XXX.img (where XXX.img is name of twrp image you just downloaded)
3. inside TWRP wipe data, system, dalvik cache
4. download Havoc 3.5 rom here: https://sourceforge.net/projects/ha...ficial-arm64-aonly-gapps-nosu.img.xz/download (if you want to choose another rom you can, just check is variant ARM64 A-Only) then place it on SD card and flash from TWRP (don't reboot)
5. download PhhMagisk here: https://drive.google.com/file/d/1ZgYuaN-sklg0ycDue08WtKsMFmzWsI6F/view (standard magisk won't work) then place it on SD card and flash from TWRP (don't reboot)
6. inside TWRP go to wipe -> system -> resize file system (do this 2 times as at first try you will get error)
7. reboot
8. rom is now booting and working.
FIXES:
-for better camera quality i suggest you to download this GCam version: https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.7-fix.apk and then go to Phh Treble Settings -> Qualcomm features and tick Use alternate camera profile (this will make phone recording video at correct quality 1080p/4k)
-to make earpiece audio during call and bluetooth multimedia audio working you must place the 3 files included in htc_audio_bt_fix.rar i attached inside /root/vendor/etc and be sure to set permissions properly (look how permissions are set in original files before replacing, you can use Root Explorer or any other file browser with root support that allow to check and edit permissions) then you must disable from the paired bluetooth device Call Audio
now you have a working android 10 htc u11+ :victory::victory: i am using it as daily rom... you will love android 10!
only bugs i faced at the moment are:
- bluetooth audio not working with calls
- some rare freezes after unlocking phone from lockscreen
I keep getting stuck on ROM loading screen, I try reflashing the havoc os system image, then PhhMagisk, but still no luck!
I had to follow this guide all the way from the start and got the phone to boot, but once I copied the htc_audio_bt_fix.rar files to /vendor/etc/ and edited its permissions and rebooted the phone and stuck at the loading screen all over again :/
Now I have the phone running but no luck with any sound on my bluetooth earphones
I have placed the rar files as stated and the permissions are exactly as the files before had them rw--r--r, for all 3 of them.
Does the quack build support Bluetooth audio calls? I don't want to go back to pie, anyone know a working GSI Android 10 for the U11+ with BT call support?
Slok 00 said:
hey guys want to write this guide to show you steps and fixes to get Android 10 working good on our dead htc u11+ (working with both QuackPhh and Havoc releases from treble project)
1. flash stock PIE rom, you can find it here: https://androidfilehost.com/?w=search&s=2Q4DIMG you must flash it from download mode by placing the .zip inside SD card after preparing it with RUU Decryption Tool.
2. install TWRP (this version: https://github.com/sabpprook/androi...es/download/0.0.1/twrp-3.3.1-0-ocm_190501.img ) with fastboot using this command: fastboot flash recovery XXX.img (where XXX.img is name of twrp image you just downloaded)
3. inside TWRP wipe data, system, dalvik cache
4. download Havoc 3.5 rom here: https://sourceforge.net/projects/ha...ficial-arm64-aonly-gapps-nosu.img.xz/download (if you want to choose another rom you can, just check is variant ARM64 A-Only) then place it on SD card and flash from TWRP (don't reboot)
5. download PhhMagisk here: https://drive.google.com/file/d/1ZgYuaN-sklg0ycDue08WtKsMFmzWsI6F/view (standard magisk won't work) then place it on SD card and flash from TWRP (don't reboot)
6. inside TWRP go to wipe -> system -> resize file system (do this 2 times as at first try you will get error)
7. reboot
8. rom is now booting and working.
FIXES:
-for better camera quality i suggest you to download this GCam version: https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.7-fix.apk and then go to Phh Treble Settings -> Qualcomm features and tick Use alternate camera profile (this will make phone recording video at correct quality 1080p/4k)
-to make earpiece audio during call and bluetooth multimedia audio working you must place the 3 files included in htc_audio_bt_fix.rar i attached inside /root/vendor/etc and be sure to set permissions properly (look how permissions are set in original files before replacing, you can use Root Explorer or any other file browser with root support that allow to check and edit permissions) then you must disable from the paired bluetooth device Call Audio
now you have a working android 10 htc u11+ :victory::victory: i am using it as daily rom... you will love android 10!
only bugs i faced at the moment are:
- bluetooth audio not working with calls
- some rare freezes after unlocking phone from lockscreen
Click to expand...
Click to collapse
So I have asked at the relevant threads regarding any word on when a bluetooth fix should be expected, but do you by any chance have any idea about that?
Because I have to decide whether to wait (if the fix maybe right around the corner or smth) or revert back to a stable pie build.
usmantahir said:
So I have asked at the relevant threads regarding any word on when a bluetooth fix should be expected, but do you by any chance have any idea about that?
Because I have to decide whether to wait (if the fix maybe right around the corner or smth) or revert back to a stable pie build.
Click to expand...
Click to collapse
unfortunately bt call audio isn't working atm only multimedia audio works... try playing with bluetooth workaround option inside treeble settings-> misc but i don't know if you will solve it
Slok 00 said:
unfortunately bt call audio isn't working atm only multimedia audio works... try playing with bluetooth workaround option inside treeble settings-> misc but i don't know if you will solve it
Click to expand...
Click to collapse
That's a bummer, I guess I'll revert to pie, i tried flashing Havoc (pie) to my phone for a change, it just wont flash. Error 255. It's been a day of disappointments :crying:
usmantahir said:
That's a bummer, I guess I'll revert to pie, i tried flashing Havoc (pie) to my phone for a change, it just wont flash. Error 255. It's been a day of disappointments :crying:
Click to expand...
Click to collapse
man i am using havoc 3.5 and i am loving it, far better than pie htc rom that is too old now
Slok 00 said:
man i am using havoc 3.5 and i am loving it, far better than pie htc rom that is too old now
Click to expand...
Click to collapse
It really is great! Too bad about the Bluetooth bug! I spend hours on-call, and I just cant go back to holding my phone to my ear :/
usmantahir said:
It really is great! Too bad about the Bluetooth bug! I spend hours on-call, and I just cant go back to holding my phone to my ear :/
Click to expand...
Click to collapse
yes i got your point, try contact phhusson (quack phh creator) is a very good guy maybe it can help you
Slok 00 said:
yes i got your point, try contact phhusson (quack phh creator) is a very good guy maybe it can help you
Click to expand...
Click to collapse
Great idea! I'll find him and hit him up. I'll post here and let you guys know if it works for me.
Hey, this is great news for me, but there's one, very important question - is there a way to use Edge Sense with this? I've seen some Magisk module re-activating the analogue feature on modded Pixels, but I haven't seen anything like that for HTC - could that work? I use Edge Sense regularly and losing it would stop me from any modding.
I downloaded the stock PIE rom from the URL provided by you, and decrypt it by RUU Decryption Tool. And now I got some img files inside two folders - firmware and system.
But then how to convert them into zip file so that I can place it inside SD card? Can you tell me in details? Sorry I'm a newbie in flashing roms.
openopentw said:
I downloaded the stock PIE rom from the URL provided by you, and decrypt it by RUU Decryption Tool. And now I got some img files inside two folders - firmware and system.
But then how to convert them into zip file so that I can place it inside SD card? Can you tell me in details? Sorry I'm a newbie in flashing roms.
Click to expand...
Click to collapse
I flashed the boot.img and system.img by fastboot into my phone instead of placing some zip into SD card, and followed the remaining steps including fixes. Now my phone is working!
However my phone can not recognize if I have plugged in the earphone or not, and of course no sound from earphone. Do you guys have any suggestions about it? Maybe I should flashed vendor.img in the first step as well?
openopentw said:
I flashed the boot.img and system.img by fastboot into my phone instead of placing some zip into SD card, and followed the remaining steps including fixes. Now my phone is working!
However my phone can not recognize if I have plugged in the earphone or not, and of course no sound from earphone. Do you guys have any suggestions about it? Maybe I should flashed vendor.img in the first step as well?
Click to expand...
Click to collapse
Flashing the vendor.img would change nothing, it is the same as it was before. The fix for earphone audio has been in the post for a long time, but there is no fix for using earphones/headphones.
Did you find the earpiece speaker fix?
---------- Post added at 03:52 PM ---------- Previous post was at 03:46 PM ----------
This is incredible, I've been following phhuson's Treble GSI development for 2 years now hoping that someone would find a fix for the earpiece speaker during calls.
I tried doing everything at once and got a bootloop, but then I tried every step separately and after a few days my U11+ is working great!
How long did it take you to find that GCam port? I've been using Arnova's for ages and could never find a good one for the U11+ before trying the one you've linked.
I'm really glad we got the earpiece fix, the U11+ still has really great hardware and the poorly made Android Pie port and old security patch was tempting me to upgrade to something new. Now I think I can hold onto it for an extra year.
My camera doesn't work...
After enable "Use alternate camera profile" then reboot , it still not working....
Is there any solution?
Please help me , camera is really important to me...
Pineapplemilk said:
My camera doesn't work...
After enable "Use alternate camera profile" then reboot , it still not working....
Is there any solution?
Please help me , camera is really important to me...
Click to expand...
Click to collapse
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
---------- Post added at 10:51 PM ---------- Previous post was at 10:41 PM ----------
Here is the way to use Edge Sense with Havoc OS.
1. Install com.htc.sense.edgesensorservice.apk (Resigned with Havoc OS keystore)
2. Install App Systemizer in Magisk
3. Systemize EdgeSensorService
4. Reboot
Now Edge Sense work fine.
And if you want to setup Edge Sense, open terminal
Code:
su
am start com.htc.sense.edgesensorservice/.ui.SettingsMainActivity
Recommended to use Edge Sense Plus to manage it so you don't need to setup in this dirty(?) way every time.
james35022000 said:
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
Click to expand...
Click to collapse
I flashed 2.15.709.1 Pie Ruu before install the "Phh AOSP Android 10"
(Havoc based on Phh)
TWRP Version : 190501
And it still can't encrypt data
Pineapplemilk said:
I flashed 2.15.709.1 Pie Ruu before install the "Phh AOSP Android 10"
(Havoc based on Phh)
TWRP Version : 190501
And it still can't encrypt data
Click to expand...
Click to collapse
Oh TWRP can't decrypt data is normal.
The thing you can do is to prevent system from encrypting data.
This thread:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Just wipe data in TWRP and flash the zip file upon
---------------------------------------------------------------------
And wait, I see XDDD
I flashed Phh AOSP before, the camera don't work neither.
You can find the issue on the Phh's github, it seems never work and no fix for our device.
So....please use Havoc OS
james35022000 said:
Oh TWRP can't decrypt data is normal.
The thing you can do is to prevent system from encrypting data.
This thread:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Just wipe data in TWRP and flash the zip file upon
Click to expand...
Click to collapse
Thank you for this information :good:
---------------------------------------------------------------------
james35022000 said:
And wait, I see XDDD
I flashed Phh AOSP before, the camera don't work neither.
You can find the issue on the Phh's github, it seems never work and no fix for our device.
So....please use Havoc OS
Click to expand...
Click to collapse
Really strange.....
Thank you for the information again~
Does Havoc os running smooth on U11+?
Phh AOSP has some bugs but it's smooth tho.
Pineapplemilk said:
Does Havoc os running smooth on U11+?
Phh AOSP has some bugs but it's smooth tho.
Click to expand...
Click to collapse
It runs smooth for me, but for the first week I kept crashing at the lock screen randomly and had to do a reset. Sometimes a normal reset would just bootloop or crash on the lockscreen again. So I had to specifically go into download mode -> bootloader mode -> recovery mode (TWRP) -> "reboot to system" which would let me get past the lockscreen without crashing.
The battery life and thermal performance is MUCH better, it's too early for me to say but I think it's pretty close to Oreo battery life and heat management might be EVEN BETTER.
I still think that HTC Oreo was smoother, but most phones weren't as smooth as the U11+ on Oreo.
The camera performance is definitely worse though, that could just be because we're forced to use the GCam port instead of the stock HTC app but it's inconsistent with lighting and sometimes crushes black levels on people's faces too much. If I find improved settings or a better GCam port then I'll link it here for you guys to use
I'm pretty sure that TWRP not being able to decrypt data is a bug with that specific version of TWRP, but I don't think there's another TWRP image that will work on the U11+ so we have to deal with it.
---------- Post added at 07:24 PM ---------- Previous post was at 07:12 PM ----------
james35022000 said:
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
---------- Post added at 10:51 PM ---------- Previous post was at 10:41 PM ----------
Here is the way to use Edge Sense with Havoc OS.
1. Install com.htc.sense.edgesensorservice.apk (Resigned with Havoc OS keystore)
2. Install App Systemizer in Magisk
3. Systemize EdgeSensorService
4. Reboot
Now Edge Sense work fine.
And if you want to setup Edge Sense, open terminal
Code:
su
am start com.htc.sense.edgesensorservice/.ui.SettingsMainActivity
Recommended to use Edge Sense Plus to manage it so you don't need to setup in this dirty(?) way every time.
Click to expand...
Click to collapse
How do you do step 1? I couldn't find any information about where to find the HavocOS Keystore or what it is? I assume it's an app to resign APKs for HavocOS?
Thanks for helping an ignorant person like me