Database Users

Red exclamation when trying to update Nexus 7 to 4.2...

I just got my new Nexus 7, and the first thing I tried to do was update to 4.2. It arrived with 4.1.2. When I pressed update, it booted into recovery, and started the loading android animation, however at about half way a red exclamation point went on the screen. This stayed on until I just rebooted the device, and it was on 4.1.2. After this, I checked for the update, and it says "Your device is up to date." I cleared the services, and it downloaded the update, and the same thing happened!
I don't know much about manually installing from Google's factory image, and I honestly don't trust myself trying to manually update it...I would rather just use the OTA.
Why does this happen? Are there any ways to fix this?

How are you doing this, using adb sideload with the ota zip or ?
- Sent from my US Cellular SGS3
---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------
There's plenty of ota zip files that are the official ota which will allow you to upgrade.
Are you 100% stock or ?
- Sent from my US Cellular SGS3

yanksrock1000 said:
I just got my new Nexus 7, and the first thing I tried to do was update to 4.2. It arrived with 4.1.2. When I pressed update, it booted into recovery, and started the loading android animation, however at about half way a red exclamation point went on the screen. This stayed on until I just rebooted the device, and it was on 4.1.2. After this, I checked for the update, and it says "Your device is up to date." I cleared the services, and it downloaded the update, and the same thing happened!
I don't know much about manually installing from Google's factory image, and I honestly don't trust myself trying to manually update it...I would rather just use the OTA.
Why does this happen? Are there any ways to fix this?
Click to expand...
Click to collapse
Is the device rooted and have you modified any system files? This generally happens when the patch update system attempts to patch a file for the update but it's been modified or missing.
Cheers,
Kermee

Haven't modified a thing, its completely stock.
Sent from my Nexus 7 using xda app-developers app

Try doing a factory reset
Sent from my SGH-T959V using xda app-developers app

I'm running into the same exact situation, except I have a 16GB. Whenever I attempt to update to 4.2 I get the robot lying on its back with a red exclamation point in its belly.

update fail...then cant reboot...

i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app

minjiet said:
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb

jalize said:
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
Click to expand...
Click to collapse
Ya, i'm rooted, now the n10 cant boot at all....what can i do?
anyone can show me step by step guide?

Or flash the Factory image with a bit editing. This should do: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app

I got that as well on my N10. Stock, stock recovery rooted. Booting into recovery didn't help. The next morning it was the same thing, but after a while it shut itself off and when I was ready to flash a stock img, had the USB cable plugged into the laptop, I look at the N10 and it's booting just fine, then starts applying the update.
Not helpful I know, but just wanted to let you know it fixed itself, I did nothing. Good luck.

Same problem on stock rooted. Impossible to boot and to switch off the device. I've wait the nexus shut down by himself and after the update have been automaticaly installed on the boot. I'm always rooted. Strange.

Use http://www.afterdawn.com/software/s...l_devices/nexus_root_toolkit.cfm#all_versions app is the best to fix and very easy
Sent from my Nexus 10 using XDA Premium 4 mobile app
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
A fixed all my problems, i am on stock with the same problem on jelly bean 4.3, now rooted and again with a custom recovery.
Sent from my Nexus 10 using XDA Premium 4 mobile app

thanks for the help...my n10 back to normal automatically after i plug in charger...weird
Sent from my HTC6435LVW using XDA Premium 4 mobile app

Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.

DEinspanjer said:
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
Click to expand...
Click to collapse
When you cleared cache you lost the update package I believe, so it didn't update, when I received my OTA I had TWRP installed and it went through nicely. Maybe you should try it and then installing Stock Recovery again.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505

I have a Nexus 10. I just took and installed the OTA that arriced 08/27/2013. I am not rooted or unlocked. It is only a wifi (not a carrier specific).
I have been sick since i took the first Ota several weeks ago. I was constantly having to reboot because it would drop the connection. Firefox was useless. And above all, I was unable to get Grassland Live wallpaper and Wind Turbine 3D to work.
It all works now!
Sent from my Nexus 10 using xda app-developers app

I just read in another thread that the issue as described is caused by apply the OTA when rooted. Just unroot then apply the OTA update and reboot. Assuming you are using SuperSU., it has an unroot option in the settings panel.
Good luck.

New Software downloading... Stock

So LG decided to update software. Is downloading now, i'm curious what version will be.
I think i will lose root and custom recovery after installing.

crissx said:
So LG decided to update software. Is downloading now, i'm curious what version will be.
I think i will lose root and custom recovery after installing.
Click to expand...
Click to collapse
Probably really minor. I hope for a QRemote update
Sent from my iPhone using Tapatalk

crissx said:
So LG decided to update software. Is downloading now, i'm curious what version will be.
I think i will lose root and custom recovery after installing.
Click to expand...
Click to collapse
I hope its a patch to fix the annoying blue line.

EdenGottlieb said:
Probably really minor. I hope for a QRemote update
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It's 117.38 MB, but it's slow..slow dwl.

System ROM is 2GB so its unlikely to be anything significant
Sent from my LG-V500 using xda app-developers app

It will not install if you have custom recovery. Will reboot only in recovery. I had to restore to my latest back-up (edit: and same thing ) I think i will revert to stock.
This update : Apps enhancement.

Which base? Still jelly bean 4.2.2?

Can someone make a flashbacks zip we can update the new changes via twrp. Or cwm?
Sent from my LG-V500 using Tapatalk

No new update for mine as of yet.
Sent from my SCH-I535 using Tapatalk

err:0x13E
I downloaded the update files and rebooted the tablet but at 3% it gives me this error err:0x13E . After that the tablet was restarted and booted on android and shows me that the tablet is suspected of rooting and cannot be updated.I have android 4.2.2 stock firmware with root access What can i do?

Installed the upgrade but have no idea what the changes are.

Update
BogdanIT95 said:
I downloaded the update files and rebooted the tablet but at 3% it gives me this error err:0x13E . After that the tablet was restarted and booted on android and shows me that the tablet is suspected of rooting and cannot be updated.I have android 4.2.2 stock firmware with root access What can i do?
Click to expand...
Click to collapse
shadowgolf said:
Installed the upgrade but have no idea what the changes are.
Click to expand...
Click to collapse
Just downloaded the latest update via Wi-Fi no problems about 10 -15 min
There two LG updates /
One of them is a New Application called drive which seem a bit like a cloud system or organiser
The other is the weather widget now shows temp in Red
Sorry "No Kit Kat " :crying:

brian566 said:
There two LG updates /
One of them is a New Application called drive which seem a bit like a cloud system or organiser The other must be a App update
:crying:
Click to expand...
Click to collapse
Thanks for letting us know.
That sounds incredibly boring.
*yawn*

brian566 said:
One of them is a New Application called drive which seem a bit like a cloud system or organiser
:crying:
Click to expand...
Click to collapse
Is "Drive" its exact and complete name? I don't seem to have got that, it might be market-specific... Are you sure you are not mixing it up with Drive from Google?

Drive
xdapao3 said:
Is "Drive" its exact and complete name? I don't seem to have got that, it might be market-specific... Are you sure you are not mixing it up with Drive from Google?
Click to expand...
Click to collapse
Yes it is google drive but i have not downloaded it was not there before the update

Got this "V50010B" update via OTA yesterday (in Italy on an Italian G Pad).
Things I have noticed so far are they have corrected a couple of bugs: tap sounds randomly muted and then randomly working again (I have them on) and a bug where you have the "Auto-show the Remote in the lockscreen when on some AP" option ON and the time widget would "multiply", over time.
P.S. I didn't lose root and I forgot to disable Xposed before updating but it hasn't affected anything. Everything works perfectly well after the update.

I have noticed two changes after the update.
1. Screen seems to be brighter on minimum brightness. Those who was crying for the 7 led's leek, can be happy.
2. If you lock screen rotation, it will be locked on the current position, instead of going back to portrait mode. Now you can lie on your side, and use the tab on landscape:good: !

brian566 said:
Yes it is google drive but i have not downloaded it was not there before the update
Click to expand...
Click to collapse
Oh.. OK. They must have made it a "system app" now whereas it wasn't before :good:
---------- Post added at 04:07 PM ---------- Previous post was at 04:00 PM ----------
Furmint said:
2. If you lock screen rotation, it will be locked on the current position, instead of going back to portrait mode. Now you can lie on your side, and use the tab on landscape:good: !
Click to expand...
Click to collapse
Good to know! The few times I lock the screen (of both my smartphone and my tablet) I usually need it in portrait but I have always found VERY STUPID this behaviour some makers/devices have of locking the orientation always and only in portrait!!
My Note II unfortunately has it, I didn't notice the G Pad had it too (I have probably never tried to lock it in landscape, so far) but I am very glad it hasn't anymore! :good:

I still haven't got the update as of noon eastern time today. Do they push it in waves or something?
Sent from my SCH-I535 using Tapatalk

For anyone tryed to flash the update with TWRP recovery and stuck into "recovery bootloop" just do this.
1)Boot into recovery
2)Go to "Advanced" and then "Terminal Command" and choose root folder.
3)Type this and then hit enter. TRY TO TYPE IT RIGHT OR YOU WILL BRICK YOUR DEVICE
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PS:Without this command even restore will not work
Ps2:Credits to the thecubed

After March Update - No notifications or pull down menu

After today's update I can no longer Access the pull down menu. All I see is a message saying "No Notifications". The pull down menu isn't there and the home button and the recent button both don't work. Has anybody any idea how this can be remedied?

Have you tried the following:
- reboot the 6P
- clear the cached data in Storage and USB
- boot into recovery and clear the cache partition

Sorry, no change

Hmm and I was just going to ask if the March update was safe to load.
Sent from my Nexus 6P using Tapatalk

How did you install the update? Are you rooted and/or any mods?

Heisenberg said:
How did you install the update? Are you rooted and/or any mods?
Click to expand...
Click to collapse
I'm having the same issue. Was on MMB29Q, stock, rooted (latest 2.68 systemless), no mods. Used Fastboot to flash the MHC19I factory images. I've tried re-downloading and re-flashing the factory image with no luck. Backing up user data now to do a factory reset.

try this.
http://forum.xda-developers.com/nexus-4/general/fix-errors-dirty-flashing-t2940507

Will test and report back. Thank you.

My guess is that data needs to be wiped prior to flashing the images, dirty flash is causing problems.

Did you install it via OTA?
Sent from my Nexus 6P using Tapatalk

Momotani-Hitoshi said:
try this.
http://forum.xda-developers.com/nexus-4/general/fix-errors-dirty-flashing-t2940507
Click to expand...
Click to collapse
This worked for me, whew!
I'm not exactly sure how this occurred. I unrooted my phone with the Nexus Root Toolkit in order to catch the OTA update. After the update was installed, I had These Problems but all is good now. Thank you.

Mister-B said:
This worked for me, whew!
I'm not exactly sure how this occurred. I unrooted my phone with the Nexus Root Toolkit in order to catch the OTA update. After the update was installed, I had These Problems but all is good now. Thank you.
Click to expand...
Click to collapse
As I said, most likely due to not wiping properly.

Momotani-Hitoshi said:
try this.
http://forum.xda-developers.com/nexus-4/general/fix-errors-dirty-flashing-t2940507
Click to expand...
Click to collapse
Thank you so much for replying in this thread. Your solution also helped me.

Is any one else still waiting for the march update ota?

Mister-B said:
After today's update I can no longer Access the pull down menu. All I see is a message saying "No Notifications". The pull down menu isn't there and the home button and the recent button both don't work. Has anybody any idea how this can be remedied?
Click to expand...
Click to collapse
Installed the update OTA with no such issues.
Hope you find a solution.

I'm still waiting for the March ota. I'm not rooted and don't want to be at this point. I use mero pcs but I don't think carrier has anything to.do with the update.

mojorisin7178 said:
I'm still waiting for the March ota. I'm not rooted and don't want to be at this point. I use mero pcs but I don't think carrier has anything to.do with the update.
Click to expand...
Click to collapse
I'd recommend you sideload it from recovery then. It would be the same as getting it from the system update app.
Sent from my Nexus 6P using Tapatalk

My notification pull down isn't working on home screen. However it works on lock screen.
I've recently got my Nexus 6P, and after setting up for first time, it received Jan update. Yesterday, I did the Feb and March OTA via adb sideload. I'm completely stock. I've reseted my device twice now, once I did restore, and 2nd time I set up device as new device. Yet my notification pull down won't work on home screen.
I haven't tried flashing factory image yet.
Any suggestions?
EDIT: I've now tried flashing 2 different builds of factory image (MMB29P and MHC19I). I still have the issue.

mumbhai55 said:
My notification pull down isn't working on home screen. However it works on lock screen.
I've recently got my Nexus 6P, and after setting up for first time, it received Jan update. Yesterday, I did the Feb and March OTA via adb sideload. I'm completely stock. I've reseted my device twice now, once I did restore, and 2nd time I set up device as new device. Yet my notification pull down won't work on home screen.
I haven't tried flashing factory image yet.
Any suggestions?
EDIT: I've now tried flashing 2 different builds of factory image (MMB29P and MHC19I). I still have the issue.
Click to expand...
Click to collapse
Are you wiping userdata when flashing? As I pointed out earlier in this thread it's most likely caused to due a mismatch in data.

Heisenberg said:
Are you wiping userdata when flashing? As I pointed out earlier in this thread it's most likely caused to due a mismatch in data.
Click to expand...
Click to collapse
yes I was wiping userdata when flashing.
I turn on debugging mode and enabled show touch, that top part (only size of status bar) wouldn't show any touch, so seemed like hardware issue.
Phone is already its way for RMA now.

Need help in unbricking my nexus 6p

i was on android m latest build and then i decided to try the new android n dp3 beta so i enrolled my 6p and updated through the ota update but after the update my 6p never started it stucks at the boot animation forever i tried wiping cache and also did a full wipe but its still the same. the oem unlock option is also disabled so i cannot flash factory images. i came to know that when we want to roll back to android m from the current beta we just have to unenroll our device from the beta and google sends an ota update of the current marshmallow build to roll back to it. now want i want to try is sideload that update package through adb an see if i can go back to android marshmallow. Please any of you who are trying out the latest android n beta provide me the zip file for the ota which google sends when we unenroll our device?

actually there is a simple step. anybody using the nexus 6p and running the latest android n beta just unenroll your device and when you get a notification for the ota update just enable usb debugging adn connect to computer and type command adb logcat and in the logcat file there will be a url for the ota just give me that url i will download it and try

Try to adb side load dp3. I think it can be installed on stock recovery and a fresh install might help. Wipe cache and factory reset afterwards and hope for the best. This won't make your problem any worse but has a chance at helping.

I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try

murphyjasonc said:
Try to adb side load dp3. I think it can be installed on stock recovery and a fresh install might help. Wipe cache and factory reset afterwards and hope for the best. This won't make your problem any worse but has a chance at helping.
Click to expand...
Click to collapse
spookytay said:
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
Click to expand...
Click to collapse
no its not happening. if anyone of you are using nexus 6p and are on the android n beta then please can you follow what i have posted in the first comment?

Ame123 said:
no its not happening. if anyone of you are using nexus 6p and are on the android n beta then please can you follow what i have posted in the first comment?
Click to expand...
Click to collapse
I second this. Would be very helpful if someone could post the official roll-back marshmallow .zip for the 6p.

https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM

matt1515 said:
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM
Click to expand...
Click to collapse
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Update: Sideload completed, first boot froze and phone restarted then second boot has booted to welcome screen!! Dude I cannot thank you enough I tried literally everything and nothing worked and I lost hope until I saw this!

AlfexOmega said:
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Click to expand...
Click to collapse
Correct.

AlfexOmega said:
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Update: Sideload completed, first boot froze and phone restarted then second boot has booted to welcome screen!! Dude I cannot thank you enough I tried literally everything and nothing worked and I lost hope until I saw this!
Click to expand...
Click to collapse
Good stuff! Glad to help I thought this would work!

matt1515 said:
Good stuff! Glad to help I thought this would work!
Click to expand...
Click to collapse
So this was the OTA that you get when you unenroll your Nexus from the Beta Programme?

matt1515 said:
Good stuff! Glad to help I thought this would work!
Click to expand...
Click to collapse
Yep--can confirm this worked for me as well. Thank you so much for posting the .zip, matt1515.

AlfexOmega said:
So this was the OTA that you get when you unenroll your Nexus from the Beta Programme?
Click to expand...
Click to collapse
Yes sir I unenrolled from the beta I got the link from adb logcat
---------- Post added at 01:22 PM ---------- Previous post was at 12:48 PM ----------
Ame123 said:
actually there is a simple step. anybody using the nexus 6p and running the latest android n beta just unenroll your device and when you get a notification for the ota update just enable usb debugging adn connect to computer and type command adb logcat and in the logcat file there will be a url for the ota just give me that url i will download it and try
Click to expand...
Click to collapse
https://android.googleapis.com/packa...cd4f52b800.zip

matt1515 said:
Yes sir I unenrolled from the beta I got the link from adb logcat
---------- Post added at 01:22 PM ---------- Previous post was at 12:48 PM ----------
https://android.googleapis.com/packa...cd4f52b800.zip
Click to expand...
Click to collapse
Nice! Thanks so much again

matt1515 said:
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM
Click to expand...
Click to collapse
it worked. thank you very much for helping:good::good::good::good:

Same thing happened to me, luckily it decided itself to boot fully after an hour. However I did notice that USB debugging was not enabled after all this mess. Does that mean if it didn't resolve then I would have had a nice brick without the option of side loading from a PC? Also does the unlock bootloader in dev options need to be checked off for any reason other than flashing custom roms? Can I still install official images and still have the bootloader locked?
Now I'm just looking for ways to be prepared in the future in case it happens again, thanks

kick069 said:
Same thing happened to me, luckily it decided itself to boot fully after an hour. However I did notice that USB debugging was not enabled after all this mess. Does that mean if it didn't resolve then I would have had a nice brick without the option of side loading from a PC? Also does the unlock bootloader in dev options need to be checked off for any reason other than flashing custom roms? Can I still install official images and still have the bootloader locked?
Now I'm just looking for ways to be prepared in the future in case it happens again, thanks
Click to expand...
Click to collapse
Leave USB debugging and OEM Unlock enabled. This will help you so much more in the event of any issues during updates.
If OEM Unlock is turned off then you cannot flash factory images. You CAN leave this off and still ADB Sideload OTAs. However, if the ADB Sideload update is corrupt or flashes and you are stuck in a bootloop, there is very little that can be done to resolve it.
Sent from my Nexus 5X using Tapatalk

Has anyone here who flashed back to MM tried to do the OTA N update again? How did it go?

freezerbite said:
Has anyone here who flashed back to MM tried to do the OTA N update again? How did it go?
Click to expand...
Click to collapse
Yes. I tried but again got stucked in bootloop. So i am not touching any beta

It's so weird that some people get stuck with this boot loop issue and some just don't. I know things can happen, but I feel there's a enough users in the same boat that there's has to be a common denominator.
Sent from my Nexus 6P using Tapatalk