Related
Q&A for [ROM] CosmicROM [AOSP] [5.1] [DarkUI] [22 Mar 2015]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] CosmicROM [AOSP] [5.1] [DarkUI] [22 Mar 2015]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Unable to flash cosmic 5.1 status 7 error
i tried flashing the rom but i got a status 7 error, plz note that i m using an updated recovery and also i have also increased the internal memory of my i9082 in reference to another thread by @k2wl . plz help. the error says this rom is for i9082 and this device is a baffin. what should i do?
open zip then go to /META-INF/com/google/android/ folder and open updater-script with notepad++ or some editor compatible with linux style.
delete first line
" getprop("ro.product.device") == "i9082" || abort("This package is for "i9082" devices; this is a "" + getprop("ro.product.device") + "".");
"
and save file in zip again or if ask update it.
Thanks
dydy_vova said:
open zip then go to /META-INF/com/google/android/ folder and open updater-script with notepad++ or some editor compatible with linux style.
delete first line
" getprop("ro.product.device") == "i9082" || abort("This package is for "i9082" devices; this is a "" + getprop("ro.product.device") + "".");
"
and save file in zip again or if ask update it.
Click to expand...
Click to collapse
thx bro had the same problem will test it nd let u know
getting status error 7 even after flashing the recovery given by you.
error is saying is saying that yours is a baffin. currently i am using cosmic cm version 5.5 buld number KTU84Q.
i cant flash CosmicROM..with recovery philz touch
DJ Minh Bu said:
i cant flash CosmicROM..with recovery philz touch
Click to expand...
Click to collapse
please elaborate on the problem....is their any error message while installation ?
SMS
Hello.
Can I choose an operator for sending SMS, as well as with calls. ("Always ask")
waiting for the update
@k2wl bro wers the new update file we people are eagerly waitin for it dont take me wrong dude bt we all are huge fans of cosmic rom as well as your work hope we get to see the new file soon and we dont have to wait more and great work broda respect for u
Error 7 in build 20150323
@k2wl I downloaded your latest build of 23rd march still m stuck with the same status 7 error i even flashed my recovery again bt still with same trouble help me out as i badly love this rom
can i flash 5.0 gapps on this rom??????
Hello sir, can I flash lollipop 5.0 supported gapps on cosmic 5.1 ROM??????????
Still getting an error
I'm getting Baffin Error
I downloaded the new build posted but ain't working
Any solutions???
aaronjgeorge123 said:
I'm getting Baffin Error
I downloaded the new build posted but ain't working
Any solutions???
Click to expand...
Click to collapse
See post #4 and edit the script and it works
File Manager
I can't find File Manager in this ROM (cosmis 5.1). Please tell me how about it
azri harahap said:
I can't find File Manager in this ROM (cosmis 5.1). Please tell me how about it
Click to expand...
Click to collapse
Pick your favorite file manager from the play store and download it.
You can't find one the rom because there is no file manager included.
The file manager is a CM feature not AOSP, so you will miss more thing
See that is so hard
A small problem
In the 2nd update of this rom the status 7 error was not resolved....so i have tried removing the first line from the updater script....but then after installing and rebooting android logo flashes for a very long time...still not having any luck with it....i have used notepad++ to do all the updating and then again compressed all the files into a zip file....please tell me if i am doing something wrong or if i am missing something....
RichyE said:
Pick your favorite file manager from the play store and download it.
You can't find one the rom because there is no file manager included.
The file manager is a CM feature not AOSP, so you will miss more thing
See that is so hard
Click to expand...
Click to collapse
since cm 12 I never flash GAPPS. I prefer the '1 mobile market' in the hope that is in use less RAM. how do I can have a file manager without having to flash GAPPS? Please help me...
azri harahap said:
since cm 12 I never flash GAPPS. I prefer the '1 mobile market' in the hope that is in use less RAM. how do I can have a file manager without having to flash GAPPS? Please help me...
Click to expand...
Click to collapse
search for file manager in the 1mobile market and you will get allot to choice from
For example
ES File Explore
Solid Explorer
Pls help....
Pls help....
How to root (manual) for galaxy grand duos i9082 - CosmicROM [AOSP] [5.1] ?
Is this ROM support otg cable
I hope to be really
Q&A for [ROM] [Anzu][Uber 4.9] AICP - 10.0 - LP 5.1.1_r6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [Anzu][Uber 4.9] AICP - 10.0 - LP 5.1.1_r6. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
there's a lil bugs
-i cant pull down noti drawer fully.
-lock screen is not working but when you put a password it will work.
Great rom BTW
zhedrhick said:
there's a lil bugs
-i cant pull down noti drawer fully.
-lock screen is not working but when you put a password it will work.
Great rom BTW
Click to expand...
Click to collapse
you may want to try and reflash the rom' i don't have the bugs you mention
plz help
i couldnot flash this rom..
1st i bought a new sd card and now had partition 2GB ext4..
i follow these steps :
Enter recovery
Wipe every thing
Format /system, then /data and then /cache
and when i click on install zip and choose the rom ...... the following appears:
finding update package...
opening update package...
installing update...
detected file system ext4 for /dev/block/mmcblk0p2
then stay at this line fora long time and at last the following appears:
symlink: some symlink failed
E:Error in /storage/sdcard0/aicp_anzu_lp-10.0-NIGHTLY-20150720.ZIP (Status 7)
Installation aborted
my previous rom was cr droid kitkat ..
Any idea for helping plzzz
thanks
error
How to flash :
•Don't do it if you don't know it
---pretty strange instructions. Now tell me, if somebody who "does not know" tries to install your rom without full knowledge of the installation process and this procedure would damage his cell phone in the way he would not be able to "repair" this on his own....?Nothing good would happen of course... I am not getting this policy of yours, because I think that nobody could know about all of the installation procedures of all of the available custom roms. I tried to install your rom instead of previously installed resurrection remix 5.1.1. My sdcard is partitioned as FAT32 primary, EXT4 primary and 256MB linux swap partitions. Your rom was installed via latest cyanogenmod recovery. After maybe 5 seconds of the process I got 2 error messages, some of the rare ones, do not remember exactly...Post full description of the install procedure pls.
emillyWse said:
How to flash :
•Don't do it if you don't know it
---pretty strange instructions. Now tell me, if somebody who "does not know" tries to install your rom without full knowledge of the installation process and this procedure would damage his cell phone in the way he would not be able to "repair" this on his own....?Nothing good would happen of course... I am not getting this policy of yours, because I think that nobody could know about all of the installation procedures of all of the available custom roms. I tried to install your rom instead of previously installed resurrection remix 5.1.1. My sdcard is partitioned as FAT32 primary, EXT4 primary and 256MB linux swap partitions. Your rom was installed via latest cyanogenmod recovery. After maybe 5 seconds of the process I got 2 error messages, some of the rare ones, do not remember exactly...Post full description of the install procedure pls.
Click to expand...
Click to collapse
flash it just like cm12.1 that it
afi1982 said:
flash it just like cm12.1 that it
Click to expand...
Click to collapse
I tried again today, I even used the system formatting tool, which I forgot to use before, but I just got 2 error messages again...one of them was signature verification error. Actually I am using Resurrection Remix ROM (5.1.1), sdcard is partitioned ext4, fat32 and linux swap...I am using cyanogen touch recovery...
emillyWse said:
I tried again today, I even used the system formatting tool, which I forgot to use before, but I just got 2 error messages again...one of them was signature verification error. Actually I am using Resurrection Remix ROM (5.1.1), sdcard is partitioned ext4, fat32 and linux swap...I am using cyanogen touch recovery...
Click to expand...
Click to collapse
are you using my kernel ?
afi1982 said:
are you using my kernel ?
Click to expand...
Click to collapse
Hi, I am using kernel 3.4.0-LX+ ([email protected]) (gcc version 4.7 (GCC) ) 1 PREEMPT Mon May 11 12:34:52 CEST 2015...hope it is been the right one. Thanks for the answer...and something else just came on my mind...maybe I did not mentioned my cell phone type yet... , it is been good old SE LT18i ARC S.
emillyWse said:
Hi, I am using kernel 3.4.0-LX+ ([email protected]) (gcc version 4.7 (GCC) ) 1 PREEMPT Mon May 11 12:34:52 CEST 2015...hope it is been the right one. Thanks for the answer...and something else just came on my mind...maybe I did not mentioned my cell phone type yet... , it is been good old SE LT18i ARC S.
Click to expand...
Click to collapse
no you need to use cm11 LX kernel the latest.
afi1982 said:
no you need to use cm11 LX kernel the latest.
Click to expand...
Click to collapse
Ok, thanks for the answer. I'll give it a try.
Hai can u upload gapps , ling die
LineageOS 15.1 fails to install on OnePlus 3T: "assert failed: op3.verify_modem..."
I'm trying to install LineageOS 15.1 on a OnePlus 3T (previously running 14.1). I've tried both
Code:
https://mirrorbits.lineageos.org/full/oneplus3/20180226/lineage-15.1-20180226-nightly-oneplus3-signed.zip
and
Code:
https://mirrorbits.lineageos.org/full/oneplus3/20180225/lineage-15.1-20180225-experimental-oneplus3-signed.zip
. In both cases, I get the following errors:
(1) If I check "Zip signature verification", then I see:
Code:
Verifying zip signature...
Zip signature verification failed!
The sha256 checksum on the zip file itself is correct.
(2) If I don't check the "Zip signature verification" option, then I see:
Code:
assert failed: op3.verify_mode("2017-11-16 04:58:57") == "1"
Updated process ended with ERROR: 7
Has anyone else encountered these problems? Any suggestions as to what I can do to further diagnose things?
Thanks!
larsks said:
I'm trying to install LineageOS 15.1 on a OnePlus 3T (previously running 14.1)...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device. Though it states 14.1, typically those threads take on the 15.1 releases until either a new thread is created or that threads title gets changed.
https://forum.xda-developers.com/showthread.php?t=3496850
If all else fails, and you don't receive any responses from the above thread, you can always post your question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3509641
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
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?