Hi, sorry for the bad english. My Xiaomi 11t 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.
I have found this solution but it doesnt seem to work for my phone
" -In a cmd prompt with ADB, type in:
adb shell
-Then:
pm uninstall -k --user 0 com.qualcomm.location "
Related
Hey everyone. With the volume, touchscreen and other problems people reported with this phone, I was really happy that I didn't experience any of them with mine or I just didn't notice.
Until something I didn't see coming at all happened - the phone, unrooted and completely stock was sitting on a table and doing nothing, when it suddenly rebooted and entered an endless reboot loop. It would go until the Enter PIN screen, then reboot again.
I don't know the cause, because as I said the firmware wasn't abused in any way Completely stock apps and firmware (4.0.1, GSM yakju) . I didn't see a problem like this mentioned on the forum - so I'm posting my solution if anyone has a similar situation:
1. boot into FASTBOOT (for example through "adb reboot fastboot" with your phone connected to the PC)
2. on your computer, use the "fastboot" executable from the SDK and type "fastboot -w". It will FACTORY RESET your phone and DELETE ALL YOUR DATA. But at least the phone booted again and works as it should.
I really love this phone, but things like that are NOT normal... a typical user shouldn't have to deal with this kind of bugs :/
I'm really anxious and nervous about this so I'll simplify this as much as I can; recently my phone was turned on on top of my desk and randomly restarted. I thought little of it, as it quickly went through the OnePlus logo (it began to take longer the second time I restarted it) and Android splash screen, but then stopped on the circles animation and remained looping there. I have very important data on it that I'd like to recover and WILL NOT factory reset (flash) my phone.
The battery icon and percentage still show up when I plug in the device. I still have access to Recovery Mode, Fastboot, and Sideload through their key shortcuts. I previously had USB Debugging enabled but can't authorize ADB since I can't check the confirmation dialogue box (shows up as "unauthorized" in command prompt). I had very little storage (less than 250mB) for the last few days. I don't have root access, custom recovery, or an unlocked bootloader.
I already tried clearing my cache; if I restart after doing so it only takes a few seconds to pass the OnePlus logo as opposed to the ~20 seconds it previously took. This delay raises every few restarts. I've tried waiting many hours to see if anything would happen or if ADB would start functioning. I also tried fully draining my battery overnight and nothing happened. My files are not deleted/fully corrupt since I could still see them when flashing through internal storage from Recovery Mode. OnePlus chat support said I have to flash my phone and Twitter support refused to respond. Local data recovery centers said I could get my phone shipped to them for a free diagnostic, should I do so or is there a way to unbrick or recover my data at home?
Is there anything I can do? Thank you very much!... for now I'll just remain depressed...
TL;DR - My phone's stuck at the circles boot animation and I want to recover my files or fix the soft-brick without resetting. I don't have root access, custom recovery, or an unlocked bootloader.
UPDATE: I boot into Recovery Mode and "Reset System Settings"- my phone rebooted with 112 gigabytes of storage already taken up and all of my Android/data folders empty! I lost very little as I set my save folders to other locations! It looks like the error was not having enough storage! OnePlus chat support said that I had to factory reset my phone, DO NOT listen to them! MY PHONE IS UNBRICKED!
Check out other responses:
https://www.reddit.com/r/Oneplus5T/comments/ahfabg/data_recovery_for_softbricked_oneplus_5t/
https://forums.oneplus.com/threads/data-recovery-for-soft-bricked-oneplus-5t.986096
I am running the factory preloader and lk.img
I rooted my RN8Pro, using LR Team TWRP, running Riru Edxposed. I rebooted the phone while charging and suddenly it I'm in this weird black screen where at the bottom it says Written 137M and at the top it says
... triggered by MRDUMP_KEY ...
... kernel detected
Userdata size 53353Mb
Output to EXT4 Partition emmc:
Pre-Allocate starts at LBA: 77824
SYS_COREDUMP starts at LBA:79270
Not all of it was showing up on screen.
Can someone please explain what it's doing and how to fix it?
Update: Phone rebooted, not into MIUI though. Now its just black screen, I can't get into recovery, nor I can get into fastboot mode when I select fastboot mode I'm greeted by a bunch of chinese options. I believe this is the factory options.
I can access adb through this, but it is unauthorised so I can't even call adb reboot.
Update, I clicked emmc on that chinese menu and I've ended up booting into android. But it's a fresh install, not sure what is going on to be entirely honest lol.
KworrV said:
I am running the factory preloader and lk.img
I rooted my RN8Pro, using LR Team TWRP, running Riru Edxposed. I rebooted the phone while charging and suddenly it I'm in this weird black screen where at the bottom it says Written 137M and at the top it says
... triggered by MRDUMP_KEY ...
... kernel detected
Userdata size 53353Mb
Output to EXT4 Partition emmc:
Pre-Allocate starts at LBA: 77824
SYS_COREDUMP starts at LBA:79270
Not all of it was showing up on screen.
Can someone please explain what it's doing and how to fix it?
Click to expand...
Click to collapse
yesterday i have experienced the same issue and i have seen that Written 137M is increasing progressively like 137M 180M 210M... so i have just waited and didn't touch anything and it did reboot. Everything is working smoothly now.
I just held the power button to force shut down and turned on normally. It seemed to boot into android with no issues. It's kinda risky though, not sure if I'd recommend doing that. Also the factory preloader seems to have different power on button combinations, as pwr+vol up will load another menu that will allow u to boot to recovery or kinda like safe mode for windows, and pwr+vol down will load you into factory qc testing stuff (all in Chinese). I just use adb or other apps to boot into recovery because honestly I'm kinda scared to fiddle with that stuff given how easily this device gets bricked.
That's odd, for both of you it seems that it just rebooted fine, I completely lost android for some reason, had to reroot and flash twrp, edxposed and all that again! All seems to be working fine at the moment although getting random reboots here and there, not sure why!
Answer
KworrV said:
That's odd, for both of you it seems that it just rebooted fine, I completely lost android for some reason, had to reroot and flash twrp, edxposed and all that again! All seems to be working fine at the moment although getting random reboots here and there, not sure why!
Click to expand...
Click to collapse
Hi, I had faced the same problem, the issue here is that TWRP is just set to 0% brightness that means that everythink is fine but you need to go to the settings and than adjust the brightness. For an screenshot just answer.
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks
Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.
Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.
Hi, recently i got in a bootloop. I was at the beach, taking pictures with Gcam, and suddenly the phone started locking and unlocking the screen, and after some time it rebooted with a "android" screen. It showed a warning saying my android was corrupted, and gave me the option to try again or factory reset.
I clicked "Try Again" and the phone tryed to reboot, and it is in a boot loop since then. I can start it in fastboot mode, but the device won't be seen by Rescue and Smart Assistant, or by ADB. Yes, i have the USB drivers installed. When i try to enter recovery mode it says "no command", and factory mode just starts the bootloop again. Please someone help me
Managed to get past no command screen, and dida factory reset.