Related
Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks
Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.
Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.
is a ZIP file available for flashing via TWRP?
Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?
seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.
Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.
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 there,
I have a little problem with twrp 3.0.2 (I think). Every time I boot to recovery and then to system, it wipes Data and dalvik cache. Automatically. That sucks because the reboot takes long and I have to restore all my apps etc. Can someone help?
7root said:
Hi there,
I have a little problem with twrp 3.0.2 (I think). Every time I boot to recovery and then to system, it wipes Data and dalvik cache. Automatically. That sucks because the reboot takes long and I have to restore all my apps etc. Can someone help?
Click to expand...
Click to collapse
What ROM? Try the modified TWRP by jcadduono or the one by eng.stk
I have the same problem. Did the modified TWRP fix it?
Why do ppl complain about old TWRP versions and never think about updating first? ....
Upgrade to latest TWRP
emuandco said:
Why do ppl complain about old TWRP versions and never think about updating first? ....
Click to expand...
Click to collapse
Because the new version are not on official twrp site
nitinvaid said:
Because the new version are not on official twrp site
Click to expand...
Click to collapse
Orly? https://dl.twrp.me/oneplus3/
3.0.3 >>> 3.0.2
emuandco said:
Orly? https://dl.twrp.me/oneplus3/
3.0.3 >>> 3.0.2
Click to expand...
Click to collapse
Check XDA twrp thread it's not on site
https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
God we can discuss this for ages now, but twrp has a way more recent OFFICIAL build on their site. 3.0.4 is a git code build and thus NOT official. Anyways I am out.
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Thanks for the response Unn113. Do I simply need to format and start from scratch?
trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Jackson.Armstrong.Blow said:
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Click to expand...
Click to collapse
Thanks!
trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Click to expand...
Click to collapse
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
the Doctor said:
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
Click to expand...
Click to collapse
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Sent from my OnePlus5T using XDA Labs
Either blu_spark or ibe recovery work. They also work with lockscreen security setup, no problems over here.
Unn113 said:
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Click to expand...
Click to collapse
How do you figure? I've successfully backed up my previous ROM and flashed another one using that TWRP, my device is encrypted properly, I've reset lockscreen security, and my device passes SafetyNet.
Had the same issue. Flashing Blu_Spark worked perfectly. Thanks @the Doctor
help for twrp
TWrp message
message came to me
say
E: primary block device /dev/block/mmcb1kop8
for mount point /data is not present
failed to mount data
unable to create /data/media folder,
icant install rom and wipe data and now dont have any rom to open my device
please help me
I had this problem after installing TWRP 3.2.1-1. A new version was released last night (3.2.1-2) which I flashed this morning and seems to solve the problem. You can find the new version here.
I have been working on the sister models also. I saw no one was building these anymore so here it is I hope it can be enjoyed by all. Spread the word. provide feedback so other fans of this ROM may obtain it and work out any bugs if there are any. I will update once or twice a week depending on time and demand. I'm compiling for three different variants. Hit the thanks button and Enjoy. Dirty flash the updates not the initial flash of this rom but the updates to it. Initial install = Factory reset, wipe data and cache, install rom zip, install gapps zip, install su zip, reboot system. As of 9-3-18 i will be switching to Ubuntu 18.04 Bionic Beaver, that being said i do not know if i will have to change anything or do anything different to keep pushing these updates out but i will most definitely try to keep them coming.
4-10-18
https://www.androidfilehost.com/?fid=890129502657597436
4-13-18
https://www.androidfilehost.com/?fid=818070582850507491
4-17-18
https://www.androidfilehost.com/?fid=818070582850508419
4-24-18
https://www.androidfilehost.com/?fid=673956719939836620 If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app
5-4-18
https://www.androidfilehost.com/?fid=818222786056028546
Root is not baked in. Flash and root your preferable way.
5-20-18
https://www.androidfilehost.com/?fid=674106145207488021
5-31-18
https://www.androidfilehost.com/?fid=674106145207490572
7-28-18
https://www.androidfilehost.com/?fid=5862345805528060741
9-3-18
https://www.androidfilehost.com/?fid=1322778262903996744
10-07-18
https://www.androidfilehost.com/?fid=1322778262904022369
12-7-18
https://www.androidfilehost.com/?fid=11410963190603868411
12-16-18
https://www.androidfilehost.com/?fid=11410963190603876081
2-25-19
https://www.androidfilehost.com/?fid=1395089523397901582
3-24-19
https://www.androidfilehost.com/?fid=1395089523397924752
5-6-19
http://download1589.mediafire.com/7...q5/lineage-14.1-20190507-UNOFFICIAL-d2tmo.zip
10-13-19
https://www.androidfilehost.com/?fid=1899786940962607809
i recommend clean flash as i built with different computer
setprop persist.lineage.nofool true in terminal emulator with root privs (type su first grant permission then setprop persist.lineage.nofool true) gets rid of persistant notification
Bluetooth dialtone when playing music fix
Settings > Battery > tap in 3-dot menu at top right tap on Battery optimisation. To show all apps and services here, select the ‘All apps’ options under the dropdown. Tap on both of the Bluetooth services and change them to Don't optimise.
thanks bro... but is it rooted rom or use any method to root it ?
hasan.sy said:
thanks bro... but is it rooted rom or use any method to root it ?
Click to expand...
Click to collapse
I use SuperSU zip
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
I appreciate the feedback and no worries mate I'm still trying to get the no sim bug worked out in the att variant no luck so far sprint variant is doing good also
Update posted 4-17-18
It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.
Sammay_Boiii said:
It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.
Click to expand...
Click to collapse
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding
Joker1716 said:
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding
Click to expand...
Click to collapse
Thank you for your rapid response! I will try that as soon as I get to my house and I'll let you know what happens
After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?
Sammay_Boiii said:
After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?
Click to expand...
Click to collapse
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
This should help
https://forum.xda-developers.com/showthread.php?t=1949687
Joker1716 said:
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
Click to expand...
Click to collapse
I will do that. Your rom needs to be flashed over stock rom?
Sammay_Boiii said:
I will do that. Your rom needs to be flashed over stock rom?
Click to expand...
Click to collapse
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?
Joker1716 said:
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?
Click to expand...
Click to collapse
What you said makes a lot of sense actually. Im used to just flashing back ups of other roms that I forgot how to flash fresh ones. I'm not used to this haha but I got it now. Stock rom 4.3 has been flashed via odin and the root method is currently on my screen.
hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3
Sammay_Boiii said:
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3
Click to expand...
Click to collapse
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher
hasan.sy said:
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher
Click to expand...
Click to collapse
Thank you. Ive been flashing this rom repeatedly and always received a "Process system not responding" then it falls into a boot loop
Update posted
Joker1716 said:
Update posted
Click to expand...
Click to collapse
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)
hasan.sy said:
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)
Click to expand...
Click to collapse
If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app