Question No recovery image in stock rom? - Xiaomi Mi 11

I just found that there is no recovery.img in stock rom and xiaomi.eu rom.
Is recovery image replaced with other image in xiaomi devices?
Thanks in advance.

Android 11 hidden reco partition

Just like LG G8, rec is integrated into boot, which means refreshing boot will lose TWRP. Unless the boot already contains

Related

help install back 9.1.10 stable from xiaomi eu beta latest wia twrp

hi friend i have xiaomi redmi 4x i have unlocked bootloader OK
I have install twrp 3110 OK
when i install this xiaomi.eu rom latest beta everything is OK
when i want install back latest stable global 9.110 by xiaomi i download normal recovery rom from xiaomi site and put it on phone storage then i normal go twrp wipe (factory reset) install 9110 install is ok
when i click reboot system i see on boot only mi logo and no this .... powered by android
also same when i choose in twrp wife all data system etc expect storage where is this downloaded rom.
could any explain me why it stuck at boot if installation via twrp is ok ?
but when i install back this xiaomi.eu rom boot works OK
tubabuyukustun said:
hi friend ....
could any explain me why it stuck at boot if installation via twrp is ok ?
Click to expand...
Click to collapse
Hello, this happens because official MIUI boot.img verifies if recovery.img is also official/original.
You have 2 options to resolve the boot problem:
1. If you want to keep TWRP then modify boot.img... http://en.miui.com/thread-249666-1-1.html (with R4X image of course)
and flash it from TWRP or fastboot: fastboot flash boot boot.img
2. If you want original recovery, get "recovery.img" from the exact TGZ image as your MIUI ZIP
and flash it: fastboot flash recovery recovery.img
:good:

Get opt encrypt and update rom [stock recovery and boot opt encrypt with magisk]

Here is my tutor after a hard work on my zenfone 4 max whole day.
first of all you must download the last asus update for zenfone 4 max, I used 233.
put it into sd card, boot into stock recovery and update. (if you have a new phone just do it, if you already unlocked bootloader and installed twrp, just boot bootloader and flash stock recovery above.)
https://drive.google.com/open?id=1YP7v9sBclQULxYPOndDPCMLikZsT8urN
after this step, just do unlock bootloader. (if not unlocked), and flash twrp.
*recommended reboot recovery twrp and make a backup now
reboot bootloader and flash the boot above, it has no decrypt and magisk 16
https://drive.google.com/open?id=1bHk0znQNsH-dWZ89P525gC-rrvN4e9bl
reboot recovery twrp. Do the following:
format data partition,
reboot recovery twrp
clear data, cache and dalvik cache.
Now boot system, all data encrypt is gone, and you can activate it if you want.
You cant boot system until this boot image is flashed, or encrypt will be activated.
How does one flash the kernel?
amspady20 said:
How does one flash the kernel?
Click to expand...
Click to collapse
kernel is the core, it is in boot image.
fastboot flash boot boot.img
(after extract boot image, cause it is zipped)
Stock Recovery
Do you have stock recovery img file for our Zenfone 4 Max (ZC554KL)? Kindly upload it again.
Hi, do you have latest stock recovery for this device? I want to update to oreo, but it requires latest firmware (at least ver .352) to execute it.
latest recovery version
Hi alegmx!
i'm really thankful that you provide this stock recovery image , it works!
but can you provide us with a newer version of the recovery image? it'll be big help if you can provide it with us!
your version is currently .215 , im upgrading my os to version 412 and it needs atleast the .352 version of the recovery.

Stock boot.img is not booting on boot_b

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!

boot.img causes bootloop

I've been trying flash pixel experience on Redmi Note 9 and it had always caused brick.
When I flash vbmeta and boot.img I can access the Recovery but system goes in bootloop. Then I flash stock boot.img for miui 12.5.2 it successfully boot system but Recovery replaced to Stock Recovery.
I flashed the system through recovery after I flashed boot.img and reboot into recovery. After that I Replaced the patched boot.img to stock one then successfully boot.
I am using PE now but can't go to the twrp.
What is wrong here I really need an answer.
Try to flash the full stock MIUI again.
VD171 said:
Try to flash the full stock MIUI again.
Click to expand...
Click to collapse
I tried 12.0.6. Same. Tried 12.0.8. Same. Tried 12.5.2. Same.
Can't flash through SPflash as last time it locked oem unlock and miunlock couldn't unlock.
Yes, you can if you are flashing the stock MIUI.

Redmi 9 MIUI 12.5 stuck at MIUI boot logo

Hi, i got a problem at boot after I've formatted data in my SHRP recovery. I have formatted Data/Cache/Dalvik then flashed zip with disable encryption and restarted system and it got stuck. I know i can fix this with flashing with SP flash tool back from 11.0.7.0 but it's long way from here. Recovery is working, maybe there is a way to flash certain files from Fastboot (sp flash tool) or flash from recovery. Thank you for help

Categories

Resources