Database Users

Update to 4.2 fail on brand new Nexus 7

Hi,
I just received a brand new Nexus 7. I turned it on, logged into my account, and then the first thing I did was go to settings -> about -> check for system updates.
It started updating to 4.2
During the update, I got the android with red exclamation point.
Pressed power and volume up and it shows this. (See attached image)
I'm completely stumped. Its brand new and hasn't been rooted or modified.
I tried sideloading the update via adb but I get the same error.
Any ideas?
Any help would be greatly appreciated. Thanks

If you got it local, exchange it. You don't have a lot of time invested at this point to try to fix it.

I had the same exact problem but it was really easy to fix.
I downloaded the Nexus 7 toolkit and did the following:
1) Installed the Google Nexus 7 Drivers from the Nexus 7 Toolkit menu.
2) Unlocked my BootLoader from the Nexus 7 Toolkit.
3) Downloaded the factory stock rom for 4.1.2 in the Nexus 7 Toolkit.
4) Put my device in fastboot mode (power + volume down)
5) Selected the option to flash the device with the factory rom.
Once it was installed, I was able to apply the OTA update. Apparently many of these devices ship with this issue.

JayOui said:
I had the same exact problem but it was really easy to fix.
I downloaded the Nexus 7 toolkit and did the following:
1) Installed the Google Nexus 7 Drivers from the Nexus 7 Toolkit menu.
2) Unlocked my BootLoader from the Nexus 7 Toolkit.
3) Downloaded the factory stock rom for 4.1.2 in the Nexus 7 Toolkit.
4) Put my device in fastboot mode (power + volume down)
5) Selected the option to flash the device with the factory rom.
Once it was installed, I was able to apply the OTA update. Apparently many of these devices ship with this issue.
Click to expand...
Click to collapse
If you're going to go through the trouble of flashing a factory image to get the N7 up to date, just flash the latest. There's no need to waste time with the OTA at this point.
edit: the blurry image shows a patch assertion error on the kernel. This means that the installed kernel does not match what the OTA was expecting to find. This is typically indicative of the presence of a custom kernel.

comminus said:
If you're going to go through the trouble of flashing a factory image to get the N7 up to date, just flash the latest. There's no need to waste time with the OTA at this point.
edit: the blurry image shows a patch assertion error on the kernel. This means that the installed kernel does not match what the OTA was expecting to find. This is typically indicative of the presence of a custom kernel.
Click to expand...
Click to collapse
I agree it is indicative of a custom kernel but I had the same problem of a device pulled directly out of the box which was unfortunately shipped from Walmart since they were sold out on Google Play at the time. BTW, the box was sealed so unless Asus is shipping refurbished units as new, I don't see how this could have happened. If you google the error for the LNX device error, you will see this is more common that would be expected.
You are also correct that I could have flashed the 4.2.1 factory image, but at that point I wanted to make sure that I could actually get the OTA updates in the future. This showed I could as I was able to get the OTA update to 4.2 and then the subsequent update to 4.2.1.

You don't happen to have the original kernel or kernel information do you? I'd like to take a closer look at it to see what the deal is. Or do you happen top recall the build number that the device was shipped with?
Sent from my Nexus 4

This happened to me today, too.
I got a brand new 32GB wifi Nexus7 from the local electronics store.
Sealed box.
CBO serial
4.1.2 JZO54K preinstalled.
Made the OTA update.
At about half of the progress bar the red exlamation mark symbol came and the device rebooted on its own after waiting 1 minute.
And now 4.1.2 is still installed.
(everything stock and locked)
Can I fix it somehow else, without rooting etc?

Likewise, mines 4 days old and the update just won't install.

I tried to clear the "data" of Google Services Framework. Then did the OTA again but it failed again with the red triangle at about 1/3 of the loading bar.
Here is a workaround which didn't work for me (clearing data of Framework)
http://www.adilhindistan.com/2012/07/upgrading-nexus-s-to-jelly-bean-411.html

I tried it several times, even wiping /cache in stock recovery doesn't help.
I will continue to try the update. And either it will work all of a sudden or I really need to adb sideload the update manually on a fresh locked, unrooted device. Come on Google.

I gave up and flashed mine via ADB there's obviously something wrong with the OTA combined with the Nexus 7 32gb as it only seems to affect this model from looking at the stories.

I went to my local dealer. And after some evaluating and checking. They were able to to connect to their wifi. I then reproduced the failure in the shop. Then afterwards they called ASUS (The salesman let me talk to Asus directly, but they couldn't help, Google is responsible for software). And after this the salesman checked a demonstration model, which already had 4.21.
Then he asked the store manager I guess (at least he wore a suit as opposed to the others.)
And finally they exchanged my model to a new one. Now I have another CBO device but this time it updates flawlessly.
I'm happy.

JayOui said:
I agree it is indicative of a custom kernel but I had the same problem of a device pulled directly out of the box which was unfortunately shipped from Walmart since they were sold out on Google Play at the time. BTW, the box was sealed so unless Asus is shipping refurbished units as new, I don't see how this could have happened. If you google the error for the LNX device error, you will see this is more common that would be expected.
You are also correct that I could have flashed the 4.2.1 factory image, but at that point I wanted to make sure that I could actually get the OTA updates in the future. This showed I could as I was able to get the OTA update to 4.2 and then the subsequent update to 4.2.1.
Click to expand...
Click to collapse
I got my 32gb in December and have had the same problem. Google support said it was an asus issue and of course asus said it was a google issue. Both only had factory reset as a suggestion, which did not work. There seems to be hundreds of users with this issue because I have found tons and tons of people with the same problem, but no real answers. Rooting and flashing is of course a fix but not really a solution. I root my phones, but really do like the nexus as is and like you would want to be able to receive further ota updates without issue. I'm intrigued by your wrong kernal idea. I got mine new from a local gamestop.
I've attached a screenshot of my info. Can you tell me, please, is this the wrong kernal? If so and I follow your steps from the nexus toolkit, what will happen to everything that is on here? Will apps, data, personal file , and settings all be wiped? Are there any backup opttions? Not being rooted I can't use my titanium backup so will a copy to pc get everything?
Thanks so much!

@Sorraia3
That release - JRO03S - seems kind of old for a device which was purchased in December. Setting that aside though, there have been a few reports on here of "pure factory" JRO03S devices that would not properly accept the OTA update.
To know what the exact error condition is, you would either need to show a picture of the recovery screen with the error message, or if there is none, get a copy of the recovery log file (which might require root and therefore poses a chicken-vs-egg problem).
If you don't want to pursue a return/exchange/repair with Google/Asus, you could try identifying the exact problem - but to do that you would need to unlock the bootloader... which causes a full tablet wipe & in any event would be more difficult than just flashing a (new version of the) full factory ROM.
Look at the "return to stock with fastboot" thread for instructions on the latter.
You need to make backups of anything worth saving as the tablet gets completely wiped during this process. You might also want to look into the "Carbon" app for backing up market apps & their data on an unrooted device before you begin.
Also, the fact that you will be unlocking your bootloader does not mean that you need to flash custom ROMs or any other "rooting" activities - you can certainly just re-lock the bootloader after installing the factory ROM, and stay in a "pure stock" condition (with the newer factory ROM).
good luck

I know it has been awhile since I posted in this thread, but I got sidetracked. I'm now going to be taking care of this and was wondering if I can jump right to the newest build or should I graduate up them? If the latter, can someone give me the proper build order? If the former, what is the most current stable build I should use?
Also, I no longer seem to be able to find the thread mentioned "return to stock with fastboot" would you have a link for it?
Wait I think I just found it. Is this it?
http://forum.xda-developers.com/showthread.php?t=1907796
So the recommendation is to go through adb rather then use the toolkit?
Thanks much!
Sent from my Nexus 7 using xda premium

[Q] Having trouble updating to Lollipop

I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.

SimonP2 said:
I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.
Click to expand...
Click to collapse
I would flash the factory image using fastboot to 5.0.1. You'll have to unlock the device again. I'm not a fan of tool kits
Sent from my Nexus 9 using XDA Free mobile app

SimonP2 said:
I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.
Click to expand...
Click to collapse
In the toolkit options enable "Force Flash Mode" and try again; this will fastboot flash the img files individually and overcome the issues with Google's new Lollipop factory packs, where the fastboot update cmd, is not working properly (as written in their own incldued flash-all.bat).
In the future.. rather than PM'ing me and making a thread.. just post in the NRT threads.
{{ WugFresh }}

It took a lot of fiddling about and several boot loops but eventually I managed to install 5.0 (using NRT) and it updated to 5.0.1 (which is what I wanted to see to be sure it was working alright before I sell it) so all is well at last. Thanks for the suggestions.

Essential PH-1 downgrade

Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.

stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service

stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Did you unlock your critical partitions along with the bootloader?

arjunv said:
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
Click to expand...
Click to collapse
Do you think you could link that post for me? I can't seem to find it.
I also don't see any uicc option on my debice. (Not sure or that matters though)

If it's Sprint you need to wait 50 days before you can unlock it. CDMA phones are a pain in the ass to unlock, always buy International if possible!
This thread has some information that might be useful:
https://forum.xda-developers.com/essential-phone/help/unlock-sprint-version-t3720727
Sent from my PH-1 using XDA Labs

SuperBrolySSJ said:
Did you unlock your critical partitions along with the bootloader?
Click to expand...
Click to collapse
This is required for the touch screen firmware to be flashed and OP needs to see this.

Unlock and remove Android for Work (AFW) Enterprise MDM

I have a Pixel 4 with Android 10 on it. It also has Android for Work (Enterprise), i.e., it is managed by work admin who can remote reset the device and also control what gets installed or not. It has MobileIron MDM agent installed on it.
How can I wipe all of this Android for Work and remove the MobileIron completely? I have no personal data on it and can do factory reset and the phone is carrier unlocked as well. The OEM unlock in Developer Options is greyed out.

Most likely, the phone was bought from Android Enterprise, which may also mean the app is built into the firmware - loaded as specified by whatever organization ordered the device from Google. But there's a couple things we can check:
Go to Accounts under Settings, make sure there is no work profile there.
Go to Security > Device Admin apps, see if you can remove the app there.
Failing those, try a factory reset. If the MobileIron app survives factory reset, it's built into the firmware.
Unfortunately there isn't much that can be done to get rid of it with a locked bootloader. You could try sideloading an OTA update but that may fail because the firmware won't match. You can also try the Pixel Repair Tool although I suspect that may not work for the same reason.
Let us know how it goes!

The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.

agaurav said:
The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.
Click to expand...
Click to collapse
What do you mean it doesn't go to bootloader mode?
Are you able to enable Developer Options and USB Debugging?

My bad. I tried Pixel Repair tool. It went thru successfully but did not remove the Android for Work so I guess I am stuck with a paper weight. Nothing can be done effectively. That's fine. I will wait for black friday deals and buy a new phone. Thanks.

agaurav said:
The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.
Click to expand...
Click to collapse
If the device is enrolled in Android Zero Touch, there is nothing you can do unless the IMEI is removed from Zero-Touch.

Help Needed - Pixel 4 - No WiFi+Data after update

Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.

Did u solve this?