Related
Hello everyone can anyone tell me how risky to unlock Mi A2? Before this device, I have used nexus 4 and Nexus 5 Galaxy S5, Those devices where easy to unlock, I saw posts here people had issues after unlocking this device. . I am happy with stock pie but I want to enjoy custom ROMs
So any suggestions please??
It is very easy to unlock bootloader but the tricky part comes in with the twrp flashing and installing custom roms since this phone has a a/b partition
Currently running on havoc os and it is buttery smooth with great battery life I would recommend to switch to a good custom ROM from the stock ROM
*Improper flashing in twrp will end up in a boot loop and after flashing twrp always switch slots and same with the ROM also to avoid boot loop
recidivist_ said:
It is very easy to unlock bootloader but the tricky part comes in with the twrp flashing and installing custom roms since this phone has a a/b partition
Currently running on havoc os and it is buttery smooth with great battery life I would recommend to switch to a good custom ROM from the stock ROM
*Improper flashing in twrp will end up in a boot loop and after flashing twrp always switch slots and same with the ROM also to avoid boot loop
Click to expand...
Click to collapse
I on pie now, so unlocking method is same? If there is any link can you please share?
To make it easy I will share how I did it
fastboot oem unlock
fastboot flashing unlock_critical
Download twrp zip and image then
fastboot boot <twrp.img>
Then transfer the zip file then flash it
After flashing do not reboot
Go to reboot option in twrp then change the current slot wipe dalvic cache cache format data then reboot
Am currently on MIUI 11.0.3 flashed with miflash
when i flash a custom rom, my phone gets rebooted to recovery
before flash wipe cache and dakvik and data and system...(the problem persists without and with wipes)
i have tried Pixel experience - Havoc -Evolution X....
also tried flashing global vendor before flash rom, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking
Any solutions for this problem?
thanks
Masoud.Ser said:
Am currently on MIUI 11.0.3 flashed with miflash
when i flash a custom rom, my phone gets rebooted to recovery
before flash wipe cache and dakvik and data and system...(the problem persists without and with wipes)
i have tried Pixel experience - Havoc -Evolution X....
also tried flashing global vendor before flash rom, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking
Any solutions for this problem?
thanks
Click to expand...
Click to collapse
Format the data partition in TWRP. You need to do this when installing over MIUI.
Robbo.5000 said:
Format the data partition in TWRP. You need to do this when installing over MIUI.
Click to expand...
Click to collapse
thanks
but after Format the data partition and Wipe cache and dakvik and mount and unmount the data partition and reboot and flash rom
and reboot to system my phone gets rebooted to recovery again
Masoud.Ser said:
thanks
but after Format the data partition and Wipe cache and dakvik and mount and unmount the data partition and reboot and flash rom
and reboot to system my phone gets rebooted to recovery again
Click to expand...
Click to collapse
Are you booting into MIUI at least once after flashing it, before flashing anything else?
I've stopped doing the mount/unmount. I now always reboot back into TWRP after formatting data, seems more reliable.
In TWRP do a factory reset, then format data, then reboot back into TWRP.
After this install the ROM you want
Robbo.5000 said:
Are you booting into MIUI at least once after flashing it, before flashing anything else?
I've stopped doing the mount/unmount. I now always reboot back into TWRP after formatting data, seems more reliable.
In TWRP do a factory reset, then format data, then reboot back into TWRP.
After this install the ROM you want
Click to expand...
Click to collapse
yes booting into MIUI at least once after flashing it
after wipe and flash rom and reboot
phone into twrp again and also internal storage format auto and am cant use storage and must again flash miui rom with miflash for problem storage
Masoud.Ser said:
yes booting into MIUI at least once after flashing it
after wipe and flash rom and reboot
phone into twrp again and also internal storage format auto and am cant use storage and must again flash miui rom with miflash for problem storage
Click to expand...
Click to collapse
Can you provide all the steps you are doing. I can't see any reason why it's not working.
Robbo.5000 said:
Can you provide all the steps you are doing. I can't see any reason why it's not working.
Click to expand...
Click to collapse
1.flash miui 11.0.3 with miflash and boot...no set setup...
2. flash twrp 3 with fastboot and reboot to twrp
3.wipe cache and dakvik
4. wipe data
5.reboot to twrp
6.flash custom rom without error
but after reboot phone again into twrp and no load rom also cant use storage and write and copy file on storage ...
i have tried Pixel experience - Havoc -Evolution X....
Masoud.Ser said:
1.flash miui 11.0.3 with miflash and boot...no set setup...
2. flash twrp 3 with fastboot and reboot to twrp
3.wipe cache and dakvik
4. wipe data
5.reboot to twrp
6.flash custom rom without error
but after reboot phone again into twrp and no load rom also cant use storage and write and copy file on storage ...
i have tried Pixel experience - Havoc -Evolution X....
Click to expand...
Click to collapse
Step 4 needs to be format data, not wipe data, you have to type 'yes' to confirm when you do it.
Robbo.5000 said:
Step 4 needs to be format data, not wipe data, you have to type 'yes' to confirm when you do it.
Click to expand...
Click to collapse
thanks
work good.
I'm new entered the Xiaomi phone discussion
a few short questions
....................
1-Is it necessary to format data for flash in each time?
2-even need to flash miui with miflah and boot before flash custom rom in each time?
and do need to flash vendor global my phone before flash custom roms?
Masoud.Ser said:
thanks
work good.
I'm new entered the Xiaomi phone discussion
a few short questions
....................
1-Is it necessary to format data for flash in each time?
2-even need to flash miui with miflah and boot before flash custom rom in each time?
and do need to flash vendor global my phone before flash custom roms?
Click to expand...
Click to collapse
1 No
2 No
If you want to flash something else, remove lockscreen security first before flashing. This should allow you to dirty flash an update, or clean flash a new ROM, without problems. You only need to format data when flashing over MIUI.
If you get into problems and you cannot successfully get a custom ROM working, this is when you need to flash MIUI first.
You only need to flash vendor/firmware files when the custom ROM recommends/requires a version that is different to what you currently have.
Masoud.Ser said:
Am currently on MIUI 11.0.3 flashed with miflash
when i flash a custom rom, my phone gets rebooted to recovery
before flash wipe cache and dakvik and data and system...(the problem persists without and with wipes)
i have tried Pixel experience - Havoc -Evolution X....
also tried flashing global vendor before flash rom, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking
Any solutions for this problem?
thanks[/QUOTE
Which model is yours indian version or Chinese ?
Click to expand...
Click to collapse
vicky#kick said:
Masoud.Ser said:
Am currently on MIUI 11.0.3 flashed with miflash
when i flash a custom rom, my phone gets rebooted to recovery
before flash wipe cache and dakvik and data and system...(the problem persists without and with wipes)
i have tried Pixel experience - Havoc -Evolution X....
also tried flashing global vendor before flash rom, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking
Any solutions for this problem?
thanks[/QUOTE
Which model is yours indian version or Chinese ?
Click to expand...
Click to collapse
global
Click to expand...
Click to collapse
I am on k20 pro and trying to flash mortal os rc 14 but after flashing it properly it always stucks in bootloop...
1. Clean all the data partitions except internal storage
2. Flashing latest vendor for MIUI
3. Flashing mortal os rc 14 zip file
4. Flashing DFE
5. Rebooting and get stucks in bootloop
Help me what can i do..
aniketkumarak said:
I am on k20 pro and trying to flash mortal os rc 14 but after flashing it properly it always stucks in bootloop...
1. Clean all the data partitions except internal storage
2. Flashing latest vendor for MIUI
3. Flashing mortal os rc 14 zip file
4. Flashing DFE
5. Rebooting and get stucks in bootloop
Help me what can i do..
Click to expand...
Click to collapse
The emoji's screwed up my reply. Try again.
1. Next time create a new post, don't resurrect a vaguely similar old post.
2. Restore MIUI with a fastboot ROM and try again. Use my guide here to help you install the ROM of choice.
https://forum.xda-developers.com/k20-pro/how-to/simple-guide-flipkart-owners-t4151007/post83329343
If you're not sure what you're doing, follow the guide exactly, do not freestyle.
1.Install any rom
2. In recovery factory reset or change data partition to ext2 and then again back to ext4
Reboot
It will boot.
[email protected] said:
2. ...change data partition to ext2 and then again back to ext4...
Click to expand...
Click to collapse
WT........
Seriously?
Hi, I am new to K20 Pro, I have not unlocked my phone yet, I was just going through the forum, to understand all the things and how flashing is done in K20 Pro, I have a question about flashing the vendor, some ROM require it & some don’t, can anyone explain? And how do I choose the correct vendor for my device?? Where can I download the right vendor??
Thanks!
stanlin salu said:
Hi, I am new to K20 Pro, I have not unlocked my phone yet, I was just going through the forum, to understand all the things and how flashing is done in K20 Pro, I have a question about flashing the vendor, some ROM require it & some don’t, can anyone explain? And how do I choose the correct vendor for my device?? Where can I download the right vendor??
Thanks!
Click to expand...
Click to collapse
When flashing you will actually need vendor and firmware files together.
These are taken from the official MIUI fastboot ROMs. You can find them repackaged in a single flashable zip file from here.
https://downloads.akhilnarang.dev/MIUI/raphael/
Flashing one of these files in TWRP is the easiest way to go.
You can also find then repackaged as separate zip files from here
https://xiaomifirmwareupdater.com/
This site has a much greater archive, so is good if you need an older version that you can't find in the other site. You will need to make sure you download vendor and firmware files for the same version.
You should always stick to the version that is for the region of your phone. e.g. Indian vendor and firmware for an Indian K20 Pro, etc.
Some ROMs use an OSS vendor and so this is included as part of the ROM install. In which case there is no need to flash the MIUI vendor.
When a new version of MIUI is released, vendor and firmware files might get updated, to fix a bug or to add extra functionality. In this case some custom ROM devs will include them so that they get the bug fixes or extra functionality in their ROM too. When this happens they will update the minimum vendor and firmware version requirements for their custom ROM - the version will be the actual MIUI version in which the vendor and firmware files were updated.
Where a ROM doesn't specify vendor and firmware and doesn't have an OSS vendor, then it normally implies that any version will work that is from MIUI based on the same Android version. In this case use the most recent version, which you will already have if you've kept up to date with MIUI updates.
When installing a new ROM, you will only need to flash vendor and firmware files if your current version is less than the required version of the new ROM.
Robbo.5000 said:
When flashing you will actually need vendor and firmware files together.
These are taken from the official MIUI fastboot ROMs. You can find them repackaged in a single flashable zip file from here.
https://downloads.akhilnarang.dev/MIUI/raphael/
Flashing one of these files in TWRP is the easiest way to go.
You can also find then repackaged as separate zip files from here
https://xiaomifirmwareupdater.com/
This site has a much greater archive, so is good if you need an older version that you can't find in the other site. You will need to make sure you download vendor and firmware files for the same version.
You should always stick to the version that is for the region of your phone. e.g. Indian vendor and firmware for an Indian K20 Pro, etc.
Some ROMs use an OSS vendor and so this is included as part of the ROM install. In which case there is no need to flash the MIUI vendor.
When a new version of MIUI is released, vendor and firmware files might get updated, to fix a bug or to add extra functionality. In this case some custom ROM devs will include them so that they get the bug fixes or extra functionality in their ROM too. When this happens they will update the minimum vendor and firmware version requirements for their custom ROM - the version will be the actual MIUI version in which the vendor and firmware files were updated.
Where a ROM doesn't specify vendor and firmware and doesn't have an OSS vendor, then it normally implies that any version will work that is from MIUI based on the same Android version. In this case use the most recent version, which you will already have if you've kept up to date with MIUI updates.
When installing a new ROM, you will only need to flash vendor and firmware files if your current version is less than the required version of the new ROM.
Click to expand...
Click to collapse
Thanks a lot brother, for this detailed explanation.. [emoji56][emoji1]
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
Code:
fastboot oem unlock
Code:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
Code:
fastboot flash boot_b twrp-3.4.0-0-jasmine_sprout.img
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via
Code:
fastboot flash boot_b jasmine_global_images_V11.0.12.0.QDIMIXM_10.0/images/boot.img
(my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
floydsen said:
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via (my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
Click to expand...
Click to collapse
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
Code:
fastboot boot TWRP-3.4.0-0-jasmine_sprout-for_V11.0.12.0.img
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
floydsen said:
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
Click to expand...
Click to collapse
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
also the name of that looks like one hell of a job ..shorten it to
recovery.img or twrp.img
fastboot boot recovery.img
but first run
fastboot getvar all
& also run fastboot flashing unlock_critical
but most importantly get another recovery
& i don't want to insult your intelligence but after flashing stock did you check to make sure bootloader was still unlocked and that dev settings was activated and that adb was toggled to on and that you authorised adb again
basicall after stock boot device and do the above ..plug in usb ..toggle adb ..authorise ..run adb devices ..if you see your device ..adb reboot bootloader ..fastboot devices ..see your device ..fastboot getvar all ..see bootloader is unlocked ..fastboot flashing unlock_critical if not done yet ...make sure to do ALL the above again after data gets wiped.....put twrp in adb folder ( MUST BE UNOFFICIAL RUSSIAN OR MODUFIED BY NEBRASSY ..rename to revovery.img ...fastboot boot recovery.img .. use file manager to put magisk.zip on internal then flash ..then reboot to rooted phone with stock recovery ...
Sent from my wayne using XDA Labs
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
KevMetal said:
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
floydsen said:
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
Click to expand...
Click to collapse
jajaja well now you know ...be careful ...some "official" roms are also more buggy than unofficial ones for Jasmine/Wayne..
LOS is an example ..so be forewarned .. if you like android 1 i guess stock rooted is a smart option to keep updates and keep device certified for google stuffs . .
alternativeky go FULL custom rom because stock and custom recovery is just a pain and not worth the hassle on an A/B treble device flashable by fastboot ..just boot the recovery when if ever needed
fyi ..you can flash magisk and it will boot ...if you don't try changing the recovery ..so you can have stock rooted with magisk without rcustom recovery...* recommended by me if you only wamt stock with root
Sent from my wayne using XDA Labs
All good now, thanks for your help! I just flashed Magisk (and also TWRP) and everything works nicely! I will need to get some experience, but I'll keep in mind that I maybe want to get rid of the TWRP recovery. Finally security testing is fun again. Thx!
Hi guys, this is my first time owning a Redmi/Xiaomi with a MediaTek SOC (G80). The device was released with Android 10 so it definitely supports Project Treble. My experience with booting GSIs on Qualcomm Snapdragon devices is straightforward but I attempted the same on the Redmi 9 and I noted the following things:
With no kernel sources released, no stable custom recovery to customize my Redmi 9, I went the GSI route via the standard fastboot commands in the bootloader before I discovered that it uses fastbootd instead to flash the system image. Phew! Also the Redmi 9 (lancelot) is compatible with arm64-ab GSIs.
UPDATE 1: GSI booted. Current custom recoveries cannot be used to flash GSIs on devices launched with Q because the system partition is logical and can only be flashed through fastbootd.
UPDATE 2:First successful boot at post #33. I wanted us to share ideas to make it possible for those interested to boot GSIs.
UPDATE 3: Some screenshots are attached below. Go to the guide for how to install.
nielsync said:
Hi guys, this is my first time owning a Redmi/Xiaomi with a MediaTek SOC (G80). The device was released with Android 10 so it definitely supports Project Treble. My experience with booting GSIs on Qualcomm Snapdragon devices is straightforward but I attempted the same on the Redmi 9 and I encountered the following things:
With no kernel sources released, no stable custom recovery, I went the GSI route via fastboot.
Flashing the vbmeta.img and running fastboot flash system system.img gives an error so i experimented with fastboot flash super system.img which worked without giving any errors. My understanding is the super partition contains more than just the system partition.
Despite successfully flashing the system image as the "super" image, I was unable to boot none of the arm64-ab GSIs I tried which included AOSP 10.0 v222 by @phhusson, Havoc-OS-v3.8 by @SKULSHADY and LineageOS 17.1-20200808 by @AndyYan
Lastly, this device being an MTK is very easy to brick!
Anyone successfully booted? Share your experience here with me.
Click to expand...
Click to collapse
You should not play with your device because this device is MediaTek processor device. I already broke my phone twice and I have to go to service centre my luck was good because I do not have to to pay any money but I learn that I never play with my device
[Update]:
This device launched with Android Q with dynamic partitions within the super partition and a relocated fastboot implementation from bootloader to user space. Theoretically to flash a GSI, boot into fastbootd from the bootloader by running the commands as below [Only proceed if you know what you are doing!!!]:
fastboot reboot fastboot
fastboot flash system system.img
fastboot -w
fastboot erase userdata (if this command doesn't work type fastboot reboot bootloader then fastboot erase userdata)
fastboot reboot
As a result of restoring my bricked device after flashing an unstable custom recovery, my bootloader relocked and therefore can't run above commands now to test if they work. I'll try again after 336 hours!
nielsync said:
[Update]:
This device launched with Android Q with dynamic partitions within the super partition and a relocated fastboot implementation from bootloader to user space. Theoretically to flash a GSI, boot into fastbootd from the bootloader by running the commands as below [Only proceed if you know what you are doing!!!]:
fastboot reboot fastboot
fastboot flash system system.img
fastboot -w
fastboot erase userdata (if this command doesn't work type fastboot reboot bootloader then fastboot erase userdata)
fastboot reboot
As a result of restoring my bricked device after flashing an unstable custom recovery, my bootloader relocked and therefore can't run above commands now to test if they work. I'll try again after 336 hours!
Click to expand...
Click to collapse
Ok i also wait for you...in my case i get 7 day wait time.....after your waiting time finished you should try as follow
Fastboot earse system
Fastboot flash system system.img.
Fastboot flash vbmeta vbmeta.img(download vbmeta.img from this post..it is important to disable Android verified boot.
You can warp data first or latter this prossess...
But i confused what type gsi should download.
A/b or a only....
I know our device does not support a/b. But it use system as root....
Shas45558 said:
Ok i also wait for you...in my case i get 7 day wait time.....after your waiting time finished you should try as follow
Fastboot earse system
Fastboot flash system system.img.
Fastboot flash vbmeta vbmeta.img(download vbmeta.img from this post..it is important to disable Android verified boot.
You can warp data first or latter this prossess...
But i confused what type gsi should download.
A/b or a only....
I know our device does not support a/b. But it use system as root....
Click to expand...
Click to collapse
The above commands can only run after booting into fastbootd apart from "fastboot flash vbmeta" due to the partitioning of the Redmi 9 and other devices launched with Android 10 that come with a SUPER partition that includes the SYSTEM, VENDOR and PRODUCT images. When you boot into fastbootd your device will be listed as "lancelot" in Device Manager under "other devices". Just make sure you have latest Xiaomi drivers and running fastboot commands via the latest Android Platform Tools. Use arm64 A/B GSIs even though it doesn't support seamless updates. I am still waiting for the bootloader unlock to start enjoying
nielsync said:
The above commands can only run after booting into fastbootd apart from "fastboot flash vbmeta" due to the partitioning of the Redmi 9 and other devices launched with Android 10 that come with a SUPER partition that includes the SYSTEM, VENDOR and PRODUCT images. When you boot into fastbootd your device will be listed as "lancelot" in Device Manager under "other devices". Just make sure you have latest Xiaomi drivers and running fastboot commands via the latest Android Platform Tools. Use arm64 A/B GSIs even though it doesn't support seamless updates. I am still waiting for the bootloader unlock to start enjoying
Click to expand...
Click to collapse
Tnx for great answer...
But why we use a/b gsi image file when our device does not support seamless updated??
Our device has a slot only
Shas45558 said:
Tnx for great answer...
But why we use a/b gsi image file when our device does not support seamless updated??
Our device has a slot only
Click to expand...
Click to collapse
Well I can't give a technical answer but I've come to realize that not all system-as-root devices support A/B partitioning but all A/B devices are definitely system as root! Similarly the Redmi 8a (a64-a/b) and 8 (arm64-a/b) also boot A/B GSIs. I say this after flashing GSIs on both devices in the past before I got the Redmi 9. I'm a Redmi boy :good:
nielsync said:
Well I can't give a technical answer but I've come to realize that not all system-as-root devices support A/B partitioning but all A/B devices are definitely system as root! Similarly the Redmi 8a (a64-a/b) and 8 (arm64-a/b) also boot A/B GSIs. I say this after flashing GSIs on both devices in the past before I got the Redmi 9. I'm a Redmi boy :good:
Click to expand...
Click to collapse
It is very great bro... I already broke my phone two time and I have to go to service centre. I was lucky because they do not take any money from me. When your waiting time is over then you flash gsi rom... And if you successfully boot your device then you you must share the process how you do it... I am very excited To use a gsi rom in my device...with out break it again... Because this time I think if I break my device
Then I have to pay the service centre
You should not flash unofficial TWRP recovery because our redmi 9 source code not published yet so the recovery has some problem and if you flash IT again your device is broke again. So I think fastboot method is safe for us
Shas45558 said:
It is very great bro... I already broke my phone two time and I have to go to service centre. I was lucky because they do not take any money from me. When your waiting time is over then you flash gsi rom... And if you successfully boot your device then you you must share the process how you do it... I am very excited To use a gsi rom in my device...with out break it again... Because this time I think if I break my device
Then I have to pay the service centre
You should not flash unofficial TWRP recovery because our redmi 9 source code not published yet so the recovery has some problem and if you flash IT again your device is broke again. So I think fastboot method is safe for us
Click to expand...
Click to collapse
You are right. Flashing that recovery caused me problems too and that's why my bootloader got locked again after restoring. Before that I tried everything to flash a GSI but could not boot. So I tried installing the GSI via that recovery and kaput
nielsync said:
You are right. Flashing that recovery caused me problems too and that's why my bootloader got locked again after restoring. Before that I tried everything to flash a GSI but could not boot. So I tried installing the GSI via that recovery and kaput
Click to expand...
Click to collapse
That's mean we have to wait when stable recovery made for our device....
It took forever
We may be out of luck with the kernel sources. Last I checked, Xiaomi had also not released sources for the Redmi Note 9 series so at least we are not alone. With no hope for Xiaomi EU ROMS, booting a GSI is now our only hope of customizing our device. The problem is, it has not happened yet. @Shas45558 maybe you will be the hero who boots the GSI
nielsync said:
We may be out of luck with the kernel sources. Last I checked, Xiaomi had also not released sources for the Redmi Note 9 series so at least we are not alone. With no hope for Xiaomi EU ROMS, booting a GSI is now our only hope of customizing our device. The problem is, it has not happened yet. @Shas45558 maybe you will be the hero who boots the GSI
Click to expand...
Click to collapse
Ha ha ha......
Shas45558 said:
Ha ha ha......
Click to expand...
Click to collapse
You are the most active guy in the Redmi 9 forums :good:
So moving forward I need you to try and boot a GSI on this phone. This post on Mi Community is helpful in understanding our device partition structure.
I think its fairly safe to boot a GSI because the stock recovery is actually maintained. The problem for me was the unofficial TWRP that caused my device to brick.
nielsync said:
You are the most active guy in the Redmi 9 forums :good:
So moving forward I need you to try and boot a GSI on this phone. This post on Mi Community is helpful in understanding our device partition structure.
I think its fairly safe to boot a GSI because the stock recovery is actually maintained. The problem for me was the unofficial TWRP that caused my device to brick.
Click to expand...
Click to collapse
Fastboot and fastbootd are not same...
But how i understand that my device is boot into fastbootd mood not fastboot mood....
Is their any secret key combination to go to fastbootd??
I think twrp methods is lot easier....but unfortunately we have not get stable twrp as soon ...
Shas45558 said:
Fastboot and fastbootd are not same...
But how i understand that my device is boot into fastbootd mood not fastboot mood....
Is their any secret key combination to go to fastbootd??
I think twrp methods is lot easier....but unfortunately we have not get stable twrp as soon ...
Click to expand...
Click to collapse
Sure with official TWRP life would be easy because you can also easily flash the dm-verity and forceencrypt disabler zip otherwise the device fails to boot even when you follow steps correctly. There's no key combination for fastbootd as far as I know. You have to use a command.
To enter fastbootd, run the following commands;
adb reboot fastboot (to boot into the bootloader)
fastboot reboot fastboot (to boot into fastbootd)
For the device to be recognized in Windows 10 you need to manually install unsigned Xiaomi drivers as shown here and after continue with the commands below;
fastboot flash system name_of_system_image.img
fastboot reboot recovery (and format data using MIUI recovery)
fastboot reboot (fingers crossed )
This post from the Redmi Note 9S may be helpful. The difference is that device has a Snapdragon processor as opposed to ours which is a MediaTek.
https://forum.xda-developers.com/showpost.php?p=83503955&postcount=1
Read this....
Shas45558 said:
https://forum.xda-developers.com/showpost.php?p=83503955&postcount=1
Read this....
Click to expand...
Click to collapse
Yeah I've seen it, thanks. That looks more promising than the first one. I haven't tested it yet but I'll do so as soon as I can on my own device. Have you tried it yourself though?
nielsync said:
Yeah I've seen it, thanks. That looks more promising than the first one. I haven't tested it yet but I'll do so as soon as I can on my own device. Have you tried it yourself though?
Click to expand...
Click to collapse
No i afraid to try.....u should try because you can restore your device...i can restore also but my laptop has some problem so do not want to take risk and unoffical is unofficial .....
And i think it is for chaina rom...ii use redmi 9 prime rom....
I'm still waiting a few more days now before I can unlock my bootloader. Can't wait to test it and use it to flash a GSI. The device you helped me root yesterday is also a Redmi 9 but wasn't mine and I can't mess around with someone else phone
nielsync said:
I'm still waiting a few more days now before I can unlock my bootloader. Can't wait to test it and use it to flash a GSI. The device you helped me root yesterday is also a Redmi 9 but wasn't mine and I can't mess around with someone else phone
Click to expand...
Click to collapse
I have also a waiting time of 98 hrs so im also here to help u all and flash gsi.Also theres a new for ya'll that PTRB RECOVERY is being tested nd booted also without any problem so jus wait some time nd stable version will be released .
I just got a hard problem that my Redmi 10 x pro reboots repeatedly and cannot enter the recovery mode or the fastboot mode.The reason for that is that i upgraded my phone to the latest MIUI12 developer ROM and flash the twrp.I want to use the SP flash tool to reflash my phone,but it said that my phone chip is not supported and i need to use the latest SP flash tool.However,the version i used had already been the latest one.It said that MT78 was not supported(or MT68?I dont remember)Hope that someone can help me! MY ＰＨＯＮＥ ＮＯＷ IS COMPLETELY NOT WORKING！
same bro, waiting for method to fix it mine too
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/