Database Users

Stuck on Google screen after updating to 4.2

I have an unlocked and rooted stock Nexus 7 with the stock rom. I Just performed an OTA update to Android 4.2 and now the Nexus is stuck on the Google splash screen with the unlocked padlock symbol. I have tried booting to recovery with the Wugs Rootkit and it shows a an android with a red warning triangle above it. Please can anyone help me to fix this.
I have a PC with Wugs Toolkit 1.5.5 and I have the Google Nexus 7 Root Toolkit 3.2.0.
Please anyone know how to the fix this as I have no idea.

Exact same problem
randomvector said:
I have an unlocked and rooted stock Nexus 7 with the stock rom. I Just performed an OTA update to Android 4.2 and now the Nexus is stuck on the Google splash screen with the unlocked padlock symbol. I have tried booting to recovery with the Wugs Rootkit and it shows a an android with a red warning triangle above it. Please can anyone help me to fix this.
I have a PC with Wugs Toolkit 1.5.5 and I have the Google Nexus 7 Root Toolkit 3.2.0.
Please anyone know how to the fix this as I have no idea.
Click to expand...
Click to collapse
I have the exact same problem. For the record I had the very latest version of SuperSU Pro that got updated today (0.98, I think) with survival mode activated. Don't know if that's the cause of the problem or just the fact that it's rooted.

Dang. Same thing here. And I also just installed the new SuperSU before applying the OTA.

Try the two posts right above this one.
I know the thread Stuck on Google Screen has some solutions that may help.
Sent from my Nexus 7
Clean ROM 2.0 - leankernel .5

ezas said:
Try the two posts right above this one.
I know the thread Stuck on Google Screen has some solutions that may help.
Click to expand...
Click to collapse
Well, since you replied, this thread is now at the top of the stack, so there's nothing above it. I'm getting old and blind, but I don't see a thread and can't find one with search called anything like "Stuck on Google Screen". Except this one, of course.
Edit...Eh, nevermind. I just flashed the full 4.2 from Google instead of mess with this any more. Restoring apps now.

CSX321 said:
Dang. Same thing here. And I also just installed the new SuperSU before applying the OTA.
Click to expand...
Click to collapse
I did exacty the same thing the app had already updated before I could do the Android 4.2 update. I fix the isue. I had to do restore to stock Rom 4.1.1 then update to 4.1.2 and then to 4.2 then recovered some of the stuff I lost with an old Titanium Backup I did a few weeks ago.

Recovered mine
Hi all,
(I'm the second poster)
I managed to get my Nexus 7 back, although losing all the data, which I think cannot be avoided.
Here is what I did, for dummies:
- Reboot into fastbood mode. For this, hold the power, volume up and volume down button.
- Use the Nexus 7 Toolkit (I donated to get the latest version) or the Nexus Root Toolkit (which I guess works as well) and flash the google factory stock rom.
- If using the Nexus 7 toolkit, at the beginning I selected that I had Android 4.2 installed.
- After flashing, my tablet was as if just taken out from the box (but still unlocked). All my old apps got downloaded automatically, although the settings / game progress were not saved. Fortunately I have some Titanium Backup backups from a little while ago.
- After all apps got downloaded, I put the tablet in fastboot mode again, and I rooted it with the Nexus 7 toolkit via option 4 and then sub-option 2.
Sorry if I said some obvious stuff, but I am not an expert, and wanted to help other non-experts
Good luck to everyone.

aran80 said:
Hi all,
(I'm the second poster)
I managed to get my Nexus 7 back, although losing all the data, which I think cannot be avoided.
Here is what I did, for dummies:
- Reboot into fastbood mode. For this, hold the power, volume up and volume down button.
- Use the Nexus 7 Toolkit (I donated to get the latest version) or the Nexus Root Toolkit (which I guess works as well) and flash the google factory stock rom.
- If using the Nexus 7 toolkit, at the beginning I selected that I had Android 4.2 installed.
- After flashing, my tablet was as if just taken out from the box (but still unlocked). All my old apps got downloaded automatically, although the settings / game progress were not saved. Fortunately I have some Titanium Backup backups from a little while ago.
- After all apps got downloaded, I put the tablet in fastboot mode again, and I rooted it with the Nexus 7 toolkit via option 4 and then sub-option 2.
Sorry if I said some obvious stuff, but I am not an expert, and wanted to help other non-experts
Good luck to everyone.
Click to expand...
Click to collapse
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
---------- Post added at 09:49 AM ---------- Previous post was at 09:44 AM ----------
aran80 said:
I have the exact same problem. For the record I had the very latest version of SuperSU Pro that got updated today (0.98, I think) with survival mode activated. Don't know if that's the cause of the problem or just the fact that it's rooted.
Click to expand...
Click to collapse
I installed the latest SuperSU version but have not updated yet, what do you recommend I do, remove the SuperSU software or not uprgade at all at this time?
Thanks,
JBIRD

jbird92113 said:
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
Click to expand...
Click to collapse
Before doing all that, plug your Nexus in and make sure USB Debugging is enabled, and also its set to camera mode, not MTP.
Goto command prompt, and use:
adb reboot recovery
You will then see the Android with a red triangle, at the same time quickly tap power and volume up, you'll then be taken to a blue screen.
Choose wipe cache.
Also you could factory reset?
Then reboot
Hope this helps.

Nexus 7 toolkit
jbird92113 said:
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
Click to expand...
Click to collapse
Sure First I thought about using Wug's Toolkit, but I saw it was not updated yet to handle Android 4.2 stuff, whereas the Nexus 7 Toolkit was.
You can download it from http://forum.xda-developers.com/showthread.php?t=1809195, but only version 3.2.0 which does not have Android 4.2 stuff. To get the latest version (3.8.2, updated yesterday 14 november), you have to donate and wait until the developer sends you a key. I donated 5 pounds but the developer says any amount is OK. I got my key 1-2h after donating.

aran80 said:
Sure First I thought about using Wug's Toolkit, but I saw it was not updated yet to handle Android 4.2 stuff, whereas the Nexus 7 Toolkit was.
You can download it from http://forum.xda-developers.com/showthread.php?t=1809195, but only version 3.2.0 which does not have Android 4.2 stuff. To get the latest version (3.8.2, updated yesterday 14 november), you have to donate and wait until the developer sends you a key. I donated 5 pounds but the developer says any amount is OK. I got my key 1-2h after donating.
Click to expand...
Click to collapse
Thanks. Do you recommend that I remove SuperSU prior to running the OTA or even for that matter just hold off on upgrading for now?

jbird92113 said:
Thanks. Do you recommend that I remove SuperSU prior to running the OTA or even for that matter just hold off on upgrading for now?
Click to expand...
Click to collapse
Well, I can only tell you the situation that I had before installing the 4.2 OTA:
- Unlocked
- Stock Android 4.1.2
- Rooted with SuperSu 0.98 and survival mode activated
Maybe the problem was to be rooted; or to have SuperSU; or to have specifically SuperSU 0.98; or to have survival mode active... I don't know.
If you want to be fairly sure to not have any problems, I would uninstall SuperSU. There is an option to do a full unroot inside SuperSU itself. Maybe before that to be even safer, you could even uninstall all the root-requiring applications?
Then, reboot, apply the OTA, and cross your fingers
Then you can root again with Nexus 7 toolkit, it was done very fast, and you will have supersu again.
Rooting or unrooting should not wipe your data.
From now on I think I will not have the survival mode activated before an OTA, just in case, as I now know how to unroot / root quite fast.
Good luck

randomvector said:
I had to do restore to stock Rom 4.1.1 then update to 4.1.2 and then to 4.2
Click to expand...
Click to collapse
I didn't bother with reverting to stock. I just booted into fastboot mode, which I was still able to do, and installed the factory 4.2 image from https://developers.google.com/android/nexus/images. I develop apps, so I already had a full development environment and the needed tools installed.

aran80 said:
Well, I can only tell you the situation that I had before installing the 4.2 OTA:
- Unlocked
- Stock Android 4.1.2
- Rooted with SuperSu 0.98 and survival mode activated
Maybe the problem was to be rooted; or to have SuperSU; or to have specifically SuperSU 0.98; or to have survival mode active... I don't know.
If you want to be fairly sure to not have any problems, I would uninstall SuperSU. There is an option to do a full unroot inside SuperSU itself. Maybe before that to be even safer, you could even uninstall all the root-requiring applications?
Then, reboot, apply the OTA, and cross your fingers
Then you can root again with Nexus 7 toolkit, it was done very fast, and you will have supersu again.
Rooting or unrooting should not wipe your data.
From now on I think I will not have the survival mode activated before an OTA, just in case, as I now know how to unroot / root quite fast.
Good luck
Click to expand...
Click to collapse
Thanks. I didn't purchase the pro version so I don't have the survival mode feature . I may just wait and see if there are any other folks running into the same issue. Thanks again

Has anyone figured this out yet? I'm also stuck on the Google boot screen after installing the 4.2 OTA on my stock, rooted Nexus 7, and I've tried the following:
- Wiped cache.
- Re-flashed the 4.2 OTA (build JOP40C) from stock recovery via adb.
- Flashed TWRP (via Wug's Root Toolkit) and renamed Superuser.apk, assuming that was the issue.
- Re-flashed the 4.2 OTA (build JOP40C) from custom recovery via WugFresh's Nexus Root Toolkit v1.5.5.
Nothing worked -- it's still locked up on the Google screen at boot. How do I fix this (ideally without wiping my user data)?

rcs408 said:
Has anyone figured this out yet? I'm also stuck on the Google boot screen after installing the 4.2 OTA on my stock, rooted Nexus 7, and I've tried the following:
- Wiped cache.
- Re-flashed the 4.2 OTA (build JOP40C) from stock recovery via adb.
- Flashed TWRP (via Wug's Root Toolkit) and renamed Superuser.apk, assuming that was the issue.
- Re-flashed the 4.2 OTA (build JOP40C) from custom recovery via WugFresh's Nexus Root Toolkit v1.5.5.
Nothing worked -- it's still locked up on the Google screen at boot. How do I fix this (ideally without wiping my user data)?
Click to expand...
Click to collapse
Same here, didn't try all you did.
I'll try to descibe what I did to see similarities,
I had my N7, Rooted 4.1.2, unlocking via face-lock, , I has just installed last update from super su, had root protection enabled,
I'm willing to pay 2.7 Bitcoins, (~31$) to someone helping me fix it without reinstalling everything.

Just an update on my situation: Since adb still worked from the Google boot screen, I managed to batch pull my TitaniumBackup folder down onto my PC. I went ahead and flashed back to stock (good guide here, for anyone who needs it: http://forum.xda-developers.com/showthread.php?t=1781250), updated, re-flashed SuperSU and Busybox, and restored all my backups without any issues.
First time I've actually had to do that, but I'm happy to see that my daily TiBu backup schedule paid off, and I'll probably feel much more confident repeating the process in the future.
Anyway, I'm assuming the issue had something to do with the SuperSU apk, as others here have guessed. I, too, had SuperSU's survival mode enabled (which I've disabled) -- and I also had OTA RootKeeper installed (which I've now ditched), In the future, I'll probably just err on the side of caution and fully unroot before applying an OTA; it's easy enough to just re-root, rather than rolling the dice with any sort of survival mode.
And if SuperSU ISN'T the issue, I'd sure like to know what is!

Hi guys, my girlfriend updated to 4.2 yesterday, and it was fine up until her battery died. so she charged it and then tried to turn it on, and it was in an endless boot loop first starting with the google logo coming up, then itll go kinda staticy and go to the X (and sorry for my future description) but then the screen will look like its in the matrix? If that makes sense. I can provide a picture if needed, but then itll just reboot and do the same thing over and over again. We went to Virgin and called samsung and they both said the same thing that the system would have to be recovered. Virgin, however directed me over to use Odin. I've never really used Odin before and am not sure what to do, so would someone mind helping me out with this issue? i've tried going into recovery menu as well, but it doesn't work. I really appreciate the answer in advance!!!!! Her phone is the galaxy nexus.

AdmiralAqbar said:
Hi guys, my girlfriend updated to 4.2 yesterday, and it was fine up until her battery died. so she charged it and then tried to turn it on, and it was in an endless boot loop first starting with the google logo coming up, then itll go kinda staticy and go to the X (and sorry for my future description) but then the screen will look like its in the matrix? If that makes sense. I can provide a picture if needed, but then itll just reboot and do the same thing over and over again. We went to Virgin and called samsung and they both said the same thing that the system would have to be recovered. Virgin, however directed me over to use Odin. I've never really used Odin before and am not sure what to do, so would someone mind helping me out with this issue? i've tried going into recovery menu as well, but it doesn't work. I really appreciate the answer in advance!!!!!
Click to expand...
Click to collapse
AdmiralAqbar, if you need to return your Nexus 7 to stock, follow this guide: http://forum.xda-developers.com/showthread.php?t=1781250
You could also boot into recovery (hold Volume Up and Down keys while you power on, then select Recovery from the list), and then try to return to stock from there (in Recovery, press Power and Volume Up at the same time, and there should be an option in the resulting list).

rcs408 said:
AdmiralAqbar, if you need to return your Nexus 7 to stock, follow this guide: http://forum.xda-developers.com/showthread.php?t=1781250
You could also boot into recovery (hold Volume Up and Down keys while you power on, then select Recovery from the list), and then try to return to stock from there (in Recovery, press Power and Volume Up at the same time, and there should be an option in the resulting list).
Click to expand...
Click to collapse
I didn't even realize this was a nexus 7 thread i'm sorry! I just noticed the same problem so i clicked into this thread haha, she has the Galaxy Nexus i9250. And i tried that, and then it'd just reboot. I'm assuming the recovery menu is corrupt maybe? Would i be able to follow the same steps in that guide for her phone?

N4 upgrade failed

Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA

Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?

If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.

BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...

As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?

Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?

Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...

Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium

Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4

TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...

Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.

tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.

[Q] Failed OTA update help?

I just got the OTA update to Android 4.4, and being eager to get it installed, hit the install button right away. I told a few people I was going to be a few minutes while installing the update... and tapped the button.
That was three hours ago, roughly.
I'm on a rooted nexus 4 with CWM Touch edition installed as a recovery. I don't know exactly what version right now but it was the latest when I installed it a few months ago.
The install launched CWM, and I waited as the loading bar filled. Right at the end it gave an error message - in a panic I didn't take note of what it was, hit the onscreen buttons and went through a window telling me I might have lost SU permissions - which I told it to fix. The startup animation (with four dots, the new 4.4 animation I guess?) started... and continued for more than five minutes.
I was still panicking and instantly launched back into CWM, downloaded a (I think correct, checked it multiple times, as on does...) update zip from the web, and flashed it via adb sideload. This gave me an "Error 7" and a failed install. I tried again, same result. Then gave up and hit the restart button in the hope that one of the attempts had indeed worked...
I now have a Nexus 4 sitting on my desk playing a nice dotty animation, and it's been doing that for fifteen minutes as of now. I'm intending to leave it as such hoping that it will actually turn on and it's just having a very long boot.
So, the question. Anyone have any ideas how to save my Nexus?
I'd rather like to end up with the data on the device intact (stupidly did not back up before installing and can't get any files off it until an install works) and possibly with Android KitKat running on it, as was the original aim of tonight, but if neither are possible, I'd at least like to end up with a functioning phone... just with any stock rom.
Thanks in advance.
P.S. I'm not new to flashing ROMs manually - my last phone was a ZTE Blade which never ran any ROM well, so I must have flashed on that phone at least ten times, including via ADB.

Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD

totally-not-me said:
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
Click to expand...
Click to collapse
Your post saved me from a complete wipe and reinstall, so thank you for sharing your fix. I had a very similar issue but my Status 7 appeared to be because of my previous root and the new install not being able change the permissions on some /system files.
Now I just need to re-enable root via the NRT.

at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk

dethrat said:
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.

I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.

thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
Not blaming you xda has almost become useless in terms of finding real info in the past week. Bombardment of repeated posts about 4.4
Sent from my Nexus 4 using Tapatalk

Lokitez said:
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
Click to expand...
Click to collapse
Sideloading is only for flashable zip packages, not official factory images that required using fastboot. Use the guide links in my signature for instruction to flash factory image.
Or you can use sideload to flash flashable stock roms: http://forum.xda-developers.com/showthread.php?t=2527806
Unless your wife is really into flashing, I suggest just leaving it everything stock.

thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user

RickyBO89 said:
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
Click to expand...
Click to collapse
It will softbrick the device, or atleast fail. I don't even have to try CWM, but with TWRP, if I make any changes to the /system partition it failed. I suggest you just flash a stock 4.4 rom: http://forum.xda-developers.com/showthread.php?t=2010887

Unable to upgrade to 4.4.4

Hello,
I have been trying to upgrade my nexus 4 to 4.4.4 or 4.4.3. I currently run the rom below and keep getting system update notifications. its downloading the update over and over and failing and killed my data plan lastnight.
When I flash a rom for 443 right now it looks to install fine. With some roms i get halfway through the config, Just after giving your name if im right. You can scroll down on the page, the arrow at the bottom of the screen that you are to click to go to the next screen turns from a down arrow to a right arrow but it never lets you click it to continue. im stuck. ive tried unclicking everything. My only safety is having the backup from 4.4.2 and i restore it back.
Some roms let me go all the way through the config but when its at the home screen and is giving you the quick tutorial, you click on the screen to continue and you can hear it click so it knows you touched the screen but it never goes further. again cant get to my homescreen to do anything. have to restore.
Ive been in this loop for a while now and just looking for any suggestions to why i cant put 4.4.3 or 4.4.4 on? Wouldnt call myself a noob with all of this but im kinda feelin like it now.
Nexus 4, Android Version 4.4.2
Kernel Version 3.4.76-NexusExperience-CAF
Nexus 5 Experience Release 3.1 CAF Kernel
Build Jan 23 2014
Build No KOT49H
Any suggestions would be appreciated. Thx

blacktuxnc said:
Hello,
I have been trying to upgrade my nexus 4 to 4.4.4 or 4.4.3. I currently run the rom below and keep getting system update notifications. its downloading the update over and over and failing and killed my data plan lastnight.
When I flash a rom for 443 right now it looks to install fine. With some roms i get halfway through the config, Just after giving your name if im right. You can scroll down on the page, the arrow at the bottom of the screen that you are to click to go to the next screen turns from a down arrow to a right arrow but it never lets you click it to continue. im stuck. ive tried unclicking everything. My only safety is having the backup from 4.4.2 and i restore it back.
Some roms let me go all the way through the config but when its at the home screen and is giving you the quick tutorial, you click on the screen to continue and you can hear it click so it knows you touched the screen but it never goes further. again cant get to my homescreen to do anything. have to restore.
Ive been in this loop for a while now and just looking for any suggestions to why i cant put 4.4.3 or 4.4.4 on? Wouldnt call myself a noob with all of this but im kinda feelin like it now.
Nexus 4, Android Version 4.4.2
Kernel Version 3.4.76-NexusExperience-CAF
Nexus 5 Experience Release 3.1 CAF Kernel
Build Jan 23 2014
Build No KOT49H
Any suggestions would be appreciated. Thx
Click to expand...
Click to collapse
im assuming that you you wiped data? you are flashing over a CAF based rom and kernel(cm), and general android is not CAF based. how and what are you flashing as well, stock 443/444?

simms22 said:
im assuming that you you wiped data? you are flashing over a CAF based rom and kernel(cm), and general android is not CAF based. how and what are you flashing as well, stock 443/444?
Click to expand...
Click to collapse
Wipe data/cache, dalvik wipe
I installed - [ROM+KERNEL][CM11][KTU84M][CAF&AOSP] Nexus 5 Experience - CM11 Based [R8.2 - 12Jun
im sure im missing a step here. its user error. in the past i flashed a rom and that was all i needed to do. Im trying to do this upgrade without connecting to a pc, its been in the closet for a while. thought of using the raspberry pi if i needed to.

blacktuxnc said:
Wipe data/cache, dalvik wipe
I installed - [ROM+KERNEL][CM11][KTU84M][CAF&AOSP] Nexus 5 Experience - CM11 Based [R8.2 - 12Jun
im sure im missing a step here. its user error. in the past i flashed a rom and that was all i needed to do. Im trying to do this upgrade without connecting to a pc, its been in the closet for a while. thought of using the raspberry pi if i needed to.
Click to expand...
Click to collapse
ok..
did you make a backup in recovery? if you did, try this, as a wipe isnt required to upgrade. restore your backup, boot up, then go back and dirty flash that rom over what you have. dirty flash means dont wipe a single thing. btw, when you flash a rom, it automatically wipes dalvik and cache, so you never actually have to do that when rom flashing(and never have to wipe anything for kernel flashing).

when i did that i can see icons on the homescreen which is different but i still get stuck at the same spot. the screen is faded with a blue circle in the center that says welcome make your self at home. it has a create more screens for apps and folders wording at the bottom with an arrow, and a OK button.
I click OK and hear it click but nothing happens. i try to scroll for the arrow and hear actions but nothing happens. I can pull down the menu at the top and goto my email. but when i go back to home, that screen is still there. ive rebooted the device. tried clicking back to get past it. run task killer. it always comes back to this intro screen on the home screen

blacktuxnc said:
when i did that i can see icons on the homescreen which is different but i still get stuck at the same spot. the screen is faded with a blue circle in the center that says welcome make your self at home. it has a create more screens for apps and folders wording at the bottom with an arrow, and a OK button.
I click OK and hear it click but nothing happens. i try to scroll for the arrow and hear actions but nothing happens. I can pull down the menu at the top and goto my email. but when i go back to home, that screen is still there. ive rebooted the device. tried clicking back to get past it. run task killer. it always comes back to this intro screen on the home screen
Click to expand...
Click to collapse
weird. it happens after dirty flashing? the reason i said dirty flash is because those menus wont appear. it might be wise to flash the stock image, then reroot.

simms22 said:
weird. it happens after dirty flashing? the reason i said dirty flash is because those menus wont appear. it might be wise to flash the stock image, then reroot.
Click to expand...
Click to collapse
Can you point me in the right direction of the right stock image? i was downloading from googles developer site "Factory Images "occam" for Nexus 4" but i think that might be the wrong thing? wouldnt extract properly. several download attempts and methods

it was the right thing you were downloading probably, as it is a google site.
nexus factory images https://developers.google.com/android/nexus/images
how to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

Ive got adb working on my raspberry pi now and im able to send commands but im getting an error towards the end
error failed to load 'image-occam--ktu84p.zip' : Cannot allocate memory
what folder is it trying to copy it to? /system?
i couldnt delete aps from system/app
i removed some stuff from /android/data but that didnt help. same error.

Nexus 6p stuck on boot animation

Hey, I'm running the preview build 2 in my 6p. Yesterday all of a sudden my phone rebooted and got stuck on the boot animation screen. I'm running on a fully stock build with bootloader locked and OEM unlock option in developer settings disabled so I can't flash any image.
I tried a factory reset from stock recovery but it still gets stuck on the boot animation screen. Please tell me what should I do. Will ADB sideload work for me if I've got the latest image already installed on my phone?
Is it applicable for warranty? Everything's stock and the N preview was installed via OTA

With your bootloader locked and no way to unlock it you're pretty much screwed. This is why it's important to have your bootloader unlocked.
Sent from my Nexus 6P

aayushshah96 said:
Hey, I'm running the preview build 2 in my 6p. Yesterday all of a sudden my phone rebooted and got stuck on the boot animation screen. I'm running on a fully stock build with bootloader locked and OEM unlock option in developer settings disabled so I can't flash any image.
I tried a factory reset from stock recovery but it still gets stuck on the boot animation screen. Please tell me what should I do. Will ADB sideload work for me if I've got the latest image already installed on my phone?
Is it applicable for warranty? Everything's stock and the N preview was installed via OTA
Click to expand...
Click to collapse
Even a factory reset didn't help? Well, that's a shock. Since your device has not been modified in anyway, you would have blamed an app. But now that you already did a factory reset, and even then it wouldn't boot, my only guess goes to a hardware failure/issue. And yes, It's perfectly eligible to be covered under warranty.

Went to the Huawei service center earlier today and they did indeed categorize it as a hardware failure.
Nothing to do now but wait for 20(twenty!!?) working days for them do carry out the appropriate repairs.
Thank you for the responses
Sent from my Nexus 5 using XDA Free mobile app

aayushshah96 said:
Went to the Huawei service center earlier today and they did indeed categorize it as a hardware failure.
Nothing to do now but wait for 20(twenty!!?) working days for them do carry out the appropriate repairs.
Thank you for the responses
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Indeed. It took them 18 days to replace the volume keys. Huawei's service is terrible in India. I miss LG

i´m have the same issue
Hi guys, i´m having the same issue with the developer preview 3 (google called the first beta). My bootloader is locked and "oem unlock" is disable. I already sideload the OTA image with adb but i´m still stuck on boot animation after the installation. Do you know what should do next?
Thanks very much for your help.

jgracio said:
Hi guys, i´m having the same issue with the developer preview 3 (google called the first beta). My bootloader is locked and "oem unlock" is disable. I already sideload the OTA image with adb but i´m still stuck on boot animation after the installation. Do you know what should do next?
Thanks very much for your help.
Click to expand...
Click to collapse
Exact same issue :'(

Ok so let me see if this helps. I had the same issue. Let it sit and reboot itself a few times and it will boot right up. Or you can fast boot flash a factory image and that should work. Mine sat for about 15 min after installing the N3 beta and then it booted.
Sent from my Nexus 6P using XDA-Developers mobile app

What would probably fix the issue is if you guys sideload the ota downgrade back to mm from dev prev 3 once someone uploads it. Anyone have it handy yet for someone to try?

Or if impatient and get bootloop error:
booting into recovery
wiping cache
wiping data
wiping cache
reboot
Should boot into N fine then.

I had the same issue and did what major said. Here are the steps with a bit more detail.
Select recovery from the fastboot menu, it will reboot into recovery. Then hit the volume up button and power buttons at the same time to get the recovery menu (I had to do this several times). Then select clear cache, then factory reset, then do clear cache again and finally reboot. That fixed it for me but it wipes your phone. Hope that helps.

S2svetko said:
I had the same issue and did what major said. Here are the steps with a bit more detail.
Select recovery from the fastboot menu, it will reboot into recovery. Then hit the volume up button and power buttons at the same time to get the recovery menu (I had to do this several times). Then select clear cache, then factory reset, then do clear cache again and finally reboot. That fixed it for me but it wipes your phone. Hope that helps.
Click to expand...
Click to collapse
Hi,
Thanks for your comment. I follow your recomendation and i´m still stuck on boot animation (not the same as boot loop). How much time it took to install android n preview 3? I waited 50 minutes on boot animation but nothing happened.
best regards

jgracio said:
Hi,
Thanks for your comment. I follow your recomendation and i´m still stuck on boot animation (not the same as boot loop). How much time it took to install android n preview 3? I waited 50 minutes on boot animation but nothing happened.
best regards
Click to expand...
Click to collapse
I have the same issue. No matter what method I try(OTA, factory image, sideload, ...), it just stuck at boot animation and wiping cache or factory reset doesn't help at all. But on preview 2 it boot completely fine.
This is very frustrating ...

Having the exact same problem guys.. I've tried literally everything with no luck kept the boot animation going for 4 hours with nothing :/ keep me updated on your progress if any

Same problem here. Updated, bootloop, tried to sideload 4 times, tried wiping cache - data - cache... nothing worked.

gasparzim said:
Same problem here. Updated, bootloop, tried to sideload 4 times, tried wiping cache - data - cache... nothing worked.
Click to expand...
Click to collapse
Tried side loading again today and still nothing honestly don't know what to do at this point

Following. Exact same situation here. None of the suggested solutions work. It has been sitting in the boot animation for 4 hours now. Hoping for a miracle..

GoodNamesWereTaken1 said:
Following. Exact same situation here. None of the suggested solutions work. It has been sitting in the boot animation for 4 hours now. Hoping for a miracle..
Click to expand...
Click to collapse
If you just try to power off the phone by holding power button pressed so it just restart itself.. worked for me when i tried N yesterday
Skickat från min Nexus 6P via Tapatalk

aayushshah96 said:
Hey, I'm running the preview build 2 in my 6p. Yesterday all of a sudden my phone rebooted and got stuck on the boot animation screen. I'm running on a fully stock build with bootloader locked and OEM unlock option in developer settings disabled so I can't flash any image.
I tried a factory reset from stock recovery but it still gets stuck on the boot animation screen. Please tell me what should I do. Will ADB sideload work for me if I've got the latest image already installed on my phone?
Is it applicable for warranty? Everything's stock and the N preview was installed via OTA
Click to expand...
Click to collapse
checkout this thread your problem will be solved http://forum.xda-developers.com/nexus-6p/help/help-unbricking-nexus-6p-t3382895
---------- Post added at 03:39 AM ---------- Previous post was at 03:38 AM ----------
GoodNamesWereTaken1 said:
Following. Exact same situation here. None of the suggested solutions work. It has been sitting in the boot animation for 4 hours now. Hoping for a miracle..
Click to expand...
Click to collapse
the miracle is here my friend check my thread http://forum.xda-developers.com/nexus-6p/help/help-unbricking-nexus-6p-t3382895
---------- Post added at 03:39 AM ---------- Previous post was at 03:39 AM ----------
gasparzim said:
Same problem here. Updated, bootloop, tried to sideload 4 times, tried wiping cache - data - cache... nothing worked.
Click to expand...
Click to collapse
try this it will 100% http://forum.xda-developers.com/nexus-6p/help/help-unbricking-nexus-6p-t3382895

S2svetko said:
I had the same issue and did what major said. Here are the steps with a bit more detail.
Select recovery from the fastboot menu, it will reboot into recovery. Then hit the volume up button and power buttons at the same time to get the recovery menu (I had to do this several times). Then select clear cache, then factory reset, then do clear cache again and finally reboot. That fixed it for me but it wipes your phone. Hope that helps.
Click to expand...
Click to collapse
This didn't work for me. There was a hardware issue in my phone and I ultimately had to go to the Huawei service center and they had to replace the motherboard.