Related
Hello..
Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error..
tried flashing from mi flash tool, flashed in 1sec issue..
Please help , how am i suppose to flash stock rom via fastboot or miflash tool..
My bootloader is already unlocked..
is their any proper guide or youtube video or something and proper download link. i am sure i downloaded the right file but don't know why getting these errors..
My Phone is Redmi Note 4 (mido) , currently on STable Global Version
Thanks..
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing
Hello..
i have redmi note 4 and i am installing stock rom but it says that rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
Now waht i do
can you please explain me.
pls
Thanks
Thanx
ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
It worked. Thanks !!
ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
Worked for me. Thank you!! Truly thought I bricked my phone.
Beast gamer said:
Hello..
i have redmi note 4 and i am installing stock rom but it says that rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
Now waht i do
can you please explain me.
pls
Thanks
Click to expand...
Click to collapse
Had this problem, outcommented the variantchecks (in the flash_all_except_data.bat and other 3 bat files). Now Miflash prompts not this but subsequent [] problem :
$for /F "tokens=2 delims=: "%in (fastboot -s [MY 7 char-DEVICENO.] getvar anti 2>&1
Probably I am apart from your problem, as Fastboot commands give no responds: for e.g.
fastboot getvar boot-mode, answer is:
< waiting for any device >
Only "success" I had:
fastboot reboot
but still in bootloop
Any help appreciated, I am a beginner...
ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
I didn't understand no -3 point????
i am flashing redmi note 5 and i am also getting mismatch error. i tried the following method but now it is displaying 'flash xbl error' and partition table doesn't exist.
any help will be highly appreciated
Shadow505 said:
For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing
Click to expand...
Click to collapse
I created an account on xda just to thank you.
this really saved my phone, I have been spending well over 12 hours trying to get this fixed
It worked as soon as i switched over to my intel powered laptop
THANK YOU
Shadow505 said:
For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing
Click to expand...
Click to collapse
I have my ryzen and this is the solution after few hour struggling with this error. Thank a bunch!
Yep, I've just been struggling to install stock 'n' lock via miflash, and it turned out the problem was my Ryzen CPU. Have dug out an old intel laptop, which doesn't connect to wifi, the battery is dead, and half the screen isn't viewable, but it does manage to install firmware via miflash. Thanks so much for this thread, which probably saved me several hours of fiddling.
I have a fairly odd device, 22" acer aa3-600 (x86 intel not ARM), and it doesn't support adb or fastboot over usb (wtf right?) but does support adb and fastboot over ethernet. I can connect fine via tcp during adb, but with little sign networking is even working on the bootloader screen i can't seem to communicate during fastboot, meaning i can't unlock the bootloader. Incredibly frustrating.
There is *one* piece that makes me think networking is enabled, which is what keeps me going at this point
This pdf mentions pinging the device and then -t pinging it (page 5 second table under fastboot) - https://01.org/sites/default/files/documentation/android_4.x_build_image_guide.pdf , which works.
i couldn't believe it when his ip was set as the same that my AIO *says* it will set for usb debugging (it doesn't), and after i set my pc to the same ip as his and connected directly i could ping! i was shocked, and this alone keeps me going.
Anyone have any thoughts?
Most of the resources i can find are official or formal release doc stuff, see below.
https://sourceforge.net/p/android-x86/system_core/ci/nougat-x86/tree/fastboot/fastboot_protocol.txt
and other bits in the release doc for x86 - https://sourceforge.net/p/android-x86/system_core/ci/nougat-x86/tree/fastboot/ - like this list of commands
https://android.googlesource.com/platform/system/core/+/master/fastboot/README.md
Code:
> fprintf(stderr,
/* 1234567890123456789012345678901234567890123456789012345678901234567890123456 */
"usage: fastboot [ <option> ] <command>\n"
"\n"
"commands:\n"
" update <filename> Reflash device from update.zip.\n"
" Sets the flashed slot as active.\n"
" flashall Flash boot, system, vendor, and --\n"
" if found -- recovery. If the device\n"
" supports slots, the slot that has\n"
" been flashed to is set as active.\n"
" Secondary images may be flashed to\n"
" an inactive slot.\n"
" flash <partition> [ <filename> ] Write a file to a flash partition.\n"
" flashing lock Locks the device. Prevents flashing.\n"
" flashing unlock Unlocks the device. Allows flashing\n"
" any partition except\n"
" bootloader-related partitions.\n"
" flashing lock_critical Prevents flashing bootloader-related\n"
" partitions.\n"
" flashing unlock_critical Enables flashing bootloader-related\n"
" partitions.\n"
" flashing get_unlock_ability Queries bootloader to see if the\n"
" device is unlocked.\n"
" flashing get_unlock_bootloader_nonce Queries the bootloader to get the\n"
" unlock nonce.\n"
" flashing unlock_bootloader <request> Issue unlock bootloader using request.\n"
" flashing lock_bootloader Locks the bootloader to prevent\n"
" bootloader version rollback.\n"
" erase <partition> Erase a flash partition.\n"
" format[:[<fs type>][:[<size>]] <partition>\n"
" Format a flash partition. Can\n"
" override the fs type and/or size\n"
" the bootloader reports.\n"
" getvar <variable> Display a bootloader variable.\n"
" set_active <slot> Sets the active slot. If slots are\n"
" not supported, this does nothing.\n"
" boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.\n"
" flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]\n"
" Create bootimage and flash it.\n"
" devices [-l] List all connected devices [with\n"
" device paths].\n"
" continue Continue with autoboot.\n"
" reboot [bootloader] Reboot device [into bootloader].\n"
" reboot-bootloader Reboot device into bootloader.\n"
" help Show this help message.\n"
"\n"
"options:\n"
" -w Erase userdata and cache (and format\n"
" if supported by partition type).\n"
" -u Do not erase partition before\n"
" formatting.\n"
" -s <specific device> Specify a device. For USB, provide either\n"
" a serial number or path to device port.\n"
" For ethernet, provide an address in the\n"
" form <protocol>:<hostname>[:port] where\n"
" <protocol> is either tcp or udp.\n"
" -p <product> Specify product name.\n"
" -c <cmdline> Override kernel commandline.\n"
" -i <vendor id> Specify a custom USB vendor id.\n"
" -b, --base <base_addr> Specify a custom kernel base\n"
" address (default: 0x10000000).\n"
" --kernel-offset Specify a custom kernel offset.\n"
" (default: 0x00008000)\n"
" --ramdisk-offset Specify a custom ramdisk offset.\n"
" (default: 0x01000000)\n"
" --tags-offset Specify a custom tags offset.\n"
" (default: 0x00000100)\n"
" -n, --page-size <page size> Specify the nand page size\n"
" (default: 2048).\n"
" -S <size>[K|M|G] Automatically sparse files greater\n"
" than 'size'. 0 to disable.\n"
" --slot <slot> Specify slot name to be used if the\n"
" device supports slots. All operations\n"
" on partitions that support slots will\n"
" be done on the slot specified.\n"
" 'all' can be given to refer to all slots.\n"
" 'other' can be given to refer to a\n"
" non-current slot. If this flag is not\n"
" used, slotted partitions will default\n"
" to the current active slot.\n"
" -a, --set-active[=<slot>] Sets the active slot. If no slot is\n"
" provided, this will default to the value\n"
" given by --slot. If slots are not\n"
" supported, this sets the current slot\n"
" to be active. This will run after all\n"
" non-reboot commands.\n"
" --skip-secondary Will not flash secondary slots when\n"
" performing a flashall or update. This\n"
" will preserve data on other slots.\n"
#if !defined(_WIN32)
" --wipe-and-use-fbe On devices which support it,\n"
" erase userdata and cache, and\n"
" enable file-based encryption\n"
#endif
" --unbuffered Do not buffer input or output.\n"
" --version Display version.\n"
" -h, --help show this message.\n"
I know you can use udp too - https://github.com/aosp-mirror/platform_system_core/commit/4601c978cad8b69e15ed63664ebb5dcf6aaf21b3
https://supportforums.cisco.com/t5/...oritizing-udp-over-tcp-using-qos/td-p/2379534
but i am having enough trouble as is. That said, if anyone thinks this is the best option please let me know.
I am also open to any other option out there. I have the droidboot bootloader on my desktop, not that i know what to do with it. Or should i try to unlock it some other way? Could i somehow enable fastboot over usb even though my device doesn't support it? An app maybe? Bootloader screen is looking for installer.cmd file, maybe that? What is that?
Any help would be seriously appreciated
I have the Acer Iconia A1-830, which also utilizes the droidboot bootloader but fastboot works fine (with some minor tweaks, you can even use adb!). Can you try to run adb reboot fastboot when in adb mode and see what that does? Good luck
I can boot in to adb and fastboot fine, i just can't run any commands in fastboot through usb.
i'll try to be more succinct, as i still need some help if possible
I can ping my device in fastboot if i set host to 192.168.42.1 and my pc to 192.168.43.2, as outline in the pdf above, but that's it. No other fastboot commands register with the device. I can only use ethernet, per the device, and need some idea of what i need to do to be able to send fastboot commands.
Anyone? Pretty pretty please??
phishphish said:
i'll try to be more succinct, as i still need some help if possible
I can ping my device in fastboot if i set host to 192.168.42.1 and my pc to 192.168.43.2, as outline in the pdf above, but that's it. No other fastboot commands register with the device. I can only use ethernet, per the device, and need some idea of what i need to do to be able to send fastboot commands.
Anyone? Pretty pretty please??
Click to expand...
Click to collapse
I want to try and help you, however I don't have all the time in the world. What is it that you are trying to do with the device? Flash a rom or unbrick? Or is it just a "I wanna see if it's working" thing?
i can't seem to communicate during fastboot, meaning i can't unlock the bootloader.
Click to expand...
Click to collapse
I'm not asking specifically just you, but yeah, thanks
Many of 6GB RAM Nokia X6 has an issue, that you can't flash system partition properly - after 1st sparse flashed, fastboot will prompt "error flashing partition".
This guide introduces a workaround for this issue.
4GB RAM Nokia X6 / 6.1 Plus needn't to follow this guide.
And 6GB RAM Nokia 7 Plus needn't to follow this guide.
Or if your 6GB RAM Nokia X6 can flash stock firmware properly, you needn't to read this guide any further.
Click to expand...
Click to collapse
I still don't clear the pattern of 6GB RAM Nokia X6 that can't flash partitions.
Prerequisites:
- Bootloader must be completely unlocked
- You have fully unpacked firmware
- Use OST LA 6.0.4 or NOST v0.4 by @stollD
Here's how:
1. Make a copy of DRG-2XXX-0-00XX-B0X.mlf at the same directory, in this example, I made a copy of "DRG-221F-0-00CN-B03.mlf".
2. Use Notepad++ or any code editor that supports unix to open "DRG-221F-0-00CN-B03 - Copy.mlf".
3. Navigate to these codes.
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system.img"
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system_other.img"
And modify them to:
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x4
IMAGE_FILE = ""
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x4
IMAGE_FILE = ""
Save it.
4. Use OST LA or NOST to flash this - you'll definitely encounter C6DA error, but don't worry about that.
5. Download TWRP for Nokia 7 Plus that doesn't require flash from here (TBA) and execute these commands under OST LA installation directory:
NOTE: YOU MUST USE fastboot-android.exe included in OST LA - DO NOT USE fastboot.exe provided by Google.
Click to expand...
Click to collapse
Code:
.\fastboot-android format userdata
.\fastboot-android reboot-bootloader
.\fastboot-android boot D:\Nokia7plusv3.2.1.0-noflash.img
After your phone booted to TWRP, you may find the touch screen doesn't work, don't worry - we only need to use adb commands.
6. Execute following commands:
[QUOTE]
You can use adb.exe from both OST LA or platform tools.
[/QUOTE]
[CODE]
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\systeminfo.img /data/systeminfo.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system.img /data/system_a.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system_other.img /data/system_b.img
.\adb shell
simg2img /data/system_a.img /data/system_a.img.ext4
simg2img /data/system_b.img /data/system_b.img.ext4
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_a
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_b
dd if=/data/system_a.img.ext4 of=/dev/block/bootdevice/by-name/system_a
dd if=/data/system_b.img.ext4 of=/dev/block/bootdevice/by-name/system_b
rm /data/systeminfo.img
rm /data/system_a.img
rm /data/system_b.img
reboot
That's all for the whole 6GB RAM Nokia X6 stock firmware flashing guide.
If you're a developer, 6GB RAM Nokia X6 is definitely unsuitable for developing.
Thanks for the guide, it will be very useful for me. I'm trying to flash this phone for a long time and I just can't unbrick it.
A few issues I've come over while following it:
OST_LA and NOST didn't want to flash DRG-221F-0-00CN-B03 ("you need to update your software" or something like that), so I had to unpack DRG-229D-0-00WW-B01.
I couldn't find Nokia7plusv3.2.1.0-noflash.img anywhere, so I used Twrp_N6.1plus_global_Aug.
When I try to use simg2img in adb shell, I get the following error:
Code:
~ # simg2img /data/system_a.img /data/system_a.img.ext4
error: file_write: write: Out of memory
Cannot write output file
---
Update: I've flashed 250A and it works like a charm! Just had to edit the .mlf according to this guide.
Hi @hikari_calyx,
have you tried flashing Nokia X6 6GB version to 6.1 Plus International Version (Android One)?
Anything I need to consider?
Hey I bought the Nokia x6 TA-1099 6gb Chinese variant it came with the global ROM 00WW_3_38A I believe it was flashed by the seller. When I got the phone I saw there was an OTA to update the pie to v3.45B I want to know if it's safe to update via OTA because it's meant for 6.1plus
:good: thanks
twrp fails
when iam flashing twrp it is showing that no such partiton is found recovery b
Recently purchased an iplay 7t after reading the xda review. This is replacing an LG v400 tablet that I had rooted. I updated the iplay to build T701_V1.20_20191112, enabled developer options, enabled oem unlock bootloader, found the corresponding firmware pac, installed magisk and used it to patch boot.img. So far so good.
I entered fastboot, then I attempted to flash the modified boot.img and was told:
Code:
target didn't report max-download-size
sending 'boot' (18584 KB)...
OKAY [ 0.593s]
writing 'boot'...
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
finished. total time: 0.608s
I tried various options to unlock the bootloader:
Code:
> fastboot getvar unlocked
unlocked:
finished. total time: -0.000s
> fastboot oem unlock
...
FAILED (remote: unknown cmd.)
finished. total time: -0.000s
> fastboot oem unlock-go
...
FAILED (remote: unknown cmd.)
finished. total time: 0.002s
> fastboot flashing get_unlock_ability
...
FAILED (remote: Not implement.)
finished. total time: -0.000s
> fastboot flashing unlock
...
FAILED (remote: Not implemet.)
finished. total time: -0.000s
> fastboot flashing unlock_critical
...
FAILED (remote: Not implement.)
finished. total time: 0.016s
> fastboot flashing unlock_bootloader
fastboot: usage: unknown 'flashing' command unlock_bootloader
> fastboot flashing unlock_bootloader_nonce
fastboot: usage: unknown 'flashing' command unlock_bootloader_nonce
Okay ... fine. I fired up SPD Research tool and attempted to use it to flash the modified boot.img. It transfers the image and then times out.
As a sanity check I used SPD Research tool to flash the original boot.img and that worked fine.
I'll note the modified image is smaller than the original, however padding the modified image with zeros to the same size didn't seem to help. Using SPD Research tool to flash the padded image still timed out.
I am looking to open a request up on the Alldocube support site (currently their registration form is giving me an error), in the meantime ... suggestions? Has anyone successfully flashed a modified boot.img on this device / rooted this device?
in the "developer option" on your phone, you should enable the "allow unlock bootloader" option.
DR.Doyle said:
in the "developer option" on your phone, you should enable the "allow unlock bootloader" option.
Click to expand...
Click to collapse
Yes ... I have that enabled.
Okay I was able to unlock the bootloader by using the procedure documented for the Qin 2 Pro. With the bootloader unlocked on reboot the device notes:
Code:
INFO: LOCK FLAG IS : UNLOCKED!!!
followed by:
Code:
WARNING: LOCK FLAG IS : UNLOCKED, SKIP VERIFY!!!
Using fastboot I can now reflash the stock vbmeta and the stock recovery without any problems and the stock recovery boots fine.
Also if I re-sign the stock recovery, then I can't flash it (fastboot flash hangs) until I've flashed a modified vbmeta containing the new public key for the re-signed recovery. Meaning flashing vbmeta is "working".
All this seems like I'm on the right track.
However attempting to boot into the re-signed stock recovery results in:
Code:
INFO: LOCK FLAG IS : UNLOCKED!!!
followed by the device hanging (without displaying the WARNING message) so there is still something that's unhappy.
Any thoughts on how to get to the point that I can flash a useable re-signed stock recovery? If I can get that to work, then I should be in good shape to install magisk.
jwehle said:
Okay I was able to unlock the bootloader by using the procedure documented for the Qin 2 Pro. With the bootloader unlocked on reboot the device notes:
Code:
INFO: LOCK FLAG IS : UNLOCKED!!!
followed by:
Code:
WARNING: LOCK FLAG IS : UNLOCKED, SKIP VERIFY!!!
Using fastboot I can now reflash the stock vbmeta and the stock recovery without any problems and the stock recovery boots fine.
Also if I re-sign the stock recovery, then I can't flash it (fastboot flash hangs) until I've flashed a modified vbmeta containing the new public key for the re-signed recovery. Meaning flashing vbmeta is "working".
All this seems like I'm on the right track.
However attempting to boot into the re-signed stock recovery results in:
Code:
INFO: LOCK FLAG IS : UNLOCKED!!!
followed by the device hanging (without displaying the WARNING message) so there is still something that's unhappy.
Any thoughts on how to get to the point that I can flash a useable re-signed stock recovery? If I can get that to work, then I should be in good shape to install magisk.
Click to expand...
Click to collapse
Dear jwehle:
good job, i have also modify the pac firmware file which based on chinese vesion firmware:T701-1101-vbmetapri-vennofbe-systemnore-recpri01.pac
What's modified:
1.resgin the vbmeta img
2.delete fbe Force encryption in vendor partitions
3.delete the script in system.img to prevent factory recovery restore
4.modify recovery.img to a magisk build-in recovery
please use SPD_Research_Tool to flash the pac,change the android os language from chinese to english ,install magiskmanager app ,and the use adb command (adb reboot recovery)to let tablet reboot to recovery.
after tablet reboot to android os again ,open magiskmanager app,you can see the magisk can get root authority .
how to change language from chinese to english,please see attach png file.
Considering that the Android os you are using is in English version(including Google services),according to the modification points above, you can try to use the vbmeta and recovery (built in magisk) modified by your own signature , and then delete the fbe Force encryption、 recovery restoration in the system and vendor images , then use the SPD_Research_Tool to package the imgs into a pac image, flash the pac image, install the magiskmanager app, and use the adb command to restart the machine into recovery mode, so you can use magisk to get root permissions.
twrp egg:https://mega.nz/#!YZ9VDZbT!1ptlOI6g3FS_ES-cLGhLy9ybGtdHQ8vzVHaasAXglXo
and last thanks PeterCxy on xda 、the other masters sifu on 4pda agian.
wangyiling said:
Dear jwehle:
good job, i have also modify the pac firmware file which based on chinese vesion firmware:T701-1101-vbmetapri-vennofbe-systemnore-recpri01.pac
What's modified:
1.resgin the vbmeta img
2.delete fbe Force encryption in vendor partitions
3.delete the script in system.img to prevent factory recovery restore
4.modify recovery.img to a magisk build-in recovery.
Click to expand...
Click to collapse
Thanks for supplying the modified PAC and for explaining the changes.
Your PAC seemed to work fine and now that I have a better understanding
of things I should be able build my own PAC when I have a chance.
Your time and effort in explaining things is appreciated.
What's the significance of removing the encryption for the vendor partitions?
jwehle said:
What's the significance of removing the encryption for the vendor partitions?
Click to expand...
Click to collapse
the vendor img in my pac，just use ext4 format.i have use simg2img convert the oringin vendor img to ext4 format,and modify the fstab file in vendor/etc folder.
fstab.sp9832e_1h10：
Code:
/dev/block/platform/soc/soc:ap-ahb/20600000.sdio/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inline_xattr,inline_data wait,check,[COLOR="DarkOrange"]fileencryption[/COLOR]=aes-256-xts,reservedsize=128M
/dev/block/platform/soc/soc:ap-ahb/20600000.sdio/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,noauto_da_alloc wait,check,[COLOR="darkorange"]fileencryption[/COLOR]=aes-256-xts
---------->
Code:
/dev/block/platform/soc/soc:ap-ahb/20600000.sdio/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inline_xattr,inline_data wait,check,[COLOR="darkorange"]encryptable[/COLOR]=aes-256-xts,reservedsize=128M
/dev/block/platform/soc/soc:ap-ahb/20600000.sdio/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,noauto_da_alloc wait,check,[COLOR="darkorange"]encryptable[/COLOR]=aes-256-xts
wangyiling said:
the vendor img in my pac，just use ext4 format.i have use simg2img convert the oringin vendor img to ext4 format,and modify the fstab file in vendor/etc folder.
Click to expand...
Click to collapse
Actually, I was more curious as to why it was necessary / desirable to remove the encryption from the vendor partitions.
jwehle said:
Actually, I was more curious as to why it was necessary / desirable to remove the encryption from the vendor partitions.
Click to expand...
Click to collapse
Just for twrp to read the data partition, convenient for personal use。
It looks like the issue on this tablet is similar to what the magisk documentation mentions regarding the new Samsung tablets. Meaning after the bootloader is unlocked when rooting you should flash newly signed versions of the following:
Code:
vbmeta
boot
recovery
What was happening is when the system started normally it saw that recovery image had been modified so it checked if the boot image was the factory standard image. Since I hadn't touched the boot image the OS went ahead and attempted to replace the recovery image I flashed with a standard recovery image generated on the fly from the factory standard boot image. This caused a soft-brick when I rebooted into recovery since that recovery image wasn't signed using the public key specified by my replacement vbmeta.
By also flashing a newly signed boot image because the signature is different from what's it knows about the system no longer attempts to use it to refresh the recovery image.
Here's an outline of what I did to successfully root the device:
Use the Qin 2 Pro instructions / tools to unlock the boot loader.
Flash the appropriate factory standard firmware to establish a know starting point. I used iplay7t(T701)-Android9.0-ALLDOCUBE-191112 from the Alldocube web site.
Use SPD Rsearch Tool to extract vbmeta-sign.img, boot.img, and recovery.img.
Use avbtool (with the below patch) to extract the public keys from vbmeta-sign.img like so:
Code:
avbtool info_image --image vbmeta-sign.img.
Use make (with the below makefile) to sign vbmeta, boot, and recovery using a new key.
Flashed vbmeta, boot, and recovery.
Booted into recovery, saw that it worked, and did a factory reset.
Used magisk to patch recovery.img in the normal fashion, signed the patched recovery using the new key, and flashed the patched recovery.
Proceed to finish installing magisk in the normal fashion.
Notes:
rsa4096_vbmeta.pem is the private key mentioned in the Qin 2 Pro article.
The dhtbsign-vbmeta command is basically the dhtb signing python script from Qin 2 Pro article.
Here's the trival patch for avbtool to dump the public keys.
Code:
--- avbtool 2020-02-22 22:11:55.107787032 -0500
+++ avbtool.dumpkeys 2020-02-22 22:15:36.046283077 -0500
@@ -1657,6 +1657,10 @@ class AvbChainPartitionDescriptor(AvbDes
Arguments:
o: The object to write the output to.
"""
+ kfd = open(self.partition_name, "w");
+ kfd.write(self.public_key);
+ kfd.close();
+
o.write(' Chain Partition descriptor:\n')
o.write(' Partition Name: {}\n'.format(self.partition_name))
o.write(' Rollback Index Location: {}\n'.format(
Here's the makefile I used for signing the images.
Code:
all: boot-sign.img recovery-sign.img vbmeta-sign.img
vbmeta-sign.img: Makefile avb4096_pkmd.bin keys/*
avbtool make_vbmeta_image --output vbmeta.img --padding_size 16384 \
--key ../rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 0 \
--chain_partition boot:1:avb4096_pkmd.bin \
--chain_partition system:3:keys/system \
--chain_partition vendor:4:keys/vendor \
--chain_partition product:10:keys/product \
--chain_partition dtbo:9:keys/dtbo \
--chain_partition recovery:2:avb4096_pkmd.bin \
--chain_partition l_modem:5:keys/l_modem \
--chain_partition l_ldsp:6:keys/l_ldsp \
--chain_partition l_gdsp:7:keys/l_gdsp \
--chain_partition pm_sys:8:keys/pm_sys \
--chain_partition dtb:11:keys/dtb
dhtbsign-vbmeta vbmeta.img vbmeta-sign.img
@rm -f vbmeta.img
avb4096_pkmd.bin: avb4096.pem
avbtool extract_public_key --key avb4096.pem --output avb4096_pkmd.bin
avb4096.pem:
openssl genrsa -out avb4096.pem 4096
boot-sign.img: boot.img avb4096.pem
cp boot.img boot-sign.img
avbtool add_hash_footer --image boot-sign.img \
--partition_name boot --partition_size 36700160 \
--key avb4096.pem --algorithm SHA256_RSA4096
recovery-sign.img: recovery.img avb4096.pem
cp recovery.img recovery-sign.img
avbtool add_hash_footer --image recovery-sign.img \
--partition_name recovery --partition_size 36700160 \
--key avb4096.pem --algorithm SHA256_RSA4096
@ jwehle，Very grateful for your detailed sharing
Did you have any trouble getting the tablet to populate the fastboot devices list?
I have USB drivers installed and can view the tablet's internal storage when it's not in fastboot mode. She's plugged directly into the mobo and I've tried two cables.
When in fastboot mode, it comes up in the Windows Device Manager as fastboot Gadget and drivers are apparently not available. I've tried using Zadig to feed it a driver of some kind, but still nothing.
MissAyako said:
Did you have any trouble getting the tablet to populate the fastboot devices list?
I have USB drivers installed and can view the tablet's internal storage when it's not in fastboot mode. She's plugged directly into the mobo and I've tried two cables.
When in fastboot mode, it comes up in the Windows Device Manager as fastboot Gadget and drivers are apparently not available. I've tried using Zadig to feed it a driver of some kind, but still nothing.
Click to expand...
Click to collapse
Seems the issue was with Windows. I thought I would be able to get the unlock token with Windows and then use WSL to do the rest of the signing, but apparently not.
Luckily I had an old laptop lying around. I threw Linux Mint on it and it worked just fine.
It didn't seem to work just using a live USB; I had to install Linux to the hard disk, but YMMV.
jwehle said:
It looks like the issue on this tablet is similar to what the magisk documentation mentions regarding the new Samsung tablets. Meaning after the bootloader is unlocked when rooting you should flash newly signed versions of the following:
Click to expand...
Click to collapse
This was wonderful, thank you! I've added some of my own notes below as an experience of what I encountered when attempting this process myself (spoiler'd because it is a lot).
I do not have enough post count to add links, but titles to the relevant articles has been added.
Follow steps in Article "Guide: How to Unlock Xiaomi Qin 2 (Pro) and Install Custom ROMs" from step 1 to (and including) step 10 (Unlocking section).
Notes:
- A Linux PC is necessary.
- You'll have to mark the "fastboot" file from the "Android_device_unlock.rar" archive as executable (chmod +x).
- Run the "fastboot" file as root.
- Getting the "SPD Research Tool" to pick up the tablet and not let the tablet try to move to either the charging
screen or the bootlogo is difficult, but do-able. Press and hold Power+Vol_Up and release when Windows does its
USB device detected chime.
- Flashing takes a few minutes (I think around 300 seconds).
- The SPD Research Tool extracts the PAC file contents into a folder. Grab the system images from there.
- The "avbtool" is available to be cloned via git from Google's repo
- The avbtool is a python script that is patched with three lines of code at line 1776:
Code:
kfd = open(self.partition_name, "w");
kfd.write(self.public_key);
kfd.close();
- When you use the patched avbtool on the vbmeta-sign.img file you copied (avbtool info_image --image vbmeta-sign.img)
it will produce several partitions with relative public keys that need to be stored in separate files for the next step.
The contents of the files are simply the public key and the partition name as the file name. Store the files in a folder named "keys".
- When creating the makefile, ensure that proper indentation is used. The code segment below is properly formatted (hopefully). If you get make errors, remove and re-indent the lines.
- If your "rsa4096_vbmeta.pem" keyfile is not placed alongside the makefile, ensure the --key flag points to this file.
- The makefile exists in the same directory as the system images.
- I had to insert local paths to the avbtool, as it was not installed to the system PATH.
- The dhtbsign-vbmeta.py command is located below. Make sure to mark this as executable as well.
Everything else is rather straightforward.
# makefile
Code:
all: boot-sign.img recovery-sign.img vbmeta-sign.img
vbmeta-sign.img: makefile avb4096_pkmd.bin keys/*
avbtool make_vbmeta_image --output vbmeta.img --padding_size 16384 \
--key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 0 \
--chain_partition boot:1:avb4096_pkmd.bin \
--chain_partition system:3:keys/system \
--chain_partition vendor:4:keys/vendor \
--chain_partition product:10:keys/product \
--chain_partition dtbo:9:keys/dtbo \
--chain_partition recovery:2:avb4096_pkmd.bin \
--chain_partition l_modem:5:keys/l_modem \
--chain_partition l_ldsp:6:keys/l_ldsp \
--chain_partition l_gdsp:7:keys/l_gdsp \
--chain_partition pm_sys:8:keys/pm_sys \
--chain_partition dtb:11:keys/dtb
./dhtbsign-vbmeta.py vbmeta.img vbmeta-sign.img
@rm -f vbmeta.img
avb4096_pkmd.bin: avb4096.pem
avbtool extract_public_key --key avb4096.pem --output avb4096_pkmd.bin
avb4096.pem:
openssl genrsa -out avb4096.pem 4096
boot-sign.img: boot.img avb4096.pem
cp boot.img boot-sign.img
avbtool add_hash_footer --image boot-sign.img \
--partition_name boot --partition_size 36700160 \
--key avb4096.pem --algorithm SHA256_RSA4096
recovery-sign.img: recovery.img avb4096.pem
cp recovery.img recovery-sign.img
# dhtbsign-vbmeta.py file (from "How I Unlocked Xiaomi Qin 2 Pro and Installed Phh GSI")
Code:
#!/usr/bin/env python
import hashlib
import sys
f = open(sys.argv[1], "rb")
b = f.read()
sha = hashlib.sha256(b).digest()
f.close()
f = open("vbmeta_signed.img", "wb")
f.write(b)
f.seek(1048576 - 512)
f.write(b'\x44\x48\x54\x42\x01\x00\x00\x00')
f.write(sha)
f.write(b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x40\x00\x00')
f.seek(1048576 - 1)
f.write(b'\x00')
f.close()
wuxianlin has build a twrp device for T701.
i think this will be a help .
Help me
Sir help pliz same problem my device ,same chipset , Symphony i95 ,pliz sir modify my pac file pliz....
wangyiling said:
Dear jwehle:
good job, i have also modify the pac firmware file which based on chinese vesion firmware:T701-1101-vbmetapri-vennofbe-systemnore-recpri01.pac
What's modified:
1.resgin the vbmeta img
2.delete fbe Force encryption in vendor partitions
3.delete the script in system.img to prevent factory recovery restore
4.modify recovery.img to a magisk build-in recovery
please use SPD_Research_Tool to flash the pac,change the android os language from chinese to english ,install magiskmanager app ,and the use adb command (adb reboot recovery)to let tablet reboot to recovery.
after tablet reboot to android os again ,open magiskmanager app,you can see the magisk can get root authority .
how to change language from chinese to english,please see attach png file.
Considering that the Android os you are using is in English version(including Google services),according to the modification points above, you can try to use the vbmeta and recovery (built in magisk) modified by your own signature , and then delete the fbe Force encryption、 recovery restoration in the system and vendor images , then use the SPD_Research_Tool to package the imgs into a pac image, flash the pac image, install the magiskmanager app, and use the adb command to restart the machine into recovery mode, so you can use magisk to get root permissions.
twrp egg:https://mega.nz/#!YZ9VDZbT!1ptlOI6g3FS_ES-cLGhLy9ybGtdHQ8vzVHaasAXglXo
and last thanks PeterCxy on xda 、the other masters sifu on 4pda agian.
Click to expand...
Click to collapse
can i just flash the pac without unlocking the bootloader.
thanks in advances
hidroela said:
can i just flash the pac without unlocking the bootloader.
thanks in advances
Click to expand...
Click to collapse
yes,just falsh pac
wangyiling said:
yes,just falsh pac
Click to expand...
Click to collapse
i did unlocked the bootloader and flash the pac and follow the instructions for magisk to work, but after a third reboot Root was gone.
i don't know what I am missing.
How to install Xiaomi.eu ROM for Redmi Note 10
We will release fastboot ROM versions until TWRP for mojito/sunny is released
UPDATE:
- TWRP for mojito/sunny is RELEASED
- From now, we will release RECOVERY version of ROM for install via TWRP, so this guide is obsolete
Steps to install xiaomi.eu ROM for first time from China ROM via fastboot (All your data and files on internal storage will be deleted!)
- Update Global ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
@ingbrzy Will be Xiaomi.Eu version for sweet?
got stuck at fastboot - bootloop after ran the bat file.
sweat...
redmi note 10 - sunny
Edit: managed to flash it after removed _ab in the script.
abc9999 said:
got stuck at fastboot - bootloop after ran the bat file.
sweat...
redmi note 10 - sunny
Click to expand...
Click to collapse
which ROM did you had before?
ingbrzy said:
which ROM did you had before?
Click to expand...
Click to collapse
global rom
Edit: managed to flash it after removed _ab in the script.
abc9999 said:
global rom
Edit: managed to flash it after removed _ab in the script.
Click to expand...
Click to collapse
ok.. flashing by windows or linux?
ingbrzy said:
ok.. flashing by windows or linux?
Click to expand...
Click to collapse
windows
abc9999 said:
windows
Click to expand...
Click to collapse
Did you cd to unzipped folder and execute script from there? Seems fastboot.exe wasn't used from our folder..
Shermo1208 said:
@ingbrzy Will be Xiaomi.Eu version for sweet?
Click to expand...
Click to collapse
@ingbrzy any comments about that? Thanks
Shermo1208 said:
@ingbrzy any comments about that? Thanks
Click to expand...
Click to collapse
yes..
ingbrzy said:
yes..
Click to expand...
Click to collapse
I really look forward to it, man. Didn't have a Xiaomi since the Redmi Note 2 and even back then you were there. Thanks for the effort. I still have 5 days left to be able to unlock the bootloader, so I have to wait anyway. Will sweet get a TWRP support? I don't know, if they still work on TWRP, the latest posts I saw were from end of 2020
ingbrzy said:
yes..
Click to expand...
Click to collapse
When?
abc9999 said:
global rom
Edit: managed to flash it after removed _ab in the script.
Click to expand...
Click to collapse
So please tell us your experience with the rom? Is it stable, are there any performance or lag issues with the rom?
Is network and radio working properly? Is call recording working?
ingbrzy said:
How to install Xiaomi.eu ROM for Redmi Note 10
We will release fastboot ROM versions until TWRP for mojito/sunny is released
Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on internal storage will be deleted!)
- Update Global ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file xiaomi.eu_multi_HMNote10_V12.0.2.0.RKGMIXM_v12-11-fastboot.zip
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
Click to expand...
Click to collapse
What about Redmi Note 10 Pro India? Will this work in that phone which has 64MP Cam and SD732G?
njaya95 said:
What about Redmi Note 10 Pro India? Will this work in that phone which has 64MP Cam and SD732G?
Click to expand...
Click to collapse
Note 10 Pro and Pro Max(india) are same and same ROMs work on those device, but Note 10 is different.
Is there a way to revert back to global MIUI after flashing the Xiaomi eu version?
ahmedwaseem said:
Is there a way to revert back to global MIUI after flashing the Xiaomi eu version?
Click to expand...
Click to collapse
https://bigota.d.miui.com/V12.0.2.0.RKGMIXM/mojito_global_images_V12.0.2.0.RKGMIXM_20210226.0000.00_11.0_global_06f2a9e26b.tgz
Use official xiaomi flash tool to flash it via fastboot.
I'm having error when flashing the fastboot file. it says "platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mojito" || echo Missmatching image and device"
my unit is sunny ( as per mi unlocker )
but there is no file specified for MOJITO or SUNNY.
thank you.
SSEFIROSU said:
I'm having error when flashing the fastboot file. it says "platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mojito" || echo Missmatching image and device"
my unit is sunny ( as per mi unlocker )
but there is no file specified for MOJITO or SUNNY.
thank you.
Click to expand...
Click to collapse
open .bat file and replace content by this code and save
Bash:
@echo off
cd %~dp0
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" goto END
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *sunny" || echo Missmatching image and device
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *sunny" || exit /B 1
platform-tools-windows\fastboot %* flash dsp images\dsp.img
platform-tools-windows\fastboot %* flash xbl_config images\xbl_config.img
platform-tools-windows\fastboot %* flash boot images\boot.img
platform-tools-windows\fastboot %* flash modem images\modem.img
platform-tools-windows\fastboot %* flash vbmeta_system images\vbmeta_system.img
platform-tools-windows\fastboot %* flash tz images\tz.img
platform-tools-windows\fastboot %* flash vbmeta images\vbmeta.img
platform-tools-windows\fastboot %* flash bluetooth images\bluetooth.img
platform-tools-windows\fastboot %* flash abl images\abl.img
platform-tools-windows\fastboot %* flash dtbo images\dtbo.img
platform-tools-windows\fastboot %* flash vendor_boot images\vendor_boot.img
platform-tools-windows\fastboot %* flash keymaster images\keymaster.img
platform-tools-windows\fastboot %* flash uefisecapp images\uefisecapp.img
platform-tools-windows\fastboot %* flash qupfw images\qupfw.img
platform-tools-windows\fastboot %* flash xbl images\xbl.img
platform-tools-windows\fastboot %* flash cmnlib images\cmnlib.img
platform-tools-windows\fastboot %* flash cmnlib64 images\cmnlib64.img
platform-tools-windows\fastboot %* flash devcfg images\devcfg.img
platform-tools-windows\fastboot %* flash hyp images\hyp.img
platform-tools-windows\fastboot %* flash imagefv images\imagefv.img
platform-tools-windows\fastboot %* flash aop images\aop.img
platform-tools-windows\fastboot %* flash cust images\cust.img
platform-tools-windows\fastboot %* flash super images\super.img
platform-tools-windows\fastboot %* set_active a
platform-tools-windows\fastboot %* erase metadata
platform-tools-windows\fastboot -w
platform-tools-windows\fastboot %* reboot
:END
thank you, after flashing it says not play protect certified. i can't access playstore to install apps.