Installed trwp and flashed multiple times my wileyfox swift to lineage 14.1
Swift wont boot gets stuck in bootloader....
Found a 14.0 image (linage) somewhere.... this works with no problems but seems an older built (buggy)
Anyone has 14.1 lineage on a swift with no problems ???
You can try installing Lineage 14.1. from CM13, see posts #155/#156 in thread 'Nightly 14.1 lineageOS Rom For Crackling'
went back to cyanogen the original firmware
Found the original firmware and twrp flashed back to that one...
https://forum.xda-developers.com/showpost.php?p=70510585&postcount=19
Old firmware but was happy with that one so.... problem solved....
Same bootloop on Wileyfox Swift, how did you...
...install the old COS on your Swift?
I downloaded all the files from G4liant's MEGA cloud storage but don't know how to continue.
Please, help if you can (see my reply to his post, too (as of today 25. June 2017)).
Thanks!
jwalesch
__________________________________________________________________________
eskodisk said:
Found the original firmware and twrp flashed back to that one...
https://forum.xda-developers.com/showpost.php?p=70510585&postcount=19
Old firmware but was happy with that one so.... problem solved....
Click to expand...
Click to collapse
original firmware
jwalesch said:
...install the old COS on your Swift?
I downloaded all the files from G4liant's MEGA cloud storage but don't know how to continue.
Please, help if you can (see my reply to his post, too (as of today 25. June 2017)).
Thanks!
jwalesch
__________________________________________________________________________
Click to expand...
Click to collapse
Do you have TWRP recovery installed on your wileyfox ?
Via the twrp recovery, you can install what is in one of the zipfiles
I guess this one :
cm-13.1.2-ZNH2KAS3LG-crackling-signed-42f2b8e414.zip
MD5: 0AEF4E4A468EF34A6DA65712156ECB2C
contains the twrp installable original firmware....
Installing works the same as you would eg install a lineage custom rom.... TWRP is rather fool proof... I tried to install some of the other files, in the other zipfiles and twrp just refused... so ... try.... no need to install google apps here, everything is in the image... As you will see in the filesize of het image, it is rather big, compared to the lineage custom roms... Everthing is there....
If you are so far... Let me know, i learned that you will have to disable the wileyfox to keep looking for updates, wileyfox will download over and over again the upgrade files, was kind of annoying...
TWRP recovery cannot be loaded on Wileyfox Swift
Hi!
I had TWRP installed, in fact in different versions.
But for whatever reason I cannot boot into TWRP anymore which is precisely one of the problems I'm having now that I wanted to flash the Lineage OS again on a second Swift (I might have erased the partition that I installed TWRP to). But I cannot install TWRP again either...
All I can reach is the bootloader which does give you an option to restart recovery but it doesn't work. The phone is stuck in a bootloop returning whatever you do to the bootloader.
So, I hoped to find some help in treating the phone to a new or its original bootloader...
Thanks for helping!
jwalesch
__________________________________________________________________________
eskodisk said:
Do you have TWRP recovery installed on your wileyfox ?
Via the twrp recovery, you can install what is in one of the zipfiles
I guess this one :
cm-13.1.2-ZNH2KAS3LG-crackling-signed-42f2b8e414.zip
MD5: 0AEF4E4A468EF34A6DA65712156ECB2C
contains the twrp installable original firmware....
Installing works the same as you would eg install a lineage custom rom.... TWRP is rather fool proof... I tried to install some of the other files, in the other zipfiles and twrp just refused... so ... try.... no need to install google apps here, everything is in the image... As you will see in the filesize of het image, it is rather big, compared to the lineage custom roms... Everthing is there....
If you are so far... Let me know, i learned that you will have to disable the wileyfox to keep looking for updates, wileyfox will download over and over again the upgrade files, was kind of annoying...
Click to expand...
Click to collapse
I have found a way to install TWRP (different versions) but didn't know how to start it.
In this post I found how to:
https://forum.xda-developers.com/wileyfox-swift/help/foolproof-twrp-guide-wileyfox-swift-t3616571
It's keeping the volume down button held down until TWRP starts, then you can do everything from there.
Everything?
I installed Lineage OS 14.1 (nightly as of 2017/06/19) as well as GApps, wiped Cache/DALVIK and restarted the system.
The OS wouldn't start, only the bootloader could I get the phone to start.
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
jwalesch said:
Hi!
I had TWRP installed, in fact in different versions.
But for whatever reason I cannot boot into TWRP anymore which is precisely one of the problems I'm having now that I wanted to flash the Lineage OS again on a second Swift (I might have erased the partition that I installed TWRP to). But I cannot install TWRP again either...
All I can reach is the bootloader which does give you an option to restart recovery but it doesn't work. The phone is stuck in a bootloop returning whatever you do to the bootloader.
So, I hoped to find some help in treating the phone to a new or its original bootloader...
Thanks for helping!
jwalesch
__________________________________________________________________________
Click to expand...
Click to collapse
jwalesch said:
[...]
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
Click to expand...
Click to collapse
Try installing the system and the GApps separately:
Wipe again, install system, then boot to system, when Lineage has successfully booted for the first time (may take a couple of minutes), go back to TWRP and install GApps.
jwalesch said:
I have found a way to install TWRP (different versions) but didn't know how to start it.
In this post I found how to:
https://forum.xda-developers.com/wileyfox-swift/help/foolproof-twrp-guide-wileyfox-swift-t3616571
It's keeping the volume down button held down until TWRP starts, then you can do everything from there.
Everything?
I installed Lineage OS 14.1 (nightly as of 2017/06/19) as well as GApps, wiped Cache/DALVIK and restarted the system.
The OS wouldn't start, only the bootloader could I get the phone to start.
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
Click to expand...
Click to collapse
I had the same problem with lineage.... only bootloader when powering on.... That is the reason why I went back to the original firmware because that solved my problem.... I once found an older lineage rom suggested somewhere on the forum that worked and got me out of the bootloader but that version was buggy... Updating from there to a the latest linage got me back to the bootloader only problem....
I will stay on the cyonogenmod now.... Until perhaps someone can tell me how to really solve the bootloader only by power up problem....
eskodisk said:
[...]
I will stay on the cyonogenmod now.... Until perhaps someone can tell me how to really solve the bootloader only by power up problem....
Click to expand...
Click to collapse
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
total backup of existing system ?
kabu83 said:
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
Click to expand...
Click to collapse
Can i backup my existing system in twrp... I tried lineage a dozen times before and always got stuck on bootloader. So can I backup my current setup because at the moment everything works as it should.... ????? I formatted my sd card as system memory so... ????
If TWPR is running and you can mount the system partition, you should be able to make a back-up via TWRP. (Not of your pictures, music and so on, see TWRP disclaimer.)
Install LineageOS from a running cm-13.1.2-ZNH2KAS3LG-crackling
Hi there!
Yes, my Wileyfox Swift is running the CyanogenMOD version cm-13.1.2-ZNH2KAS3LG-crackling.
Everything seems to be OK, it just wants to keep downloading an update which I can save but when I'm asked to install it the normally automatic installation process doesn't work:
The phone reboots back to TWRP but doesn't show the just downloaded .zip file (which normally would happen) and doesn't install it either. Installation stops in TWRP, when I tap on REBOOT > SYSTEM the OS reboots normally but shows the OS version I had before.
Can you tell me where these update .zip files are saved so that I could install it maybe from the TWRP's file manager?
If that doesn't work I would try to update TWRP and after that install the current Lineage OS over the CM 13.1.2 as you suggested.
Thanks for helping!
jwalesch
________________________________________________________________________________________________
kabu83 said:
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
Click to expand...
Click to collapse
jwalesch said:
Hi there!
Yes, my Wileyfox Swift is running the CyanogenMOD version cm-13.1.2-ZNH2KAS3LG-crackling.
Everything seems to be OK, it just wants to keep downloading an update which I can save but when I'm asked to install it the normally automatic installation process doesn't work:
The phone reboots back to TWRP but doesn't show the just downloaded .zip file (which normally would happen) and doesn't install it either. Installation stops in TWRP, when I tap on REBOOT > SYSTEM the OS reboots normally but shows the OS version I had before.
Can you tell me where these update .zip files are saved so that I could install it maybe from the TWRP's file manager?
If that doesn't work I would try to update TWRP and after that install the current Lineage OS over the CM 13.1.2 as you suggested.
Thanks for helping!
jwalesch
________________________________________________________________________________________________
Click to expand...
Click to collapse
What update does it want to keep downloading? I guess it might be the official stock 7.1.1..
You probably need to download the Lineage.zip manually from official Lineage downloads.
Then restart to TWRP and install the Lineage.zip.
TWRP has a toggle button in the lower left corner, where you can switch from 'Install image' to 'Install zip'. With 'install zip', you should find the zip.
The update is cm-13.1.2-ZNH2KAS7EB-crackling.
I have it ready to be installed on the phone but it won't show in any filemanager, be it in TWRP nor the system's filemanager nor AMAZE filemanager which I also installed.
So, I assume the download either isn't actually saved properly or it's a hidden file or something of that sort.
In other threads they say that updates were saved to a folder called "cmupdater". I cannot find any folder with that name either.
I also have the latest LineageOS .zip file ready to be installed on my phone and have tried to install that from TWRP (by the way: Now running the latest version for the Wileyfox Swift, ie. twrp-3.1.1-0-crackling). All it does is it produces an error saying something like "Error 7... cannot be installed".
SOLVED for now:
From here https://cyanogenupdatetracker.com/downloads/ I downloaded the latest available CM version (SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip) which seemed to be exactly the one that my phone kept downloading and couldn't install.
I copied it to my external sd card and installed it from there via TWRP.
After that the system rebooted normally, Android then updated all my installed apps and now the system is downloading yet another update:
Android 7.1.1 (Nougat) - TOS111B
As I know that version of Android on the Wileyfox it's not actually something I would want to install myself. But I shall try to install the latest Lineage OS instead.
Let's keep each other posted (in German?)!
___________________________________________________________________________________________________
kabu83 said:
What update does it want to keep downloading? I guess it might be the official stock 7.1.1..
You probably need to download the Lineage.zip manually from official Lineage downloads.
Then restart to TWRP and install the Lineage.zip.
TWRP has a toggle button in the lower left corner, where you can switch from 'Install image' to 'Install zip'. With 'install zip', you should find the zip.
Click to expand...
Click to collapse
jwalesch said:
The update is cm-13.1.2-ZNH2KAS7EB-crackling.
I have it ready to be installed on the phone but it won't show in any filemanager, be it in TWRP nor the system's filemanager nor AMAZE filemanager which I also installed.
So, I assume the download either isn't actually saved properly or it's a hidden file or something of that sort.
In other threads they say that updates were saved to a folder called "cmupdater". I cannot find any folder with that name either.
I also have the latest LineageOS .zip file ready to be installed on my phone and have tried to install that from TWRP (by the way: Now running the latest version for the Wileyfox Swift, ie. twrp-3.1.1-0-crackling). All it does is it produces an error saying something like "Error 7... cannot be installed".
SOLVED for now:
From here https://cyanogenupdatetracker.com/downloads/ I downloaded the latest available CM version (SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip) which seemed to be exactly the one that my phone kept downloading and couldn't install.
I copied it to my external sd card and installed it from there via TWRP.
After that the system rebooted normally, Android then updated all my installed apps and now the system is downloading yet another update:
Android 7.1.1 (Nougat) - TOS111B
As I know that version of Android on the Wileyfox it's not actually something I would want to install myself. But I shall try to install the latest Lineage OS instead.
Let's keep each other posted (in German?)!
___________________________________________________________________________________________________
Click to expand...
Click to collapse
English is forum language I guess, you could probably send me a private message to clarify anything in German.
I also had the error 7 issue when installing Lineage, you need to wipe system (you will loose everything though, it is not possible to install Lineage over Cyanogen, like a dirty flash).
In TWRP, choose Wipe/advanced Wipe/ tick system only / repair, 2F2S. After that, format data.
Then the installation of Lineage with TWRP should run through. Let the system boot for the first time, if it runs, boot back to TWRP and install GApps.
With that method, I am on LOS nigthly 20170626 now and happy.
Hi kabu83!
Thanks a lot for your last reply - it helped me to finally get Lineage OS 14.1 installed!
At the moment the phone is rebooting the system after installing the GApps, everything seems to run smoothly and - guess what - I'm happy, too, now!
How about sending me a PM? (As I have no clue as to how that works it would be nice if you could send me that one more reply to let me know.)
Related
I unlocked the bootloader following Motorolas steps. I then flashed the latest version of TWRP avaiable on the development forum and then flashed Lineage OS + the root zip they provide and gapps. I couldn't figure out how to get out of the bootloop so I've since gone back to stock. Any idea what I was missing?
TWRP:
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
Lineage:
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
Did you read the notices and entries on the Linage last pages of the thread that people are having it fail on the install, the latest release? That would be a clue...
I even tried flashing Pure Nexus but that too was stuck on a loop. I left it for about 10 minutes as it was loading. :/
I did the same thing like you on my first attempt, on my second I was able to install Lineage OS successfully. I'll provide the steps I did.
First attempt steps:
1. Unlocking the bootloader using Motorola website
2. Installing TWRP from the same link in your post.
At that point I tried booting the phone, but the phone was booting to TWRP only, tried wiping, format data from TWRP with no luck.
3. From TWRP flashed Lineage OS zip file and GAPPS nano package (the latest version of TWRP is able to see SD card).
At that point I was able to to boot LOS only after executing "fastboot erase user data". Doing the same from within TWRP was not doing the job. The problem was that after each reboot the phone was getting into bootloop again and "fastboot erase userdata" was necessary.
4. At that point I noticed that TWRP thread starts with warning that you have to install a patcher to disable this "verity" feature of the bootloader may be. And I installed the patcher "Verity_FE_patcher.zip"
The patcher didn't fix the issue and went back to stock Nougat using the guide below:
https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
First I tried "flashall.bat" , but it didn't wor.k and I flashed all the files manually using the guide . The phone booted normally and I updated it with one OTA update.
Second attempt steps:
1. I wanted to install the verity patcher before anything else and I boot TWRP 3.1.0.1 without flashing it. It booted normally and I realized that the SD card was formated and the patcher zip file is not there. I reboot the system and the phone got in bootloops again even the TWRP was not installed. I coppied the patcher zip, LOS zip, GAPPS zip on SD card . I tried to boot (without flashing) TWRP again, but for some reason TWRP was not able to boot.
2. I flashed TWRP
3. Booted TWRP and flashed verity patcher.
4. Wiped from TWRP and boot the system
At that point I was able to boot the stock firmware with TWRP installed and I was able to restart the phone normally.
5. Flashed LOS and nano GAPPS
Now everything seems to work properly.
Hope this will help.
Thanks. I'll give this a shot tonight. Our first attempts sound very alike.
As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.
You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root
hello, that's what I did and it worked well
this has happened here since 5.0.4
Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.
I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.
Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this
Hello everyone,
after installing Omni-Rom without gapps I tried to install gapps via adb sideload on stock recovery.
Unfortunately no device was shown in device manager when starting sideload.
Anyone faced this issue?
Is there another way to install gapps?
Thank you!
No.
Stock recovery can only install official updates zip files, approved by OEM.
To install anything unofficial, like OpenGApps, you need a custom recovery, like TWRP.
BTW, I never get the sideload feature of official recovery to work in any phone I tried it (not much to tell the truth, but looks like a fake feature).
BubuXP said:
No.
Stock recovery can only install official updates zip files, approved by OEM.
To install anything unofficial, like OpenGApps, you need a custom recovery, like TWRP.
BTW, I never get the sideload feature of official recovery to work in any phone I tried it (not much to tell the truth, but looks like a fake feature).
Click to expand...
Click to collapse
Thank you! I wanted to install gapps on omni treble gsi...
Solved by copying zip to system partition, installing twrp, formatting data, installing gapps with twrp, reinstalling stock recovery and formatting data again with stock recovery...
What a waste of time... Hope we will get a working twrp soon.
Btw. have you tried to use the phone unencrypted with rooted stock kernel? With editing vendor > etc > fstab.qcom forceencrypted to encryptable it works, but without wifi in rom.
The question is: will reflashing the stock kernel/recovery heal that wifi problem? I would try, but right now everythin is set up fine - perhaps you already tried...
If that would work, then it would be easy to use twrp. Then you only would need to change the boot.img after using twrp...
I hope that someone here can help me rescue to rescue my data.
I was on the AOSiP build from september and than decided to encrypt my device. That worked perfectly. Now I wanted to install the latest update. The internal updater didn't work (just booted into TWRP recovery without further action, so I moved the update file to microsd and than updated manually by flashing the zip file via TWRP). Prior to the whole action, I updated TWRP through the app to the latest version.
Now my phone doesn't boot anymore, it is stuck in the AOSiP boot animation. Reverting to a previous TWRP version (3.2.3.2) didn't help, also flashing the september build again didn't help.
In TWRP I was unable to decrypt data, because TWRP keeps asking me for a password (but I don't remember putting a password in the first place). Therefor I switched from TWRP to OrangeFox recovery. Here decryption worked, put still after flashing the phone doesn't boot.
Anyone that has further ideas how to fix this without loosing all my data? Any help appreciated!
Have you tried installing another kernel?
kotobodj said:
Have you tried installing another kernel?
Click to expand...
Click to collapse
No, but as my system was running before without problems I don't expect the kernel to be the problem .. Or why would that make sense?
SOLVED: I noticed that flashing the update manually didn't automatically flash Gapps right afterwards. So flashing the Gapps helped and the phone now boots normally!
Hi everyone, I have an HTC One M8. I wanted to root it but something went wrong and now it is stuck on the white screen with the ONE logo. I correctly unlocked the bootloader and installed twrp. I had downloaded SuperSU on my pc (flashing it with TWRP should have been the following and last step), but after I installed TWRP, before rebooting, it asked me to install SuperSU and I said yes, thinking it would save time. Now I can enter bootloader, I can enter TWRP, but that's it. I tried to install a couple of 0P6BIMG packages, but it always says that the image size is too big. Any help? Thanks.
Download stock ROM, install it from TWRP. If you get errors, try flashing through fastboot (if you can access it)
0purple said:
Download stock ROM, install it from TWRP. If you get errors, try flashing through fastboot (if you can access it)
Click to expand...
Click to collapse
I tried a few, different sizes, I don't know which one to chose, they're all 0P6BIMG, from 1,2Gb to 1,6Gb. Which one should I choose?
This is what TWRP gave me when I tried to install Lineage OS. Also, can you provide a link for the custom rom since all those I tried didn't work?
I`m sorry, I won`t be able to help here. Try researching
Solved. If it can be of any help, apparently the twrp was corrupted and couldn't flash any rom. I changed twrp (3.5) and flashed lineage 17.1. All fine, just keep in mind lineage 17.1 is not friend with Magisk 20.4, but gets along well with 20.3.