Hi all,
I got my Wileyfox storm running stock CMOS 13.0 in April and had no problems for about a month. Eventually, I got a pop-up notification with an "Incremental Update" for the phone. I downloaded it and when ready to install, I did so - or at least tried. The update finished and booted into recovery for some reason. At the time I didn't question it and just rebooted the phone from recovery. This led to a boot hang on the "Cyanogen Mod Ready" boot screen.
After searching around for a fix I eventually tried to flash over the stock ROM via Fastboot - which for some reason errored on emmc_appsboot and the phone rebooted itself - with a penguin instead of the Wileyfox boot logo and STILL hangs on the Cyanogen screen. I can also now not boot into fastboot and not boot to fastboot from recovery either (which I CAN still boot to).
Does anyone have any ideas on how to fix this ASAP??? Help would be greatly appreciated!
Many thanks.
I've finally found something that works, unplug the battery for a day or two, then plug in and charge and turn on and might boot properly. Frustrating having to do it every time you get into the bootloop hang and doesn't work every time but still probably salvageable.....I discovered after being bricked for 14 months.
Related
Hi,
Boot looping problem with my m2.
Was flashed
20111012-0056-Nightly-v1.0
(previously was on MIUI 1.10.8, before that was the MS2Ginger rc).
With that version of CM7, the phone will drop call while the battery low dialog pops up sometime. Maybe the cpu vel is too low.
Also when last time this happened, the phone shutdown itself and now it's boot looping.
Some time it can boot over the bootmenu (can see the blue/green led), but after that stuck at the boot logo or boot into black screen.
few time it can boot into Android.
Most of the time it can't even boot over bootmenu, just stuck at the boot logo.
Reflashed and wiped everything and it doesn't help.
Reflashed MIUI on to it and same problem.
Tried to get the logcat running but it only says waiting for device,
though I plugged the phone but got nothing on the command line.
//===update
using RSD Lite to flash the phone will fail because
"error getting subscriber unit"
or "error erasing subscriber unit"
Any suggestion?
Regards,
skygunner said:
Hi,
Boot looping problem with my m2.
Was flashed
20111012-0056-Nightly-v1.0
(previously was on MIUI 1.10.8, before that was the MS2Ginger rc).
With that version of CM7, the phone will drop call while the battery low dialog pops up sometime. Maybe the cpu vel is too low.
Also when last time this happened, the phone shutdown itself and now it's boot looping.
Some time it can boot over the bootmenu (can see the blue/green led), but after that stuck at the boot logo or boot into black screen.
few time it can boot into Android.
Most of the time it can't even boot over bootmenu, just stuck at the boot logo.
Reflashed and wiped everything and it doesn't help.
Reflashed MIUI on to it and same problem.
Tried to get the logcat running but it only says waiting for device,
though I plugged the phone but got nothing on the command line.
Any suggestion?
Regards,
Click to expand...
Click to collapse
Have you tried flashing the stock .sbf via RSD Lite?
Yes was trying that. But the falshing doesn't seem to be completed sucessful.
Stuck at sw update in progress...
RSDlite 4.9 shows error getting/erasing subscriber unit?
It seems like the phone has been disconnected before the flash completes
See this thread and particulary this :
EVEALEX62 said:
It's good for me !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Yououououououououououou !!!!!!!!!!
I don't know if all this is nécessary but it's what I have doing .....
1rst, I have full charge my battery !
I have do this (all step 1 to 11 because "boot up the phone manually" ) with the sbf 2.2.2 officiel but modify whith this post :
The first time don't work but the second time it's good !!!!
So BIG thanks to all people have help (pat972, Atomos33,Emacore,dangpzanco,will5, motodoido) , but especially to r2beta0 et Mikevhl
Click to expand...
Click to collapse
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
Hi,
I have a Note 4 t-mobile that is "brick" right now. and I hope if anyone offer assistance.
It is running Android 6. Ever since the last upgrade the phone would freeze and reboot on its own. I fixed that problem by installing Wake Lock. After that it would still experience sluggish at time but the phone is still very much usable.
Lately, after watching a bit of streaming video the phone would slow down so much that a reboot is needed. But yesterday my last reboot turned my phone into a brick. After that reboot the phone rebooted itself to the download mode. So I took the battery out, waited for a few minutes and put the battery back in and started the phone. Instead of booting normally the phone displayed the message including "set warranty bit: recovery" and then followed by the flashing TWRP splash screen. By "flashing TWRP splash screen" I mean the TWRP splash screen ( with the TEAMWIN logo) would be shown on the screen for a second, then the screen black out for a couple of seconds, then the splash screen is back on for a second, and the screen black out for a couple of seconds, etc, and never successfully boot into TWRP recovery. I had left the flashing splash screen overnight and nothing changed. Connect the phone to my pc via usb and fastboot wouldn't recognize my phone when phone was flashing the TWRP splash screen. So I tried to flash TWRP again by starting my phone in download mode "volume down + power". When I connected my phone to my pc Odin recognized my phone. But when I tried to flash a custom recovery (TWRP or CWM) it seems the download started but never finished (on the phone I could see the progress bar started but never progress further).
Any suggestions would be greatly appreciated1
Additonal info
I just wanted to add that my phone is still running the stock ROM.
Problem solved
Problem solved. Once I used a different cable and the download process actually worked and I was able to flash stock ROM using Odin.
Hello,
I'm currently experiencing a bootloop on my phone, it gets to the resurrection remix logo screen during boot then restarts. I've tried booting into recovery and download mode. When I try to boot into recovery it loads the factory reset screen as usual but when I say yes to the reset in order to launch TWRP it just goes to the LG logo, then remix and restarts all over. I got into download mode one time since this started but since then I've made countless attempts to boot into it again and can't.
What I was doing right before this happened is, I recently completely wiped my phone, flashed stock firmware, wiped, then installed resurrection remix. Everything was going perfect, it started no problem, I went through and cleaned up some apps I didn't want etc normal setup steps then I used the power menu to boot into recovery instead of just using the hardware keys and the bootloop started.
Besides the not booting, the other major issue here is that it never stays connected to the pc via adb long enough to do any actions or flash a single file. By the time the pc sees it and adb sees it, I have roughly 2 seconds before it restarts again.
I really really really need any help I can get please ASAP as this is my mom's phone and she needs it for work in 4 hours. This issue started about four hours ago and I've been trying to fix it ever since. I feel like I have looked everywhere on here and through google but probably missed the solution. Before you ask, I'm 28 not a teenager and work in IT as a career for the last 12 years so don't get the wrong impression. She asked me to work on it because I had set it up a few months back with a lollipop version of resurrection remix and magisk, but in the last month or so she was having really poor performance and issues with settings crashing and a few other apps.
I hope you don't need any more info from me, if you do however I'll be here trying to fix it until she goes to work at least. I really could use the help and would greatly appreciate it.
Thank You
Hi, I've had my Lg g6 for 3 years and ran some custom OS on it, Havoc i belive.
The rom stopped getting updates so i stayed on the last version... It was slow, bad and buggy but it worked.
Yesterday my phone died when the battery ran out and it won't start, all i get in the spinning circle that goes on forever.
The phone does charge, but it just won't boot up, and my attempts go get into recovery fails.
I have to pull the battery to kill it, then tried vol up + pwr and vol down + power, it just goes to the boot animation.
Since it was years ago i had to fiddle with adb/recovery/roms i don't even know where to start, the first idéa was to boot into recovery and wipe dalvik or perhaps reinstall the rom, i think i still got the file on the phone....
I don't even have adb on the computer atm
Any ideas on what to do? Probably the flash is corrupted (or broken) and i feel it won't work for long if i get it working again...
Update: Got into OrangeFox and tried to install Havoc again. error 1 on that one so tried LineageOs that isn't dead.
Hope this works...
Stil booting, didn't bother with gapps and stuff until i know the phone boots.
Fingers Crossed...
Got it working by dirty flash