I've been having issues with my Nexus 9 (WiFi version) since the April security OTA. I've never messed around with flashing images or even side loading for that matter.
On reboot, I started to see an error stating "Your device is corrupt. It can’t be trusted and may not work properly."
On bootup I also get: There's an internal problem with your device contact you manufacturer for details.
A bit of searching around (and the timing relative to April update) made this appear to be a software issue. I mostly ignored it for a week since I was in the middle of reading an ebook on it.
A few days later, I started getting pretty regular errors for Google Play services. I figured it was time to try to wipe it and start from a fresh image.
However on reboot, I still get the same error at bootup and when it takes me to the activate screen I get a message saying "There's an internal problem with your device. Contact your manufacturer for details".
After hitting OK to that, I get a few pop ups about Bluetooth share services failing.
When I try to proceed to setup the tablet with my google account, it hangs on the Checking Connection screen. I left it that way for 30 minutes and nothing.
A quick google search later, and I had rebooted into recovery mode and tried clearing the cache. No luck.
Prior to all of this, my device was successfully connected to my wi-fi. Nothing has changed with the wifi, only the device. I found a suggestion of using tethering on my phone, that still hangs.
While I was recovery mode I noticed it was on what I presume was the March update's build: MMB29V not April.
So I tried to use adb sideload with MMB29V (6.0.1) To MOB30D (6.0.1). It got to the point that it said it was at 47% on my PC, and the tablet was "patching after verification". It sat there for about 90 minutes with no change that I could tell, so I rebooted it.
At this point I'm not sure if I screwed it up further. It appears to still be on MMB29V.
I wanted to try to do a brand new factory image of MOB30D, but I can't:
1) unlock the bootloader without:
2) enabling developer mode, which I can't do without:
3) logging into my tablet with my google account. which I can't do because:
4) I can't get past wifi Connection checking.
So I'm stuck at this point, and I have no idea how to proceed. I assume for security reasons there is no way unlock the bootloader without first enabling it through developer mode?
Am I being too impatient? Is there something else I can try?
Any help would be appreciated.
Thanks.
On reboot, I started to see an error stating "Your device is corrupt. It can’t be trusted and may not work properly."
On bootup I also get: There's an internal problem with your device contact you manufacturer for details.
A bit of searching around (and the timing relative to April update) made this appear to be a software issue. I mostly ignored it for a week since I was in the middle of reading an ebook on it.
A few days later, I started getting pretty regular errors for Google Play services. I figured it was time to try to wipe it and start from a fresh image.
However on reboot, I still get the same error at bootup and when it takes me to the activate screen I get a message saying "There's an internal problem with your device. Contact your manufacturer for details".
After hitting OK to that, I get a few pop ups about Bluetooth share services failing.
When I try to proceed to setup the tablet with my google account, it hangs on the Checking Connection screen. I left it that way for 30 minutes and nothing.
A quick google search later, and I had rebooted into recovery mode and tried clearing the cache. No luck.
Prior to all of this, my device was successfully connected to my wi-fi. Nothing has changed with the wifi, only the device. I found a suggestion of using tethering on my phone, that still hangs.
While I was recovery mode I noticed it was on what I presume was the March update's build: MMB29V not April.
So I tried to use adb sideload with MMB29V (6.0.1) To MOB30D (6.0.1). It got to the point that it said it was at 47% on my PC, and the tablet was "patching after verification". It sat there for about 90 minutes with no change that I could tell, so I rebooted it.
At this point I'm not sure if I screwed it up further. It appears to still be on MMB29V.
I wanted to try to do a brand new factory image of MOB30D, but I can't:
1) unlock the bootloader without:
2) enabling developer mode, which I can't do without:
3) logging into my tablet with my google account. which I can't do because:
4) I can't get past wifi Connection checking.
So I'm stuck at this point, and I have no idea how to proceed. I assume for security reasons there is no way unlock the bootloader without first enabling it through developer mode?
Am I being too impatient? Is there something else I can try?
Any help would be appreciated.
Thanks.
Facebook
Twitter
Instagram