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:
Related
Hi Guys
When I turn my phone on, after the Galaxy S first screen, the screen is multi-colored for about 1 second before going to the boot animation. Once the boot animation appears the screen is fine.
That's not a problem. What is a problem is booting into recovery, the top of the screen has a few blue lines. It still operates as if it is in recovery, as if I press the power button it reboots - but if I press down once, then power, it's not rebooting. So it looks like it's just the screen can't display what's being sent to it. So I can't do anything in Recovery like installing the auto-phone record, screen capture service or extended power menu. It will also be a problem if I come to install another ROM.
Does anyone know why? It started happening after I flashed a new ROM - I flashed the new ROM because the phone was constantly freezing when running certain apps (and needed the battery removed to restart the phone) - it's no longer freezing.
thanks
I'm not sure but,i think it because you don't have the good bootloader.For example,if you flash a rom from Froyo to gingerbread,you need to choose a rom with the gingerbread sbl(bootloader) include.
So to avoid this problem,just re-flash the entire rom with boot loader included.
Just go there http://forum.xda-developers.com/showthread.php?t=1102881
thanks I'll try that
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.
[Q&A] [ROM] Omega v2.1 boot loop after enable ultra low power saving mode S5 SM-G900I
Hi all,
Long time lurker, first time poster!
I need some assistance on what I can do to get my rooted Telstra (AUS) Galaxy S5 (SM-G900I) phone to get out of boot loop (or hang). Currently running Omega v2.1 and TWRP 2.8.5.0.
Problem first started when I enabled ultra low power saving mode and then rebooted my phone (using 4 way reboot menu, fast reboot) as it became non-responsive after enabling it. When the phone tried to reboot, it got to the omega logo and it now just spins around and around. I've left it for a good 10 minutes or so but it keeps spinning. Took out battery for 30 seconds, does the same thing when booting up again.
So first step I tried was going into TWRP, made a backup of all partitions to my external SD, then wiped dalvik cache and normal cache. Tried booting into Omega after that and it does the whole "Andriod is upgrading" thing and goes through all the 300 or so apps, then it goes to the "Starting apps." and the screen goes from blue-ish to black and white (as if ultra power saving mode is on) and stays on that screen, no boot. I suspect that because that mode is on that the CPU is throttled down a lot and it's going to take forever to get anywhere. If that's not the case, something else could be wrong however you can clearly watch it go from a blue-ish box to black and white. It's been "Starting apps." for about 15 minutes now. (edit: wrote this entire thread, 30 minutes now still sitting on "starting apps") (Edit2: it has been 24 hours since this thread post and it is still stuck on "starting apps").
Does anyone have any ideas on what I can do to get it out of ultra low power saving mode without being able to boot into Omega? Or any ideas on how to get it to boot fully? It seems to make it quite far into the boot process but it won't fully boot. Battery has to be taken out for reboot as it just doesn't boot. I'd like to avoid a full wipe if possible but if that's the only option I guess I'll have to take it.
Any tips would be appreciated!
FIXED
Hi all,
I fixed the problem by taking a stab in the dark and flashing with the original Omega ROM (v2.1) again and NOT doing a full wipe. This wiped the SYSTEM partition reinstalled all the apps (where the problem was) and installed Omega ROM again. It booted fine and it was still on ultra low power saving mode when I landed at the home screen. Everything was 100% intact!
Just in case anyone comes into this situation: find the exact image of the ROM you have installed and flash it (NO FULL WIPE) again and you'll clear the system partition and reinstall all the apps. Should clear up this issue if you can't get past the boot logo or have some corrupt app stopping the boot.
ok so first off this phone was brand new when i got it 6 months ago. no matter what rom i flash or kernel combo, my phone always ends up 'freezing' up on me. after sitting there staring at the unresponsive phone i will either yank the battery or keycombo reboot. upon trying to boot again it doesnt get past the red and blue writing about enforcing whatever just sits there. so i boot to twrp but it hangs at splash screen if i wait a long time it will eventually go but im talking like 30 mins. weird right? when i do get back in i can restore a backup or wipe, clearing cache and dalvik does nothing it just sits at boot logo. and flashing kernels does nothing. what could be doing this?
I'm currently installing lineageos in my phone, it is booting for the first time and it looks fine, I've heard that the first time booting up the phone with a custom rom can take a while, 1-10 minutes. My phone has been in the lineageos booting screen for quite a while now and im getting worried. Do i need to wipe my phone and reinstall lineageos? EDIT: It is now in the same boot screen for around 40 minutes now. Edit 2:It got stuck on one part of the animation and the only thing in he screen is the curved blue line without any animations EDIT 3: Problem is solved, i reinstalled lineageos and it is working well