Phone stuck in boot loop, no recovery, no fastboot - Wileyfox Storm

My wileyfox storm device is stuck in a constant boot loop, I cannot get it to boot into recovery mode, I cannot get it to boot into fastboot either.
This problem started occurring a couple weeks after the device fell off my lap and the screen cracked.
I just really want to recover the data from the device somehow because I have a lot of photos and things that I would like to backup.
Thanks in advance,
Kari.

Kari. said:
My wileyfox storm device is stuck in a constant boot loop
This problem started occurring a couple weeks after the device fell off my lap and the screen cracked.
Click to expand...
Click to collapse
This is hardware problem. The only way to save your data - is to disassamble your phone and detach the touchscreen cable. Then you can boot your device and use mouse via USB OTG, so that you can save your data to sdcard.

Related

G1 brocken?

Hello,
yesterday my G1 rebooted itself several times. Now it's hanging at the first boot screen, the G1 screen, and sometimes it doesn't start and the screen stays black.
The phone has still warranty, but there was the Cyanogen-Mod flashed, does that matter?
Do you have any ideas what I can do?
what were you doing to the phone before it started acting all crazy? can you boot into recovery or fastboot?
i changed nothing on the phone, only a few days beforce i installed the cyanogenmod, but it was working fine.
the recovery mode isn't really working. the phone goes either out a few seconds after i entered the recovery mode or it hangs on the G1 screen.
it's crazy.

Is my Nexus 4 bricked or irreperably broken?

Hello people,
I have a German Nexus 4 and it gets stuck in bootloop whenever I turn the power on.
I've had issues with the phone since the last few months - i.e. random reboots, random program crashes.
But recently I tried to root it in order to install the Android L developer preview. It was during the booting process, when my Nexus crashed and it has been unable to boot ever since.
When I push all three buttons (power + 2 volume rocker buttons) simultaneously, I get the fastboot screen.
Choosing the following options has these effects:
Start --> phone tries to boot but gets stuck in bootloop forever and ever
Restart bootloader --> restarts the fastboot screen
Recovery mode --> phone shows the robot with an opened belly and a red warning sign (see photograph)*
Power Off --> turns the power off
Also, it is NOT detected or recognized by my Macbook when I connect the Nexus via USB cable. So it's impossible for me to access the phone via my Macbook.
*This is the screen shown when I try to go into Recovery mode in fastboot:
[can't upload outside link to image]
So this leaves me with no options as I never get further than the 4 turning circles forever and ever.
Is my Nexus 4 broken or is there still a chance to unbrick it? (I have a MacBook, so Windows programs won't work for me)
Of course it's not possible to recognize it when OS is not running.
Download WugFresh toolkit, ADB drivers (Universal) and the factory image. Enter fastboot, connect USB and flash the image
Your phone is not hardbricked, because it boots into the bootloader.
It might be recovered if you can access it with fastboot.
Try uninstalling all related drivers and install the Naked Universal Driver.
Thanks for your replies!
Unfortunately, the programs you mentionned don't work on my Mac (they seem to be Windows-only).
Also, how can I install stuff on my Nexus? Since it is not recognized by my MacBook, I can't load any files onto my Nexus.
And since any command on the fastboot screen only leads to the phone powered off, restart of the fastboot screen or the mentionned bootloop, I cannot perform any actions on the Nexus ...
Go to a friend with Windows.
Problem solved!
Somehow after the 1000th bootloop I finally reached the screen where I could wipe the phone.
And then it finally booted! Now all the data are lost and it's like a new phone, but at least it's working again!
How long was the boot loop? Was it the new boot animation from L?
Because when you flash L, the first boot up may take up to 15 minutes, leading you into thinking it's a boot loop.

Brick Help - Stock Sprint ROM

Hello all,
As fate would have it, the day of me getting my new G5, my G2 went in to a boot loop before I could transfer my data.
I'm desperate to get the data back if possible. Below are the details.
Phone went in to boot loop, then would not turn on. I have tried periodically to turn on the phone, but it will not boot. It will loop at the LG screen and occasionally the Sprint screen. It intermittently charges when connected to power. Today, I hooked up it up to a PC and powered on and got the Demigod screen. Loaded dload mode, but the drivers didn't install. On reboot I got the LG screen with a security error and now it won't power up again.
Any suggestions? Seems like it may be hardware related.
thatguy7 said:
Hello all,
As fate would have it, the day of me getting my new G5, my G2 went in to a boot loop before I could transfer my data.
I'm desperate to get the data back if possible. Below are the details.
Phone went in to boot loop, then would not turn on. I have tried periodically to turn on the phone, but it will not boot. It will loop at the LG screen and occasionally the Sprint screen. It intermittently charges when connected to power. Today, I hooked up it up to a PC and powered on and got the Demigod screen. Loaded dload mode, but the drivers didn't install. On reboot I got the LG screen with a security error and now it won't power up again.
Any suggestions? Seems like it may be hardware related.
Click to expand...
Click to collapse
not familiar with demigod orother stuff, but can you enter into recovery in twrp.? if you can then plug into pc and see if drive appear retreave your data if it does then fix bootloop.
raptorddd said:
not familiar with demigod orother stuff, but can you enter into recovery in twrp.? if you can then plug into pc and see if drive appear retreave your data if it does then fix bootloop.
Click to expand...
Click to collapse
Doesn't TWRP have to been installed when rooting a device? This device is not rooted.
thatguy7 said:
Doesn't TWRP have to been installed when rooting a device? This device is not rooted.
Click to expand...
Click to collapse
yes i assumed this was rooted and hada custom recovery.. sorry i do not know if theres something you could do..might as well say good bye to your data.. but wait and see if theres a way.. am not familiar with the demigod.

Verizon Moto Z Force stuck in bootloop after getting wet

Okay, so heres my issue. Moto Z got wet. It happened during an accident at work and I got a bit side tracked and after a while I noticed the phone was getting really hot so I accidentally restarted it instead of turning it off. Now the phone is stuck in a boot loop. I can get to the boot loader screen. I can restart boot loader via button commands but anything else I try for instance, recovery mode, it goes in to the loop again. My laptop ( windows ) see the phone but not a as a Moto z and I can talk to it with commands on the laptop. I"ve tried flashing with no success. Maybe I'm not doing something right on that part. I'm not trying to unlock the bootloader mainly because I can't considering the model of it. I just want to restore the firmware on the phone. Is it possible? Many thanks in advance.
Yeah I own this cell phone as well. Some trick you could try is to let it drain power wise out. Get a zip-lock page for freezer add a folded paper towel with it and your phone. Leave it in the freezer for 30 hrs. Plug it up to power turn i on. Note if you have changed anything to the firmware to the cell phone this might not work.
Thanks for tip tipstir. I have been trying to restore the firmware for a few days now, researching like hell. I didn't touch the phone for about a week before attempting to restore it. Yesterday I used an all in one tool form a developer here and managed to stop the boot loop. Now all it does is boot to the fast boot screen. It still won't go in to recovery or anything. Flashing fails on RSDlite 3 out of 38 steps. Anything else I can try?

Screen stopped functioning while system still working fine

My phone screen stopped functioning, as in it stays as a black screen no matter what, during boot up, recovery, and Fastboot screen. The phone system itself is still functioning, If I boot into the system I get notifications from my apps which causes the notification LED to go off and I feel notification vibrations.
The most confusing part about this is it happened randomly, I checked my phone in the morning and it was fine, I shut it down and left it for an hour and came back and that's when I started having this issue.
I have tried rebooting the phone many times, and also to recovery and Fastboot and no luck, the screen stays black. I can fortunately access my files through my computer when I connect it through usb and its in the recovery screen. Also, Fastboot recognizes my device through my pc when its in Fastboot mode.
I have checked it around and it doesn't seem anyone has had this issue except maybe this guy:
https://forum.xda-developers.com/mi-9t/help/black-screen-9t-t3999649
But he doesn't seem to have found a solution.
As for my ROM, I was running Pixel Experience Buttery Smooth and I have also used the screen overclock mod:
https://forum.xda-developers.com/mi-9t/themes/screen-overclock-mode-t4079693
However It never ended up working for me so I stopped using it months ago.
If anyone has any suggestions for what I can do, I am extremely desperate as sending this phone for repairs is going to be really hard to do, I am really hoping this is an issue I can solve without doing that.
Thank you for any help
So I decided to try accessing my phone through my Pc by using a software like Vylor to mirror my screen to my PC, the problem is I can't get my device to be recoginzed by ADB. It is recognized by fastboot when in fastboot mode and when it is in recovery I can access all my files through the file explorer. However, when I boot my phone normally it adb does not list it under adb devices when it is connected through USB.
Does anyone know what could be the issue? I am sure I had usb debugging on before by screen stopped working.

Categories

Resources