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.
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.
Good day,
I need advice. I have a Mi 10 and until recently I had V12.0.6.0.QJBEUXM on Android 10, my phone offered me an update to android 11 V12.2.4.0.RJBEUXM. Some things stopped working so I then found out according to Google that this is a beta version (I probably had my updates enabled, my stupidity) anyway when I wanted to get V12.0.6.0.QJBEUXM back to my phone so I'm stuck on the fastboot screen. I had the bootloader locked, but when I found out that it was a beta version, I unlocked the bootloader and wanted to load back the previous version with android 10 via flash, but the flash tool throws me one error after another, first "sparecrclist error" and then " missmatching image and device "which is bull**** because I have a 100% correct version. I have the bootloader unlocked, but I can't flash any rom on it beacuse mi flast tool throw erros. Can you advise what to do with it?
Solution to Miflash crclist error / failed.
1: Download OFFICIAL MIUI ROM and unzip this ROM to any folder.
2: Open this folder , you'll find 3 files named "flash_all.bat""flash_all_except_storage.bat""flash_all_lock.bat" , create a copy and back them up to another folder for safe.
3: Open and edit the file according to your needs (for example , you need to edit flash_all.bat if you want your phone leaves no files.), Find the listed code:
fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Add "REM"before the two lines , like this:
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Save and exit after this done.
4: Launch Miflash , flash this ROM like usual
if it shows "FAILED" after flash complete and your phone exit fastboot and go dark , congratulations ! you have successfully flashed this ROM !I can't send a connection, just look at it
Problem solved, i have to flash twrp and install Xiaomi.eu rom then via twrp flash global rom with android 10 a then reset and flash via mi flash and lock bootloader.
Platform-Tools
Windows - Mac OS - Linux
Drivers
Windows 64 Bit - 32 Bit - Mac OS
Zip
Stock Firmware (Android 11) - Bootloader Unlock
GSI ROM (PixelExperience_Plus_arm64-ab-11.0-20211011-UNOFFICIAL.img.xz)
product_gsi.img
Root Magisk (rename the .apk file extension to .zip) installing using recovery OrangeFoxR11.1 - twrp_3.6.1-11-0
****COMMAND****
flash stock - flash gsi
adb reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
exit
adb reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash product product_gsi.img
fastboot flash boot boot2.img
fastboot flash system pixel.img
fastboot flash recovery recovery2.img
fastboot -w
fastboot reboot
exit
Click to expand...
Click to collapse
Spoiler
- boot boot2.img and recovery recovery2.img <---- optional
- fastboot flash system pixel.img <---- rom-name
Procedure to install the GSI custom ROM
- Extract Platform Tools + Stock Firmware + GSI ROM + gsi product (in the same folder) and launch commands, easy
List + GSI
II'm test before, thanks
Si alguien lo prueba para hacerle saber cómo le está yendo
I've already tried it and it can't install the rom, I don't know if I'm executing the command wrong or what, but it didn't work for me.
Kira565 said:
I've already tried it and it can't install the rom, I don't know if I'm executing the command wrong or what, but it didn't work for me.
Click to expand...
Click to collapse
1. https://mirrors.lolinet.com/firmware/moto/astro/official/
2. Ctrl + F download rom "RPL31" (RPLS31, not)
3. After you install the Stock ROM and the device starts correctly, activate usb debugging and execute these commands:
adb reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash product product_gsi.img
fastboot flash system ROM.img
fastboot -w
fastboot reboot
exit
Por favor de um jeito pelo Orange Fox sem PC
Alexsjvr1 said:
Melhor da um jeito pelo Orange Fox sem utilização de PC por favor
Click to expand...
Click to collapse
Alexsjvr1 said:
1. https://mirrors.lolinet.com/firmware/moto/astro/official/
2. Ctrl + F download rom "RPL31" (RPLS31, not)
3. After you install the Stock ROM and the device starts correctly, activate usb debugging and execute these commands:
adb reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash product product_gsi.img
fastboot flash system ROM.img
fastboot -w
fastboot reboot
exit
Click to expand...
Click to collapse
thanks bro I already tried several I am currently on corvus gsi
Alexsjvr1 said:
Hello! How are you? This is my first post on this page, and I wanted to share the method to install GSI ROM on this One Fusion, I do it at the request of a friend
It is a simple process that does not take more than 15 minutes, come on! !
SDK tools platform 7-Zip
Windows - Mac OS - Linux
Windows Drivers 64 Bit 32 Bit - Mac OS
Stock Firmware (Android 11) - Bootloader Unlock
GSI ROM (PixelExperience_Plus_arm64-ab-vndklite-11) - product_gsi.img
Magisk (rename the .apk file extension to .zip) installing using custom recovery
or you can try this already patched image magisk_patched
COMMAND
Spoiler
- boot boot2.img and recovery recovery2.img <---- optional
- fastboot flash system pixel.img <---- rom-name
Procedure to install the GSI custom ROM
- Extract Platform Tools + Stock Firmware + GSI ROM + gsi product (in the same folder) and launch commands, easy
Here is a link that I find interesting to share for those who have not yet decided which rom to install 15 best custom ROMs
Click to expand...
Click to collapse
its faster and stable, but the multimedia audio via Bluetooth does not work.
In Logcat... Bluetooth is crazy and has battery drain... the rom needs a FIX.
I RECOMMEND CrDroid GSI ctrl+f (-arm64-bgZ-lite.img.xz)
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
reddermanu said:
its faster and stable, but the multimedia audio via Bluetooth does not work.
In Logcat... Bluetooth is crazy and has battery drain... the rom needs a FIX.
Click to expand...
Click to collapse
You can fix the bluetooth media audio disabling the A2DP offload in PHH settings, I have also experienced the battery drain issue on most GSIs, try to stick to AOSP as I haven't met any battery drain there.
reddermanu said:
its faster and stable, but the multimedia audio via Bluetooth does not work.
In Logcat... Bluetooth is crazy and has battery drain... the rom needs a FIX.
Click to expand...
Click to collapse
Solution to Bluetooth connection problem
To fix the Bluetooth connection problem, simply go to Settings/PHH Treble Settings/Misc Features and check the Force-disable A2DP offload option. Then, restart the phone.
KUATIKO said:
I RECOMMEND CrDroid GSI ctrl+f (-arm64-bgZ-lite.img.xz)
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Click to expand...
Click to collapse
crDroid exelent option
I got the following error when I executed the command fastboot flash system image:
target reported max download size of 536870912 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/6 (524212 KB)...
OKAY [ 13.213s]
writing 'system_a' 1/6...
OKAY [ 2.874s]
sending sparse 'system_a' 2/6 (518272 KB)...
OKAY [ 13.113s]
writing 'system_a' 2/6...
FAILED (remote: Operation not permitted)
finished. total time: 31.563s
Click to expand...
Click to collapse
The bootloader is unlocked and I flashed the stock rom as described on tutorial.
lteixeiramnc said:
I got the following error when I executed the command fastboot flash system image:
The bootloader is unlocked and I flashed the stock rom as described on tutorial.
Click to expand...
Click to collapse
@lteixeiramnc you must use the latest version of fastboot https://developer.android.com/studio/releases/platform-tools.
crdroid is the best https://sourceforge.net/projects/tr...om-v316-220330-arm64-bgZ-lite.img.xz/download
disable the A2DP offload in PHH settings!
Alexsjvr1 said:
Hello! How are you? This is my first post on this page, and I wanted to share the method to install GSI ROM on this One Fusion, I do it at the request of a friend
It is a simple process that does not take more than 15 minutes, come on! !
SDK tools platform - 7-Zip
Windows - Mac OS - Linux
Windows Drivers 64 Bit 32 Bit - Mac OS
Stock Firmware (Android 11) - Bootloader Unlock
GSI ROM (PixelExperience_Plus_arm64-ab-vndklite-11) - product_gsi.img
Magisk (rename the .apk file extension to .zip) installing using custom recovery
or you can try this already patched image magisk_patched
COMMAND
Spoiler
- boot boot2.img and recovery recovery2.img <---- optional
- fastboot flash system pixel.img <---- rom-name
Procedure to install the GSI custom ROM
- Extract Platform Tools + Stock Firmware + GSI ROM + gsi product (in the same folder) and launch commands, easy
Here is a link that I find interesting to share for those who have not yet decided which rom to install 15 best custom ROMs
Click to expand...
Click to collapse
@dpkg-i-foo-deb @Alexsjvr1 masters!
can i install a android12 gsi??
latest pixelexperience for example?
reddermanu said:
@dpkg-i-foo-deb @Alexsjvr1 masters!
can i install a android12 gsi??
latest pixelexperience for example?
Click to expand...
Click to collapse
Yes+info: https://teletype.in/@syoker/XT2073-FlashGSIROM_EN
Alexsjvr1 said:
Yes+info: https://teletype.in/@syoker/XT2073-FlashGSIROM_EN
Click to expand...
Click to collapse
@Alexsjvr1 best android 12 gsi rom for astro? help with link... I don't know which one to download
reddermanu said:
@Alexsjvr1 best android 12 gsi rom for astro? help with link... I don't know which one to download
Click to expand...
Click to collapse
These are the most used:
Pixel Experience Plus
Release Pixel Experience Plus 12.1 v412 · ponces/treble_build_pe
Initial PE+ build Sync with April sources of PE+ Sync with AOSP 12.1 v412 (thanks @phhusson) Clean flash is not required if coming from normal version!
github.com
SuperiorOS
xiaomemeindex.com
CorvusOS
Tipz Team Builds - Browse /GSIs/CorvusROM/Beta/20220423 at SourceForge.net
sourceforge.net
crDroid
Gsi_projects - Browse /v412/crDroid-8.4 at SourceForge.net
sourceforge.net
Alexsjvr1 said:
These are the most used:
Pixel Experience Plus
Release Pixel Experience Plus 12.1 v412 · ponces/treble_build_pe
Initial PE+ build Sync with April sources of PE+ Sync with AOSP 12.1 v412 (thanks @phhusson) Clean flash is not required if coming from normal version!
github.com
SuperiorOS
xiaomemeindex.com
CorvusOS
Tipz Team Builds - Browse /GSIs/CorvusROM/Beta/20220423 at SourceForge.net
sourceforge.net
crDroid
Gsi_projects - Browse /v412/crDroid-8.4 at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
thank for the direct linksssssss
Custom ROM installation guide
##Fast check phone active slots:
Cmd command
Adb reboot bootloader
fastboot getvar all
Display show : current active slots a / b
Tested phone list:
1.Tecno KG8 ( Active slots a )
2. Other phone work
##custom rom Architecture: Arm64
##System image name :
X X X os arm64 ab
1.Custom Rom installation process :
Download item :
Product.img link:product.img
Boot.img link : your build numbers boot.img buckup sp tool / Flash file download and boot.img extract
Vbmeta.ing link :
Commands:
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a/b vbmeta.img
Fastboot flash boot_a/b boot.img
fastboot reboot fastboot
fastboot delete-logical-partition product_a/b
fastboot erase system
fastboot flash system_a/b system.img
fastboot create-logical-partition product_a/b 40000
fastboot flash product_a/b producti.img
fastboot -w
fastboot reboot
After boot custom rom
2.Custom Rom root installation:
magisk patches boot.img flash adb
3. custom to stock rom:
Sp flash tool to format and download
##Gcam/Camara :Camara go apk
## Common Problem fixed :
1. Speaker and Headphones working at the same time gsi rom: Video clip
4.Custom Rom Link: Tested rom :
Arm64
## Official Android 12 :
1. AOSP OS
Thanks for Phhusson
Download link :
1.system-squeak-arm64-ab-gapps
2. system-squeak-arm64-ab-vndklite-gapps
2. Corvus OS
Thanks for TipzTeam2
Download link :
1.Corvus_vS3.2-Vindicate-treble_arm64_ab-Gapps-Official-00521007
2.Corvus_vS3.2-Vindicate-treble_arm64_ab_vndklite-Gapps-Official-00521007
## Unofficial Android 12 :
1. Pixel Experience OS
Thanks for ponces
Download link:
1.PixelExperience_Plus_arm64-ab-12.1-20220722-UNOFFICIAL
2.PixelExperience_Plus_arm64-ab-vndklite-12.1-20220722-UNOFFICIA
Custom Rom download link : Generic-System-Image
(update custom rom download)
HIT THE THANKS BUTTON IF ABOVE INFORMATION IS HELPFUL TO YOU
These partitions are important when you'll have to restore the phone back to normal from worst case.
Code:
elableinfo (/dev/block/sda4) - This partition contains Certification Image, may not important.
imeilock (/dev/block/sdg1) - This partition contains your device IMEI.
persist (/dev/block/sda8) - This partition contains your device PSN, MAC, Bluetooth.
oemowninfo (/dev/block/sda2) - This partition contains SKUID, exclusive info, etc.
simlock (/dev/block/sde63) - Carrier locked TA-1251 only. Mandatory to allow your phone boot if your phone isn't carrier locked.
Other Snapdragon 765G based Android phones can also refer this, although we can't guarantee it will 100% apply on your phone. DO NOT FOLLOW THIS GUIDE IF YOU ARE USING TA-1257 (NOKIA 8 V 5G UW from Verizon Wireless).
WARNING:
1. DO NOT SHARE YOUR CRITICAL PARTITION BACKUP IMAGES TO ANYONE ELSE TO PREVENT ABUSE, PLUS, SHARING THIS VIOLATES THE RULE OF XDA.
2. CRITICAL PARTITION BACKUP IMAGES FOR BOTH TA-1243 AND TA-1251 AREN'T INTERCHANGEDABLE.
Click to expand...
Click to collapse
To backup these partitions:
1. Unlock the bootloader and root your phone with Magisk.
2. Execute these commands:
Code:
adb shell mkdir /storage/emulated/0/bgt-critical/
adb shell su
(Confirm root permission on your phone - if you missed that or didn't confirm it, open Magisk app and grant it manually)
adb shell su -c dd if=/dev/block/bootdevice/by-name/imeilock of=/storage/emulated/0/bgt-critical/imeilock.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/persist of=/storage/emulated/0/bgt-critical/persist.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/oemowninfo of=/storage/emulated/0/bgt-critical/oemowninfo.img
adb shell su -c dd if=/dev/block/bootdevice/by-name/simlock of=/storage/emulated/0/bgt-critical/simlock.img
adb pull /storage/emulated/0/bgt-critical/
3. Save entire bgt-critical directory at safe place.
Additionally, you must do QCN backup in case you erased NVRAM at worst case.
To do that:
1. Root your phone with Magisk.
2. Execute this command on your PC with ADB shell for enabling Qualcomm Diag Port:
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,adb
3. Install QPST 2.7.496 and use QPST Software Download to backup both XQCN and QCN images, and save both of them at bgt-critical partition you have saved.
Here's how to reinstall stock firmware, in case you bricked the phone at worst situation.
Please disable automatic translation on your web browser if you can't click "CLICK TO SHOW CONTENT" button.
Click to expand...
Click to collapse
Assuming you have UFS lun0-lun6 erased, or the phone is currently at Qualcomm 900E which are considered worst situation.
1. Download following firmware, and extract it 3 times - you'll get tons of files inside.
bgt-2210-0-00WW-B01.HMDSW.7z | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
2. Use text editor to open rawprogram0_sparse.xml and delete the string super.img inside to save time when doing part 1 flashing.
Use text editor to open rawprogram4.xml and replace the string abl.elf into BGT-abl.elf , then save it.
3. Copy prototype ABL into the firmware directory, and make sure the filename is BGT-abl.elf .
4A. (For Windows users)
Please install QPST 2.7.496 or newer and Qualcomm USB Driver before you proceed. You'd better to erase all other incompatible drivers to increase success rate.
Once installed, please copy QSaharaServer.exe and fh_loader.exe from QPST installation directory (C:\Program Files (x86)\Qualcomm\QPST\bin by default) to firmware directory.
4B. (For macOS / Linux users)
Please install Python EDL from following website:
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
5. If your phone is currently at 900E, you must disassemble the phone by opening the back cover and make sure the motherboard is exposed.
Disconnect the battery, use a pair of tweezers to short the test point, then connect your phone to PC. Using USB 2.0 port is strongly recommended for best stability.
{
"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"
}
If you're using PC that only has USB 3.1 port you may like encounter USB port throttling issue. In this case you must buy an USB hub as workaround.
To check if your phone is properly connected:
(For Windows users)
Please open Device Manager and check if your phone is listed as Qualcomm HS-USB QDLoader 9008 / Qualcomm HS-USB Diagnostics 9008. If not you need to disconnect the phone, short the test point and connect the phone to PC again. Once it's listed you can remove the tweezer.
(For macOS / Linux users)
Please execute this command:
Code:
lsusb
and see if a device started from 05C6:9008 is listed. If yes, you can remove the tweezer and proceed to next step.
6A. (For Windows users)
Please check the COM port in Device Manager, assuming the COM port number is 8.
Open a Command Prompt or PowerShell window at directory where you have tons of firmware files extracted.
Execute this command (replace the COM port number to actual COM port number you see in Device Manager)
Code:
.\QSaharaServer -p \\.\COM8 -s 13:prog_firehose_ddr.elf
If you see a message says image uploaded successfully, you can proceed to next step.
Execute this command to upload rawprogram XML configuration:
Code:
.\fh_loader --port=\\.\COM8 --search_path=. --sendxml=rawprogram0_sparse.xml,rawprogram1.xml,rawprogram2.xml,rawprogram3.xml,rawprogram4.xml,rawprogram5.xml,rawprogram6.xml --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=UFS
Wait for image files being uploaded, now write patch XML configuration:
Code:
.\fh_loader.exe --port=\\.\COM8 --search_path=. --sendxml=patch0.xml,patch1.xml,patch2.xml,patch3.xml,patch4.xml,patch5.xml,patch6.xml --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=UFS
Once these commands are executed successfully, you can disconnect the phone, reconnect the battery and power it on.
Your phone should boot straight into Fastboot mode. If it doesn't boot the battery might be drained, recharge it a little bit before you proceed.
6B. (For macOS / Linux users)
Assuming you have Python EDL installed properly.
Open a terminal under the directory where you have firmware extracted, and execute this command:
Code:
edl qfil rawprogram0_sparse.xml,rawprogram1.xml,rawprogram2.xml,rawprogram3.xml,rawprogram4.xml,rawprogram5.xml,rawprogram6.xml patch0.xml,patch1.xml,patch2.xml,patch3.xml,patch4.xml,patch5.xml,patch6.xml /path/to/where/firmware/images/arelocated/ --memory=ufs --loader=prog_firehose_ddr.elf
Wait for image files being uploaded. If the flashing procedure is throttling, you may want to execute this command before connecting phone with test point shorted.
Once this command is executed successfully, you can disconnect the phone, reconnect the battery and power it on.
Your phone should boot straight into Fastboot mode. If it doesn't boot the battery might be drained, recharge it a little bit before you proceed.
7. Reinstall all other partitions with Fastboot command.
If you're Windows user, please DO NOT USE Minimal ADB and Fastboot, but use this instead: https://developer.android.com/studio/releases/platform-tools
Code:
fastboot flash partition:0 gpt_both0.bin
fastboot --set-active=a reboot-bootloader
fastboot flash xbl xbl.elf
fastboot flash xbl_config xbl_config.elf
fastboot flash abl abl.elf
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash storsec storsec.mbn
fastboot flash pwinfo pwinfo.img
fastboot flash bluetooth BTFM.bin
fastboot flash modem NON-HLOS.bin
fastboot flash core_nhlos Core_NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash logfs logfs_ufs_8mb.bin
fastboot flash keymaster km4.mbn
fastboot flash featenabler featenabler.mbn
fastboot flash toolsfv tools.fv
fastboot flash metadata metadata.img
fastboot flash aop aop.mbn
fastboot flash qupfw qupv3fw.elf
fastboot flash imagefv imagefv.elf
fastboot flash uefisecapp uefi_sec.mbn
fastboot flash multiimgoem multi_image.mbn
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
By doing this will allow your phone boot as the bare minimal situation, but not ideally functional.
Next you must restore critical partitions you have backed up before.
Code:
fastboot erase fsc
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fs_image.img
fastboot flash elableinfo /path/to/bgt-critical/elableinfo.img
fastboot flash imeilock /path/to/bgt-critical/imeilock.img
fastboot flash persist /path/to/bgt-critical/persist.img
fastboot flash oemowninfo /path/to/bgt-critical/oemowninfo.img
fastboot reboot
8. Once your phone boots into normal OS, use Magisk to root your phone, and execute this command to enable Qualcomm Diag Port:
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,adb
9. (For Windows users) Use QPST Software Download to restore the QCN/XQCN image you backed up before. Eject SIM before you doing so to prevent issues.
10. (Skip if you're not using Carrier locked TA-1251) Reboot the phone into Fastboot mode and flash simlock partition:
Code:
adb reboot bootloader
fastboot flash simlock /path/to/bgt-critical/simlock.img
fastboot reboot
11. Enjoy your fully revived Nokia 8.3.
Reserved #3