Related
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
Hi guys,
I just f*** my phone!
I had updated my phone G5 RS988 unlocked edition in the version Rs98821b !
I wanted to downgrade it to the version RS98811c .
I installed lg drives , LGUP_Store_Frame_Ver_1_14_3.msi and uppercut !
I started uppercut loaded the kdz file and the phone was stuck at 5% on the screen or at 11% in the LGUP .
It gets out 10% error ERROR CODE: 0x2BC, Invalid command response code = 0x80000121.
I tried to reboot the device but it is stuck at the Firmware Update(Download Mode) .
Any suggestion ?
Maybe I need any other version of KDZ???
ok guys after some read I fixed the problem by installing the firmware "RS98810h_01_0303.kdz"
So now is possible to downgrade throught twrp or not?
searius said:
ok guys after some read I fixed the problem by installing the firmware "RS98810h_01_0303.kdz"
So now is possible to downgrade throught twrp or not?
Click to expand...
Click to collapse
You are now stuck on Brightpoint firmware that is not for the unlocked version. Your best bet is to follow the instruction on this thread.:
https://forum.xda-developers.com/lg-g5/development/stock-rs988-11c-rom-flashable-zips-imgs-t3612358
11D has the bootloader mode you can get that from here:
https://forum.xda-developers.com/lg-g5/development/stock-rs988-11d-rom-flashable-zips-imgs-t3623199
Don't forget to thank autoprime.
searius said:
ok guys after some read I fixed the problem by installing the firmware "RS98810h_01_0303.kdz"
So now is possible to downgrade throught twrp or not?
Click to expand...
Click to collapse
Hi! Thanks for the post!
I ran into exactly same problem. Any luck downgrading to RS98811c or getting rid of Brightpoint? I wasn't able to flash anything except for RS98810h_01_0303
searius said:
Hi guys,
I just f*** my phone!
I had updated my phone G5 RS988 unlocked edition in the version Rs98821b !
I wanted to downgrade it to the version RS98811c .
I installed lg drives , LGUP_Store_Frame_Ver_1_14_3.msi and uppercut !
I started uppercut loaded the kdz file and the phone was stuck at 5% on the screen or at 11% in the LGUP .
It gets out 10% error ERROR CODE: 0x2BC, Invalid command response code = 0x80000121.
I tried to reboot the device but it is stuck at the Firmware Update(Download Mode) .
Any suggestion ?
Maybe I need any other version of KDZ???
Click to expand...
Click to collapse
Did you ever get your phone fixed? I have the exact same problem. stuck on firmware update and lg up always stuck at 10 percent then error out. thanks
You might want to try flashing the ZIP/IMG
https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907
From TWRP
johnzenobia said:
Did you ever get your phone fixed? I have the exact same problem. stuck on firmware update and lg up always stuck at 10 percent then error out. thanks
Click to expand...
Click to collapse
Yes bro I fixed it.
But I dont remember very much.
What I did was to install again the same firmware that was the phone not to try to downgrade and after it I install the downgrade version through TWRP.
But I am not sure for this because has passed more then 8 months.
wolfu11 said:
You are now stuck on Brightpoint firmware that is not for the unlocked version. Your best bet is to follow the instruction on this thread.:
https://forum.xda-developers.com/lg-g5/development/stock-rs988-11c-rom-flashable-zips-imgs-t3612358
11D has the bootloader mode you can get that from here:
https://forum.xda-developers.com/lg-g5/development/stock-rs988-11d-rom-flashable-zips-imgs-t3623199
Don't forget to thank autoprime.
Click to expand...
Click to collapse
Hi Brother,
I have and LG G5 RS988 (Full Stock + No Root), so it was in RS988 21D Andorid 7.0 Firmware
I wanted to downgrade it, so I downloaded RS988 11C Android 6.0 KDZ file and tried to flash it through LG UP but it stucked at 10% and gave an error, and device was soft bricked So, I had to download the RS988 10H Brightpoint firmware which luckily got me out of bricked state and firmware is running fine, But i did some research and got to know that I cannot unlock my bootloader in this Brightpoint firmware..
So now i want to unlock my bootloader, what should I do now or is there any way to somehow go to RS988 11C ????
perniteo said:
Hi! Thanks for the post!
I ran into exactly same problem. Any luck downgrading to RS98811c or getting rid of Brightpoint? I wasn't able to flash anything except for RS98810h_01_0303
Click to expand...
Click to collapse
Hi Bro!
Were U able to get rid of Brightpoint or able to downgrade to RS98811c??
HyperXG said:
Hi Brother,
I have and LG G5 RS988 (Full Stock + No Root), so it was in RS988 21D Andorid 7.0 Firmware
I wanted to downgrade it, so I downloaded RS988 11C Android 6.0 KDZ file and tried to flash it through LG UP but it stucked at 10% and gave an error, and device was soft bricked So, I had to download the RS988 10H Brightpoint firmware which luckily got me out of bricked state and firmware is running fine, But i did some research and got to know that I cannot unlock my bootloader in this Brightpoint firmware..
So now i want to unlock my bootloader, what should I do now or is there any way to somehow go to RS988 11C ????
Click to expand...
Click to collapse
Wow sorry it's been years. I think your best bet is to follow that link that you "d me on and go to 11D cause that has the boot loader mode but it's been so long Not sure they're still available sorry.
wolfu11 said:
Wow sorry it's been years. I think your best bet is to follow that link that you "d me on and go to 11D cause that has the boot loader mode but it's been so long Not sure they're still available sorry.
Click to expand...
Click to collapse
Thanks for answering bro, I've solved my issue.........
I had the LG V10 with Android 6 rooted and I upgraded it to Nougat by flashing the kdz version 30b with the already installed TWRP. For various reasons, I had to reinstall the stock version of the OS (30b), which removed TWRP from the phone. Now, I want to reinstall TWRP to root it again. Currently, I have the 30c version (updated from 30b with the false hope that the below problem would be fixed) with the bootloader unlocked. However, when I try to flash the TWRP image file (or any recovery images, even the stock recovery image), I always receive the following error:
Code:
fastboot flash recovery twrp-3.0.0-0-h901.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.194s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.212s
I tried also to restore the rooted Android 6 KDZ (which did not gave me the above problems) using LGUP but it tells me that there is an "antirollback" problem because the version I want to install is older than the one I have. Then I tried to install the TWRP TOT file with LGUP but it gives me a communication error when it starts upgrading.
I think the solution would be to rollback to Android 6, install TWRP with fastboot working, then flash the rooted Nougat again. However, I cannot find how to rollback to an older Android version without TWRP and I cannot install TWRP with the current Android version. In practice, I am in a loop...
I don't know what else to do. Any help on how can I root my phone now?
@brok85
The simple fastboot commands for installing custom recovery were patched out sometime in the later MM firmwares. Since you lost root on Nougat, there currently is no option to get TWRP since there is no way to downgrade to any version of MM even with a modified LGUP.
If and when such a downgrade is possible you'd probably have to roll-back to 30b first instead of going to straight to MM.
chin'ah.girl said:
@brok85
The simple fastboot commands for installing custom recovery were patched out sometime in the later MM firmwares. Since you lost root on Nougat, there currently is no option to get TWRP since there is no way to downgrade to any version of MM even with a modified LGUP.
If and when such a downgrade is possible you'd probably have to roll-back to 30b first instead of going to straight to MM.
Click to expand...
Click to collapse
I have already rolled back to 30b. Antirollback check passes successfully as long as you want to flash the same Android version, e.g., Android 7...
Wouldn't it be possible to modify the 30b so that we can get those fastboot commands back? that would fix the problem without need to roll back to MM...
Unfortunately we can't modify fastboot commands at the ROM level because we have no way of flashing a modified ROM to the device that would allow the commands to go through. If we were it would be even more simple to flash a pre-rooted ROM through LGUP, but that has already been confirmed not to work as well.
So basically it's either downgrade or exploit a security flaw that allows root on the current ROM, and since no one is currently working on this device (at least to my knowledge) both of those are starting to look less and less likely.
brok85 said:
I have already rolled back to 30b. Antirollback check passes successfully as long as you want to flash the same Android version, e.g., Android 7...
Wouldn't it be possible to modify the 30b so that we can get those fastboot commands back? that would fix the problem without need to roll back to MM...
Click to expand...
Click to collapse
If your on 30b then the dirty cow exploit works, search this forum for it.
Sent from my LG-H901 using XDA Labs
skywalker-live said:
If your on 30b then the dirty cow exploit works, search this forum for it.
Sent from my LG-H901 using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion! Would you please link a reference for dirty cow? I found something in the forum but I also read that someone bricked their devices, so it would be better to have the correct procedure.
That information is incorrect, unfortunately. Dirty Cow was patched out in January 2017, the 30b ROM is on May 2017 security patch. I even tried to do it myself and the "adb logcat -s recowvery" command no longer works, hence the reason why we need to downgrade to v20l for the exploit.
chin'ah.girl said:
That information is incorrect, unfortunately. Dirty Cow was patched out in January 2017, the 30b ROM is on May 2017 security patch. I even tried to do it myself and the "adb logcat -s recowvery" command no longer works, hence the reason why we need to downgrade to v20l for the exploit.
Click to expand...
Click to collapse
Except for the fact that 30b increased the anti rollback and we can't go back to 20l.
Sent from my LG-H901 using XDA Labs
@skywalker-live
I'm not entirely certain that's the problem. Any time you flash a ROM with a lower anti-rollback count usually results in a hard brick/9008 mode, not a soft brick. The few times I was able to successfully flash the device that was what happened and the phone was easily recovered from a soft brick with LGUP or LG Bridge. That is unless LG developed away for the bootloader to not be so stringent for easier recovery and less phones needing to be sent back to the factory. Also I believe the G5 was able to downgrade between MM and N.
Either way for us users who intentionally/unintentionally upgraded and lost root we don't have any options at the moment.
@chin'ah.girl. That is the whole point of anti roll back, to prevent going backwards, in this case it closes the last exploit used for rooting. This phone started with full fastboot capability on android 5.1.1. (yay we did everything like normal dev phones) Then with 6.0 LG removed fastboot flashing commands (unlocked bootloader that can't do anything), the dirty cow exploit gave us temp root to install twrp. There were 3 updates for the h901 in 6.0. The first 2 were ARB 0, the 3rd ("security" update) increased ARB to 1. Then 7.0 came and ARB increased to 2, because LG patched dirty cow. In a way ARB is designed to brick your phone if you force it, sure our phones are recoverable but only with the same version you started with. On newer LGs (v20? and newer) it just warns you and won't let you downgrade. I've looked back at all the posts from when 7.0 (30b) was released and anyone on unrooted, untwrped software has been stuck there. The only way to have root/ twrp on 30b is to have flashed a safely created stock rom in twrp. Even the best devs for this phone are stuck on 30b. I'm even looking at different brands unless someone can root the latest LG firmwares ( I would like a v20 but all my local stores only have the latest firmwares in stock).
Sent from my LG-H901 using XDA Labs
Well I guess having a soft brick with anti-rollback is better than having 9008 (I know it's also possible to recover from this mode but much more work is involved). I definitely know that currently no one has made progress because I'm one of the people in those threads. Haha!
So I guess that leaves us with hoping someone finds an exploit in current firmware...or buying a new phone like you suggested.
OOOHHHHH NO.. i just got my v10 today hoping to root and all but it's in 30c already.. and from what i have been reading in this thread... sounds like i'm doomed.. i have never used a phone without root...... unlucky me... my love for v10 got me in trouble........
skywalker-live said:
@chin'ah.girl. That is the whole point of anti roll back, to prevent going backwards, in this case it closes the last exploit used for rooting. This phone started with full fastboot capability on android 5.1.1. (yay we did everything like normal dev phones) Then with 6.0 LG removed fastboot flashing commands (unlocked bootloader that can't do anything), the dirty cow exploit gave us temp root to install twrp. There were 3 updates for the h901 in 6.0. The first 2 were ARB 0, the 3rd ("security" update) increased ARB to 1. Then 7.0 came and ARB increased to 2, because LG patched dirty cow. In a way ARB is designed to brick your phone if you force it, sure our phones are recoverable but only with the same version you started with. On newer LGs (v20? and newer) it just warns you and won't let you downgrade. I've looked back at all the posts from when 7.0 (30b) was released and anyone on unrooted, untwrped software has been stuck there. The only way to have root/ twrp on 30b is to have flashed a safely created stock rom in twrp. Even the best devs for this phone are stuck on 30b. I'm even looking at different brands unless someone can root the latest LG firmwares ( I would like a v20 but all my local stores only have the latest firmwares in stock).
Sent from my LG-H901 using XDA Labs
Click to expand...
Click to collapse
What is the difference between a rooted .kdz and a rooted .img?
We can flash a .kdz with LGUP so we would not need the TWRP in the first place. Why is not possible to build a rooted version of the 30b and generate a .kdz to flash with LGUP?
It is probably a stupid question but I am kind of ignorant in this matter...sorry for any blasphemy I may have involuntarily said above
brok85 said:
What is the difference between a rooted .kdz and a rooted .img?
We can flash a .kdz with LGUP so we would not need the TWRP in the first place. Why is not possible to build a rooted version of the 30b and generate a .kdz to flash with LGUP?
It is probably a stupid question but I am kind of ignorant in this matter...sorry for any blasphemy I may have involuntarily said above
Click to expand...
Click to collapse
Unfortunately those that are working to patch lgup to flash rooted .kdz's are still unsuccessful. But that has been everyone's hope for quite a while. Injecting root into a .kdz changes its signature, and then lgup fails to flash it.
Sent from my LG-H901 using XDA Labs
@chin'ah.girl if @ PlayfulGod is working on this let me know. I helped back in the day getting the lg flex running twrp. Yall might want to look into flashing a modified bootloader from a phone that is equal. Like we used the G2 aboot to bypass lgup errors it and got loki working. But then lg wouldnt not rls the source so we could get a stable kernel. But we did end up having twrp and root. . Check the aboot file. I will see if @djrbliss or maybe @Dees_Troy will jump in here and see what happens. idk how close the aboot is to the v20 or sense there was a working aboot for this phone you might be able to force a older aboot. it might softbrick but then you should be able to use fastboot cmds. hope this helps. Inbox me if you need. If I can find the old aboot file that worked I will play around with it
Gotroot said:
@chin'ah.girl if @ PlayfulGod is working on this let me know. I helped back in the day getting the lg flex running twrp. Yall might want to look into flashing a modified bootloader from a phone that is equal. Like we used the G2 aboot to bypass lgup errors it and got loki working. But then lg wouldnt not rls the source so we could get a stable kernel. But we did end up having twrp and root. . Check the aboot file. I will see if @djrbliss or maybe @Dees_Troy will jump in here and see what happens. idk how close the aboot is to the v20 or sense there was a working aboot for this phone you might be able to force a older aboot. it might softbrick but then you should be able to use fastboot cmds. hope this helps. Inbox me if you need. If I can find the old aboot file that worked I will play around with it
Click to expand...
Click to collapse
As far as I know no one is working on this as it seems most devs have given up and have moved onto the v20, or if they are working on it they haven't said so in the forums that I've seen. With that in mind help from anyone would be greatly appreciated, even if it is a long shot!
The aboot from the v20 might work.. It just need to be edited. I have played around with downgrading. Idk why lg seems to do this with certain models. The flex was a beast of a phone still is. But they wouldnt rls the scource kernel. Lg said they did but it wouldnt compile it was missing all kinds of drivers. Lg has lost all my respect
Any hope on rooting stock Nougat now? My V10 bootlooped and I sent it into LG and of course they flashed stock Nougat recovery so my TWRP is gone.
xxcmb3k3xx said:
Any hope on rooting stock Nougat now? My V10 bootlooped and I sent it into LG and of course they flashed stock Nougat recovery so my TWRP is gone.
Click to expand...
Click to collapse
Welcome to the train bro,..... None for now...
skywalker-live said:
@chin'ah.girl. That is the whole point of anti roll back, to prevent going backwards, in this case it closes the last exploit used for rooting. This phone started with full fastboot capability on android 5.1.1. (yay we did everything like normal dev phones) Then with 6.0 LG removed fastboot flashing commands (unlocked bootloader that can't do anything), the dirty cow exploit gave us temp root to install twrp. There were 3 updates for the h901 in 6.0. The first 2 were ARB 0, the 3rd ("security" update) increased ARB to 1. Then 7.0 came and ARB increased to 2, because LG patched dirty cow. In a way ARB is designed to brick your phone if you force it, sure our phones are recoverable but only with the same version you started with. On newer LGs (v20? and newer) it just warns you and won't let you downgrade. I've looked back at all the posts from when 7.0 (30b) was released and anyone on unrooted, untwrped software has been stuck there. The only way to have root/ twrp on 30b is to have flashed a safely created stock rom in twrp. Even the best devs for this phone are stuck on 30b. I'm even looking at different brands unless someone can root the latest LG firmwares ( I would like a v20 but all my local stores only have the latest firmwares in stock).
Click to expand...
Click to collapse
Among the marshmallows for H901, I have seen 20e, 20j and 20l here. And I have myself seen that 20e is on ARBv1 while 20j and 20l are on ARBv2 just like 30b and 30c. So 30b and 30c must be downgradable to 20j or 20l via LGUP due to having the same ARB version i.e. 2.
You can yourself verify the ARB versions by extracting the KDZ, then DZ and then searching for SW_ID in either ABOOT or SBL1 partition images. They both contain the same string whose 8th-last digit shows the ARB version of that KDZ.
I have tried flashing 20j and 20l on my h901 30b via LGUP. All checks pass as well as many partitions including modem, boot, laf, factory, recovery, aboot etc. are flashed but on 23% while flashing system partition the 0x2000 Invalid Command Response is shown by LGUP. Can anyone please try this downgrade and let me know what they get?
Would it be due to the reason that I am flashing H901BK files over H901?
as the title says.
I flashed official b360 oreo using oldroid's guide, which worked, i however lost HW keys.
I then flashed the oreo TWRP (3.1.1-1) to reecovery_ramdisk_a.
then re-flashed oreo nocheck recovery.
Then flashed AOSP oreo sysem.img.
still no HW keys.
My IMEI is now approved for official b360 install, so i want to downgrade, get back HW keys and install b360.
ive tried dload method, get install error - so cant do that.
I cant seem to get back to the stock system.img as i get transfer failed in fastboot if i try to re-flash it.
since im not on stock system.img, i cant do the method listed by oldroid in his rollback guide as i think flashing oreo twrp messed stuff up.
obviously cant use FF as the AOSP updater doesn't detect the update.
so im pretty much stuck? iv'e spent the last 5 hours trying to get this to work, with no hope.
iv'e never had a problem like this with a phone!
HELP!!!!!
Find the B120 guide. That's the only way I know how to get the the keys back.
Sent from my STF-L09 using Tapatalk
tried that, unless there is another one, link?
Try this new hwota to rollback from oreo to nougat. Downgrade to B120 will get you back your buttons.
https://forum.xda-developers.com/showthread.php?p=75662105#post75662105
checking now, hope it works, step 1 was a success, so lets hope step 2 works
ok, back on stock oreo me thinks, although bootloop, i'll try factory reset and cache wipe
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