This is how it works for me.
If someone knows a better way let me know.
What you need
Xiaomi Mi 10 (UMI) with unlocked bootloader and latest Xiaomi.eu ROM installed
A/B GSI
PC with ADB & Fastboot installed
USB Cable
Mi 10 stock recovery installed or img for installation
TWRP.img for Mi 10 (If you want to install anything else like Magisk or something)
Boot to fastboot
(Skip this part if you're using stock recovery)
Power off your phone
Hold Volume down + Power until you see fastboot screen
Flash stock recovery found in latest firmware
Code:
fastboot flash recovery recovery.img
Boot to recovery
Power off your phone
Hold Volume up + Power until you see recovery screen
Wipe data
Select option Connect with MiAssistant
Reboot into fastbootd (Fastboot User Space)
Code:
adb reboot fastboot
Erase system partition
Code:
fastboot erase system
Flash your GSI
Code:
fastboot flash system system.img
If you're done here and doesn't want to install anything else
Just reboot and enjoy!
Code:
fastboot reboot
If you want to install anything else
Reboot to fastboot
Code:
fastboot reboot bootloader
Boot TWRP
Code:
fastboot boot TWRP.img
Use MTP to transfer your zip files to internal storage
Install them
Reboot
Enjoy!
Working Images (Need to be A/B)
Quack Phh-Treble
AOSP Q Mod //CAOS
Maybe any image with phhusson treble_experimentations included
At this time (Patch v222) there are some issues (Nothing compared to MIUI's bugs )
Audio issues (Most of them can be fixed by disabling audio effetcs in phh's Settings)
BT audio doesn't work
Fingerprint doesn't work
90 Hz Display doesn't work (Limited to 60 Hz)
Tell me if you found any other working GSI (Please provide forum link)
Which vendor and firmware did you used? Latest one 20.9.4 or specific one?
https://xiaomifirmwareupdater.com/vendor/umi/
https://xiaomifirmwareupdater.com/firmware/umi/
sceryavuz said:
Which vendor and firmware did you used? Latest one 20.9.4 or specific one?
https://xiaomifirmwareupdater.com/vendor/umi/
https://xiaomifirmwareupdater.com/firmware/umi/
Click to expand...
Click to collapse
My Mi 10 was on latest xiaomi.eu stable.
you can write what system images you managed to run on mi10
Kabanoska said:
you can write what system images you managed to run on mi10
Click to expand...
Click to collapse
Sorry I dont understand
Edit: Now I got it...
Is it same guide for Mi 10 Pro?
henkka22 said:
Is it same guide for Mi 10 Pro?
Click to expand...
Click to collapse
I think it'll be the same. As long as you can go to fastbootd with this guide it should be fine.
Basecatcherz said:
I think it'll be the same. As long as you can go to fastbootd with this guide it should be fine.
Click to expand...
Click to collapse
I can confirm that this tutorial works for cmi too. Phhs treble is running but same bugs. Andy yans lineage didn't work If you want this tutorial could be copied to mi 10 pro forums too since there is no roms for it
henkka22 said:
I can confirm that this tutorial works for cmi too. Phhs treble is running but same bugs. Andy yans lineage didn't work If you want this tutorial could be copied to mi 10 pro forums too since there is no roms for it
Click to expand...
Click to collapse
There is something weird here...
I tried some other GSI and ended up soft bricked. Flashed latest stock (boots up) and then flashed CAOS GSI again.
It goes to boot splash and restarts all the time.
Are you on xiaomi.eu?
Basecatcherz said:
There is something weird here...
I tried some other GSI and ended up soft bricked. Flashed latest stock (boots up) and then flashed CAOS GSI again.
It goes to boot splash and restarts all the time.
Are you on xiaomi.eu?
Click to expand...
Click to collapse
I flashed latest stable xiaomi.eu (was on weekly) and then flashed phhs treble. Can't flash over weekly android 11. Didn't try caos
henkka22 said:
I flashed latest stable xiaomi.eu (was on weekly) and then flashed phhs treble. Can't flash over weekly android 11. Didn't try caos
Click to expand...
Click to collapse
Alright. I flashed latest stable xiaomi.eu ROM and now CAOS boots up. Looks like they made some relevant changes.
And btw you don't need stock recovery. I have twrp which have userspace fastboot aka fastbootd so I can leave it installed
henkka22 said:
And btw you don't need stock recovery. I have twrp which have userspace fastboot aka fastbootd so I can leave it installed
Click to expand...
Click to collapse
I tried that, too (LR Team). But Windows was unable to find the right driver and I was unable to use it. Even on Ubuntu it wasn't working.
Basecatcherz said:
I tried that, too (LR Team). But Windows was unable to find the right driver and I was unable to use it. Even on Ubuntu it wasn't working.
Click to expand...
Click to collapse
I just used newest platform tools directly from google site on ubuntu
henkka22 said:
I just used newest platform tools directly from google site on ubuntu
Click to expand...
Click to collapse
On ubuntu I used them, too. In the windows package there are no drivers included.
I tried many drivers flying around in the www...
Does caos gsi pass safetynet for you?
henkka22 said:
Does caos gsi pass safetynet for you?
Click to expand...
Click to collapse
The non-rooted variant with magisk, yes.
Phh's got the problem thats it's pre-rooted.
Basecatcherz said:
On ubuntu I used them, too. In the windows package there are no drivers included.
I tried many drivers flying around in the www...
Click to expand...
Click to collapse
I used Windows originally, you'll have to manually install the Xiaomi drivers from Xiaomi cn website through computer mangement, on this link: https://www.xiaomi.cn/post/18464849. Since these are not signed, you will have to disable signature enforcement on Windows 10! Here is an article on doing that, method 1 works: https://windowsloop.com/disable-driver-signature-enforcement-on-windows/.
Or you can try Mi Flash Tool and look for the install driver option, I haven't tried that method. Let us know how it goes .
xda-jimjongs said:
I used Windows originally, you'll have to manually install the Xiaomi drivers from Xiaomi cn website through computer mangement, on this link: https://www.xiaomi.cn/post/18464849. Since these are not signed, you will have to disable signature enforcement on Windows 10! Here is an article on doing that, method 1 works: https://windowsloop.com/disable-driver-signature-enforcement-on-windows/.
Or you can try Mi Flash Tool and look for the install driver option, I haven't tried that method. Let us know how it goes .
Click to expand...
Click to collapse
I will try that. Maybe tomorrow
Unsigned drivers are not the way I like...
I have MIUI 11 Xiaomi.eu Android 10 stable, can I flash this ROM and Gapps, and maybe some progress to remove in existing issues?
Related
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
C666PO said:
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
Click to expand...
Click to collapse
I have an almost identical problem to you.
except: my device is GM1910, I had a stock hydrogen OS, which has been converted to oxygen OS.
so far, I have tried twrp-3.3.1-0, 3.3.1-2, 3.3.1-3, 3.3.1-4, on oxygen OS version 10.0.2.GM21AA, 10.0.3.GM21AA, and 10.3.0.GM21AA, all would stuck at the fastboot mode logo screen
Rolling back to a lower version of oxygen OS, including version 9.5.1 and 9.5.7 causes my OP7P in bootloader mode no longer recognized by "fastboot devices", or even by "dmseg" as a usb device.
I received a suggestion of trying the latest TWRP 3.3.1-74 build, which I intend to try later tonight, but got not so optimistic about, seeing that you've experimented with TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
OblixioN said:
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
Click to expand...
Click to collapse
Hi OblixioN,
I tried the image with the Q at the end: TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio and it worked. I had no idea what the Q or Pie meant so your information just solved my problem. I assume it will work for you.
Huge thanks!
Thanks - worked for me as well!
Unfortunately I formated before getting to this solution, so rather unnecessary for me, but what I did was getting the unofficial twrp for guacamole here:
h-t-t-p-s://androidfilehost.com/?fid=4349826312261707787
(from this post: https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322)
Then I booted to fastboot at ran
Code:
fastboot set_active a
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
fastboot set_active b
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
Now I could boot into twrp, it found all the internal data storage, and I could sideload
Code:
adb sideload .\twrp-installer-3.3.1-4-guacamole.zip
adb sideload .\Magisk-v20.3.zip
C666PO said:
I had no idea what the Q or Pie meant so your information just solved my problem.
Click to expand...
Click to collapse
It means if you are on Android Q, you need to use the TWRP version that supports Android Q.
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
hey there.
So, first of, You restart it by pressing and holding volume up, down and power at the same time for 10+ seconds.
And second, try updating Oxygen OS to its latest version. It works for me now, just unpacked a new OnePlus 7 Pro, didn't work on Android 9, works on Android 10 latest update.
OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
While in fastboot , " fastboot boot twrp.img
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
SABMAN said:
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
Click to expand...
Click to collapse
I tried installing a new kernal and after that mine would go directly to bootloader, no matter what I did it went directly to bootload, thankfully fastboot was still active but using boot cmd into anything would fail,, ,I started my msm tool, and rebooted into edl and as soon as a com port became active on the MSM panel I hit start, and it took off running and did it's thing,
I think my issue had two reasons!
1. The boot.img file i used was from the earlier Oxygen update not the version i had just installed.
2. The phone encryption (but i doubt this!)
Anyway since nothing helped i erased the phone and restored it Now it's working again!
Follow These methods (100% worked)
1. Boot to fastboot mode (power +vol down)
2. Extract ADB.rar to Drive C (Put the recovery and vbmeta files in ADB Folder) vbmeta link Below
3. Connect Phone To PC with USB Cable
4. from Start run CMD and type cd:\adb (pres enter) And type the following Commands :
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery Twrp-3.4.2B_toco_by.alex.msk1407.img (you can rename it to twrp.img) -LINK BELOW (Many Thanks To Alex msk)
fastboot reboot recovery
5. in twrp: wipe-> format data -> Type yes and tap enter (blue key)
6. Copy xiaomi.eu rom and magisk.zip to phone
8. in twrp: install rom and magisk.zip
9. in twrp: Boot to recovery (the phone is restarting to twrp again)
10. in twrp: reboot system
12. Enjoy
ADB Link :
https://mega.nz/file/x8whTZSa#UP7UvnDO7rsuefBWb1meUd4iZZXMJBHIDUa1lMnQXNI
TWRP Link :
https://mega.nz/file/0lAywALA#hx6U3_xgW3fpndSR0OWsRBxEncQ9CGQb2ezMOAldTRQ
3.4.0-14 TWRP Link:
https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4107209
vbmeta Link:
https://mega.nz/file/t4QmXACT#hqN6TNDt2mlAPrQUnClGtmaCvWJR3eO3TRAa8I4JhGk
Magisk Link :
https://mega.nz/file/Y4BEBILD#kre2gRvSJgwJRto1Yg-o7gblTRXAftUGxJSoKNowWkI
xiaomi.eu 12.0.3 Rom Link (Updated):
https://sourceforge.net/projects/xi...e10LITE_V12.0.3.0.QFNMIXM_v12-10.zip/download
thank
thanks and good to see, that the mi note 10 lite has it own section now. hope there will come a lot of custom things.
Does Gpay work with bootloader unlocked and xiaomi.eu rom?
is the widevine L1 working?
is the hdr working
For installing updates, do we need to follow the dirty flash process via TWRP? I tried via the updater but the process simply restarts mobile and nothing happens.
New version of Xiaomi.eu ROM is out.
Question is how to updtae without losing data?
What's the problem? The test TWRP from mauronofrio can't decrypt data? Sry for the questions, I have not tested it yet
eugenwollekneul said:
What's the problem? The test TWRP from mauronofrio can't decrypt data? Sry for the questions, I have not tested it yet
Click to expand...
Click to collapse
Yes, cant decrypt -> probably can't update.
Even if you do use OTG to read the .zip...
Will it overwrite to encrypted partitions? Won't that break the system?
Or
Will it boot fine - but will the updated ROM be able to read the probably still encrypted user data?
maxlieb said:
Yes, cant decrypt -> probably can't update.
Even if you do use OTG to read the .zip...
Will it overwrite to encrypted partitions? Won't that break the system?
Or
Will it boot fine - but will the updated ROM be able to read the probably still encrypted user data?
Click to expand...
Click to collapse
I have a Redmi note 8 with xiaomi.eu but I think I can help you. In order to update you flash the new zip. It just overwrites the system partition not the data. And you are still able to decrypt them. There is no problem I tried it. You will have to reflash magisk although.But in case anything goes wrong just format data and you will be fine.
PinkNinja said:
I have a Redmi note 8 with xiaomi.eu but I think I can help you. In order to update you flash the new zip. It just overwrites the system partition not the data. And you are still able to decrypt them. There is no problem I tried it. You will have to reflash magisk although.But in case anything goes wrong just format data and you will be fine.
Click to expand...
Click to collapse
There`s a new twrp that decrypts everything so no more problem anyway
is this twrp fully working? or does it have the same problems as mauronofrio's Twrp 3.3.1.0?
Ahmed Hesham said:
is this twrp fully working? or does it have the same problems as mauronofrio's Twrp 3.3.1.0?
Click to expand...
Click to collapse
Yes it's fully working.
Στάλθηκε από το Mi Note 10 Lite μου χρησιμοποιώντας Tapatalk
Super weird... it didnt work for me... flashing was successful
but it keeps rebooting to fastboot mode.
While doing format data, i did receive an error message "unable to find /metadata" is that normal?
EDIT: So what happen is, I did all over again with slightly different steps
1) i reflashed official firmware to revive my phone
2) Once I'm able to boot on official ROM, I flash TWRP
3) Format Data + restart TWRP
4) Copied ROM and flash Xiaomi EU rom
5) Restart to system immediately after flashing ROM. Managed to boot Xiaomi EU rom.
6) Reboot to recovery and flash magisk
7) Restart to system, set up, and done.
Kediraksith said:
1) i reflashed official firmware to revive my phone
Click to expand...
Click to collapse
How you reflas official firmware?
andriej1974 said:
How you reflas official firmware?
Click to expand...
Click to collapse
I think he did it with the miflash tool. I had to do it so because I stucked in Fastboot mode.
I also had a problem with metadata. I have recovery aleks.msk, can enter fastboot but nothing else. Miflash does not work, uploading the firmware via recovery does not get up.
In fastboot mode copy latest xiaomi.eu zip (not the fastboot, the regular one)to the phone and flash it in twrp - reboot to system
Can anyone please post a link to Xiomi EU ROM. Can't find it. Thanks
RAMBO29 said:
Can anyone please post a link to Xiomi EU ROM. Can't find it. Thanks
Click to expand...
Click to collapse
In the First Post
Hi Everyone
I was rooting My op7 pro after updating to open beta android 11. While i was booting twrp it shows Fastboot Mode screen And stuck on that
Hope i ll find possible solution from the community
Regards
ali_hamza
I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.
benjaminries said:
I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.
Click to expand...
Click to collapse
You should just be able to run direct install after you boot to A11 with the patched boot image.
Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.
calripkenturner said:
You should just be able to run direct install after you boot to A11 with the patched boot image.
Click to expand...
Click to collapse
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?
benjaminries said:
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?
Click to expand...
Click to collapse
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.
calripkenturner said:
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.
Click to expand...
Click to collapse
Got it. Yeah my Magisk Manager was still installed from previous beta, but it took away the "direct install" option when I lost root from flashing the unpatched boot.img. Personally I would always rather patch my own boot.img file than rely on something from a filesharing service, especially when trying to get out of brick...
But I can see how until proper TWRP support comes, we can just use Magisk to patch alternate boot slot before rebooting but immediately after flashing the latest OOS beta using the regular system update process. Hindsight...
benjaminries said:
Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.
Click to expand...
Click to collapse
need to use orangfox recovery
esi2121 said:
need to use orangfox recovery
Click to expand...
Click to collapse
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?
benjaminries said:
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?
Click to expand...
Click to collapse
Check the orangefox ,it's only recovery support a11 for now
esi2121 said:
Check the orangefox ,it's only recovery support a11 for now
Click to expand...
Click to collapse
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.
Yesterday i download and tried to flash Pitch Black Recovery Project but results were same.
I think there should be some changes regarding A11 in any recovery so the best is that we should wait for their( Devs) further response
benjaminries said:
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.
Click to expand...
Click to collapse
yup thats it , but in orangefox git said official support A11
esi2121 said:
yup thats it , but in orangefox git said official support A11
Click to expand...
Click to collapse
Check out this (now locked) thread though: it seems like there's no working port of OrangeFox for guacamole that supports OOS11 yet... lots of people bricking and boot-looping on the hope that there might have been!
[UNOFFICIAL] [RECOVERY] [OnePlus 7 Pro] OrangeFox Recovery Project [R10.1] | XDA Developers Forums (xda-developers.com)
HI Everybody,
I have a Oneplus 8T, European, I installed lineage recovery and Lineage OS 18.1, rooted, but now I would like to reinstall Oxygen 11. Please, can you tell me how to do or where to find the answer?
Please, don't tell me to use TWRP because at moment it's not available for this smartphone.
Thank you All in advance!
You'll need to download the msm recovery tool for your device. Will take it back to new
11mackey11 said:
You'll need to download the msm recovery tool for your device. Will take it back to new
Click to expand...
Click to collapse
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I guess you could try to fastboot flash a full rom zip I think that should work. If not you can just use the MSM tool to restore.
The steps to fastboot flash a full OOS rom zip should be the same as listed in this conversion thread https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I believe it can fastboot flashed. I just haven't tried it yet. I did see another post where the steps were laid out but remember where I saw it
I am also very interested in the answer to this question. And I think I know why the answer is "use the MSM tool".
Here's how I arrived at that:
If you use payload_dumper to have a look at what gets flashed when installing a rom, there's a number of image files that aren't listed in /dev/block/by-name such as odm, product, vendor and even system(!). This means that you cannot flash them using fastboot and the only way to flash them is via fastbootd (which is in recovery.img).
So the theoretical process is:
- boot into fastboot
- flash boot, recovery, and the other "normal" partitions
- start fastbootd using "fastboot reboot fastboot"
- flash the remaining partitions
- reboot
The problem with OOS is that fastbootd looks very much like recovery: it has no ADB/fastboot connectivity. So you cannot flash the remaining partitions.
Conclusion: the MSM Tool is the only way to return.
Acknowledgment: thanks to @chandu dyavanapelli for the Evolution-X rom installer script which helped me understand what's going on. See https://forum.xda-developers.com/t/...0_r34-evolution-x-passion-22-04-2021.4266067/
Im trying to install generic TWRP
I successfully unclocked bootleader after waiting for a week
but i ran into partitition unknown error while flashing TWRP
now its on bootloop
Any help?
what command are u using to flash the image file?
Code:
fastboot flash recovery twrp.img
give an error - FAILED (remote: '(recovery_a) No such partition')
then i tried
Code:
fastboot getvar curent-slot
give me a
then i did
Code:
fastboot flash boot_a twrp.img
see the problem is there is no supported or officol twrp fpr poco x5 pro
So i tried poco x3 twrp
try this fastboot flash boot_ab twrp.img
this device already received unofficial orange fox recovery
Recovery For Redwood
ORANGEFOX Recovery For Poco X5 Pro
www.pling.com
It may be completely off target, but how about using the slot b side?
info
-
-
Muganz said:
info
Click to expand...
Click to collapse
hey, can you link me that telegram group?
scorthyn said:
hey, can you link me that telegram group?
Click to expand...
Click to collapse
there u go..
Poco X5 Pro | Redmi Note 12 Pro Speed | Official
Poco X5 Pro OFFICIAL Community • Read rules (/rules), English only • Channel: @PocoX5ProUpdate • Photography group: @PocoX5ProPhotography • Off-Topic group: @PocoOffTopic • Customization group: @PocophoneCustomization
t.me
I already rooted it without TWRP
I never really needed TWRP
I just needd the root.
I dont want to test broken Untested roms on it yet.
I just wanted to uninstall system apps
And unlock few settings thats it
Bilalll said:
I already rooted it without TWRP
I never really needed TWRP
I just needd the root.
I dont want to test broken Untested roms on it yet.
I just wanted to uninstall system apps
And unlock few settings thats it
Click to expand...
Click to collapse
How did you root it without twrp? Just using fastboot/adb with an unlocked bootloader I assume? Thank you.
Zylam Marex said:
How did you root it without twrp? Just using fastboot/adb with an unlocked bootloader I assume? Thank you.
Click to expand...
Click to collapse
First download device original rom from the redmi website
Unlock bootloader after registering ur phone
Unlock device from developers options
Wait for 7 days
Do what is required
Download magisk
Open original rom and copy boot. Img
Open magisk and patch the copied boot. Img
reply to this post after you reach here
Bilalll said:
First download device original rom from the redmi website
Unlock bootloader after registering ur phone
Unlock device from developers options
Wait for 7 days
Do what is required
Download magisk
Open original rom and copy boot. Img
Open magisk and patch the copied boot. Img
reply to this post after you reach here
Click to expand...
Click to collapse
Oh nice, thank you for the rapid response. Unfortunately I do not yet have a X5 Pro, I'm actually waiting for custom roms to appear, ever since Xiaomi baked gestures into the stock launcher I stopped buying phones until I could custom rom. Nova Launcher is a must for me and using it without gestures feels wrong. I was just curious as to how you rooted without a custom recovery. Very interesting you are using magisk on a different device to patch the boot image in the fastboot rom, which I assume you will flash using the mi flash. Is that what's happening? Thank you.
Zylam Marex said:
Oh nice, thank you for the rapid response. Unfortunately I do not yet have a X5 Pro, I'm actually waiting for custom roms to appear, ever since Xiaomi baked gestures into the stock launcher I stopped buying phones until I could custom rom. Nova Launcher is a must for me and using it without gestures feels wrong. I was just curious as to how you rooted without a custom recovery. Very interesting you are using magisk on a different device to patch the boot image in the fastboot rom, which I assume you will flash using the mi flash. Is that what's happening? Thank you.
Click to expand...
Click to collapse
No need to flash with mi flash after u patch it with magisk.
After magisk step
U will boot into fastboot and install the patched boot. Img
U may have 2
One is for fastboot rom
2nd is for recovery rom
Depends on the rom u falshed during flashing using mi flash tool
For fastboot u will use receovey comand
For bootloader rom u will use boot command while flashing boot. Img
Hope it will help u and others
Also yeah these are the silly things I wanted to root this phone. Navigation or lockscreen wallpaper suggestions or annoying box icons etc etc
Bilalll said:
First download device original rom from the redmi website
Unlock bootloader after registering ur phone
Unlock device from developers options
Wait for 7 days
Do what is required
Download magisk
Open original rom and copy boot. Img
Open magisk and patch the copied boot. Img
reply to this post after you reach here
Click to expand...
Click to collapse
im trying to install magisk. can u help me with steps 7 and 8. i dont really know what to do there. I found Global 14.0.6.0 but there are multiple links eg. fastboot/recovery which ROM to download?
is magic hide works? i want it to pass safetynet checks.
thx
Szajkop said:
im trying to install magisk. can u help me with steps 7 and 8. i dont really know what to do there. I found Global 14.0.6.0 but there are multiple links eg. fastboot/recovery which ROM to download?
is magic hide works? i want it to pass safetynet checks.
thx
Click to expand...
Click to collapse
Install magisk apk first
Go check ur Ramdisk Status
If its Yes
Download Fastboot rom
If no
Download recovery
After downloading the above
U will find boot. Img inside
Next is just going into fastboot mood
Run fastboot receovery command if ita receovery
Or
Run fastboot boot command if its fastboot
Check the exact commands on the good
Sorry for typos or bad explaination
Bilalll said:
No need to flash with mi flash after u patch it with magisk.
After magisk step
U will boot into fastboot and install the patched boot. Img
U may have 2
One is for fastboot rom
2nd is for recovery rom
Depends on the rom u falshed during flashing using mi flash tool
For fastboot u will use receovey comand
For bootloader rom u will use boot command while flashing boot. Img
Hope it will help u and others
Also yeah these are the silly things I wanted to root this phone. Navigation or lockscreen wallpaper suggestions or annoying box icons etc etc
Click to expand...
Click to collapse
If I'm not wrong, you can do these with the debloater via usb debugging
Bilalll said:
Code:
fastboot flash recovery twrp.img
give an error - FAILED (remote: '(recovery_a) No such partition')
then i tried
Code:
fastboot getvar curent-slot
give me a
then i did
Code:
fastboot flash boot_a twrp.img
see the problem is there is no supported or officol twrp fpr poco x5 pro
So i tried poco x3 twrp
Click to expand...
Click to collapse
sir how to fix, same for me
Muganz said:
what command are u using to flash the image file?
Click to expand...
Click to collapse
sir can you help me? same for me
after done the unlock bootloader, i flash rom but the problem is i bypass the platfirm tools, i did is..
got to cmd
c: \users\karen\Downloads\fastboot flash boot c:\users\karen\Downloads\orangefox.img
after this in the youtube "how to install orange fox" i turn off and volume up
then my phone is bootloop
then i flash again twrp recovery but it says error, now my phone is always in fastboot
do you know how to fix sir
thank you 🥹🥹