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.
Hello everyone. I wondered if anyone could give me some help with updating my Ascend Mate 2 model MT2-L05 to 4.4 KitKat?
I received the phone on Thursday and it came with 4.2.2 installed.
It shows build number as : MT2-L05V100R001C17B912
From my searching, this appears to be the China Unicom version. I have been to updates on the phone and searched OTA and i'm told that the device is up to date. I have no option on the phone to update from SD card.
I have downloaded the 4.4 update ROM from the official Huawei site for the MT2-L05 and have tried flashing it with the 3 Button bootup method and I receive this message when the autoflasher starts :
checking Module MD5RSA...OK
checking Module CRC...OK
checking Module...CURVER...OK
checking Module VERLIST...
sd_update_func.....fail
then above this recovery gives me 4 options :
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
I then choose reboot system and the phone starts up no problem.
I have tried putting the dload folder on a 16gb Lexar sd card, a brand new class 10 Sandisk ultra sd card, and i have also tried putting the dload folder on the phone's internal storage and i get the same error message every time i try to update.
Any help would be greatly appreciated. Thank you!
4L0M said:
Hello everyone. I wondered if anyone could give me some help with updating my Ascend Mate 2 model MT2-L05 to 4.4 KitKat?
I received the phone on Thursday and it came with 4.2.2 installed.
It shows build number as : MT2-L05V100R001C17B912
From my searching, this appears to be the China Unicom version. I have been to updates on the phone and searched OTA and i'm told that the device is up to date. I have no option on the phone to update from SD card.
I have downloaded the 4.4 update ROM from the official Huawei site for the MT2-L05 and have tried flashing it with the 3 Button bootup method and I receive this message when the autoflasher starts :
checking Module MD5RSA...OK
checking Module CRC...OK
checking Module...CURVER...OK
checking Module VERLIST...
sd_update_func.....fail
then above this recovery gives me 4 options :
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
I then choose reboot system and the phone starts up no problem.
I have tried putting the dload folder on a 16gb Lexar sd card, a brand new class 10 Sandisk ultra sd card, and i have also tried putting the dload folder on the phone's internal storage and i get the same error message every time i try to update.
Any help would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
KK is not available for the phone in the US... yet. Apparently, it is coming but for now, you are stuck with JB.
Thank you for the reply zzEvilGeniuszz, but I am in the UK, and I own the Hisilicon powered Ascend Mate 2 from China.
I do not own the US model, which i believe off the top of my head is Model no : MT2-L03.
I have the correct 4.4 rom downloaded from the official Huawei chinese site and i have also tried the needrom version ( which i think is exactly the same as the official one ), I just cannot get it to flash correctly.
Best Regards !
4L0M said:
Thank you for the reply zzEvilGeniuszz, but I am in the UK, and I own the Hisilicon powered Ascend Mate 2 from China.
I do not own the US model, which i believe off the top of my head is Model no : MT2-L03.
I have the correct 4.4 rom downloaded from the official Huawei chinese site and i have also tried the needrom version ( which i think is exactly the same as the official one ), I just cannot get it to flash correctly.
Best Regards !
Click to expand...
Click to collapse
The only problem is that most of us have the US variant. I personally can't give any advice as to what to do and I'm pretty sure most of the active members on this mate 2 forum will be the same. :/
I am curious, if @4L0M uploaded the KK update to one of us, couldn't altering the build.prop to the same specifications as the US version make a difference? Meaning, if altering the build.prop to US version, then installing, would that work???
I don't think that would work.
There are currently 5 different official 4.4 roms for download from the official Huawei Chinese support site :
MT2_C00 : China Telecom
MT2-L05 : China Unicom ( My Ascend Mate 2 i think, although i see a lot of references to C00 too, so I am a bit confused.)
MT2-L05 : China Unicom Channel
MT2-L02 : Mobile Channels
MT2-L01 : China Mobile
I just extracted my build prop file and it says I am running version : MT2-L05V00R001C17B107SP1.
I have found out there are updated versions B109, B110, B111 and B115 of 4.2.2, so i will see if I can hunt them down and flash them in sequence, then try to flash 4.4
I don't know enough about reading my build prop to work out if it's any good to you, but i can upload it somewhere if you would like to have a look, bearing in mind, at the moment it's only 4.2.2
Ok, so I found all 4 update files and downloaded them. They are about 900 mb each.
I put the first update B109SP5 on my memory card, did the 3 button fastflash startup, and IT WORKED ! ! ! It flashed no problem, then rebooted.
Update Successful. The mate 2 had been on for about 2 mins, then a notification came up telling me that an update was available for the device.
Update was called B110.
I downloaded this ( was about 45mb, it rebooted. SUCCESS !
I then went to settings, Updates, and I now had more options in the menu !
I chose Update online, it downloaded and flashed another small update called B111.
Reboot Success !
Yet another online update , ownloaded, Flashed success This Update was B112.
I then went to online update again, and it said B408 update is available. This one is 4.4 KiKat !
Before i downloaded the 4.4 update, I installed Play Store from .apk i downloaded using the stock browser as none of these updates include the Play Store. I then downloaded Root Checker, as i had rooted the Mate 2 last night. I had lost root annoyingly, as I was going to try to use OTA rootkeeper to try and keep my root, before flashing 4.4
I tried downloading KingRoot apk from playstore, as this is the root manager I had installed yesterday, but I couldn't root with KingRoot.
4.4 is downloading as we speak...............or as I type, to be precise.
Hello again.
I successfully flashed my MT2-L05 to 4.4.2 KitKat at the weekend. Initial impressions are very good.
It seems to have freed up about 400mb of more RAM compared to 4.2.2
4.2.2 free ram at boot up 800mb
4.4.2 free ram at boot up 1245mb
I now have emotion UI 2.3, but haven't used it as i always use Nova Launcher Prime. The phone is miles snappier on 4.4.2, it's a noticeable improvement in speed around the UI and general app opening and viewing of websites etc. The pulldown toggle menu now has a nice transparency to it.
The lockscreen now has a pullup menu at the bottom in the dead centre for a pullup instant access menu to Calendar, Calculator, Torch and mirror apps. There is now a camera icon on the bottom right to instantly bring up a camera from your lockscreen.
4.4.2 on Ascend Mate 2 doesn't appear to support Album artwork on Lockscreen like my Note 2 4.4.2 did.
I also consistently have 1000 less points on Antutu benchmark ( 27,000 ) on 4.4.2 compared to 4.2.2 ( 28,324 )
I also have one more question if anyone can help me. My IMIE number on my box is the same as the one listed in status on the phone, yet the serial number on my box is now different from the serial number my phone shows in phone status. I don't know if this was always the case, or it changed when I flashed 4.4.2
Which one do you think i should Email to Huawei to see if they will send me an unlock code for bootloader?
I have tried for the hell of it Towelroot, Framaroot, Vroot, Kingo, Kingroot, SRS root, and Root Genius to try and root 4.4.2 to now avail. Root Genius told me it was successful, but no root on reboot.....which sucks.
4L0M said:
Hello again.
I successfully flashed my MT2-L05 to 4.4.2 KitKat at the weekend. Initial impressions are very good.
It seems to have freed up about 400mb of more RAM compared to 4.2.2
4.2.2 free ram at boot up 800mb
4.4.2 free ram at boot up 1245mb
I now have emotion UI 2.3, but haven't used it as i always use Nova Launcher Prime. The phone is miles snappier on 4.4.2, it's a noticeable improvement in speed around the UI and general app opening and viewing of websites etc. The pulldown toggle menu now has a nice transparency to it.
The lockscreen now has a pullup menu at the bottom in the dead centre for a pullup instant access menu to Calendar, Calculator, Torch and mirror apps. There is now a camera icon on the bottom right to instantly bring up a camera from your lockscreen.
4.4.2 on Ascend Mate 2 doesn't appear to support Album artwork on Lockscreen like my Note 2 4.4.2 did.
I also consistently have 1000 less points on Antutu benchmark ( 27,000 ) on 4.4.2 compared to 4.2.2 ( 28,324 )
I also have one more question if anyone can help me. My IMIE number on my box is the same as the one listed in status on the phone, yet the serial number on my box is now different from the serial number my phone shows in phone status. I don't know if this was always the case, or it changed when I flashed 4.4.2
Which one do you think i should Email to Huawei to see if they will send me an unlock code for bootloader?
I have tried for the hell of it Towelroot, Framaroot, Vroot, Kingo, Kingroot, SRS root, and Root Genius to try and root 4.4.2 to now avail. Root Genius told me it was successful, but no root on reboot.....which sucks.
Click to expand...
Click to collapse
I can't get antutu to work on mine. Also on stock 4.4.2. Not really an issue thought. There's a thread on rooting ham2 here that seems to work without the need to unlock bootloader.
Hi scpion. Thanks for the reply.
Antutu works perfectly for me, so not sure what the problem could be mate.
I managed to Root 4.4.2 in the end using Root Genius 2.0.1.3
Regards !
4L0M said:
Ok, so I found all 4 update files and downloaded them. They are about 900 mb each.
Reboot Success !
4.4 is downloading as we speak...............or as I type, to be precise.
Click to expand...
Click to collapse
Hi there.I have the same phone MT2-L05,the same specs exactly as yours,bought from to2c .
Could you please help and tell me step-by-step first the link you found the updates and then how did yousuccesfully managed that(the updating procedure)?I'm stocked to the 1st step that is,the phone trying to update by it's OTA but never happens so after turning on by itself, I have the screen you allready said a few posts before:
"then above this recovery gives me 4 options :
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
I then choose reboot system and the phone starts up no problem."
and there is no any updating.
Thanks
mAthosalas said:
Hi there.I have the same phone MT2-L05,the same specs exactly as yours,bought from to2c .
Could you please help and tell me step-by-step first the link you found the updates and then how did yousuccesfully managed that(the updating procedure)?I'm stocked to the 1st step that is,the phone trying to update by it's OTA but never happens so after turning on by itself, I have the screen you allready said a few posts before:
"then above this recovery gives me 4 options :
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
I then choose reboot system and the phone starts up no problem."
and there is no any updating.
Thanks
Click to expand...
Click to collapse
Hi there. I will try and help you if I can.
First thing.
Can you please got to "Settings" on your phone, scroll down to "About Phone" and look for "Build Number" and tell me EXACTLY what is listed there, we can then go from there.
4L0M said:
Hi there. I will try and help you if I can.
First thing.
Can you please got to "Settings" on your phone, scroll down to "About Phone" and look for "Build Number" and tell me EXACTLY what is listed there, we can then go from there.
Click to expand...
Click to collapse
Hi there, i want to know where do you get those 4 updates......my phone build is MT2-L05V100R001CHNC00B111.....i also cannot straight flash to kit kat MT2-L05V100R001CHNC00B606.............my phone cannot update OTA....and i also cannot find build after B111
You will find all build on emui.com (Chinese website)
wantwo said:
Hi there, i want to know where do you get those 4 updates......my phone build is MT2-L05V100R001CHNC00B111.....i also cannot straight flash to kit kat MT2-L05V100R001CHNC00B606.............my phone cannot update OTA....and i also cannot find build after B111
Click to expand...
Click to collapse
Here is a List and direct downloads of ALL Roms for Chinese variants of Ascend Mate 1, Ascend Mate 2 and Ascend Mate 7. Just find your model of phone and flash the corresponding Roms in the CORRECT ORDER :
http://susutun1.blogspot.co.uk/2014/06/android-firmware-huawei-m-series.html
I'm in the process of making cm11 and cm12 for the US version of the MT2. It would help greatly if I had a dump of the 4.4 system files for this phone. Unfortunately I don't know how to extract them from the proprietary format. Would anyone be willing to help me out with a system dump from their 4.4 phone? Please PM me and I can provide detailed instructions. You will need to be rooted.
All the US owners would be hugely grateful.
Thanks!
tdm said:
I'm in the process of making cm11 and cm12 for the US version of the MT2. It would help greatly if I had a dump of the 4.4 system files for this phone. Unfortunately I don't know how to extract them from the proprietary format. Would anyone be willing to help me out with a system dump from their 4.4 phone? Please PM me and I can provide detailed instructions. You will need to be rooted.
All the US owners would be hugely grateful.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2433454
Would that help any tdm?
Moody66 said:
http://forum.xda-developers.com/showthread.php?t=2433454
Would that help any tdm?
Click to expand...
Click to collapse
Thanks, it may. I will need to find someone with a windows box or dig up the referenced perl tools.
I will give it a shot as well. mtyler7807 has used it. I will pm him just in case.
I uploaded a decrypted update image from the MT2-L05 in this forum months ago.
Download it here :
http://forum.xda-developers.com/ascend-mate2/general/resource-unpacked-mt2-l05-4-4-2-t2884764
V12.2.2.37-20150827
【Model Name】
PF500KL
【Release Date】
2015/09/15
【Release Note 】
1 Enhanced system performance
2 Improve compatibility of SIM card
3 Improve quality of communication
4 Fix system UI virtual key issue
5 Fix external storage path issue
I have a PadFone S and when I went to check for a system update it began downloading.
Wonder if it fixed the tablet charging phone. Can't seem to install this if you have root. Anyway to install it or wait for the full zip on asus website to update?
Wait unless someone pulls the OTA update link. The update was only 66mb
Thanks for the heads up, we should be able to just flash the full firmware here: http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-12.2.2.37-user.zip
Did anyone successfully install this update, just by flashing from the asus website?
If so, is everything great?
Justatechie said:
Did anyone successfully install this update, just by flashing from the asus website?
If so, is everything great?
Click to expand...
Click to collapse
Omg, I didn't think it was possible but it looks like Asus added even more bloat to this update. Spent the last half hour deleting stuff! Overall though, it seems smoother and uses a little less ram at the start. Not a bad upgrade if you root and uninstall a bunch of useless Asus apps.
beserker15 said:
Omg, I didn't think it was possible but it looks like Asus added even more bloat to this update. Spent the last half hour deleting stuff! Overall though, it seems smoother and uses a little less ram at the start. Not a bad upgrade if you root and uninstall a bunch of useless Asus apps.
Click to expand...
Click to collapse
What more could they possibly add, I thought this was already enough lol.
I didn't update it yet but I will once its fully charged and set up.
Afterwards I will check everything, it raises a serious question what happens when I update the remove the bloatware after using root.
Im hoping everything would be alright until cyanogen gets tablet support.
Kingroot can't root the phone on this update. Any other method to root?
Justatechie said:
What more could they possibly add, I thought this was already enough lol.
I didn't update it yet but I will once its fully charged and set up.
Afterwards I will check everything, it raises a serious question what happens when I update the remove the bloatware after using root.
Im hoping everything would be alright until cyanogen gets tablet support.
Click to expand...
Click to collapse
Yeah what sucks is since we don't have a ROM, flashing this full install adds back all of the bloatware I removed from the last update. What I did after updating was get Titanium Backup on there and just delete a bunch of Asus apps that I don't need, looking at you Clean Master. After doing that, restart the phone and the Playstore will no longer want you to update the apps you've removed.
Linux4ever85 said:
Kingroot can't root the phone on this update. Any other method to root?
Click to expand...
Click to collapse
You updated via TWRP recovery right? If so, just flash Super SU. No reason to use Kingroot at all on this phone.
beserker15 said:
You updated via TWRP recovery right? If so, just flash Super SU. No reason to use Kingroot at all on this phone.
Click to expand...
Click to collapse
I don't have TWRP since my phone is a plus. I am not sure if the method will work as the same for regular S model.
I have a stock PadFone s plus so I updated via ota. But my daughter has my old PadFone X that converted to S I flashed the new update via twrp via adb fastboot
beserker15 said:
Yeah what sucks is since we don't have a ROM, flashing this full install adds back all of the bloatware I removed from the last update. What I did after updating was get Titanium Backup on there and just delete a bunch of Asus apps that I don't need, looking at you Clean Master. After doing that, restart the phone and the Playstore will no longer want you to update the apps you've removed.
Click to expand...
Click to collapse
I just flashed the update via twrp, I didnt see new bloatware added to my system, I even checked all apps and the only thing new and welcoming is padfone station assistant.
I had cm 12.1 installed before I had converted this device into a padfone s, and it was fast zippy and clean and you never had to worry about system memory like you do on the asus fws. The only way I will keep cm is when it supports the docking station.
This update made my phone quite fast and antutu is showing scores of 47,193 making it faster than the zenfone 2. Wow.
Justatechie said:
I just flashed the update via twrp, I didnt see new bloatware added to my system, I even checked all apps and the only thing new and welcoming is padfone station assistant.
I had cm 12.1 installed before I had converted this device into a padfone s, and it was fast zippy and clean and you never had to worry about system memory like you do on the asus fws. The only way I will keep cm is when it supports the docking station.
This update made my phone quite fast and antutu is showing scores of 47,193 making it faster than the zenfone 2. Wow.
Click to expand...
Click to collapse
I am going to test this when I get the update installed.
I have a PFX converted to PFS LP. I downloaded the Zip then transferred to the phone. It automatically detected the update file and installed without issue, just waiting for the "Android is Upgrading" to finish. Then I will post back with Antutu scores. I will of course debloat and reboot prior to running Antutu. I only wish I had thought to run Antutu prior to updating for comparison.
Update:
I got an Antutu score of 44182. A bit lower than the above mentioned. I will do some tweaks to attempt to raise the score.
45889 was the best I was able to get. Are you doing anything special with settings on your phone, Justatechie?
Just tried Kingroot and was able to root my phone. Then used super sume to remove the Kingroot and put super su for root. I used the latest Kingroot apk.
daggorlad said:
I am going to test this when I get the update installed.
I have a PFX converted to PFS LP. I downloaded the Zip then transferred to the phone. It automatically detected the update file and installed without issue, just waiting for the "Android is Upgrading" to finish. Then I will post back with Antutu scores. I will of course debloat and reboot prior to running Antutu. I only wish I had thought to run Antutu prior to updating for comparison.
Update:
I got an Antutu score of 44182. A bit lower than the above mentioned. I will do some tweaks to attempt to raise the score.
45889 was the best I was able to get. Are you doing anything special with settings on your phone, Justatechie?
Click to expand...
Click to collapse
I did it from a cold boot, when it first starts up, cleared the RAM using that booster utility and achieved a score of over 47,000k. After that the score averages down to 45,000 and the more benchmarks you are doing in a short time the lower score would be due to thermal throttling I assume. And I forced stopped some running services that would automatically start up to achieve the best score possible.
I removed most of the bloatware that I considered useless and just kept the ones that were useful for me.
The original lollipop update gave me a 47k, the second update made it slower towards 43k, then this update touches 47k again. (I'm starting to think that this is too high for a snapdragon 800 processor,because the rest of the snapdragon 800 devices just touch 40k)
I have also noticed that when I dock it to the tablet, its loads up faster than other updates.
Usually I have to wait like 3-5 seconds until the launcher could display the apps or using dynamic display.
daggorlad said:
I am going to test this when I get the update installed.
I have a PFX converted to PFS LP. I downloaded the Zip then transferred to the phone. It automatically detected the update file and installed without issue, just waiting for the "Android is Upgrading" to finish. Then I will post back with Antutu scores. I will of course debloat and reboot prior to running Antutu. I only wish I had thought to run Antutu prior to updating for comparison.
Update:
I got an Antutu score of 44182. A bit lower than the above mentioned. I will do some tweaks to attempt to raise the score.
45889 was the best I was able to get. Are you doing anything special with settings on your phone, Justatechie?
Click to expand...
Click to collapse
I have the Padfone X converted as well. getting around the same benchmark 45.7k the highest which is amazing to me. I was just wondering where u put the file for it to automatically detect it and what recovery are you using? I'm using twrp and ended up having to look up the zip file on my phone. I could download the ota update but once it rebooted to install it, it would just go into twrp recovery and i could not find where it downloaded the update on my phone that way.
russell.odell said:
I have the Padfone X converted as well. getting around the same benchmark 45.7k the highest which is amazing to me. I was just wondering where u put the file for it to automatically detect it and what recovery are you using? I'm using twrp and ended up having to look up the zip file on my phone. I could download the ota update but once it rebooted to install it, it would just go into twrp recovery and i could not find where it downloaded the update on my phone that way.
Click to expand...
Click to collapse
I downloaded using PC then just dropped it in the root of storage (not phone root, but top directory accessible using a PC).
So, In order to better prepare for the Nougat update whenever Lenovo/Motorola decided to give it's U.S. customers the official OTA, I had decided to Unroot my phone and install Stock firmware official version .64. Went through all the steps, got a No command error screen when trying to get to recovery, also showed Modified in FastBoot mode. Also, I had decided to do this because I was having some irritating Error Report issue always downloading.
Anyway, I learned that I can hold Power then press UP volume button once then release power to get to Recovery despite the "No Command" screen. Also, eventually that I needed to downgrade to .49, then accept the .64 OTA in order to get rid of the "Modified" message in Fastboot Screen. So, went through all the trouble to download the .49 firmware, flashed it, etc. When I got into my phone, I checked for Software updates as soon as I was able, to get the .64 update. But, lo and behold, instead I was gifted with a screen explaining that I would instead be getting Androud 7.0 Nougat. Awesome. I live in California. Was totally not expecting Nougat, because I check almost every day and would never get that long awaited message lol.
So I am surprised. I noticed, when I flashed straight to .64 firmware and checked for Software updates, I Did Not get the Nougat OTA notification. Only with the .49 firmware. I didn't think to take a screen shot, and am currently downloading the Nougat update now. When it is installed, I'll take a screenshot of the firmware version once booted into my phone. It's about time, I'm going to be ordering the G5 for my wife tomorrow, and was a tad bit jealous that it would already come with Android 7.0 lol. Hope this gets the rest of you American users excited, and hope this information helps. You can find a guide how to downgrade here in the forums or google, or at stechguide website. PS- I cannot guarantee nor take responsibility that you will have the same luck to get the OTA as I did. Downgrade at your own discretion.
Notice the firmware version. Joy!
I would have done this if I waited 2 weeks earlier. If more people get it and can confirm, just maybe I will unroot and go back to stock. But I love all the customizations with Resurrection Remix.
selw0nk said:
I would have done this if I waited 2 weeks earlier. If more people get it and can confirm, just maybe I will unroot and go back to stock. But I love all the customizations with Resurrection Remix.
Click to expand...
Click to collapse
Had to do a quick search on what Resurrection Remix was, very nice rom it seems!
Doukeyakusha said:
So I am surprised. I noticed, when I flashed straight to .64 firmware and checked for Software updates, I Did Not get the Nougat OTA notification. Only with the .49 firmware. I didn't think to take a screen shot, and am currently downloading the Nougat update now. When it is installed, I'll take a screenshot of the firmware version once booted into my phone. It's about time, I'm going to be ordering the G5 for my wife tomorrow, and was a tad bit jealous that it would already come with Android 7.0 lol. Hope this gets the rest of you American users excited, and hope this information helps. You can find a guide how to downgrade here in the forums or google, or at stechguide website. PS- I cannot guarantee nor take responsibility that you will have the same luck to get the OTA as I did. Downgrade at your own discretion.
Click to expand...
Click to collapse
I too didn't get an OTA update notice when I went back to .64 stock/unrooted . So I said the heck with it and went back to Invicta and will stay there. I ran stock nougat flashed via the TWRP flashable files that were available for a while. But when the rubber meets the road, I see no advantages to going through the hassles of downgrading my phone to stock anything given that the features, performance, stability and battery life are far better on various custom ROMS. Not to mention that the security is more up to date. Just my own opinion.
hmmmm..interesting...tempted to try this out
My phone is too new to be rooted (sorry, I no longer do that first day...) After seeing the earlier posts I checked last night, no luck.
Today is another day! New version installing now. NPJ25.93-14 just said, "Hello, Moto". Woohoo!
Peace,
Tom
OTA zip
Does anyone have the OTA files? I suspect I will have to manually flash the files in Fastboot due to earlier impatience (I did nougat soak test and then downgraded back to stock). Now the regular ota keeps giving me error which I am assuming is tied to the gpt.bin error I got when I downgraded. I can't do anything scripted. Gotta install manually from fastboot.
Just for your info... The Amazon ad remover doesn't work after the update. XT1625
Downloading in Austin Texas
Sent from my Moto G (4) using XDA-Developers Legacy app
Has anyone made an image as I need it to unbrick my phone?
Amston said:
Has anyone made an image as I need it to unbrick my phone?
Click to expand...
Click to collapse
My wife's just got the update. Mine is unlocked and rooted. If someone can tell me the steps to get back to a position to download the ota, and root again, and pull the image, I'll happily do it. I'm on .48 right now. Looks like I need to relock the bootloader and reload .48 fresh, but I'm not real sure at this point.
downloaded and installed. startup animation was fun. anyone know how to root this build?
fredwinky said:
downloaded and installed. startup animation was fun. anyone know how to root this build?
Click to expand...
Click to collapse
I dunno. Try searching the G4+ forum? There is a post that tells you how.
I got the update before the weekend and installed it. Everything went smooth and the changes are very nice. I've noticed the Bluetooth issues I had seem fixed (dropping connections, having to de-pair, power cycle and re-pair). However, one annoying thing still persists and it seems related to Do Not Disturb. Sometimes the audio never comes back after DND. Notifications, touches, calls, they're all silent after DND is turned off. I have to power cycle the phone and then it works. I had this issue on Marshmallow and Motorola advised me to wipe & reset. That took care of the issue but it seems to have come back for now. No other issues that I can find right now.
The only thing I've noticed is with my wifi . Every now and then it doesn't auto connect when returning home. This was reported by a number of people during the soak test but I guess it wasn't important enough because the OTA was released anyway. Also, I previously had the option of connecting with 2.4GHz, 5GHz, or auto. Now there is no option and I've noticed that sometimes I'm connected with 2.4 and sometimes with 5 but it seems to be random.
Sent from my SM-T530NU using Tapatalk
fredwinky said:
downloaded and installed. startup animation was fun. anyone know how to root this build?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3484672
Has the instructions to root.
Sent from my Moto G (4) using Tapatalk
I'm new to this phone Can anyone give me a link to the ".49 firmware"
I ordered this phone as an early xmas gift for my mother during black friday, got it for $115 32gb unlocked from B&H Photo. Just wanted to mention as a current Nexus 6 owner I'm surprised how this phone is basically pure android with the exception of 2 Moto apps. I was able to upgrade from 6.0 to Nougat out of the box and then the security patches without any issues. Once all updates were done I just erase the device to factory and setup as expected. Jealous it's running faster than my Nexus 6 (and I'm running performance mode using ex kernel manager). Only wish Motorola can reboot the nexus 6 with a bigger screen and fingerprint.
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
draqkin said:
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
Click to expand...
Click to collapse
I have exactly same phone (c185) never tried unlocking bootloader but I updated to emui 9 159 there are some buggy things like when you want to use third party lunchers You can't use gesture navigation and it has so many bugs so not using gesture is better
there are again some problems with third party launchers (im using nova) like sometimes when you go to "resents" its totally blank and you have to force stop "huawei home" to make it right
there are some good changes in camera like new 960 fps slow motion (but there is a huge crop in 240fps 720p and 960fps 720p I can't remember that 240fps had that crop or not) Turning off master ai and some new scene detection but it's slower than last one
there is a new performance mode that i love using it (it feels like a real flagship however it's not because of stupid SOC)
there is a new AI api that android 8 didn't have so most of apps wasn't able to use NPU
in emui 8 there is a little bit better battery
I love changes to my phone so I preferred buggy new firmware to old ones there are so many good little changes in interface (like when you take a picture you can go to gallery then scan it for QR code)
There is a way better Mira cast functionality (and new desktop mode in it)
hi touch, hi vision
These were all expensives I had with emui 9 that I can think of
How did you update @arianamirgholami ?
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Same here, although my brother and I have the same device (ALP-L29C185) and we're on the same career, he got the pie update like a month ago and nothing for me yet. I think it's a matter of time until our imeis turns.
MasterThiefGarrett said:
How did you update @arianamirgholami ?
Click to expand...
Click to collapse
I used Erecovery of firmware finder
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Fazee99 said:
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Click to expand...
Click to collapse
I finally got the OTA update from EMUI 8 to EMUI 9
curgervending said:
I finally got the OTA update from EMUI 8 to EMUI 9
Click to expand...
Click to collapse
Thats great. Means you got more luck. Mine is still on 9.0.0.159 and no update. Please also confirm one thing. What is android security patch in this version?
Finally grab the update today morning...
Another update today. Woww