Related
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
Code:
fastboot oem unlock
Code:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
Code:
fastboot flash boot_b twrp-3.4.0-0-jasmine_sprout.img
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via
Code:
fastboot flash boot_b jasmine_global_images_V11.0.12.0.QDIMIXM_10.0/images/boot.img
(my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
floydsen said:
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via (my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
Click to expand...
Click to collapse
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
Code:
fastboot boot TWRP-3.4.0-0-jasmine_sprout-for_V11.0.12.0.img
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
floydsen said:
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
Click to expand...
Click to collapse
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
also the name of that looks like one hell of a job ..shorten it to
recovery.img or twrp.img
fastboot boot recovery.img
but first run
fastboot getvar all
& also run fastboot flashing unlock_critical
but most importantly get another recovery
& i don't want to insult your intelligence but after flashing stock did you check to make sure bootloader was still unlocked and that dev settings was activated and that adb was toggled to on and that you authorised adb again
basicall after stock boot device and do the above ..plug in usb ..toggle adb ..authorise ..run adb devices ..if you see your device ..adb reboot bootloader ..fastboot devices ..see your device ..fastboot getvar all ..see bootloader is unlocked ..fastboot flashing unlock_critical if not done yet ...make sure to do ALL the above again after data gets wiped.....put twrp in adb folder ( MUST BE UNOFFICIAL RUSSIAN OR MODUFIED BY NEBRASSY ..rename to revovery.img ...fastboot boot recovery.img .. use file manager to put magisk.zip on internal then flash ..then reboot to rooted phone with stock recovery ...
Sent from my wayne using XDA Labs
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
KevMetal said:
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
floydsen said:
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
Click to expand...
Click to collapse
jajaja well now you know ...be careful ...some "official" roms are also more buggy than unofficial ones for Jasmine/Wayne..
LOS is an example ..so be forewarned .. if you like android 1 i guess stock rooted is a smart option to keep updates and keep device certified for google stuffs . .
alternativeky go FULL custom rom because stock and custom recovery is just a pain and not worth the hassle on an A/B treble device flashable by fastboot ..just boot the recovery when if ever needed
fyi ..you can flash magisk and it will boot ...if you don't try changing the recovery ..so you can have stock rooted with magisk without rcustom recovery...* recommended by me if you only wamt stock with root
Sent from my wayne using XDA Labs
All good now, thanks for your help! I just flashed Magisk (and also TWRP) and everything works nicely! I will need to get some experience, but I'll keep in mind that I maybe want to get rid of the TWRP recovery. Finally security testing is fun again. Thx!
OnePlus 7T Pro HD01AA Global 11 Open Beta 1
Magisk Patched Boot Image v21.4 Patched Manager v8.0.7
https://www.androidfilehost.com/?fid=17248734326145719979
May need to install Magisk Manager manually
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719978
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719976
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719977
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322189
OnePlus 7T Pro HD01AA India 11 Open Beta 1
Magisk Patched Boot Image v21.4 Patched Manager v8.0.7
https://www.androidfilehost.com/?fid=17248734326145719991
May need to install Magisk Manager manually
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719989
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719993
Stock Recovery Image
https://androidfilehost.com/?fid=17248734326145719992
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322190
OnePlus 7T Pro HD01AA Global 10.0.13
Magisk Patched Boot Image
https://www.androidfilehost.com/?fid=10763459528675591747
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01AA 10.0.13
https://www.androidfilehost.com/?fid=10763459528675591755
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675591746
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591748
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591745
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320328
OnePlus 7T Pro HD01AA India 10.3.7
Magisk Patched Boot Image
https://www.androidfilehost.com/?fid=10763459528675592073
Full ZIP OxygenOS HD01AA 10.3.7
https://www.androidfilehost.com/?fid=10763459528675592086
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675592074
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675592075
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675592076
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320346
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboot
Wifi issue?
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
isellmidgets said:
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
Click to expand...
Click to collapse
Make sure you flash the right boot for your model number.
Settings>About phone>Build number should end HD01BA or HD01AA so make sure it's the right one.
If you want to test that your Wi-Fi works with one of the boot images.
Instead of 'fastboot flash boot patched_file_name.img' do 'fastboot boot patched_file_name.img'
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
isellmidgets said:
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
Click to expand...
Click to collapse
I unlocked my OP 7t pro's bootloader, and every time there is an update I download the stuff mirrored by digidude512 ... I grab the magisk patched boot and the updated system pack.
I go to updates, update manually with having the update pack in the root of the storage.
When the update is done, I do not restart using the update reboot button - I use the boot to bootloader option at the power button menu (which can be enabled at the dev settings).
Then going to fastboot directly I flash the patched boot image using fastboot on windows cmd: fastboot flash boot boot_blabla.img --slot all
Reboot, go to magisk manager, update magisk using recommended direct install. Update magisk manager. Done.
Never had any problem (no wifi f*ery, nothing) and there is no need for TWRP at all. Open bootloader, magisk root and modules, adaway, stock ROM. Decent and clean.
Thanks a lot @digidude512 once again for this. Pretty convenient for others this way.
[zozi] said:
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
Click to expand...
Click to collapse
If you're rooting for the first time, use fastboot boot patched_boot.img and perform a direct install from within Magisk Manager to avoid potential headaches.
If you are doing an OTA update and want to retain root, you should not be fastboot flashing anything (you're not following the right guide).
[zozi] said:
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
Click to expand...
Click to collapse
Sorry for the late reply, I couldn't sign in while XDA was changing format.
For HD01BA you want this thread.
[OOS] [11] Open_Beta_2_HD01BA [EU] [Stock/Patched boot.img] [Stock/ADB Recovery] [Full ZIP] [OOS 10.0.13]
@digidude512 Every Update needs a new Thread... interesting. Stop this sh!t.
forum.xda-developers.com
can someone please provide me with batched boot image for OnePlus 7T (India), i extracted the boot.img by using payload dumper then i batched it using magisk 8.0.5 but unfortunately when i flash it using fastboot it loops at the OnePlus animation logo
Thread updated with files for OxygenOS 11 Open Beta 1 including both Global and India Variants.
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed
Do you unlock bootloader?
zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...
leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).
Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.
Hi, i'm trying to root my CN version 13.0.5 without the twrp, I'm using the magisk to patch the boot file, but after patch and use the command "fastboot flash boot boot.img, the mi 11 ultra just stuck in the mi logo. I'm not been able to root my phone, right now, how to root the CN version 13.0.5?
i did the same root with the android 11 and worked, something change?
hi, did you install magisk canary and not magisk stable?
I have just Root Xiaomi.eu A12 Miui13 with the same method and it work.
Hi. FIrst - better to use Magisk 23.0 - as you will still have Magisk hide. But more important - just the "fastboot boot boot.img" command instead. Once you have booted without issues you can go into Magisk and patch the real boot image file from there and restart. This is how it always worked for me. Not really sure what is the big difference there but as I said - that worked for me.
When you are running the miui 13, copy the boot.img from fastboot folder to your phone(remember the location). Open magisk app, choose install and search for boot.img on your phone. After patching is done, copy the patched file into your fastboot folder on pc. Boot into fastboot, type fastboot flash boot (and drag the patched file from fastboot folder here) and hit enter. after flashing fastboot reboot
Thanks for the help, i'll try to patchin a few hours and back here to give the feedback!
marcel112 said:
When you are running the miui 13, copy the boot.img from fastboot folder to your phone(remember the location). Open magisk app, choose install and search for boot.img on your phone. After patching is done, copy the patched file into your fastboot folder on pc. Boot into fastboot, type fastboot boot (and drag the patched file from fastboot folder here) and hit enter. after flashing fastboot reboot
Click to expand...
Click to collapse
Does that Format my Data? And how do i remove the Patch(remove magisk)?
Afg Playa said:
Does that Format my Data? And how do i remove the Patch(remove magisk)?
Click to expand...
Click to collapse
It does not format. That's just for root. You can flash the rom in fastboot again or flash the boot.img again from the folder images
thiagoserrao said:
Thanks for the help, i'll try to patchin a few hours and back here to give the feedback!
Click to expand...
Click to collapse
Did IT Work?
Afg Playa said:
Did IT Work?
Click to expand...
Click to collapse
Using CN no, i tried with the rom downloaded but didn't worked. So i take a step and installed the EU version, not been able to connect to android auto and other stuffs was killing me!
After install the EU version, i just did the same steps to root the boot, and worked without problem
thiagoserrao said:
Using CN no, i tried with the rom downloaded but didn't worked. So i take a step and installed the EU version, not been able to connect to android auto and other stuffs was killing me!
After install the EU version, i just did the same steps to root the boot, and worked without problem
Click to expand...
Click to collapse
Great, It also worked for me Xiaomi.eu 13.0.9.0.
I have difficulties too rooting my Mi 11 Ultra with Android 12. I have installed the latest canary of Magisk and when I patch the boot.img and flash it the device stucks on Android logo. When I boot the device with fastboot boot magisk_patched***.img I'll get a black screen.
Can anybody post a patched boot.img from Xiaomi.eu 13.0.9.0 Rom? Perhaps it works when I flash this one on my device.
User1977 said:
I have difficulties too rooting my Mi 11 Ultra with Android 12. I have installed the latest canary of Magisk and when I patch the boot.img and flash it the device stucks on Android logo. When I boot the device with fastboot boot magisk_patched***.img I'll get a black screen.
Can anybody post a patched boot.img from Xiaomi.eu 13.0.9.0 Rom? Perhaps it works when I flash this one on my device.
Click to expand...
Click to collapse
i just lost my root without reason, i just restarted my phone, than no root anymore and not being able to installing again ;D. what a hell
Start from the beginning by flashing unpatched boot.img and use Magisk v23. V24 has nothing but problems. I was frustrated for a few hours with it and going back to v23 solved everything.
As the title says. I managed to unlock the bootloader but now I need to install TWRP to install magisk, right? How do I get around doing that? There are some shady downloads on the internet but on twrp.me there is nothing for the phone. What do I do? Thanks in advance!
the device does not have official TWRP, the others available on telegram group do work fine
Thank you, but what telegram group? Could you forward me a link to it or something?
GeoS__ said:
Thank you, but what telegram group? Could you forward me a link to it or something?
Click to expand...
Click to collapse
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
SubwayChamp said:
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Thanks a lot. Is there a spesn version? Can I flash this spes version on my spesn phone? Thank you in advance
GeoS__ said:
Thanks a lot. Is there a spesn version? Can I flash this spes version on my spesn phone? Thank you in advance
Click to expand...
Click to collapse
spes and spesn are the same device. the "n" in spesn stands for NFC support
MarvavCZE said:
spes and spesn are the same device. the "n" in spesn stands for NFC support
Click to expand...
Click to collapse
Oh really? Can i flash it then? I really do not care much for NFC.
GeoS__ said:
Oh really? Can i flash it then? I really do not care much for NFC.
Click to expand...
Click to collapse
Of course, you can, in recovery builds these differences don't matter.
just rooted with FASTBOOT and latest Magisk.App
How to Root Xiaomi MIUI 13 based on Android 12 via Magisk
In this guide, we will show you the detailed steps to root your Xiaomi device running MIUI 13 based on Android 12 via Magisk.
www.droidwin.com
Installation
The Magic Mask for Android
topjohnwu.github.io
Current installed MiUi version needs to match the complete Recovery Image you have to download
in my case:
https://bigota.d.miui.com/V13.0.11.0.RGKEUXM/spesn_eea_global_images_V13.0.11.0.RGKEUXM_20220606.0000.00_11.0_eea_5c36ea339b.tgz
or
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Extracting the Boot.Img - let magic app patch it on your fone copy back to Computer and install it like described on "droidwin":
fastboot flash boot magisk_patched-25100_0UGhl.img
have fun
linolino
GeoS__ said:
As the title says. I managed to unlock the bootloader but now I need to install TWRP to install magisk, right? How do I get around doing that? There are some shady downloads on the internet but on twrp.me there is nothing for the phone. What do I do? Thanks in advance!
Click to expand...
Click to collapse
I am in the same situation,
ie. I have a Note 11 Pro without NFC
[Phone code: SPES ]
• bootloader unlocked from Xiaomi (after 7+ days waiting)
• running MIUI Global 13.0.15 [ RGCMIXM ] , Android v 11 RKQ1.211001.001
I have following TWRP
- twrp-3.6.2-12.1-21.06.22
- twrp-3.6.2_12-0-spes-Jabiyeff
and I tried to flash TWRP in fastboot (below), but it always fails and does not work
Code:
fastboot flash recovery twrp.img
I'm used to flashing TWRP and ROMs, but it's been a while since I touched a Xiaomi device,
so I am wondering is there anything different that I need to do ?
also, any 'new methods' for flashing Magisk ?
( and passing SafetyNet )
I am typing this on my custom ROM. I did not flash through fastboot. I booted to the twrp img with it though (fastboot boot twrp.img if i remember correctly.) and, well, i flashed from the option inside twrp
GeoS__ said:
I am typing this on my custom ROM. I did not flash through fastboot. I booted to the twrp img with it though (fastboot boot twrp.img if i remember correctly.) and, well, i flashed from the option inside twrp
Click to expand...
Click to collapse
so, you flashed TWRP recovery, by booting the TWRP from your PC ?
OK... I can try that.
exactly. i connected with adb and checked with adb devices, then pushed the twrp image to the phone and booted off of it through fastboot. if it works booting off of the img it's pretty safe to flash
To flash a custom recovery on Spes, you need to first run the following command in fastboot on the pc:
fastboot boot XXX.img (this is the name of twrp/ofox/Shrp image)
then inside the recovery, you must go to advanced and select the option flash this twrp, with that the recovery is installed by default. But remember that every time you install a new rom, the recovery will change, so you should flash twrp every time you finish installing a new rom.
Microsheepcl said:
To flash a custom recovery on Spes, you need to first run the following command in fastboot on the pc:
fastboot boot XXX.img (this is the name of twrp/ofox/Shrp image)
then inside the recovery, you must go to advanced and select the option flash this twrp, with that the recovery is installed by default. But remember that every time you install a new rom, the recovery will change, so you should flash twrp every time you finish installing a new rom.
Click to expand...
Click to collapse
exactly! twrp even offers a checkbox to automatically reflash itself after the rom when flashing
interesting, it seems to work a little bit different than what I did before! thx for sharing your knowledge
metaxda said:
I am in the same situation,
ie. I have a Note 11 Pro without NFC
[Phone code: SPES ]
• bootloader unlocked from Xiaomi (after 7+ days waiting)
• running MIUI Global 13.0.15 [ RGCMIXM ] , Android v 11 RKQ1.211001.001
I have following TWRP
- twrp-3.6.2-12.1-21.06.22
- twrp-3.6.2_12-0-spes-Jabiyeff
and I tried to flash TWRP in fastboot (below), but it always fails and does not work
Code:
fastboot flash recovery twrp.img
I'm used to flashing TWRP and ROMs, but it's been a while since I touched a Xiaomi device,
so I am wondering is there anything different that I need to do ?
also, any 'new methods' for flashing Magisk ?
( and passing SafetyNet )
Click to expand...
Click to collapse
Have these twrp you used decrypted the device succesfully? The both twrp i used didnt work on decrypt, and both bootlooped my phone after trying to flash them to recovery(others/flash to device), The one that worked on me was a unnoficial Ofox
UltimaDea said:
Have these twrp you used decrypted the device succesfully? The both twrp i used didnt work on decrypt, and both bootlooped my phone after trying to flash them to recovery(others/flash to device)
Click to expand...
Click to collapse
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"
gentano said:
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"
Click to expand...
Click to collapse
3.6.1 only works for MIUI A11 ROMs
3.6.2 only works for AOSP and A12 MIUI (but no for MIUI ROM flashing)
3.7.0 fully works for any ROM except A11
gentano said:
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"
Click to expand...
Click to collapse
Both the TWRP 3.6.2-12.1 and TWRP 3.7.0_12-0-spes works on my phone (SPES Global)
I am on android 12 version of MIUI 13. In fact I used the TWRP 3.7 to flash MIUI13.EU 13.0.5 A12 ROM and it works.
The two versions above can decrypt my phone without any problem. MTP also works in recovery mode.
Your phone is using Android 11. Probably that's the reason the TWRP versions I've mentioned above does not work for you.
I tend to agree with NeoSDAP.