Hi guys
I have a nexus 7 that was working perfectly with kitkat until one day it just hung on the boot logo and wouldn't go passed it no matter how many time i rebooted it.
I updated it to lollipop and it now boots up fine but its so slow it almost unusable.
I've tried putting kitkat back on it (and clearing the cache) but every time i do it goes back to hanging at the boot logo.
Any ideas what's going on?
Clearing cache is not sufficient when going back in time, you need to wipe your data, too.
Related
Hi,
I have a nexus 10, rooted running latest nightly CM (19/12) and has been running fine without issues.
I turned it on this morning and its sat at the Google boot logo (and doesnt go any further).
I booted to recovery and did a reflash, wiped cache, wiped dalvic etc ... no joy.
tried a complete factory reset still no joy, is not booting past the google screen.
what next?
thanks
Dan.
DanielGwalter said:
Hi,
I have a nexus 10, rooted running latest nightly CM (19/12) and has been running fine without issues.
I turned it on this morning and its sat at the Google boot logo (and doesnt go any further).
I booted to recovery and did a reflash, wiped cache, wiped dalvic etc ... no joy.
tried a complete factory reset still no joy, is not booting past the google screen.
what next?
thanks
Dan.
Click to expand...
Click to collapse
Sounds like its something in the /system or /boot partitions, maybe. You might need to download the official, completely stock N10 firmware that the device came with and flash that to fix the problem. You can probably just google search for 'stock Nexus 10 firmware' and find a download link somewhere. Of course, if you have a backup file of before you flashed the CM nightly, then you could just restore that and it would work in much the same way don't panic, there is always a way
I got seemingly the same problem. Was copying a movie to the tablet and it crashed as usual. Probably ****ed up the file system or something. Now im traveling for the first time since I bought the tablet and it doesn't work. Grrrreat. :/
Edit: while I was sulking on the way to the airport (actually I wasnt sulking as I just got a new job 20 minutes ago yay) the tablet decided to boot up just fine when I wasnt watching.
My issue is this -- my phone will be running fine for days, even weeks, and will then spontaneously reboot. The phone will then get stuck on the Android "Starting Applications" step and never get any further. I've attempted to wipe cache and Dalvik, and even gone so far as to re-flash the ROM I happen to be running at the time.
This has happened to me at least a half dozen times, and it's starting to frustrate me. I've had this issue with at least 4 different ROMS, including CM 10.1, PA, AOKP, and at least one mixed feature ROM. The only solution I've found at this point is to do a factory reset and system wipe and start from scratch.
Any suggestions on what I might try next time? I'm really at a loss.
dont wipe or clear data after you flash a rom. flash rom and if it installs correctly then clear the cache and thats it. then let it reboot
i used to get stuck in that same screen, but thats because i was clearing data after i had flashed a rom. hopefully that helps
Had this issue. Do a stock flash with the toolkit
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2
go to recovery, do a factory data reset.
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
I am on official 5.0.1 firmware and my phone is rooted
it has been working properly for more than 3 weeks, suddenly yesterday it was switched off because i ran out of battery
after charging it,when I turn it on I am stuck on samsung logo
any help please that doesn't involve wiping data through recovery as I dont want to lose my data?
have you tried to wipe cache only?
also dalvik.
sometimes it helps!
This morning while at work i decided to try another ROM while I had some time. I have been running VRtoxin with no issues as of this morning. I downloaded the latest pure nexus and proceeded to advance wipe everything but storage. I flashed the rom and dynamic gapps. The phone booted up and seemed to be fine until i tried to open a few of the apps i use on a regular basis. When i went to open facebook, hangouts, google plus and some others i would get a notification that unfortunately the app was stopped. I tried rebooting and reinstalling pure nexus and kept getting the same messages. I finally got sick of it and decided to flash my back up i made this morning of VRtoxin. That's when the boot loops started. I have since then mounted system, advance wiped all but storage and tried to flash both VR and pure nexus. Neither will get past boot loop. I have waited 15+ minutes for each.
Thank you in advance.
nvanells said:
This morning while at work i decided to try another ROM while I had some time. I have been running VRtoxin with no issues as of this morning. I downloaded the latest pure nexus and proceeded to advance wipe everything but storage. I flashed the rom and dynamic gapps. The phone booted up and seemed to be fine until i tried to open a few of the apps i use on a regular basis. When i went to open facebook, hangouts, google plus and some others i would get a notification that unfortunately the app was stopped. I tried rebooting and reinstalling pure nexus and kept getting the same messages. I finally got sick of it and decided to flash my back up i made this morning of VRtoxin. That's when the boot loops started. I have since then mounted system, advance wiped all but storage and tried to flash both VR and pure nexus. Neither will get past boot loop. I have waited 15+ minutes for each.
Thank you in advance.
Click to expand...
Click to collapse
Try manually flashing each stock IMG
Boot, system, vendor, recovery. Then re flash twrp then try restoring your backup.
Yup. That's exactly what I would do. I would do. Report back and let us know!
Thank you for the advice. Before the response i just started over completely. Reflashed back to stock, flashed twrp and rooted. I'm back on VRToxin now with no problems.
I'm a ROM flashing junky, what do i have to do differently now on the 6p? I've never had this problem on my N6. On my N6 i would advance wipe everything but storage and then flash a new ROM with Gapps and never had this happen.