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. Hard & a lot.
*
*/
This is a very early development version, only flash if you know what you're doing! I guarantee nothing.
Due to some unknown bug It could happen that you won't be able to enter twrp UI after installing. Then you need adb access to wipe the data partition.
This should allow a first look on Android 12 on the Z1 compact.
Download
SourceForge
Click to expand...
Click to collapse
Source Code: https://github.com/115ek/manifest
Changelog:
30.12.2021
initial release
reserved
I am amazed that you were able to do this. Thank you so much, and to the AICP team as well. I installed it and like to be able to see the new things even though the device is very old.
-FancyUsername- said:
I installed it and like to be able to see the new things
Click to expand...
Click to collapse
Did you find an appropriate GAPPS version?
tramp20 said:
Did you find an appropriate GAPPS version?
Click to expand...
Click to collapse
You could try https://github.com/BiTGApps/BiTGApps-Release/releases/tag/v1.7
However, I'm not sure if it still fits. Android gets bigger and bigger. No one thought about that 8 years back when amami was released.
Thank you.
This package has only 84 MB.
I will try LOS 19 with BiTGApps the next days.
No one has courage?
I tried the new ROM :-(
As usual: I made a backup of the system and a backup of the internal SDCard!
1. in TWRP (twrp-3.4.0-1-amami) factory reset and installing ROM + open_gapps-arm-12.0-pico-20211218-UNOFFICIAL_MOD.zip (at the same time)
2. reboot to LOS 19
3. configuring most things
noticed a not working bluetooth and missing NFC
missing "reboot to recovery" in extended power menu
4. shutting down and booted to recovery TWRP to make a first backup
TWRP showed only the welcome picture without menu and repeated this endless.
So I could not do a restore :-(
Then I flashed TWRP again with fastboot (even with a fastboot erase recovery) but this did not help.
After some tries I decided to flash the stock ROM with EMMA (all will be deleted incl. internal SDCard).
Flashed TWRP again and restored my LOS 18.1 backup and copied the int. SDCard back with MTP.
So after ~ 4 hours my Z1c was running again.
The next day I tried all again with the same disappointing result.
@tramp20 Sorry for the trouble.
If you get stuck at the TWRP bootscreen, connect an USB cable. Then
Code:
adb shell rm /data/system/storage.xml
adb reboot recovery
There's also a fix for this already. I just didn't pick it yet.
ref: https://github.com/chil360/android_...mmit/8016a9332ec85f05d539a892b2617517f9b3dbc1
Thank you.
I will wait for a new fixed ROM
Up front: Thanks a lot for still supporting this quite old but lovely phone.
As I am no pro I cannot say for sure, that I did not make any mistakes, but I can see the same issues regarding bluetooth and NFC as @tramp20. Also I can not find a camera in the system and therefore the flashlight is not available too.
I did not know, that there should be a button to reboot to recovery, but there is none on my amami right now with your ROM.
I am using the recommended BiTGApps.
I first flashed the ROM, then rebooted to recovery from twrp.
then i installed the BiTGApps and rebooted to recovery again. It just seemed right to me.
I rebooted to system and set everything up, then came across what i've described.
As I now know that there might be a fix for at least some of the issues I will wait for a possible new version of your ROM and try again.
Regards
spechaa
Hi, can anyone help how do I can fix lag issue on this rom?
Hello, i will be very glad to see new update ! If this ROM will rock stable like LOS 17.1/18.1 on my 6-7 years old Sony Xperia Z1c, it will be crazy awesome!
jurkoman said:
Hello, i will be very glad to see new update !
Click to expand...
Click to collapse
it looks not good :-(
[ROM][Unofficial][11.0][signed][OTA] Lineage OS 18.1 for Xperia Z1 compact
This thread aims at providing LineageOS 18.1 builds for the Sony Xperia Z1 compact with current security patches. You can consider this thread as a successor of our LineageOS 17.1 thread, where you may also find some useful information. This is...
forum.xda-developers.com
tramp20 said:
it looks not good :-(
[ROM][Unofficial][11.0][signed][OTA] Lineage OS 18.1 for Xperia Z1 compact
This thread aims at providing LineageOS 18.1 builds for the Sony Xperia Z1 compact with current security patches. You can consider this thread as a successor of our LineageOS 17.1 thread, where you may also find some useful information. This is...
forum.xda-developers.com
Click to expand...
Click to collapse
Hello, which one can you suggest more ? 18.1 or 17.1 ?
jurkoman said:
18.1 or 17.1 ?
Click to expand...
Click to collapse
Go for 18.1 it is very solid and receives updates. 17.1 is no longer maintained
has someone be able to get of that los recovery? its not detecting my phone via adb or fastboot to install twrp
ERIKW!§ said:
has someone be able to get of that los recovery? its not detecting my phone via adb or fastboot to install twrp
Click to expand...
Click to collapse
"los recovery" and "fastboot"? You know how to reboot your phone to the bootloader, and use fastboot, right?
You may want to study the installation instructions in the OP of this old thread - it's still valid afaik. Also the link to the relevant TWRP version and troubleshooting section in the same post could be of help
Good luck
Related
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on find7
Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want. Recommended nano package)
Official root addon
LineageOS Extras
Changelog:
Changes for find7
Bug reports:
How to submit a bug report
LineageOS JIRA
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to LineageOS
XDA:DevDB Information
Official LineageOS 15.1 for Find7a/s, ROM for the Oppo Find 7
Contributors
mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Any version of ColorOS. Unified storage not supported.
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-07-09
Last Updated 2018-11-15
Just curious. Are there any way for find 7 to install nano gapps? I keep on getting insufficient storage... Sad...
Am having problem of cold start gps. Takes about 8-10 mins before locking in. However, once lock in,everything work perfectly.
Updated on 18july.now everything is perfect. Even the battery life got better.
thank you???
luckywang95 said:
Just curious. Are there any way for find 7 to install nano gapps? I keep on getting insufficient storage... Sad...
Click to expand...
Click to collapse
You can delete the storage check in the installer script. Did it before and worked fine. I'm gonna try it tonight with this build.
Update: Stucked in bootloop. Gonna try tommorow again.
Update#2: Here is my working solution:
1. Flashing rom
2. Flashing addonsu
3. Flashing openGapps micro
Whats the perception about the Lineage<color>Accent.apks ?
They seemed to compromise my device and after removing these system aps
my find7 starts twice as fast as before.
In Settings->Apps they are all active but do nothing and their names are renamed like kakao lavendel kirsche carbon...
I'dont know whats this about,
but I feel Hacked and compromised by these apks!
Please explain what these apks are good for
and why it is stated in Settings->Apps that they do nothing else as being in background active
nor is anything protokollised from their activity!
I did a clean fresh install with these Custom Rom,
wiping all partitions and installing them with TWRP 3.2.2.0
With best regards Zoltan-X
P.S.: Find7 works better without these and no Errors are caused in usage so far!!!
Zoltan-X said:
Whats the perception about the Lineage<color>Accent.apks ?
They seemed to compromise my device and after removing these system aps
my find7 starts twice as fast as before.
In Settings->Apps they are all active but do nothing and their names are renamed like kakao lavendel kirsche carbon...
I'dont know whats this about,
but I feel Hacked and compromised by these apks!
Please explain what these apks are good for
and why it is stated in Settings->Apps that they do nothing else as being in background active
nor is anything protokollised from their activity!
I did a clean fresh install with these Custom Rom,
wiping all partitions and installing them with TWRP 3.2.2.0
With best regards Zoltan-X
P.S.: Find7 works better without these and no Errors are caused in usage so far!!!
Click to expand...
Click to collapse
Are you serious? These are just simple apks for the styles you can change from display settings.
If you are so curious about "being hacked" look at the source: https://github.com/LineageOS/android_packages_overlays_Lineage
Curios i've had in those app a data collecting folder structure,
like db, files, and more, maybe a rootkit on my device???
I don't know, since i removed those my find7 works again really well,
what it didn't do since a long time in this year....
With best regards
Code looks fine and i'll recheck if the image was compromised or not or how, but later these days.
thank you for the quick hint to those files!
P.S.: I've dirty reflashed the image i used to install lineageOS, after the expected remove, and no these nightly seems not been compromised,
Sorry for the alert,
but in the last days many hacks occured in my private relationships with my dearest, so I was a little curios, but seems now clean on my device!
Thank You verry much,
and Kudos Kudos Kudos to your quick hint reply.
I just installed lineage-15.1-20180806-nightly-find7-signed.zip to replace my stock Oppo Find7 firmware on the weekend and after a few days with it, so far so good! I had to lose the LVM unfortunately, but I'd rather have an up to date OS.
The battery life seems shorter than the stock firmware. I can still get through the day, but down to 40 or 50% or less by 6PM instead of much more with the stock Oppo FW. I haven't tried tweaking any battery life settings yet though.
Two minor things with the install compared to the LineageOS howto - the SD card path was different to what was documented ( /internal_sd not /sdcard) , and I had to install open_gapps-arm-8.1-pico-20180812.zip (pico instead of the documented nano version)... but this was minor stuff and I got where I wanted to go.
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
hexplor said:
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
Click to expand...
Click to collapse
Video recording is now working on latest AOKP Rom for Find 7. Google is your friend.
knusto said:
Video recording is now working on latest AOKP Rom for Find 7. Google is your friend.
Click to expand...
Click to collapse
Wooot ! They have nougat builds for find 7
hexplor said:
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
Click to expand...
Click to collapse
It will be fixed in next build.
mikeioannina said:
It will be fixed in next build.
Click to expand...
Click to collapse
Thank you so much. Can't wait
hexplor said:
Wooot ! They have nougat builds for find 7
Click to expand...
Click to collapse
AOKP is now on Oreo for Find 7
mikeioannina said:
It will be fixed in next build.
Click to expand...
Click to collapse
Got the latest build. All fine Thanks
Allthough its not supported i've got unified working. not reliable tho. the only way i got it working when flashing los and direct rebooting into recovery again and then flashing the cm-13.0-find7-unified-storage-patch.zip from the according thread. cuz the original link is dead incl mirror i got my copy uploaded to gdrive here. https://drive.google.com/file/d/1sZ72qUD5P7qL4tsIF3MB-cQk9x9pamRR/view?usp=sharing
only drawback being you cant reboot anymore cuz that will somehow give you the your-sdcard-is-****ed message. havent found a reasonable routine so i guess you'll have to try your luck yourself and maybe give feedback?
Hi, could you disable CABC(Content Adaptive Brightness Control) or provide a way to disable it? The hardware of Find 7 use it and it really makes some troubles, brightness, color. Really thanks if you have that time
I read that the problem of heavy games crashing on Bacon (Oneplus One) was resolved recently with this commit https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_bacon/+/218799/
I have the same problem with the Oppo Find 7/s (i.e. heavy games are crashing). As this device has the same processor and RAM as that of the Bacon, is it possible to get the same fix for Find 7 as well?
Manas1796 said:
I read that the problem of heavy games crashing on Bacon (Oneplus One) was resolved recently with this commit https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_bacon/+/218799/
I have the same problem with the Oppo Find 7/s (i.e. heavy games are crashing). As this device has the same processor and RAM as that of the Bacon, is it possible to get the same fix for Find 7 as well?
Click to expand...
Click to collapse
That commit has already been applied for Find7 - https://github.com/LineageOS/androi...mmit/80e1e7e5ffca2c69730eecc8c498423c2ea48463
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 ?
[ROM][9.0][OFFICIAL] LineageOS 16.0 for Wileyfox Swift
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on crackling
IF YOU ARE CURRENTLY RUNNING LINEAGE 15.1 w/ENCRYPTION A FULL DATA FORMAT WILL BE REQUIRED TO MOVE TO 16.0. AN ISSUE WITH ENCRYPTION WAS FOUND IN 15.1 THAT CANNOT BE CORRECTED WITHOUT A FULL FORMAT
Official Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want)
Changelog:
Changes for crackling
Bug reports:
How to submit a bug report
Donate to support development:
Donate via PayPal to jrior001
Donate via PayPal to LineageOS
XDA:DevDB Information
LineageOS, ROM for the Wileyfox Swift
Contributors
jrior001, mikeioannina, 115ek
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2019-04-15
Last Updated 2020-03-29
@jrior001 Thats great news. Thanks for all your hard work! Much appreciated.
Can you say some words about the encryption problem? What was wrong with LOS' 15.1 way of doing it?
I saw you reverted the GPS blobs. Does that mean GPS fixing is faster now?
Edit: As to my question that I posted initially: Seems the problem is in front of the screen, found the answer already...
morita11 said:
@jrior001
Can you say some words about the encryption problem? What was wrong with LOS' 15.1 way of doing it?
I saw you reverted the GPS blobs. Does that mean GPS fixing is faster now?
Click to expand...
Click to collapse
We missed a change in 15.1 prior to it shipping that pretty much put every legacy device using he encryption in a bad place that can't be recovered from.
For gps, yes it does seem to be locking faster and tracking better while driving.
Sent from my Mi MIX 2S using Tapatalk
Patiently waiting for feedback before I update the phone of my wife. She's still using LOS 14.1, is it possible to update to LOS 16 (the phone is encrypted)?
Obscurax said:
Patiently waiting for feedback before I update the phone of my wife. She's still using LOS 14.1, is it possible to update to LOS 16 (the phone is encrypted)?
Click to expand...
Click to collapse
Its possible that may work, but it is not a tested and supported upgrade scenario. I would highly advise taking every necessary backup precaution should you attempt that.
Sent from my Mi MIX 2S using Tapatalk
What is the latest bootloader LineageOS works with?
I can confirm that it doesn't boot when coming from the last stock firmware:
Code:
ro.build.display.id=TOS373K - N2G48B
Regarding TWRP
Thanks a lot @jrior001 for giving us LineageOS 16!
Before I update, I have a few questions regarding TWRP:
What's the difference between the TWRP version linked in the wiki and the official one? When upgrading to 15.1, the official version did not work
Will TWRP be able to read encrypted partitions or does it still suffer form the problem you mentioned here: https://forum.xda-developers.com/showpost.php?p=77967754&postcount=111
Regards,
Zapp
zappbrannigan62 said:
Thanks a lot @jrior001 for giving us LineageOS 16!
Before I update, I have a few questions regarding TWRP:
What's the difference between the TWRP version linked in the wiki and the official one? When upgrading to 15.1, the official version did not work
Will TWRP be able to read encrypted partitions or does it still suffer form the problem you mentioned here: https://forum.xda-developers.com/showpost.php?p=77967754&postcount=111
Regards,
Zapp
Click to expand...
Click to collapse
The one from the wiki decrypts 16.0 and 14.1 but nothing will decrypt 15.1.
Keep in mind the big red note in the OP if you are encrypted on 15.1, a full wipe/format will be requited to move to 16.0.
Sent from my Mi MIX 2S using Tapatalk
Upgrading to 16 directly from 14.1 worked for me, no issue with encryption :good:
Awesome guys. Finally we have gps again. Thanks thanks thanks.
I did run into an issue today. I was making videos and photos of hawaiian hula performance and after that of my girlfriend with a beautiful hawaiian sunset in the background. It turned out to be to much beauty for the phone as it rebooted when trying to make a photo. After the phone turned on again all the videos and photos where nowhere to be found. That is all the info i can give at this moment. When i find out more i will give an update.
Update: The reboots occur very frequently when using the photo app. I have to say that I flashed over LOS 15.1. Am I the only one with these issues or can other people confirm the bug?
Update2: Just saw that I had HDR enabled. That might have been the problem.
I got a similar problem:
after upgrading from 15.1 to 16.0 following the howto under - removed - I get sometimes - it doesn't seem to be correlated with the use of a certain app - a very annoying crash:
The display goes black, then it shows the Lock Screen for one second, then it goes dark again... and so on.
There is no other solution than opening the case, removing the battery, putting the battery back again and then starting the phone.
This is a really really annoying bug, much more annoying then the occasional reboots of LineageOS 15.1.
Please fix that. I am willing to support the develpers with any informations, if somebody tells me what to do.
jrior001 said:
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on crackling
Click to expand...
Click to collapse
I followed the instructions from the link exactly and now I have spent the long weekend looking to fix:
"Failed to mount '/system' (No such device)"
I installed TWRP (3.3.0-0) per this post (https://forum.xda-developers.com/wil...1/post72537703) and I am trying to install lineage os, which fails with:
"Updater process ended with ERROR: 7"
And then the above in response to "Updating partition details".
NotATechnician said:
I followed the instructions from the link exactly and now I have spent the long weekend looking to fix:
"Failed to mount '/system' (No such device)"
I installed TWRP (3.3.0-0) per this post (https://forum.xda-developers.com/wil...1/post72537703) and I am trying to install lineage os, which fails with:
"Updater process ended with ERROR: 7"
And then the above in response to "Updating partition details".
Click to expand...
Click to collapse
The latest recommended twrp is linked on the lineage wiki, https://wiki.lineageos.org/devices/crackling/install
If you still get errors, please post the entire message. "ERROR 7” is a general assert failure but if you read the rest of the message it usually tells you why it failed. If it doesn't make sense post it here or pull the recovery.log and post that here for me.
"adb pull /tmp/recovery.log" will pull the log.
Sent from my Mi MIX 2S using Tapatalk
jrior001 said:
The latest recommended twrp is linked on the lineage wiki, https://wiki.lineageos.org/devices/crackling/install
If you still get errors, please post the entire message. "ERROR 7” is a general assert failure but if you read the rest of the message it usually tells you why it failed. If it doesn't make sense post it here or pull the recovery.log and post that here for me.
"adb pull /tmp/recovery.log" will pull the log.
Click to expand...
Click to collapse
Thanks! I did "fix" it in the meantime...
For the record, the version of TWRP is the latest (at current time of writing). But for anyone else stumbling on the thread for a fix..
I took the heavy-handed approach, not only wiped the /system partition, but reformatted as ext4 (it was previously splashfs)
Flashed Lineageos 16, GApps-9-arm64.nano, and the root add-in, wiped Dalvik and Cache, reboot to System.
But it only rebooted to Bootloader, no matter how I did it. So then I flashed crDroid4.7 just because it was in the folder even though I knew nothing about it. Wipe Dalvik&Cache, reboot to system and happy days, it chugged for a while before giving me a new set-up experience.
So, I flashed the Pie crDroid (5.3) and I am off to the races. crDroid is LineageOS based, so do not ask me why one boots and the other does not, but my Crackling Wileyfox has life again. So, I am somewhat using LineageOS and very grateful for all the people who put the work in.
NotATechnician said:
For the record, the version of TWRP is the latest (at current time of writing).
Click to expand...
Click to collapse
Might be that the latest version is not the latest 'recommended' version of TWRP? Have you tried 3.2.3.0?
kabu83 said:
Might be that the latest version is not the latest 'recommended' version of TWRP? Have you tried 3.2.3.0?
Click to expand...
Click to collapse
Latest, 3.3.0-0, works for me with no issues.
Sent from my Wileyfox Swift using XDA Labs
Is this rom SELinux Enforcing?
dedaol said:
Is this rom SELinux Enforcing?
Click to expand...
Click to collapse
Enforcing is mandatory on lineage officials.
Sent from my Mi MIX 2S using Tapatalk
I can't get it working, it always fails at 47%. I tried different builds and it's always the same problem. I format the data and wiped cache & system before I did the sideload. TWRP version is the one from the lineageos wiki.
Any idea what could be the problem?
Thanks!
Code:
C:\WINDOWS\system32>adb sideload lineage-16.0-20190429-nightly-crackling-signed.zip
serving: 'lineage-16.0-20190429-nightly-crackling-signed.zip' (~47%) adb: failed to read command: No error
Edit: found this link https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47 and I'll try it tomorrow again.
Edit2: didn't work. Copied the build and opengapps Pico to the SD card and flashed it via TWRP. Worked and the phone runs again.
Persistent mobile network issue
I upgraded from 15.1 to 16.0 at the first opportunity. Upon returning to France from a trip to neighbouring Switzerland I saw that my French mobile service had automatically switched to piggy-backing on it's Swiss roaming partner. This has cost implications and so I've now restored my previous installation of 15.1.
The problem I have with ver. 16 is that I cannot manually select the mobile network. Has this affected anyone else?
LineageOS 17.1 is a free, community built, aftermarket firmware distribution of Android 10.0 (Q), which is designed to increase performance and reliability over stock Android for your device.
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.
*
*/
LineageOS 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Known bugs:
Fantom icons in launcher after installing/updating apps. Fixed since 2020-03-18 build.
Expanded desktop doesn't work. LineageOS team planning to remove this feature entirely. This feature was removed in latest builds.
For some users phone won't boot after installing Magisk. Right now there is no solution. Use rom without Magisk. Fixed since 2020-02-22 build. Credits to @Sashko98 for help!
Screen timeout does not work if the Screen lock is set to none. Fixed since 2020-05-31 build.
Random drops of the bluetooth connection. Fixed since 2020-06-13 build.
Screen mirroring via slimport HDMI adapter doesn't work.
PMF aka 802.11w doesn't work.
Downloads:
ROM: https://sourceforge.net/projects/hammerhead-lineageos/files/17.1/
GAPPS: https://opengapps.org/?arch=arm&api=10.0&variant=pico
Credits:
Many thanks to the LineageOS team and all the contributors out there in the community
Contributors:
@z3DD3r, @EnesSastim, @Sashko98, @razorloves, esa-n, jprimero15 and others
Source Code:
Device tree: https://github.com/z3DD3r/android_device_lge_hammerhead/tree/lineage-17.1
Kernel tree: https://github.com/z3DD3r/android_kernel_lge_hammerhead/tree/lineage-17.1
Vendor tree: https://github.com/z3DD3r/android_vendor_lge/tree/lineage-17.1
Android version: 10.0.0 (Q)
Kernel version: Linux 3.4.113
SELinux: Enforcing
Status: Stable
Created 2020-01-23
Last Updated 2020-06-23
GAPPS Installation
To install GAPPS you should increase the /system partition size
This can be done for example with TWRP HH.R
[RECOVERY][UNOFFICIAL] TWRP HH for Nexus 5 (hammerhead)
TWRP HH for Nexus 5 About: 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...
forum.xda-developers.com
Also LineageOS Team have recommendations about GAPPS
Here are the most important two copied from LineageOS WiKi:
If you opt to use Open GApps, they offer a variety of sizes of packages that include and overwrite different apps. We only recommend package sizes up through nano. If you use a larger package, we can not guarantee that everything will function on your device, as in many of these cases our included apps are overwritten in favor of the Google App equivalents.
Google apps should be installed via recovery immediately after installing LineageOS. If you reboot into LineageOS before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
reserved
Thanks for your work.
I'm running 17.1-20200122. Works amazingly well so far. No bugs detected.
Thank you @z3DD3r for your amazing work for Hammy
Hardware Macaddress
Thanks for this amazing rom which is super fast. I am unable to connect to my home WiFi with static ip.
My configuration is - Nexus 5 32 GB, Rom 24 Jan, Open Gapps Nano 23 Jan, TWRP system repartioned to 2GB..
Unable to disable Mac randamnization....can’t find any toggle.hence unable to use hardware MAC address.
Kindly advise a fix. Thanks in advance.
zheega said:
I'm running 17.1-20200122. Works amazingly well so far. No bugs detected.
Click to expand...
Click to collapse
How is the battery-drain for you? I tried an earlier version and that wasn't nice regarding battery. Almost half the time compared to the 16.0.
I've just run a single charge on the last build, but seems good so far. Better than 16.0 I would say.
Encryption working flawlessly !!!
Beta TWRP decrypts DATA in recovery !!! (carefully read instructions and posts.)
Excellent work, everybody.
anilspice said:
Thanks for this amazing rom which is super fast. I am unable to connect to my home WiFi with static ip.
My configuration is - Nexus 5 32 GB, Rom 24 Jan, Open Gapps Nano 23 Jan, TWRP system repartioned to 2GB..
Unable to disable Mac randamnization....can’t find any toggle.hence unable to use hardware MAC address.
Kindly advise a fix. Thanks in advance.
Click to expand...
Click to collapse
Static ip works for me and I dont have mac randomization.
I dirty flashed from lineage-16.0-20191225 to 17.1-20200124 and wiped cached/davik. Everything seems fine (old apps, lte, camera, wifi). Only thing I miss is homescreen icon grid is max 5x5, I liked 5x7. Nice work!
I'm trying to flash the rom to my nexus5 with twrp. The installation went ok, but when i boot, it seems to stuck at the loading screen (blue ball going from right to left). Am I doing something wrong?
anilspice said:
Thanks for this amazing rom which is super fast. I am unable to connect to my home WiFi with static ip.
My configuration is - Nexus 5 32 GB, Rom 24 Jan, Open Gapps Nano 23 Jan, TWRP system repartioned to 2GB..
Unable to disable Mac randamnization....can’t find any toggle.hence unable to use hardware MAC address.
Kindly advise a fix. Thanks in advance.
Click to expand...
Click to collapse
Mac randomization is disabled cos our device doesn't support it. Have u been able to connect to your WiFi on LOS 16? Can u send me logcat?
Toedels said:
I'm trying to flash the rom to my nexus5 with twrp. The installation went ok, but when i boot, it seems to stuck at the loading screen (blue ball going from right to left). Am I doing something wrong?
Click to expand...
Click to collapse
Looks very strange. Have u wiped your partitions before installation? Tell me version of TWRP and versions of ROM, GAPPS and Magisk you tried to install.
z3DD3r said:
Mac randomization is disabled cos our device doesn't support it. Have u been able to connect to your WiFi on LOS 16? Can u send me logcat?
Looks very strange. Have u wiped your partitions before installation? Tell me version of TWRP and versions of ROM, GAPPS and Magisk you tried to install.
Click to expand...
Click to collapse
I'm a little further. I've installed lineage-17.1-20200119-UNOFFICIAL-hammerhead.zip and it's booting. But when i want to install open_gapps-arm-10.0-pico-20200124.zip, it says there's not enough space.
Did you resize your partition?
EnesSastim said:
As 07/19 u have to resize, here is the tutorial:
How to increase system (assuming that u have unmodified partitions):
1. Flash twrp-3.3.1-HH-hammerhead.img
2. Open terminal (TWRP -> Advanced -> Terminal)
3. Type hh_repart -m
4. Wait until your phone reboots.
How to revert everything:
1. Open terminal (TWRP -> Advanced -> Terminal)
2. Type hh_repart -r
3. Wait until your phone reboots.
4. Install original TWRP (3.3.1-0 at the current moment)
Download: https://mega.nz/#!x840QaZT!zjxqy1mK07u--T0Jt4451BLiwmpELe4GFdgW-20s4zc
Credits: @z3DD3r
Click to expand...
Click to collapse
Toedels said:
I'm a little further. I've installed lineage-17.1-20200119-UNOFFICIAL-hammerhead.zip and it's booting. But when i want to install open_gapps-arm-10.0-pico-20200124.zip, it says there's not enough space.
Click to expand...
Click to collapse
This old build is permissive and device is not certified in Play Market. Use build 20200123 or newer cos they are enforcing.
z3DD3r said:
Mac randomization is disabled cos our device doesn't support it. Have u been able to connect to your WiFi on LOS 16? Can u send me logcat?
Thanks for response. Had earlier been using crdroid pie rom till Nov 2019 with system partition extended to 1.5 GB and Micro gapps. All was fine till then. As I usually keep on updating the apps regularly..In Dec 19 wifi stopped working. I thought had a hardware failure. The hammerhead kept on going without wifi as it was not a daily driver. In Jan I repartioned the sys again to 2GB using TWRP 3.3.1-2.0GB HH and installed LOS 17.0 with stock gapps as I had enough space. It worked with few minor issues then i kept on upgrading every day as you kept on building now on 25 th Jan 17.1 LOS with 16jan stock gapps.
All builds worked perfectly...but without wifi, which used to trun on sometimes after I copied .mcaddr from /persist to /data/misc/wifi folder through TWRP file manager...but is still unable to download or update data and automaticaly switches back to cellular data.
As far as logcat...kindly advise how to!! As I had never done that.
I am not a developer or IT guy. Hope above helps.
Regards
Added info: Had gone back to stock and installed TWRP HH 1.5 Gb few times. Installed LOS 16 to but the same issue remains...unable to connect to my home static IP as my wifi is hidden and all devices on my home network have individual IP address.
Click to expand...
Click to collapse
Somebod y said:
Did you resize your partition?
Click to expand...
Click to collapse
That did the trick! I'll try to install the latest version now.
It feels really smooth. Didn't expect that on such old device.
There's an article about your ROM on German ZDNet. Hope to see this eventually being official one day.
https://www.zdnet.de/88376265/lineageos-android-10-fuer-nexus-5/
wifi does not work, cannot connect !!
.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
What's working?
Stuff
What's not working?
Enforcing
Other stuff
Installation
1. Boot into twrp
2. Advanced -> ADB Sideload -> Swipe
5. adb sideload lineage.zip
6. Wipe Data
7. Profit?
Downloads: https://1pwn.ixmoe.com/android/surfna/Lineage18.1-Mod/
Notes
This ROM comes with Google Apps!
This ROM comes with Customizations that are not apart of LineageOS
Source: https://github.com/electimon/VoidKramel/tree/Void-moto-4.9-redo
Credits: @electimon, @erfanoabdi, @SyberHexen
Updated: 06/20/2021
June Patch and userdebug
I have the T-Mobile version of this phone, with the a ramdisk-enabled Magisk-patched boot image, and working touch recovery.
I tried this lineage 18 rom, and ended up in a boot loop. I noticed that your lineage 18 treble version includes new vendor and boot images. This was not clear in the instructions.
Recently, I successfully installed a phh-aosp 11 gsi system image only on this phone with no issues. I had to disable superuser after booting up the first time, because magisk is installed in the boot image, but otherwise no problems. No need for new vendor or boot images. Hope this info helps. Thanks for all of your work on the Moto E6.
There is a need for the new boot and vendor images because this is a 64BIT ROM not a 32BIT ROM like stock and the GSIs, and why do you tell me this without providing any kinds of logs. Also this is NOT A GSI, it is a source built ROM, thanks.
Thanks for clarifying. I wll try again and have some logs.
Update: I tried to install both roms. Rom v2 boot looped. Rom v1 stayed on G symbol. I waited 20 minutes on that one, but no change. I did install magisk.zip both times. Perhaps that is the problem. I don't know how to save logs prior to actually booting the rom. Thanks.
Update 2: No difference with or without magisk installed into boot image.
Just for the record, I installed this and I've booted into the OS. Now I want to see if I can get microG on here.
@Electimon I'm pretty sure I can't install microG because Gapps leaves no space for microG to be installed, and the OrangeFox recovery isn't mounting system so I can't resize it. Can you make a LineageOS version without gapps installed, or can uninstalling Gapps suffice?
Another update: While I could never get LineageOS and microG to work, one stunning thing that I discovered is that if you install this ROM, you can now use arm64 A/B GSI ROMs. This opens up the possibilities immensely as I reckon arm64 a/b GSIs will be around way longer than anything else.
Absence of com.android.documentsui means that when you are trying to choose folders for an application, there is no application available to do so. This results in crashes when you are trying to do something such as giving external SD card support to an application.
Had to go back to 32 bit because using power button seems to force restart on my phone. I'm sure I'm the only one with this issue
@Electimon will it work on E6 Play too?
do u plan to rls it without gapps (I can install some of my choosing later, right)?
@koyo @scottyrick2 managed to run it?
if not what other solution did u come up with/rom (maybe stock+micro?)
Also do i need those too & why? https://forum.xda-developers.com/t/recovery-unofficial-orangefox-r11-x-64bit-f2fs.4293397/ & https://forum.xda-developers.com/t/e6-aio-toolkit-mod-release.4122643/ & https://forum.xda-developers.com/t/experimental-twrp-dirty-port-for-moto-e6.3976715/
The post says moto e6 only.
Electimon said:
The post says moto e6 only.
Click to expand...
Click to collapse
Could You fix one for Play too?
My country only sell those ;( Thanks
kamolinkaaa said:
@Electimon will it work on E6 Play too?
do u plan to rls it without gapps (I can install some of my choosing later, right)?
@koyo @scottyrick2 managed to run it?
if not what other solution did u come up with/rom (maybe stock+micro?)
Also do i need those too & why? https://forum.xda-developers.com/t/recovery-unofficial-orangefox-r11-x-64bit-f2fs.4293397/ & https://forum.xda-developers.com/t/e6-aio-toolkit-mod-release.4122643/ & https://forum.xda-developers.com/t/experimental-twrp-dirty-port-for-moto-e6.3976715/
Click to expand...
Click to collapse
No I didn't. I'm in the process of selling the phone because it wouldn't work. Got a Moto G Fast instead for the same price
kamolinkaaa said:
Could You fix one for Play too?
My country only sell those ;( Thanks
Click to expand...
Click to collapse
I don't have the device
koyo said:
No I didn't. I'm in the process of selling the phone because it wouldn't work. Got a Moto G Fast instead for the same price
Click to expand...
Click to collapse
Oh u so lucky, can't get Moto G Fast here...so am gonna buy E5 Plus
Electimon said:
I don't have the device
Click to expand...
Click to collapse
Is there an option to buy E6 in Your area and send to me (& hm root it w Your rom), please?
Or maybe I can warp E6 Play to You and u could create a rom for it too hmm
Discontinued, los-modded 12 is coming soon
No one wants this phone so I'm stuck with it. Hopefully LOS 12 will fix the problems with LOS 11
thank you @Electimon for building this ROM! i have successfully flashed it to a Visible Moto E6 and works just fine for my needs. I used OrangeFox recovery to get to this stage. Flashed Magisk v23.0 afterwards and that works just fine as well.
just wondering, was there a specific reason you went with Google GO apps instead?
keep up the good work and look forward to Android 12 LOS ROM. reset my XDA password and logged on just to express my appericiation and grattidue for your work. thanks again.
desidude2000 said:
thank you @Electimon for building this ROM! i have successfully flashed it to a Visible Moto E6 and works just fine for my needs. I used OrangeFox recovery to get to this stage. Flashed Magisk v23.0 afterwards and that works just fine as well.
just wondering, was there a specific reason you went with Google GO apps instead?
keep up the good work and look forward to Android 12 LOS ROM. reset my XDA password and logged on just to express my appericiation and grattidue for your work. thanks again.
Click to expand...
Click to collapse
I went with GO GApps because surfna is limited in RAM, it would not be good with full gapps, no RAM left for system. Thank you for using my work!!