5.0.2 upgrade ERROR -- PURE STOCK - Nexus 9 Q&A, Help & Troubleshooting

I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??

you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)

Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse

From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens

Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.

Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.

Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse

the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.

On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse

the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...

Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse

FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.

I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous

When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30

@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.

cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?

kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153

cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you

kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome

Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse

Related

4 OTA 5.0 attempts - 4 Failed installations! Help 😯

So frustrated!
#1 was regular attempt w/device as is
#2 w/factory reset
#3 unrooted
#4 rooted and changed some system files (that I remember that had been modified....a camera mod, volume mod etc)..i thought Factory reset would have done that.
All 4 Failed
At a loss at this point.
Any help appreciated!
I have had a problem with FOTA twice as well. I also unrooted, and did a factory reset. Changed BBS back to a user app before unroot. Both times I got the FOTA it begins to install, gets to maybe 10% (guessing here) and then the Andy with the red triangle pops up with "ERROR!" beneath it. After that I have to boot into recovery and manually reboot.
Hopefully this doesn't hijack your thread, but when I tried to install the update with ADB, it tries to load the update, then ADB cannot see the device anymore.
rockky said:
So frustrated!
#1 was regular attempt w/device as is
#2 w/factory reset
#3 unrooted
#4 rooted and changed some system files (that I remember that had been modified....a camera mod, volume mod etc)..i thought Factory reset would have done that.
All 4 Failed
At a loss at this point.
Any help appreciated!
Click to expand...
Click to collapse
I also am having the same issue. I tried once with root, once without, reset device and even tried removing my sd card. And it still fails. I have never done anything but root my device so im also very confused.
str33tprintz said:
I also am having the same issue. I tried once with root, once without, reset device and even tried removing my sd card. And it still fails. I have never done anything but root my device so im also very confused.
Click to expand...
Click to collapse
The only way may be to revert all the way back to 4.4.2 and start a fresh (watch out for all your data - back it up as this will wipe it probably)
blueether said:
The only way may be to revert all the way back to 4.4.2 and start a fresh (watch out for all your data - back it up as this will wipe it probably)
Click to expand...
Click to collapse
I started to install 4.4.2 with adb in recovery following Doomlord's guide but as soon as I give the install command adb suddenly cannot see my device ?
Adb commands work fine up until that point, I'm throughly confused now. Do I need to unlock my bootloader to do that? I was under the impression that root and unlocked BL were not necessary for that.
I used towelroot to root my phone about a month ago. I read somewhere that the OTA update to Lolipop won't take unless it is absolutely stock. I am nopt the most knowledgeable about these things, so what exactly did using towelroot do that made it impossible to update to Lolipo OTA? How to I fix it so that Lolipop can be flashed to my phone? Thanks!
There's a 4.4.2 flashable zip I saw.
Can that not be flashed from the sdcard?
rockky said:
There's a 4.4.2 flashable zip I saw.
Can that not be flashed from the sdcard?
Click to expand...
Click to collapse
I did read about going back to 4.4.2, but was unable to cohesively follow it. I think that people were having trouble downgrading. Also, would that make my phone totally, absolutely stock? Kind of hijacking the thread, but it is still relevant to the OP's issue. I don't mind spending time on something if I know the outcome will get me to where I want to be. Thanks!
jeraldjunkmail said:
I did read about going back to 4.4.2, but was unable to cohesively follow it. I think that people were having trouble downgrading. Also, would that make my phone totally, absolutely stock? Kind of hijacking the thread, but it is still relevant to the OP's issue. I don't mind spending time on something if I know the outcome will get me to where I want to be. Thanks!
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/showpost.php?p=57338156&postcount=97

[Q] Soft-bricked Nexus 9 with no bootloader unlock

Dear all,
I am asking for the solutions to solve this issue.
The device goes into bootloop after updating to 5.0.2.
It was known that the device has not enable OEM Unlock through development options. (and cannot get into setting page at this moment.)
Therefore, i cannot unlock the device by using
"fastboot oem unlock" in the fastboot mode of the device.
I have tried wipe data and perform factory reset in recovery mode.
but the device still get into bootloop.
May i ask for any possible solution for flashing back stock rom?
I'm in the same situation. I believe the only solution is to return the device for "repair".
Go to recovery, wipe cache, making sure to give it a full hour to finish. Then reboot. You'll probably still be on 5.0.1.
GrillMouster said:
Go to recovery, wipe cache, making sure to give it a full hour to finish. Then reboot. You'll probably still be on 5.0.1.
Click to expand...
Click to collapse
I am having the same problem. I tried wiping the cache from recovery as well as doing a full reset, and still stuck. HTC is suggesting sending them the device.
FWIW, I am locked/unrooted and running stock.
Have the same problem. Recovery said, that update has been installed, errors reported on tzdata read.
Additional problem: bougth from Amazon and use at russia… Delivery cost is ~insane.
penguinolog said:
Have the same problem. Recovery said, that update has been installed, errors reported on tzdata read.
Additional problem: bougth from Amazon and use at russia… Delivery cost is ~insane.
Click to expand...
Click to collapse
Were you able to fix it? I'm having the same problem, I just can't believe it's not possible to unlock the bootloader any other way.
if im stock 5.01 and i try to do an OTA update to 5.1.1, will that make a bootloop? or its only via 'bad flashing' in adb that causes loop?
i don't want to void my warranty untill im sure im going to keep my n9 LTE
thx
cobyman7035 said:
if im stock 5.01 and i try to do an OTA update to 5.1.1, will that make a bootloop? or its only via 'bad flashing' in adb that causes loop?
i don't want to void my warranty untill im sure im going to keep my n9 LTE
thx
Click to expand...
Click to collapse
It appears from feedback from other users, that sometimes the OTA can just "go wrong". So it's best to unlock your bootloader prior to installing the OTA. That way, if something does go wrong, you can easily recover from it.
cam30era said:
It appears from feedback from other users, that sometimes the OTA can just "go wrong". So it's best to unlock your bootloader prior to installing the OTA. That way, if something does go wrong, you can easily recover from it.
Click to expand...
Click to collapse
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
cobyman7035 said:
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
Click to expand...
Click to collapse
That's good news. Glad to hear it.
cobyman7035 said:
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
Click to expand...
Click to collapse
Simply switching "Enable OEM unlock" doesn't void your warranty, and it covers your butt in case something happens.

[Updated] OTA update bricked your Nexus 9? -- Google Now Provide OTA images

Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Instructions for sideloading the OTA images.
Use the latest OTA image from the above link instead of using Android N OTA.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Posting this in a new thread so more people see it.
Get the Android N Preview OTA from here.
Google has updated the OTA zips again for nexus 9.
We've updated the OTA packages on https://developer.android.com/preview/download-ota.html. This should fix the issue with adb sideload failing at 47%. Please try again with the new packages.
Click to expand...
Click to collapse
Quote taken from here
Note: Removed Marshmallow from the tittle because it has been report to work for lollipop brick as well.
Try this if sideloading a marshmallow OTA doesn't work. See here. (Also see this link for instructions on sideloading.)
My Nexus 9 that I purchased when the device was originally put up for sale, got an OTA to 6.0.1 a few weeks back. I had not activated OEM Unlock in settings, no developer mode so I also hadn't activated USB Debugging. Well, that legit OTA ended up soft bricking my device. From that moment on, all it would ever do was show the booting screen until the battery died.
I tried manually sideloading Google's official update to 6.0.1 to the device, no go. It kept failing during the process.
I tried (knowing it likely wouldn't work) playing around with Nexus Root Toolkit to see if maybe there was some magic in there that would work, no go.
After two straight weeks of trying, I could not get an update pushed to the device and last night had resigned myself to sending it into HTC for repair... something that they weren't sure yet whether or not would incur a cost FOR ME to repair, even though in a completely stock and pristine device, the OTA update is what hosed it.
This morning, I heard that Google released sideloadable Android N images for all supported Nexus devices that some were saying would work in this scenario. (https://plus.google.com/u/0/+ArtemRussakovskii/posts/K4oUnQymMqG)
And what do you know, that totally worked. It sideloaded to my Nexus 9 and its working again.
tl;dr If you got an OTA for your Nexus and it ruined the device, and nothing else works, try to update it to N. Worked for me.
Thanks to Artem and Lenny Fudenna for the heads up.
Click to expand...
Click to collapse
dweissinger said:
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
Click to expand...
Click to collapse
Thanks pal. You saved my Nexus 9 LTE after 4 months of soft brick.
This is because the N OTA is a full-block/full image OTA zip that doesn't check the system partition of it's current state. It will just blindly flash. This kind of OTA image is perfect for recovering locked bootloader devices because it is signed by Google, unlike their factory images which are not signed and gets flashed like any other custom ROM.
I hope Google will provide full-block OTAs for major version releases in the future to resolve instances like this. With the requirement of enabling OEM unlocking in the new Nexus devices, full-image OTAs like these would be required to recover from failed standard OTA updates. I imagine this can happen with the monthly security update OTAs like it did with you. For those who never had an OTA fail, they never knew they were dodging bullets all those times.
For those concerned that stolen devices can be re-purposed this way, fear not. Even with a factory reset (no more user data), after flashing this OTA to get my Nexus 9 working again, it asked me to authenticate with the last owner's credentials before letting me in. So this should still deter thieves if they get a hold of a full-image-OTA thinking they can just flash a factory image with a locked bootloader. Much safer than leaving the bootloader unlocked or keeping OEM unlocking enabled.
Another reason why it's a good idea vs the old Full Factory Image method: will not delete user data.
I seriously hope the Google Android team consider releasing full-image OTAs in the future as standard practice - at least for major Android releases (no need to do this for all the minor updates - kind of like reinstalling Windows and getting all the security updates).
Creating a full-image OTA shouldn't add much to their workflow. The OTA for Lollipop to Marshmallow, for example, would have to be a full-image OTA anyways. The only thing the Android team needs to do is to disable version checking so it can be side loaded no matter what state the system partition is in.
Also, if a user wants to keep their data partition intact, a full-image OTA for the major release is important. If Google only released a single full-image OTA for the original OS the device released with (example: Lollipop), and someone needs to recover from a bad OTA update when they're already in Marshmallow, the original Lollipop build may not work with the new data partition schema.
Of course you'd be thinking "I'll just be happy the device is not bricked", but if you can also solve the "I'm glad I didn't lose any data" dilemma without much effort, why wouldn't you?
Well, I have discovered an exception to this solution .
Yesterday I set my Nexus 9 to update to the Android N Preview but when I returned I had the robot with the exclamation mark and my machine would not boot . I went through all the processes to try and get a factory image of 6.0.1 installed but had not preset my bootloader to allow an unlock.
I eventually found this article and duly downloaded the Android N developer preview factory image and then tried to ADB sideload but the process failed.
And I knew why it failed. It failed because it told me that the factory image I had downloaded from the correct URL was older than the version that had failed the OTA process.
Google does not give a version date for their Android N developer images so I had concluded that they must be up-to-date.
I now realise that their image was not up-to-date so I will now have to wait for Google to publish a newer version of their Developer N factory image that is the same age or newer than the failed OTA update from yesterday so that I can successfully ADB sideload the image without getting this error .
Just as well that I have some technical knowledge or I'd be sending my Nexus 9 back to HTC for something that was not my fault.
Overall - not impressed.
Herbiv4 said:
I eventually found this article and duly downloaded the Android N developer preview factory image and then tried to ADB sideload but the process failed.
Click to expand...
Click to collapse
You don't sideload a factory image, you sideload an "OTA zip" linked in the OP or again here
corkiejp said:
You don't sideload a factory image, you sideload an "OTA.zip" linked in the OP or again here
Click to expand...
Click to collapse
Just to clarify - I was up until 3:30am this morning having been through factory images, OTA zip files, the SDK for Android, the Wugfresh Nexus Root Kit, installing Linux Mint to try and get fastboot working when my Windows PC didn't seem to want to recognise my Nexus 9. I eventually sorted out the drivers included with the SDK because the Wugfresh drivers did not play nicely with my Nexus 9. Then I realised that as my bootloader was locked I could get nowhere with restoring 6.0.1. MMB29R.
After more googling I found this webpage and the link to the OTA .zip file plus the instructions of how to force the upgrade to the developer preview of Android N. Fantastic I thought.
I did in fact download the OTA .zip file from the right URL posted above and tried to sideload that file but it failed because the download was older than the files that Google sent to my Nexus 9 OTA earlier the previous afternoon.
So, as I said before, I now have to wait until Google to update their OTA .zip file to a version equal to or newer than the failed OTA file from yesterday.
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
So apologies for using the wrong phrase - it wasn't a factory image - it was an OTA .zip file and my tablet did try to send over the .zip file but it failed owing to it's age relative to the files already on my Nexus 9.
Hope that this clarifies everything.
The bottom line is - sideloading an OTA.zip file isn't as simple as it has been made out to be.
Herbiv4 said:
I did in fact download the OTA .zip file from the right URL and tried to sideload that file but it failed because the download was older than the files that Google sent to my Nexus 9 OTA.
Click to expand...
Click to collapse
Thanks for clarifying, Google must have sent you an Android N OTA which included the latest patch. Hopefully they will provide new OTA zips with Preview 2 in April. Which should hopefully resolve your problem. As i haven't seen a link for the latest patch OTA yet.
Herbiv4 said:
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
Click to expand...
Click to collapse
You could setup a change detection on that page. I use it on the factory images page all the time.
Herbiv4 said:
The bottom line is - sideloading an OTA.zip file isn't as simple as it has been made out to be.
Click to expand...
Click to collapse
I remind you of the title of this thread "Marshmallow OTA update bricked ..." which should make this process still valid for those devices. Your findings are worth posting on the Android N thread.
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
ignaciouy said:
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
Click to expand...
Click to collapse
MPA44I is Marshmallow Developer Preview. Is your device bricked that long? You should have RMA'd that while in Warranty.
Please check stock recovery to see if your device reports a different build version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
corkiejp said:
MPA44I is Marshmallow Developer Preview. Is your device bricked that long? You should have RMA'd that while in Warranty.
Please check stock recovery to see if your device reports a different build version.
Click to expand...
Click to collapse
You mean this?
That long because I tried everything, and nothing worked
I can't RMA because this was a gift in USA, and I live in Uruguay. So I can't send it to usa and get another back, I think I can't do that. + I can't afford it :/
ignaciouy said:
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
Click to expand...
Click to collapse
ignaciouy said:
That long because I tried everything, and nothing worked
I can't RMA because this was a gift in USA, and I live in Uruguay. So I can't send it to usa and get another back, I think I can't do that. + I can't afford it :/
Click to expand...
Click to collapse
What error did you get when trying to sideload the Android N zip?
corkiejp said:
What error did you get when trying to sideload the Android N zip?
Click to expand...
Click to collapse
First of all, thanks for replying, this is what I get
I checked the md5 of the file and it's the same of the google download page
ignaciouy said:
First of all, thanks for replying, this is what I get
I checked the md5 of the file and it's the same of the google download page
Click to expand...
Click to collapse
You maybe looking to perform a miracle here.
Other things to check: -
Your Cable
Versions of adb and fastboot on your PC (have you got the latest).
People have reported errors when using a faulty cable.
The stock recovery on your device maybe to old to apply the Android N OTA.
I tried 3 cables, and the same with all of them.
192:volantis-npc56x ignacio$ adb version
Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
192:volantis-npc56x ignacio$
Isn't that the last one?
The stock recovery on your device maybe to old to apply the Android N OTA.
Click to expand...
Click to collapse
And what can I do? :-|||
Herbiv4 said:
So, as I said before, I now have to wait until Google to update their OTA .zip file to a version equal to or newer than the failed OTA file from yesterday.
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
Click to expand...
Click to collapse
corkiejp said:
You could setup a change detection on that page. I use it on the factory images page all the time.
Click to expand...
Click to collapse
I setup a change detection on the page and google has update the OTA zip for Nexus 9.
Nexus 9
"volantis" volantis-ota-NPC56X-2785955f.zip
MD5: 36d813350fd660ab751a434782f5523f
SHA-1: 2785955fd77310106d2fa9f02f93b595d77b8e72
Nexus 9G
"volantisg" volantisg-ota-NPC56X-d93e161c.zip
MD5: 1fb7d83cd065a962dbed49e72db97dc4
SHA-1: d93e161c15503dc641b654f6ef4c1611222bc9fd
Click to expand...
Click to collapse
corkiejp said:
I setup a change detection on the page and google has update the OTA zip for Nexus 9.
Click to expand...
Click to collapse
Hello there Corkiejp, thanks very much for doing this. I downloaded this new OTA .zip file last night and used adb sideload as instructed. The transfer got to 47% on the PC side and on the Nexus 9 side the installation started briefly before suddenly rebooting so the install fails. When booting to recovery it shows the very latest version has registered but as the install has failed it cannot boot. I have done a factory reset and tried the process again but got the same result.
I'll have to wait for the next update and I'll try process again.
Otherwise, I'll have to ask HTC to fix this for me.
Herbiv4 said:
Hello there Corkiejp, thanks very much for doing this. I downloaded this new OTA .zip file last night and used adb sideload as instructed. The transfer got to 47% on the PC side and on the Nexus 9 side the installation started briefly before suddenly rebooting so the install fails. When booting to recovery it shows the very latest version has registered but as the install has failed it cannot boot. I have done a factory reset and tried the process again but got the same result.
I'll have to wait for the next update and I'll try process again.
Otherwise, I'll have to ask HTC to fix this for me.
Click to expand...
Click to collapse
Get the recovery logs to see where it failed and post the results in this thread.
Hello, good evening I'm having the same Issue that herbiV4; it gets till 47% then reboot and shows the android in its back and *ningun comando" (No commands) if I try to reboot, it send me once again to the recovery menu like... It doesn't have a OS? Even when it "updated" the recovery menu I really REALLY need help, I already contacted with HTC and the told me to send it but I'm from Venezuela so that's absolutely impossible for me, the Nexus has been bricked for 4 months ;---;
This is what the ADB shows me in the pc.
And this is what the tablet shows exactly after it reboot post "No error" from adb
This is the Last log, I truly dont get the "error" thingy :/
Help :crying:
If your getting error's from this process, it maybe helpful to google, to report your recovery logs to this thread.
If your device is in this state we would really appreciate logs from more devices.
1) Power off your tablet.
2) Press and hold the Volume Down button. Then, while holding Volume Down, also press and hold the Power button until the tablet turns on. (Fastboot mode)
3) Press the Volume Down button once to highlight "Recovery." Press the Power button to start in recovery mode. You'll see an image of an Android robot with a red exclamation mark. (Recover mode)
4) Press and hold down the Power button. Then, while holding Power, press and release the Volume Up button once.
5) Use the Volume Up and Volume Down buttons to navigate to "View recovery logs", and press the Power button to select.
6) There might be multiple log files. Start from "/cache/recovery/last_log" to view the log contents. Look for lines like "Finding update package...", "Opening update package...", etc. These lines indicate that the log file is for the OTA.
7) Navigate towards the end of the log using the volume buttons and look for any errors.
We are specifically interested in knowing if the bricked devices show "fsync failed: I/O error". We are exploring options to recover devices with locked bootloaders that are bricked. We'll post an update here.
Click to expand...
Click to collapse
This process has been reported to work on a bricked lollipop device.
This process has been reported to work on a bricked lollipop device.
defmetal96 said:
Hi I know this is a long shot but do you know how to fix this ^^ abort error?
Currently stuck on LRX22L but it is not booting as the OTA update to LRX22L failed for no apparent reason, foolishly my bootloader is still locked and the OEM unlock option is not checked.
is there any salvation?
Click to expand...
Click to collapse
defmetal96 said:
Sideloaded the N preview and that finally did the trick.
For anyone else with this issue I think the N preview is the only escape at present if your tablet is locked and refusing OTA updates
Click to expand...
Click to collapse

Tesco Hudl 2... Is anyone still here?

Hi Interweb!
I was wondering just how many people were still "in the know" on the topic of rooting, unlocking bootloader and general Android development for the Tesco hudl2 [HTFA4B] tablet. Obviously with Tesco's little trick of shutting down the servers, two thirds of us were left with Kitkat, and having had enough of it, I decided to root. Everything went fine. I booted back into Android KitKat (stock) and then installed Xposed Framework. Presumably the installation failed, as upon rebooting, the tablet booted straight into stock recovery. I have been seeing this for two months now, having removed the battery several times, refitting it and trying to reinstall android with the ROM form this link:
hudl2_ota_rel.android-build.20150803.092218_to_rel.android-build.20150917.142239.zip | GEM-FLASH Firmware
firmware.gem-flash.com
Either way, I am now faced with a soft brick. Does anyone know how to fix? The exact text displayed in Stock Recovery is down below.
To be clear, I occasionally DO see the "powered by android" screen before booting into recovery, but not every time.
A possible solution would be if there is a fastboot mode I can access, I may can use Odin and flash a Custom ROM onto the tab. Or, alternatively, if anyone has, or knows someone who may have Tesco's key signature, that too would be useful in building a ROM.
I've had this tablet since I was 7 years old, and it's been part of my life for many years now. If anyone can help please do
Many Thanks.
[TAGGING SOME PEOPLE WHO MAY BE ABLE TO HELP]
@Rickav
@droident
People not on XDA who may can help:
Kirwan Lyster - Head of Facebook's Android department and former head of Tesco Connected Devices (hudl) software team. [email protected]
The Guardian Consumer Champions
BBC Watchdog
Martin Lewis - Money Saving Expert.
Android system recovery <3e>
K0T49H.rel.android-build.20151102.170607 release-keys
Volume up/down to move highlight:
power button to select.
reboot system now
wipe data/factory reset
wipe cache partition
apply update from ADB
apply update from external storage
apply update from cache
[ANDROID WITH OPEN BELLY]
No Command.
Click to expand...
Click to collapse
Hey, just got pinged by XDA after a long time. It's all so sleek-looking now.
I'll cut to the chase—Unfortunately, I've got nothing to help with here. I'm a fan of the Hudl2 as well and still have it around as a backup ebook reader as the screen works reliably. It's running walking stock Lollipop and it occasionally throws up Play Services errors (which appears to be resolvable).
Following the dead download link on the MoDaCo forum post, I searched for stock ROMs and landed on the same Gem Flash site that you linked. Specifically, I found 3 results linked to the Hudl2. For the sake of future visitors, I've downloaded and attached all 3 of them to this post (in case it's locked, the password is "www.gem-flash.com").
I wouldn't get my hopes up, but it might be worth giving each a go. Honestly, I wouldn't even know where to begin with flashing but I think you're way ahead of me here.
Genuinely wishing you the best of luck, and I really hope it works out.
Rickav said:
Hey, just got pinged by XDA after a long time. It's all so sleek-looking now.
I'll cut to the chase—Unfortunately, I've got nothing to help with here. I'm a fan of the Hudl2 as well and still have it around as a backup ebook reader as the screen works reliably. It's running walking stock Lollipop and it occasionally throws up Play Services errors (which appears to be resolvable).
Following the dead download link on the MoDaCo forum post, I searched for stock ROMs and landed on the same Gem Flash site that you linked. Specifically, I found 3 results linked to the Hudl2. For the sake of future visitors, I've downloaded and attached all 3 of them to this post (in case it's locked, the password is "www.gem-flash.com").
I wouldn't get my hopes up, but it might be worth giving each a go. Honestly, I wouldn't even know where to begin with flashing but I think you're way ahead of me here.
Genuinely wishing you the best of luck, and I really hope it works out.
Click to expand...
Click to collapse
Thanks @Rickav . Presumably you saw my DM.
All three come out with:
Code:
Finding update package...
Opening update package...
Verifying update package...
E:end of footer from /tmp/update.zip not 0xFFF (File exists)
E:signature verification failed
Installation aborted
once adb sideloaded in stock recovery (all I have access to).
Is there any chance of you making a nandroid backup zip using the CWM fastboot custom recovery in "hudl2 root stuff.zip" on MoDaCo? I know it's asking a lot. @paulobrien might send me a system image and couple of OTA zips and other assorteds for a start which may help. Before I attempted Xposed I was trying to get Lollipop but the OTA server has been decommissioned (confirmed by Kirwan Lyster, head of hudl2 software), so if I can do that by other means that'd be great. Fist priority though: get it running. You can see by the video what is happening.
Many thanks,
Cessna
If can't do this, may need to try to unlock bootloader. Any ideas, also useful.
@Rickav I really appreciate your assistance, but going by this link:
New update Sept 15
www.modaco.com
It looks like my tablet is dead. What do you think of this?
Hi,
In case anyone is looking for clear instructions on how to overcome the problem after a factory reset of the Tesco Hudl 1 & 2 you will find them here (works for Hudl 2 as well). Use a date between 27 June 2019 and 26 June 2020 :
HUDL bricked after factory reset and how to fix it - Hey Munky!
I did a factory reset on my HUDL and bricked it. Here's a quick step-by-step guide on how to unbrick it after a factory reset.
www.heymunky.co.uk
Or the same with pictures but remember to use a date between 27 June 2019 and 26 June 2020 :
Rob's stuff - Hudl - Fix
Update 23 May 2023: This mechanism for recovery of a factory reset Hudl 1 no longer works. Due to the Tesco server at https://device.tesco.mobile.com/ no longer responding correctly to requests this technique no longer works and will fail after Step 18. As far as I know my Custom ROM is now the
rob.themayfamily.me.uk
(If this date solution ever fails then another option is to create a new user in the settings menu and reboot into it.)
Post if it works for you
I am going to try and update my hudl 2 to lollipop android 5. ADB sideload fails so i need to update from sdcard or from cache folder, just a case of where the cache folders are and how to add to them.
Hi @ushilives
Whatever you do, please don't do that! Doing so causes your device to become unbootable, and unrecoverable!!!
It will end up like mine did, and, trust me, you ain't getting it back, KitKat, Lollipop, or else.
Sorry to let you down, I just don't want to see another Hudl killed.
Regards,
Cessna
Did yours brick before or after you installed xposed?
CessnaBroon said:
Hi @ushilives
Whatever you do, please don't do that! Doing so causes your device to become unbootable, and unrecoverable!!!
It will end up like mine did, and, trust me, you ain't getting it back, KitKat, Lollipop, or else.
Sorry to let you down, I just don't want to see another Hudl killed.
Regards,
Cessna
Click to expand...
Click to collapse
Did yours brick before or after you installed xposed?
ushilives said:
Did yours brick before or after you installed xposed?
Click to expand...
Click to collapse
When I rebooted after installing xposed. I also know people who bricked it from sideloading other builds in ADB, due to Tesco's locked bootloader having extra security measures.
CessnaBroon said:
When I rebooted after installing xposed. I also know people who bricked it from sideloading other builds in ADB, due to Tesco's locked bootloader having extra security measures.
Click to expand...
Click to collapse
Ah OK thanks. I'll have a read more into it Rather than using recovery
Please do. Just check for me please, does it still boot? If yes, what have you attempted so far? Thanks

Having trouble installing the 11.0.2.BE88CF Update

I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
This also what happened to me.
szophiya said:
I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
JazzieBoi said:
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
Click to expand...
Click to collapse
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
arda99 said:
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
Click to expand...
Click to collapse
Wow I had no idea metro did that. I knew metro doesn't like unlocked bootloader's and are strict. I will never buy one in my life .
szophiya said:
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Click to expand...
Click to collapse
You could try flashing the stock boot.img via fastboot to see if it finishes installing. https://forum.xda-developers.com/attachments/boot-11-0-1-be88cf-img-zip.5399231/
You'll need to reboot to fastboot and then run: fastboot flash boot_a boot-11-0-1-be88cf-img and then fastboot boot_b (img filename). Try rebooting and performing the update then.
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Misclicked and did a double post, sorry.
szophiya said:
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Click to expand...
Click to collapse
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
JazzieBoi said:
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
Click to expand...
Click to collapse
The MSM you provided is for BE86AA and BE89BA, not for BE88CF which is what they need.
As far as I know, no MSM exists for BE88CF: https://forum.xda-developers.com/t/...8cf-11-0-2-be88cf-rooting-impossible.4367271/

Categories

Resources