FORUMS
Remove All Ads from XDA

Bricked Swift

3 posts
Thanks Meter: 0
 
By narmista, Junior Member on 25th July 2016, 11:40 PM
Post Reply Email Thread
Hello Everyone!

I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?

Thanks in advance!!
 
 
26th July 2016, 10:15 AM |#2  
Member
High Wycombe
Thanks Meter: 6
 
More
Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.

In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wile...false-t3276317
26th July 2016, 04:15 PM |#3  
OP Junior Member
Thanks Meter: 0
 
More
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
27th July 2016, 11:40 AM |#4  
Member
High Wycombe
Thanks Meter: 6
 
More
Quote:
Originally Posted by narmista

Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.

Does the phone give any indication of being connected? Notification light, starting the display, etc?

If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.

If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.
29th July 2016, 06:42 AM |#5  
Senior Member
Flag Johannesburg
Thanks Meter: 31
 
More
Quote:
Originally Posted by narmista

Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.

If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me
29th July 2016, 09:10 AM |#6  
OP Junior Member
Thanks Meter: 0
 
More
Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread