Why MI MIX2S doesn't work on DP4 ? - Treble-Enabled Device Questions and Answers

I see different devices can flash android P DP4 except MIX2S.
I tried more than 5 times but it never boots into system...
I am sure that I flash in a right way...
Does anyone succeed on MIX2S?

Not work too.

I think its a vendor problem

Try to use vendor from official android p and not work

I think you'll need the MiFlash toolkit to flash.
But it isn't great for use as a daily driver if that's what you're intending.

Related

Mi A2 Lite Stuck on Android 8.1 - What am i doing wrong?

Hi everybody,
i have a new Mi A2 Lite. I purchased it from a private person, not a shop, but it was still in foil and opened by me. It works nicely, is fast, the phone feels fine, i like it. It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates. The same for the security patches - they are from nov. 2018, which is nearly a year ago, but there are no updates either.
I wanted to install android 9, so i did lots of tricks and things like using a VPN to poland and resetting the phone and so on, but to no avail - there are no updates.
so...
(1) is there something that can be done wrong? why wouldnt the phone find updates?
(2) is there a way to flash the official OTA zip without unlocking? I do not want a special kernel or rom, i dont want to modyfy anything on the os, i just want the official, latest os on the phone
(3) Any other ideas?
Thanks in advance
damaltor said:
It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates.
Click to expand...
Click to collapse
Hi!
Could you please share a screenshot showing your actual Android build number and kernel version? You might have a fake A2 lite (Redmi 6 Pro).
Edit: Don't flash anything before you're sure that your device is a geniue A2 lite, otherwise you will brick your device.
yep, i heard about that. unfortunately, i did flash it by now, but the flash worked perfectly. i unlocked the bootloader with fastboot, flashed the last fastboot package, and re-locked the bootloader. the device is now on android pie and it still works nicely. is there any way to find out if it is genuine after flashing?
So, now i can say the following:
- the deveice works still well with the flashed software.
- the device did just find and download the google security patches of sep 2019
- the imei of the device passes the xiaomi authentication test
so, i am somewhat sure that the device is an original.
still, i am interested why the device was stuck on the old version. maybe it could only handle incremental updates and the old incremental update was not available anymore?
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
My screens:
ibb.co/SKjNJ6D
ibb.co/YR4793D
Regards!
Facing The same in my Mi A1
The same thing is happening with my Mi A1, I have Android 8.1 an I hadn't update to Android 9. Every day the notification for Android 9 would appear in my phone, saying that is available.
Today that update didn't show and when I checked for updates, it said I was already up to date.
Sorry for my English, I barely know it
Well i could probably Help you to flash your device but you should be sure that the device is not a fake, too. I cannot help you with that though. I will look in here tomorrow and give you a few hints to the flashing process.
So, the screenshots of the A2 Lite look pretty mich exactly like mine did. for me the only way was to reflash the device. if you are interested, i can tell you how, but there is a risk of bricking your device if it is a fake a2 lite. i cannot tell by your screenshots, maybe @thorin0815 can?
Otherwise, do you want to try it and risk ist?
edit: you can put in your imei here to check your phone, though i would not entirely trust it.
https://www.mi.com/global/shield#imei_en
*Deleted* *replay *
chriss7777 said:
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
Click to expand...
Click to collapse
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
well, thats what i did. fortunately there is no longer the need to wait for hours or days to unlock the bootloader, it works in an instant now even without registration.
thorin0815 said:
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
Click to expand...
Click to collapse
I did not notice what update it was downloading. I unboxed it, then I connect to WiFi and it started downloading. Anyway it downloaded aprox. 1GB of data, then restart and update. And now it is stuck with 8.1. I thought it will be Android 9 after update with latest patches.
I validate IMEI's on site and it is valid, also it has all google logos, and so on.
Is there any comprehensive update manual for MiFlash for this model?
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Switch on your phone.
Go to settings, about phone.
Tap the build number multiple times until "you are a developer".
Open the developer options.
Switch on USB debugging.
Switch on "allow unlocking bootloader".
Leave settings.
Download this, and install it, answering yes to all three questions:
https://forum.xda-developers.com/showthread.php?t=2588979
Connect the phone and when asked, accept the adb debug question on your phone. Your computer is now allowed to debug your phone.
Also download your new os from here:
https://xiaomifirmwareupdater.com/miui/ (put your phone model in there and download the latest fastboot image)
Unpack it. Depending on your packing program you might have to unpack twice - you should have a few folders and files.
Download the mi flash tool here:
https://www.xiaomiflash.com/
Now you are ready. Take a deep breath. Make sure your phone is charged, 50% should be enough.
Disconnect and Switch off the phone. Hold volume down and power until a rabbit working on an Android robot is seen on the screen. Now reconnect the cable.
Open a command window on the computer by pressing windows+R and entering "cmd".
In that window, type "fastboot oem unlock" and press enter. You should get the answer "OKAY".
If your phone reboots now, hold volume down and power again until the rabbit is there again.
Start miflash. Show miflash the folder in which you unpacked the os files.
In the lower right select "clean and lock" and then press update, select your phone, and press flash.
Flashing now takes roundabout 5 minutes.
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
damaltor said:
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
Click to expand...
Click to collapse
It works like a charm. Also now it is updating with new security patch. Thanks damaltor!
No problem, good to hear that it worked!

[GSI][UNOFFICIAL] Descendant 4.0.1 Modified [Stable][XT1952-2]

MODIFIED EXCLUSIVELY FOR MOTO G7 PLAY
WARNING
Do not try to install this via fastboot, remove the magisk, to remove just reinstall the Stock Rom
MAIN FEATURES
Added apps
Battery usage statistics working
BusyBox already installed
Gapps already installed
More speed
More battery
Notch fix
Root modified by Spaceminer
Several useless apps removed
Tweaks
And more
DOES NOT WORK
Fingerprint
Automatic brightness
NAVIGATION BAR
If the navigation bar disappears, activate it in the configuration
INSTALLATION INSTRUCTION
1. Download and extract
2. Put the GSI on your memory card
3. Restart your phone in Bootloader / Fastboot mode
4. Open fastboot on your computer
use the command: fastboot -w
use the command: fastboot boot twrp.img
5. TWRP: Install> Install image> Choose image file> Flash on the system
DOWNLOADS
TWRP by Spaceminer: https://mega.nz/file/roRzBCTK#THHq0VMWqgtowJNkY-Id3b9S9H9dhzsJhE83k0Kvt2k
GSI: https://drive.google.com/file/d/1-2L4Hl8iUgHqb-ER0TVggjHsVZQEz8G-/view
Wow, incredible!! Please continue with the work, the system is perfect, thank you very much !!
Thank you for this! Is there a way to remove root on this? I want to see if I can use Magisk instead.
Is there going to be an android 10 build?
Not work lockscreen for me.
wanderleiAlfa said:
Not work lockscreen for me.
Click to expand...
Click to collapse
You need an encrypted data partition, but sadly this means TWRP can't read data, and it wont boot when installed, only through fastboot boot twrp.img
Thanks, i will try.
Adb shell
su 0
/system/bin/phh-securize.sh
Working well on the xt1952-4. Got Magisk installed as well, and disabled the phh-supersu app and a couple other apps I've never heard of. The auto brightness and fingerprints, is that something fixable in the near future? I will l likely keep for a daily driver ROM, especially with those fixes.. Either way, thanks for the ROM here. Worked when other GSIs failed. ?
Anybody has tested this gsi with xt1952-6 variant?
Anybody got this working on boost mobile when the rom setups it says sprint I tried to input the boost apn settings I always use with android 10 GSIs that always works and it’s not working here I can’t get data working on any android 9 GSI at least this one shows a Provider in mobile data other pie GSIs just show 31000 in mobile data I just need this to work I can’t install gps joystick as a system app in Q GSI roms to use system mode but it works in pie ROMS I use it together with smali patcher to avoid rubberbandin
theburrus1 said:
Working well on the xt1952-4. Got Magisk installed as well, and disabled the phh-supersu app and a couple other apps I've never heard of. The auto brightness and fingerprints, is that something fixable in the near future? I will l likely keep for a daily driver ROM, especially with those fixes.. Either way, thanks for the ROM here. Worked when other GSIs failed. [emoji854]
Click to expand...
Click to collapse
Was you able to get smali patcher to work everytime I run the tool I get this error with this rom but with other roms I can run smali patcher with no issue....
([emoji88]Descendent GSI[emoji88])
@PoochyX, in fastboot mode, try configuring the /carrier partition and /fsg to Boost Mobile.
fastboot oem config carrier boost
fastboot oem config fsg-id boost
I have not yet tried this ROM on my Boost device. But those config commands have worked on my other Moto devices when using custom ROMs. Just an idea. These commands prompt the /utags partition to configure the device to specific mobile providers, such as Boost Mobile, Virgin Mobile, etc.
I got it i had to upgrade modem back to android 10 and then data configured properly
PoochyX said:
I got it i had to upgrade modem back to android 10 and then data configured properly
Click to expand...
Click to collapse
That's good to know @PoochyX. Thanks for confirmation on that. By upgrading the modem back to Android 10, I'm assuming you mean the stock Android 10 Retail firmware. Are you referring to NON-HLOS.bin only or NON-HLOS.bin and fsg.mbn? Thanks again.
Viva La Android said:
That's good to know @PoochyX. Thanks for confirmation on that. By upgrading the modem back to Android 10, I'm assuming you mean the stock Android 10 Retail firmware. Are you referring to NON-HLOS.bin only or NON-HLOS.bin and fsg.mbn? Thanks again.
Click to expand...
Click to collapse
Yeah the issue is if you have upgraded to android 10 then you have to use the android 10 modem & fsg with android 9 and Android 10 GSIs (and also u would get signal issues with a android 9 modem on android 10 (even if u didn't upgrade to stock 10 to have to revert to a android 10 modem) also the android 10 DSP bin (adspso) or you won't hear anything when you call somebody but the android 9 dtbo cause android 9 GSIs won't boot with android 10 dtbo but android 10 GSIs can boot with android 9 dtbo...
([emoji88]Descendent GSI[emoji88])
PoochyX said:
Yeah the issue is if you have upgraded to android 10 then you have to use the android 10 modem & fsg with android 9 and Android 10 GSIs (and also u would get signal issues with a android 9 modem on android 10 (even if u didn't upgrade to stock 10 to have to revert to a android 10 modem) also the android 10 DSP bin (adspso) or you won't hear anything when you call somebody but the android 9 dtbo cause android 9 GSIs won't boot with android 10 dtbo but android 10 GSIs can boot with android 9 dtbo...
([emoji88]Descendent GSI[emoji88])
Click to expand...
Click to collapse
That's really good info to know. Thanks as always, @PoochyX.

Problem with Moto G6 Play xt1922-2

Hi, I'm new here so no hate.
I have a problem with the moto g6 play xt1922-2, I can not upload the rom via zip or image. The phone has no software.
I wanted to install lineage 17.1 but all the files that I uploaded on the phone blew the installation error .zip damage so I downloaded from different links and from two different laptops and then I tried to install lineage 16 from this page
http://theupgradeguide.com/2020/01/10/install-android-10-on-moto-g6-lineageos-17-how-to-guide/
And then nothing the same, every time the zip file is damaged, I tried to unpack it and repack it using different programs without any effects.
Not to mention that every time I installed I did a wipe.
I read that it can be twrp bad but I searched for moto g6 and found 3.2.1 and 3.2.3 and no further results.
I even tried to install
PixelExperience_Plus-9.0-arm64_aonly
But still the same, I run out of ideas can anyone help me?
I used the tutorial:
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
email: [email protected]
Your device is arm a but you're trying to install ROMs meant for arm64. That's the first issue. Second problem is there are no ROMs specific to our device. Only GSI ROMs.
Re
what do you mean he's armed? what else than arm64 I can install? which gsi rom do you suggest? can I install the rom pixel experience
tyranrun992 said:
what do you mean he's armed? what else than arm64 I can install? which gsi rom do you suggest? can I install the rom pixel experience
Click to expand...
Click to collapse
Our device is ARM-Aonly is what I mean. I would recommend havoc to flash: https://forum.xda-developers.com/pr...led-device-development/gsi-havoc-os-t3930030/
This app shows you what gsi your device is compatible with. https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
Since our device is arm-aonly, you'll see this as a confirmation in the app:

Question Android 13 bootloop

Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Shipoftheline said:
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Click to expand...
Click to collapse
I can't enter to recocery after flashing android 13
Kirya27 said:
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Click to expand...
Click to collapse
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Lughnasadh said:
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Click to expand...
Click to collapse
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Kirya27 said:
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Click to expand...
Click to collapse
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Lughnasadh said:
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Click to expand...
Click to collapse
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Kirya27 said:
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Click to expand...
Click to collapse
Well, you didn't mention you were using the latest Platform Tools, so I suggested it as that's one of the 1st steps of troubleshooting in these situations. You also didn't specifically mention using Android Flash Tool, so I suggested that as well.
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
This sounds interesting. I'll try it today when I get home and post the results here.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
I tried the method that you described and indeed, for some time the phone worked on Android 13 (however, when it was turned on, it wrote that this device was suddenly damaged due to something, photo below). True, after 15-20 minutes of use, phone rebooted into the bootloop, just for no reason at all. I flashed exactly as you said, separately in each slot ...
I have had this screen when I soft bricked after flashing lineage os. I fixed it with flashtool. My exact setup is windows 11, flashtool through Microsoft edge with the options to force flash and wipe device checked in flashtool. Flashtool has rescued my p6pro many times with this setup.
fil3s said:
У меня был этот экран, когда я завис после прошивки Lineage OS. Починил флештулом. Моя точная настройка — это Windows 11, flashtool через Microsoft Edge с параметрами принудительной прошивки и очистки устройства, отмеченными во flashtool. С помощью этой настройки Flashtool много раз выручал мой p6pro.
Click to expand...
Click to collapse
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Kirya27 said:
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Click to expand...
Click to collapse
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
fil3s said:
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
Click to expand...
Click to collapse
I tired fastboot -w many times
Kirya27 said:
I tired fastboot -w many times
Click to expand...
Click to collapse
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
fil3s said:
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
Click to expand...
Click to collapse
Tried. It turns out the same as on the stock firmware
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
apis903 said:
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
Click to expand...
Click to collapse
They clearly designed these phones to fail. They implied they would be usable for 6 years, but like all previous google phones, it will brick itself within 2. This 6 Pro is definitely the last product I buy from Google. I've had 3 other Nexus/pixel phones, none of which lasted. My sister is still using my hand-me-down iPhone 7 that I dropped off a cliff.
I can't do iphones though, and I don't want to support slave labor.. so my options are extremely limited. I'm only going to buy smartphones produced in the USA. It's dangerously cheap to produce phones using the less strict labor and material laws of foreign countries, phones are being treated as disposable, which is unacceptable. My modified Nexus 5X is perfectly usable despite having half the CPU disabled and being a 7 year old phone, thanks to overclocking. Companies should not release a new device unless it is a worthy upgrade over the previous one. It should happen every 3 years, not every year.
I just hope other nerds wake up and stop supporting Google. We have to boycott Google until they create desirable products. Pixel is so undesirable that they spend their ad money on woke bull**** that no one cares about except the sheep, but they like iPhones. Google is just burning our money and ignoring our needs.
Edit: I'm just salty that I got scammed by Google. They lost all of their people who cared. Google is full of corrupt people who want to make a buck. Pixel 7 is essentially the exact same as Pixel 6. The lack of a pro mode in the camera app perfectly represents Google's priorities. It would take one developer a couple days to add such a feature to the app. Google is not doing ANYTHING good.

Question [Windows 11] [Pad 5][Mindows]

So there's this tutorial for installing windows 11 on Xiaomi Pad 5
Simple and easy way unlike past methods. And it's available for all users
How to Install Windows 11 on Xiaomi Pad 5 - Gizmochina
It’s been more than a year since the Xiaomi Pad 5 is here with all its high-end specifications consisting of Snapdragon 860 and Snapdragon 870 on respective models. Surprisingly, the Android tablet from Xiaomi can now run Windows 11 without any major bugs or flaws. As spotted on Geekbench...
www.gizmochina.com
It works using one click installer (chinese tool)
The problem is that it lack a lot of details and support is only on chinese.
Did anyone tried it?
I searched on the internet no other websites or YouTube videos
Yesterday I was about to install it and try it but the prompt box said there's a high risk of getting a bricked device and using Mi Flash Tool in fastboot won't help after updating the partitions so basically it's beyond my expertise.
I already has the ArrowOS custom ROM not MIUI.
And how can someone fix a bricked device after updating partitions.
I installed windows 11 on my xiaomi mi 8 that have a snapdragon cpu, the same as mi pad 5 and the process should be the same. When i modified partitions for installing windows 11, i was not able to reinstall android because “userdata” partition got deleted. With “parted” tool (or the same tool used for modify partitions), i deleted all windows paritions and re-created the default “userdata” one, so i was able again to install android and use mi flash tool. (Always take a screenshot or a backup of the default partition lable, in case you have to restore it)
Found a video that should be useful:
Thank you so much
The video is great but the tool is much easier (one-click installation tool)
I have no expertise in modifying partitions, so ur experience in ur mi 8 would be very valuable.
I might need to ask u some questions when things get messed up if choose to proceed with it.
Yes
Yousef Kassir said:
Thank you so much
The video is great but the tool is much easier (one-click installation tool)
I have no expertise in modifying partitions, so ur experience in ur mi 8 would be very valuable.
I might need to ask u some questions when things get messed up if choose to proceed with it.
Click to expand...
Click to collapse
yes, i can help you in this process, but it’s a bit different than xiaomi mi 8, because i did it 1 year ago, so, maybe I should be able to help only in cases of problems. If you can, post here a screenshot of the default partition lable.
EDIT: if you want to dualboot, the process is a bit different, because you will have to shrink the userdata partition, not remove it completely. This way you should be able to use flash tool even with windows installed, but I'm not sure, because I'm not familiar with this guide. But remember that with the dualboot you will have less space in both operating systems.
I'd recommend using commands instead of the automatic tool, but if you're not familiar with cmd, then you're free to do whatever you want. However, I leave the official guide (for dualboot) https://github.com/erdilS/Port-Windows-11-Xiaomi-Pad-5/blob/main/guide/English/1-partition-en.md
Yousef Kassir said:
So there's this tutorial for installing windows 11 on Xiaomi Pad 5
Simple and easy way unlike past methods. And it's available for all users
How to Install Windows 11 on Xiaomi Pad 5 - Gizmochina
It’s been more than a year since the Xiaomi Pad 5 is here with all its high-end specifications consisting of Snapdragon 860 and Snapdragon 870 on respective models. Surprisingly, the Android tablet from Xiaomi can now run Windows 11 without any major bugs or flaws. As spotted on Geekbench...
www.gizmochina.com
It works using one click installer (chinese tool)
The problem is that it lack a lot of details and support is only on chinese.
Did anyone tried it?
I searched on the internet no other websites or YouTube videos
Yesterday I was about to install it and try it but the prompt box said there's a high risk of getting a bricked device and using Mi Flash Tool in fastboot won't help after updating the partitions so basically it's beyond my expertise.
I already has the ArrowOS custom ROM not MIUI.
And how can someone fix a bricked device after updating partitions.
Click to expand...
Click to collapse
If you brick your device is very difficult to unbrick it. I have an POCO F3 which is bricked and it has passed over 4 months and i can't do anything to unbrick or restore the partitions. If you are new study a week or two about android partiotions in internet be experienced and after that try to port windows 11.
But if you liked tweaking and you want the maximum perfomance of your tablet take a look at my guide.
The same tool (Engage Machine Toolbox V2.1.2) Has a button to revert the partitions and make userdata last partition and delete the windows ones. Once that's done you simply reboot and will boot to android(in case it crashed in the middle of the process). If it still doesn't boot, flash with mi flash because it will work now, or use fastboot rom. Anything but clear all and lock. Do not use that option(I don't know why it's applied by default at mi flash startup+load images folder).
I just bricked my mi pad 5 last night, struggled for several hours until I managed to revert it to Android. Still haven't been able to install Windows 11 on it. I reach the point in the gizmochina tutorial where it makes the partitions, it never asks for the wim file, throws error : no uefi or windows partitions found. Haven't tried to install manually, like create partitions and flash partitions using cmd.
Blitzz.666 said:
The same tool (Engage Machine Toolbox V2.1.2) Has a button to revert the partitions and make userdata last partition and delete the windows ones. Once that's done you simply reboot and will boot to android(in case it crashed in the middle of the process). If it still doesn't boot, flash with mi flash because it will work now, or use fastboot rom. Anything but clear all and lock. Do not use that option(I don't know why it's applied by default at mi flash startup+load images folder).
I just bricked my mi pad 5 last night, struggled for several hours until I managed to revert it to Android. Still haven't been able to install Windows 11 on it. I reach the point in the gizmochina tutorial where it makes the partitions, it never asks for the wim file, throws error : no uefi or windows partitions found. Haven't tried to install manually, like create partitions and flash partitions using cmd.
Click to expand...
Click to collapse
Try to install It manually, It should work, try to do the steps in the video
Maxsenza151 said:
I'd recommend using commands instead of the automatic tool, but if you're not familiar with cmd, then you're free to do whatever you want. However, I leave the official guide (for dualboot) https://github.com/erdilS/Port-Windows-11-Xiaomi-Pad-5/blob/main/guide/English/1-partition-en.md
Click to expand...
Click to collapse
Much appreciated bro
Blitzz.666 said:
The same tool (Engage Machine Toolbox V2.1.2) Has a button to revert the partitions and make userdata last partition and delete the windows ones. Once that's done you simply reboot and will boot to android(in case it crashed in the middle of the process). If it still doesn't boot, flash with mi flash because it will work now, or use fastboot rom. Anything but clear all and lock. Do not use that option(I don't know why it's applied by default at mi flash startup+load images folder).
I just bricked my mi pad 5 last night, struggled for several hours until I managed to revert it to Android. Still haven't been able to install Windows 11 on it. I reach the point in the gizmochina tutorial where it makes the partitions, it never asks for the wim file, throws error : no uefi or windows partitions found. Haven't tried to install manually, like create partitions and flash partitions using cmd.
Click to expand...
Click to collapse
You're so correct about the clear all and lock thing, it once happened to me during installing fastboot rom cuz its the default option. The solution is just use the mi unlock tool again and it will do the job. Regarding installing windows, will u try the tool again or try manually? In both cases, if it works , please let me know id really appreciate it
I will try the manual way because i spent like 5 hours trying this tool.
5, because there is no backout plan in case something happens.
I always hate this about all tutorials out there : they assume it works 100%. If it fails, no help from anyone.
The tool throws errors like : data is not formatted(because you need to format data via recovery and then boot straight into fastboot...anything else fails), partition table failure(because the userdata is not the last partition(this happens when the partitions are made for windows install), and last error that I got was "windows or uefi partition not found"...i still haven't cracked this one.
I think I have time today to try manually. Will let you know.
Yup that's unfortunate it says if you have questions ask in the comments and there's no comment section at all. It's barely a guide.
For example: they should've mentioned that thing about formatting and booting directly to fast boot. While in the tutorial it says format then reboot then go to fastboot which is useless cuz when you first boot after formatting data you've already lost ur formatted state. Anyways I wish you good luck with manual tutorial.. the dual boot one that Maxsenza151 shared seems a good option. Waiting to hear from u
Yousef Kassir said:
Yup that's unfortunate it says if you have questions ask in the comments and there's no comment section at all. It's barely a guide.
For example: they should've mentioned that thing about formatting and booting directly to fast boot. While in the tutorial it says format then reboot then go to fastboot which is useless cuz when you first boot after formatting data you've already lost ur formatted state. Anyways I wish you good luck with manual tutorial.. the dual boot one that Maxsenza151 shared seems a good option. Waiting to hear from u
Click to expand...
Click to collapse
There is no comment section because the text is copy-paste from somewhere else.
So I did the dual boot and it works like in this tutorial :
Git : https://github.com/erdilS/Port-Windows-11-Xiaomi-Pad-5/
The issue is that camera and speakers do not work and the charge is amazingly slow.
I'm hoping on some driver updates in the future but for now I'm using it on Android...
Blitzz.666 said:
There is no comment section because the text is copy-paste from somewhere else.
So I did the dual boot and it works like in this tutorial :
Git : https://github.com/erdilS/Port-Windows-11-Xiaomi-Pad-5/
The issue is that camera and speakers do not work and the charge is amazingly slow.
I'm hoping on some driver updates in the future but for now I'm using it on Android...
Click to expand...
Click to collapse
Ouch, speakers and camera are important.
I'm glad it booted up, tho. Although it had issues I think you learned new stuff during this tutorial. Thanks for keeping me updated. I hope im the future there will be more driver updates and an easier method.
Yousef Kassir said:
You're so correct about the clear all and lock thing, it once happened to me during installing fastboot rom cuz its the default option. The solution is just use the mi unlock tool again and it will do the job. Regarding installing windows, will u try the tool again or try manually? In both cases, if it works , please let me know id really appreciate it
Click to expand...
Click to collapse
Just do the manual One. The Renegade Project team highly recommend to follow the GitHub guide that i sent to you. If you use your brain, you can do It, its quite simple too. Join Project Renegade telegram group and ask them.
P.S: on the renegade project website they say that you need to follow github guide because there are some importand device-specific steps!
In the photos, you can see what they say.
(There is a uninstall guide too on github)
Yousef Kassir said:
Ouch, speakers and camera are important.
I'm glad it booted up, tho. Although it had issues I think you learned new stuff during this tutorial. Thanks for keeping me updated. I hope im the future there will be more driver updates and an easier method.
Click to expand...
Click to collapse
These features Will be implemented with new driver updates. Its still in work.
Watch here the development status. https://renegade-project.tech/en/state
does/will the pogo keyboard work?
Thanks bro
Maxsenza151 said:
Just do the manual One. The Renegade Project team highly recommend to follow the GitHub guide that i sent to you. If you use your brain, you can do It, its quite simple too. Join Project Renegade telegram group and ask them.
P.S: on the renegade project website they say that you need to follow github guide because there are some importand device-specific steps!
In the photos, you can see what they say.
(There is a uninstall guide too on github)
Click to expand...
Click to collapse
I joined the telegram group, until everything works I'll install it. Now I'm good with arrowos 13, yesterday i tried to install miui 14 dev chinese rom and i bricked my pad 5 and even mi flash tool couldn't make it through. I then managed with a little help of mindows tool and then reflashed arrowos .
Yousef Kassir said:
I joined the telegram group, until everything works I'll install it. Now I'm good with arrowos 13, yesterday i tried to install miui 14 dev chinese rom and i bricked my pad 5 and even mi flash tool couldn't make it through. I then managed with a little help of mindows tool and then reflashed arrowos .
Click to expand...
Click to collapse
How did official rom brick your device lol?
Anyway i found the nabu specific telegram group https://t.me/nabuwoa
I heard that mindows can brick your pad..

Categories

Resources