Related
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Ste_J said:
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Click to expand...
Click to collapse
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Floralina123 said:
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Click to expand...
Click to collapse
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Ste_J said:
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Click to expand...
Click to collapse
Hi Ste_j, thanks for the reply. I unrooted it already, or so I thought using nabilabs but it looks like twrp was removed and gapps remains - which I'm happy about seeing as I can't update it using ota update with google playstore- that could have been a disaster.
Here is my question I posted -
I Apologise for my ignorance in android in general.
I have rooted a Nabi 2 successfully installing Gapps etc using Nabilab, which was a pleasure to use. Now that the new OTA update is available which includes the Googleplaystore I would like to unroot and get the OTA updates. I thought I had unrooted it - using Nabilabs (twrp would not work, can't remember why but I think the touchscreen part wouldn't work for me). I returned to stock using (option 1. -1.9.37. Android can boot.) recovery using Nabilabs. I think I did a factory reset after that -sorry but it was weeks ago. Anyway, I suspected something wasn't right when I still had Gapps. I don't have TWRP on it now.
When I do the OTA update I get the dead android on reboot. Nabi is working fine apart from that. I read a lot of pages on this website but it ended up confusing me more than helping me unfortunately as I'm not android savvy.
I just need someone to tell me exactly what to do to properly unroot the Nabi so that it is truly back to original so I can use the OTA updates. I have no need to root the nabi again as the google play store is now officially available. And I've got a UK Nabi 2.
Ste_j,
I assumed I had a Uk nabi because I'm in Ireland. I don't know how to check this as it doesn't say uk here but the
model no is NABI2-NV7A-IE
Android version 4.0.4
Kernel version 3.1.10-00298-ge08b99f
[email protected] #2
SMP PREEMPT Tue Feb 26 17:21:35 HKT 2013
Build no IMM76L
Product version: 2.0-release-keys
I don't want to unroot any further unless I can get the latest ota update that gives me the google play store. I would rather leave it as it is now(gapps still on it) until you get yours working successfully I will gladly follow your lead from start to finish then. I just hope someone in the know replies with the solution. I too had been reading the nabi forum but cannot post there.
Tnx
Sounds like one of my recent 1am going on for 2 adventures in nabi land!
Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
Ste_J said:
Sounds like one of my recent 1am going on for 2 adventures in nabi land!
Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
Click to expand...
Click to collapse
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
metalheadkicks said:
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
Click to expand...
Click to collapse
Not yet. Waiting on 2.2 to be uploaded on the other thread. Hopefully the guy will get chance to upload over the weekend
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?
In theory restoring either of these(2.0 stock or 2.1 stock) http://forum.xda-developers.com/showpost.php?p=50158865&postcount=67
should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.
Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.
A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.
Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
aicjofs said:
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?
In theory restoring either of these(2.0 stock or 2.1 stock) http://forum.xda-developers.com/showpost.php?p=50158865&postcount=67
should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.
Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.
A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.
Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
Click to expand...
Click to collapse
Thank you. I have restored 2.0 from that post
Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
Ste_J said:
Thank you. I have restored 2.0 from that post
Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
Click to expand...
Click to collapse
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.
Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi.
aicjofs said:
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.
Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi.
Click to expand...
Click to collapse
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
Ste_J said:
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
Click to expand...
Click to collapse
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
aicjofs said:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
Click to expand...
Click to collapse
That was going from 2.1 to 2.2
And yes i appear to be cross threading at the moment. Grabbed the 2.2 update and just spent the last hour trying to get past the stuck nabi screen. Got back to 2.1 eventually. Fastboot and Nabilab with just enough time to fire over previous TWRP and get back to the restore
Any ideas on how to update the boot loader?
Moving back to the other thread http://forum.xda-developers.com/showthread.php?t=2041224&page=9
aicjofs said:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
Click to expand...
Click to collapse
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
Verifying current system. . ,
assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")
E:Error in /cache/nabi2-update.zip
(Status 7)
Installation aborted
So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
Uk nabi update - leaving nabi as is until it's solved
I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
MattP79 said:
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
Verifying current system. . ,
assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")
E:Error in /cache/nabi2-update.zip
(Status 7)
Installation aborted
So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
Click to expand...
Click to collapse
Floralina123 said:
I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
Click to expand...
Click to collapse
Have you tried this? http://forum.xda-developers.com/showpost.php?p=50431606&postcount=98
It has to be done manually but should get a UK Nabi to complete stock version 2.2.
In case you need to know for some reason in the future that is a SHA1 hash not md5.
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
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
UPDATED TOPIC! 02.08.2017
ASUS has released the NEWEST Nougat Update for ZF3U:
Newest Release: Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
Previous Version: Version WW_14.1010.1705.49 Release Date: 21.06.2017
Here is the official Update for Manual Install. DIRECT from ASUS Servers. Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/UL-ASUS_A001-WW-14.1010.1706.50-user.zip
Via:
http://https://www.asus.com/Phone/ZenFone-3-Ultra-ZU680KL/HelpDesk_Download/
If the link is expired Get it from the Asus ZenFone 3 Ultra Support and Firmware Website under Drivers and Tools-ANDROID Section. It is for the WW Version:
UPDATE! :OTA Update Working ONLY with phones with LOCKED Bootloaders. The Manual Update will work with both LOCKED and UNLOCKED Bootloaders. I have tested the OTA Update and after I unlocked my ZF3U's bootloader, I can no longer get update notification (on my previous ZF3U-I am on my 2nd one). From what I have read, ASUS servers block any devices with unlocked bootloaders from accessing automatic system updates. My only option is to find a way to RELOCK the bootloader or use the Manual Update file.
Enjoy!
Changelog:
Android 7.0 Nougat comes with handful of features such as App Shortcuts, Multi Window support, restart setting to power menu, Launch the camera by pressing the power button twice, Image Keyboard support, 100 emoji added, GIF Support, Quick Reply via Notification, Notification Redesigned panel, Notifications prioritization, Enhanced Doze Mode, System UI Tuner, Customizable Quick Settings, Don Not Disturb, New Settings Panel Redesigned, Data Saver per App, seamless updates and New Emoji Support.
-----------------------------------------
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item：
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to：
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, .
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
ctorbaoglu said:
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
It may be because your Bootloader is unlocked. If it is you will not receive the update. My ZF3U's bootloader was locked when I received the update. However, when I unlocked the bootloader, rooted and then decided to wipe everything through TWRP to do a fresh install of everything to reinstall Android 7.0 the trouble started. Now, I cannot do firmware update using the system Update menu (notification of update availability is not there). This is because the bootloader is now unlocked and I don't know if it is possible to relock it. I guess I have to wait for the full manual package of Android 7 to become available or see if anyone can help me to relock the bootloader and then update from Android 6.0 original firmware. I was excited to be finally getting Android 7.0 but only managed to use it for 1 day. Oh well, you live and learn.:crying:
Click to expand...
Click to collapse
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
AWFRONT said:
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
Click to expand...
Click to collapse
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
doctahjeph said:
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
Click to expand...
Click to collapse
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
doctahjeph said:
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
Click to expand...
Click to collapse
I have tried your suggestion numerous times and;
-it appears that when I boot to Android M, I don't have any sound in calls, fingerprint and other issues fully remain.
-when I upgrade to Android N, then Iam able to hear call sounds but fingerprint scanner still does not register and other issues still remain.
I have a feeling that somewhere along the process my device has enabled some sort of encryption and this is preventing the device from enabling all the features. No matter how many times I install/reinstall/wipe using stock or TWRP no change.
Does anyome know how I could disable encryption either using some sort of google service or through root etc... In settings device reports that it is encrypted. Also when I first booted the device after firmware update encrypting device message was shown. Not sure whats going on with my device. Hope to find out/fix soon though.
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
AWFRONT said:
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Click to expand...
Click to collapse
???? Thank you!!!
ASUS has released the NEWEST Nougat Update for ZF3U.
Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item：
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to：
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, .
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
Once again, I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Never mind.
AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
Hey @AWFRONT How did u manage to go back from android 7 to 6 ...i recently updated my phone to nougat and want to go back to mm. Could u help me out I have unlocked bootloader
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
AWFRONT said:
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
Click to expand...
Click to collapse
all of this from twrp or stock recovery
If you have TWRP installed then apply from it, if not you can use the stock recovery of Android 6.0 as posted in one of the topics of ZF3U forum sections and flash it using custom recovery and then flash the appropriate firmware file of Android MM version 6.0 and on completion wipe cache, factory data and reboot.
Due to lack of developer support for this device, I do not recommend that you rollback the firmware. When my 1st device failed I realised that ASUS devices don't have the software fixability ease of Samsung devices so I am using my 2nd ZF3U in its original factory state. I love the device as it is and don't want to mess with it and root is no longer important to me.
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
gubbilo144 said:
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
Click to expand...
Click to collapse
mine is
Malam
anybody updated to WW-14.1010.1711.62 is it still 7.0 or 7.1.1
So my phone is still stuck on Android 9 with the November Security Update. I had the Android 10 update/upgrade pending install on my phone but I held off upgrading due to the many reported issues people reported with it. One day my phone randomly rebooted but stayed on Android 9. Since then, every time I check for an update, it says it's currently up-to-date. Has this happened to anyone else? Do I need to manually download the Android 10 update and flash it from recovery? Where can I even download the update/upgrade from?
I actually ended up buying a new phone because of this issue (my job requires me to have company email on my phone and it has to have at least the latest quarterly security update). None too pleased.
I have the exact same issue. Been digging for a while trying to find the solution.
ctechbob said:
I have the exact same issue. Been digging for a while trying to find the solution.
Click to expand...
Click to collapse
Manually download and flash the updates yourself. That's what I had to do.
Looks like they pushed an update tonight (6/15/20) Showing A10 update with 5/2020 security patch.