Related
Welcome!
This Megathread is to help bring the different threads together for the Xiaomi Black Shark (SKR-A0 or SKR-H0) since the xiaomi-black-shark tag is broken (at least for me it is). This will also serve as a one-stop shop for people who need general black shark support!
Disclaimer: You (the user) assume the risk for any bootloader unlocking, rooting, or any other modifying of your device. These can lead to phone's being bricked or boot-looped. We aren't to blame if the directions aren't followed to the T!
Tips before modding your phone
1. Stay organized! Make a folder for any files you download or data your backup so you don't lose anything important
2. Backup your user data onto your computer. It is guaranteed 100% of the time that your phone's data will be wiped when installing of uninstalling ANY of the modifications listed below. Unless you have been rooting and unlocking bootloaders for years, you don't want to skip this step.
Common ADB and Fastboot Commands
These are some commands you'll need to get to know:
adb devices: this shows what devices are currently connected to your computer
adb pull: this pulls a file from your phone and saves it to a location on your computer. You will need to specify the location of the file and the save location of the file
adb reboot bootloader: this reboots the phone into fastboot mode to use fastboot commands
fastboot devices: this shows what devices are connected to your computer in fastboot mode
fastboot boot filename.img: this boots the phone with using a image file of your choice
fastboot flash disk_partiton filename.img: this will flash an image file over the disk partition you want.
Example:
fastboot system system.img flashes a new system_a.img over the system parition of your phone's storage. This is where the main operating system is held on the phone.fastboot reboot: reboots the phone
fastboot continue: boots the phone straight from fastboot into the system, not restarting the phone.
Unlock/Relock your Bootloader
WARNING: This WILL wipe your internal data
On Android, the phone must have an unlocked bootloader to enable some of the common modding features. These steps will unlock your bootloader.
Pre-requisites:
1. You will need the SDK Platform Tools downloaded onto your computer. This has the necessary adb and fastboot programs you will need in order to unlock your bootloader.
2. Enable Developer Options on the Phone
-Go to Settings -> About phone and tap the Build Number 7 times to enable Developer Options
3. Enable OEM unlocking
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
4. Enable USB Debugging. This lets you use ADB (Android Debugging Bridge) to send commands from your computer to the phone.
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable USB debugging.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable USB debugging.
5. Boot into fastboot mode.
-Booting from the Phone:
Turn the Phone off
Press and hold the Volume Down Button
Turn the phone on while holding the volume down button
-Booting from the PC:
Connect your phone to your computer.
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: adb devices
A pop up should show up on your phone. Click the checkmark next to "Always allow from this computer" and click ok. Your computer is now allowed to send commands to the phone.
Now run the command: adb reboot bootloader
You should now be in fastboot mode!
To check if you're in fastboot mode:
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: fastboot devices
If your device shows up then you're in fastboot mode! You should also see a line of text that says something like:
"Bootloader Locked"
"Bootloader Unlocked"
Unlocking your Bootloader:
1. If your phone says bootloader is locked:
While connected to your PC run the following commands:
-For SKR-A0
fastboot oem unlock
-For SKR-H0
fastboot flashing unlock
If there is a warning click to proceed with the unlock. THIS WILL WIPE YOUR DATA AT THIS TIME.
If your phone says bootloader is unlocked:
Skip this step!
Your Bootloader is now Unlocked!!
Relocking your Bootloader:[/size]
1. Boot into fastboot mode
2. Connect your phone to your computer
3. Run the Bootloader Lock command
3a. For Both Versions
fastboot flashing lock
WARNING: THIS WILL WIPE YOUR DATA.
Your bootloader is now Locked!
Rooting Using TWRP
Unlocked Bootloader Required!
Required files:
The latest Magisk Zip and APK files...it can be found here
A Computer with the latest SDK Platform tools
TWRP image file found at this thread
Do NOT download the installer.
1. Boot into fastboot mode and connect to your computer
2. Run the command: fastboot boot Name_of_twrp_file_.img
Replace Name_of_twrp_file.img with the name of the twrp image file you've downloaded for the blackshark
Tips:
If your screen is upside down, that's ok! Your touches will be in the same spot, the image is the only thing that's upside down.
On first boot, if TWRP is asking for a decryption password, you will need to wipe your data before going forward.
3. Move the Magisk Zip file to your phone's storage
4. On TWRP:
Click install -> Magisk.Zip file -> Swipe to confirm flash
5. After the install is complete: Swipe to reboot the phone
DO NOT INSTALL TWRP APP IF IT ASKS YOU TO
6. After the phone reboots, install the Magisk apk file
7. If you start the magisk app and it says Magisk is not installed, try rebooting your phone.
8. If you start the magisk app, and it asks to download extra resources, click ok.
You're now rooted!
Install GApps
Installing GApps should only be for the CN version!
You can find the directions and required files in this thread here
Factory Images
For the CN version (SKR-A0)
The factory images can be found on Google Drive here
For the Global version (SKR-H0)
[Guide] Restoring Black Shark 1 Global to Stock OTA bug fixed!
Using Project Treble (GSI) System Images!
What is Project Treble and GSI?
The Generic System Image (GSI) was added into Android 8.0 devices to enable OEM partners and developers to help with updating devices. Using an dual system approach (slot a and slot b) android phones can be updated seamlessly (without rebooting) and recover devices from a bad update.
Project Treble is an extension of this feature to enable developers to update their OS easier to new versions of Android! This includes *drum roll* the ROM commmunity!! So if your phone supports project treble and gsi (which the Black Shark does) we already have ROMs available to us!
The Downside to Project Treble Roms
Our Vendor File isn't compatible with Treble ROMs and we can't use other vendor files (as what I have seen so far) so these bugs will exist for now:
The S logo doesn't turn off. Stays Green lit.
You may not be able to increase screen brightness.
Fingerprint may not work on the Treble ROM.
Installing a Project Treble Rom
YOU WILL LOSE YOUR USERDATA. THERE IS NO GETTING AROUND THIS AS OF NOW.
Prerequisites:
Unlocked Bootloader on your phone and adb, fastboot, TWRP image and the most recent Magisk Zip on your computer.
For CN variants (SKR-A0) you may need to use the Global (SKR-H0) vendor and boot images. These steps were tested on using the Global Images
1. Choose your rom over here
2. Download the ARM64 A/B version of your rom of choice. The Black Shark supports Seamless Updates and it's based on the 64bit architecture (as are most modern phones).
3. Factory Reset your phone. You can do this either through the recovery or through the system settings.
4. Boot into bootloader mode on the phone and connect the phone to the PC.
5. Erase the system partition: fastboot erase system
6. Flash the new system OS: fastboot -u flash system system_image_file.img
7. Boot into TWRP from fastboot: fastboot boot twrp_file.img
8. Tap the DO NOT ALLOW SYSTEM MODIFICATIONS
9. Move the Magisk Zip file to your phone.
10. Click Install -> Magisk Zip -> Swipe to Install
11. Reboot the Phone
That's it! Your screen will be upside down during the media locking process (using a Disable Force Encryption file has not worked for me). Once your get to the setup page you may have to set it up with the screen upside down. THIS IS THE SAME AS HOW TWRP IS UPSIDE DOWN BUT THE TAPS ARE IN THE NORMAL SPOTS. If a warning comes up that's normal.
Android 9.0 Pie News!!!
https://forum.xda-developers.com/android/development/news-black-shark-2-features-coming-to-t3924703
How to Get CN Rom's Shark Space and MI Market onto Global ROM:
https://forum.xda-developers.com/an...-cn-shark-space-mi-market-blackshark-t3927854
Credits:
TWRP by @mauronofrio
Offical XDA Magisk Thread
@gilbert32 for factory global images
Placeholder
---------- Post added at 04:28 PM ---------- Previous post was at 04:25 PM ----------
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.
gilbert32 said:
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Click to expand...
Click to collapse
No problem!
The CN version gets messed up on the OTA if your active boot is on B. It seems the OTA updates only work with active boot A. It also gets messed up obviously if the backup boot is not the same version. I had to make sure both system_a and system_b were on CN before updating system_a with the OTA.
Hope this helps.. obviously I'm a CN user, but you never know! :good:
gilbert32 said:
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.
Click to expand...
Click to collapse
I already have a linux environment in the works...
I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.
gilbert32 said:
I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.
Click to expand...
Click to collapse
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!
JengaMasterG said:
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!
Click to expand...
Click to collapse
AFAIK, it's gonna be pretty hard to build without having the kernel sources. Unless they release them soon, building for the device directly is gonna be a long shot.
However, checkout the treble device forums. You can download and flash roms from that section, and they will probably boot, but you'll have problems with auto brightness, random reboots, etc.
I still can't get the auto brightness and device specific stuff to work.
I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.
a8530516 said:
I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.
Click to expand...
Click to collapse
can you share how you did it here?
JengaMasterG said:
The Model version is set by the vbmeta.img files. You should be able to find those here under the factory image files section.
If you want any future support, ask for it in in the megathread so we can keep all the support in one thread :good:
Click to expand...
Click to collapse
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks
khususgw said:
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks
Click to expand...
Click to collapse
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.
JengaMasterG said:
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.
Click to expand...
Click to collapse
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks
khususgw said:
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks
Click to expand...
Click to collapse
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.
Reply:
Xiaomi Black Shark support are the thing which people need to know now a days world is evolving and things are changing rapidly.
JengaMasterG said:
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.
Click to expand...
Click to collapse
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks
khususgw said:
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks
Click to expand...
Click to collapse
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.
JengaMasterG said:
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.
Click to expand...
Click to collapse
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a
khususgw said:
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a
Click to expand...
Click to collapse
Yeah you can do it that way!
JengaMasterG said:
Yeah you can do it that way!
Click to expand...
Click to collapse
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.
khususgw said:
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.
Click to expand...
Click to collapse
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.
JengaMasterG said:
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.
Click to expand...
Click to collapse
after i try flash from scratch
and using old vendor b
still i cant do the OTA update
Hi everyone,
I have rooted my last few smartphones and was always happy with it. Now I got new Blackview BV9800 PRO and I want to root it with Magisk. but as the phone is new, there is lack of information on the internet, Anyway, I have found some information, but it is not complete and I believe You, smart guys, can help me to root my smartphone
This is the information I got:
How to root it with Magisk :
Download your rom from : viewtopic.php?f=285&t=532354 (you can alternatively extract it with SP Flash Tool and WWR)
Download and install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/rel ... v7.5.0.apk
Patch the boot image with Magisk Manager
Unlock the bootloader. (Wipe the phone! )
Flash the patched boot image with SP Flash Tool or Fastboot. (ONLY the boot image)
Reinstall Magisk Manager
This is what I did and what happened:
I installed latest Magisk apk from official sources. I opened the app, clicked on "Install Magisk", then via this app I downloaded the zip file, then tried to installed it via Magisk but got an error "Unsupported/Unknown image format".
Any ideas what have I done wrong? Did I have to flash boot image from the ROM, and not the one Magisk downloaded? P.S., the smartphone is new, nothing more then I written above is done to it (no oem unlocking, no usb debugging, etc).
RESERVED
I let Magisk manager patch the original boot.img. After flashing it with fastboot or SP Flash the phone stuck with message that verified boot didn't accept the signature.
Hm... Is there anyone who rooted BV9800 Pro successfuly and could guide us? ?
update fail.
I greet you, I accidentally deleted it when I updated, Nvram. on my phone. BV9800pro. It is possible to provide me with firmware recovered from a similar phone. I also posted on the forum at Blackview but without answer
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
update fail
LGZACRO said:
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
Click to expand...
Click to collapse
Hello
Yesterday during an update, by accident, my equipment, BV9800pro, performed a complete formatting, "Full Format + Dowload", it seems that Nvram has also been rewritten. it is possible to provide us with a solution or file with this data, specific to our equipment. i need a original nvram.bin, and nvram.data, in firmware from Blackview site this its not exist..
if someone wants to help me, I send them a private message with their email address
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
LGZACRO said:
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
Click to expand...
Click to collapse
who guarantees this?
rooting worked for me with that solution given to the PM. I wanted to install AOSP, but I found that the thermal image did not work anymore, there were some problems when previewing the video files from Facebook, and I gave up. from the mistake as I mentioned I format + dowload and delete all important partitions. nvram .bin si nvdata. Nothing works properly, TEE and Google Key are inactive, the thermal image fails, some applications are closed immediately. This is the experience with rooting and installing AOSP on the BV9800Pro
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
make total firmware dump and send the bakup , or nvram.bin nvdata.bin file,
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
i dont now. i dont install twrp.
Ok, pm me your skype or signal or wickr or fb. We will try to do this in few hours
LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
I posted in their forum a detailed error report but the moderator deleted my post.
Don't bargain for help by them.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
As I mention there's no TWRP available for this phone yet.
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
I rooted it exactly like You and it worked perfectly! Thanks for auch detailed rooting guide!
By the way guys, I think we Should open the request for TWRP for BV9800Pro. How do You think?
After you unlocked bootloader, it changed to orange state, and it always shows "Your device has been unlocked and can't be trusted..Your device will boot in 5 seconds", it could be resolved by modified LK image.
Refer to
1. https://forum.hovatek.com/thread-31664.html
2. http://bbs.blackview.hk/viewtopic.php?f=286&t=532899 -- included modified LK image
Of course, you could reflash by fastboot, no need to use SP flash tool.
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
james35888 said:
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
Click to expand...
Click to collapse
zlatkomas said:
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
Click to expand...
Click to collapse
Hi, I'm not rooted (yet) and my BV9800 PRO is having some issues with the loudspeaker, any media like YouTube or Spotify, play audio for a second or two and then just go mute, volume can be high but no audio at all, phone calls last longer but also go mute and have to go back to regular "ear-speaker" to keep listen to the other side. Are this the same problems you refer to? I can't remember if this happened after the OTA update tho. Thank you.
I just received my ROG Phone 5 today and rooted it using Magisk. These are my notes. (I like to keep rooting notes for each device in case I ever need to check how I did it or repeat the process.)
If you are already familiar with rooting a device with Magisk, then you will find these notes very familiar. These are based on the generic Magisk method listed here: https://topjohnwu.github.io/Magisk/install.html
Magisk's instructions note that the device should be running a stock ROM. If you are using a brand new device, this should already be true BUT there are reports online that some resellers are selling a locked device that was previously unlocked, flashed with a custom rom, and then re-locked. (The people reporting this issue have devices that say Tencent on the back and come in a rectangular box, but it's also possible that you have a Tencent version that can be unlocked. Asus made a deal with Tencent to release a special Tencent edition of the phone, but Asus is also selling the phone as well. I have not heard any reports of the non-Tencent version coming in a state that cannot be unlocked. I bought one that was more expensive and got sent the pro in the non-rectangular box, without Tencent on the back of the phone.)
I rooted the phone from a machine running Ubuntu. I imagine it would also work from other linux distros or from osx, but I have no idea if it will work from Windows.
1) Turn on Developer Options:
Start phone, go through setup process (skip as much as you can because you will lose all of these settings in the rooting process), go to Settings->System->About Phone->Software Information->click on the build number seven times, enter your pin when/if prompted
2) Enable USB Debugging:
Go to Settings->System->Developer Options
Enable USB Debugging
Connect via USB from the side of the phone to your computer (do not use the usb port on the bottom of the phone)
When prompted on the phone, agree to allow File Transfer and USB Debugging and trust the PC
3) Check whether the bootloader is already unlocked:
Open a terminal on your computer
(install adb and fastboot if you have not previously done so)
$ adb reboot bootloader
Wait for device to reboot, then from the terminal do
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
... etc
^^ This is what the output may look like if your device is not already unlocked.
If the bootloader is already unlocked, you can skip step 4.
4) Unlock the phone:
Start up your phone
Download the unlock utility on your computer:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
from the terminal do
$ adb install ./AsusUnlock_1.0.0.7_210127_fulldpi.apk
This will install the unlock tool on the phone
Open the newly installed unlock app on the phone
Follow the instructions in the app to unlock your device.
After unlock, you will have to go through the phone setup all over again. Annoying, I know.
From this point on, you can expect a warning about your bootloader being unlocked every time you boot the phone. This is normal.
(If unlock fails, you may have been sold a phone that was unlocked by a reseller, flashed with a custom ROM, and then re-locked. If that's the case, this method of rooting your phone will not work. You can always try to return the phone if it was advertised as being unlocked and isn't.)
5) Install Magisk:
Download the latest Magisk apk onto your PC from https://github.com/topjohnwu/Magisk/releases and rename it to Magisk.apk
Open a terminal on your PC and
$ adb install ./Magisk.apk
This will install the Magisk app on the phone
Open it and verify that it says "Ramdisk Yes" two lines under the blue word Magisk. The ROG Phone 5 *should* say this and if it does not something is wrong, refer to the official Magisk instructions.
6) Download the firmware from ASUS:
Let your phone update if it has not already. Mine was pushed an update after install.
Check the exact version you are currently on after the phone updates.
Go to Settings->System->About Phone->Software Information
You need to know your Extension Rom and your Build Number
Then download the firmware from Asus for your build number by going to the URL corresponding to your build number and extension, such as:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-18.0840.2103.26-1.1.81-user.zip
Where 18.0840.2103.26 from the link above is my build number and 1.1.81 is my extension ROM. If your build number and extension are different, change those values in the URL.
7) Extract the boot.img from the firmware:
Unzip the downloaded firmware
Install Payload Dumper on your PC: https://github.com/vm03/payload_dumper (instructions for installing payload dumper are on the github)
Copy payload.bin from the extracted firmware into the payload dumper folder
Open a terminal, cd to the folder containing payload dumper and payload.bin and then run
$ python3 payload_dumper.py payload.bin
Note: depending on how python is installed, you may need to type python instead of python3 here.
Once this completes, the boot.img file will be in payload dumper's output folder
$ cd output
$ adb push boot.img /sdcard/boot.img
8) Patch the boot file using Magisk:
Open Magisk
Press the install button to the right of the word Magisk
Press "Select and Patch a File", browse to the boot.img from the file folder (if you put it in SDcard like me, try checking the Rog Phone 5 folder for it)
Magisk will patch the boot.img to make it usable for your phone and place it in a file named magisk_patched_[random_strings].img in the Downloads folder of your phone.
9) Flashing the rooted firmware:
Transfer the patched file to your PC and rename it to ./magisk_patched.img
Reboot into fastboot by opening a terminal and entering
$ adb reboot bootloader
Test the image file prior to flashing:
$ fastboot boot ./magisk_patched.img
If that did not error (the bootloader unlock warning is normal), reboot into flashboot and flash:
$ adb reboot bootloader
$ fastboot flash boot ./magisk_patched.img
$ fastboot reboot
After the warning about the bootloader being unlocked, the phone should boot as normal. Once booted, open Magisk and verify that it is rooted by looking for the version of Magisk that is installed. Under the word Magisk in blue, it should say Installed: version. If it says Installed: N/A then your device is not rooted.
You should be able to further test whether you have root access at this point by doing
$ adb shell
$ su
Then clicking accept on the su request on your phone. If that works, the device is definitely rooted.
Thank you for the notes.
Unlocked bootloader and Rooted my ROG phone 5 WW firmware today.
Double checked with my firmware and extracted boot.img
Payload dumper was not working in both of my pc for some reason (bsdiff4 error). Tried with Android phone through termux and successful to extract the boot image.
Rooted with magisk passing safetynet.
Thank you
jhosharath said:
Thank you for the notes.
Unlocked bootloader and Rooted my ROG phone 5 WW firmware today.
Double checked with my firmware and extracted boot.img
Payload dumper was not working in both of my pc for some reason (bsdiff4 error). Tried with Android phone through termux and successful to extract the boot image.
Rooted with magisk passing safetynet.
Thank you
Click to expand...
Click to collapse
Awesome. Please write up an alternative for step 7 if you can, in case anyone else needs it.
Also, I actually am getting a SafetyNet API Error, so I'm curious if you did anything special to make it work.
hey, thank you very much for your notes, they would have been very helpful a few weeks ago when i almost bricked my device eheh.
i'm also getting a safetynet error (ctsProfile), wonder what that could be.
also didn't know about the build number, i kept flashing raw firmwares blindly like a moron, accidentally getting the right ones it seems... so thanks for that too.
i too have been wanting to write my notes on the forum for others to read, but you... you made the difference !!
amazing work
To extract the payload.bin through android phone I followed the steps as mentioned in this link
https://forum.xda-developers.com/t/tutorial-android-ota-payload-dumper-on-android.4061799/
Credits to GuestK00376 for the tutorial.
Until TWRP recovery comes this will be very much useful for those who have issues with that python or payload dumper in pc.
Safetynet API error is a problem with magisk recently. You can download Safetynet testing apps from playstore and check it. Mine had CTS profile false only which i sorted with universal safetynet fix magisk module. Also check playstore certification of device in playstore settings. If not certified then you have to hide it with magisk hide fully then have to clear Google play services and google play store data in aeroplane mode. Reboot, revert aeroplane mode to normal and then it was certified.
Thank you. Hope this will help. Good luck
I just successfully rooted my device I purchased it from Amazon it was the tencent edition it already had the global ROM installed I used the app to unlock the bootloader successfully I was able to extract the boot image from my Android device I made a small tutorial video I'm going to edit it and post it in case anybody's interested and wants to see it done
chairman011 said:
I just successfully rooted my device I purchased it from Amazon it was the tencent edition it already had the global ROM installed I used the app to unlock the bootloader successfully I was able to extract the boot image from my Android device I made a small tutorial video I'm going to edit it and post it in case anybody's interested and wants to see it done
Click to expand...
Click to collapse
Very much appreciated and useful for those who are trying to root. Good work bro
I am not a YouTuber or anything I just took bits and pieces from everybody's advice I couldn't have done it without the help of you guys hopefully this helps somebody I hope I didn't make it too difficult to understand.
Hopefully it helps somebody
Sorry guys I forgot to mention you need the safety net universal fix module here's the XDA link I forgot to mention that in the video my apologies
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
I am happy to report that I am now passing SafetyNet after Installing both the Universal SafetyNet Fix from github and the MagiskHide Props Config plugin within Magisk (press the puzzle piece button on the lower right hand corner of the Magisk app, then search for it). I'm not sure what exactly made it work though. After install, I was able to configure which applications to hide from via the Superuser->Magisk Hide menu within Magisk.
I had some difficulty with props and ended up reverting changes after trying to update my fingerprint to match the Rog Phone 3. Then things started working after several reboots. I'm not sure what is going on here, so I'm not confident that someone else will be able to reproduce this via the steps I used. Otherwise I'd write up a comprehensive set of steps used here.
I had to use another app to verify safetynet because the check is not working within Magisk.
You forget to explain for the safetynet
You way are good but not complete,
-magisk hide
-Univerversal SafetyNet 1.1.1 (patch)
-canary (new magisk)
Without that you are rooted but, with SafetyNet error
And after bootloader unlock after phone restart before root upgrade your Netflix, because after it's too late impossible to upgrade and no Netflix fix
chairman011 said:
I am not a YouTuber or anything I just took bits and pieces from everybody's advice I couldn't have done it without the help of you guys hopefully this helps somebody I hope I didn't make it too difficult to understand.
Hopefully it helps somebody
Click to expand...
Click to collapse
I tried to use termux and when i paste the last "apt update && apt upgrade -y" i get a error that tells me that its under maintenance
All fastboot / adb commands require using the side USB-C port
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Make sure you have fastboot installed
Add platform tools to PATH (post 2)
Make a backup of anything important
Sign out of all Google accounts on device
Open settings -> accountsTap the google email addressTap "Remove account"
Reboot into bootloader
Connect the phone to the computerYou must use the side USB port
From the system (usb debugging enabled):adb reboot bootloader
OR
Boot the phone with volume up + power
Use a 64-bit OS to flash the raw firmware
Open a command or terminal window"cd" to the extracted firmware folderExecute the flash_raw/all for your OS
I recommend using Windows to flash the firmware. If you have Mac, using a Windows image in VMWare also works. This will NOT lock your bootloader.
Those looking to convert between CN and WW firmware:
Repair ROG Phone 5 ZS673KS through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
These materials can only be used for ROG Phone 5_ZS673KS, and ROG Phone 5S_ZS676KS cannot be used. ROG Phone 5S ZS676KS Please see...
forum.xda-developers.com
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
Bootloader Unlock App
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
Raw Firmware Packages (courtesy of m8822 / johnny886 / HunterTik / JazonX)
Downloads for : ASUS ROG Phone 5 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
WW_ZS673KS_18.0830.2102.88_M2.13.24.14.3-ASUS_1.1.80_Phone-user.raw
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw
Downloads for : ASUS ROG Phone 5 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw
S Series Raw Firmware (courtesy of JazonX)
Downloads for : ASUS ROG Phone 5 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
WW_ZS676KS_18.1220.2107.106_M3.13.24.43-ASUS_1.1.32_Phone-user.raw
Disclaimer:
This process will wipe your data and cannot be reversed until complete (See below).
Do not disconnect or reboot your phone during the flashing process.
I am not responsible for bricks, loops, or any other natural or man-made disasters.
Note: Newer raw firmware includes separate commands for wipe / no wipe install
If attempting to flash the device fails instantly, please see this thread:
[GUIDE]How to reboot to EDL from fastboot
Most Qualcomm-based Android PDAs support emergency download (EDL) mode allowing to unbrick device, unlock bootloader or modify protected device parameters. If ADB interface is accessible, "adb reboot edl" can be used to reboot to EDL mode. Many...
forum.xda-developers.com
Note: This does not trigger true EDL mode. Try before attempting a true EDL restore.
It is recommended that platform tools is extracted to the root directory (C:\) on Windows or the home folder (~/) on Mac / Linux. Replace PLATFORM_TOOLS_FOLDER with the full path below.
Adding platform tools to PATH (Windows courtesy of LifeHacker):
Open the Start menu and search for “advanced system settings.”
Click “View advanced system settings.”
Click the box that says “Environment Variables.”
Under “System variables” click on the variable named “Path”.
Click “Edit...”
(Windows 7,8): Add ;[PLATFORM_TOOLS_FOLDER] to the end of the “Variable value” box. Do not forget the semicolon.
(Windows 10): Click “New” and paste the folder path where you extracted the Platform Tools. Hit Enter and click OK.
Adding platform tools to PATH (Mac / Linux):
Add the following line to ~/.bash_profile (or .profile)
PATH=$PATH:[PLATFORM_TOOLS_FOLDER]
Open a terminal window and enter this command
source ~/.bash_profile (or .profile, is used above)
twistedumbrella said:
"Make sure you unlocked the bootloader"
Click to expand...
Click to collapse
Can I go from WW to CN w/o unlocking the BL?
My tencent edition ROG5 with WW f/w denied me unlocked BL when tried with official unlocking app.
I want to try my luck on CN f/w for one last time.
Much appreciate your hard work for our cursed edition device..
Unless the reason the app didn't work is that it is already unlocked, it may fail.
Guese I don't have any options left other than waiting for the EDL f/w to become available, do I?
The EDL firmware is linked in the first post.
I should stick to calling it raw firmware for clarity.
twistedumbrella said:
The EDL firmware is linked in the first post.
Click to expand...
Click to collapse
OK, I'm a bit confused. Help me out here please.
The EDL f/w you are talking about is missing some key files & thus non-functional.
Since my device was unlocked once & then re-locked, the official unlocking app is non-functional as well.
Is there any way, other than paying some random foreigners, to unlock the BL?
You are looking to flash the bootloader in EDL mode, since you can't replace the bootloader in the bootloader itself. The raw firmware does not include the firehose file required to use QPST. This is the firmware you use in EDL mode after recovering from a hard brick.
I haven't checked if the bootloader in included in the raw firmware, but since a small portion of the flash requires userspace fastboot, I would assume it is quite possible
twistedumbrella said:
You are looking to flash the bootloader in EDL mode, since you can't replace the bootloader in the bootloader itself. The raw firmware does not include the firehose file required to use QPST. This is the firmware you use in EDL mode after recovering from a hard brick.
I haven't checked if the bootloader in included in the raw firmware, but since a small portion of the flash requires userspace fastboot, I would assume it is quite possible
Click to expand...
Click to collapse
Will be waiting for your findings. Many gratitude for taking this into consideration..
If you encountered following error while executing flashall_aft, make sure check your fastboot install --> post 2.
get cpu id fail
FAILED (remote: 'Unknown variable')
get cid fail
FAILED (remote: 'Unknown variable')
get project fail
FAILED (remote: 'Unknown variable')
...
fastboot: error: project name () mapping the wrong raw id (0x33)
Can I go from WW to CN w/o unlocking the BL?
and
Would I be able to return to WW from CN w/o unlocking the BL as well?
aimsjahan said:
Can I go from WW to CN w/o unlocking the BL?
and
Would I be able to return to WW from CN w/o unlocking the BL as well?
Click to expand...
Click to collapse
No (plural)
tnx for this thread
2 questions
after this i can update rom manually with copy in root folder
is there any video guide for this convert ?
yaser86100 said:
tnx for this thread
2 questions
after this i can update rom manually with copy in root folder
is there any video guide for this convert ?
Click to expand...
Click to collapse
Updates will be the same as having an unlocked bootloader. Move it to /sdcard/ and reboot.
No video guides. It is harder to copy text shown in a video than from the text itself.
I am aware some of the original links have "expired" (or been removed by the original owners). Fortunately, I made sure to download all but one of the firmware locally and will be uploading them to AndroidFileHost to avoid them getting lost again.
is it worth changing the version from WW to CN?
thieftime1980 said:
is it worth changing the version from WW to CN?
Click to expand...
Click to collapse
Unless you are in China, no.
tnx for making this thread
one question
after conver if i modified build prob and add ww to country file fingerprint sensor works normal or could be have problem?
yaser86100 said:
tnx for making this thread
one question
after conver if i modified build prob and add ww to country file fingerprint sensor works normal or could be have problem?
Click to expand...
Click to collapse
There could always be problems. Seems to be hit or miss.
Hi all, thought I would post a simple guide for people who are wanting to get some customisation on their ROMs and install root.
First off - as of this post there's no working twrp/orangefox for this device and as far as I'm aware android 12 itself still has lots of recovery quirks.
So without further ado, we will be using the fastboot method to install MIUI 13 EU stable.
First things first - we need to unlock our bootloader...
Log into your Mi Account using your phone with a data connection (disable WiFi)
- Enable Developer Settings -> Enable USB Debugging
- Enable OEM Unlock in Developer Settings
- Add device in Mi Unlock status in Developer Settings.
You now need to wait 168 hours before the unlock tool will work....
Now use your device as normal (yes you can use WiFi) but make sure you actually use it for things like calling, texts, GPS and some data usage. I say this because some users report that the timer has not expired even though technically 168 hours had passed.
Right - still with me? Let's continue the guide. Next step before we unlock our bootloader is to backup our data.
I repeat
BACKUP YOUR ENTIRE DEVICE BECAUSE IT WILL BE WIPED ENTIRELY. That means your photos, music, everything. This will delete everything. You have been warned.
Download the tool here
Apply for permissions to unlock Mi devices
en.miui.com
And follow the on-screen prompts and eventually your phone will reboot.
I usually let it completely boot (may take 10 minutes) until it enters the MIUI welcome screen etc just to verify the device is still functioning as expected.
Next phase has two options:
Option one, install MIUI EU ROM and root
Option two install root only.
If you only want to root your stock MIUI then skip to option two down below.
Option one, install MIUI EU ROM and root:
First off, we will need ADB installed. I used the version linked below
[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools
Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com
I put the folder in C:/ADB
Download fastboot image/rom for your phone.
MAKE SURE YOU PICK THE CORRECT FILE FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOUR DEVICES CODENAME IS, DO NOT PROCEED ANY FURTHER OTHERWISE YOU WILL BRICK YOUR DEVICE.
In MY case, my phone is the one listed in this forum, a Poco x4 pro 5g. So I downloaded the file for a Poco x4 pro 5g codenamed veux
From here. EDIT: The file names have since been updated due to this phone having multiple varients so be sure to check which device/files you need - the correct file for a Poco x4 pro 5g is now "VEUXG"
Xiaomi.eu Multilang MIUI ROMs - Browse /xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13 at SourceForge.net
OFFICIAL mirror of MIUI Multilang ROM by https://xiaomi.eu/
sourceforge.net
Extract the fastboot image/rom into this folder c:\ADB (or where you installed your ADB folder)
Open "cmd.exe" on your PC
Change to directory were you have installed adb & fastboot/ROM file locations
Type (ALL commands here are without the quotation marks, for example the next few words would be: cd c:\adb) "cd c:\adb" press enter
This will set ADB to our target folder that you moved your fastboot ROM into.
Connect your phone to the pc and reboot phone. Then by holding "Volume -" and "Power on" buttons simultaneously after approx 10 seconds or so you should see "fastboot" on the phone.
Now in the CMD window, type "fastboot devices" and hit enter.
You should see a number (sometimes with characters) appear alongside the word fastboot which signals that you're connected correctly.
if you dont see a number:
change USB port / change USB cable / use USB 2.0 / check driver installation...
Once you have fastboot detecting your device, DOUBLE CHECK YOU HAVE THE CORRECT INSTALLATION FILE FOR YOUR DEVICE.
Got the right one? Sweet, we're ready to flash MIUI EU.
with your rom extracted into a folder (I put mine inside the adb folder) right click the bat file you wish to use - FORMAT or UPDATE, choose "copy path", insert in command line/cmd window then press enter. Follow on screen directions.
Wait for it all to complete now you're good to go, it will reboot and you're successfully running MIUI EU! Now read below if you want to root your device too
Root
I'm guessing you've already booted up your phone running MIUI EU by now, set up the basics until you get it to the home screen.
Download magisk and install it onto your phone.
Now we need to patch our boot.img and lucky for us the boot.img is located inside the MIUI ROM you downloaded earlier on your PC - nice!
Extract the boot.img and place this onto your phone via USB or SD card.
Unfortunately for those running a stock ROM, you will need to locate your stock ROM files boot.img.
Open magisk, tap install then the option to patch the boot.img (you'll see how to do this once you open the app)
At this stage I removed any of the other MIUI files/folders from my ADB folder to avoid any confusion. transfer the patched boot.img into your ADB folder on your PC and rename it to boot.img
Turn your phone off and boot into fastboot mode again Open CMD again
Type "cd c:\adb" press enter.
"Fastboot devices" press enter.
(Make sure you see the numbers/letters that show your device is detected etc)
Now type
"fastboot flash boot boot.img"" press enter and wait for the process to complete.
Congratulations you now have a nice fluid ROM without loads of bloat and root ready to install some goodies
For those of you who haven't tried a MIUI EU ROM I suggest you have a Google to see what additional features it offers over stock. I prefer it over any aosp/custom ROM due to the stability, customization and the fact it's stripped of all MIUI bloatware
https://xiaomi.eu/community/threads/xiaomi-eu-vs-global-rom-differences.37425/ here's what I found for those lazy ones among us.
1qazwsx4 said:
Now type
"fastboot flash boot.img" press enter and wait for the process to complete.
Click to expand...
Click to collapse
Many thanks for your post but this one should be "fastboot flash boot boot.img"
Hientran43 said:
Many thanks for your post but this one should be "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Your welcome and thanks for that, corrected and updated my fault for posting so late into the night haha
Just wanting to be 100% sure, as I'm pretty sure this is right but really don't want to brick the phone -
The Poco X4 Pro 5G with Model 2201116PG would be formatted with the ROM
xiaomi.eu_multi_VEUX_V13.0.4.0.RKCCNXM_v13-11-fastboot.zip, yes? Or would it be the VEUXG rom?
GandhiChan said:
Just wanting to be 100% sure, as I'm pretty sure this is right but really don't want to brick the phone -
The Poco X4 Pro 5G with Model 2201116PG would be formatted with the ROM
xiaomi.eu_multi_VEUX_V13.0.4.0.RKCCNXM_v13-11-fastboot.zip, yes? Or would it be the VEUXG rom?
Click to expand...
Click to collapse
There are also 4 phones under the VEUXG ROM name. Although the 64-megapixel camera phone Codename peuxp. Unclear, i would also be interested in which one to install
GandhiChan said:
Just wanting to be 100% sure, as I'm pretty sure this is right but really don't want to brick the phone -
The Poco X4 Pro 5G with Model 2201116PG would be formatted with the ROM
xiaomi.eu_multi_VEUX_V13.0.4.0.RKCCNXM_v13-11-fastboot.zip, yes? Or would it be the VEUXG rom?
Click to expand...
Click to collapse
If your model number matches my screenshot. I flashed the file for veux/peux which was a China based ROM. The ROM has been changed to a global base, VEUXG is the one to go for
kacsa105 said:
There are also 4 phones under the VEUXG ROM name. Although the 64-megapixel camera phone Codename peuxp. Unclear, i would also be interested in which one to install
Click to expand...
Click to collapse
To everyone, please don't flash anything without confirming what model your phone is.
The reason I did NOT post the direct download link here is because Xiaomi released a few devices similar and other countries specs vs global might be different too.
kacsa105 said:
There are also 4 phones under the VEUXG ROM name. Although the 64-megapixel camera phone Codename peuxp. Unclear, i would also be interested in which one to install
Click to expand...
Click to collapse
VEUX and VEUXG are the same, I have tried it.
Hientran43 said:
VEUX and VEUXG are the same, I have tried it.
Click to expand...
Click to collapse
Not quite. They had to divide veux device to China and Global due to different NFC HW in both device variants. Meaning if you flash a veux (which I originally had) your NFC may have issues or possibly not even work)
veux=HMNote11EPro
veuxg=HMNote11Pro5G_POCOX4Pro5G
What is the last Xiaomi.eu ROM for x4 Pro? Because I see the 13.0.9 in the download website official of VEUXG devices Xiaomi EU
Works great, downloaded xiaomi.eu rom for redmi note 11 pro 5g, and has a simple tool that installs the rom on it's own without typing out the commands at their websites downloads. Although i did have to follow the guide to flash magisk via fastboot. Thanks
Vincent Foxx said:
Works great, downloaded xiaomi.eu rom for redmi note 11 pro 5g, and has a simple tool that installs the rom on it's own without typing out the commands at their websites downloads. Although i did have to follow the guide to flash magisk via fastboot. Thanks
Click to expand...
Click to collapse
How is the EU ROM ? Any bugs ?
Vincent Foxx said:
Works great, downloaded xiaomi.eu rom for redmi note 11 pro 5g, and has a simple tool that installs the rom on it's own without typing out the commands at their websites downloads. Although i did have to follow the guide to flash magisk via fastboot. Thanks
Click to expand...
Click to collapse
Yup, can simply run their bat files though it's always good to understand some of the basics on using ADB. You're welcome
Inpain said:
How is the EU ROM ? Any bugs ?
Click to expand...
Click to collapse
None that I have noticed, fast and fluid on the latest EU version
1qazwsx4 said:
Yup, can simply run their bwt files though it's always good to understand some of the basics on using ADB. You're welcome
None that I have noticed, fast and fluid on the latest EU version
Click to expand...
Click to collapse
Sweet, cause stock is driving me nuts, sluggish as sh** lol.
Many thanks for your manual. I have POCO X4 5G 8/256 with 13.0.1.0.RKCEUXM firmware, I would like to flash Indonesian one 13.0.2.0.RKCIDXM (without root access) to activate call recording. Does your manual work as well for such upgrade? Thanks
bistron said:
Many thanks for your manual. I have POCO X4 5G 8/256 with 13.0.1.0.RKCEUXM firmware, I would like to flash Indonesian one 13.0.2.0.RKCIDXM (without root access) to activate call recording. Does your manual work as well for such upgrade? Thanks
Click to expand...
Click to collapse
You're very welcome. I can't guarantee that it would work for anything other than MIUI EU ROM but I know as a fact that it has automatic call recording if you choose to flash it instead of Indonesian rom