hi there -
update (20230216): an updated february build is available.
i built lineageos 20 (aka: android 13) for my fairphone 4, microg and f-droid are included. seems to work fine, have a look here: https://bing-bong.de/stuff/fp4/ if you want to give it a try. to flash the image, do the following:
unlock your bootloader as documented here: https://support.fairphone.com/hc/en-us/articles/4405858258961-FP4-Manage-the-bootloader
adb reboot bootloader and make sure your fp4 is listed in fastboot devices (fwiw, that didn't work with usb3 ports on my thinkpad)
flash the lineageos recovery image: fastboot flash boot lineage-20.0-20221218-UNOFFICIAL-FP4-recovery.img
adb reboot recovery, do the format data/ factory reset dance and flash the image via apply update and adb sideload FP4/lineage-20.0-20221218-UNOFFICIAL-FP4.zip
thank you to Sony make.believe for double checking this. Things not working as expected:
notification led
to the best of my knowledge, the device-specific bits in the lineage-repo are based on this effort. the lineageos repo for the fp4 can be found here.
t.
Any plans to make the LOS part official? That might even convince me to buy the FP4 finally.
heinhuiz said:
Any plans to make the LOS part official? That might even convince me to buy the FP4 finally.
Click to expand...
Click to collapse
i didn't do any of the heavy lifting myself and merely took what others already pushed to the lineage repos for the upcoming lineageos 20 release, all kudos goes to them.
Lineageos20 will probably be released at around April 2023 and will most likely add fp4 to the list of officially supported devices - i just didn't want to wait that long
t.
Please post your kernel sources inline with the liscnece requirements. @tfbb
Logix said:
Please post your kernel sources inline with the liscnece requirements. @tfbb
Click to expand...
Click to collapse
Code:
[email protected]:~$ du -hs lineage/src/LINEAGE_20_0/kernel/ lineage/src/LINEAGE_20_0/vendor/fairphone/FP4/
2.6G lineage/src/LINEAGE_20_0/kernel/
345M lineage/src/LINEAGE_20_0/vendor/fairphone/FP4/
[email protected]:~$
i suppose you really don't want me to post this here
you can recreate what i did by checking out https://github.com/lineageos4microg/docker-lineage-cicd/tree/lineage-20-python , tweak a few things there (i'll be happy to help) and run something like
Code:
docker run -it -e "BRANCH_NAME=lineage-20.0" -e "DEVICE_LIST=FP4" -e "SIGN_BUILDS=true" -e "SIGNATURE_SPOOFING=restricted" -e "INCLUDE_PROPRIETARY=true" -e "CCACHE_SIZE=100G" -e "PARALLEL_JOBS=8" -e "WITH_GMS=true" -v "/home/thoralf/lineage/src:/srv/src" -v "/home/thoralf/lineage/zips:/srv/zips" -v "/home/thoralf/lineage/logs:/srv/logs" -v "/home/thoralf/lineage/ccache:/srv/ccache" -v "/home/thoralf/lineage//keys:/srv/keys" -v "/home/thoralf/lineage/manifests:/srv/local_manifests" lineage20-python
Regarding the licenses: I hope we can both agree upon that things in either the lineage or the muppets repo should be safe to use.
tfbb said:
Code:
[email protected]:~$ du -hs lineage/src/LINEAGE_20_0/kernel/ lineage/src/LINEAGE_20_0/vendor/fairphone/FP4/
2.6G lineage/src/LINEAGE_20_0/kernel/
345M lineage/src/LINEAGE_20_0/vendor/fairphone/FP4/
[email protected]:~$
i suppose you really don't want me to post this here
you can recreate what i did by checking out https://github.com/lineageos4microg/docker-lineage-cicd/tree/lineage-20-python , tweak a few things there (i'll be happy to help) and run something like
Code:
docker run -it -e "BRANCH_NAME=lineage-20.0" -e "DEVICE_LIST=FP4" -e "SIGN_BUILDS=true" -e "SIGNATURE_SPOOFING=restricted" -e "INCLUDE_PROPRIETARY=true" -e "CCACHE_SIZE=100G" -e "PARALLEL_JOBS=8" -e "WITH_GMS=true" -v "/home/thoralf/lineage/src:/srv/src" -v "/home/thoralf/lineage/zips:/srv/zips" -v "/home/thoralf/lineage/logs:/srv/logs" -v "/home/thoralf/lineage/ccache:/srv/ccache" -v "/home/thoralf/lineage//keys:/srv/keys" -v "/home/thoralf/lineage/manifests:/srv/local_manifests" lineage20-python
Regarding the licenses: I hope we can both agree upon that things in either the lineage or the muppets repo should be safe to use.
Click to expand...
Click to collapse
Not what i meant m8. please see other rom posts they all link to a github with their kernel sources. This is to be complaint with the legal requirements of GPL code. Plese post your source repos (your github) in the inital post. Of course muppets and linage are safe.
Logix said:
Not what i meant m8. please see other rom posts they all link to a github with their kernel sources. This is to be complaint with the legal requirements of GPL code. Plese post your sources in the inital post.
Click to expand...
Click to collapse
once again, these are not _my_ sources, see above. afaik, the initial effort on which the lineageos tree is based on can be found here: https://github.com/WeAreFairphone/android_kernel_fairphone_sm7225 .
tfbb said:
once again, these are not _my_ sources, see above. afaik, the initial effort on which the lineageos tree is based on can be found here: https://github.com/WeAreFairphone/android_kernel_fairphone_sm7225 .
Click to expand...
Click to collapse
I understand that ^ this is what is needed for the legal requirement please add it to your intial op. Thank you for your understanding and compliance with the law. All sources must be posted when using GPL Code.
tfbb said:
hi there -
i built lineageos 20 (aka: android 13) for my fairphone 4, microg and f-droid are included. seems to work fine, have a look here: https://bing-bong.de/stuff/fp4/ if you want to give it a try.
to the best of my knowledge, the device-specific bits in the lineage-repo are based on this effort.
t.
Click to expand...
Click to collapse
Thanks for your work!
Will you update the rom regularly?
And how should I flash your recovery, like with these commands;
fastboot flash recovery_a <lineage-20.0-20221218-UNOFFICIAL-FP4-recovery.img>
fastboot flash recovery_b <lineage-20.0-20221218-UNOFFICIAL-FP4-recovery.img>
?
Best regards
Sony make.believe said:
Thanks for your work!
Will you update the rom regularly?
Click to expand...
Click to collapse
yes, i'll provide monthly updates at least until images will become available at https://download.lineage.microg.org/ . i'll also look into providing ota-updates, but won't promise anything here and now.
Sony make.believe said:
And how should I flash your recovery, like with these commands;
fastboot flash recovery_a <lineage-20.0-20221218-UNOFFICIAL-FP4-recovery.img>
fastboot flash recovery_b <lineage-20.0-20221218-UNOFFICIAL-FP4-recovery.img>
Click to expand...
Click to collapse
in a nutshell:
unlock your bootloader as documented here: https://support.fairphone.com/hc/en-us/articles/4405858258961-FP4-Manage-the-bootloader - i guess you did this already
adb reboot bootloader and make sure your fp4 is listed in fastboot devices (fwiw, that didn't work with usb3 ports on my thinkpad)
flash the lineageos recovery image: fastboot flash boot lineage-20.0-20221218-UNOFFICIAL-FP4-recovery.img - i didn't specify any slots here
adb reboot recovery, do the format data/ factory reset dance and flash the image via apply update and adb sideload FP4/lineage-20.0-20221218-UNOFFICIAL-FP4.zip
hth,
t.,
tfbb said:
yes, i'll provide monthly updates at least until images will become available at https://download.lineage.microg.org/ . i'll also look into providing ota-updates, but won't promise anything here and now.
in a nutshell:
unlock your bootloader as documented here: https://support.fairphone.com/hc/en-us/articles/4405858258961-FP4-Manage-the-bootloader - i guess you did this already
adb reboot bootloader and make sure your fp4 is listed in fastboot devices (fwiw, that didn't work with usb3 ports on my thinkpad)
flash the lineageos recovery image: fastboot flash boot lineage-20.0-20221218-UNOFFICIAL-FP4-recovery.img - i didn't specify any slots here
adb reboot recovery, do the format data/ factory reset dance and flash the image via apply update and adb sideload FP4/lineage-20.0-20221218-UNOFFICIAL-FP4.zip
hth,
t.,
Click to expand...
Click to collapse
Sounds good! I think, I will give it a try
I only have one comment on point 3 of your instructions:
You should separate the commands "flash" and "boot" to avoid errors.
And could you please link the points to the first post? That would provide for more overview
PS:
At the opportunity, best also add the links that the mod asks for. Very likely your post will be deleted/locked soon otherwise....
hi sony,
Sony make.believe said:
I only have one comment on point 3 of your instructions:
You should separate the commands "flash" and "boot" to avoid errors.
Click to expand...
Click to collapse
… that's what worked for me, according to my history could you please check if fastboot flash recovery … works as well? i'll update my post in this case.
Sony make.believe said:
And could you please link the points to the first post? That would provide for more overview
PS:
At the opportunity, best also add the links that the mod asks for. Very likely your post will be deleted/locked soon otherwise....
Click to expand...
Click to collapse
i'll update the first post if you can confirm that this worked for you as well. i already added the link to the wearefairphone-repo, so logix should be happy now.
tfbb said:
hi sony,
… that's what worked for me, according to my history could you please check if fastboot flash recovery … works as well? i'll update my post in this case.
i'll update the first post if you can confirm that this worked for you as well. i already added the link to the wearefairphone-repo, so logix should be happy now.
Click to expand...
Click to collapse
Ok, I tested it and you were right;
"fastboot flash boot..." was correct, I take back my statement.
Unfortunately the location service in MicroG does not work, so I switched back to IodeOS.
But that was the only bug I noticed after 3 hours of use, so the ROM looks stable to me.
Sony make.believe said:
Ok, I tested it […]
Click to expand...
Click to collapse
thank you, i amended the first post.
Sony make.believe said:
[…] Unfortunately the location service in MicroG does not work […]
Click to expand...
Click to collapse
selecting this will be possible if you set the location permission for "mozilla unifiednlp backend" to "allow all the time" (via settings → apps → all apps → show system).
Now when FP4 is officially supported by lineageos, I suppose there should be an official build available from the microg lineageos project. The builds are now appearing in the downloads page, about 1 architecture per hour. However, it seems to be going alphabetically, and FP4 is not there. Is it because there is a problem with the FP4 folder on the official lineage mirror?
- official lineage FP4 download page: (returns Internal Server Error at the time of writing): https://download.lineageos.org/FP4
- microg lineage builds download page: https://download.lineage.microg.org/
According https://github.com/lineageos4microg/docker-lineage-cicd/pull/366
it seems that FP4 microG build will be available in the next few days.
the january build is available. please note that i've had to build with RELAX_USES_LIBRARY_CHECK=true due to an otherwise failing build process. this is definitely not optimal, but didn't cause any issues after some superficial testing. i'll put up another build if this gets fixed.
the february build is available, built without RELAX_USES_LIBRARY_CHECK=true . please note that this will be the final build i'll be offering - LineageOS for microG images are now available here: https://download.lineage.microg.org/FP4/
Thank you for the fantastic ROM. The phone has been running for over 2 months without any problems with it. Thanks alot !!
Related
This is DIY
If you are just looking for a well done and stable PA download, you are probably the wrong place. Then go and grab xzzz9097s build, it's good!
If you are impatient and know what to do, just leave and do the init/sync/build.
For anyone wanting to build her/his own PA without any "extras", go ahead and read on.
We already have a very easy full guide to compile CM10 for HOX. I was looking for the same for ParanoidAndroid, but did not find a 100% guide, meaning I had to do it myself.
To be fair, I only needed to do 1% as you will see after the usual disclaimer. I hope this little guide will be enough to make anyone complile their own PA for the HOX.
The usual disclaimer:
I am no developer!
I just happen to be able to read and understand instructions. I am persistent and know how to search for answers.
With luck and patience I ended up with a 184MB zip, that installs and runs just fine on my HOX.
I pass this guide as it is now, no guarantee no returns. I will probably not be able to help much here, time is very limited, so no commitments for support from me.
If it breaks you device, you broke it all by yourself
I am no developer!
gokussjx made the general guide, explaining how to port Paranoid Android 3.xx to different devices.
It works 99% for Endeavoru. The last 1% takes some effort to get right.
For me, not knowing what I am doing, it took a lot of trial and error, but eventually, - I made it and might as well pass it on here.
I'm in debt to all the people helping out in that thread. Huge thanks!
To get started, just follow a few simple steps:
You need a linux setup.
Install as your main system or run it in windows with VirtualBox.
Most guides are expecting Ubuntu. I use Mint Debian 64, which is just perfect for this job (and everything else ).
For VirtualBox you need at least a 50GB virtual-drive. Add 16GB if you will use ccache. I have build PA with a 52GB VBox in Win7.
It was just enough to compile, but had no room for ccache!
Compile time (VBox) on EliteBook 8540w (i7) was 120min. Not too bad, considering my old DeskTop need close to 4 hours on pure Linux.
Expect to download 8GB of source. Add 18GB for building to the "out" folder.
Enough statistics now, let's get started.
Follow gokussjx guide to setup linux for PA compiling.
Follow only these steps:
# Install OpenSSL, for Python
# Install Dependencies
# Configure USB
# JAVA JDK Installation
# Python Installation (just pick option 1)
# Android SDK
Click to expand...
Click to collapse
Exit gokussjx guide and continue here:
Download your favorite arm toolchain:
I found mine here.
Just extract the archive to any folder with user access, later you will point the build system to the /bin folder of the toolchain.
Install CCACHE:
Code:
$ sudo apt-get install ccache
Activate it in .bashrc:
Code:
# use ccache
export USE_CCACHE=1
You can change max-cache size, 16G should be enough for this build.
From terminal:
Code:
$ ccache -M 16G
Install Repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Download the build manifest:
Code:
$ mkdir -p padroid/system
$ cd padroid/system
$ repo init -u git://github.com/teemodk/manifest.git -b padroid
Get the source!
Code:
$ repo sync -j16
Find this section in "build/envsetup.sh" update with your favorite arm toolchain:
Code:
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=[B]~/toolchain/linaro4.8/bin[/B]
;;
mips) toolchaindir=mips/mipsel-linux-android-$targetgccversion/bin
;;
Go!
Code:
$ ./rom-build.sh endeavoru
Thats all. If it went well, get your new ROM in "out/target/product/endeavoru"
Don't forget the gApps.
Credits go to
PA:molesarecoming, D4rKn3sSyS for the awesome hybrid magic. All PA contributors. gokussjx for the mother of all PA guides. All the helpful people here, that use their time to help.
CM(aosp):thöemy,gorbi16,tbalden,(pabx) and all the unknown soldiers contributing to CM
Everyone I forgot.
Differencies from the official guide.
The official PA manifest is put together in a way, so you can easily build and maintain multiple devices with only one manifest.
It works by adding and removing device specific code with local manifests under the "vendor/pa" folder.
However, I am only compiling for OneX, so I found it easier to add/remove stuff directly in the main manifest.
The downside to this is, that you have to manually maintain the manifest everytime you want to sync with PA. Place for improvement
All changes in STEP 2 of the official guide, is already done if using my guide with padroid manifest.
In vendor/pa these steps are done:
Code:
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/manifests/endeavoru.adds"]/manifest/<device>.adds[][/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/manifests/endeavoru.removes"]/manifest/<device>.removes[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/prebuilt/pa_endeavoru.conf"]/prebuilt/pa_<device>.conf[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/products/pa_endeavoru.mk"]/products/pa_<device>.mk[/URL]
* Add device makefile entry to [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/products/AndroidProducts.mk"]/products/AndroidProducts.mk[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/tree/padroid/vendorprops"]/vendorprops/<device>.proprietaries[/URL]
* Add device lunch menu entry to [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/vendorsetup.sh"]/vendorsetup.sh[/URL]
Furthermore, I temporarily moved the CM adds/removes from "vendor/pa/manifests" to .repo/manifest.xml.
I am sure there are better ways to handle git/repo/manifest etc., but this works well for me for now. Open for suggestions though.
Problem Solving
If (when) you run into problems, go to the official guide and find the answer. Most, if not all, errors is already answered there. If not, ask.
But first make a serious effort to find the error yourself. Read some good advice about finding the error.
As a rule of thumb: The build system tells you where to find the error! Something is missing, something is duplicated or somthing is just wrong. It's all in the log, running up your screen when compiling.
Build 25.Oct.2013
http://d-h.st/XRt
Nice, I'm always eager to learn this stuff .
Thanks!
ROM uploaded to post 3.
teemo said:
ROM uploaded to post 3.
Click to expand...
Click to collapse
Thank you so much Teemo, for providing the guide and the rom.
Just a Q: is this stock ParanoidAndroid rom (stock kernel?) ?
Thanks again for your work :good:
Mat08.cc said:
Thank you so much Teemo, for providing the guide and the rom.
Just a Q: is this stock ParanoidAndroid rom (stock kernel?) ?
Thanks again for your work :good:
Click to expand...
Click to collapse
The ROM is as close to stock as it get for OneX. It is really a mix of CyanogenMod and ParanoidAndroid. I follow the official build guide from PA-team.
The kernel is from same source as CM.
You can see everything in the manifest.
@teemo
your build is running fast and stable, congratulations! maybe you can keep updating this .. I appreciate it and I'm sure many other people would be of the same opinion
Sry,wrong threat....
Gesendet von meinem EndeavorU mit Tapatalk
Hi @teemo I was trying to build my own rom using a different source.
I'm pretty sure I've done things right except that when i start my build it ends up after few seconds saying: "Kernel source found, but no configuration was defined. Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file"
I checked my BoardConfig.mk file and what I've got is TARGET_KERNEL_CONFIG := cyanogenmod_endeavoru_defconfig
I thought you may know how to help me with this!
Other infos: I'm tryn to build paranoidandroid 4.0 and i'm using cyanogenmod files for the endeavoru since i know aospa is cyanogenmod based right?
Hope you can help me :fingers-crossed:
Mat08.cc said:
Hi @teemo I was trying to build my own rom using a different source.
I'm pretty sure I've done things right except that when i start my build it ends up after few seconds saying: "Kernel source found, but no configuration was defined. Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file"
I checked my BoardConfig.mk file and what I've got is TARGET_KERNEL_CONFIG := cyanogenmod_endeavoru_defconfig
I thought you may know how to help me with this!
Other infos: I'm tryn to build paranoidandroid 4.0 and i'm using cyanogenmod files for the endeavoru since i know aospa is cyanogenmod based right?
Hope you can help me :fingers-crossed:
Click to expand...
Click to collapse
Hi, I don't know what it takes to build ParanoidAndroid 4
But maybe you can ask in the Paranoid guide.
Or you can ask here for all other builds.
EDIT: Btw, to build PA4 or any other KitKat, you need the new sources for OneX (device+vendor+kernel). This guide will not work for KitKat.
teemo said:
Hi, I don't know what it takes to build ParanoidAndroid 4
But maybe you can ask in the Paranoid guide.
Or you can ask here for all other builds.
EDIT: Btw, to build PA4 or any other KitKat, you need the new sources for OneX (device+vendor+kernel). This guide will not work for KitKat.
Click to expand...
Click to collapse
I used the new sources but that was the result! I'll start from zero again to see if I missed something Thanks for the reply always really kind!
Mat08.cc said:
I used the new sources but that was the result! I'll start from zero again to see if I missed something Thanks for the reply always really kind!
Click to expand...
Click to collapse
the aospa dev build the aospa kitkat version...so a few days waiting and it will be there
One-X-master said:
the aospa dev build the aospa kitkat version...so a few days waiting and it will be there
Click to expand...
Click to collapse
Yeah I thought so! But I would love to learn! I have always looked to devs as to extraordinary people, understanding what makes them such would be great
Hey @teemo , sorry to bother you, but could you make an update build of PA? I don't have a stable connection, can't make a build of the new PA.. :/
Thanks man, take care
LuisDias said:
Hey @teemo , sorry to bother you, but could you make an update build of PA? I don't have a stable connection, can't make a build of the new PA.. :/
Thanks man, take care
Click to expand...
Click to collapse
All credits to @audahadi https://drive.google.com/folderview?id=0B-KjFDQ914F4dVdQLU9nT3VkMGc&usp=sharing
bosas200 said:
All credits to @audahadi https://drive.google.com/folderview?id=0B-KjFDQ914F4dVdQLU9nT3VkMGc&usp=sharing
Click to expand...
Click to collapse
Thanks brotha
teemo said:
Build 25.Oct.2013
http://d-h.st/XRt
Click to expand...
Click to collapse
Any chance helping me build AOSB with newer cm 11 base?
As no instructions anywhere on building AOSB from source. Source is
https://github.com/AOSB?page=1
Many thanks
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .
if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.
Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.
Tks
Thanks man!
Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.
OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img
iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html
I cannot flash gapps arm 7.1.x
Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine
Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?
Hi!
First: I am NOT a dev or contributor of this rom. Please visit before going ahead: https://forum.xda-developers.com/t/gsi-11-lineageos-18-x-gsi-all-archs.4205461/
Second: You do anything at your own risk and should know how to recover a non booting device!
Just playing around with this rom on my SHT-AL09, tested on version 20210317 so far:
Working
- Mobile network including 4G (German carrier Telekom)
- Outgoing & Incoming calls
- Bluetooth
- 2,4 & 5g Wifi
- Front & Back camera
- Video recording
- MTP
- SDcard
- GPS (seems to be working on Telegram)
- Fingerprint reader
Not Working:
- Mobile network icon shows no signal strength
- VoLTE
- VoWIFI
How to install:
- Make a backup.
- Device needs to have bootloader unlocked.
- Visit the above link again --> sourceforge --> lineage-18.x and download version "...treble_arm64_bv*" + unpack it.
- Visit: https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ (I have done it via bootloader method.)
How to update:
- Dont know yet.
Unfortunately I cant get TWRP to work, so I cant test gapps or root. If you have a clue, please let me know - thx!
So you tested a GSI Lineage ROM on the your M5, is it rooted? Should be great to see magisk included in any room, i use Phh treble Quack, it's pre-rooted with su.
Hi @massima
according to this post by one of the dev's Magisk is broken and supersu should be used instead. I can confirm that this works. You do not need working TRWP, just install the app from fdroid, as mentioned.
For me the rom works well, but as I use the tablet without gapps and only as a youtube player (YT Vanced works fine!), I have not really tested "real world szenarios" yet. Also I cannot say something regarding camera quality and battery performance in comparsion to the stock rom, as I went straigt to Linage 15.1 when I got the tablet in 2018.
Yes, i remember that magisk is incompatible with GSI images. I never used Lineage, for me an AOSP experience is the best. I'm waiting to upgrade to Quack when it will receive its last update probably a vanilla edition because the gapps version has a RO system partition and the vnk version doesn't fit, every version is prerooted with phh-su.
Thanks
P.S.: i added a page of our beloved M5 in the phh's wiki.
massima said:
Yes, i remember that magisk is incompatible with GSI images. I never used Lineage, for me an AOSP experience is the best. I'm waiting to upgrade to Quack when it will receive its last update probably a vanilla edition because the gapps version has a RO system partition and the vnk version doesn't fit, every version is prerooted with phh-su.
Thanks
P.S.: i added a page of our beloved M5 in the phh's wiki.
Click to expand...
Click to collapse
Hi Massima,
Sorry for this noob question - where would I find the M5 entry in the phh's wiki?
And generally, is it possible to install a treble rom on the M5 with gapps and functioning bluetooth? I've been using Openkirin so far but no luck with bluetooth there.
Many thanks for any help you can offer.
spoo333 said:
Hi Massima,
Sorry for this noob question - where would I find the M5 entry in the phh's wiki?
And generally, is it possible to install a treble rom on the M5 with gapps and functioning bluetooth? I've been using Openkirin so far but no luck with bluetooth there.
Many thanks for any help you can offer.
Click to expand...
Click to collapse
This is the link, just search your device mine is the M5 8" wifi (sht-w09). You can flash a vanilla (no gapps), the gapps version (be aware is Read Only). if you need a rewritable System partition download the vndklite version (arm64-AB-gapps-vndklite is 2,9Gb but it will not fit in the standard partition <2,9GB ).
I haven't ever tested the bluetooth so i can't say if it works.
Thanks for your reply and the link. I'll check it out if I can figure out the flashing etc.
Flashing seems relatively straightforward. Curious if Bluetooth works. Mine is the CMR-W09-C432
Thanks for the report. This finally gave me confidence to upgrade mine. I did an upgrade from huawai 9.1 to ASOP Phhusson with gapps. I had to register the device at google to get access to gapps -pretty straightforward (https://www.google.com/android/uncertified/). It was relatively straightforward and took about an hour, which was mainly spend on reading.
Steffe89 said:
Thanks for the report. This finally gave me confidence to upgrade mine. I did an upgrade from huawai 9.1 to ASOP Phhusson with gapps. I had to register the device at google to get access to gapps -pretty straightforward (https://www.google.com/android/uncertified/). It was relatively straightforward and took about an hour, which was mainly spend on reading.
Click to expand...
Click to collapse
May I know how to do because when I key command in my pc adb shell, it shows:
C:\adb>adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ "select * from main where name = "android_id";"'
/system/bin/sh: sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ select * from main where name = android_id;: inaccessible or not found
Thanks
toystory2000 said:
May I know how to do because when I key command in my pc adb shell, it shows:
C:\adb>adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ "select * from main where name = "android_id";"'
/system/bin/sh: sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ select * from main where name = android_id;: inaccessible or not found
Thanks
Click to expand...
Click to collapse
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
@Steffe89
"Magisk compatibility is mostly broken since Android 11 - use PHH-SU instead. Install the app and you'll get root for apps."
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Besuz said:
@Steffe89
"Magisk compatibility is mostly broken since Android 11 - use PHH-SU instead. Install the app and you'll get root for apps."
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
Maybe.... According to many posts v21 brings stable magisk support to android 11 so that is a little contradictory....
Anyhow, I'm not really interested in root. I want try and see if magisk with universal patch could make root-hating apps and widewine L1 drm work.
Steffe89 said:
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
Click to expand...
Click to collapse
Thanks a lot
Steffe89 said:
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
Click to expand...
Click to collapse
You're probably aware of that anyway, but just checking that you didn't use "fastboot flash ramdisk patched_boot.img" or "fastboot flash recovery_ramdisk patched_boot.img"
spoo333 said:
You're probably aware of that anyway, but just checking that you didn't use "fastboot flash ramdisk patched_boot.img" or "fastboot flash recovery_ramdisk patched_boot.img"
Click to expand...
Click to collapse
sorry, meant to write: ... not "fastboot flash ramdisk patched_boot.img" but "fastboot flash recovery_ramdisk patched_boot.img"
I am not really sure that I did I correctly, but yes. I followed these instructions https://topjohnwu.github.io/Magisk/install.html#Huawei.
I think the problem is that I failed to remove phh-
Perhaps try again and check that you've got recovery_ramdisk as the target?
I'm also curious because I'm currently on Openkirin and would like to try what you've been doing. Currently have Magisk installed and wouldn't want to be without it because of Adaway etc.
Do you mind describing your steps: you had official Huawei 9.1 installed, then unlocked the bootloader, flashed Phhusson and then added Gapps?
@spoo333: i tried to send an image from my M5 to the pc and viceversa with bluetooth, no problem.
@Steffe89:
i read in the phh' s telegram channel to remove root with the securize option, then clean the cache. I did't test it.
I found this in the phh's gsi channel:
flash super su phh
create sbin
edit init.environ.rc (it's on /)
add line
export PATH /sbin:/vendor/bin:/system/bin
save
remove su in system/bin
done flash magisk
Once again i don't test it, i'm using phh supersu. See/write here.
massima said:
@spoo333: i tried to send an image from my M5 to the pc and viceversa with bluetooth, no problem.
@Steffe89:
i read in the phh' s telegram channel to remove root with the securize option, then clean the cache. I did't test it.
I found this in the phh's gsi channel:
flash super su phh
create sbin
edit init.environ.rc (it's on /)
add line
export PATH /sbin:/vendor/bin:/system/bin
save
remove su in system/bin
done flash magisk
Once again i don't test it, i'm using phh supersu. See/write here.
Click to expand...
Click to collapse
Massima, that's encouraging to hear re bluetooth. Hope Bluetooth headphones would work too...
Following this thread, I recently built e/OS 0.22q for Motorola One xt1941-4 (deen). Please refer to https://e.foundation/e-os/ to learn more about e/OS.
After several weeks of usage this ROM seems to be very useful. Find the zip file with the images of the Andoid 10 version here. Unzip and flash using adb and fastboot. Please use at your own risk!
I used the following repos in my local manifest:
https://github.com/electimon/device_motorola_deen, branch Lineage-17.1
https://github.com/electimon/vendor_motorola_deen, branch Lineage-17.1
https://github.com/100Daisy/android_kernel_motorola_deen, branch android-10-release-qpks30.54-22-13
In addition, I included
https://github.com/LineageOS/android_system_qcom, branch Lineage-17.1
which is obviously needed by some stuff from vendor. Vendor files are from 2019, so if someone could provide a more recent repo, I would be glad to know (last stock rom provided by Motorola is from October 2021)
All credits go to the creators of the LineageOS 17.1 port (link to thread at the top of this post)! Very good job guys!
Works just fine, thanks.
LSV12 said:
Works just fine, thanks.
Click to expand...
Click to collapse
Thanks!
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
01nick07 said:
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
Click to expand...
Click to collapse
I'm sorry, but I have no time and I am not good at making tutorials at all. Please refer to the thread referenced at the beginning of the initial post. There you should find all necessary information. If this is not enough, do some more searching and reading on XDA. If you still feel uncomfortable, stay with the stock rom.
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
xdadevc said:
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
Click to expand...
Click to collapse
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
HerrElling said:
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
Click to expand...
Click to collapse
I read your article and managed to follow it and compile my own e/os. I'm also not an android developer. I did some kernel work in the early days, around Android 2.0 but my path diverged and now I'm completely lost.
Let's keep in touch. If you restart your efforts, I'll be happy to contribute. Meanwhile I'll try my best to get some info from the e/os forums and (pray) the lineageos residual devs.
This is a BETA build for NEW Lineage 20, Android 13. Possible bugs may be present. Let me know!!
MSM to Android 11 if you want to start clean, then flash either CrDroid or Nameless c63 firmware to begin.
This is based on the Android Open Source Project. It can be used without any need to have any Google application installed. It does still include various proprietary hardware-specific code.
Gapps must be flashed separately and are not included in this ROM.
All the source code is available in the Github repo here.
Thanks go to Github and LineageOS for their source code and device specific code. I couldn't have built this without it!!!
The ROM uses the LineageOS source code, device specific code and proprietary blobs. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated daily with minor changes.
You may use another recovery however you will receive a signature verification error. You can simply ignore and choose yes and flash it anyway. You will need to do this with gapps and magisk.apk to root.
DOWNLOAD ROM & GAPPS HERE
#1 REBOOT TO BOOTLOADER
#2 FACTORY RESET: fastboot -w
#3 REBOOT TO RECOVERY
#4 SIDELOAD ROM IN RECOVERY
adb sideload lineage-20-20221112-UNOFFICIAL-lemonadep.zip
reboot recovery
adb sideload lineage-20-20221112-UNOFFICIAL-lemonadep.zip
reboot recovery
#5 SIDELOAD GAPPS: NikGapps-core-arm64-13-20221109-signed.zip
#6 REBOOT TO SYSTEM
#7 REBOOT TO LINEAGE RECOVERY IF YOU WISH TO ROOT
SIDELOAD MAGISK.APK
adb sideload magisk.apk
#8 REBOOT TO SYSTEM
Updates available in built in updater. settings, system, updater.
You can change preferences to check for updates daily.
Sounds interesting......even though I love stock, this is tempting!
TheGhost1951 said:
Sounds interesting......even though I love stock, this is tempting!
Click to expand...
Click to collapse
I'm with you man. I'm on stock too and Lineage is my least favorite ROM. I'm just trying to help others who like it and diagnose and fix a annoying bluetooth bug.
Is possible to post screen shots. plz
OOS camera included. And Oneplus setting
break.cold said:
Is possible to post screen shots. plz
OOS camera included. And Oneplus setting
Click to expand...
Click to collapse
Come-on guy, do your research like the rest of us here.....Google, bing, xda....search. put forth the effort and the reward is greater
What (and where) are the changes you made to Bluetooth connectivity? Does this solve the longstanding problem of "stuttering" audio on Bluetooth phone calls?
MJPollard said:
What (and where) are the changes you made to Bluetooth connectivity? Does this solve the longstanding problem of "stuttering" audio on Bluetooth phone calls?
Click to expand...
Click to collapse
I don't have it listed anywhere. I dumped the firmware from stock and pulled the bluetooth and implemented it into this. I tested it and didn't notice any issues but I went back to stock. Lineage is not my thing. All I can say is to test it out and report any issues and I'll continue to work on any problems that may exist.
09/27 update posted
10/01 update posted
TheSayaMan said:
10/01 update posted
Click to expand...
Click to collapse
Changelog?
Beytullah61 said:
Changelog?
Click to expand...
Click to collapse
Changes in regards to bluetooth connectivity only.
LineageOS/Bluetooth at main · MikeSaya1/LineageOS
Contribute to MikeSaya1/LineageOS development by creating an account on GitHub.
github.com
10/09 update posted. More bluetooth improvements.
TheSayaMan said:
10/09 update posted. More bluetooth improvements.
Click to expand...
Click to collapse
10/15 posted. October security patch.
Thread changed from LineageOS 19 Android 12 to LineageOS 20 BETA Android 13
Can you build for oneplus 9?
imbasador said:
Can you build for oneplus 9?
Click to expand...
Click to collapse
Yes, I'm working on it
Because of the lack of interest on this. This thread will be closed.
Thread closed at the OP's request.