My nexus 10 is completely stock and locked.
I just got the OTA 5.0 lollypop update and completed it. I always do a factory reset after each major Android update so I wanted to boot into the bootloader and enter into the stock recovery. After selecting recovery from the bootloader I get a blank dark backlit screen for about 30-40 seconds before the "laying down android" appears on the screen. Is it normal to take this long on 5.0? I thought It froze on me the first time because on 4.4 the "laying down android" appears instantly after selecting recovery, then I could [power] and [vol up] to get into recovery and complete the cache wipe and factory data wipe.
On 4.4 I would clear my cache from recovery on a regular basis, this new update would add another 30-40 seconds to the process if what I am seeing is normal.
I think this is the new normal; the first time it happened to me I thought I had f'd something up. I've only noticed on the N10 though, and not my N5, which is a bit odd. I'm not sure if this might be somehow related to the new more secure boot image and kernel for Lollipop (maybe some kind of additional processing to launch Recovery) or simply an effect of the older processor in the N10 somehow, or some unfortunate combination of both, or just random luck. You'd think Recovery doesn't take much juice to launch, but I'm not sure all the stuff going on behind the scenes at runtime.
Anyway, long-winded answer -- but yes, I'm seeing the same thing.
Related
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?
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
sucinimad said:
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Click to expand...
Click to collapse
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
deusfaux said:
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
Click to expand...
Click to collapse
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
deusfaux said:
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
Click to expand...
Click to collapse
In the end, I went through almost the exact experience (including red LED). Running on stock 4.3 image now. Thanks.
my phone is reboot today.
there might be problem with rooted stock kernel?
there are someone has same problem?
Acuity said:
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
Click to expand...
Click to collapse
i got the same issue, look here: http://forum.xda-developers.com/showthread.php?t=2380546
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
ChameleonGeek said:
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
Click to expand...
Click to collapse
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
acejavelin said:
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
Click to expand...
Click to collapse
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
ChameleonGeek said:
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
Click to expand...
Click to collapse
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
acejavelin said:
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
Click to expand...
Click to collapse
I wait several times more than 10 minutes. I wipe data/cache after restart the phone. I found the solution in Google Forum: https://productforums.google.com/forum/#!topic/nexus/D2vKK9rLgh8[1-25-false]
You should only have to wipe /cache from recovery to get out of it. I believe wiping /data is unnecessary (so you can avoid losing your data if you are concerned.
Ended up "solving" this by doing a stock restore via Odin, after which TouchWiz would never load an icon (crash loop). Reinstalled TWRP via Odin, then flashed ViSiON X N3 via TWRP.
--
Morning guys,
I've had some reboots lately and a weird situation last week where I had to do operating system surgery to get the thing to boot at all.... HOWEVER things were going quite well for some time, and it's been rooted and non-stock for months.
Nevertheless I woke up this morning and it was off, I figured the battery had died so I swapped batteries... It boots, it gets to the launcher and it loads the app icons then freezes and reboots... over and over again.
edit: to be clear, as soon as the slider bar touches the right-hand side the phone freezes, the vibration holds for several seconds, and then the device reboots. obviously not what one expects from this operation (having done it before). I was able to wipe the Cache separately... trying to wipe the Dalvik cache all by itself in an advanced wipe does this reboot thing.
OK I said, i will just clear and reflash this.
Going into TWRP, attempting to do a factory reset wipe just freezes, buzzes, and reboots immediately (to the not working OS)... in order to make this all stop I pull the battery, because now the button on the side won't seem to do a hardware poweroff for anything. Just ends up resetting the current reboot.
--
Any advice would be helpful now. I was just going to say forget it and grab the tiniest ROM i could find and ride it out until I upgrade the device, but now I'm just concerned with getting it active. The rebooting in recovery when trying to do a wipe does not make me feel too great. First and only problem I've had with android roms.
Thanks,
Chris
Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.