So recently i flashed the new cyanogen 14.1 nightly rom but it said their was an update but after i installed it it tried to go into recovery and wouldnt start. I shut it down and it would only go into fastboot mode and show the boot image. after this i downloaded fastboot and adb files and a tool kit and it now boots into the actual rom but still not recovery. so how can i get the recovery to pop up? iv already tried to flash twrp again but it still didnt load. and i even flashed the stock recovery and still wouldnt boot up. if anyone knows a way i can fix my recovery it would help alot. :good:
I have exactly same problem as you k hope it's a problem with the new cyanogenmod 14.1 nightly if not may try to change the kernel? I'm looking around too
Same problem here.... I installed TWRP and Dirty Unicorns on my One Plus 3, but immediately had a host of problems (including home key not working). I then flashed the most recently nightly (cm-14.1-20161119-NIGHTLY-oneplus3.zip). It booted fine, but now I cannot get into recovery. Any attempt to boot into recovery will put me back at the unlock warning screen... The phone is functionally useless at this point, because it doesn't even have gapps on it.
How can I restore this phone to a usable state (i.e., enter recovery to allow flashing of gapps)?
official twrp doesnt work with community builds and cm 14.1. You have to use modified twrp 3.0.2-22. the link can be found easily in official cm 14.1 forum on xda.
So I have TWRP installed on my phone and am running the CM 13 custom rom. When I boot into TWRP and then hit reboot system, it gives me the warning "No OS installed! Are you sure you wish to reboot?" It gives me this error every time, even though I DO have an OS installed. The reason that this is a problem is that I need to flash a Gapps zip onto my phone, but whenever I try to, it says that I have no rom installed, and that I need to flash a rom before gapps. This is very annoying, because I DO have a rom installed, but yet these errors keep showing up. To find the guide I followed, type (I'm unable to post links yet) "How to Install CM 13 On T-Mobile Galaxy S2 Android Marshmallow 6.0" into google. It will be the first link. I followed those steps exactly, so I don't know why this is happening. Any possible fixes would be appreciated!
AndroidAllTheWay358 said:
So I have TWRP installed on my phone and am running the CM 13 custom rom. When I boot into TWRP and then hit reboot system, it gives me the warning "No OS installed! Are you sure you wish to reboot?" It gives me this error every time, even though I DO have an OS installed. The reason that this is a problem is that I need to flash a Gapps zip onto my phone, but whenever I try to, it says that I have no rom installed, and that I need to flash a rom before gapps. This is very annoying, because I DO have a rom installed, but yet these errors keep showing up. To find the guide I followed, type (I'm unable to post links yet) "How to Install CM 13 On T-Mobile Galaxy S2 Android Marshmallow 6.0" into google. It will be the first link. I followed those steps exactly, so I don't know why this is happening. Any possible fixes would be appreciated!
Click to expand...
Click to collapse
I would try to flash another version of TWRP. Sometimes, the latest TWRP is not the most compatible with all the ROMs out there.
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.)
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Similar problem
-- sorry, wrong device, please disregard. I can't seem to find a delete button. Newby passing through.--
I have not previously installed custom ROMs on my devices. Now I am also trying to install Lineage 17.1 on my Galaxy Tab Pro 12.2 and thus far have been unable. Maybe your experience is similar to mine:
I used ODIN to flash the latest TWRP to the boot loader and booted to recovery (so Samsung system boot would not replace TWRP with stock recovery) and TWRP recovery is stable. In TWRP, I installed SuperSU from a zip file on the extSD. After booting into the stock system, I was prompted to finish rooting, which I did using TWRP. Once I was able to reliably boot into recovery or normally (stock system), I booted to recovery and made a backup of my stock image. I have reliably flashed Samsung stock image, which boots to the initial setup process, and restored by backed up image, which boots to the previously configured state.
At this point I downloaded the Lineage 17.1 image zip file onto the extSD card and tried flashing it from recovery. While unzipping the image, the recovery screen shows a couple of error messages, along the lines of image is 'for device v1awifi but this device is .' and flashing fails. I believe at this point rebooting hangs with the Samsung logo animation, but I have been able to boot recovery and restore my previous rooted Samsung stock state. Custom ROM Manager confirms my device Codename is v1awifi.
Is this what you experienced? If not, how is your experience different? Can you describe your approach, what steps you've taken, and where the process does not go as expected?
ScrooLoose said:
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Click to expand...
Click to collapse
where did you find 17.1 for tab pro 12.2?
ScrooLoose said:
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Click to expand...
Click to collapse
So you are on TWRP 3.4.0-0?
Although I own a P900 I had problems flashing 17.1 before updating to 3.4.0-0.
And for 17.1 I used BiTGapps instead of opengapps for the last didn't like it.
Does anyone know how to modify this note 12.2 LOS 17 zip so it can be flashed on tab 12.2? https://forum.xda-developers.com/t/...l-lineage-17-1-android-10-q-20201221.4152395/
I was able to get it installed on my Tab pro 12.2 T900. It gets stuck on the bootup lineage logo screen. I guess android 10 on this device is too good to be true.
Dusterrr said:
I was able to get it installed on my Tab pro 12.2 T900. It gets stuck on the bootup lineage logo screen. I guess android 10 on this device is too good to be true.
Click to expand...
Click to collapse
I had the same issue. You need to flash 17.1 over 14.1.
rojorojorojo said:
I had the same issue. You need to flash 17.1 over 14.1.
Click to expand...
Click to collapse
I tried this and it isn't working. Any suggestions? Can you help me out? Nevermind, its working this time! I tried many times, but the final time I didn't clear cache and it worked .
NVM not working again...
I clean flashed lollipop with odin, then twrp, then lineageos14.1, configure it, and dirty flashed 17.1, and at the moment it's working. No root installed.
I need help bad - can't figure out how to get my phone working again and it is basically stuck in fastboot.
This is a POCO F3 (alioth) and I previously had Lineage 18 and TWRP recovery installed (since I like to do full backups)
I flashed new firmware, then the OS, then gapps, rebooted, looks great. Awesome. Now I'm just gonna go back and install the latest TWRP and be done. This is where I must have gone wrong.
I used fastboot flash boot twrp.img with the latest version of TWRP (I had to do the same to sideload Lineage 19 since the older version I had was apparently not compatible and couldn't get the Lineage recovery to load) rebooted to recovery, and TWRP asked for my pattern to decrypt as usual. But it would not accept my pattern. I hit cancel, and because I didn't have access to my data I wasn't able to install TWRP by having it patch the ramdisk. Okay, maybe it's a glitch, I tried booting into TWRP again and got the same thing. When I went to reboot again I noticed the slot was A, instead of B which it had always been previously. So I thought maybe my system partition was on B and switching that would solve it. But after I switched that slot, TWRP has never gotten past the splash screen before it reboots and I can't boot into my system at all. Essentially the only thing I can boot into is Fastboot.
I have tried flashing the latest Lineage recovery (does not boot), an older version of TWRP (boots but sees none of my data) and stock MIUI boot.img (boots to recovery but has no options besides wipe).
I am at a loss here - I know I probably did something wrong in there, but is my system wiped? I have a lot of data on there I'd like to retain. I don't think it is wiped but I don't understand the a/b partition setup or why TWRP boot-loops on me. Any help would be greatly appreciated.
stevencrayne2 said:
Upgrade to LineageOS 19 gone wrong...
I need help bad - can't figure out how to get my phone working again and it is basically stuck in fastboot.
This is a POCO F3 (alioth) and I previously had Lineage 18 and TWRP recovery installed (since I like to do full backups)
Click to expand...
Click to collapse
FWIW althafvly who is one of the LineageOS maintainers of the Xiaomi POCO F3 / Redmi K40 / Mi 11X (alioth) wrote in the post #1 of his XDA thread [ROM][OFFICIAL][alioth/aliothin][12.1] LineageOS 19.1 *(bolded by him)*:
Flashing LineageOS through TWRP is NOT SUPPORTED and NOT ADVISED.
***
I figured out what seems to be a solution for preserving my data - for anyone else who has a similar issue, here are the steps I used to solve:
If Lineage recovery boots for you, by all means use that. I couldn't get it to boot from fastboot.
Select slot A in fastboot. flash latest TWRP to boot_a. Select slot A again. boot to recovery. TWRP should load, it will not decrypt your data but it doesn't wipe it either. Hit cancel there. Then go to advanced and ADB sideload. Sideload Lineage ROM. reboot to recovery, and finally Lineage recovery shows up. Sideload Gapps there and whatever else. Boot to system. DO NOT REINSTALL TWRP.
Apparently TWRP can access the disk somehow, but won't decrypt existing data. Hope this helps someone.