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!
I was running Cyanogenmod on a Note 4G. For the past month, however, the battery was draining very quickly and the phone would shut off randomly, many times a day. I decided to roll back to MIUI. During the process, something happened to the internal memory, which went from 2/3 full to about 10% full. Recovery disappeared. I tried to use a couple of different MiFlash tools, but those didn't work (it showed it was flashing MIUI but the process went for 3 seconds and then it said it was done. I tried flashing recovery - that didn't work. Tried various methods of flashing a ROM (MiFlash, fastboot, ABD) and those didn't help.
[update] Boy do I feel like a dimwit. I was trying to flash the phone as if it was a Note 4G LTE when it was a Note 2. It's my wife's phone that is the 4G. After pulling out some my diminishing hair the light went on. I then flashed a recovery and now am installing MIUI using the recovery. Yay.
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
you are on a Beta, it is expected, if you need stability flash CM13
GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
I didn't think it was the rom since I reflashed a previously working version, tried the latest version, performed several full wipes, etc. I'm fetching the latest 13.0 and will get the latest opengapps mini for it and see if that helps.
GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
johnnyrichter said:
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
Click to expand...
Click to collapse
I figured
If you don't mind answering one more for me...
I'm on OK3. Is there any path to upgrade to a newer firmware while maintaining unlocked bootloader and root, or is it advised that I stick to OK3 and use only the DEV ABOOT roms like I have been?
johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
N0rth3rnl1ght said:
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
Click to expand...
Click to collapse
My phone ran fine on CM14.1(7.1.1) for at least a month and a half. Not sure why turning the phone off made it stop working with that version. CM13.1 is stable, have you tried that?
Been having the same issues with a 7.1.1 rom Mokee. For the time I've reverted to my S4....
Exact same steps i took. Flashing, wiping, and everything minus external SD.
There is a bootloader update which I did. There is a full update bootloader (I updated and now on PL1) which takes you to Safestrap then back yo TWRP. Others have reported just flashing a PL1 firmware in Odin under AP runs stable.
At this point I'll drop to 6.0 roms, my issues is holding cell service. I can't get any clean flashed rom to give me full data and call service.
I'd like to update firmware/radios if it's possible and won't break my unlock/root and still allow TWRP. Just not sure how to do it properly, starting with my unlocked/rooted BOK3 firmware.
Hello, i am new in this forum, hope to do everything right :good:
I bought a used G935F which shows a very strange behavior ...
When i got it, it stuck in bootloader. I didnt managed to install stock rom via Odin or Smart Switch, it always left Installation after "Installing Update" with 32% and went into a black Screen of death with a blue lonesome light. Went to a shop an bought a microSD card, flashed TWRP 3.1.1 and tried several custom roms. I managed to install three of them after i wiped cache, Dalvik cache, System, internal storage and formated data three times. Rebooted into recovery and installed the Rom. That worked most of the times :fingers-crossed: But after 1,5 to 3 days of usage, the mobile started crashing. First only a reboot, then some application hangs and finally a total crash with only bootloader working. Seems that system and data partitions had gone corrupt. Starting the procedure again leads to a fully working device ... for a short time, few days. Someone ever heard of that strange Kind of behavior?
Can this be caused by a faulty battery?
Tuxs68 said:
Can this be caused by a faulty battery?
Click to expand...
Click to collapse
I don't think so, because my old s7 has this same problem , i flash any firm or custom firm and when the system will boot up it's freezes in the updating system screen and "die" completely for almost one day, when the battery is discharged and i can recharge and flash a firmware again and the same problem occurs . I think that it's a motherboard issue.
Mine is actually working fine ? Managed to install a slim rom yesterday afternoon. If i start an incomplete installation, i also have to wait until battery ist empty. I wiped all caches and partitions and used twrp to install the rom. Tried a few times until installation reached 100%. THEN ... I let the device start and finish boot. That worked for me ... yesterday ... Now i can use my phone without restrictions. Hope for a loooooong time uptime is now nearly 24 hours.
Uptime now 48 hours:fingers-crossed: Hope is rising
Time of Death 11.11 PM. :crying:
Used app, app crashed, several restarts, dead. Internal storage not mountable. Actually black screen of death, i ll wait till battery is discharged. This afternoon i ll take my mobile to a repair shop to have a new battery
I do not believe that is battery issue,most likely motherboard is dying (emmc memory) i have similar symptoms and under warranty my motherboard vas replaced,
Jap, got a new Logicboard
Hi!
Is not my first time flashing a custom ROM but... Since a couple weeks ago I received flashed No Limits and usually in 3-4 seconds my OP5 booted up now needs 10 seconds approximately...
I already wiped everything included the internal storage and re flashed it because I had a problem with Google wakelocks, now everything is smooth and cool except the boot up
May somebody have any idea of a possible solution?
Thanks guys and have a nice day!
VSMiguel said:
Hi!
Is not my first time flashing a custom ROM but... Since a couple weeks ago I received flashed No Limits and usually in 3-4 seconds my OP5 booted up now needs 10 seconds approximately...
I already wiped everything included the internal storage and re flashed it because I had a problem with Google wakelocks, now everything is smooth and cool except the boot up
May somebody have any idea of a possible solution?
Thanks guys and have a nice day!
Click to expand...
Click to collapse
Ten seconds sounds normal for a proper reboot. Three to Four seconds sounds like you were using the 'Hot' reboot option before.
Nothing here to be concerned about.