Sorry Im new in xiaomi modding,is there a way to flash gsi without twrp?,can I flash gsi from fastboot?
yes, via fastboot. the command is flash system system.img (replace system with the name of the rom). connect to nippon gsi telefram Channel. you can find a large choice of ported rom from xiaomi devices. but i'm not sure vendor are fully compatibile with mediatek. but you can try. flashing system don't damage the bootloader. so you can reflash easy stock in case of problems
wetito said:
yes, via fastboot. the command is flash system system.img (replace system with the name of the rom). connect to nippon gsi telefram Channel. you can find a large choice of ported rom from xiaomi devices. but i'm not sure vendor are fully compatibile with mediatek. but you can try. flashing system don't damage the bootloader. so you can reflash easy stock in case of problems
Click to expand...
Click to collapse
You tried it first???
no... my phone is 3 days old. First i want to test miui. and i think this phone will recive miui 13. so at now i don't want to do heavy modding. only debloating. i like miui. aosp rom have bored me. on my old mi A3 i have try many gsi also android 12 beta. but mi a3 is not an mtk phone. so the only way to know if gsi works is try. i'm quite sure that many gsi will boot. i think the gsi much compatible are note 8 ported
Installed android 12 gsi via dynamic system update. Requires a unlocked bootloader.
Note that my phone has dm-verify corrupt on boot, but still works. The dsu loader seems to be functional. You would have package custom gsi's to load via dsu.
But being able to duel boot std ROM + gsi ROM is a win
Auswolf said:
Installed android 12 gsi via dynamic system update. Requires a unlocked bootloader.
Note that my phone has dm-verify corrupt on boot, but still works. The dsu loader seems to be functional. You would have package custom gsi's to load via dsu.
But being able to duel boot std ROM + gsi ROM is a win
Click to expand...
Click to collapse
Can you try to flash only gsi ROM?
if dsu work well, is the best safe way to try a12. great tips!!!!! sometimes gsi are not fully compatible with vendor. and in particular MTK devices are not modding phones. 99,9% of dev hare on snapdragons. maybe if xiaomi will launch more mtk devides out of China, the situation could change. But in my opinion MIUI don't need to be modded. only debloated and unlocked. Our phone sure will recive miui13 based on A12. I have tryed aosp beta, and the dynamic theming is a fantastic function. implemend on miui will make this rom super cool
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.
Auswolf said:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.
Click to expand...
Click to collapse
nice! connect to nippon gsi. there is a lot of gsi. of all major custom rom. and also miui
Auswolf said:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.
Click to expand...
Click to collapse
But I want only 1 boot not dual boot
use command fastboot flash system... or via twrp (twrp touch don't work but you can use twrp manager in pc terminal with phone connected via usb). internet is full of guide how to flash gsi via twrp. if you like aosp rom try android 12 beta. or dot os. new 5.2 is out. the system ui is very cool. and official gsi for all android go out soon
wetito said:
use command fastboot flash system... or via twrp (twrp touch don't work but you can use twrp manager in pc terminal with phone connected via usb). internet is full of guide how to flash gsi via twrp. if you like aosp rom try android 12 beta. or dot os. new 5.2 is out. the system ui is very cool. and official gsi for all android go out soon
Click to expand...
Click to collapse
Can you try I don't want to brick my phone
oh no! my phone is 3 day old and i love miui. it's impossibile damage bootloader flashing a generic system img. you have alreagy unlock bootloader. if phone dont dont boot you can easily reflash stock via miflash. i will bootloader only when xiaomi will stops major updates. i post my news only for user that live aosp roms
wetito said:
oh no! my phone is 3 day old and i love miui. it's impossibile damage bootloader flashing a generic system img. you have alreagy unlock bootloader. if phone dont dont boot you can easily reflash stock via miflash. i will bootloader only when xiaomi will stops major updates. i post my news only for user that live aosp roms
Click to expand...
Click to collapse
My bootloader still not unlocked ._. but I bricked my phone just putting it in fastboot mode
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse
wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse
My phone bricked after going to fastboot and DM verify corrupted
wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse
Fire1511 said:
My phone bricked after going to fastboot and DM verify corrupted
Click to expand...
Click to collapse
because you flashed a bad full rom with boitloader locked. i suppose a china rom. all guide are clear "Unlock bootloader before"
using a gsi is safe to prevent big damage. because flash only system partition. probably you didn't read guide with attention. modding must do carefully. i suggest you reflash stock in edl mode. is the only solution
wetito said:
because you flashed a bad full rom with boitloader locked. i suppose a china rom. all guide are clear "Unlock bootloader before"
using a gsi is safe to prevent big damage. because flash only system partition. probably you didn't read guide with attention. modding must do carefully. i suggest you reflash stock in edl mode. is the only solution
Click to expand...
Click to collapse
I don't flashed anything lol
Fire1511 said:
I don't flashed anything lol
Click to expand...
Click to collapse
you said "my phone is bricked after going to fastboot". it can happen only if you have made a mod. like a no stock recovery or a non stock rom. or you said a lot of stupid claims
wetito said:
you said "my phone is bricked after going to fastboot". it can happen only if you have made a mod. like a no stock recovery or a non stock rom. or you said a lot of stupid claims
Click to expand...
Click to collapse
I went to fastboot fastboot
Related
Hi!
I'm new here and doing some research on flahing pixel experience rom on redmi 4 santoni running on miui 11 based on android nougat.
I've read and watched videos through several guides. I am not sure about flashing lazy flasher.
Now, I know that it disable dm Verity while flashing new custom ROM in Redmi 4 santoni.
Is it necessary to flash lazy flasher along with TWRP image while trying to install the custom ROM after successfully rebooting TWRP recovery without starting miui 11?
Thanks, in advance!
JasGen said:
Hi!
I'm new here and doing some research on flahing pixel experience rom on redmi 4 santoni running on miui 11 based on android nougat.
I've read and watched videos through several guides. I am not sure about flashing lazy flasher.
Now, I know that it disable dm Verity while flashing new custom ROM in Redmi 4 santoni.
Is it necessary to flash lazy flasher along with TWRP image while trying to install the custom ROM after successfully rebooting TWRP recovery without starting miui 11?
Thanks, in advance!
Click to expand...
Click to collapse
I've flash a lot of custom roms, never flash lazy flasher. So I think you don't need it.
JasGen said:
Hi!
I'm new here and doing some research on flahing pixel experience rom on redmi 4 santoni running on miui 11 based on android nougat.
I've read and watched videos through several guides. I am not sure about flashing lazy flasher.
Now, I know that it disable dm Verity while flashing new custom ROM in Redmi 4 santoni.
Is it necessary to flash lazy flasher along with TWRP image while trying to install the custom ROM after successfully rebooting TWRP recovery without starting miui 11?
Thanks, in advance!
Click to expand...
Click to collapse
zkoz said:
I've flash a lot of custom roms, never flash lazy flasher. So I think you don't need it.
Click to expand...
Click to collapse
When I read TWRP installation procedure for my Redmi 4X device in the official website twrp.me they warned me, "This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab".
Videos tutorial for Redmi 4X are also suggesting for and flashing lazy flasher in order to avoid bootloop in this device.
Also, does this lazy flasher permenantly disable DM Verity of a device? Is it safe to use?
I just don't want to root my device.
Try without lazy flasher. Its hard to brick this device. Only unlock bootloader and do the rest things to flash custom rom.
When it comes to twrp use orangefox
zkoz said:
Try without lazy flasher. Its hard to brick this device. Only unlock bootloader and do the rest things to flash custom rom.
When it comes to twrp use orangefox
Click to expand...
Click to collapse
Do you mean to use orangefox instead of TWRP?
JasGen said:
Do you mean to use orangefox instead of TWRP?
Click to expand...
Click to collapse
Yes! Yes! Yes!
zkoz said:
Yes! Yes! Yes!
Click to expand...
Click to collapse
My region is India.
Which region should I choose to download TWRP- America or Europe mirror link? Coz they have provided only these two regions.
JasGen said:
My region is India.
Which region should I choose to download TWRP- America or Europe mirror link? Coz they have provided only these two regions.
Click to expand...
Click to collapse
it doesn't matter. It's only mirror for downloads
zkoz said:
it doesn't matter. It's only mirror for downloads
Click to expand...
Click to collapse
Hey, man thanks I have successfully installed pixel experience 10 on my device. Thanks for your help.
JasGen said:
Hi!
I'm new here and doing some research on flahing pixel experience rom on redmi 4 santoni running on miui 11 based on android nougat.
I've read and watched videos through several guides. I am not sure about flashing lazy flasher.
Now, I know that it disable dm Verity while flashing new custom ROM in Redmi 4 santoni.
Is it necessary to flash lazy flasher along with TWRP image while trying to install the custom ROM after successfully rebooting TWRP recovery without starting miui 11?
Thanks, in advance!
Click to expand...
Click to collapse
Hi. there's no need to flash lazy flasher over custom ROM. It is needed only in the case you want to use TWRP + stock MIUI
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 .
Want to confirm before proceeding, I find this instruction.
How to Root Xiaomi Mi 11 Ultra and Unlock Bootloader
Want to root Xiaomi Mi 11 Ultra with Magisk? Here's how to root Mi 11 Ultra along with a guide to unlock bootloader.
www.ytechb.com
I've already unlocked the bootloader, want to make sure it is safe to do so (won't brick etc)
bump, anybody successfully rooted the phone?
linnil said:
Want to confirm before proceeding, I find this instruction.
How to Root Xiaomi Mi 11 Ultra and Unlock Bootloader
Want to root Xiaomi Mi 11 Ultra with Magisk? Here's how to root Mi 11 Ultra along with a guide to unlock bootloader.
www.ytechb.com
I've already unlocked the bootloader, want to make sure it is safe to do so (won't brick etc)
Click to expand...
Click to collapse
You need to patch to boot image a and boot image b
As descriped here. This worked on my MI11
https://www.getdroidtips.com/root-xiaomi-mi-11/
linnil said:
bump, anybody successfully rooted the phone?
Click to expand...
Click to collapse
Yes. I patched my boot.img with magisk, then flashed it using "fastboot flash boot_ab magisk_patched(boot.img file name).omg"
Caveat: I bricked my device like many others after unlocking the bootloader and flashing xiaomi.eu ROM. I had to have a authorized EDL account holder flash a factory ROM (in my case I had a China variant flashed with the Global ROM), after which I flashed xiaomi.eu latest stable ROM and then rooted it.
does google pay still work after root?
xreactx said:
Caveat: I bricked my device like many others after unlocking the bootloader and flashing xiaomi.eu ROM. I had to have a authorized EDL account holder flash a factory ROM (in my case I had a China variant flashed with the Global ROM), after which I flashed xiaomi.eu latest stable ROM and then rooted it.
Click to expand...
Click to collapse
I still don't get, how you all bricked your phones? I was able to unlock (granted, after 7 days) successfully and update CN with EU-ROM... There's thread for it in this forum.
[ROM][MIUI][star/mars] Xiaomi.eu ROM for Xiaomi MI 11 Pro / Ultra
How to install Xiaomi.eu ROM for Xiaomi MI 11 Pro / Ultra We will release fastboot ROM versions until TWRP for star/mars is released TWRP RELEASED Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on...
forum.xda-developers.com
SanHelios said:
I still don't get, how you all bricked your phones? I was able to unlock (granted, after 7 days) successfully and update CN with EU-ROM...
Click to expand...
Click to collapse
Seems it was an issue with setting the active slot in the installation script. Solution is described here and since then it looks as if no more bricks occur
s3axel said:
Seems it was an issue with setting the active slot in the installation script. Solution is described here and since then it looks as if no more bricks occur
Click to expand...
Click to collapse
Oh thanks, mate. I missed that one..
Now back to issue, does it work, rooting the device the way it is descibred on that page?
SanHelios said:
Oh thanks, mate. I missed that one..
Now back to issue, does it work, rooting the device the way it is descibred on that page?
Click to expand...
Click to collapse
My pleasure
And yes, I rooted my device this way although I took the "fastboot flash boot_ab" approach instead of the separate flashing of a and b.
For updating the ROM I took the boot image before installing, patched it with Magisk, copied it back to the images installation folder and let the update script do its magic - thus I got instant-root for the update...
s3axel said:
My pleasure
And yes, I rooted my device this way although I took the "fastboot flash boot_ab" approach instead of the separate flashing of a and b.
For updating the ROM I took the boot image before installing, patched it with Magisk, copied it back to the images installation folder and let the update script do its magic - thus I got instant-root for the update...
Click to expand...
Click to collapse
well, i just rooted it according to the site's instructions.. it booted up, BUT the Safety-Net-Check was negative... Did i miss something?
you n
SanHelios said:
well, i just rooted it according to the site's instructions.. it booted up, BUT the Safety-Net-Check was negative... Did i miss something?
Click to expand...
Click to collapse
you need to hide Magisk Manager and also Magisk hide Google Play, Play services and Google Services Framework
s3axel said:
My pleasure
And yes, I rooted my device this way although I took the "fastboot flash boot_ab" approach instead of the separate flashing of a and b.
For updating the ROM I took the boot image before installing, patched it with Magisk, copied it back to the images installation folder and let the update script do its magic - thus I got instant-root for the update...
Click to expand...
Click to collapse
I flashed it separately on the second attempt for 12.5.3. The first time I tried flashing the patched boot.img I was greeted with an error.
Hi! I have the latest xiaomi eu weekly installed (21.6.23) as well as unofficial twrp.
I would like to root the phone with magisk, but I don't understand a few things.
Magisk manager require patching the boot.img file from the zip firmware.
I can not just simply install magisk zip file in twrp to root mi11 ultra?
If not, I understand that I have to patch the boot.img- but do I have to do it every time I want to install update of the latest xiaomi.eu firmware?
The second question is about data.
Am I loosing the data by rooting the device by this method?
EDIT:
Ok, I managed. So those are the steps that I did:
I unpacked the boot.img from the xiaomi.eu firmware in my phone. Then I patched the file, and copy this file to the adb installation folder of my pc.
Later it's easy- usb debugging needs to be active in developer options, then connect your phone by the cable to your pc, accept usb debugging in your phone, start CMD in the adb folder in your pc and write the command:
fastboot flash boot_ab nameofthefilewhatmagiskgenerated.img
then
fastboot reboot
And done, root works. Data are untouched.
I did it easier, boot into twrp and flash magisk.zip done
Also I'm on official EEA firmware, with original stock recovery, so doesn't matter what rom you use. On xiaomi EU you don't even need adb because you already have twrp injected
Is there anything to worry about when you update the phone while having root access?
Is the following order right?
1) update Rom over twrp and delete dalvik&cache
2)flash magisk.zip again
3)boot into system
Right ?
I have the latest EU Rom 12.5.7...
Just take this bat with decrypted Star twrp 3.5.1
unzip and klick Install-Star.bat
fastboot boot star.img are the commands in there
xNAPx said:
I did it easier, boot into twrp and flash magisk.zip done
Click to expand...
Click to collapse
how did you get twrp on your mi 11??? I cannot find a working method. I have Global ver
ottjoshua said:
how did you get twrp on your mi 11??? I cannot find a working method. I have Global ver
Click to expand...
Click to collapse
why Pixel experience rom is not available for redmi note 10s yet?
i beg developers attention, plz make this rom for redmi note 10s
there is not an official TWRP, thats why.... but you can still install GSI roms
maur0p said:
there is not an official TWRP, thats why.... but you can still install GSI roms
Click to expand...
Click to collapse
I have some question
1. Does phone manufacture provide this twrp?
2. how can I install GSI ROMs?
3. Is there any possibility to release the twrp mode?
is there any change to release pixel experience for redmi note 10s
shiblu06 said:
I have some question
1. Does phone manufacture provide this twrp?
2. how can I install GSI ROMs?
3. Is there any possibility to release the twrp mode?
Click to expand...
Click to collapse
1. we already have twrp
2. fastbootd
3. what
Oh btw just to add, lineageos (built from source) booted, but don't expect it to be released soon, nor pixel experience to get released
J6idot said:
1. we already have twrp
2. fastbootd
3. what
Oh btw just to add, lineageos (built from source) booted, but don't expect it to be released soon, nor pixel experience to get released
Click to expand...
Click to collapse
but eventually note 10s will get pixel experience right , i mean without bugs
phoenixnithish2112 said:
but eventually note 10s will get pixel experience right , i mean without bugs
Click to expand...
Click to collapse
too late
does flashing a miui rom;for example miui14; using pe recovery lock the bootloader again?
is there way to flash to the new miui14 without locking back the bootloader?
thank you
kidbetin said:
does flashing a miui rom;for example miui14; using pe recovery lock the bootloader again?
is there way to flash to the new miui14 without locking back the bootloader?
thank you
Click to expand...
Click to collapse
No, you will get a nice bootloop if you try that
tutibreaker said:
No, you will get a nice bootloop if you try that
Click to expand...
Click to collapse
thank you
what rom can i flash with the pe recovery?
kidbetin said:
thank you
what rom can i flash with the pe recovery?
Click to expand...
Click to collapse
none if you want still have a phone to use
There is one rom now https://download.pixelexperience.org/rosemary/
Has anyone installed the PE rom yet? I tried yesterday, following the instructions, and just got a boot loop after flashing the PE recovery rom.
However, the instructions confused me a little...
Flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
Click to expand...
Click to collapse
fastboot flash boot <recovery_filename>.img
Click to expand...
Click to collapse
(My bold)
Should that be 'fastboot flash recovery' ??
Also, I'm not coming from stock but from a custom ROM (riceDroid). Would that make a difference?
Thanks for any (kind) comments
portcere said:
Has anyone installed the PE rom yet? I tried yesterday, following the instructions, and just got a boot loop after flashing the PE recovery rom.
However, the instructions confused me a little...
(My bold)
Should that be 'fastboot flash recovery' ??
Also, I'm not coming from stock but from a custom ROM (riceDroid). Would that make a difference?
Thanks for any (kind) comments
Click to expand...
Click to collapse
Hey, I ran into the same problem today. If I find a solution, I'll let you know. I would be glad if you share too.
I tried again yesterday to install Pixel Experience, and again it just boot loops when booting into recovery mode. I've now reinstalled stock Miui and will try again.
portcere said:
Has anyone installed the PE rom yet? I tried yesterday, following the instructions, and just got a boot loop after flashing the PE recovery rom.
However, the instructions confused me a little...
(My bold)
Should that be 'fastboot flash recovery' ??
Also, I'm not coming from stock but from a custom ROM (riceDroid). Would that make a difference?
Thanks for any (kind) comments
Click to expand...
Click to collapse
There no recovery partition so it shouldn't. I'm on this ROM currently and have no problems with installation. The guide says that you need to be on latest global a11 miui (12.5.16.0.RKLMIXM). You didn't miss that?
xuser_0 said:
There no recovery partition so it shouldn't. I'm on this ROM currently and have no problems with installation. The guide says that you need to be on latest global a11 miui (12.5.16.0.RKLMIXM). You didn't miss that?
Click to expand...
Click to collapse
I've no idea what version of the bootloader I'm on as getprop ro.bootloader returns 'unknown'
But, as I'm on "latest" v13 Miui, I suspect the bootloader is the wrong one. Do I have to downdate to 12.5 before installing PE?
Edit: I've downdated the device to 12.5 RKLMIXM and have flased the PE recovery image, all okay. It's now installing the PE zip, so fingers crossed that's it.
Edit edit: I have PE on my device! Thank you at @xuser_0 for highlighting were I'd gone wrong.
The key @JohanGriman appears to be to ensure your device is not on the latest Miui but the latest 12.5 version.
Is there any instructions on how to install Magisk on this? I've tried to usual ways (via apk and flashing .zip thru adb sideload) but it fails to repack the boot image. Will a manual patch of the boot image and reflash work?
Edit: I've been able to directly patch the PE recovery image (as used in the installation process) using the Magisk apk on my device. Can I now flash this patched image to the device?
I don't want to try it as other instructions I've found talk about a vbmeta image that needs to be flashed too, and I don't know if that's necesary.... and I don't want to trash my device again!
Just flash it but it will break safetynet. To fix safetynet enable Zygisk, add google play services to deny list and install shamiko.
xuser_0 said:
Just flash it but it will break safetynet. To fix safetynet enable Zygisk, add google play services to deny list and install shamiko.
Click to expand...
Click to collapse
Thanks, that worked perfectly
Hello dear forum
Just got a huge problem, after installing twrp, i wanted to update from Miui13 to Miui14.
it chopped everything up a bit. But then finally done with a message, see attachment.
Since then I can no longer do a normal restart, the phone just hangs in fastboot mode.
Tested a fastboot boot twrp.img, no success.
Does anyone have advice for me?
Which TWRP(full name)?
this one
twrp-3.7.0_11-0-star.img
i test now a recovery flash with Mi Flash Pro, i thing is the one solution.
Are you sure of the version of your device, Star and not Venus?
Anyway you used a TWRP A11 while the system is A12.
try flashing the correct TWRP A12 again.
star/
Recovery for Xiaomi devices - Browse /star at SourceForge.net
List of relevant recovery in one place
sourceforge.net
venus/
Recovery for Xiaomi devices - Browse /venus at SourceForge.net
List of relevant recovery in one place
sourceforge.net
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP
If the TWRP flash works:
TWRP/wipe format data type yes reboot TWRP.
Sideload or use OTG for flashing the rom.
If nothing works use Miflash.
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
bjnass said:
i test now a recovery flash with Mi Flash Pro, i thing is the one solution.
Click to expand...
Click to collapse
Not a official tool.
that should be official
only works if you log in with the Xiamoi account.
But pimps with all Roms
by the Mi 11 Ultra write -> star
bjnass said:
that should be official
only works if you log in with the Xiamoi account.
But pimps with all Roms
Click to expand...
Click to collapse
Miflash does not require Xiaomi account only MiUnlock.
But it was like that, maybe the Pro version.
now currently I come to the Chinese Recovery 5.0
What is the best thing for me to do?
bjnass said:
by the Mi 11 Ultra write -> star
Click to expand...
Click to collapse
Useful details :Mi 11 venus/Mi 11 ultra Star.
bjnass said:
But it was like that, maybe the Pro version.
now currently I come to the Chinese Recovery 5.0
What is the best thing for me to do?
Click to expand...
Click to collapse
If that didn't work use Mi Flash (dont relock the bootloader).
Phone starts only in Fastboot
Hello dear forum Just got a huge problem, after installing twrp, i wanted to update from Miui13 to Miui14. it chopped everything up a bit. But then finally done with a message, see attachment. Since then I can no longer do a normal restart...
forum.xda-developers.com
now the phone has reset itself
So install everything again from the beginning, hope it works directly with Miui 14.
Which twrp should I take A12 Or A13?
bjnass said:
now the phone has reset itself
So install everything again from the beginning, hope it works directly with Miui 14.
Which twrp should I take A12 Or A13?
Click to expand...
Click to collapse
If the system is A12 Miui 13, TWRP A12.
If the system is A13 Miui 14,TWRP A13.
Why didn't you flash MIUI 14 with Miflash?
Yes i test it but dont work.
when i take the xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13 rom mi Flash say
-> couldn't find flash script.
and on the server dont have more Miui14 Rom with fastboot script include
bjnass said:
Yes i test it but dont work.
when i take the xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13 rom mi Flash say
-> couldn't find flash script.
and on the server dont have more Miui14 Rom with fastboot script include
Click to expand...
Click to collapse
TGZ files not ZIP.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Package Name: star_global_images_V14.0.1.0.TKAMIXM_20230210.0000.00_13.0_global_3abbe1c73e.tgz
Version CN
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
This is the gobal image ??
i like the EU Rom
bjnass said:
This is the gobal image ??
Click to expand...
Click to collapse
Yep, and below the CN version.
bjnass said:
i like the EU Rom
Click to expand...
Click to collapse
Xiaomi EU rom is a custom rom not a stock.