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
Related
Ok i know the fourm is somewhat littered with these posts, and i've tried to do as much myself as i can.
Last night my phone offered the KitKat OTA update.
Its a Nexus 4, with unlocked bootloader, TWRP recovery and root, but no system modifications.
I accepted the update, thinking that it would simply update to kitkat and lose my root. On rebooting to install, the phone launched TWRP by itself, and TWRP ran the update, it went thru various stages of patching things before getting to a step saying something about permissions, where it stopped with an error.
I rebooted the phone and ended up stuck at the new 4.4 boot animation.
I went back into TWRP and tried clearing the caches, and also using the "fix permissions" option but still it hung at the boot animation.
So needing to get the phone working, with minimal data loss, i downloaded the 4.3 stock image, and flashed the boot and system files on in fastboot mode. Hoping to get the phone rolled back to 4.3 where it was before.
Partial Success, in so far as the phone booted, but things are somewhat "weird".
Some data has vanished, such as my call log, and my SMS inbox. Other data seems fine, such as my email client, my wifi settings, google login info, backgrounds etc. But on top of that there are weird quirks, for instance if i swipe down the notification bar, the settings button doesnt work, and i think notifications arent actually showing up either. Similarly, the home button is broken and does nothing. And even more strangely the keyboard appears to be missing!
I'm thinking we're probably at the stage of having to flash a complete factory image, and at least the phones booted so i can pull off my images and things. I'm somewhat pissed about my SMS as i didnt even think of backing them up because it was an OTA update and i assumed it would Just Work.
Any thoughts on what has happened here?
Regards
Kevin
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Same case, mi phone only works with 4.3. Download the 4.3 image, and only flash boot and system, dont flash userdata.
Try flashing the images and making it wipe your device so you don't have any data left. (AKA Clean flash, you did a dirty flash)
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Aragorn84 said:
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Click to expand...
Click to collapse
Yes you do. A clean flash is a full wipe.
Yeh that sorted it, Sorry about the double post above, i tried to edit it but it wouldnt let me.
I copied my images off and did a full wipe and now its working again.
It seems like the forum is littered with these messages, but no-one seems to know the actual cause? I presume its somehow related to the modified recovery not applying the update properly?
Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.
Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.
I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.
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!
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Probably something went wrong in the update process and conflicted with something else.
Anyway: hard reset.
The "no command" screen is just a security screen and it's normal, you need to bypass it to enter to the recovery with a button combination (that now I don't remember, but I never remembered it even though I used to enter in recovery after pressing random buttons combinations lol).
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
cybrdude said:
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
Click to expand...
Click to collapse
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
cybrdude said:
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Click to expand...
Click to collapse
Press power + volume up to get recovery menu.
Was having a similar issue. I'm all stock, unlocked bootloader. Signed for N preview and instantly got the OTA download. It installed and pretty much within a few minutes the bootloops started. couldn't even power down without it rebooting on its own. I got it to power down without turning itself back on through recovery/power down. I let it sit and cool down. Upon reboot.....was doing well, and started to boot loop again. I REALLY did not want to factory reset.
Heisenberg said:
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
Click to expand...
Click to collapse
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
So for me, a factory reset and setting up a brand new phone (no backups of any kind....even from Google) have seem to do the trick. Unfortunate that I lose my wifi password backups. Asking some people for their wifi passwords again is a PIA. Especially the ones who don't know them, and it's a 27 key password from their cable company. Anyone know how to pull just the wifi backups from google?
My thought is one app or setting was causing my problem so I'm slowing adding everything one at a time. PIA really. I don't miss the Froyo days that's for sure.
cybrdude said:
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
Click to expand...
Click to collapse
What happened to your old account?
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.