TRWP Install help

[GigahurtzUK]

I am trying to install TWRP on my swift.

I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.

ABD shows no devices listed

Fastboot shows "8bce440" when "fastboot devices" is run

fastboot -i 0x2970 erase recovery sits at "waiting for any devices"

I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.

I am stumped. Any help guys.

 

[ReneX10]

You did the unlock bootloader bit in settings?

 

[GigahurtzUK]

You did the unlock bootloader bit in settings?

Hi cheers for replying.

Yeah I've unlocked bootloader in settings.

not sure what I'm not seeing.

 

[ReneX10]

Hi cheers for replying.

Yeah I've unlocked bootloader in settings.

not sure what I'm not seeing.

Love to help more, but I've always used linux to fastboot.

Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did

Have you tested fastboot with any other devices? just as an experiment

 

[GigahurtzUK]

Love to help more, but I've always used linux to fastboot.

Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did

Have you tested fastboot with any other devices? just as an experiment

No other devices to test with.

I will have to try linux then. I just need a usb to make a linux live usb

Cheers

 

[M_Kay]

I am trying to install TWRP on my swift.

I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.

ABD shows no devices listed

Fastboot shows "8bce440" when "fastboot devices" is run

fastboot -i 0x2970 erase recovery sits at "waiting for any devices"

I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.

I am stumped. Any help guys.

If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.

 

[noob2016]

Is this the norm when changing recovery.img?

If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.

i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?

 

[M_Kay]

i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?

I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.

 

[noob2016]

Thanks for the fast reply and help

I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.

1st thanks for fast reply and help

im not in bootloop, thank goodness!
I'm currently in TWRP, when the recovery was in CM the gapp-arm64-aroma-5.1 it installed flawlessly following the cm12.1 flash but after the update 13.0 the gapp can't be installed even reverting back to 12.1 and using the same files. I did wipe all prior to change of rom also match it (i.e. cm13.0 to gapp 6.0).
Maybe this will solve it. I will try to erase recovery and re-install TWRP

i will report back after. Thanks

 

[noob2016]

Works

Thanks it worked on pico gapp but not in aroma

followed the erase command and install TWRP again.
Many thanks

 

[noob2016]

TWRP not working in Aroma Gapp need fix

In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.

What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107

This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me

 

[robin0800]

In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.

What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107

This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me

This TWRP works wioth aroma gapps

https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP

 

[noob2016]

Thanks

This TWRP works wioth aroma gapps

https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP

Thanks for the info and fast reply.

Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb

 

[robin0800]

Thanks for the info and fast reply.

Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb

Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial

 

[noob2016]

I will try

Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial

Thanks for the reply and also on my other post.

Since this is for swift, i will try to install but sadly i have given it back already. It was just here for the upgrade and when i got the chance to get hold of it again i will definitely try and report back.

Many thanks.

 

[msiviter]

Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.

What am I doing wrong?

Thanks

 

[robin0800]

Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.

What am I doing wrong?

Thanks

The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495

 

[msiviter]

The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495

I think it was a windows 10 problem, I gave it all another try this morning firstly using the WinDroid Universal Android Toolkit to Unlock Bootloader and flash TWRP . I then rebooted into recovery and hey presto TWRP. Flashing CM13 nightly and pico gapps was then childsplay.

Any ideas why google play didnt offer to auto restore all my apps? Thats a bit of a pain.

Otherwise very pleased, phone seems a bit more responsive using CM13 than CyanogenOS. I tried to format my SD to use as internal storage too but i couldnt see them separately afterwards to free up device storage so I reverted back.

Thanks for trying to help.

 

[noob2016]

Yey!!!

Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495

Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!

 

[ZB2016]

Got stuck in a TWRP loop after installation. Regardless which reboot option I choose, always TWRP 3.0.0 comes up. No idea what I did wrong but for me it is of more interest how to get rid of it. Accessible external SD contains cm14-zip and also Stock 6.0.1. Installed CM14 multiple times, but has no impact on what comes up after selecting reboot/reboot recovery/reboot fastboot - it is always TWRP. Tried it also via adb sideload from within TWRP, no change of behaviour. Same when I tried to install stock rom.

Bootloader issue? How to get it back? I have 2 further Swifts available so I can dump several necessary partitions from them, but I need to know which tools are required, since I usually deal with MTK-based androids. Backup of userdata and sdcards is available, so if a reset to stock is necessary, this is not a problem from that point of view - if I only would have the info, how to get back a working bootloader.

Even though I love this recovery, it is obviously annoying ... Any help appreciated. Tnx in advance!

Edit: Fixed. I removed the battery for several hours and without battery with plugged in USB cable (not the WF one, I have tons of them lying arround here) I was able to reboot to normal fastboot. From then on it was strraightforward:
checked OEM lock status via fastboot command on PC
flashed newest TWRP
rebooted to TWRP
installed Stock ROM to get all partitions reinitialized correctly
rebooted to OS - YEAH, the swift lives again
Rebooted to recovery
Installed CM14 and OpenGApps Nano (ARM, not ARM64, since it produces an error)
Reboot to OS - YEAH, here we are.