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
Hello everyone :laugh:
I'm new here in this forum and as on android user as well so go soft on me
I have a problem regardless the root and unroot device, my nexus 7 in rooted (I dunno if it is rooted by manufacture or not)
I installed some online games like Iruna online and avabel problem is I always got the same error screen "Authentication Failed"
I heard it got something to do with rooted devices, so I tried some programs that un-root the device for certain apps but it failed too.
any suggestion or this error is duo to something else
Ps:Google play is restricted in my country so I'm using hotspot
Do you want to hide the root or unroot the device.
No Nexus 7's are sent rooted from the manufacturer if it is rooted then this has been done by a user. Wugfresh nexus toolkit has an option to unroot but this involves flashing an unrooted stock ROM and will wipe the device. I'm not aware of any other way to unroot the tablet. Some apps say that they can hide the su binary from other apps. For more info on what "root access" actually is see XDA university for a pretty concise explanation. Try hide my root by amphoras if you can't get that on hotspot PM me and I will send you the .apk file.
Sent from one of my 47 iPads running android C3P0
I tried multiple apps that hide root but all failed, I will try the one you mention,
and I'm asking about the error too "Authentication failed" is it because of root or else ?
Edit: I just tried the app and the same error
SheepRaider said:
Hello everyone :laugh:
I'm new here in this forum and as on android user as well so go soft on me
I have a problem regardless the root and unroot device, my nexus 7 in rooted (I dunno if it is rooted by manufacture or not)
I installed some online games like Iruna online and avabel problem is I always got the same error screen "Authentication Failed"
I heard it got something to do with rooted devices, so I tried some programs that un-root the device for certain apps but it failed too.
any suggestion or this error is duo to something else
Ps:Google play is restricted in my country so I'm using hotspot
Click to expand...
Click to collapse
Hi, SheepRaider...
If your Nexus 7 is rooted with Chainfire, then unrooting it should be relatively straightforward...
------------------------------------------------------------
** Go into the App Drawer and locate the SuperSU app. By default, the icon should be a YELLOW triangle with a RED hash (#) overlayed on top of it. However, this may have been changed by whoever originally rooted the device. See the first thumbnail at the bottom of this post for the alternative icons. If it's been made invisible (hidden from launcher), then things become a little more technically challenging. See this post for more details on this.
** Once you have located the SuperSU app, run it and tap on the SETTINGS tab.
** Scroll down to the option, Full unroot - Cleanup for permanent unroot, tap on this and follow the on screen instructions.
** Reboot your Nexus 7... you should now be unrooted.
------------------------------------------------------------
Take a look at my attached thumbnail images for the sort of things you should expect to see.
Hope this helps... and good luck.
Rgrds,
Ged.
I'm locked out of my S5 and the only way to unlock it seems to be by alternate password, which I don't remember.
Google Android Manager will no longer allow you to reset the lock screen password, there are no other options listed, and it seems that my phone will undergo a factory reset about 10 failed attempts at guessing the password. I have one guess left.
Is there any way to save the data on my phone before the factory reset, or a way to bypass it completely?
The phone is not rooted at all, and I'm unsure as to the specific software version, as I can't look to see.
I think you can boot into recovery and maybe backup your files
Sent from my SM-G900V using XDA Free mobile app
How so?
I'm in recovery mode now.. I don't have any CWM or anything like that, and I don't see any options.
Maybe I should try to apply the recent update and see if that resets everything?
Updated to the latest version.
Doesn't look like that helped anything.
Still locked, and I don't want to try another password incase I'm still on my last try.
I can set up the ADB while in recovery mode... Can I backup via the ADB in recovery mode?
When I use adb devices, my device comes up as "sideload" rather than device? Why?
i had my at&t s7e rooted for a while and i decided to unroot it, after i did so it still shows the custom/ unlocked symbol when booting up. can i make this go away? and if so how can i do so?
Only way to go is to Odin a stock rom again and perform factory reset.
Hi!
I have issue with app on my S7 Edge that demands me to unroot. I rooted my phone 5 years ago or more and I don't remember a thing about it. I did this to permanently remove bloatware. Only way I know to unroot is to flash stock-rom again but I don't want to loose my hard effort on debloating + data and so on. Is there any tricks for that? Like hide/remove su binary? I really don't remember where to start. Also with factory reset or something I cant remember I lost root access partially - that is apps can still tell that phone is rooted (root checker tells that root access is available but then also orange warning that root access is not properly installed on this device). But they can't request root privilege for some reason. But I still have this custom recovery rom installed where I have basically root access to phone - do you think I could use this to somehow hide temporarily root from my app that is complaining about it and then later restore root to the full - that is to make apps able to request root access again? I would like to keep my apps/data and I remember them getting lost in process of rooting due to some samsung encryption crap - not sure how to check data/app loss would be case now since I did it so long time ago. Could anyone help me out?
For documentation purposes. So in my case I had lost root with factory reset. I had to boot into TWRP and re-flash super su. Difference from official tutorial: https://forum.xda-developers.com/t/...ial-twrp-for-galaxy-s7-edge-hero2lte.3334084/ was that in step 9 my phone did not complain about dm-verity,. I did not have to disable encryption and I did not loose my data. Someone may correct me but it was because I had already rooted in past and the most likely cause for "loosing" root was doing factory reset. PS I have european model so I am not sure how much it makes this tutorial different.
Now what is left to do is come up with ideas how to hide root from 1 specific app in Android 7.