Lineage 16.0 now available from here
https://download.lineageos.org/crackling:laugh:
for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
upd: yes, my bad, for me 15.1 also doesn't work, so it is on my side.
upd: I did this to fix it: https://forum.xda-developers.com/showpost.php?p=66158015&postcount=2) as I understand I downgraded fastboot to be cynogen, from los
ilya_m said:
for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
Click to expand...
Click to collapse
You may have to sideload it if coming from 15.1
ilya_m said:
for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
Click to expand...
Click to collapse
Are you using the nougat bootloader? Try downgrading to any of the COS13 firmwares then flashing.
FWIW though this is a bug with LOS since beroid's crDroid works fine with the newer bootloader. Same with his TWRP (this bug does exist in OrangeFox Recovery which suggests it's a software thing).
Works, but I'd stay to 15.1
The ROM works fine for me. Everything, the camera, talks work fine. But I don't know if it's just me but my phone runs pretty slow on the new ROM, without any of my apps installed.
I've installed it on my Swift which has TWRP 3.3.1 with no issues.
The issue started when I wanted to install OpenGapps pico. I get error 70, saying I have no space.
I've tried a lot of things I've found online, including wiping everything (full wipe, including any and all partitions, /data, /system, and everything else), resizing the /system partition (still only 1511MB).
I've searched this Swift sub-forum, and have not found a solution. Is my search failing me?
I still get error 70 when I try to install OpenGapps, saying there's not enough space.
Anything else I can try?
romanboy said:
I've installed it on my Swift which has TWRP 3.3.1 with no issues.
The issue started when I wanted to install OpenGapps pico. I get error 70, saying I have no space.
I've tried a lot of things I've found online, including wiping everything (full wipe, including any and all partitions, /data, /system, and everything else), resizing the /system partition (still only 1511MB).
I've searched this Swift sub-forum, and have not found a solution. Is my search failing me?
I still get error 70 when I try to install OpenGapps, saying there's not enough space.
Anything else I can try?
Click to expand...
Click to collapse
Are you installing the GApps in TWRP immediately after the LOS Installation, prior to booting into LOS?
Have you tried the nano instead the pico?
I followed the instructions at https://wiki.lineageos.org/devices/crackling/install using twrp 3.2.3 as instructed. I used MindThe Gapps 9.0 as I saw somewhere (as romanboy above found) that standard Gapps gives error 70 (not enough space) even for nano version. Swift boots into LOS 16 after some time but it keeps displaying popup about Pixel Setup keeps stopping: I can only show App Info (with Force Stop option) or Close app: either case results in popup appearing again. I've asked the author of the above wiki (on reddit #LineageOS) but no reply.
I started again by installing cm13.2 then used twrp 3.2.3 to install LineageOS16.0 followed by OpenGapps 9 pico. All now Ok.. So MindTheGapps 9.0 is no good.
Camera not working, flashed with latest TWRP.
Official Rom
LaneyUK said:
Camera not working, flashed with latest TWRP.
Click to expand...
Click to collapse
There is now an official lineage Rom
https://download.lineageos.org/crackling
Related
hello,
(with "this rom" i mean >sultan cm13<. I edited the title, before that it "was can't but sultan cm13", but now i know it doesnt boots any aosp roms)
a few days ago i used this rom as secondary with multirom (primary was freedom 1.10). now today, i wanted to use this rom as my dailydriver rom. i made the normal procedure, making a backup, then wiping the partitions (system, data, cache, dalvik) and after it flashing the rom. on the first try, i did it like i usually do, first the rom, then the gapps and then xposed. then i rebooted, and it was stuck on the 1+ logo screen about 10 mins. then i reflashed it, but just the cm.zip. then i still got stuck.
i tried it with the unofficial and the official twrp recovery. now i did a nandroid restore to the freedomos rom, and it boots normal.
please help me, i really want to use sultans cm13, i really like it!
i don't know why it doesn't work, i mean as a secondary it booted flawless..
btw i'm on the 3.2.7 firmware
(problem exists on all 6.0 aosp roms i tried. Please read further posts)
Did you follow the flashing instructions to the letter? If you did, you would have seen that the CM13 requires a one time flash of the OOS 3.2.6 firmware (linked in the thread).
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
ReNeH99 said:
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
Click to expand...
Click to collapse
BTW, which xposed version did you flash? If it was v86.x then that's the most likely culprit (since the latest patch, v87 works, v86.x causes bootloop).
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
ReNeH99 said:
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
Click to expand...
Click to collapse
Hmm... strange... TWRP doesn't give any errors either?
Hw4ng3r said:
Hmm... strange... TWRP doesn't give any errors either?
Click to expand...
Click to collapse
nope no errors, all the folders and build.prop, etc is in the /system folder too..
i also redownloaded the rom, md5 hash is right and it doesn't help either
May be a silly question but did you uninstall multirom?
Hw4ng3r said:
May be a silly question but did you uninstall multirom?
Click to expand...
Click to collapse
yep
i gonna try to flash RR 5.7.4, to see what happens then
edit: what i forgot to say, i also reinstalled multirom and the multirom recovery for another try. in the multirom menu the touch doesn't work then, and when the primary rom (cm13 sultan) boots after 5 secs, i just get a black screen, the phone isnt of, just a black screen, i have to press all 3 buttons for a reboot then.
edit2: RR also does not boot
edit3: lol i just reinstalled multirom and it boots as secondary rom. then i copied it to the primary slot, and *bling* it doesn't boot again... i dont get this...
Ok i tried it with multiple AOSP roms and it simply doesn't work. Strange thing is, they work as a secondary rom when i have multirom installed.
Does anybody have a solution for this maybe? I hope someone who knows about this problem can help me i don't want oos anymore i need aosp
https://download.lineageos.org/crackling
The First One!
Do we need su for arm or su for arm64?
Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64
What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs
kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite
M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs
AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.
Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"
Can this be installed over the top of cm13.0 nightly?
Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.
M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.
Wifi
Installed tonite smoothly however no wifi - anyone else with this?
Same here, just reported a bug to the bugtracker.
Make a clean install three days ago, all works fine
pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-
Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.
M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.
I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.
ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English
hi,
today, i tried to update my op3 from lineageos 14.1-201703202 to the new lineage-14.1-20170309 with twrp. but i when flashing, i get error 7.
i already had the same issue the last time and could solve the issue with first flashing oxygen 4.0.3.
i guess when i flashed oxygen 40.3, i got the newest firmware and modem (and still have it, of course). why do i get this "error 7" again?
i thought it was because of the "false" twrp (i have 3.0.4-1) and then i made the big mistake to update twrp to 3.1.0.0. this version of twrp wiped my phone. thanks good, i had a one day old full nandroid backup to restore phone including going back to twrp 3.4.0-1.
but what should i do to get the newest lineageos flashed?
i am a absolute beginner and dont have deeper knowledge, but i am already a little bit angry that everytime i want to flash an lineageos update, i get into trouble. is this normal with oneplus3 and lineage? what am i doing wrong?
thanks a lot for your help.
best regards,
flotsch1
I have a similar issue with LineageOS updates.. I flashed LineageOS14.1-20170208 nightly on my Oneplus 3 with twrp-3.0.4-1, however I cannot upgrade to newer nightly releases. For some reason they always fail to install, it actually boots on recovery mode but installation using twrp quickly fails and I cannot even see the exact error it throws. Any ideas?
If you do a search, you will see how to fix this error. It is an error in the script and you simply have to remove a couple lines.
jim262 said:
If you do a search, you will see how to fix this error. It is an error in the script and you simply have to remove a couple lines.
Click to expand...
Click to collapse
It isn't, it is a check for firmware... Could be that lineage is using OB12 firmware now..
Same here, had the error 7 when i flashed 20170302. Fixed it with a new modem firmwae installation.
Now i have the same error again installing 20170309.
But there's new fw/modem here https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Install latest and flash new lineage. No error 7 here!
kebeil said:
Same here, had the error 7 when i flashed 20170302. Fixed it with a new modem firmwae installation.
Now i have the same error again installing 20170309. But theres no new fw/modem ... https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Click to expand...
Click to collapse
The fix is mentioned in the official weekly lineageos thread. basically you need to factory reset, flash the zip file attached in the thread and then flash the latest lineageos nightly/weekly image, followed by wiping dalvik and cache. It worked for me anyway, although everything got wiped so I had to restore my apps from backup (I use titanium backup).
flashing the betafirmware was the solution for error 7, but please see my other tread explaing my gapps-problems after successful lineagos update.
Here is how you fix error 7 in TWRP. You simply edit the first Two lines in the updated script by deleting them. https://youtu.be/XkwSO_I9GfE
I got my op3 phone loaded up with twrp version 3.0.2-1 but many errors occurred after I flashed this version.
Current problems on my phone right now:
-"The dm-verity is not started in enforcing mode" occurs every time I turn on the phone.
-Twrp won't read any of my files inside the "sdcard" folder wether it's just regular folder, .zip files, and even .img files.
-It also looks like only 1 version works of twrp works on my phone right now since any twrp versions after 3.1.0 causes the twrp program to froze and doesn't completely move past welcome screen of twrp.
I believe I had the same problem. Contact OnePlus on their support page. In a chat support window, tell the operater about your problem, and ask for an appointment with a level 2 technician. They should schedule you an appointment with a technician who should be able to wipe your phone no matter what state/condition it's in. They fixed my phone in a matter of minutes. But PLEASE, try to remember to be respectful and co-operative, it usually gets you better service no matter who you are dealing with.
For dm - verity problem, it's not a problem tough... Just a security breach as seen by Google.
BTW here is the fix...It's easy , follow the thread :
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
Can't comment on twrp as I'm on the 3.0.2-1, haven't tried 3.1. Hope it helps, Thanks!
Use TWRP 3.0.4-1. 3.0.2 can't decrypt internal storage, at least not on mine it couldn't.
Also if you have f2fs file system, TWRP takes a loooooong time to boot. Just wait, even though it seems hung. Takes several minutes. If you have ext4, it's quick. Use the app 'Diskinfo' to check
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
mremghz said:
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
Click to expand...
Click to collapse
That doesn't make sense..
The latest recovery works fine here, atleast the official one. If you are in F2fs and encrypted keep in mind it takes a long long time since F2fs is really bad at this.. Depending in how full your internal storage is it can take up to 10 minutesm
Twrp 3.0.4.1 or
3.1.0 x v.26 blu_spark.
To get OTA you need to be stock, only Oos official stuff.
I do have my oneplus 3 formatted as f2fs, but it is not encrypted. I don't know what happened to it when I tried to do an update with lineage os it basically factory reset the phone (and no I didn't wipe anything but the cache) and it would not install any zips from my internal sd card. I had to go back to fastboot and reflash TWRP 3.0.4.1 recovery. Then I wiped the device and reinstalled lineage, now it works perfectly fine.
They are lineage nighty OTA updates.
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
Code:
Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 -r 16384 /dev/block/mmcblk0p56
process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption.
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
todorare said:
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
Click to expand...
Click to collapse
Which recovery are u using ?
Armaty said:
Which recovery are u using ?
Click to expand...
Click to collapse
I was using TWRP, but I somehow managed to fix it using Redwolf. Have no idea what happened, but it's ok now.
Hello, I encountered the exact same issue with same origin...
Do you remember what you did to sort this out ?
thanks
(I posted in another thread, before finding yours)
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
0101chaitanya said:
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
Click to expand...
Click to collapse
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
eljuggy said:
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
Click to expand...
Click to collapse
If you ever need to format data just use official build from twrp.me. The one from Lineage wiki has some problems for now. Redwolf is probably based on official one, that's why you succeded.
The thing is that you need to use it ONLY to format /data partition and then switch back to Lineage one before flashing system zip. Known problem, wiki is just a little misguiding here.
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
trespass23 said:
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
Click to expand...
Click to collapse
Update: after closing and run again RedWolf, tap to Format data, magically it worked. I don't know why but thats'it.
Thanks.
this issue seems to pop-up now and then.
just to make it easier for future users coming across this issue. I had explained the issue here in the following post and how to fix it.
just scroll down till it says: "so for those that would like to switch to f2fs but for some reason end up in "black screen with blue led and the phone vibrates".
it applys to the same /data issue.
page 25 off official lineageos 8.1 thread:
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-p2-t3814361/page25