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
Related
Hello everybody.
I am a Defy Red Lense user with a recently flashed PA 2.14 build (coming from 2.00 version of same ROM). At first 3-4 boots everything was ok, till I made some changes on phone config (namely enabling 16 bit transparency as recommended by it's maker, and then some small changes in Paranoid Android Settings) and asked me to reboot. Ok so I went to reboot and as usual, it booted me into bootmenu, and I chose "boot" and "2ndinit" as usual. After a odd bootloop (where the phone wouldn't go through the blue, then green LED sequence and would then reboot, show Moto logo boot animation, rinse and repeat, etc) that I ended by pressing vol - and entering, again, into bootmenu, I chose again boot and 2ndinit and then something really weird happened:
After almost half an hour i'm still stuck at the very ROM booting animation (the Paranoid Android one, no the Moto logo), just like the guys that tried that new kernel that were reporting 15+ min first boot times. As a clarification, my first boot with just flashed 2.14 took, at most, 5 minutes. And there is another odd vehaviour, concerning the PA boot animation: it gets randomly stuck for a few secs and continues as usual, with no looping from 0 just like the normal loopboot.
So here comes the questions:
- What is really happening? is it really booting or the phone is just stuck in ROM bootanimation? How long should I wait to consider shutting it down?
- Is there some way to get out of it/shutting it down without damaging the device? Can I just pull the battery off without bricking the device?
Looking fowardd for some theories behind this issue :good:
Well, seems like it was OK to unmount the battery while on ROM booting animation, since I haven't had mayor problems after doing so and rebooting. Now the phone works just fine.
Tho im still curious the reason behind this pseudo-bootloop. Thanks for reading anyways :good:
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 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.
Hey guys,
Yesterday evening my phone kept restarting.
I let it go untill the battery reached 0.
Charged it and it kept doing it.
I tried reflashing it with stock rom.
Now it reboots, starts up into android system update thing (blue screen) reaches 32.
Then it says erasing, restarts.
Now its stuck in bootloop i think.
After showing the model screen, it says no command (again with the blue screen) then it restarts.
I tried flashing different stock roms.
I can boot in download mode but i cant seem to get into recovery mode (yes i've really really tried this.)
Any1 can help me? all help appreciated.
So the whole situation :
I was using Google Experience Rom (Android 10). I turned off my cellphone to charge, It restarted but stuck on charging logo. So I forced fully restarted it. and from that moment it goes to Google Logo, Stuck for second to two and then restarted. I tried flashing TWRP, TWRP-fbe, and TWRP 4 cores but when i select recovery from Bootloader it again goes to Google Logo and restart. I also tried to flash stock rom but same issue.
Kindly need help.
Sharjeel_97 said:
So the whole situation :
I was using Google Experience Rom (Android 10). I turned off my cellphone to charge, It restarted but stuck on charging logo. So I forced fully restarted it. and from that moment it goes to Google Logo, Stuck for second to two and then restarted. I tried flashing TWRP, TWRP-fbe, and TWRP 4 cores but when i select recovery from Bootloader it again goes to Google Logo and restart. I also tried to flash stock rom but same issue.
Kindly need help.
Click to expand...
Click to collapse
If you flashed stock rom and still couldn't boot you likely have the BLOD. Did you try the TWRP found in the link below? If so and you still can't boot into that recovery your phone is likely dead, unfortunately.
https://forum.xda-developers.com/nexus-6p/general/bootloop-death-blod-workaround-zip-t3819515