Question Xiaomi Note 11 stuck to rebooting into recovery mode 5.0 after unlocking the screen

Search This thread
Nov 12, 2022
17
9
Hi there, I've encountered this issue and fixed it by heating the phone, enabling USB debug and removing Qualcomm component via ADB.

Now I'm being suggested with the 13.0.2.0.SGKEUXM update...

Should I execute this update? Will it reinstall the Qualcomm component? I still have USB debug enabled but still..

Thanks.
 

fear619

Member
Oct 14, 2010
31
0
One And Only
Hi there, I've encountered this issue and fixed it by heating the phone, enabling USB debug and removing Qualcomm component via ADB.

Now I'm being suggested with the 13.0.2.0.SGKEUXM update...

Should I execute this update? Will it reinstall the Qualcomm component? I still have USB debug enabled but still..

Thanks.
I have problem with updating to 13.0.2.0 sgkeuxm, phone get stuck in recovery mode after reboot and after few hard resets i turns on but again on older version.
 

mhdrrazin

New member
Mar 7, 2023
2
1
I cant turn on usb debugging. Tried heating...sdcard...everything to no avail.any solutions!?
 

kodairyu

New member
Mar 7, 2023
2
0
1D5iFf5.jpeg

Doesn't work anymore, running Android 12....
Edit. OOOH DERP... I have 5G Note 10 with mediatek lol
 

taMim_bd

New member
Mar 12, 2023
1
0
Uninstalled successfully, but the trick DID NOT WORK 😭
Still facing the auto reboot to the recovery problem.

My device: Redmi Note 11 Pro+ 5G (Indian variant, Snapdragon SoC) running on Android 12, MIUI 13.0.4.0 (Global Stable)

1678615920059.png
 

lepusang

Member
Jun 24, 2015
23
3
I had the same problem

Believe the USB board is stuck in a dev deployment mode similar to metaDB loader
that's why it can't enable charging mode

Fix
Removed the back cover
Disconnected the battery
Reconnected the battery
Device started to operate as expected
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    1D5iFf5.jpeg

    Doesn't work anymore, running Android 12....
    Edit. OOOH DERP... I have 5G Note 10 with mediatek lol

    1D5iFf5.jpeg

    Doesn't work anymore, running Android 12....
    Edit. OOOH DERP... I have 5G Note 10 with mediatek lol
    For me uninstalling was success but it didnt solve the problem😥
  • 9
    Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.
    4
    my device is rebooting to recovery mode only 10s after unlocking it. So I cannot enable usb debugging as after clicking on "USB Debugging" to enable, it once again asks for confirmation which counts down for 10seconds. is there any other way to enable usb debugging.
    KEEP TRYING. I cannot stress this enough, just got my phone back from that hell-loop thanks to pxbrz for his advice and Adonys for sharing it. After like 70 or so attempts it didn't put me through the countdown, just an "Are you sure" pop-up and done.

    To give you a chance as possibly close to mine, take into account I:
    -Was in airplane mode.
    -Had battery saver on.
    -Entered settings through the notifications tab directly from the lock screen.
    -Passed through the steps as fast as I could.
    -Checked the waiver box before the countdown ended.
    -Close to the countdownless attempt, I kept tapping like crazy the countdown blocked button in case I was able to catch a minuscule frame (I'm guessing it happened though I didn't actually saw the button lit up).

    (I have no idea if anything of the above had an actual effect but just in case)

    Then I used the ADB command as pxbrz kindly instructed: (avoid the quotes)
    "pm uninstall -k --user 0 com.qualcomm.location" Followed this guide before:

    I haven't updated yet though some ppl in the thread said it's safe while you keep the service uninstalled, I'll avoid the update for as long as I can.

    Any questions whatsoever about what I exactly did, feel free to ask. It's not gonna damage your phone more than it is already and you'll get your phone AND files back.

    PD: Immediately backup right after just in case, I know I will lol.
    3
    Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.

    MIUI Global
    13.0.16.0(RGCMIXM)
    Android ver: 11 RKQ1.211001.001
    3
    I Cant Believe I have Just Done one of my Life's Stupidest Thing I just Heated my Phone and it Worked Out. If you don't want any Data Loss and want your Phone Normally Killing Out that Faulty QUALCOMM Program with Adb Works out Superfix USB Debugging is a problem then Heating has been a solution to me it just gave out that few seconds and I have Done it Finally
    3
    Hi all!
    So grateful to everyone here who helped with the solution.
    This particular thing worked and thanks to all the following workarounds for enabling USB debugging!!

    WIshing good luck for the future lol!