Upgraded to CM11 from CM10, using the 03/01/14 build and full GApps. On first boot, there was no homescreen though individual items could still be opened (ie settings and items on the lock screen widget). It then got stuck in an infinite startup sequence (to the point where the battery died from a full charge), reflashed cm11 and now gone with just core gapps and its back to no home screen.
Does anyone have any suggestions?
Thanks
EDIT
Re installed again and it worked - no idea what i did differently, but its working great now!
Related
Here is the story. I've got my Vibrant as a replacement for my older one two weeks ago. The old one had a problem with Home button responsiveness and at the end I decided to go with replacement. After some testing with identical firmware (freshly flashed) on both phones I found that the the new one boots much faster - around 12 sec difference (the time my audio widget is fully loaded) and overall I was very happy, until today when my phone screen turn of during some work on the browser. The buttons light was on and the screen became black.
1. I did battery pool. First boot was very slow. Force close for some koush process ( probably clockworkmod) came out .
2. I did 'wipe cache' - multiple force close after that
3. Factory reset - it was somewhat booting very slow and I decided to go with Odin.
I was able to put the phone in downloading mode and flash JFD with repartitioning. Everything looked ok during the process, but after reboot it plays Tmobile animation, startup sound, shows the letter S and stucks there.
I am able to get in stock 2e recovery. If I choose reinstall packages it goes to clockworkmod recovery (I thought clockworkrecovery should disappear after flashing with odin, but it is there) I tried flashing different usb ports - no difference.
The phone was with stock JI6 firmware, rooted with OCLF, ROM Manager with clockworkmod installed. Was working fine till today. I didn't experience any lag issues and neither of the lag fixes were installed or tested.
I played with clockworkmod recovery options format: system, data, sdcard.
I was not able to format boot - some error.
I am not a very good writer... sorry if somebody gets upset.
I will appreciate any help or idea.
Thanks
Fix for your problem
Sounds like some of the rom is either corrupted or the factory reset did not have J i-6 in it.......not enough info. Personal message me and i ll help you fix this problem.
TL;DR: I have flashed the stock 4.2.1 image through fastboot, and yet my n7 wifi still reboots continuously at the google screen with the little unlocked lock.
Background: I have had the device for about 3 months, no real problems with it before this. I was reading yesterday night and i fell asleep, and thus instead of being on my desk all night the device was under a blanket. When i woke up, I opened the cover and found it on the google screen with the lock. It was warm, but not incredibly so. I thought it was weird that it had rebooted and apparently frozen, but i held down the power to turn it off. when i turned it back on, it started the google screen, then went black, then started the google screen again. Seems like there may be some sort of a kernel issue that is keeping it from booting. The next thing i did was to go into recovery (had CWM at this point, and it was rooted as well but that's a moot point if i can't get into the system.) and i did a backup, then wiped data and did a restore from the backup that i had just made. after rebooting, it made it all the way into the system, and seemed ok. I set it down, and a few moments later it turned off and started doing the loopy google screen thing again. Next, I went into recovery and wiped data/factory reset, and tried to boot up. no luck, still looping. Next, i grabbed the 4.0 toolkit from the dev section and tried to flash the stock recovery from that, but it was proving troublesome so i just downloaded the image myself and fastbooted then replaced cwm with the stock recovery, wiped everything, and flashed the 4.2.1 image. that should have worked, from what i understand, but no, still being loopy. I re-wiped and flashed, tried 4.1.2 instead, that didn't work, and i re-did 4.2.1. after flashing 4.2.1 and then leaving it boot looping for a little while, i noticed that it sometimes made it into the boot animation and then the animation froze and it rebooted and looped more. after a few more tries, powering it off, leaving it for a few min, and powering it on again, it booted all the way to the welcome screen to pick a language and then froze. some number of loops later, it made it all the way to picking a wifi network and froze. I have yet to make it past that point. Thinking it may help, i fastbooted CWM onto the device, so i have a more capable recovery now. I am now going to look into pushing a non stock rom to the device to see if that will help at all.
Any ideas on what on earth could have caused this? Was it just that the device was a little warmer than usual for a while?
Any ideas on how i can fix this? Much appreciated!
Lastly, should i consider looking at sending it back to google? I didn't think there was anything wrong with the hardware, but i'm not sure.
Thanks!
Update: After leaving the system repeating it's loopy boot thing for about 45 min, it seems to have finally booted into the system, and has yet to reboot again. I have no idea why this happened in the first case, nor why this finally worked in the end, but so far it seems ok.
More: Ok, so it still seems to be looping a lot. I have no idea why still. I'm having trouble getting it to boot back into the system, so hopefully something helps fix this.
Ok, so a day later it seems to have settled down such that there's very little looping on the google logo screen any more; now it just tends to randomly reboot when in use. this is quite frustrating, but seems more similar to what others have reported to be the case with 4.2.1. oddly, i never had these reboot issues before it decided to fail the first time, so i'm not sure if this is just because ii'm on 4.2.1. I may look at flashing back to 4.1.2 and staying there, i suppose it can't hurt. does anyone else have any ideas as to what could be going on?
I had CM11 snapshot M5 running on my tablet and out of the blue I had Google Plus f/c on me while not in use. Then Chrome f/c while not in use, then I think it was YouTube f/c when not in use. I restarted the tablet and it got to the CM loading screen, then restarted itself and now it will not go past the intro screen with the Google logo and the lock at the bottom. It will sit on the Google screen for about 10 seconds then reboot and it just keeps doing that.
I managed to get into TWRP and updated to TWRP 2.7.0.0 I have 2 ROM zips in my cmupdater folder on my sd so I did a full wipe and tried to install both of those, but they have the same outcome of going to the Google screen then rebooting.
If anyone can help that would be so much appreciated. Nothing was updated but apps from what I can tell so I have no idea what happened and why it is still happening after a full wipe and fresh flash.
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!
Hi!
Rom: CM12 20150320
Recovery: CWM 6051 touch
Bootloader: MAKOZ30f (if that helps)
About a week ago i unlocked and flashed my nexus 4 to CM12. After that the phone has worked well until today. The phone was acting a bit laggy, so I thought a reboot would be nice. However, after the reboot it only gets past the first google screen. After that it gets stuck in a weird animation (see picture) I have never seen before for about 5 minutes, and after that the screen just shows a black image (completely black but you can see the screen is still on). This repeats when I retry. I can still enter bootloader and recovery.
Any idea why this happened? And how to fix? I guess a reset (or reflash?) could solve it, but it would be nice if that was not necessary. =)
I made two observations during the day, related?
-some app prompted for some CM12 updates, but I had no time to deal with them at the time so I just closed the app.
-while playing music from spotify while working, the sound lagged for a second at a time, about one time per hour.
Thanks in advance! Let me know if there are details missing!
albinhj said:
Hi!
Rom: CM12 20150320
Recovery: CWM 6051 touch
Bootloader: MAKOZ30f (if that helps)
About a week ago i unlocked and flashed my nexus 4 to CM12. After that the phone has worked well until today. The phone was acting a bit laggy, so I thought a reboot would be nice. However, after the reboot it only gets past the first google screen. After that it gets stuck in a weird animation (see picture) I have never seen before for about 5 minutes, and after that the screen just shows a black image (completely black but you can see the screen is still on). This repeats when I retry. I can still enter bootloader and recovery.
Any idea why this happened? And how to fix? I guess a reset (or reflash?) could solve it, but it would be nice if that was not necessary. =)
I made two observations during the day, related?
-some app prompted for some CM12 updates, but I had no time to deal with them at the time so I just closed the app.
-while playing music from spotify while working, the sound lagged for a second at a time, about one time per hour.
Thanks in advance! Let me know if there are details missing!
Click to expand...
Click to collapse
Flash stock image from google... maybe some stuff from CM12 go wrong...
Not use CWM recovery...better TWRP...this is updated.