Flash Xiaomi Qin F22 pro (stock firmware with Google Play , with and without ROOT)

Search This thread

izyer

Senior Member
Jun 7, 2017
71
12
I unpacked all files super.bin and Rom~.
Onec i open mtkclient
I didn’t find flash flashboot to choose the file
Sorry if I disturb you
There’s any other tool to flash this rom
Thx
🌹
Do it without MTKCLIENT.

Enable the USB Debugging option under Settings > Developer options.

Developer options is hidden by default; use the following steps:

  1. On the device, go to Settings > About <device>.
  2. Tap the Build number seven times to make Settings > Developer options available.
  3. Then enable the USB Debugging option. (From Developer options)
Then connect your phone to your computer and enter flashboot mode.
You can find a way of doing it here: @ https://www.hovatek.com/forum/thread-19503.html

unpack 42.super.img and u will get system_a.img (+others)

adb reboot fastboot (this will reboot your phone in fastboot)

fastboot reboot fastboot (this will go in mode that you can flash system.a.img )

fastboot flash system_a system_a.img
fastboot flash system_b system_b.img

.... do that for all the files.
 
  • Like
Reactions: kamil.syria

kamil.syria

Member
Dec 9, 2015
25
1
Do it without MTKCLIENT.

Enable the USB Debugging option under Settings > Developer options.

Developer options is hidden by default; use the following steps:

  1. On the device, go to Settings > About <device>.
  2. Tap the Build number seven times to make Settings > Developer options available.
  3. Then enable the USB Debugging option. (From Developer options)
Then connect your phone to your computer and enter flashboot mode.
You can find a way of doing it here: @ https://www.hovatek.com/forum/thread-19503.html

unpack 42.super.img and u will get system_a.img (+others)

adb reboot fastboot (this will reboot your phone in fastboot)

fastboot reboot fastboot (this will go in mode that you can flash system.a.img )

fastboot flash system_a system_a.img
fastboot flash system_b system_b.img

.... do that for all the files.
I think my problem from mtkclint
I will try with out it
 

kamil.syria

Member
Dec 9, 2015
25
1
Do it without MTKCLIENT.

Enable the USB Debugging option under Settings > Developer options.

Developer options is hidden by default; use the following steps:

  1. On the device, go to Settings > About <device>.
  2. Tap the Build number seven times to make Settings > Developer options available.
  3. Then enable the USB Debugging option. (From Developer options)
Then connect your phone to your computer and enter flashboot mode.
You can find a way of doing it here: @ https://www.hovatek.com/forum/thread-19503.html

unpack 42.super.img and u will get system_a.img (+others)

adb reboot fastboot (this will reboot your phone in fastboot)

fastboot reboot fastboot (this will go in mode that you can flash system.a.img )

fastboot flash system_a system_a.img
fastboot flash system_b system_b.img

.... do that for all the files.
Brother thanks a lot for your time
I try to do this👆🏻 but i get error msg same like a picture
Then i go to flash super.bin
Everything is okay
But still I have cracked with Bluetooth
Not open (this old problem)
Everything working good also i got play store but google keyboard is crashed
How i can get all languages
 

Attachments

  • 9B89B1D6-AB3C-4B43-B1EF-30C49166F1DC.jpeg
    9B89B1D6-AB3C-4B43-B1EF-30C49166F1DC.jpeg
    2.8 MB · Views: 35

izyer

Senior Member
Jun 7, 2017
71
12
Brother thanks a lot for your time
I try to do this👆🏻 but i get error msg same like a picture
Then i go to flash super.bin
Everything is okay
But still I have cracked with Bluetooth
Not open (this old problem)
Everything working good also i got play store but google keyboard is crashed
How i can get all languages
fastboot flash system_a system_a.img
 
  • Like
Reactions: kamil.syria

bsoklev

Member
Dec 1, 2022
7
4
Hello,
I tried all of the methods but it neither work for me. Sequence of events as follows:
I got the phone and took a full backup by dumping the whole flash using mtkclient.
Extracted super.rar and used mtkclient to flash super.bin - after reboot phone boots to bootloader. There is no way to clear cache/data from the phone so I do fastboot -w. Same thing - phone boots to bootloader.

Flash from backup and phone boots OK.
Flash the 1.0.7_unlocked and phone boots OK to 1.0.7.

Flash super.bin again and once more phone boots to bootloader.
Flash 1.0.7 again - phone boots normally.
Flash super.bin using fastboot - access denied.
Use mtkclient to unlock the bootloader - phone boots with warnings.
Flash super.bin using fastboot - phone locks on bootscreen and gets really hot.
Flash 1.0.7 again - phone boots normally.
Unpack super.bin and got system_a.ext file
Flash system_a.ext with fastboot - phone locks on bootscreen and gets really hot.
Flash 1.0.7 again - phone boots normally.
Unpack super.img from 1.0.7 and got a system_a.img file.
Flash system_a.img file using fastboot - phone locks on bootscreen and gets really hot.

So, basically anything flashed with fastboot bricks the phone, super.bin flashed with mtkclient makes the phone to boot to bootloader.

The only thing that I am not sure how to do is how to properly unpack the bin or img files on windows so I do it on my macbook using Keka.
Any suggestion would be appreciated.
 

kamil.syria

Member
Dec 9, 2015
25
1
Do it without MTKCLIENT.

Enable the USB Debugging option under Settings > Developer options.

Developer options is hidden by default; use the following steps:

  1. On the device, go to Settings > About <device>.
  2. Tap the Build number seven times to make Settings > Developer options available.
  3. Then enable the USB Debugging option. (From Developer options)
Then connect your phone to your computer and enter flashboot mode.
You can find a way of doing it here: @ https://www.hovatek.com/forum/thread-19503.html

unpack 42.super.img and u will get system_a.img (+others)

adb reboot fastboot (this will reboot your phone in fastboot)

fastboot reboot fastboot (this will go in mode that you can flash system.a.img )

fastboot flash system_a system_a.img
fastboot flash system_b system_b.img

.... do that for all the files.
Follow this
It’s done ✅ with me Qin F22 Pro
 

izyer

Senior Member
Jun 7, 2017
71
12
Hello,
I tried all of the methods but it neither work for me. Sequence of events as follows:
I got the phone and took a full backup by dumping the whole flash using mtkclient.
Extracted super.rar and used mtkclient to flash super.bin - after reboot phone boots to bootloader. There is no way to clear cache/data from the phone so I do fastboot -w. Same thing - phone boots to bootloader.

Flash from backup and phone boots OK.
Flash the 1.0.7_unlocked and phone boots OK to 1.0.7.

Flash super.bin again and once more phone boots to bootloader.
Flash 1.0.7 again - phone boots normally.
Flash super.bin using fastboot - access denied.
Use mtkclient to unlock the bootloader - phone boots with warnings.
Flash super.bin using fastboot - phone locks on bootscreen and gets really hot.
Flash 1.0.7 again - phone boots normally.
Unpack super.bin and got system_a.ext file
Flash system_a.ext with fastboot - phone locks on bootscreen and gets really hot.
Flash 1.0.7 again - phone boots normally.
Unpack super.img from 1.0.7 and got a system_a.img file.
Flash system_a.img file using fastboot - phone locks on bootscreen and gets really hot.

So, basically anything flashed with fastboot bricks the phone, super.bin flashed with mtkclient makes the phone to boot to bootloader.

The only thing that I am not sure how to do is how to properly unpack the bin or img files on windows so I do it on my macbook using Keka.
Any suggestion would be appreciated.
If you are flashing the super.bin (from super.rar) you cant flash it with mtkclient only from fastboot.

You have 2 options, first option is to:

boot your phone to fastboot

adb reboot fastboot

fastboot flash super super.bin

fastboot reboot

After this if your phone boots into the fastboot again type:

fastboot reboot fastboot (with this you will get into the menu where you can WIPE your data)

Second option:

unpack super.bin

adb reboot fastboot

fastboot reboot fastboost

fastboot flash system_a system.a.img (do this for all the files)

reboot the phone, if your phone boots again into fastboot do

fastboot reboot fastboot

wipe your data.

Done

What version did you had that you backed up with mtkclient? Can you share your backup? (without userdata or whats its called , thats unnecesary and it has 50GB) Maybe i can make one good ROM combining them.


adb reboot fastboot
 
  • Like
Reactions: kamil.syria

bsoklev

Member
Dec 1, 2022
7
4
If you are flashing the super.bin (from super.rar) you cant flash it with mtkclient only from fastboot.

You have 2 options, first option is to:

boot your phone to fastboot

adb reboot fastboot

fastboot flash super super.bin

fastboot reboot

After this if your phone boots into the fastboot again type:

fastboot reboot fastboot (with this you will get into the menu where you can WIPE your data)

Second option:

unpack super.bin

adb reboot fastboot

fastboot reboot fastboost

fastboot flash system_a system.a.img (do this for all the files)

reboot the phone, if your phone boots again into fastboot do

fastboot reboot fastboot

wipe your data.

Done

What version did you had that you backed up with mtkclient? Can you share your backup? (without userdata or whats its called , thats unnecesary and it has 50GB) Maybe i can make one good ROM combining them.


adb reboot fastboot

Unpack super.rar -> super.bin ✅
adb reboot fastboot ✅
fastboot flash super super.bin ✅
fastboot reboot ✅
⬇️
1670078267100.jpg

fastboot reboot fastboot ✅
⬇️

1670078267114.jpg

There is no option to WIPE from this screen!
fastboot -w ✅
I get first picture - blank screen with "=>FASTBOOT mode"



If I unpack super.bin and do
fastboot flash system_a system_a.img
fastboot flash product_a product_a.img
fastboot flash vendor_a vendor_a.img
fastboot reboot
⬇️

1670080593583-1.jpg


Phone locks on the this screen and gets very warm

I may have different phone type or bootloader or something else is different but I just can't get it to work.

Link to my dumped ROM V1.1.0
 

izyer

Senior Member
Jun 7, 2017
71
12
Unpack super.rar -> super.bin ✅
adb reboot fastboot ✅
fastboot flash super super.bin ✅
fastboot reboot ✅
⬇️
View attachment 5776261
fastboot reboot fastboot ✅
⬇️

View attachment 5776263
There is no option to WIPE from this screen!
fastboot -w ✅
I get first picture - blank screen with "=>FASTBOOT mode"



If I unpack super.bin and do
fastboot flash system_a system_a.img
fastboot flash product_a product_a.img
fastboot flash vendor_a vendor_a.img
fastboot reboot
⬇️

View attachment 5776275

Phone locks on the this screen and gets very warm

I may have different phone type or bootloader or something else is different but I just can't get it to work.

Link to my dumped ROM V1.1.0
Select Enter recovery when you get to that menu.

Edit: In worst case scenario you can flash everything from ROM 1 0 7 less super.img then only flash super.bin, i did it on mine and it worked.

Edit2: Both ways of flashing its good that after the flash you do

fastboot reboot fastboot

Enter Recovery

Wipe
 

izyer

Senior Member
Jun 7, 2017
71
12
Unpack super.rar -> super.bin ✅
adb reboot fastboot ✅
fastboot flash super super.bin ✅
fastboot reboot ✅
⬇️
View attachment 5776261
fastboot reboot fastboot ✅
⬇️

View attachment 5776263
There is no option to WIPE from this screen!
fastboot -w ✅
I get first picture - blank screen with "=>FASTBOOT mode"



If I unpack super.bin and do
fastboot flash system_a system_a.img
fastboot flash product_a product_a.img
fastboot flash vendor_a vendor_a.img
fastboot reboot
⬇️

View attachment 5776275

Phone locks on the this screen and gets very warm

I may have different phone type or bootloader or something else is different but I just can't get it to work.

Link to my dumped ROM V1.1.0
Does WiFI and bluetooth work in your ROM?
 

bsoklev

Member
Dec 1, 2022
7
4
Does WiFI and bluetooth work in your ROM?
Yes, WiFi and Bluetooth work. Microphone seemed OK when I was testing. I can't test VoWiFi and VoLTE as my service provider supports just handful of phones.

By the way, I still can't flash super.bin. When I do as you suggested - go to recovery and wipe then reboot and the phone boots to bootloader again and again.

I went as far as trying to create my own super.img partition by re-packaging the system_a.img, product_a.img and all the other files using lpmake tool, but initial tests are not promising either.
 
  • Like
Reactions: izyer

izyer

Senior Member
Jun 7, 2017
71
12
Yes, WiFi and Bluetooth work. Microphone seemed OK when I was testing. I can't test VoWiFi and VoLTE as my service provider supports just handful of phones.

By the way, I still can't flash super.bin. When I do as you suggested - go to recovery and wipe then reboot and the phone boots to bootloader again and again.

I went as far as trying to create my own super.img partition by re-packaging the system_a.img, product_a.img and all the other files using lpmake tool, but initial tests are not promising either.
Did you try to flash everything from ROM 1.0.7_unlocked (with mtkclient) and boot up in 1.0.7 then flash the super.bin ? (i think you need the bootloader from 1.0.7. but be sure on startup to select first option , second its student mode that replaces the bootloader somehow)

I hope we can get that 1.9.8 firmware soon, it seems to have everything.
 
Last edited:

gaguga

Senior Member
Nov 1, 2014
111
78
You can test with this, https://romprovider.com/xiaomi-qin-f22-pro-firmware-support/, its same as mine but no google play. Its the full rom unlocked, wifi still doesnt work. With this rom if i select "student mode" i can update the phone OTA to v3.0.2 or something and everything works but you cant install any apps, if we could merge them somehow... , I did try to grab only the system_a.img and flash it but the phone wont work after, i can cross flash the system_a.img from my google play rom to the one i shared but after update it doesnt work anymore (to crossflash).
This is my full backup.
It's for phone recovery.
See how to use it here.
 

Attachments

  • Android_scatter_Fastboot4_64.txt
    1.5 KB · Views: 14
  • Like
Reactions: izyer

bsoklev

Member
Dec 1, 2022
7
4
the process is the same
Can you take a full dump of your phone with mtkclient ?


See the video and the link in the description of the video to download version (works only on windows) of mtkclient which doesn't need Python3. Install driver and the mtkclient gui.
Power off the phone, press volume down and power button and simultaneously plug in the phone to the usb of your laptop/pc. Keep buttons pressed until you get a bunch of stuff appearing in the console then release buttons. Then go to "read partitions(s)" tab and select everything except the "userdata" partition. When you get all partitions downloaded to your laptop, then compress them and share here.
 
  • Like
Reactions: izyer

izyer

Senior Member
Jun 7, 2017
71
12
Can you take a full dump of your phone with mtkclient ?


See the video and the link in the description of the video to download version (works only on windows) of mtkclient which doesn't need Python3. Install driver and the mtkclient gui.
Power off the phone, press volume down and power button and simultaneously plug in the phone to the usb of your laptop/pc. Keep buttons pressed until you get a bunch of stuff appearing in the console then release buttons. Then go to "read partitions(s)" tab and select everything except the "userdata" partition. When you get all partitions downloaded to your laptop, then compress them and share here.
He has F21 pro not F22 pro :) its not useful for us.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Thanks to everyone who is adding his skills to have a good working ROM for this apparently great phone.

    I'm looking forward to buying this model but I need to know what 3G and 4G Bands it's working on, and if you can add bands if they are missing, like it was possible with MTK toolbox a few years back. I'm in europe and my country is for example on B20 4G band, wich isn't listed on any of the aliexpress seller.

    Bands needed:
    3G -> B1 (2100 MHz), B8 (800 MHz)
    4G -> B1 (2100 MHz), B3 (1800 MHz), B20 (800 MHz)
    optional: B28 (700 MHz), B38 (2600 MHz)

    And from what I read here, if you buy a "Google" version of this phone, it would come already bootloader unlocked, right?

    Thanks for any information.
    Ok, I now received my F22 Pro with v1.0.3 goggled and bootloader unlocked version. I did the (long!) backup with MTKclient and installed NVTclean V2 ROM, thanks to Than, izyer and a_testi for the work and help.

    I can now answer my own questions about the Network frequencies:
    After installing MTK EngineerMode apk, I can see that all the Bands that I
    20230124_134938_HDR.jpg
    20230124_134926_HDR.jpg
    needed are activated. Apparently the phone has all international Bands activated, check the photos attached to see if your local ones are there. Cool thing to know!

    If they could sell a 256GB version, or at least the announced 128GB, of the F22 (or with microSD extension), it would be a perfect, simple and light phone for everyday use.
  • 2
    So, as a warning (really this should be in the first post)

    The "NVT" ROM seems to be a Vietnamese hack, or whatever the default language with lots of accents on each letter of the alphabet is supposed to be. The boot screen (fake and extremely ugly linux boot screen), security patch level January 2022, lots of preinstalled junk apps like Samsung Music or social networks, PIN limit to 4 digits, etc. doesn't really create a lot of confidence.

    Not sure if root works properly. If it does, everything except the PIN limit can be fixed with dedication.

    But the pure Google ROM was much better in that regard.

    Still compared to the pure Google ROM it appears better because it supports the physical hardware layout.

    4 digit pin limit really is such a shame. Thank Xi Jinping for that. Police need to be able to crack the PIN quickly if you say Tiananmen Square.

    It's the downside of Chinese phones: software is always bad, no matter what you do. Chinese can make really good hardware, but never any good software.

    Edit: Even the charging screen (when powered off) was molested by the guy who created the ROM. *sigh*

    Edit2:
    Magisk appeared after second reboot. To restore the factory's branding:

    - logo.bin restores the boot loader and charge screens: https://anonfiles.com/GeX605M2yd/logo_bin (for use with mtkclient: mtk w logo)
    - bootanimation.zip, goes into /system/media: https://anonfiles.com/84ob1aMeyc/bootanimation_zip

    Also be aware that "NVT" is in charge of the software updater and can push whatever they want to your phone using this firmware. Best to disable the updater completely.

    Edit3:
    The guy even had to piss his name into /system :cautious:
    rmdir /mnt2/Mod\ Bởi\ Nguyễn\ Văn\ Thản/
    You'd think the build version, software update, charge animation, and boot logo would be enough.

    Edit4:

    Linux commands that worked for me to replace the boot animation without making a Magisk module:

    Extract partitions from super.bin backup made using mtktool, then:

    Code:
    # mount product_a.ext /mnt/
    # rmdir /mnt/Mod\ Bởi\ Nguyễn\ Văn\ Thản/
    # umount /mnt
    # mount system_a.ext /mnt
    # cp bootanimation.zip /mnt/system/media/
    # e2fsck -yf system_a.ext
    # e2fsck -yf product_a.ext
    # lpmake --metadata-size 65536 --device-size=4294967296 --metadata-slots=3 --group=google_system_dynamic_partitions_a:2466766848 --partition=product_a:none:196341760:google_system_dynamic_partitions_a --partition=system_a:none:1812168704:google_system_dynamic_partitions_a --partition=vendor_a:none:458256384:google_system_dynamic_partitions_a --image=product_a=./product_a.ext --image=system_a=./system_a.ext --image=vendor_a=./vendor_a.img --group=google_system_dynamic_partitions_b:2466766848 --partition=product_b:none:196341760:google_system_dynamic_partitions_b --partition=system_b:none:88780800:google_system_dynamic_partitions_b --partition=vendor_b:none:458256384:google_system_dynamic_partitions_b --image=product_b=./product_b --image=system_b=./system_b.img --image=vendor_b=./vendor_b --sparse  --output ./super.new.img

    Then flash super.new.img using fastboot (not mtktool; it won't work!)

    If only the factory would release the official international image. But given that the year is almost over, it will likely never happen. So, to anyone out here, the NVT ROM is currently your best bet and will probably be the only firmware easily available for a long time.
    2
    Sadly I'm not an Android developer or hacker. The last time I deeply played around with custom ROMs was when the Samsung Galaxy S6 was current. Anyway I wasted an entire afternoon and evening on what follows. Now I'm tired and stuck. I just want a working phone, and I did this stuff purely out of self defence, because technology has become hostile.

    Modify ROM

    To edit the ROM, this is roughly how I did it:

    1. I use 7-Zip to open "Than.img" - 7-Zip can actually understand some of the ROM dumps and extract them
    2. I switch to a junk Debian VM where I have the folder with extracted files set as a shared folder (with VMware 17 and the latest Debian, this works right of the box)
    3. Then I do this:

    Code:
    # All of the below as root, because YOLO
    
    cd ~/
    wget http://newandroidbook.com/tools/imjtool.tgz
    wget https://ci.android.com/builds/submitted/9401535/aosp_cf_x86_64_phone-userdebug/latest/cvd-host_package.tar.gz
    tar xzf imjtool.tgz
    tar xzf cvd-host_package.tar.gz
    
    # Go to where extracted files are
    cd /mnt/hgfs/rom/work
    mkdir /mnt/product
    mkdir /mnt/system
    mount product_a.ext /mnt/product/
    mount system_a.ext /mnt/system/
    
    # Now you can play around!
    # You don't have much space to work with, but it's OK for small patches.
    # /dev/loop0      188M  176M  8.0M  96% /mnt/product
    # /dev/loop1      1.7G  1.7G   13M 100% /mnt/system
    # Out of space?
    # You can grow the ext4 partition images a bit.
    #  umount /mnt/system
    #  e2fsck -f /mnt/hgfs/rom/work/system_a.ext
    #  resize2fs /mnt/hgfs/rom/work/system_a.ext 2G
    #  mount system_a.ext /mnt/system/
    # Now you have 300 MB more space.
    
    # To finish up
    umount /mnt/product
    umount /mnt/system
    e2fsck -yf system_a.ext
    e2fsck -yf product_a.ext
    
    ~/bin/lpmake --metadata-size 65536 --device-size=8589934592 --metadata-slots=3 \
    --group=google_system_dynamic_partitions_a:2802081792 \
    --partition=product_a:none:196341760:google_system_dynamic_partitions_a \
    --partition=system_a:none:2147483648:google_system_dynamic_partitions_a \
    --partition=vendor_a:none:458256384:google_system_dynamic_partitions_a \
    --image=product_a=./product_a.ext \
    --image=system_a=./system_a.ext \
    --image=vendor_a=./vendor_a.img \
    --group=google_system_dynamic_partitions_b:88780800 \
    --partition=product_b:none:0:google_system_dynamic_partitions_b \
    --partition=system_b:none:88780800:google_system_dynamic_partitions_b \
    --partition=vendor_b:none:0:google_system_dynamic_partitions_b \
    --image=product_b=./product_b \
    --image=system_b=./system_b.img \
    --image=vendor_b=./vendor_b \
    --sparse --output ./super.new.img
    
    # you need to edit the numbers in above command as follows:
    # device-size = size of all files (or just 8589934592 for 8GB partition)
    # group = size of the files in that group
    # partition = size of the image file
    # find the sizes using command "stat -c '%n %s' *"
    
    # If it complains about "vendor_b" being strange, just set its image file
    # to vendor_a.img and adjust the numbers again. It doesn't matter.
    # Slot B is normally never used.


    WiFi Calling Crash
    For the Settings app crashing when trying to enable VoWiFi, it's caused by an oversight by the original ROM developers.

    The APK is at /system/system_ext/priv-app/MtkSettings/MtkSettings.apk

    The crash is:

    Code:
    java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$WifiCallingSettingsActivity}: java.lang.IllegalStateException: This Activity already has an action bar supplied by the window decor. Do not request Window.FEATURE_ACTION_BAR and set android:windowActionBar to false in your theme to use a Toolbar instead.
           at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3675)
           at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3832)
           at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
           at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
           at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
           at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2247)
           at android.os.Handler.dispatchMessage(Handler.java:106)
           at android.os.Looper.loopOnce(Looper.java:201)
           at android.os.Looper.loop(Looper.java:288)
           at android.app.ActivityThread.main(ActivityThread.java:7881)
           at java.lang.reflect.Method.invoke(Native Method)
           at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:568)
           at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)

    The workaround could be as simple as:

    1. Decompile it with apktool (use "apktool -r" because it cannot reassemble resources correctly)
    2. Open this file: smali/com/android/settings/Settings\$WifiCallingSettingsActivity.smali
    3. Comment out this line, save, recompile (apktool b), and sign:
    Code:
        .line 280
        # invoke-virtual {p0, p1}, Lcom/android/settings/core/SettingsBaseActivity;->setActionBar(Landroid/widget/Toolbar;)V

    But if you put the patched settings app into the ROM you will brick the phone. All system apps need to be signed with the same platform key, and that key is somewhere in China. I don't know how to bypass the signature check for system apps. I think you can resign all system apps with a custom key but unless someone could tell me how, I don't know. I think because of this also you can't just translate the missing strings in the Phone app.


    Cleaned ROM

    Here's my attempt to clean up the NVT ROM. This is currently running on my phone but if it bricks your phone then I am sorry. You may need to wipe userdata. Maybe not. I don't know. I wiped it.

    • Restored factory boot logo and charge animation
    • Restored factory boot Android animation
    • Removed "Mod\ Bởi\ Nguyễn\ Văn\ Thản" folder
    • Removed NVT's hacked QinSystemUpdate, so he can't remotely destroy phones (NOTICE Settings app will crash if you try to check for updates, because the APK it needs is now no longer there)
    • Removed "Gbroad" which didn't work because poor NVT could not spell "GBoard" correctly
    • Removed Samsung Music
    • Removed Zalo (Vietnamese social network)
    • Removed SprdQuickSearchBox
    • Removed Facebook Messenger
    • Removed third-party IR Blaster app
    • Removed Baidu App and Baidu Location Service
    • Removed "MtkCalendar" which NVT actually replaced with his own Vietnam Lunar Calendar. sigh
    • Restored Sound Recorder from 1.0.7 Qin China ROM to undo NVT's hardcoded Vietnamese translation of it
    • Replaced build.prop with the one from the clean Google ROM to restore the phone identifying itself as a Duoqin F22 Pro, to remove various ricer style "performance tweaks"/"speed optimizations", and to get rid of more references to "NVT" (as a bonus the phone no longer defaults to Vietnamese after wiping userdata)
    NVT is such a strange person. He even renamed the logo partition to "super.bin", probably hoped that people don't remove his branding. Also the phone reported itself as an Infinix HOT 12, not Duoqin F22 Pro. NVT also changed one of the stock wallpapers, but I have not yet found out how to undo it. Really, the only thing missing from his ROM that the phone starts playing a sound file of someone shouting "Nguyen Van Then" at maximum volume every 30 seconds. Anyway, while NVT still haunts the wallpaper selector, he should be pretty much gone elsewhere. I'm glad the guy did all of this work, but it's always better to become famous by what you do rather than by who you are.

    Download patched ROM: https://anonfiles.com/n5vfCfMey7/ThanCleaned_7z Use V2 below

    The ROM is pretty much naked, so you need to replace a lot of missing stock apps with custom ones. I recommend using F-Droid (search "Simple Mobile Tools"). They are not perfect, but decent enough, and free without ads. Music player can be replaced with the excellent app "Musicolet" from Google Play. A better romaji T9 keyboard and 10key Japanese keyboard can be taken from https://github.com/shuuryou/f22pro/

    I have really mixed feelings about the NVT version, cleaned or not. It's more like the Chinese ROM and the hardware features of the phone are now working essentially without flaws, but the software experience feels so mediocre. Like, it can be tolerated, but it could be so much better with a few little tweaks and changes overall. Not being able to modify the system APKs is a pity.

    Edit: I may have accidentally removed all keyboards. Just install one via adb.

    Edit2: Of course NVT also replaced all the ringtones. I will have to clean the cleaned ROM even more and will try to fix the keyboard issue then also.

    Edit3: Second attempt now available.
    2
    I can also confirm the ROM works fine. I've done very little testing but seems OK.
    It was a nice surprise after all those failed attempts to make the phone work with super.rar, I managed to install the ROM first time and it is working OK. Some of the submenus of the main settings menu crash and the overall feel of the system shows that it is not the most stable but it is usable.
    It remains to be seen does the OTA update work...
    2
    Edit: ill upload my backup and ill tell you what i did , i am not sure what fixed it exactly but yeah it worked in the end.

    I did all of this after my phone was bricked and the screen did not light up.

    So i got into mtkclient (download my arhive and you need to have python installed , check mtkclient website)

    opened Flash Tool (SP FLASH ive uploaded in the other post) and used Format all Flash then disconnected the phone
    (somtimes needed to keep OFF button pressed for 10 sec before i can connect again)

    after that

    cd mtclient

    python mtk wl ROM (this will flash all the files from my backup - unlocked bootloader)

    pressed volume UP and volume Down at the same time and connected the USB to the phone, phone started flashing the files

    after all done i disconnected the phone from the USB

    opened Flash Tool and i pressed Download button with everything selected.

    connected the USB to the phone (without pressing anything on the phone)

    it flashed and it worked.

    ---If the computer cant find the phone keep the OFF button pressed for 10 seconds then try again.

    Was a bit messy when i was trying to connect the mtkclient , tried in different ways , you need to figure it out if it doesnt work exactly with what i wrote.

    Edit: There was magisk app installed somewhere and i have root now too. (it wasnt showing at the beginning but after i installed a different launcher and rebooted the phone i saw it there)

    What ive noticed , VoWifi option doesnt work from the settings menu (crashes) , you need some 3rd app to enable the switch , Call Log (phone app) is not fully translated and the main launcher is limited , you cant change any settings (for home screens etc..) , everything else seems to work.

    Link: https://files.fm/u/cvxzz2gaq
    1
    Once i make root for my F22 pro
    The Bluetooth not working
    I try to do same like this post👆🏻
    But how i can get (Scatter File) from rom folder
    The ROM_2_1.0.7_Unlocked.7z
    Have only one file 59 GB
    Any help??
    You can delete userdata file from ROM_2_1.0.7_Unlocked, its a file with 50GB that you dont need.

    I am flashing it with "mtkclient" ( https://github.com/bkerler/mtkclient , i have a version that works nice with windows but this one should work too) or you can only flash the system_a.img from super.bin / .img with fastboot.

    Flashing super.rar - you get Google play but no WiFi , no Volte or VoWifi + a random crash sometimes, only EN and CH and bad microphone when calling.

    Flashing ROM_2_1.0.7_Unlocked.7z (or only the system_a.img INSIDE super.img from fastboot) and going with the normal mode you get working WiFI and no crash but Volte and Vowifi doesnt work, bad microphone when calling, only EN and CH and no Google Play but you can install from 3rd party

    Flashing ROM_2_1.0.7_Unlocked.7z (or only the system_a.img INSIDE super.img from fastboot) but going with the Student mode (second option on first boot), you can OTA update to the last firmware 3.0.0 something and you get working Wifi and Volte. VoWifi still crashes , you cant install any apps and no Google play, only EN / CH. (i didnt test microphone quality with this one)

    Flashing system_a.img from super.rar after flashing the rest of the files from ROM_2_1.0.7_Unlocked.7z (all files from super.img less system_a.img ) you get Google play, WiFI working but no Volte or VoWifi , only EN and CH bad microphone when calling.

    My phone came with an "pure Android version" (and i didnt backup it before flashing this other stuff , sadly) , it had all languages ,google play and no bugs (vowifi , volte etc all working) but the keypad buttons werent doing what they supposed to do and some stock functions were missing (ex: You couldnt end call from end call button etc , the screen was just going off instead and many others things like this), you had to do many things from the touchscreen. The seller sent me that super.bin but as you see its bugged , but the buttons from the keypad are working as intended.

    Seller told me like 4 5 6 times in the past month that he will give me Global ROM with no bugs but nothing, he said its not released yet.

    Edit: We need this firmware but i cant find it anywhere: