Hi,
when i was trying to install a new ROM (CM13) to my phone (xiaomi mi3). when i connected it to the computer my computer said i need to format the disk before using. After i did so, when i sideloaded the ROM i told me i was missing partitions to flash this ROM. Does anyone know how to deal with this?
Thanks for any help
Put it in fastboot mode and MiFlash factory image.
Download MIUI ROM Flashing Tool and Xiaomi Mi 3 CDMA/WCDMA Lastest Global Developer Version Fastboot File Download:
http://en.miui.com/a-234.html
Then install TWRP and CM13.
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 had converted my Mi A2 into 6x but i forgot to delete Firmware Update folder. Now i'm using Pixel Experience Rom based on 6X.
Is it possible to go back Mi A2? (Without Opening Phone Backpart
Oline1032 said:
I had converted my Mi A2 into 6x but i forgot to delete Firmware Update folder. Now i'm using Pixel Experience Rom based on 6X.
Is it possible to go back Mi A2? (Without Opening Phone Backpart
Click to expand...
Click to collapse
open fastboot :
fastboot getvar all
there will be a bunch of info ...if the ARB number is higher than 4 the answer is NO
fyi: you can enter edl from fastboot or twrp custom recovery if your phone is in working order .. shorting the pins ( test point) by opening phone physically only becomes necessary if your phone is bricked
open fastboot :
fastboot oem edl
***something to consider is you can't just flash an android 1 rom ...you need to download the repartition script to repartition your partition layout or all attempts will fail
the ROG Phone has like all newest phones A/B partitions.....can i ...install
(exmpl. Custom rom on partition A and keep stock rom on B)?
HomuraEngetsuka1995 said:
the ROG Phone has like all newest phones A/B partitions.....can i ...install
(exmpl. Custom rom on partition A and keep stock rom on B)?
Click to expand...
Click to collapse
bad idea, rog have recovery_a + recovery_b, system_a system_b etc
and one userdata storage
bootloop system guaranteed
So I really new into this, I didn't really know what I was doing but i tried to install Pixel Experience on my device. After some struggle it seems that I managed to flash the rom into system. I followed the instruccions to the part where you wipe all data from the phone, but then it got stucked and didn't start the OS, maybe system got corrupted or something bc when I try to reinstall the rom cmd tells me "This partition doesn't exists".
As far as i know there isn't a version of twrp for Redmi note 10 5g so all I have is Xiaomi ADB Fastboot Tools. Pls help me.
What firmware do you want to install？
Can you elaborate on your installation process, guide instructions and firmware sources?
1:
Do not need to use twrp, general Fastboot command to brush the GSI on the line, after installation to play some black screen patch and settings.
GSI always jumps to Fastboot and Recovery after booting, indicating that there is a problem with GSI, replace it with another variant or downgrade version.
2:
Fastboot Method
https://c.mi.com/thread-1857937-1-0.html
jianjianus said:
What firmware do you want to install？
Can you elaborate on your installation process, guide instructions and firmware sources?
Click to expand...
Click to collapse
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
Fire1511 said:
Code:
I am NOT responsible for bricked devices, destroyed SD cards or any
damage that may happen to your device.
Requirements:
Unlocked bootloader.
WARNINGDon't use Nippon gsi they aren't working,I recommend using phh gsi by @phhusson lineage os by @AndyYan and PE 12 by @ponces
How to guide:
power + volume down button
fastboot reboot fastboot
install fastbootd drivers,follow this tutorial
fastboot set_active a
fastboot erase system
fastboot flash system (name gsi.img)
fastboot --disable-verity --disable-verification flash vbmeta (vbmeta.img)
fastboot flash vbmeta_b (vbmeta.img)
fastboot set_active a
fastboot reboot recovery
in recovery select wipe data
reboot to system
The GSI will be installed in your phone
Bugs:
Brightness slider but you can fix it
Recommended rom:
Pixel experience:
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Select arm64 ab variant
How to fix brightness slider:
Go to phh treble settings,misc settings enable "use alternative brightness scale", "use linear screen brightness slider" and "allow setting brightness to the lowest possible",reboot the device
There is an better alternative to fix this annoying bug,follow this guide!
[GSI] Brightness Fix & Other Fixes
Brightness black lockscreen fixed & Brightness Slider fix. GSI Misc Settings ✅Use Linear Brightness Scale ✅Force Alternatice Backlight Scale ✅Allow Settings to the lowest Flash this file on magisk and reboot :) Note: There's a better fix...
forum.xda-developers.com
How to fix bluetooth audio:
Go to phh treble settings,misc settings, "Force enable a2dp off-load" and "Bluetooth workarounds" select mediatek option and reboot the device.
How to install magisk on your device:
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
How to flash gapps:
You need magisk on your phone
Download this file then flash from magisk
MagiskGApps - Browse /r/Stock at SourceForge.net
GApps for Magisk
sourceforge.net
Click to expand...
Click to collapse
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab
chileangarbage said:
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
Some people have given feedback that this phenomenon occurs with v415.
I tried it and this problem also appeared. They said that dropping down to V414 would not cause this problem.
I don't know if the latest version has a fix?
I have not tried this firmware again and am currently using lineageos19.1
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net
Pixel Experience Plus v415.1 is also reported not to work on MediaTek devices. v414 is the latest working version.
chileangarbage said:
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
chileangarbage said:
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
This tutorial works. But not ABSOLUTELY. I did get stucked on bootloader ever after flashing 3 different images. I think that problem was caused because versions of bootloader in my original ROM and installed GSI image didn't match(I was trying to flash latest Android version but my original ROM was Android 11). So I tried flashing the GSI image with Android version 11 and that worked. Therefore, I wanna say that just don't worry just keep flashing and you'll see the Love One.