Device gets stuck on the red droid eye and then restarts... I can't access the SD card but I can get into recovery and bootloader modes... Neither of which does me any good atm lol.
Problem solved thank god.
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
Got a problem with my samsung galaxy s5. A few days ago it was working fine but occasionally randomly rebooted itself. It was be on a bootloop then it will boot up normallly after while.
Randomly the phone had ended up in a bootloop which it is not able to recover from.
i tried using the recovery mode, but that doesnt work. The phone will boot up the first logo after while, but usually it will boot up to a white screen, then will constantky repeat and never end. The screen is working fine, i do not know why it is booting to white screen.
My phone did that with stock ROM bootloop, I found a good ROM and cm12, soz I didn't answer your question that well. But to me the white screen your getting sounds likes you've deleted your boot loader, but don't take my word for it as I'm not a XDA developer, but I'd try and reload boot loader, but wait till you get a reply from xda
Today, my mom's GS5 became stuck in a boot loop and I don't know how it happened since it's her phone and neither does she. I believe it is running 5.1.1 but I could be off by an update or two. The phone is NOT rooted and has never had any software customizations at all.
When booting, the green android pops up for maybe two-tenths of a second saying "installing system update..." and then it quickly changes to saying "no command" at which point the white screen with "T-mobile" comes up and gets stuck there, giving off a small vibration every 13 seconds.
I know the battery was low when this starting happening, so maybe the phone could have been installing an update and the battery died during it, but my mom didn't initiate an update as far as she knows (she's not too tech savy), but I can't say with any certainty how it happened.
I have already tried removing the battery. I can boot into recovery mode and I tried wiping the cache but that didn't fix anything. I can't boot into safe mode.
If anyone has any solutions or ideas, I'd greatly appreciate it! I'm hoping to not have to wipe the internal memory because there are a ton of prom pictures on there from just last weekend that were just taken and haven't been backed up, so my mom really wants those back. I know I've managed to flash my Droid Razr M before when it was rooted and stuck in a bootloop and I managed to keep my internal data somehow, so I'm hoping it is possible
Thanks in advance for any help!
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.
i finall got my phone rooted and twrp installed...but last night i did a reboot just to refresh everything...once it got passed the SHARP logo it went to a black screen and said Camelion work foce closed...every time i hit OK it would pop up again..over and over and over again..so i powered down and tried boot into recover with the volume and power buttons...NO FREAKIN LUCK!!!all it did was vibrate and go to the logo screen...but now it stays stuck on it and wont do anything!!!IF ANYONE HAS ANY IDEAS PLEASE LET ME KNOW...i have prolly gone through the whole internet trying to find a fix but all dead ends..Thank You