After unlocking bootloader and rooting, i tried installing xposed. App installed fine but after installing framework it just bootlooped on the huawei logo. Did factory reset via twrp, it booted fine, but not on the first try.
Then i did something even dumber: flashed custom rom. To be exact it was openkirin rom.
Worked without problem but i didn't like some things. Now comes the worst part: couldn't boot back to stock.
Flashed system, ramdisk and recovery but no dice.
Tried sdcard update with + - power combo. Says software install failed after 5%.
Even bought the bloody dc phoenix, flashed update but it just throws me in recovery. If i do factory reset, it stays at 0% for a long time. Last option would be to leave it overnight on factory resetting.
Any further insight in this problem would be helpful coz i'm running out of ideas.
I'm not an expert but if no one has any suggestions for you then Funky Huawei can fix this but it's quite an expensive solution.
https://funkyhuawei.club/
ok, so a little update. seems like the site i tried to download firmware from had messed up the versions. flashed 121 version, got 161, and that one got me up and running but wifi is dead. doing looong factory reset. will update further.
site's name is huawei - firmware dot com, for anybody looking into downloading from them
jasonleeg said:
I'm not an expert but if no one has any suggestions for you then Funky Huawei can fix this but it's quite an expensive solution.
https://funkyhuawei.club/
Click to expand...
Click to collapse
those guys are expensive as heck! dc phoenix is much more decent with prices and you get better deal for your money if you find yourself go that route ofc
Two things:
Xposed v90 beta 4 is compatible with EMUI and a download link / discussion can be found here. Beta 3, which might still be the latest official version, will cause a bootloop. This should be stickied somewhere.
Getting back to stock can be a ****. I don't know if stock eRecovery might work now that official updates are available? Funky Huawei's eRecovery method works - but yeah, it's expensive. Their unbrick method does not work (or did not work for me), and I'm not sure if DC will work either.
thref23 said:
Two things:
Xposed v90 beta 4 is compatible with EMUI and a download link / discussion can be found here. Beta 3, which might still be the latest official version, will cause a bootloop. This should be stickied somewhere.
Getting back to stock can be a ****. I don't know if stock eRecovery might work now that official updates are available? Funky Huawei's eRecovery method works - but yeah, it's expensive. Their unbrick method does not work (or did not work for me), and I'm not sure if DC will work either.
Click to expand...
Click to collapse
in the end i managed to return to stock. and no swear words can describe the feeling of the whole process. i would rather have kidney stones again then restore my tablet again to stock.
and yeah, DC worked. flashed b121 version. it booted but no wifi or bluetooth. connected to hisuite and then updated to b181, latest version. now is the time to try xposed again when i still have some time with DC phoenix
Is your bootloader unlocked and OEM Unlocked via Device Settings? If so, I might be able to help you. PM me in this case.
I flashed by accident a Chinese Rom and messed up my system, was able to recover and flash stock.
Sent from my HTC U12+ using Tapatalk
Related
Hey friends, I am very new to the rooting scene. I have a at&t htc m8 and i made the mistake of trying to root the fast and easy way. I followed a guide by a user names Unlocker. I would post the link but am unable to at this current time because i am new here
That has it's readers use hasoon2000's all in one toolkit. Well I think I screwed up in that process. when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. So naturally I freaked out tried my best to unroot the damn thing by following a guide created by the same guy after he got many complaints of issues
Naturally I had problems with this aswell. Now where i'm at, at this current moment is
**tampered** ***unlocked**
I successfully (i think) removed super su and did my best to get back to stock firmware. well I failed at that aswell. I still have TWRP on my phone and managed to get security turned back on.
What I am asking is for any references or maybe even some fresh help on how i can either get my phone back to stock firmware so i can take the OTA updates and be on my merry way or maybe reccomend a custom rom I can use that has the new lolipop software.
Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM. I feel pretty helpless right now but if i can get some instruction I know I will be able to figure this out.
I'm still really new to this also, but I'll try my best (just take everything I say w/ a grain of salt...):
Krob189 said:
... when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. ...
Click to expand...
Click to collapse
Do you mean that you'd successfully done whatever you were doing and this was happening in normal use? AFAIK it is normal for the the screen to power off during long-running TWRP actions, and power button wakes it up.
Krob189 said:
...
I successfully (i think) removed super su and did my best to get back to stock firmware. well I failed at that aswell. I still have TWRP on my phone and managed to get security turned back on.
Click to expand...
Click to collapse
Which firmware do you have on it now? Do you have ADB installed? If so, it might be helpful if you post the output of the command
Code:
fastboot getvar all
. If not, I think you'll need ADB and fastboot to help recover.
Krob189 said:
...Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM ...
Click to expand...
Click to collapse
AT&T uses GSM. The GSM version should be correct. Depending on the firmware you have installed, specific versions of twrp may not work. In my case, twrp 2.8.4.0 wouldn't work on AT&T's stock 4.4.2 firmware, but would on the 4.4.4 firmware.
EDIT: Did you make a TWRP backup before attempting these changes? Depending on the state of your firmware, restoring that might be enough to fix things.
AT&T Stock 4.4.4 RUU
This should solve your problem, if you can achieve s-off again:
AT&T Stock 4.4.4 RUU
Krob189 said:
That has it's readers use hasoon2000's all in one toolkit. Well I think I screwed up in that process. when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. So naturally I freaked out tried my best to unroot the damn thing by following a guide created by the same guy after he got many complaints of issues
Click to expand...
Click to collapse
All the panic is for nothing. Its normal for the TWRP screen to appear for a brief moment when the device is powered off, and you connect the charger. At least on older versions of TWPR (and the version installed by Hasoon's toolkit is quite old).
Krob189 said:
Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM. I feel pretty helpless right now but if i can get some instruction I know I will be able to figure this out.
Click to expand...
Click to collapse
The TWRP version you want is the GSM. All versions of the M8 are essentially the same (and considered "GSM") except for the CDMA (Sprint & Verizon) and dual SIM variants.
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
brasticstack said:
Do you mean that you'd successfully done whatever you were doing and this was happening in normal use? AFAIK it is normal for the the screen to power off during long-running TWRP actions, and power button wakes it up.
Click to expand...
Click to collapse
What the OP is describing was a known bug, and happened when outside of recovery and while the phone was powered off (and while connecting the charger).
Wow thank you for fast responses!
So from my understanding I have a outdated TWRP version. I suppose I need to read up on how to update this and also how to flash a new rom. I only rooted my phone so I could pair up my ps3 controller to my phone so I can play games on it. I regret doing it now to be honest because I have modded my 3ds to play the same games i was using on my phone
I would love to be on the lolipop update that launched yesterday I believe. Should I stick to a rooted rom or just flash a stock version? Can anyone recommend a good lolipop root that has some tweaks for battery life and overall performance?
Krob189 said:
So from my understanding I have a outdated TWRP version. I suppose I need to read up on how to update this and also how to flash a new rom.
Click to expand...
Click to collapse
Just get the latest version of TWRP from their website. As you are asking what version (CDMA vs. GSM) it sounds like you are already getting there.
It sounds like you have the version of TWRP that was installed by the toolkit. That version is many months old. But its a minor bug, anyway. How often do you charge the phone with it powered off, anyway. I also don't think you can do anything in TWRP in this condition (if a security risk is your concern). The TWRP appears for a split second, and that's it.
Krob189 said:
I would love to be on the lolipop update that launched yesterday I believe. Should I stick to a rooted rom or just flash a stock version? Can anyone recommend a good lolipop root that has some tweaks for battery life and overall performance?
Click to expand...
Click to collapse
Lollipop didn't launch for AT&T, its just a long-delayed 4.4.4 update for us. To update to 4.4.4, either return to stock ROM and stock recovery to get the OTA, or relock the bootloader and run the official RUU.
Lollipop (5.0) started to roll out for some Euro CIDs, and has been out for US Dev Edition for a while. But you can't get to Sense Lollipop unless you s-off (or until AT&T releases it).
Hi guys...quick question. I have a Huawei P8 that "used" to have Marshmallow Beta Rom installed. Long story short. Since there was no root I tried to revert back to stock with fastboot. Problem is when I tried to flash the B200 stock rom it got stuck on the last "sending" file for about half an hour (which normally takes about 3 minutes for full rom flash). Thought that I just unplug and try to reflash rom again(big mistake it seems but my last 2 phones were nexuses so I thought that it's impossible to actually brick your phone). Anyway...now I'm stuck on a bootloop with no way of entering recovery or the bootloader or fastboot, or anything else for that matter. The Vol+ - and Power combinations don't seem to be working. Any help would be greatly appreciated. Thanks
Check this thread:
http://forum.xda-developers.com/showthread.php?t=3260704
You will find a fix
30adi said:
Check this thread:
http://forum.xda-developers.com/showthread.php?t=3260704
You will find a fix
Click to expand...
Click to collapse
Yeah...already tried that. Eventually this morning, after countless tries I managed to flash the first firmware for our P8 which is a beta B030 version. Now technically the phone works..but I no longer have audio and device isn't getting recognised by the PC (though Fastboot works fine), therefore it must be a software issue. An hour ago I managed to flash B170 and even B200 but the audio issue and usb connection issue is still there. Kinda running on fumes here. Anyone has any other ideea if I should flash anything else. Mind you...I can only update via fastboot...Normal update methods do not work. Thanks
If you had marshmallow beta rom, there is a downgrade package. Have you used it? It's version B300
30adi said:
If you had marshmallow beta rom, there is a downgrade package. Have you used it? It's version B300
Click to expand...
Click to collapse
No...haven't used it. Got a link by any chance? I did a google search but the links were all dead. Thanks
UPDATE: Ok....found it...but I'm gonna need to extract it since local update isn't working. Will update. Bottom line...I messed up because I didn't do the research before trying to rollback to B200. Stupid me
You should go back to marshmallow and do a proper downgrade: B313 -> B300 -> B200
Check the thread, you have to downgrade via 3 button combination for B300, and 2 button combination for B200
B300 is the only proper downgrade package
Good luck!
30adi said:
If you had marshmallow beta rom, there is a downgrade package. Have you used it? It's version B300
Click to expand...
Click to collapse
Man...you're a life saver. That was totally it. Everything back in order now.. Hai sa traiesti
Doamne ajuta!!! Well done
The Sony Xperia Z2 tablet has got to be the most horrible device in android history to root or install a recovery on it. The process and the complexity of it is just horrible. You daren't ever make the slightest change to a rom or anything in twrp as it just screws everything up on this device. I can't count the amount of roms i've put on it just to totally trash the device and you have to start from scratch. Either you put a new rom on, it wipes the recovery, you have to piss about using flashtool to flash some other ftf on just to get into recovery, then you have to then flash another tft to get root, the list just goes on and on. I don't even know why sony mobile even bother offering the bootloader unlock option in the first place, it's an absolute nightmare. It's basically you can have root with the official stock firmware, if you want a custom rom spend the next 2 weeks trying to get supersu installed on it. The most horrible device I've ever come across.
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
BabelHuber said:
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
Click to expand...
Click to collapse
I've tried Carbon and would love to use it but it just screws up the tablet after install and recovery gets wiped so you can't even go back to restore a back up. You then have to reflash using Emma then back into flashtool to reflash the tft to get recovery to work again because flashtool ends up reporting back that the current tft is not compatible with the device. It's a finicky device to root. It's got to be the worst out of all android devices. E.g my Samsung s9 had it rooted and flashed with a custom rom in around 5 mins. No matter what firmware is installed. Sony decided that after 23.1.A.575 or whatever rooting was not possible after that. Also every method on here telling you how to do it is different to each other and inconsistant. I tried 23.1.A.575 root for UK and it would not allow for twrp to be booted into. I had to use xperiafirm to download the Taiwanese version so I could get the batch script to allow recovery so holding down power on volume down would allow twrp to load. It's just a painstakingly horrible device to root to get something so simple. But yes your right probably best time to get rid and something different. Sorry for the rant it's just been a frustration for me.
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
BabelHuber said:
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
Click to expand...
Click to collapse
I've followed so many without much success. I tried the solution by kulvertti to the letter and the tab was having non of it. I think the problem also is that a lot of the links are dead to the specific tft you need to download so getting the exact version is tricky. The only one that has worked for me is the Taiwanese rom then using the recovery script by danalec to get Marshmallow flashed which is what I'm running now. So I made a back up today and thought OK let me try carbon because I can get all the nice customization options like being able to choose a dark theme for the settings menu instead of piercing white. What is it with manufacturers wanna make every thing bright and painful on the eyes. Anyway downloaded gaps wiped system etc installed rom and once it loaded the system was all unstable and lost root and recovery. So I give up now and have to accept I can only have marshmallow on it.
Danalec has a very simple root method for Marshmallow in the general section. This is one of the best tablets out there by far. Build quality doesn't come close with other brands.
Hey Guys,
what do you think is the best costum rom (stable) for the Mate 10 pro?
Is it possible to flash it with Pie 9.0.161?
Thanks for Help :victory:
Just wait for the ota update to pie.
that's definitely a worse rom. i'm on it right now.
wooley4766 said:
Just wait for the ota update to pie.
Click to expand...
Click to collapse
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Pie Update
HauAbDuLauch said:
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Click to expand...
Click to collapse
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
revjamescarver said:
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
Click to expand...
Click to collapse
but no custom
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
93starletgt said:
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
mirandam said:
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
Click to expand...
Click to collapse
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
93starletgt said:
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
Click to expand...
Click to collapse
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
mirandam said:
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
Click to expand...
Click to collapse
Thanks! Last question. If I would like to go back to stock using the All In One Tool, how can I flash stock recovery? And where can I find it? Many thanks for your help.
are there custom roms for the huawei mate 10 pro??
cause cant find it on xda.
mine is stock it works but the no status bar pull down on lockscreen is anoying ;( sometimes and that only the stock sms app show on the always screen on...
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