Related
Hello everyone. I have gotton permission from @jholtom to re-open this thread and start building it on my own (we are never alone ). He will still be here and will still be helping. All credit goes to him, he got this off the ground for the LS990. I'm just here to take over the saddle. Enjoy!
[ROM][Q&A] CM12 Questions and General Thread
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.<br />
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Kernel Source: https://github.com/CyanogenMod/android_kernel_lge_g3
Click to expand...
Click to collapse
Yup. It's finally here. CM12.1 with basically everything* working.
*Working:
Pretty much everything:
WiFi
3G/LTE
Camera (back and front-facing and LED flash,) camcorder works in 1080p, no 4k yet
Sound
Screen (duh)
Proximity, Accelerometer, Gyroscope
GPS
Partial Bluetooth support (FitBit and some other devices not working yet)
SDCard read/write
SMS/MMS
NFC - Yes NFC works now, but needs testing
*Not working:
EVDO Rev. A has some issues with out a patch (its cooked into the unofficial rom already)
CM-12.1 reports of DATA not working, but its working for some Its mostly fixed in 4/23 build, please use ZV8 modem
Installation Instructions:
*NOTE*: You must be Bump'd for this to work. This requires flashing via custom recovery
1. Download this and 5.1 GApps (recommended PA GApps Here. You are going to need to use the Lollipop ones, this is 5.1)
2. Put both on Internal Storage
3. Reboot into recovery
4. BACKUP CURRENT ROM
5. Factory Reset/Wipe if not on CM12, you CAN dirty flash cm12.1 over cm12
6. Flash CM12.1 (no need to wipe System)
7. Flash GApps 5.1
(Optional: flash SuperSU Lollipop Edition for Root. Download here)
8. Reboot
9. wait.. wait ..wait
10. Profit
To get root/SU, enable Developer Options and change "Root Access" options.
Downloads
Official CM Nightly Builds HERE
Latest Unofficial Builds: 7/21/15
Hrubak's Builds Download from MEGA
Mirror: Hrubak's Builds Download from AFH
K0nane Server Links:
Repositories are at github.com/jholtom
Kernel sources are at github.com/invisiblek/android_kernel_lge_g3
Using Cyanogenmod Repositories
@invisiblek was pretty awesome in getting this going, much more credit goes to him than me, he really had the base for this, and now I just fix crap for the ls990.
@Berzerker7 @jholtom, shoutout because I stole your thread body.
XDA:DevDB Information
CyanogenMOD 12.1, ROM for the Sprint LG G3
Contributors
clark44, Hrubak, RandomPooka, invisiblek, jholtom, Shelnutt2
Source Code: https://github.com/cyanogenmod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Nightly
Beta Release Date: 2015-06-23
Created 2014-11-30
Last Updated 2015-07-21
So awesome to see this! Thanks mass for taking over. Encouraging.
Good work, unfortunately I cannot get any data or network connection. WiFi works great however
It looks like Bluetooth is struck out so I'm not sure if it's working here or not but if it isn't RandomPooka has the fix for it.
YYYYEEEESSSSS!!! My pants are soaked
Welcome back good to see you taking the reins
Sent from my LGLS990 using Tapatalk
Not data connection only wifi
crazycori said:
Good work, unfortunately I cannot get any data or network connection. WiFi works great however
Click to expand...
Click to collapse
Same here
clark44 said:
Hello everyone. I have gotton permission from @jholtom to re-open this thread and start building it on my own. He will still be here and will still be helping. All credit goes to him, he got this off the ground for the LS990. I'm just here to take over the saddle. Enjoy!
<b><font color="Red">Beta is here, go try it</font></b><br />
<br />
<br />
Yup. It's finally here. CM12 with basically everything* working.<br />
<br />
*Working:<br />
Pretty much everything:<br />
WiFi (Reports of 5Ghz being broken)<br />
2G/3G/LTE<br />
Camera (back and front-facing and LED flash, no 4K recording as it's not in CM yet) (new issues with camera connection error, and quality)<br />
Sound (little bit quiet)<br />
Screen (duh)<br />
Proximity, Accelerometer, Gyroscope<br />
SDCard read/write<br />
GPS (can drain battery really fast)<br />
<br />
*Not working:<br />
Wireless Charging (it works but it's very, very slow)<br />
Bluetooth - (All of it)<br />
NFC - (Might be a battery killer in current state, uninstall or freeze it in TiBu)<br />
<br />
<br />
Installation Instructions:<br />
*NOTE*: You must be Bump'd for this to work. This requires flashing via custom recovery.<br />
1. Download this and GApps (recommended PA GApps here You are going to need to use the Lollipop ones, this is 5.0)<br />
2. Put both on Internal Storage<br />
3. Reboot into recovery<br />
4. BACKUP CURRENT ROM<br />
5. Factory Reset/Wipe<br />
6. Flash CM12 (no need to wipe System)<br />
7. Flash GApps<br />
(Optional: flash SuperSU Lollipop Edition for Root. Download here)<br />
8. Reboot<br />
9. ???<br />
10. Profit<br />
<br />
<b>Downloads </b><br />
<br />
K0nane Server Links:
11/30 Build<br />
<br />
Repositories are at github.com/jholtom<br />
Kernel sources are at github.com/invisiblek/android_kernel_lge_g3<br />
<br />
@invisiblek was pretty awesome in getting this going, much more credit goes to him than me, he really had the base for this, and now I just fix crap for the ls990.<br />
<br />
@Berzerker7 @jholtom, shoutout because I stole your thread body.<br />
XDA:DevDB Information
CyanogenMOD 12, ROM for the Sprint LG G3
Contributors
clark44, jholtom, invisiblek
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 11/30
Beta Release Date: 2014-11-30
Created 2014-11-30
Last Updated 2014-11-30
Click to expand...
Click to collapse
Do we have an official change log or support forum made?
Sent from my LGLS990 using Tapatalk
awesome glad you're working on it!
Nice job @clark44 thanks for this
Can anyone confirm bluetooth is working? I would so use yhis as my daily driver, but previous builds with no bluetooth have made my G Watch a vegetable lol so Ive been going back and forth between CM12 and stock. If theres a fix like mentioned above, could someone post a link? I cant seem to find it.
Anyone having trouble connecting to their network? It connect for me when first booted but loses all signal after a few seconds
Cleanser2012 said:
Anyone having trouble connecting to their network? It connect for me when first booted but loses all signal after a few seconds
Click to expand...
Click to collapse
Yes
Bluetooth isnt working for me but wifi seems to be fine.
Yeah I second the sprint network not working. It gets roaming signal but not sprint signal. Also its not recognizing my SD card. Anyone else notice this?
Bluetooth works for me GPS is way off tho
Sent from my LGLS990 using Tapatalk
randyrampage609 said:
Bluetooth works for me GPS is way off tho
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Did u wipe data before flashing because I didnt
Cjay1518 said:
Did u wipe data before flashing because I didnt
Click to expand...
Click to collapse
Did normal wipe
Sent from my LGLS990 using Tapatalk
Is anyone able to get android wear to connect?
It's not working for me.
I didn't wipe system and able to get data
For those that don't know what Evervolv is, Evervolv is an AOSP (Android Open Source Project) rom aimed at Snapdragon powered devices. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
If you would like to contribute to Evervolv, please visit our Gerrit Code Review.
Current version: Based off 6.0.1 Marshmallow)
Features:
Extended PowerMenu
Battery %,
Volume button music control.
Trackball Wake (Available on devices with a trackball/pad)
CM Theme manager
ability to turn all customization off with one switch in the toolbox, giving you 100% aosp look and feel.
eng builds (instead of userdebug like everyone else) providing more open experience (ie adb root by default)
full complement of commandline tools (busybox, vim, ssh, curl/wet with ssl support!)
custom updater written from scratch by Preludedrew and Texasice, featuring automatic update checks,
support for downloading gapps, and advanced automatic install (TWRP and CWM supported but TWRP preferred)
Bug Reporting:
Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use EVPaste to post your logs.
Downloads:
7-4 Build
Source:
Evervolv Github
Device Tree
Tab A common tree
MSM8916-common tree
Kernel Source
Changelog:
View the recent changes at Evervolv Gerrit
Donations:
If you wish to donate please do so here (Paypal)
What's working:
Touchscreen
Power, Home, Recents, Back buttons
Wifi
Bluetooth
Camera
Sensors
GPS
Storage's (internal, external, adoptable storage)
Bugs/Not Working:
Initial setup takes a while to initialize
Audio
Video/DRM
Offline charging
Playstore downloads old app versions
How to flash a Rom properly?
Make sure you are using Lollipop Firmware or your touch will be flipped we are activily working on supporting the Marshmallow firmware
Copy the rom and gapps to your tablet
Boot into your custom recovery
OPTIONAL make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop
Wipe dalvik cache
Wipe/format system
Wipe/format data
Flash rom
Flash gapps
Reboot and give your device some time to do it's first boot!
In case someone likes to compile on their own:
You need to setup Linux first, good tutorial here:
Ubuntu / Xubuntu:
- https://nathanpfry.com/how-to-prepar...-android-roms/
- https://nathanpfry.com/how-to-setup-...-android-roms/
- https://nathanpfry.com/how-to-set-up...-android-roms/
- https://nathanpfry.com/how-to-setup-...-android-roms/
Arch based Linux ready to go:
- BBQLinux by @codeworkx http://bbqlinux.org/
Once you have synced Evervolv source run the following in terminal:
Code:
mkdir -p .repo/local_manifests
nano .repo/local_manifests/local_manifest.xml
Add the following to your local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
-<manifest>
<project revision="mm-6.0" remote="github" path="vendor/samsung" name="Evervolv/android_vendor_samsung"/>
<project revision="mm-6.0" remote="github" path="hardware/samsung" name="Evervolv/android_hardware_samsung"/>
<project revision="mm-6.0" remote="github" path="kernel/samsung/msm8916" name="Evervolv/android_kernel_samsung_msm8916"/>
<project revision="mm-6.0" remote="github" path="device/samsung/qcom-common" name="Evervolv/android_device_samsung_qcom-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/msm8916-common" name="Evervolv/android_device_samsung_msm8916-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt5-common" name="Evervolv/android_device_samsung_gt5-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt510wifixx" name="Evervolv/android_device_samsung_gt510wifixx"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt58wifixx" name="Evervolv/android_device_samsung_gt58wifixx"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/audio-caf/msm8916" name="Evervolv/android_hardware_qcom_audio-caf"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/display-caf/msm8916" name="Evervolv/android_hardware_qcom_display-caf"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/media-caf/msm8916" name="Evervolv/android_hardware_qcom_media-caf"/>
<project revision="mm-6.0-caf" remote="github" path="hardware/qcom/bt-caf" name="Evervolv/android_hardware_qcom_bt"/>
<project revision="mm-6.0-caf" remote="github" path="hardware/qcom/wlan-caf" name="Evervolv/android_hardware_qcom_wlan"/>
</manifest>
Save the file.
Back in terminal:
Code:
repo sync
. build/envsetup.sh
lunch gt510wifixx
make otapackage
(you can replace gt510wifixx with gt58wifixx if you like to build for the Galaxy Tab A 8.0 WIFI (SM-T350)
Great work man, happily waiting for lte support to get this great cheap tab bloadware-free:highfive:
Hello, this ROM is also compatible with the version Galaxy Tab A SM-T550? Thank y
pickmod said:
Hello, this ROM is also compatible with the version Galaxy Tab A SM-T550? Thank y
Click to expand...
Click to collapse
Umm not trying to sound like a jerk here but doesn't the title of the thread say it's for the Samsung Tab SM-T550?
---------- Post added at 18:02 ---------- Previous post was at 18:00 ----------
What about the Samsung Tab A 8.0 (SM-T350)? Will it work? Would love to flash it. ?
alias4ever said:
Umm not trying to sound like a jerk here but doesn't the title of the thread say it's for the Samsung Tab SM-T550?
---------- Post added at 18:02 ---------- Previous post was at 18:00 ----------
What about the Samsung Tab A 8.0 (SM-T350)? Will it work? Would love to flash it.
Click to expand...
Click to collapse
have a look here
http://forum.xda-developers.com/andr...-t350-t3411150
@deadman96385:
First of all many apreciate for your hard work, you didn`t give up just like me^^
Will it be possible to compile pure cm with your repos?
Just saw that you updated the branches...
Will both Galaxy-Tab-A and Evervolv repos be updated?
Maybe you can add a how-to of flash for some new users just like that: https://andi34.github.io/faq.html
And some additional informations later like here :http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
Thanks @Android-Andi
This is not meant to be some kind of criticism, just wanna support this device thread
alias4ever said:
What about the Samsung Tab A 8.0 (SM-T350)? Will it work? Would love to flash it.
Click to expand...
Click to collapse
Here is Evervolv for the T350
http://forum.xda-developers.com/android/development/rom-evervolv-galaxy-tab-sm-t350-t3411150
Chemnitzer said:
have a look here
http://forum.xda-developers.com/andr...-t350-t3411150
@deadman96385:
First of all many apreciate for your hard work, you didn`t give up just like me^^
Will it be possible to compile pure cm with your repos?
Just saw that you updated the branches...
Will both Galaxy-Tab-A and Evervolv repos be updated?
Maybe you can add a how-to of flash for some new users just like that: https://andi34.github.io/faq.html
And some additional informations later like here :http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
Thanks @Android-Andi
This is not meant to be some kind of criticism, just wanna support this device thread
Click to expand...
Click to collapse
It should be possible to build cm with the repos but i have not tried it yet, the Galaxy-Tab-A org will be were i test things out and once its stable it will be merged on to the Evervolv repos. I will add some of the info you mentioned
Edit: 3rd post now has install instructions and a compile guide
deadman96385 said:
Here is Evervolv for the T350
http://forum.xda-developers.com/android/development/rom-evervolv-galaxy-tab-sm-t350-t3411150
It should be possible to build cm with the repos but i have not tried it yet, the Galaxy-Tab-A org will be were i test things out and once its stable it will be merged on to the Evervolv repos. I will add some of the info you mentioned
Click to expand...
Click to collapse
Just figured that some of your source links are not working
Chemnitzer said:
Just figured that some of your source links are not working
Click to expand...
Click to collapse
Fixed there was an extra " on a couple of them
Very cool, hope you support tgphe LTE version soon.
Gesendet von meinem SM-T555 mit Tapatalk
Blindie said:
Very cool, hope you support tgphe LTE version soon.
Gesendet von meinem SM-T555 mit Tapatalk
Click to expand...
Click to collapse
Will be added by deadman in time, have Seen it in beta repo already so work is in progress:victory:
omfg finally someone did it! thank you so much!
---------- Post added at 10:42 PM ---------- Previous post was at 10:10 PM ----------
Just found a bug: the touch is upside down. i think it is due to the new marshmallow bootloader, because ashyx had the same problem with the twrp recovery
hellcat50 said:
omfg finally someone did it! thank you so much!
---------- Post added at 10:42 PM ---------- Previous post was at 10:10 PM ----------
Just found a bug: the touch is upside down. i think it is due to the new marshmallow bootloader, because ashyx had the same problem with the twrp recovery
Click to expand...
Click to collapse
Is it reversed in twrp/system/Both?
What twrp are you Using?
Made a clean Flash?
alias4ever said:
Umm not trying to sound like a jerk here but doesn't the title of the thread say it's for the Samsung Tab SM-T550?
---------- Post added at 18:02 ---------- Previous post was at 18:00 ----------
What about the Samsung Tab A 8.0 (SM-T350)? Will it work? Would love to flash it.
Click to expand...
Click to collapse
I'm so sorry! I meant if it is compatible with the version Tab A SM-P500 ?!?! Thank you!
pickmod said:
I'm so sorry! I meant if it is compatible with the version Tab A SM-P500 ?!?! Thank you!
Click to expand...
Click to collapse
I doubt it is compatible with P500 but it is worth a shot
Chemnitzer said:
Is it reversed in twrp/system/Both?
What twrp are you Using?
Made a clean Flash?
Click to expand...
Click to collapse
No, ashyx fixed it in the recovery. Before the fix the same was present in the twrp
I'm using twrp 3.0.2.1
hellcat50 said:
No, ashyx fixed it in the recovery. Before the fix the same was present in the twrp
I'm using twrp 3.0.2.1
Click to expand...
Click to collapse
Chemnitzer said:
Is it reversed in twrp/system/Both?
What twrp are you Using?
Made a clean Flash?
Click to expand...
Click to collapse
You are correct currently you need to have lollipop firmware installed we our actively working on the kernel to support the M firmware. I have also added a note in the install instructions about it.
deadman96385 said:
You are correct currently you need to have lollipop firmware installed we our actively working on the kernel to support the M firmware. I have also added a note in the install instructions about it.
Click to expand...
Click to collapse
Can I downgrade the firmware without bricking the device?
And what about the bootloader?
nevermind, downgraded and now the touch works. hopefully the other existing issues will be fixed soon
Just found another issue: the rotation doesn't work after sometime using the tablet. After a reboot it's working again until it stops working again.
For those that don't know what Evervolv is, Evervolv is an AOSP (Android Open Source Project) rom aimed at Snapdragon powered devices. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
If you would like to contribute to Evervolv, please visit our Gerrit Code Review.
Current version: Based off 6.0.1 Marshmallow)
Features:
Extended PowerMenu
Battery %,
Volume button music control.
Trackball Wake (Available on devices with a trackball/pad)
CM Theme manager
ability to turn all customization off with one switch in the toolbox, giving you 100% aosp look and feel.
eng builds (instead of userdebug like everyone else) providing more open experience (ie adb root by default)
full complement of commandline tools (busybox, vim, ssh, curl/wet with ssl support!)
custom updater written from scratch by Preludedrew and Texasice, featuring automatic update checks,
support for downloading gapps, and advanced automatic install (TWRP and CWM supported but TWRP preferred)
Bug Reporting:
Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use EVPaste to post your logs.
Downloads:
7-9 Build
Source:
Evervolv Github
Device Tree
Tab A common tree
MSM8916-common tree
Kernel Source
Changelog:
View the recent changes at Evervolv Gerrit
What's working:
Touchscreen
Power, Home, Recents, Back buttons
Wifi
Bluetooth
Sensors
GPS
Storage's (internal, external, adoptable storage)
Bugs/Not Working:
Mobile Data/Calling/Messagaing
Initial setup takes a while to initialize
Audio
Video/DRM
Camera
Offline charging
Playstore downloads old app versions
How to flash a Rom properly?
Make sure you are using Lollipop Firmware or your touch will be flipped we are activily working on supporting the Marshmallow firmware
Copy the rom and gapps to your tablet
Boot into your custom recovery
OPTIONAL make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop
Wipe dalvik cache
Wipe/format system
Wipe/format data
Flash rom
Flash gapps
Reboot and give your device some time to do it's first boot!
In case someone likes to compile on their own:
You need to setup Linux first, good tutorial here:
Ubuntu / Xubuntu:
- https://nathanpfry.com/how-to-prepar...-android-roms/
- https://nathanpfry.com/how-to-setup-...-android-roms/
- https://nathanpfry.com/how-to-set-up...-android-roms/
- https://nathanpfry.com/how-to-setup-...-android-roms/
Arch based Linux ready to go:
- BBQLinux by @codeworkx http://bbqlinux.org/
Once you have synced Evervolv source run the following in terminal:
Code:
mkdir -p .repo/local_manifests
nano .repo/local_manifests/local_manifest.xml
Add the following to your local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
-<manifest>
<project revision="mm-6.0" remote="github" path="vendor/samsung" name="Evervolv/android_vendor_samsung"/>
<project revision="mm-6.0" remote="github" path="hardware/samsung" name="Evervolv/android_hardware_samsung"/>
<project revision="mm-6.0" remote="github" path="kernel/samsung/msm8916" name="Evervolv/android_kernel_samsung_msm8916"/>
<project revision="mm-6.0" remote="github" path="device/samsung/qcom-common" name="Evervolv/android_device_samsung_qcom-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/msm8916-common" name="Evervolv/android_device_samsung_msm8916-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt5-common" name="Evervolv/android_device_samsung_gt5-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt510ltexx" name="Galaxy-Tab-A/android_device_samsung_gt510ltexx"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt510wifixx" name="Evervolv/android_device_samsung_gt510wifixx"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt58wifixx" name="Evervolv/android_device_samsung_gt58wifixx"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/audio-caf/msm8916" name="Evervolv/android_hardware_qcom_audio-caf"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/display-caf/msm8916" name="Evervolv/android_hardware_qcom_display-caf"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/media-caf/msm8916" name="Evervolv/android_hardware_qcom_media-caf"/>
<project revision="mm-6.0-caf" remote="github" path="hardware/qcom/bt-caf" name="Evervolv/android_hardware_qcom_bt"/>
<project revision="mm-6.0-caf" remote="github" path="hardware/qcom/wlan-caf" name="Evervolv/android_hardware_qcom_wlan"/>
</manifest>
Save the file.
Back in terminal:
Code:
repo sync
. build/envsetup.sh
lunch gt510ltexx
make otapackage
Great Work for this!
Any plans for CM-13.0?
Chemnitzer said:
Great Work for this!
Any plans for CM-13.0?
Click to expand...
Click to collapse
Once the bugs are worked out i will work on cm-13.0
deadman96385 said:
Once the bugs are worked out i will work on cm-13.0
Click to expand...
Click to collapse
"Evervolv/android_device_samsung_gt510ltexx" is missing on github
Chemnitzer said:
"Evervolv/android_device_samsung_gt510ltexx" is missing on github
Click to expand...
Click to collapse
Fixed sorry about that its currently on my Galaxy Tab A org for now https://github.com/Galaxy-Tab-A/android_device_samsung_gt510ltexx
Auto standby is not working. In stock Rom, display goes of when LiD of cover is closed and goes back on when LiD is lifted.
Good job!
Thanks for this!:highfive:
Chemnitzer said:
Auto standby is not working. In stock Rom, display goes of when LiD of cover is closed and goes back on when LiD is lifted.
Click to expand...
Click to collapse
It is on the to-do list i will add a few potential fixes that might fix it, but i do not currently have a smart cover yet.
Hello! First I want to thank you for your work! I just installed the Rom, but not just opened, it stays hanging around with the sign Evervolv, screen saying that you are loading applications and then again Evervolv and so I get an hour without change. That may be, as I fix it? Thank you!
dodka said:
Hello! First I want to thank you for your work! I just installed the Rom, but not just opened, it stays hanging around with the sign Evervolv, screen saying that you are loading applications and then again Evervolv and so I get an hour without change. That may be, as I fix it? Thank you!
Click to expand...
Click to collapse
You made a clean flash?
Are you running latest twrp?
Sorry for Late reply
Chemnitzer said:
You made a clean flash?
Are you running latest twrp?
Sorry for Late reply
Click to expand...
Click to collapse
Yes, i made clean flash and i have instaled latest TWRP.
dodka said:
Yes, i made clean flash and i have instaled latest TWRP.
Click to expand...
Click to collapse
Which Version?
I use latest from ashyx and no issue like that
https://www.androidfilehost.com/?fid=24499762635999217
Also make an advanced wipe, not only factory reset
After wipe, you shouldt directly reboot into recovery and allow modifications.
Last, install Both ROM and Recovery WITHOUT Reboot
You surely own a sm-t555/ GT510LTE? (only to be sure)
I managed to install the Rom, but can not find the gapps. From where I have to download? Thank you!
dodka said:
I managed to install the Rom, but can not find the gapps. From where I have to download? Thank you!
Click to expand...
Click to collapse
http://opengapps.org/
You need arm version for android 6.0 in whatever variant you prefer.
Remember to install gapps together with rom BEFORE Reboot and First Boot of ROM
@deadman96385
Hows the progress on Rom?
Best let people work in peace, I'm sure they are progressing and will soon have another update of this interesting Rom.
I have managed to fork deadmans device tree to cm-13.0 for gt510lte.
If somebody is interrested in just pm me.
I will not start an own thread for this until it is proper booting.
Any support is welcome
any members interested in cm development may check my forum: http://forum.xda-developers.com/and...-t550-t555-t3449597/post68407172#post68407172
What's up guys, even though this Nexus 4 is 4 years old, (pun not intended XD) it's still holding up strong and in time for some Nougat treatment. [emoji14]
Note: Most of the components are working and I believe that it is enough for daily tasks. However, YOU see whether it fits your needs or not.
Working:
- Audio
- Wi-Fi
- Bluetooth
- RIL
- H/W Acceleration
- USB
- GPS
- NFC
- Sensors
Semi-Working:
- Camera (Video recording stutters sometimes with some apps)
Not Working:
How to Flash:
1. Download Zip
2. Flash zip
3. Flash GApps
4. Wipe Data (If coming from anything other than 7.0)
4. Flash SuperSU (Optionnal, Uses systemless as a root method)
5. Profit
Note: You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings.
Download:
AOSP 7.0 download folder
Mirror
Quanta:
Quanta V19 Test
GApps:
OpenGApps
Banks GApps
SuperSU: SuperSU Stable
Sources:
Device Tree
Kernel Source
Changelog, other stuff
Code:
V10 (18/12/16):
- Updated to Android 7.1.1
- Patched kernel with the latest security fixes.
V9: (14/10/16)
- Video recording on Camera2 partially fixed (Video shakes sometimes)
- Fixed stack trace for native processes
- Updated to October's Security patches
- Misc fixes
V8: (18/09/16)
- Kernel patched accordingly to September security fixes (Patches all Quadrooter exploits up to now)
- Fixed Torch
V7: (11/09/16)
- Updated to September security fixes (For real this time)
- Enabled H/W encoding for video recording
- Re-enabled navigation bar tweaks and night mode in SystemUI
- Fixed Google Play Services FC's using OpenGApps (For real also)
- Add possibility to change WebView provider
V6: (09/09/16)
- Updated to September security patches
- Fixed freezing while watching YouTube
- Attempt to enable LTE
- Hidden misc battery drain as it causes some misinterpretations
V5: (05/09/16)
- Enabled Doze for real this time
- Reverted a change that may have broke Camera
V4: (02/09/16)
- Fixed H/W video decoding for the most part
- Kernel: SDCard FS enabled
- Attempt to fix permissions for GApps
- Enabled Navigation Bar tweaks and Night mode in SystemUI Tuner.
V3: (30/08/16)
- Fixed Sensors
- Semi-Fixed camera
- Fixed MPDecision
- Enabled Doze
- Used Flo's developper preview N GPU drivers
V2: (28/08/16)
- Fixed audio
- Fixed GPS
- Fixed data connectivity
- Disabled the power toggle widget which caused Settings to crash on every boot
V1 (26/08/16):
- Initial release
Here's a video showing how to install the ROM. (Thanks @Swapnil Soni)
Here's another one with a little overview of it. (Thanks @DaKoin)
Build instructions:
Since some of you guys asked me how to build from scratch, I will give a walkthrough of what I mostly did.
Note that this is in no way a walkthrough in how to compile (there are several guides for that on XDA) but more a guide
on how I did my setup so you can replicate the AOSP builds on your device.
Here's what I did:
1. Download the latest AOSP revision for android-7.1 which is r6 at the time of this writing (replace with whatever required branch necessary)
Code:
repo init -u https://android.googlesource.com/platform/manifest -b refs/tags/android-7.1.1_r6
repo sync
2. Download the kernel source used for the build:
Code:
git clone https://github.com/zaclimon/android_kernel_google_msm -b mako_nougat
3. Once both sources has been downloaded, compile the kernel. Note that AOSP do have a kernel toolchain that you can use to compile
Code:
export CROSS_COMPILE "/path/to/aosp/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-"
make mako_defconfig
make -j$(grep -c processor /proc/cpuinfo)
4. Copy the arch/arm/boot/zImage file to the Android source into device/lge/mako-kernel
Note: You must create the said directories if they don't exist. You also must rename the file to kernel after copy.
5. Go back to the AOSP source, and download/update/replace the following repositories for each component (relative path):
Code:
device/lge:
git clone https://github.com/zaclimon/android_device_lge_mako mako
hardware/qcom:
git clone https://github.com/zaclimon/android_hardware_qcom_audio audio
git clone https://github.com/zaclimon/android_hardware_qcom_display display
git clone https://github.com/zaclimon/android_hardware_qcom_gps gps
git clone https://github.com/zaclimon/android_hardware_qcom_media media
vendor:
git clone https://github.com/zaclimon/android_vendor_lge lge
6. Apply the following patches to each of their respective repositories:
Code:
bionic:
https://github.com/LineageOS/android_bionic/commit/81af26a3a033723fb34ddf280e33a9d4a6ce82c4.patch
frameworks/base:
https://gist.github.com/zaclimon/bb39d7f5059b63e3add3b5cad15e87db
https://android-review.googlesource.com/#/c/147266/
system/sepolicy:
https://github.com/LineageOS/android_system_sepolicy/commit/10dd0402ab62aa1a6416d7ea549a6a3eea1c6ae4.patch
7. Increase RAM usage for Jack (Only if you have 6/8GB of RAM in your system)
Code:
export ANDROID_JACK_VM_ARGS="-Xmx4g -Dfile.encoding=UTF-8 -XX:+TieredCompilation"
8. Once all the patches have been applied, we can now proceed to compile the system.
Code:
. build/envsetup.sh && lunch aosp_mako-userdebug
make -j$(grep -c processor /proc/cpuinfo) otapackage
9. The build should be in out/target/product/mako
10. Flash and enjoy!!
You're the king, buddy! ?
P.
[sntfrmnxs⁴]
first
oops, second
Thanks @zaclimon and BTW wiping data is needed?
Nitin
nitin.chobhe said:
first
Nitin
Click to expand...
Click to collapse
Ha ha ! Almost.
Sent from my Nexus 4 using Tapatalk
You're great!!
nitin.chobhe said:
first
oops, second
Thanks @zaclimon and BTW wiping data is needed?
Nitin
Click to expand...
Click to collapse
It's not necessary per se because it should boot fine. That said, as always, it's recommended to wipe so random issues are less prone to happen.
Merci infiniement !!!
Just downloaded, and works, I think we need to changes the permission so that google play service not crashing
Its people like you who make this world a better place, thank you very much!
zaclimon said:
It's not necessary per se because it should boot fine. That said, as always, it's recommended to wipe so random issues are less prone to happen.
Click to expand...
Click to collapse
Thanks man! One last question - I need N gapps for this, right?
Open gapps should be fine?
@cqloveqc what gapps did you use? And what permissions need to be modified?
Nitin
funthomasz said:
Its people like you who make this world a better place, thank you very much!
Click to expand...
Click to collapse
nitin.chobhe said:
Thanks man! One last question - I need N gapps for this, right?
Open gapps should be fine?
@cqloveqc what gapps did you use? And what permissions need to be modified?
Nitin
Click to expand...
Click to collapse
Please everybody read the note (I should make it bold so people can see it)
"Note:You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings. I'm also surprised to say that even with your data not wiped, it's working."
I am coming from the fake Nexus Rom aka I do not have a custom bootloader yet. What bootloader is the best to go with?
Could someone write me a quick instruction how to get started with my situation. I bet there are a lot coming from fake nexus.
Thanks for the great work!!
wow! cool zaclimon, so quanta is now N compatible i guess? haha, gj, if i'll find any kind of fix for something, i'll pull request, and thanks alot!
aabuk said:
wow! cool zaclimon, so quanta is now N compatible i guess? haha, gj, if i'll find any kind of fix for something, i'll pull request, and thanks alot!
Click to expand...
Click to collapse
I compiled a stock kernel as I wanted to start off a fresh base if ever others wanted to use a custom kernel. (Including myself with Quanta) It is patched with Google's latest updates.
I could compile a build of Quanta and incorporate the patches required to boot Nougat but it wouldn't be fair lool.
zaclimon said:
Please everybody read the note (I should make it bold so people can see it)
"Note:You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings. I'm also surprised to say that even with your data not wiped, it's working."
Click to expand...
Click to collapse
I'm using the open gapps 7.0 arm version, and after change the app permission, all is good so far
And another sergestion, can we change the original LCD density to 240 instead of the default 320 ?
This change make the desktop more attractive.
zaclimon said:
I compiled a stock kernel as I wanted to start off a fresh base if ever others wanted to use a custom kernel. (Including myself with Quanta) It is patched with Google's latest updates.
I could compile a build of Quanta and incorporate the patches required to boot Nougat but it wouldn't be fair lool.
Click to expand...
Click to collapse
hahaha, okie, atleast i got some space to look at dem kernelzz, thanks for echo
cqloveqc said:
I'm using the open gapps 7.0 arm version, and after change the app permission, all is good so far
And another sergestion, can we change the original LCD density to 240 instead of the default 320 ?
This change make the desktop more attractive.
Click to expand...
Click to collapse
This has been allowed always from build.prop, did you try that?
P.
[sntfrmnxs⁴]
Gu$houn* said:
This has been allowed always from build.prop, did you try that?
P.
[sntfrmnxs⁴]
Click to expand...
Click to collapse
Yes, I've tried that by using a es file manager, but if we can make the 240 default, we don't need to make change anymore
Damn I'm late to the party, downloading now !
And thanks a ton @zaclimon for keeping mako alive, you're the man !
@zaclimon nice work.. keep it clean please
/e/ OS
/e/ is a “deGoogled” version of Android OS, actually a fork of LineageOS. It has an open-source Android OS core, with no Google apps or Google services accessing your personal data.
Your data is YOUR data!
Learn more
Download
Github Releases
Flash and update instructions
If you are coming from MIUI.
- Unlock the bootloader and install brick protection (factory-preloader, lk, lk2). More info about these processes can be found here.
- Disable AVB by flashing stock vbmeta.img with the following command: "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".
- Find a decent working TWRP, flash, and boot it using the manual key combo (e.g. official non-CFW TWRP or LR.TWRP for A9 if you are on MIUI A9, LR.TWRP for A10 if you are on MIUI A10).
- If you have begoniain, run this command "adb shell resetprop ro.product.device begoniain".
- Format data.
- Flash the latest /e/ OS build (CFW is included in the rom zip).
- Flash a CFW compatible recovery (like CFW TWRP) either from within the recovery you already have booted or by rebooting to fastboot.
- Reboot into System.
If you are coming from a non-CFW custom rom.
- Reboot to fastboot and Install brick protection (factory-preloader, lk, lk2). More info about these processes can be found here.
- Boot into custom non-CFW recovery.
- Format data.
- Flash the latest /e/ OS build (CFW is included in the rom zip).
- Flash a CFW compatible recovery (like CFW TWRP) either from within the recovery you already have booted or by rebooting to fastboot.
- Reboot into System.
If you already are on a CFW custom rom with CFW custom recovery installed.
- Boot into custom CFW recovery.
- Format data if you're clean flashing. Skip this step if you are just updating /e/ os.
- Flash the latest /e/ OS build (CFW is being reflashed together with the rom zip).
- Reboot into System.
About the builds
- Remember that the builds tagged with "testing" have a little higher chance to include unresolved issues.
- There is no OTA-update support, at least at the moment.
- CFW is included in the rom zips. There is no need for flashing any extra CFW zip.
- I have no plans of trying to make this rom official (lack of time for propper maintainance). The basic thing that needs to be fixed right now is SELinux and this is probably not going to happen any time soon. If you are a developer that wishes to take over this project and make it official or maybe just fix SELinux, please, go ahead and do it!
Issues
- The camera doesn't have full resolution support.
- SELinux is Permissive.
- You tell me!
Repositories used in building this rom
android_device_xiaomi_begonia: https://github.com/LineageOS/android_device_xiaomi_begonia
android_device_xiaomi_begoniain: https://github.com/LineageOS/android_device_xiaomi_begoniain
android_kernel_xiaomi_mt6785: https://github.com/LineageOS/android_kernel_xiaomi_mt6785
android_device_xiaomi_mt6785-common: https://github.com/LineageOS/android_device_xiaomi_mt6785-common
android_hardware_mediatek: https://github.com/LineageOS/android_hardware_mediatek
android_device_mediatek_sepolicy: https://github.com/LineageOS/android_device_mediatek_sepolicy
proprietary_vendor_firmware: https://github.com/HyperTeam/proprietary_vendor_firmware
proprietary_vendor_xiaomi: https://gitlab.com/the-muppets/proprietary_vendor_xiaomi/-/tree/lineage-17.1
android_vendor_e: https://gitlab.e.foundation/steadfasterX/android_vendor_e/
Special thanks
* @theimpulson , @Sahil_Sonar , @Agent_fabulous and rest of developers and testers that gave life to the development of Redmi Note 8 pro.
* @steadfasterX who patiently guided me in the process of building an android rom for the first time.
* Have I forgotten someone? Please poke me with the name!
Contribute
Feel like contributing/donating? Please contact the above aforementioned people or look for a "donate" link in their posts/threads. You could also consider contributing to the /e/ foundation.
Support links
/e/ community forum: https://community.e.foundation/
/e/ announcements (Telegram group): https://t.me/mydataismydata
/e/ community support (Telegram group): https://t.me/joinchat/C49jqEUbP-CNUGjzu-dTEA
/e/ public (Telegram group): https://t.me/joinchat/GNc9FVNKxz5OGPo3mFql5g
Begonia Support | Custom ROMs (Telegram group): https://t.me/dreamsupportbegonia
Useful information about /e/
* What’s in /e/?
The /e/ ROM is a fork of LineageOS that is strongly ungoogled. It consists of:
a set of sorted and improved default open source applications
various online services such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
It is not mandatory to use the /e/ services though. If you want to enjoy this degoogled rom and at the same time not use the /e/ services, the /e/ apps can easily be disabled. This way, one can set up a private server for contacts/calendar/files sync (eg. with Nextcloud) and use this instead.
* DeGoogling / UnGoogling
The goal of “unGoogling” is to remove or disable any little or big feature that is sending any data to Google servers, and to offer non-Google default online services, including for search.
Google default search engine is removed everywhere and replaced by other services.
Google Services are replaced by microG and alternative services.
all Google apps are removed and replaced by good alternative applications
Google servers are not used anymore to check connectivity
NTP servers are not Google NTP servers anymore
DNS default servers are not Google anymore, and their settings can be enforced by the user to a specific server
Geolocation is using Mozilla Location Services in addition to GPS
CalDAV/CardDAV management and synchronization application (DAVDroid) is fully integrated with the user account and calendar/contact application
* Description of /e/ default applications
All pre-installed applications are open source applications but the Maps app.
Web-browser: an ungoogled fork of Chromium, built from Bromite patch-sets, with specific /e/ settings
Mail: a fork of K9-mail for better user experience, some bugfixes and support for oauth, with OpenKeyChain for PGP encryption support
SMS: a fork of QKSMS
Camera: a fork of OpenCamera
Dialer: default Android dialer application
Calendar: a fork of Etar calendar, that fixes crashes with calendar invitations
Contact: default Android contact application
Clock: a fork of Android deskclock application
Gallery: default Android gallery3d application
Filemanager: Android documentsui application
Sound recorder: default LineageOS sound recorder
Calculator: default Android calculator2 application
Keyboard: default Android keyboard
Android application installer is /e/ application installer, that supports more than 60,000 applications.
Maps: MagicEarth
Weather: a fork of GoodWeather for a modified user interface, using data fetched from Open Weather Map
PDF reader: PdfViewer Plus
Notes: a fork of NextCloud Notes to support /e/ online accounts
Tasks: OpenTasks
* Description of /e/ online services at ecloud.global
/e/ “spot” at https://spot.ecloud.global search engine is a fork of SearX meta-search engine, with major look&feel improvements and peformance improvements
/e/ cloud (ecloud.global) includes drive, mail, calendar, contacts, notes, tasks and office. It’s built upon NextCloud, Postfix, Dovecot and OnlyOffice. It’s been integrated to offer a single login identity in /e/OS as well as online, where users can retrieve their data at https://ecloud.global services, or self-hosted on their own server
Changelog
2021-04-19
* New builds for begonia/begoniain (v0.16)
- Q security patches for April 2021
- See this list of issues being resolved on v0.16
2021-04-03
* New builds for begonia/begoniain (v0.16 testing)
- Q security patches for March 2021
- See this list of issues being resolved on v0.16
2021-03-16
* New builds for begonia/begoniain (v0.15)
- One can now see the actual /e/ os version being reflected in Settings > About phone (instead of v1 that was being displayed before)
- Detailed changelog on the /e/ os v0.15 release here
2021-02-28
* New builds for begonia/begoniain (v0.15 testing)
- MicroG version updated to 0.2.17.204714
- Q security patches for February 2021
- See this list of issues being resolved on v0.15
2021-01-19
* New builds for begonia/begoniain (v0.14)
- All builds are now signed with private keys
- UI changes across default applications
- MicroG version updated to v0.2.16.204713
- Maps updated to v7.1.21.1.3613AA78.047032E6
- OpenKeyChain updated to v5.5
- Q security patches for January 2021
- Misc LOS code updates
2021-01-03
* Initial release for begoniain (v0.13)
- Signed with private keys
2020-12-30
* Initial release for begonia (v0.13)
- Signed with public android test keys
Build Guide
Here is an /e/ build guide. I don't know if all my practices are optimal but I would gladly receive any feedback on how to make it better.
Thanks for an ungoogled rom.
Is this rom non CFW?
Now im on cfw rom android 10, can i flash e os?
Gilbran_01 said:
Now im on cfw rom android 10, can i flash e os?
Click to expand...
Click to collapse
xobust said:
Thanks for an ungoogled rom.
Is this rom non CFW?
Click to expand...
Click to collapse
No need to flash cfw! Just follow the instructions provided on post #1.
As you know very well, the vast majority of currently installed custom roms for the N8pro is based on CFW. So: What should those guys do who have installed a custom rom (for me Bliss A10 with CFW2.1) and want to check out /e/? Getting back to MIUI A9 first?
sliveness said:
As you know very well, the vast majority of currently installed custom roms for the N8pro is based on CFW. So: What should those guys do who have installed a custom rom (for me Bliss A10 with CFW2.1) and want to check out /e/? Getting back to MIUI A9 first?
Click to expand...
Click to collapse
Okay, I 'll try to get into a little more detail. The newer builds of LineageOS (and thus of /e/ also) include a series of proprietary images included into the zip. They include also the images that are included in CFW. So, yes, they kind of are considered as CFW builds but one does not need to flash any CFW zip, as the CFW images are being flashed with every rom flash now.
It may feel pointless to include those images in every rom update as they just make the size of the zips higher. They do not really need to be flashed every time a rom update comes out, as they are unchanged. But I think this method is preferred right now because @theimpulson is aiming for LOS 17.1 to get official and it's important from this aspect. Of course, I could adjust the builds to not include the cfw images and go the other way, but I chose to stick to the LOS way for now.
So, to sum it up: No need for flashing CFW (as it already is included in the rom zip). Just follow the instructions on post #1!
Thank you for this important information! I did not know about this integration which seems to be quite reasonable in view of all these different CFW versions.
polfrank said:
Build Guide
Here is an /e/ build guide. I don't know if all my practices are optimal but I would gladly receive any feedback on how to make it better.
Click to expand...
Click to collapse
Hi @polfrank
I have been making /e/ ROMs, mostly for Sony devices and, like you I needed to reference a repo outside of github in a manifest . The repo is in a gitlab instance hosted at git.coop. I did it with the following code in my manifest
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- git.coop remote -->
<remote name="gitcoop"
fetch="https://git.coop/"
revision="main" />
<!-- Proprietary blobs for z3c -->
<project name="phone-custom-roms/vendor_sony_z3c" path="vendor/sony/z3c" remote="gitcoop" revision="main" />
<project name="phone-custom-roms/vendor_sony_shinano-common" path="vendor/sony/shinano-common" remote="gitcoop" revision="main" />
<!-- Proprietary blobs for lilac -->
<project name="phone-custom-roms/vendor_sony_lilac" path="vendor/sony/lilac" remote="gitcoop" revision="main" />
</manifest>
I don't think you will need to go that far as I believe a `gitlab` repo name is already defined, so you should just be able to change the line in your manifest to something like
Code:
<project name="the-muppets/proprietary_vendor_xiaomi" path="vendor/xiaomi" remote="gitlab" />
I hope that helps. You can check out the manifests I use in my git.coop 'manifests' repo
petefoth said:
Hi @polfrank
I have been making /e/ ROMs, mostly for Sony devices and, like you I needed to reference a repo outside of github in a manifest . The repo is in a gitlab instance hosted at git.coop. I did it with the following code in my manifest
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- git.coop remote -->
<remote name="gitcoop"
fetch="https://git.coop/"
revision="main" />
<!-- Proprietary blobs for z3c -->
<project name="phone-custom-roms/vendor_sony_z3c" path="vendor/sony/z3c" remote="gitcoop" revision="main" />
<project name="phone-custom-roms/vendor_sony_shinano-common" path="vendor/sony/shinano-common" remote="gitcoop" revision="main" />
<!-- Proprietary blobs for lilac -->
<project name="phone-custom-roms/vendor_sony_lilac" path="vendor/sony/lilac" remote="gitcoop" revision="main" />
</manifest>
I don't think you will need to go that far as I believe a `gitlab` repo name is already defined, so you should just be able to change the line in your manifest to something like
Code:
<project name="the-muppets/proprietary_vendor_xiaomi" path="vendor/xiaomi" remote="gitlab" />
I hope that helps. You can check out the manifests I use in my git.coop 'manifests' repo
Click to expand...
Click to collapse
Thanks for your insight! If I remember correctly, I had tried to reference the gitlab remote on .repo/manifests.xml but when doing repo sync it would say that it could not find the repository. I am going to give it a new try considering your tips when the next build comes!
Cannot flash from Pixel Experience (with CFW 3.2).
Formated Data and flashed, but the phone restarts twice and boots into TWRP.
Any Idea? I'm using TWRP 3.4.0-3 and have the EU version of begonia.
xobust said:
Cannot flash from Pixel Experience (with CFW 3.2).
Formated Data and flashed, but the phone restarts twice and boots into TWRP.
Any Idea? I'm using TWRP 3.4.0-3 and have the EU version of begonia.
Click to expand...
Click to collapse
Did you really format the data (the process that you have to type "yes" in order for it to be done) or just wipe data?
polfrank said:
Did you really format the data (the process that you have to type "yes" in order for it to be done) or just wipe data?
Click to expand...
Click to collapse
Yes I did, forgot to copy my backups to the computer too .
I had this problem before though, I could not flash any Android 10 ROMs after flashing Pixel Experience.
Did anyone successfully revert to Android 10 and CFW 2.1?
I tried to repair the fs of the data partition too.
xobust said:
Yes I did, forgot to copy my backups to the computer too .
I had this problem before though, I could not flash any Android 10 ROMs after flashing Pixel Experience.
Did anyone successfully revert to Android 10 and CFW 2.1?
I tried to repair the fs of the data partition too.
Click to expand...
Click to collapse
I'd probably suggest to just flash the stock ROM and start from scratch.
FivEawE said:
I'd probably suggest to just flash the stock ROM and start from scratch.
Click to expand...
Click to collapse
Got it working, not sure how. I formated and flashed again and it worke.
Is it possible to decrypt data from TWRP? It does not prompt me for my graphical
password when i start the recovery. Guesse i have to factory reset to install magisk.
xobust said:
Got it working, not sure how. I formated and flashed again and it worke.
Is it possible to decrypt data from TWRP? It does not prompt me for my graphical
password when i start the recovery. Guesse i have to factory reset to install magisk.
Click to expand...
Click to collapse
I haven't found a way or a recovery with working decryption. I think flashing Magisk should be fine even with encrypted /data partition (it has worked for me on PE). Flashing of the Magisk uninstaller script, however, won't work with /data encrypted.
xobust said:
Got it working, not sure how. I formated and flashed again and it worke.
Is it possible to decrypt data from TWRP? It does not prompt me for my graphical
password when i start the recovery. Guesse i have to factory reset to install magisk.
Click to expand...
Click to collapse
FivEawE said:
I haven't found a way or a recovery with working decryption. I think flashing Magisk should be fine even with encrypted /data partition (it has worked for me on PE). Flashing of the Magisk uninstaller script, however, won't work with /data encrypted.
Click to expand...
Click to collapse
Which custom recovery do you use? I use twrp 3.4.0_10 without problems. I get prompt to decrypt user data every time I reboot to recovery.
polfrank said:
Which custom recovery do you use? I use twrp 3.4.0_10 without problems. I get prompt to decrypt user data every time I reboot to recovery.
Click to expand...
Click to collapse
I've been using the ones recommend for PE. On forums there's only 3.3.1 Unofficial as far as I know. It'd be much appreciated If you posted a link for the 3.4.0 one .