Hey Guys,
Running on marshmallow and the phone got rebooted an hung at optimizing apps says 1 of 1 . Quite some time and doesn't load into the main os. can some on advice ?
norysrinivas said:
Hey Guys,
Running on marshmallow and the phone got rebooted an hung at optimizing apps says 1 of 1 . Quite some time and doesn't load into the main os. can some on advice ?
Click to expand...
Click to collapse
Try wait little more time. I must wait 20 minutes but with another situation and it boot up. Give also information about rom and kernel which you use (build version too of both) will be easy.
Did a wipe cache partition which didn't help, later wiped to factory reset via recovery mode which helped to regain the device access.
How ever the device was running on stock android on android 6. It just rebooted automatically and never came up. Though as said about factory reset helped.
The optimization took me more than 30min. I just left it and did my jogging.
sent from OPO using Tapatalk
Related
On my i747 I installed Omni ROM 4.4.3-20140620-d2lte-HOMEMADE. After install and reboot I noticed the load time was in excess of five minutes from the moment the Omni logo splash appears. Is this normal? I can't be sure but I think each boot takes longer, (so tired right now). Any suggestions?
I am experiencing the same. I flashed to my SPH-l710 using the latest from http://forum.xda-developers.com/showthread.php?t=2591298.
I would love to go back to using this rom. I absolutely love it miles above CM but the boot time is easily in excess of 10 minutes.
exarkun631 said:
On my i747 I installed Omni ROM 4.4.3-20140620-d2lte-HOMEMADE. After install and reboot I noticed the load time was in excess of five minutes from the moment the Omni logo splash appears. Is this normal? I can't be sure but I think each boot takes longer, (so tired right now). Any suggestions?
Click to expand...
Click to collapse
Talk to whomever provided the build, as that is not an officially supported device (in addition to not being present at dl.omnirom.org - the HOMEMADE part of the filename is a dead giveaway).
First bootup after installation is always long - if subsequent boots are long there's a problem though.
It is normal if it is your first boot after flashing new rom...
It just that the Android is installing (preparing apps for first use)
The same will happen when you clear Dalvik cache or change runtime from Dalvik to ART.
If it is the same on second and other boot then it is problem with your rom
Dodgy apps (or heaps of apps) can cause that too. Is it still slow if you do a factory reset ? (do a backup before hand so you can restore all your data). As pointed out above if you do a factory reset the initial boot will still be slow
Thanks everyone. I went ahead and wiped the drive then installed CM11 for the i747 (d2att) and all is well with booting. One day I will check out omnirom again because the features are just insane!
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
Hi everyone,I got in deep serious **** while trying to decrpyt my Samsung S5, which is encrypted using its official settings app. It was showing android logo while decrypting for almost 2 and a half hours. Then I think the device froze since it was taking so long in comparison to encryption that apporximately take 15 minutes max. So I removed the battery and restarted it and UNLUCKILY got the message while starting that decyption interrupted, do Factory reset. Now whenever the TWRP recovery trying to wipe the data, it fails. IF ANYONE know how to restore the phone, Please tell me.
Thanks in advance :good:
Sachinaditya5 said:
Hi everyone,I got in deep serious **** while trying to decrpyt my Samsung S5, which is encrypted using its official settings app. It was showing android logo while decrypting for almost 2 and a half hours. Then I think the device froze since it was taking so long in comparison to encryption that apporximately take 15 minutes max. So I removed the battery and restarted it and UNLUCKILY got the message while starting that decyption interrupted, do Factory reset. Now whenever the TWRP recovery trying to wipe the data, it fails. IF ANYONE know how to restore the phone, Please tell me.
Thanks in advance :good:
Click to expand...
Click to collapse
try this twrp https://www.androidfilehost.com/?fid=24459283995296044 and if it is not working flashback stock recovery my old s4 fixed by stock recovery
It works
Flashed the TWRP recovery 3.0, and hey it really worked . Thanks :good:
Hi there,
I started this topic because I am out of options and I don't know what to do at this point.
My Phone is a XT1562 DualSim.
I recently flashed http://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690 and I also installed "MODEM" (MPD24.107-70) from page 1, but not right away.
First I wiped everything expect "internal storage". The phone booted but it restarted during boot (which might be okay) but then it rebooted again during boot. The boot process finally finished and I got to the screen "Android is starting - Optimising app x of y." The phone rebooted even during that process and that is definitely not normal I think. So after a couple of reboots android did finally optimise all apps but the phone did still reboot withing the first 30 seconds after it was booted.
From here I did a lot of testing and doing. These are my findings:
- When I set phone to flight mode / airplane mode it does NOT reboot... Hurray!
- When I flash another ROM (Official CM 13, http://forum.xda-developers.com/mot...m-cyanogenmod-13-preview-moto-x-play-t3252255) the phone runs like a charm, NO reboots whatsoever.
- - But as soon as I flash gapps and the phone is booted, I get the reboots again (usually within the first 30 seconds).
- - Again setting the phone to flight mode prevents itself from rebooting.
- - Apparently it doesn't matter what version of gapps I flash. I even tested the light version (ARM, 6.0, Pico, from http://opengapps.org/). It still reboots. I also tried gapps mini and stock.
Oh and I don't think its MODEM (mentioned above) related, because I faced these problems already before I installed / updated the MODEM. Well I thought its MODEM related, that's why I went back to MODEM stock version MPD24.107-52 but that did't help either. I should mention that I am not sure if I had MPD24.107-52 installed originally but spetrum (the rom developer) pointed me to that version: http://forum.xda-developers.com/showpost.php?p=69129552
I also restored my working TWRP backup from an android I used for month and guess what, yep, reboots
brrrrr this is frustrating
I never experienced that before and frankly I am out of ideas.
Anything is welcome and appreciated
Thank you
If nothing helps reflashing the whole firmware is always an option
minimale_ldz said:
If nothing helps reflashing the whole firmware is always an option
Click to expand...
Click to collapse
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
I always go back to flashing stock rom with rsdlite whenever things went wrong and I can't solve it by flashing small fixes.
rancor187 said:
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
Click to expand...
Click to collapse
I mean full stock firmware you flash with fastboot or RSD. Roms are usually only system + kernel, so not very helpful in your case
Guys! Good news. I did go back to stock firmware and from there to official CM13. Of course I had to root and install TWRP again but it was worth it.
I lost a few days spending my time with it but I'm glad its all good now thanks to you.
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt