Develop Bugs

[Guide][DualBootPatcher] Multi Boot for Note Pro 12.2

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
First of all, I want to say big thanks for @chenxiaolong
Only his hard work allowed us to use an easy way to switch firmware.
I just built the debug version of the program with small changes to our tablets, checked it and pulled request to the author.
From today (version 9.1.0.r205.g1dc88ed2) our devices are officially supported.
Supported both devices – SM-P905 (viennalte) and SM-P900 (v1awifi).
SM-P905 - tested by me.
SM-P900 - not checked yet.
Official site: https://dbp.noobdev.io
Source code: https://github.com/chenxiaolong/DualBootPatcher
Official thread: https://forum.xda-developers.com/showthread.php?t=2447534
Here I just want create a small guide, how to use program.
Primary rom – big rom (touchwiz rom), it will be store in system partition. Another roms will eat part of data partition.
Let's see example:
Primary firmware – touchwiz rom (my port or official 5.0.2 firmware) with root.
First additional firmware – lineage 13
Later you can add as many firmwares as you want.
1. Download additional firmwares and gapps (if you need it)
2. Download the most recent snapshot release of Dual Boot Patcher and install it on tablet.
3. Open Dual Boot Patcher and grant root permission. Open menu (3 lines at the top left corner) and go to the ROMs. It will promt set kernel (say yes) or you can press 3 dot menu key and click “Set kernel”. It's should be done only once - Dual Boot Patcher will store boot for primary partition.
4. Then open menu again and go to the “Patch Zip file”. Press “+” at the right bottom corner and then “Add flashable zip”. Chose “lineage 13” zip file. In new small window: Device will be selected automatically (LTE or Wifi version), in the “Partition configuration” select “Data slot” and then enter an ID: “lineage13” for example. In description you will see: “Installs ROM to /data/multiboot/data-slot-lineage13” and press continue. Then program will prompt store new zip file. It's very important: you should store zip in the internal storage. Then you need to start convert (press checkbox at the right top corner).
5. Make item 4 for gapps (on this moment I getting crash of the program, just run program again). When you will enter an ID – it's should be the same as for firmware. If you entering “lineage13” for rom, you should entering “lineage13” for gapps too.
6. Now we have both files in the internal storage. Reboot in TWRP. Very important: just flash both files without ANY wipes and then reboot.
7. Your device will boot into new rom. Install Dual Boot Patcher app and set the kernel for your second ROM as well.
8. Now if you want back to the primary rom – in ROMs menu just press to the primary rom (you will see message: “Successfully switched ROM”) and reboot.
9. If you need more additional roms – repeat items 4-7 with new Data slot ID
10. Wipe additional rom – in ROMs – press 3 dot menu for needed rom – select “Wipe ROM” - and check all items, except last one (“Multiboot files”).
11. Remove additional rom – in ROMs – press 3 dot menu for needed rom – select “Wipe ROM” - and check all items here.
I played yesterday with Dual Boot Patcher, installed 4 roms - it's working great.
Just carefully use guide.

@Valera1978
Awesome news! Thank you for sharing.

---

nick_stokes said:
I ask you to clarify, the patch should be applied to all files? supersu, xposed, any addons? or only ROM and GApps?
Click to expand...
Click to collapse
All files.
The idea is: replace links (mount) to partitions (like system, data, cache) to folder in data partition or sdcard. This is why we need to patch the firmware and additionals in program.
So we need to be careful with the aroma installer that use their own update-binary (not our case).
I checked on the 13.0, 14.1 and my port. All was fine.

---

error message
i clicked 'set kernal' but received an error message "could not determine the boot partition because this device's codename 'v1awifikx' is not recognized"
what should I do? help please.... T_T

TaeJaLee said:
i clicked 'set kernal' but received an error message "could not determine the boot partition because this device's codename 'v1awifikx' is not recognized"
what should I do? help please.... T_T
Click to expand...
Click to collapse
Added the request (https://github.com/chenxiaolong/DualBootPatcher/pull/485) to the author.
I hope soon (today\tomorrow) will be a version with v1awifikx support.

SM-P901 ( v1a3g, v1a3gxx ) not supported, please add too.

Could you add gtanotexlwifikx codename for the Samsung Galaxy Note Pro 12.2 (Wifi) ? Please...

TaeJaLee said:
Could you add gtanotexlwifikx codename for the Samsung Galaxy Note Pro 12.2 (Wifi) ? Please...
Click to expand...
Click to collapse
in patcher choose v1awifi

it occurs error in installing..
I guess because of different codename (T800 <-> P900)
(without dualboot patching, it was installed successfully)

Hi @Valera1978
thanks for this amazing port.
I did successed in flashing my primary ROM (a modified & rooted & bloatware free '5.0.02' Samsung stock rom: LL-5.0.2-TW]CivZ_P900_Lollipop-5.0.2-Rev4.0 [BPA1][Final Release]), then installed the DualBoot app with success and set the kernel -> fine.
Then I patched an unofficial resurrection remix 5.8.5 as multiboot-data-01 with its respective opengapps pico, both with success and flashed them with TWRP also with success.
RR ROM boot and setup are fine!
up to there all is fine.
But then I simply can't install the DualBoot App on my data-01 ROM (the RR 5.8.5). I get an error message saying I can't install (don't have the exact message in mind and I forget to bring my tab with me at work).
what could cause this miss-behavior?
I know I can still swap ROMs with TWRP with the tips you mentionned (did not tried yet as I did not finalized setting up my RR rom).
For folks wanting to try DualBootPatcher on P900 (v1awifi) do not try to install as secondary nor as cashed slots: you simply do not have enough space (well I think I did succesed with a LineageOS on cache but not sure, RR always failed).
This seems to work grand on data slots.
thanks in adance for your help.
Die

Thank you for topic. lineage os of installation is completed and os is running but other files (gapps ) are not installed, error occurs.
Edit: resolved when the latest version of the twrp was installed
https://dl.twrp.me/v1awifi/twrp-3.4.0-0-v1awifi.img.tar.html
Thank you very much it works great.

does someone still has a link to the multiboot patcher?

KHPKero said:
does someone still has a link to the multiboot patcher?
Click to expand...
Click to collapse
hello, you can just search for the realese number and find it that way. There is more newer versions too

Problem updating Huawei Mediapad M2-A01LV100R001C100B006 4G SIM Unlocked - NL

Hi,
Goal is to upgrade my M2, I believe it has a modem because it is able to receive SMS, 4G network, etc...
One thing is missing, calling functionality, dialer stuff ... is this hardware or firmware (or driver not installed)?
Can somebody please confirm or know how these things work?
So I want to upgrade because, I just want to be up to date, new android!
No updates are available if I try the official via EMUI Update way... online at Huawei nothing is available either (they refer to EMUI). It says most current version.
But then I read people from other European countries do have updates installed, 'same' model ... WTF?!?
Version / model : M2-A01L / 2GB
* Everything is still factory.
* EMUI : 3.1
* Android : 5.1.1
* Custom version : CUSTC100D002
* Bootloader version : V100R001C00B000_FASTBOOT
* Kernel version : M2-A01LV100R001C100B006_BOOT
* AP : M2-A01LV100R001C100B006_SYSTEM
* CP Version / baseband : 21.600.20.00.010(balong)
* Cust Version : Cversion:C100 DVersion002
So first things first reading different posts and tutorials about updating:
* https://forum.xda-developers.com/mediapad-m2/how-to/guide-official-updates-m2-tablet-root-t3589363
* https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
Im already stuck at the official steps:
1 - On tablet created folder : InternalStorage/HwOUC placed M2-A01LV100R001C100B007.zip and rename in update.zip
2 - Turn off , Reboot device (not connected to laptop) , should automatically install update above. Nothing happens.
So lets try bootloader maybe I can choose to update from folder or something. Nope, just 3 options, (reboot:wipe cache:factory)
Strange... Im wondering
1 - If they disabled something so updating is not possible at all?
2 - Other possibility in the forum, update.app in dload... people mention the process got stuck on 2%. Can you get back to original, it just fails or do you need to do a factory reset to get a working tablet again?
3 - What steps to take to make sure you can always... yes, always get back to your factory firmware when updating.
4 - Then I was reading about simply download to a full firmware (not an update)
HUAWEI_MediaPad+M2+10.0_M2-A01L_Firmware_Android+5.1.1_EMUI+3.1_V100R001C100B010CUSTC100D001_Germany_Spain_Belgium.zip
Not Netherlands... Im not 100% confident this is the way to go. Last part of the filename D001_German... mine is D002, so, aaargh
I hope you can guide me and help me updating. I dont know much about this, is it really chipset, hardware or just software (compilation) stuff...

jesperrekuh said:
Hi,
Im already stuck at the official steps:
1 - On tablet created folder : InternalStorage/HwOUC placed M2-A01LV100R001C100B007.zip and rename in update.zip
2 - Turn off , Reboot device (not connected to laptop) , should automatically install update above. Nothing happens.
So lets try bootloader maybe I can choose to update from folder or something. Nope, just 3 options, (reboot:wipe cache:factory)
Click to expand...
Click to collapse
Making progress ... step:
0 - Back to factory settings, yes wipe that thing and let's see... then:
1 -
a - Unpacked M2-A01LV100R001C100B007.zip placed in internal storage/dload. Settings > Update > menu > local update. Package found, rebooting, installing, SUCCESS, rebooting again.
b - Open Settings > About Tablet > look at buildnr... A01LV100R001C100B006 didn't change, huh. repeated steps above...
Lets's see what happens if go to OTA-M2-A01LV100R001C100B010.zip, same steps... and after updating process. nothing changed, still the same ... A01LV100R001C100B006 ...
So somehow the manual local update looks into dload folder > changes the boot procedure to update > then looks into a factory prepped setting > updates to its original and no version change.
Edit:
Placed file 007 in internal storage > dload , powered off , then I did :
Vol + UP and Vol - Down and PowerOn buttons, waited until I got the installing EMUI screen.
Nope, nothing changed.

YESSSSS , SUCCESS :good: read!!! (and above)
- Tablet (bought in the Netherlands) - Huawei M2 10" - A01L :
* Custom version : CUSTC100D002
* Bootloader version : V100R001C00B000_FASTBOOT
* Kernel version : M2-A01LV100R001C100B006_BOOT
* AP : M2-A01LV100R001C100B006_SYSTEM
This is what I did :
- Factory reset, tried to update B006 -> B007 -> B010, nothing seemed to be changed although it said success ...
- Not rooted, no TWRP, not Developer or Manufacturer mode... just basic.
Then downloaded rom in this topic :
https://forum.xda-developers.com/mediapad-m2/development/rom-m2-a01l-lte-premium-stock-t3624094
Huawei 10 - M2 A01L - B010 LTE file
- sdcard in tablet (not internal storage)
- create folder dload
- unzip file (above) and place the contents of the extracted file and its subfolder dload into this.
- the folder contained file UPDATE.APP and hw folder. Total size 3.3GB.
- Power down
- Unplug all cables
- Check if you have sufficient power >50%
- VolUp + and VolDown - and PowerOn, wait until EMUI Install screen, takes around 15-20seconds.
- Install starts until finished, 15minutes. Slow progress.
- Looks like it hangs on 99% but wait for success
Et voila, from B006 -> B010 and yes, including dialer... made a phonecall...
Next is rooting...

As I was saying... ROOTING, success again.. what ... a .... day !!!
My Steps :
0. Did above... don't forget
1. Follow these steps and pay 4 credits : Steps to Unlock, Recovery and Root
- Manufacturer mode to get the unlock code, back to hiSuite mode
- Command line tools for windows : ADB and fastboot
- Follow the exact procedure , step 18.
2. Troubles finding the files you need:
- TWRP for Android 5.1.1 More information can be found link here
- SuperSu

Enabling call on M2-801L
jesperrekuh said:
As I was saying... ROOTING, success again.. what ... a .... day !!!
My Steps :
0. Did above... don't forget
1. Follow these steps and pay 4 credits : Steps to Unlock, Recovery and Root
- Manufacturer mode to get the unlock code, back to hiSuite mode
- Command line tools for windows : ADB and fastboot
- Follow the exact procedure , step 18.
2. Troubles finding the files you need:
- TWRP for Android 5.1.1 More information can be found link here
- SuperSu
Click to expand...
Click to collapse
I read your post with interest. I was trying to do exactly the same thing i.e. enable the calling features on my M2-801L.
Eventually got my tablet fully working and your post helped a lot!!
So thanks for posting the info.

[Guide] ALLDOCUBE X NEO Flash Class 101

Hello and welcome here.
I’m Warren, an X NEO user from Mainland China .
X NEO is a great device that opens all low-level permissions to users, but it is undeniable that it is far more difficult to flash than Xiaomi's devices, especially the logic of the A/B partition。
Fortunately, through the help of many people, I successfully overcome many difficult problems, and now I decided to write a Thread like a guide book to integrate some basic knowledge of the flash to X NEO.
Each part of this post will contain the following:
a) Materials needed for flashing
b) Instructions for flashing steps
c) Possible problems and solutions

Attention !!
a) I will spend some time (maybe a few days?) to update everything
b) All content is written in simplified Chinese and translated into English by Google translation machine for reading. This is due to forum restrictions
c) Due to the use of machine translation, the grammar and vocabulary are unavoidably rigid, and I don’t want to manually proofread him for the time being. Because I don’t have enough energy, I have written the original document as closely as possible to the English writing logic
d) I understand English, so I can send out any questions or private messages without worry
e) The content of the post is my own original, but many materials and ideas are provided by users at home and abroad, including several masters from XDA and hardware forums. I just did some trivial sorting and reproduction work, here Thank them for their hard work
f) Have fun

#0 Preparation
Step 1 Download materials & prepare environment
This part is very important, it will be directly related to the success or failure of subsequent work (because of lack of necessary environment or materials)
How to do?
1. Save the file in this MEGA address: HnwhAIhJ#uVaWZIzUOUcAIwAbcrNMsg
2. Download ADB
3. Unzip (you can move the unzipped folder to any place you like)
4. Remember this path. Anytime I say "Run an ADB command/open ADB input", you can open this path, right-click on the blank space of the folder to open the command prompt book and enter the command.
5. Download Magisk on github
Step 2 Flash your device to the Chinese version of the firmware
a) This is because the Chinese version of the firmware is more modifiable than the overseas version
b) The following content will be based on the "200522" firmware (I know this is not the latest, but the updated version has not been confirmed by me)
c) If you insist on downloading the latest firmware, you can go to the official website of Cube China
How to do?
1. Download "XNeo(T1009)-Android9.0-200522-Firmware&Tutorial.rar" in the "Firmware-China" folder of MEGA and unzip it
2. Follow the official instructions in the folder (documents in the root directory) to flash the firmware
note:
a) The device can and can only be flashed in Qualcomm 9008 mode (the official data cable supports this function)
b) The official instruction book is in simplified Chinese, if you don’t understand Chinese, translate it
Step 3 Confirm ADB environment and OEM unlock
How to do
1. Open ADB
2. Type "ADB" and press Enter (the self-check information indicates that the environment is established successfully)
3. Turn on the tablet
4. Enter Settings-System-About Tablet
5. Click the version number until the floating prompt appears
6. Go back to the upper level (system) and enter the developer options
7. At this time, "OEM Unlock" should be opened automatically and cannot be changed
8. Click to open "USB debugging" and connect to the computer to activate the function according to the prompts
9. Click to open "Verify App via USB" to activate the function

#1 Official system customization
a) First of all, the official version of the system is a typical simple ASOP system based on Android 9. It is not much different from third-party customized systems such as Los to a certain extent. If you don’t want to be too tossed, you can use it directly after optimization according to the following guidelines
Step 1 Brush into third-party REC (TWRP)
a) N/A
How to do it?
1. Download "TWRP-CUBE_X_Neo-20200522.img" in the "TWRP" folder in MEGA
2. Copy to the path of ADB
3. Open ADB
4. Type "adb devices" and press Enter
5. Type "adb reboot bootloader" and press Enter
6. Type "fastboot flash boot_a .\recovery.img" and press Enter
7. Enter "fastboot flash boot_b .\recovery.img" and press Enter
8. The flashing completion prompt is displayed twice
9. Now that TWRP has been successfully swiped in, you can enter the recovery mode through the volume button and power button
note:
a) Flashing into a third-party REC will cause OTA failure (over-the-air upgrade is not possible)
Step 2 Flash into Magisk
a) Have Root permissions
b) Flash into the module
c) Conveniently flash into the XP framework
How to do?
1. Enter rec
note:
a) You can use the same method to flash in GAPPS components (Google and download by yourself) to use GMS components and related services
b) Magisk version 21.0 is recommended, which is beautiful and will not automatically fail
c) Recommended modules: font module, scheduling module (search and download by yourself)
Step 3 Flash into the XP framework
a) Use certain software/modules that require special permissions and environments
How to do?
1. Open Magisk
2. Go to the online module library that comes with Magisk
3. Find the Riru-Core module to download and install
4. Find the Riru-EDxposed module to download and install
5. Restart the phone
6. Install and open Edxposed Manger (Google and download by yourself) to activate the module
7. Restart the phone
8. Success
note:
a) Edxposed chooses the YAHAFA version instead of the SANDHOOK version
b) Recommended modules: Youtube background playback related, exercise count modification related, camouflage location related, social software beautification and additional functions related
Step 4 Install auxiliary software
a) Green Guardian: Clean up the background and make 4G memory run smoothly (GooglePlay recommends buying genuine)
b) Streamlined version of fluid gesture software (increase system-level full-screen gestures)
c) Force to rotate the old version of the software (add system-level software horizontal screen support)
d) The download links of the above two apps are too low and I can’t send them out. You can get them by private message
Step 5 Uninstall pre-installed third-party software
a) Complete through a third-party software manager
b) The system software can also be appropriately streamlined (pay attention to safety)

[GUIDE] IMEI / Connection Repair on Asus Zenfone 2E ZE500CL Z00D

[GUIDE] IMEI / Connection Repair on Asus Zenfone 2E ZE500CL Z00D
I am writing this guide because I recently recovered a bricked ZE500CL and after flashing around so many different files I lost my IMEI and connection abilities. After a little research and some thought I easily repaired my IMEI and restored my connection abilities. Just follow the steps below. I don't have this phone long and I am still learning so some of these steps might not be needed. Nevertheless it DOES work if you follow it properly.
What you will need:
1) Asus Flash Tool - https://drive.google.com/open?id=1n7tJr7lAlPnL8-nmK8f5kGmDHbRv5gxo
2) Asus Phone Drivers - https://drive.google.com/open?id=11XLRW5pEScYdBYwh0vDM-Wup9orGPWDf
3) Debug Service Firmware - https://drive.google.com/open?id=1ISofitM3yhYpu46JD0KWGLXybvtLQyAy
4) Intel Phone Tool - https://drive.google.com/open?id=1dQjjlHjWs8tDrfNU_ikgesKK2uKaTyXt
5) Intel Drivers - https://drive.google.com/open?id=1hE9j35VMOD5QGHjDy_aM2vVCs2PVOOm1
6) ADB / Fastboot Tools - https://drive.google.com/open?id=1nbAS8k4JMAXG8YH2qIFHpRjX60TTlYIt
7) IMEI Number - You should have this. If not generate one based off another ZenFone 2E Z00D's IMEI.
8) ZenFone Root Tool - https://drive.google.com/open?id=1NHf516Yex9KfsnufVNz0vkchJWCiMHo2
9) Root File Browser (ES File Explorer, Root Browser etc) - Get from the internet, place on your phone via MTP file transfer or push/install it in adb.
NOTE: If you choose the first way you will have to go into your debugging app in the applications. It will be the one with the magnifying glass and says Asus Log something on it. I no longer have the Service Firmware installed so I can't remember. You will find it though. Once you do go in and find the usb settings and just change modes and you will see the drivers install and device ASUS_Z00D or something similar should appear in device manager under devices. If it fails to load make sure you have the correct ASUS Drivers installed and if that doesn't work the last way is to select the ( ! )Driver and then manually install the USB MTP Device driver which will fix the issue.
10) Factory Folder Backup (This MIGHT not all be needed, still checking to make sure.. for now include it) - https://drive.google.com/open?id=1fvH0QdrzLFM34vsm2KNfQBU5fr8eSM14
First Step:
Download everything above and then install 6,2,5,4 (Install the drivers that come with Intel Tool before installing it. You should be prompted during installation) and then install 1.
Second Step:
Open Asus Flash Tool and make sure your phone is connected to the computer and you are in fastboot mode.
You can get there 2 ways. (1) Turn the phone off, hold Vol+, then push the power button, and when you feel it vibrate release the power button while holding Vol+. (2) Open command prompt and enter "adb reboot bootloader" (this is if you're adb is setup system wide, if not navigate to your SDK Tools folder and enter there).
Flash the Debug Service Firmware you downloaded. Check WIPE to wipe before flashing.
Once you see the phone boot up goto the next step.
Third Step:
Open Intel Phone Tool and follow this guide here to fix your IMEI! -
NOTE: You can skip the setprop commands he enters into adb shell in command prompt. This firmware already has the COM Port opened and USB Debugging enabled for you.
Fourth Step:
Now you will need to root your phone using the Root Tool I linked in the beginning (Do not worry about upgrading the SuperSU Binary.) Next you will need to install a root browser on your phone like ES File Browser, Root Browser etc. Something that allows access to root / hidden files. Navigate to /Factory and /Config and backup these two in their entirety to your MicroSD card or computer. Replace your factory with mine if it is empty and doesn't contain the files in the steps below. Now comes time to edit. Makes these changes to the files. (I am not 100% sure which all DO need to be made so I just modified most all of the values.)
These instructions are thanks to @BORETS24
I have changed them a tad as our handset differs from the one he wrote them for. I am still not entirely sure if everything needs to be copied/modified. Don't have a lot of spare time on this handset to figure out everything. I just know from testing this will get your phone functioning again.
Serial number, WI-MAC, BT-MAC repair instructions
(You will be replacing everything after step 5. Below explains what to edit.)
1. If you have an empty factory partition, use the archive, replace factory folder with archive version to root file system via file manager, ES File Explorer or others (root required and root browsing required of the application). Serial Number, WiFi MAC, BTMAC, colorID you may see on box from phone (or make up something for each value). .. you can generate the WiFi MAC based off these Unassigned? Assignments - 00:90:4C, 00:09:4C or just make one up based off a random Assignment from here - https://regauth.standards.ieee.org/standards-ra-web/pub/view.html#registries. For the Bluetooth - 22:22:AF or something you find on the previous site. You can check easier after you generate here - http://www.coffer.com/mac_find/. For color ID I left mine the same as what is in the factory.zip which is Silver.
2. Then open and edit factory/PhoneInfodisk/bt_addr.conf- this BT MAC, replace 00:00:00:00:00:00 numbers to your MAC.
3 Then open and edit factory/PhoneInfodisk/colorID- color code of your phone. For example silver is 6J.
4. Then open and edit factory/PhoneInfodisk/PhoneInfo_inf- 6F0000000 (yours will be 12 numbers) replace to your serial number, 1C002C... change to you BT-MAC, 00B72... change to your WiFi MAC, 6J change to your color code, RU... change to US,EU,CN,TW,RU (do not think this matters much). I changed mine to US I think.
5. Then open and edit factory/PhoneInfodisk/ssn- enter your serial number replacing 0000000. (12 numbers)
6. Then open and edit factory/wifi/mac.txt- enter your WiFi MAC replacing 00000.
Fifth Step:
Open Asus Flash Tools and flash desired build of RAW firmware over the Debug Service Firmware. I suggest the latest WW firmware which is ver .126. From here you can stay on this firmware after replacing the files below or surf around XDA and find out what customized ROMS are available for this phone. Personally I unlocked my Bootloader, flashed TWRP, flashed .126, flashed Resurrection Remix 5.8.4 ? on Nougat 7.1.1 and then flashed a SU. RR I wouldn't recommend as it is buggy and neither would I of MoKee as it is buggy as well. I am fixing the bugs in RR so it runs fine as I particularly like RR over others since it comes pre installed with a horde of features so you can customize your handset to your hearts desire.
1. Install a root File Browser and root your phone again.
2. Replace /config with your backed up /config.
3. Replace /factory with your backed up /factory.
4. Reboot.
Now check everything in settings and make sure it looks right. All should look A-OK except for serial #. I am still working on that and will edit this once I finish. Layout of our phone is different than the one I took files from. You might have to replace the file again if you flash certain custom ROM's. I flashed RR and didn't have to.
EDIT: After a few reboots I seem to lose my MAC's again and the serial (unknown) is replaced by Medfield1534DD97. Both WiFi and BlueTooth still work though. You just have the random default generated MAC's. I can live with that as long as it works. Though if anyone can shed some light on this issue or anything else I would be extremely grateful.
Enjoy Your Phone!
-------------
For the Asus Zenfone 2E ZE500CL Z00D I will be uploading in the near future somewhere an organized package compiled of all recoveries, roms custom + stock firmware, root, bootload unlockers, tools, apps and guides all together so you can easily download and skip the time consuming research I had to endure. It is around 10GB. I am officially done learning this phone now. It has been a long 3 days and now it is time to ship it out to a buyer. =]
XDA: noidodroid

Question How to convert asus rog phone 6 pro chinese version to global rom?

how to convert asus rog phone 6 pro chinese version to global rom?

root the phone then flash it, but i dont think there is anyway to root it

concorduser said:
root the phone then flash it, but i dont think there is anyway to root it
Click to expand...
Click to collapse
until now still dont have 1 proper guide to root for 6 pro

I can not found any Official guide for How to convert. Old method worked for Rog 2 is not work anymore on Rog 6.
Found COUNTRY code file and already modified it into WW but fingerprint appeared on phone still remain at CN (with re-flash the whole system package (holos - dallas/texas.raw).
But you can still do following step to gain Device is certified on Play Store and eat FOTA update.
1. Flash WW rom (full rom not OTA), finish all set up.
2. Root your phone, by using Magisk.
(unlock bootloader via official apk from Asus, install Magisk Manager.apk, copy and place original boot.img on your phone and use Magisk Manager on phone to patch it, using CMD and fastboot command on PC to flash boot magisk patched.img, now you have rooted phone with magisk.)
3. With root explorer, navigate to /vendor/factory/COUNTRY open and edit CN to WW.
4. Re-flash WW if you want to make sure if there is any change on your phone. (My vendor fingerprint still not changed into WW).
5. Now you have WW rom on tencent hardware but Play store remain "Device is not certified".
6. Install termux and some modules on Magisk as: MagiskHide Props Config (must have), SElinux permissive (optional), Systemless Hosts, Universal SafetyNet Fix (must have), zygisk - SUI (optional).
7. After reboot your phone, come back to Magisk to make sure MagiskHide Props Config is properly installed. Then open Termux and typing:
su
props
- A short list is appeared on Termux, and you typing 1 to choose option "1 - Edit device fingerprint." then enter
- Choose "f" next to pick option "f - pick a certified fingerprint". then enter
- Choose next "1" to pick up "Asus". then enter
- Choose next "2" to pick up "ROG phone 5" then enter
- Choose next "Yes" to confirm and reboot phone.
Your phone is going to reboot and do a normal clear cache/data with Play Store to force Play Store recognize new status of your phone. Even download and install safetyNet test/check to make sure every thing is green.
Now your phone could eat up FOTA update, not OTA update. But please re-do the patched boot.img with Magisk Manager everytime you do an update by FOTA.
PS: difference between FOTA and OTA is:
FOTA - download update file from Asus HomePage, place it on root of your /SDcard folder, reboot phone and an update notification will show, do an update and it will success.
OTA - download directly via system/system update.
I will add credit later. All that works above is not belong to me.

tuannghia1985 said:
I can not found any Official guide for How to convert. Old method worked for Rog 2 is not work anymore on Rog 6.
Found COUNTRY code file and already modified it into WW but fingerprint appeared on phone still remain at CN (with re-flash the whole system package (holos - dallas/texas.raw).
But you can still do following step to gain Device is certified on Play Store and eat FOTA update.
1. Flash WW rom (full rom not OTA), finish all set up.
2. Root your phone, by using Magisk.
(unlock bootloader via official apk from Asus, install Magisk Manager.apk, copy and place original boot.img on your phone and use Magisk Manager on phone to patch it, using CMD and fastboot command on PC to flash boot magisk patched.img, now you have rooted phone with magisk.)
3. With root explorer, navigate to /vendor/factory/COUNTRY open and edit CN to WW.
4. Re-flash WW if you want to make sure if there is any change on your phone. (My vendor fingerprint still not changed into WW).
5. Now you have WW rom on tencent hardware but Play store remain "Device is not certified".
6. Install termux and some modules on Magisk as: MagiskHide Props Config (must have), SElinux permissive (optional), Systemless Hosts, Universal SafetyNet Fix (must have), zygisk - SUI (optional).
7. After reboot your phone, come back to Magisk to make sure MagiskHide Props Config is properly installed. Then open Termux and typing:
su
props
- A short list is appeared on Termux, and you typing 1 to choose option "1 - Edit device fingerprint." then enter
- Choose "f" next to pick option "f - pick a certified fingerprint". then enter
- Choose next "1" to pick up "Asus". then enter
- Choose next "2" to pick up "ROG phone 5" then enter
- Choose next "Yes" to confirm and reboot phone.
Your phone is going to reboot and do a normal clear cache/data with Play Store to force Play Store recognize new status of your phone. Even download and install safetyNet test/check to make sure every thing is green.
Now your phone could eat up FOTA update, not OTA update. But please re-do the patched boot.img with Magisk Manager everytime you do an update by FOTA.
PS: difference between FOTA and OTA is:
FOTA - download update file from Asus HomePage, place it on root of your /SDcard folder, reboot phone and an update notification will show, do an update and it will success.
OTA - download directly via system/system update.
I will add credit later. All that works above is not belong to me.
Click to expand...
Click to collapse
thanks