mi 11 lite 4g courbet wont boot after flashing 13.0.9 recovery rom


A

alimataei

Members
Feb 16, 2019
86
20
alimataei said:
Have u find any solution? I checked and its the most downloaded rom version for mi 11 lite 4g
Click to expand...
Hello, sorry for my late response. No I haven't found any solution to this issue. I've tried several approaches:

1. From bootloader:
a) flashing a previous global/stock ROM,
b) flashing one of the unofficial TWRP recoveries or even the latest unofficial Orange Fox for our device.
c) booting into recovery.
d) flashing latest xiaomi.eu.
e) rebooted.

Result (boot into recovery, no matter what).

2. Same as 1. (but with latest global image).

Result. Couldn't even flash it. Flashing process returned abnormally with E3003... And TWRP returned error code 1.

So, my friend, we're "stuck on stock".

One thing that is bothering me the most is the silence that the 'community' here greets out particular issues.

Even more, I seem to be some sort of outcast since I've got almost no answer to issues I've posted before, in the forums. And I am not even sure why that may be. But for me this is more of a suit yourself community, than a real sharing one.

Maybe someone with higher responsibilities here may address these griefs of mine, and, more, address the more important underlying issue of why aren't we able to install this otherwise longed for ROM from such seemingly hostile and silent brotherhood...

Go figure...
 
The number of very knowledgeable members is limited. Most of us can point at common answers to common issues, but at this level of details, I know I can bring nothing to the table.
 
  • Like
Reactions: mccurly and LOLO9393
mccurly said:
Hello, sorry for my late response. No I haven't found any solution to this issue. I've tried several approaches:

1. From bootloader:
a) flashing a previous global/stock ROM,
b) flashing one of the unofficial TWRP recoveries or even the latest unofficial Orange Fox for our device.
c) booting into recovery.
d) flashing latest xiaomi.eu.
e) rebooted.

Result (boot into recovery, no matter what).

2. Same as 1. (but with latest global image).

Result. Couldn't even flash it. Flashing process returned abnormally with E3003... And TWRP returned error code 1.

So, my friend, we're "stuck on stock".

One thing that is bothering me the most is the silence that the 'community' here greets out particular issues.

Even more, I seem to be some sort of outcast since I've got almost no answer to issues I've posted before, in the forums. And I am not even sure why that may be. But for me this is more of a suit yourself community, than a real sharing one.

Maybe someone with higher responsibilities here may address these griefs of mine, and, more, address the more important underlying issue of why aren't we able to install this otherwise longed for ROM from such seemingly hostile and silent brotherhood...

Go figure...
Click to expand...
Is there a fastboot image of this version ?
 
JiaiJ said:
The number of very knowledgeable members is limited. Most of us can point at common answers to common issues, but at this level of details, I know I can bring nothing to the table.
Click to expand...
@JiaiJ . Hello! Thank you. Finally an answer from the other side! You may think that I am being ironic, but not quite. It's actually the opposite. I finally understand why I have been sort of greeted with such a disturbing silence. I do understand and I apologize for my inconvenient remarks, in the sense that they may be interpreted as ironic or arrogant. Maybe I am like that, at least unintentionally. And therefore my apologies to the community and to yourself, @JiaiJ . Thank you once more for having the time to intervene. I really appreciate it!!!

As for you @alimataei , that could actually be a solution for our particular problem. I know for a fact that there's no such a fastboot version for our ROM version. But, maybe, that would be the way for installing it. I mean, since this particular version (13.0.9) is the first that should be installed as a recovery update, maybe that should be the way to go. If you have the time, please consider flashing a previous fastboot ROM from here (xiaomi.eu, I mean) and then, after that, try to update to latest 13.0.9 from recovery. (I will try this approach as well during next weekend if I get that opportunity). I'll post the results back here when that happens.


Meanwhile, cheers. Thank you for your attention, and again, do forgive for my inconvenience.
 
  • Like
Reactions: JiaiJ
alimataei said:
hey guys ive installed 13.0.8 using fastboot methode and it works perfectly but when i tried to flash 13.0.9 using both twrp and orangefox i get bootloop to recovery, anyone else has this problem ?

if your phone boots normally what recovery version are you using ? care to share the link of the recovery ?
Click to expand...
If you have any Magisk Modules -> disable/delete them before flashing.
Another workaround, extract the boot.img and flash it with fastboot
If possible use the boot.img from the working ROM installation
# fastboot flash boot boot.img
 
katerpanne said:
If you have any Magisk Modules -> disable/delete them before flashing.
Another workaround, extract the boot.img and flash it with fastboot
If possible use the boot.img from the working ROM installation
# fastboot flash boot boot.img
Click to expand...
@alimataei , a first word, I overlooked the fact that you've already tried to flash latest xiaomi.eu recovery ROM on top of previous xiaomi.eu fastboot ROM. And (it did not work... Is that correct? I am assuming it is, so apologies are in order for having recommended something you might have already tried and with which you weren't successful).

@katerpanne , I suppose you are talking of the boot.img file/partition/image from xiaomi.eu own flash file (version 13.0.8), correct?

Please, @katerpanne , can you confirm that?

Thank you!
 
mccurly said:
@alimataei , a first word, I overlooked the fact that you've already tried to flash latest xiaomi.eu recovery ROM on top of previous xiaomi.eu fastboot ROM. And (it did not work... Is that correct? I am assuming it is, so apologies are in order for having recommended something you might have already tried and with which you weren't successful).

@katerpanne , I suppose you are talking of the boot.img file/partition/image from xiaomi.eu own flash file (version 13.0.8), correct?

Please, @katerpanne , can you confirm that?

Thank you!
Click to expand...
Yep i tried updating the 13.07 and 13.08 using recovery image of 13.09 but bootloop in recovery and after a full wipe too, however i havnt tried to flash the previous boot image to the new version which seems promising, but i cant risk it right now ;))
Can some one try it?
 
alimataei said:
Yep i tried updating the 13.07 and 13.08 using recovery image of 13.09 but bootloop in recovery and after a full wipe too, however i havnt tried to flash the previous boot image to the new version which seems promising, but i cant risk it right now ;))
Can some one try it?
Click to expand...
@alimataei , hello. I am currently trying to boot latest 13.0.9 ROM (which, by the way flashed successfully with twrp-3.6.2_12.1-courbet-Aryannn999.img TWRP recovery), with previous 13.0.8 boot.img . Although it flashed alright, (the exit message from that flashing was the expected, "done"), I was still stuck on twrp recovery bootloop. So I rebooted from there into bootloader/fastboot, checked that the phone was recognised with "fastboot devices" command and having a serial code (of my phone) returned, I then used the command: "fastboot boot boot.img" on which boot.img was the extracted image from previous xiaomi.eu ROM. I can confirm that the device booted fine. I have yet to verify its working state (namely if it is able to screencast to Android (chromecast) TV which was the main issue I had with previous 13.0.8 version). After that I'll report back.

Cheers!
 
mccurly said:
@alimataei , hello. I am currently trying to boot latest 13.0.9 ROM (which, by the way flashed successfully with twrp-3.6.2_12.1-courbet-Aryannn999.img TWRP recovery), with previous 13.0.8 boot.img . Although it flashed alright, (the exit message from that flashing was the expected, "done"), I was still stuck on twrp recovery bootloop. So I rebooted from there into bootloader/fastboot, checked that the phone was recognised with "fastboot devices" command and having a serial code (of my phone) returned, I then used the command: "fastboot boot boot.img" on which boot.img was the extracted image from previous xiaomi.eu ROM. I can confirm that the device booted fine. I have yet to verify its working state (namely if it is able to screencast to Android (chromecast) TV which was the main issue I had with previous 13.0.8 version). After that I'll report back.

Cheers!
Click to expand...
Hello! @alimataei , I can confirm that I could boot that boot.img from previous xiaomi.eu rom (version 13.0.8). I can confirm that I could cast to Android (chromecast) TV as well.

@katerpanne , thank you for your workwaround.

I'll report back if / when issues arise.

I'll keep an eye on this thread.

Cheers!
 
  • Like
Reactions: katerpanne
mccurly said:
Hello! @alimataei , I can confirm that I could boot that boot.img from previous xiaomi.eu rom (version 13.0.8). I can confirm that I could cast to Android (chromecast) TV as well.

@katerpanne , thank you for your workwaround.

I'll report back if / when issues arise.

I'll keep an eye on this thread.

Cheers!
Click to expand...
Hi @alimataei and @katerpanne , Just for a last clarification. I've rebooted the phone into system after issuing that "fastboot boot boot.img" command. Of course it did boot, but, of course as well, that solution would not stick, since I did command the phone to "only boot" with that "yet unflashed" boot.img. (Remember, that the command I issued was "fastboot boot boot.img". But once I rebooted the phone, predictably of course, that boot.img would be gone. So again I rebooted into fastboot/bootloader, and to make that temporary boot.img stick, I issued "fastboot flash boot boot.img" (notice that the command was one argument longer, and instead of "fastboot boot..." I did a "fastboot flash boot...") and it had the expected result.

I have tested already and when rebooting again the phone did not reboot into recovery as previously.


Now to @katerpanne , are you somehow related to the developers team here at xiaomi.eu? Why did you suggest this boot.img workaround in the first place? What are the "lookout for" aspects that we should be expecting from now on from this workaround? Will there be a simple fix for this issue? (I was thinking of a full xiaomi.eu ROM where we wouldn't have to worry about do this workaround...).


That's all for now.

Thank you!
 
  • Love
Reactions: katerpanne
mccurly said:
Now to @katerpanne , are you somehow related to the developers team here at xiaomi.eu? Why did you suggest this boot.img workaround in the first place? What are the "lookout for" aspects that we should be expecting from now on from this workaround? Will there be a simple fix for this issue? (I was thinking of a full xiaomi.eu ROM where we wouldn't have to worry about do this workaround...).
Click to expand...
Last time I had a longer discussion with another user he had the same issue.
We have tried a lot and this workaround was helpful
I dont know why this issue occurs, this was the last idea from me and it was working :)

you can boot the boot.img or flash it
 
Last edited:
  • Like
Reactions: mccurly
mccurly said:
Hi @alimataei and @katerpanne , Just for a last clarification. I've rebooted the phone into system after issuing that "fastboot boot boot.img" command. Of course it did boot, but, of course as well, that solution would not stick, since I did command the phone to "only boot" with that "yet unflashed" boot.img. (Remember, that the command I issued was "fastboot boot boot.img". But once I rebooted the phone, predictably of course, that boot.img would be gone. So again I rebooted into fastboot/bootloader, and to make that temporary boot.img stick, I issued "fastboot flash boot boot.img" (notice that the command was one argument longer, and instead of "fastboot boot..." I did a "fastboot flash boot...") and it had the expected result.

I have tested already and when rebooting again the phone did not reboot into recovery as previously.


Now to @katerpanne , are you somehow related to the developers team here at xiaomi.eu? Why did you suggest this boot.img workaround in the first place? What are the "lookout for" aspects that we should be expecting from now on from this workaround? Will there be a simple fix for this issue? (I was thinking of a full xiaomi.eu ROM where we wouldn't have to worry about do this workaround...).


That's all for now.

Thank you!
Click to expand...
Well, thanks for the feedback. Ive replaced the boot.img file from 13.09 with 13.08 using winrar and flashed the 13.09 zip, everything works fine, also flashed magisk and orange fox afterwards both work perfectly too
 
mccurly said:
Hi @alimataei and @katerpanne , Just for a last clarification. I've rebooted the phone into system after issuing that "fastboot boot boot.img" command. Of course it did boot, but, of course as well, that solution would not stick, since I did command the phone to "only boot" with that "yet unflashed" boot.img. (Remember, that the command I issued was "fastboot boot boot.img". But once I rebooted the phone, predictably of course, that boot.img would be gone. So again I rebooted into fastboot/bootloader, and to make that temporary boot.img stick, I issued "fastboot flash boot boot.img" (notice that the command was one argument longer, and instead of "fastboot boot..." I did a "fastboot flash boot...") and it had the expected result.

I have tested already and when rebooting again the phone did not reboot into recovery as previously.


Now to @katerpanne , are you somehow related to the developers team here at xiaomi.eu? Why did you suggest this boot.img workaround in the first place? What are the "lookout for" aspects that we should be expecting from now on from this workaround? Will there be a simple fix for this issue? (I was thinking of a full xiaomi.eu ROM where we wouldn't have to worry about do this workaround...).


That's all for now.

Thank you!
Click to expand...
Hey guys, have u installed miui 14, android 13 on mi 11 lite 4g ? My only internet connection is this phone where im currently in and couldnt risk to flash it before getting confirmation
@katerpanne
@mccurly
 
So, update to xiaomi.eu_multi_MI11Lite_V14.0.3.0.TKQMIXM_v14-13 failed.
My courbet gets stuck in a bootlop (to TWRP recovery).

Flashing the boot.img from the previous version (V14.0.2.0) does not seem to work anymore.

Anybody successfully updated to V14.0.3.0?
 
Last edited:
You must log in or register to reply here.

Similar threads

M
Stuck on boot loop after installing ROM!
Replies
5
Views
3K
Questions & Answers
medesnabbt
M
Igor Eisberg
  • Locked
  • Sticky
Installing a Custom Recovery
Replies
0
Views
302K
Questions & Answers
Igor Eisberg
Igor Eisberg
F
Unable to flash Xiaomi.eu rom with TRWP on Mi 11 ultra
Replies
2
Views
3K
Xiaomi Mi 11 / Pro / Ultra / Lite / 11TPro
Fernando84
F
gogocar62
How to install Xiaomi.eu ROM for devices A/B
Replies
321
Views
165K
Xiaomi Mi 11 / Pro / Ultra / Lite / 11TPro
bicboc
bicboc
A
Mi 10 Lite Zoom: avoiding chinese
Replies
7
Views
3K
Xiaomi Mi 10/Pro /10Lite/Ultra/10T/Pro/Lite/10S
Poney70
Poney70
Top Bottom
Back