[solved] Can't Reboot To Recovery From Os


dogiex

dogiex

Finnish language.Translator
Aug 24, 2015
1,264
142
Device: Kate
Weekly 7.9.7
TWRP ZCX 3.0.2 and official 3.1.1-0 tested

When I choose 'Reboot to recovery' from updater, it only reboots the phone amd don't reboot to recovery.

Is there some kind of steps to be done to make it work or is it a rom issue?

Would love to get it to work to be able to automate OTA updates.

Have Kate users the same issue or does it work for someone and what rom do you have?

[Solved Method #1 Flashing official rom again]
Confirmed on device KATE
https://xiaomi.eu/community/index.php?posts/386437

[Solved Method #2 Flashing emmc_appsboot.mbn]
Confirmed on KENZO, KATE, IDO, LAND, LIBRA & AQUA

If you get bootloop after method #2, just simply reunlock your bootloader using MiUnlockTool and restart system.
https://xiaomi.eu/community/index.php?posts/387445
 
Last edited:
  • Like
Reactions: wamy007, MeiGuddet, graw2 and 1 other person
Hi dogiex, I have the same problem and I use Kenzo.
It's not a big trouble because we can access by the manual mode. But ofc would be better the automatic mode...
 
This problem seems to affect Redmi Note 3 Pro and SE, and Redmi 3.

These phones are considered 'old' from Xiaomi point of view and judging from that thread it's very clear that they don't care to fix it.

I think they want all Kenzo users to DOWNGRADE to Redmi Note 4x haha (why in the world people who own a Snapadragon 650 want to downgrade to Snapdragon 625? Kenzo's SOT is very good already, with xiaomi.eu my Kenzo's SOT is 9hr for normal daily usage, no game).

Lucky for Kenzo users, xiaomi.eu still supports it.
 
Last edited:
Soebianto said:
This problem seems to affect Redmi Note 3 Pro and SE, and Redmi 3.

These phones are considered 'old' from Xiaomi point of view and judging from that thread it's very clear that they don't care to fix it.

I think they want all Kenzo users to DOWNGRADE to Redmi Note 4x haha (why in the world people who own a Snapadragon 650 want to downgrade to Snapdragon 625? Kenzo's SOT is very good already, with xiaomi.eu my Kenzo's SOT is 9hr for normal daily usage, no game).

Lucky for Kenzo users, xiaomi.eu still supports it.
Click to expand...
My brothers Kenzo boots ro recovery fine but he is using stable roms. Also Hennessy and Hermes (mom and dad phone) boots fine to recovery and they use stable.
 
Soebianto said:
This problem seems to affect Redmi Note 3 Pro and SE, and Redmi 3.

These phones are considered 'old' from Xiaomi point of view and judging from that thread it's very clear that they don't care to fix it.

I think they want all Kenzo users to DOWNGRADE to Redmi Note 4x haha (why in the world people who own a Snapadragon 650 want to downgrade to Snapdragon 625? Kenzo's SOT is very good already, with xiaomi.eu my Kenzo's SOT is 9hr for normal daily usage, no game).

Lucky for Kenzo users, xiaomi.eu still supports it.
Click to expand...
Have you tried it with latest china rom if it works there?
 
dogiex said:
My brothers Kenzo boots ro recovery fine but he is using stable roms. Also Hennessy and Hermes (mom and dad phone) boots fine to recovery and they use stable.
Click to expand...

This bug only affected Developer ROM 7.3.16 and after, I started using developer xiaom.eu ROM since Dec 2016 and before 7.3.16 reboot to recovery from Updater was fine.

Didn't try flashing China Dev ROM because i'm kinda lazy and i strongly believe if this problem was created by xiaomi.eu they would has fixed it long ago..

We also have several RN2, 1 using xiaomi.eu Dev ROM 7.6.x, 1 using xiaomi.eu stable and 1 using latest global stable, all boot to recovery just fine via Updater.
 
It's my first time on dev ROM, and I got this problem before in Stable. I think start after installing the 8.2.1.0 stable
 
Ok I tested this with Global dev 7.9.15 rom and reboot to recovery worked with ZCX recovery, I'm now installing EU rom 7.9.8 on my Kate device and hope that it's fixed or at least the 7.9.15 fixes it.
 
Problem solved! Rebooting to recovery mode now works on my Kate:
Steps to how I made it work:
  1. Flashed latest Global (because my device is Kate and only has Global rom) developer fastboot rom version 7.9.15 via MiFlashTool (XiaoMiFlash) with Clean all option tapped
  2. Rebooted to the OS, enabled USB-debugging and flashed ZCX TWRP next in fastboot
  3. Booted to TWRP and format data
  4. Rebooted TWRP and from mount options disabled "system read only"
  5. From settings enabled "enable MIUI ota updates"
  6. Flashed EU rom
  7. Rebooted to system and it can now reboot to recovery from OS
 
Last edited:
Ok, for your device kate (based on global) I understand that you need all that steps but I don't understand for m Kenzo...
 
Pitada said:
Ok, for your device kate (based on global) I understand that you need all that steps but I don't understand for m Kenzo...
Click to expand...
You could try with china rom the same steps for Kenzo.
 
dogiex said:
You could try with china rom the same steps for Kenzo.
Click to expand...
Its like I said before. Must be other thing, if your brother's phone boots to recovery. I was in last Xiaomi.eu stable ROM and could not boot. So same situation different behavior...
I will try to look if someone else have this issue and if exist a easier solution.
Thanks anyway
 
dogiex said:
Ok I tested this with Global dev 7.9.15 rom and reboot to recovery worked with ZCX recovery, I'm now installing EU rom 7.9.8 on my Kate device and hope that it's fixed or at least the 7.9.15 fixes it.
Click to expand...

So they fixed it in 7.9.15 ROM?

It didn't work in 7.9.7 right? you're using eu 7.9.15 ROM now, right? (I suspect if you flash to eu 7.9.7, the reboot to recovery won't work again).
 
Last edited:
Soebianto said:
So they fixed it in 7.9.15 ROM?

It didn't work in 7.9.7 right? you're using eu 7.9.15 ROM now, right? (I suspect if you flash to eu 7.9.7, the reboot to recovery won't work again).
Click to expand...
It worked in 7.9.7 yes. And I updated to 7.9.15 via OTA and worked fine.
I did the steps I mentioned before using the first MIUI build 7.9.7 for Kate. After flashing it did not work. After the steps it worked.
 
  • Like
Reactions: Soebianto
dogiex said:
It worked in 7.9.7 yes. And I updated to 7.9.15 via OTA and worked fine.
I did the steps I mentioned before using the first MIUI build 7.9.7 for Kate. After flashing it did not work. After the steps it worked.
Click to expand...

Thanks a lot for sharing this, hopefully next dev rom fix the problem for Kenzo, like to avoid step 1 & 3 if possible.
 
Finally, I fix the reboot to recovery bug (Updater app) on my Kenzo.

I simply flashed the 'emmc_appsboot.mbn' file I extracted from latest MIUI Developers China ROM 7.9.21 (since xiaomi.eu is based on China ROM).

Thanks to @dogiex for the idea (https://xiaomi.eu/community/threads/solved-cant-reboot-to-recovery-from-os.41559/#post-386437), and thanks to @ingbrzy for the confirmation flashing the file won't cause me some troubles.

Xiaomi.eu started removing this file since ROM 6.11.17 to protect people who unlocked their Bootloader UN-OFFICIALLY from getting bootloop if they upgrade the ROM.

For those who got problem with this reboot to recovery bug (can not boot to recovery from Updater app), here are the steps :

WARNING (really important) :
1. This is for OFFICIALLY UNLOCKED BOOTLOADER ONLY.
2. MAKE SURE your device is USING the SAME Mi Account you used to unlocked the bootloader.
3. Turn on USB Debugging & OEM Unlocking in the Developer Options.
4. Make sure your bootloader is still unlock (Fastboot mode, type 'fastboot oem device-info').
5. After flashing this file, some people had their bootloader re-locked and bootloop (it was smooth for me, not re-locked bootloader or bootloop), fortunately once you unlocked the bootloader officially, you can use Mi Unlock tool to unlock it again without asking for permission.
6. Backup important data on your phone to SD Card or PC ... better safe than sorry, right?).


Please be warned that if you stopped using that mi account with your device for quite sometime (you deleted the mi account from your device), there is a possibility that your unlock permission revoked by Xiaomi, if this happened then you need to ask for unlock permission again (this happened to a friend here who tried this, fortunatelly he got the permission and all is good now).

SOME NOTES :
1. file 'emmc_appsboot.mbn' inside these zip files was extracted from the official MIUI China Developer ROM.
2. Use the same or lower version of 'emmc_appsboot.mbn' file compare to your current ROM version.
3. if bootloop happens after flashing, don't panic, just boot to fastboot & unlock the bootloader using Mi Unlock tool.

(Flashing via Fastboot) :

1). Extract the 'emmc_appsboot.mbn' file from latest MIUI Developers ROM or simply download from links below:

Links (fix reboot to recovery bug in Xiaomi.eu ROM, OFFICIALLY UNLOCKED BOOTLOADER only):
for KENZO / Redmi Note 3 Pro :

for KATE / Redmi Note 3 Pro Special Edition :

for IDO / HM3 :

for LAND / HM3S :

for LIBRA / Mi 4c :
emmc_appsboot (MI4C_CHINA_Dev_ROM_7_9_14).zip (for LIBRA xiaomi.eu v7.9.14 and up)​

for AQUA / Mi 4s :

2). Boot your phone to Fastboot (power+vol down), connect to PC
3). Go to Commond Prompt in Windows (run as administrator)
4). Type : "fastboot flash aboot emmc_appsboot.mbn", press ENTER
5). Type : "fastboot flash abootbak emmc_appsboot.mbn", press ENTER
6). Reboot your phone and try reboot to recovery from Updater app.

Notes :
1. If fastboot won't run, maybe you need to install 'Minimal ADB & Fastboot 1.4.3'.
2. Screenshot (when i was flashing the file) : http://ibb.co/naQXW5

*********************************************************
You can also flash via TWRP these flashable zip files below :

(Flashing via TWRP) :

for KENZO / Redmi Note 3 Pro :

for KATE / Redmi Note 3 Pro Special Edition :
TWRP_emmc_appsboot_miui_HMNote3ProtwGlobal_7.9.15.zip (for KATE xiaomi.eu v7.9.15 and up)​

for IDO / HM3 :

for LAND / HM3S :
TWRP_emmc_appsboot_miui_HM3S_7.9.21.zip (for LAND / HM3S xiaomi.eu v7.9.21 and up)
​
for LIBRA / Mi 4c :
TWRP_emmc_appsboot_miui_MI4c_7.9.14.zip (for LIBRA xiaomi.eu v7.9.14 and up)​

for AQUA / Mi 4s :
TWRP_emmc_appsboot_miui_Mi4s_7.9.7.zip (for AQUA xiaomi.eu v7.9.7 and up)​
 
Last edited:
  • Like
Reactions: ingbrzy, Adeolu, MeiGuddet and 4 others
Soebianto said:
Finally, I fix the reboot to recovery bug (Updater app) on my Kenzo.

I simply flashed the 'emmc_appsboot.mbn' file I extracted from latest MIUI Developers China ROM 7.9.21 (since xiaomi.eu is based on China ROM).

Thanks to @dogiex for the idea (https://xiaomi.eu/community/threads/solved-cant-reboot-to-recovery-from-os.41559/#post-386437), and thanks to @ingbrzy for the confirmation flashing the file won't cause me some troubles.

Xiaomi.eu started removing this file since ROM 6.11.17 to protect people who unlocked their Bootloader UN-OFFICIALLY from getting bootloop if they upgrade the ROM.

For those who got problem with this reboot to recovery bug (can not boot to recovery from Updater app), here are the steps :
(WARNING : this is for OFFICIALLY UNLOCKED BOOTLOADER ONLY)
0. Backup important data on your phone to SD Card or PC ... better safe than sorry, right?
1. Extract the 'emmc_appsboot.mbn' file from latest MIUI Developers ROM
2. Boot your phone to Fastboot (power+vol down), connect to PC
3. Go to Commond Prompt in Windows (run as administrator)
4. Type : 'fastboot flash aboot emmc_appsboot.mbn', ENTER
5. Type : 'fastboot flash abootbak emmc_appsboot.mbn', ENTER
6. Reboot your phone and try reboot to recovery from Updater app.

Notes :
1. If fastboot won't run, maybe you need to install 'Minimal ADB & Fastboot 1.4.3'
2. link to the 'emmc_appsboot.mbn' file from latest MIUI Developers China ROM 7.9.21 for KENZO :
https://www.androidfilehost.com/?fid=673368273298988061
3. I believe this same steps will also works for Kate & Redmi 3.

Screenshot : http://ibb.co/naQXW5
Click to expand...

Hi Soebianto,

With wich rom you did this steps?
Will I need to do this all the time I update a new xiaomi.eu dev rom?
Thanks in advance
 
Pitada said:
Hi Soebianto,

With wich rom you did this steps?
Will I need to do this all the time I update a new xiaomi.eu dev rom?
Thanks in advance
Click to expand...

I'm using xiaomi.eu 7.9.21, and flashed the 'emmc_appsboot.mbn' file I extracted from MIUI Developers China ROM 7.9.21 for KENZO ( I shared the link above), because xiaomi.eu is based on china ROM.

No, I don't think we need to flash this file every time we update Dev ROM, we only need to if Xiaomi update / change this file.

If you read my reply above, Xiaomi.eu started removing this file since ROM 6.11.17 (before that version, they included this file), and we started having this bug with dev ROM 7.3.16, so it's about 4 months Xiaomi didn't touch this file.

But now that we know how to fix this easily..
and if Xiaomi change that file, i will try to update these links here if 'dogiex' is ok with it.
 
Last edited:
  • Like
Reactions: Adeolu, Pitada and dogiex
Soebianto said:
I'm using xiaomi.eu 7.9.21, and flashed the 'emmc_appsboot.mbn' file I extracted from MIUI Developers China ROM 7.9.21 for KENZO ( I shared the link above), because xiaomi.eu is based on china ROM.

No, I don't think we need to flash this file every time we update Dev ROM, we only need to if Xiaomi update / change this file.

If you read my reply above, Xiaomi.eu started removing this file since ROM 6.11.17 (before that version, they included this file), and we started having this bug with dev ROM 7.3.16, so it's about 4 months Xiaomi didn't touch this file.

But now that we know how to fix this easily..
and if Xiaomi change that file, i will try to update these links here if 'dogiex' is ok with it.
Click to expand...
Go for it, I edited the OP to link to your guide also.
 
  • Like
Reactions: Adeolu and Pitada
@Soebianto: In your last post in the 7.9.14/15 thread you wrote: "...the reason why i asked this is i found a thread sharing the 'emmc_appsboot.mbn' file that fix the same problem in Redmi 3...". Where did you found this thread? Is there the same solution as yours here? Then I will try this on my HM3/ido.
 
MeiGuddet said:
@Soebianto: In your last post in the 7.9.14/15 thread you wrote: "...the reason why i asked this is i found a thread sharing the 'emmc_appsboot.mbn' file that fix the same problem in Redmi 3...". Where did you found this thread? Is there the same solution as yours here? Then I will try this on my HM3/ido.
Click to expand...

The solution i used and shared above should also works perfectly for Kate and Redmi 3 IDO.

The thread i mentioned was using a patched version emmc_appsboot.mbn file, so if you officially unlocked the bootloader, better use the emmc_appsboot.mbn from MIUI ROM.

The steps are the same for Kenzo, Kate and Ido, just use the right emmc_appsboot.mbn file for your device : emmc_appsboot (HM3_CHINA_Dev_ROM_7_9_21).zip (link in my post above) or you can download miui recovery china dev rom yourself and extract that file (the file i shared here was extracted from latest miui recovery china dev rom).

The thread i found is in xda forum, the solution is the same, flash that emmc_appsboot file (some people use miflash, but i like to use fastboot, it's simple for me), and i'm using original emmc_appsboot.mbn from miui rom,because my bootloader is OFFICIALLY unlocked.

You can also see the screenshot i took when i was flashing that file... after flashing, the reboot to recovery bug was fixed.
 
Last edited:
  • Like
Reactions: MeiGuddet and Adeolu
I cant flash..sorry im a noob on this things .
There´s no way to made a flash file of this?

Can some one explain to me how to flash whit miflash please.
 
Last edited:
You must log in or register to reply here.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
284
Views
110K
HyperOS
AndyLis
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
281K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
42K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
39K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
44K
HyperOS
KGVER
KGVER
Top Bottom
Back