Database Info

EMUI 9 Stable is now available for M5

As the tiltle said, ive seen the 9.0.155 firmware for all M5 Devices, which means that it might take max. 1 month to be downloaded from ota.
See the screenshot below in the attachment
Update 1: the chinese firmware which is C00 might get merged with the other regions firmware, which means that we might get the advantages of the chinese Firmware (e.g. online themes in theme app, .......)
By the way, this update does support Full screen gestures, i saw it after unpacking the firmware
Note: if you want to flash the firmware using flashy, DONT AND NEVER EVER using eRecovery to downgrade as this will COMPLETELY destroying your device, just do not downgrade for now
Update: EMUI 9 is officially start rolling out, some people already received it through HiCare app, All credits go to @sz.hatef's for this announcement.

Woww great news!! Thanks for sharing!!

Not showing up on my SHT-W09C567. Still waiting for 8.0.0.196 to be approved.
When EMUI 9 is released should we be able to root in the usual fashion?

Tool Belt said:
Not showing up on my SHT-W09C567. Still waiting for 8.0.0.196 to be approved.
When EMUI 9 is released should we be able to root in the usual fashion?
Click to expand...
Click to collapse
Yes, through Fastboot mode as Magisk 18.1 and above does support EMUI 9

FoOtY1337 said:
Woww great news!! Thanks for sharing!!
Click to expand...
Click to collapse
You welcome

THE MAXIMUM POWER said:
Yes, through Fastboot mode as Magisk 18.1 and above does support EMUI 9
Click to expand...
Click to collapse
So just extracting and patching the ramdisk as in
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157

Tool Belt said:
So just extracting and patching the ramdisk as in
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
Click to expand...
Click to collapse
Thank you for that

Just now showing up Firmware Finder (not approved) on my SHT-W09C567
---------- Post added at 09:53 PM ---------- Previous post was at 09:48 PM ----------
THE MAXIMUM POWER said:
Thank you for that
Click to expand...
Click to collapse
Actually that guide apparently may not be valid for 9.0 according to this:
https://www.xda-developers.com/magisk-canary-root-huawei-honor-devices-emui-9/
https://topjohnwu.github.io/Magisk/install.html
(scroll down to the Huawei section)

Are you sure that this is a firmware for a m5 sold outside china?
The name is totally different and in the the description it is mentioned the P8 Vip service.
Inviato dal mio CMR-AL09 utilizzando Tapatalk

giovaorama said:
Are you sure that this is a firmware for a m5 sold outside china?
The name is totally different and in the the description it is mentioned the P8 Vip service.
Inviato dal mio CMR-AL09 utilizzando Tapatalk
Click to expand...
Click to collapse
It is under the c432 firmware which means that it is for European countries, maybe it is still under development, but after unzip the files it shows that it is a base firmware

skyfileos.com/2019/02/09/huawei-mediapad-m5-10-pro-official-stock-update-firmware-download/ is this working? Just update?

warcanoid said:
skyfileos.com/2019/02/09/huawei-mediapad-m5-10-pro-official-stock-update-firmware-download/ is this working? Just update?
Click to expand...
Click to collapse
It will not work as it is going to failed by checking the package process

Flashed it via beta flashy. The proces aborted just before finishing. Nevertheless, I've got Pie up and running on my CMR-W09C432. Rooting via Magisk doesn't work.

Meningitis said:
Flashed it via beta flashy. The proces aborted just before finishing. Nevertheless, I've got Pie up and running on my CMR-W09C432. Rooting via Magisk doesn't work.
Click to expand...
Click to collapse
Did you try rooting using the info I provided in response #8?

Sure, I did. Maybe I'll try the Magisk Beta branch tomorrow..

If I have an unlocked Bootloader and want to keep it (I am on PHHH-Treble, vendor says 8.0.0.161, C423) that way, but update the vendor, is this Update the way to go?
So unpack, patch ramdisk and flash all the necessary files?
Thanks for any help! (there may stand experienced user at the left, however, I'd say, most posts were in a uite noobish state, so that I advanced into this rank without too much progress )

kev1807 said:
If I have an unlocked Bootloader and want to keep it (I am on PHHH-Treble, vendor says 8.0.0.161, C423) that way, but update the vendor, is this Update the way to go?
So unpack, patch ramdisk and flash all the necessary files?
Thanks for any help! (there may stand experienced user at the left, however, I'd say, most posts were in a uite noobish state, so that I advanced into this rank without too much progress )
Click to expand...
Click to collapse
Due to the crash while flashing, I wouldn't recommend flashing the build at all. Besides, my bootloader stayed unlocked, so updating the vendor should be possible, eventhough I don't see the reason for it? Do you want to flash Pie based GSIs?

Yeah, Pie-based GSI are on the horizon ... can only get one or two to boot (phh and I think Havoc).
Edit: I do not want to lose rot, so I'll have to wait a little longer

Is there anyone who got emui 9 official update? I see it on firmware finder and. 195 build is approved but i didn't get it. Even dns change method doesn't work.

Meningitis said:
Flashed it via beta flashy. The proces aborted just before finishing. Nevertheless, I've got Pie up and running on my CMR-W09C432. Rooting via Magisk doesn't work.
Click to expand...
Click to collapse
Can you please share a video how the full screen gestures look like?
BTW this crash while rebooting after flashing emui 9 on m5 will cause a HUGE problem if you want to downgrade using eRecovery as it happend once to me, i had to send it to huawei service, this problem will not even let you enter fastboot and you can not even unbrick your device using the chinese version of hisuite, so be careful and try not to enter eRecovery at all, (the crash is because there flashy do flash an only p20 pro FSD (firmware package check disable) and it is not for M5 so the abort will be caused while flashing the xloader (huaweis bootloader)

General (TMO) Don't update Galaxy A32 5G

Don't update to the new version with Bootloader V3 because Kernel Source of V2 is released which might be able to be used to unlock the bootloader, and to make custom roms or new TWRP versions

TypicalGellert said:
Don't update to the new version with Bootloader V3 because Kernel Source of V2 is released which might be able to be used to unlock the bootloader, and to make custom roms or new TWRP versions
Click to expand...
Click to collapse
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.

neotheone11 said:
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.
Click to expand...
Click to collapse
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.

neotheone11 said:
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.
Click to expand...
Click to collapse
I just keep them paused, I'm not sure if your able to disable it with adb

tavella said:
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.
Click to expand...
Click to collapse
Thank for the suggestion. Yes, that is what I meant when I said that I disabled automatic updates in the Developer Options. One of my Galaxy A32 phones kept pestering me to update despite the fact that I disabled the "automatic update" option so I was wondering if there was a better solution.
Do we know the IP addresses of the update servers? I searched online, but could not find the definitive answer.

tavella said:
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.
Click to expand...
Click to collapse
My 2nd A326U is on V3 ( T-mobile ) soon bootloader will be unlocked

financeledger said:
My 2nd A326U is on V3 ( T-mobile ) soon bootloader will be unlocked
Click to expand...
Click to collapse
I also have v3 (T-mobile) and am waiting for the same thing as you.

Hello guys. Where I can see bootloader version?
Thanks for answer.

Software version. Settings/About
5th digit from end is bootloader version. For example 3AUF7 is the ending on my version. 3 is the bootloader version.

Setting/about/software information/build number

scottyrick2 said:
Software version. Settings/About
5th digit from end is bootloader version. For example 3AUF7 is the ending on my version. 3 is the bootloader version.
Click to expand...
Click to collapse
Can you take screenshoot?

Ryan.XM said:
Can you take screenshoot?
Click to expand...
Click to collapse
My Screensho is not working properly right now.
Here are Step-by-step directions to find your bootloader version.
1. open Settings on your phone
2. choose About
3. choose Software Information
4. look at the number under the Build Number section
5. the fifth character from the right is the bootloader version
Let me know if you have problems.
Best,

scottyrick2 said:
My Screensho is not working properly right now.
Here are Step-by-step directions to find your bootloader version.
1. open Settings on your phone
2. choose About
3. choose Software Information
4. look at the number under the Build Number section
5. the fifth character from the right is the bootloader version
Let me know if you have problems.
Best,
Click to expand...
Click to collapse
Ok thanks bro,

Here's what I did on my T-Mobile A326U Samsung Galaxy A32 5G
1. Open the Android 11 Settings on your phone
2. Choose About phone
3. Choose Software information
4. Look at the number under the Build number section
5. The fifth character from the right is the Bootloader version
Mine is apparently Bootloader version 6.

Blu Vivo XL4 Rooting and Custom Rom Questions

I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.

Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
Vivo doesn't allow bootloader to be unlocked

That's nonsense, I can enable OEM unlocking in the developer settings, ain't that what's required?

Austinredstoner said:
Vivo doesn't allow bootloader to be unlocked
Click to expand...
Click to collapse
It's not Vivo company! That's a BLU company.
Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.

DragonPitbull said:
It's not Vivo company! That's a BLU company.
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.
Click to expand...
Click to collapse
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.

Jewel724 said:
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.
Click to expand...
Click to collapse
Yes! Android 8 from very OEMs/companies not have Treble/GSI compatibility.
Only Android 8.1 has that.
Update: Install this app https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en-US in the phone and know what architecture your phone/firmware has. That will show you which type of GSI file you can test.

Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.

Jewel724 said:
Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.
Click to expand...
Click to collapse
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.

DragonPitbull said:
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.
Click to expand...
Click to collapse
I'll give it a shot. In terms of performing a backup, I would assume that' typical "copy all files on phone to desktop folder just in case"

I should've mentioned, I don't have an SD card in my device, just a SIM card. I don't think I can use TWRP, which is going to complicate matters.

Hello I have a Blu Vivo XL4 android 8.1.0 Oreo, I'm trying to install a custom rom, I looked everywhere not a single rom is made for Blu phones.
bootloader unlocked
according to treble info:
System-arm64-aonly.img.xz
Your device supports the legacy version of project treble using VNDK version 27.0
Use an A-ONLY operating system
ARM64
Seamless upgrades are not supported
NO dynamic partitions
HELP
thanks

Android 12 - KB2007 released

Android 12 just dropped for TMobile OnePlus8T. I already want to roll back to 11 but after reading the guides none of them work and I'm assuming it's because you can't do that on a KB2007. But my phone is carrier and bootloader unlocked?

I'm struggling because mine is going to force the update at night, even tho I have automatic updates disabled on developer options. I have been looking for a way to stop it but nothing seems to work, not even the adb command to uninstall/disable the updater package. I don't know what else to do beside turning off the phone every night so it doesn't update itself.

fitrockx said:
I'm struggling because mine is going to force the update at night, even tho I have automatic updates disabled on developer options. I have been looking for a way to stop it but nothing seems to work, not even the adb command to uninstall/disable the updater package. I don't know what else to do beside turning off the phone every night so it doesn't update itself.
Click to expand...
Click to collapse
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com

Rootk1t said:
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for the information. Sadly mine can't be rooted yet. Once I'm able to get the unlock from T-Mobile I'll definitely try that.

Question Android 12 OTA REDMI NOTE 11 PRO 5G

When it is going to receive android 12 update OTA the Redmi note 11 pro 5 g veux rom EEA?

There is already Android 12 available
Version 13.0.3.0 SKCEUXM

davinceh said:
There is already Android 12 available
Version 13.0.3.0 SKCEUXM
Click to expand...
Click to collapse
Yes but the OTA doesnt come

I can't see any new update on my device. Still A11

Mado__ said:
I can't see any new update on my device. Still A11
Click to expand...
Click to collapse
Yes me too, that is why i am asking why the OTA isnt coming to our devices

Oh right

I think it's a bug or something. If you have previous than 13.0.10 versions software you can probably update directly. But if you have 13.0.10 you can't. You'd probably can update when there's an update who switches to the most recent security patches. You can't even force install via options not miflash not recovery flashable roms. I know cause i've tried that. Only way to do it is unlock bootloader, which is not adviced since you'll lose warranty. Anyway, only change i noticed is the toggles being a bit different. You just have the brightness and volume sliders vertically. Everything else looks the same to me. Of course you can always update with miflash and relock bootloader, but it's a risk. Either way you'll need to backup your data before doing it

Alvaro_.15 said:
Yes me too, that is why i am asking why the OTA isnt coming to our devices
Click to expand...
Click to collapse
Mado__ said:
I can't see any new update on my device. Still A11
Click to expand...
Click to collapse
I'm as well on a11
Was trying every possible download file non of them working.
Look like Xiaomi left us behind

Hi, same problem here.
I have version 13.0.10.0 with Android 11 and I am not receiving OTA updates.
Through recovery mode it doesn't let me update to version 13.0.2.0 or 13.0.3.0 with Android 12.
I tried everything but nothing.
How to do?

It's so crazy this phone is still on A11 lol..