Hey all,
I have updated by Redmi Note 8 Pro, to 11.0.3 yesterday. The updated stated to be solving some issues with Netflix (although it worked perfectly fine for me).
The issue:
After unlocking the phone, it reboots itself after a few seconds 10-20s, and goes into redmi-recovery 3.0.
Thankfully it is giving me enough time to use google authenticator (I have extremely important auth codes here that I cannot lose).
Edit: Worth mentioning that this happens when the Xiaomi Sim Activation Service is performing its activation.
Edit2: The "unlocking", refers to unlocking the screen by drawing the pattern.
Way forward:
As I don't have a secondary phone with the authentication codes, the option to wipe the system is a no go here.
I have been scouring the forums for any hints etc, but did not come across anything useful for my case.
Do you have any suggestions how this situation could be averted? Any feedback welcome.
Thanks!
khorne55 said:
Hey all,
I have updated by Redmi Note 8 Pro, to 11.0.3 yesterday. The updated stated to be solving some issues with Netflix (although it worked perfectly fine for me).
The issue:
After unlocking the phone, it reboots itself after a few seconds 10-20s, and goes into redmi-recovery 3.0.
Thankfully it is giving me enough time to use google authenticator (I have extremely important auth codes here that I cannot lose).
Edit: Worth mentioning that this happens when the Xiaomi Sim Activation Service is performing its activation.
Way forward:
As I don't have a secondary phone with the authentication codes, the option to wipe the system is a no go here.
I have been scouring the forums for any hints etc, but did not come across anything useful for my case.
Do you have any suggestions how this situation could be averted? Any feedback welcome.
Thanks!
Click to expand...
Click to collapse
Unlocking of the bootloader if I am not mistaking always goes with an automatic wipe of system and I am afraid nothing can be done to avoid this besides of course not unlocking bootloader in the first place.
From what I recall it does not go to recovery by itself when it completes the unlocking procedure, it just reboots to fresh new start of OS.
Sorry if I am bringing some bad news here.
Good luck!
Muad.Dib said:
Unlocking of the bootloader if I am not mistaking always goes with an automatic wipe of system and I am afraid nothing can be done to avoid this besides of course not unlocking bootloader in the first place.
From what I recall it does not go to recovery by itself when it completes the unlocking procedure, it just reboots to fresh new start of OS.
Sorry if I am bringing some bad news here.
Good luck!
Click to expand...
Click to collapse
Thanks for your feedback even though it might not be positive!
> Just to clarify I did not unlock the bootloader, it was a standard OTA update pushed to my phone.
>> By unlocking I mean drawing the pattern on the screen, the phone works fine while "locked", but as soon as I unlock it (draw the pattern), it will restart after 10-20 seconds.
Thanks again.
The issue somehow disappeared on its own.
For people who would experience this in the future (I have no idea if any of those steps fix the issue).
>Since I had a limited amount of time to take all the actions, I performed a sync of all accounts + did a fresh google backup
>Once triggered I quickly locked the phone (This prevented the restarts).
After I completed backing up all my data and was about to wipe the phone, it suddenly started working as usual.
I have no idea if the backups triggered some mechanism or did the mi account sync trigger the SIM Activation Service, but the issue is now gone.
Related
Three days in with a replacement Pixel C, it has stopped recognising my lockscreen pattern. I know it is correct as I use the same pattern on my phone. Wiping the cache has no effect.
I can't use Android Device Manager to set a new password as it detects that the lock screen is already active.
Is there any option other than a factory reset?
PriyanPhoenix said:
Three days in with a replacement Pixel C, it has stopped recognising my lockscreen pattern. I know it is correct as I use the same pattern on my phone. Wiping the cache has no effect.
I can't use Android Device Manager to set a new password as it detects that the lock screen is already active.
Is there any option other than a factory reset?
Click to expand...
Click to collapse
In this case, even a factory reset might not help.
Just to confirm, should anyone else have the same issue, a factory reset did solve the problem and the error has not returned. Still no idea what could have caused it though.
Solution
I had this problem also just hold the power button down for like a minute.
I'm having the same problem, was working fine a few hours ago then not recognizing the pattern. I've tried holding the power button but that just powers it off. When I turn it back on it asks for my pattern to power the device back on and it recognizes the pattern then just fine but once it power's up and I try to put the same pattern in to unlock the screen it says wrong pattern!! What the hell is going on here? Any help please?
This happened to me and Google RMA'd the unit. I had to factory reset it, but if you want to retain the data on it I strongly recommend installing something along the lines of Airdroid so that you can access the file hierarchy remotely even if the device is locked.
Airdroid has its benefits in other areas, however I found it a lifesaver for that one incident which allowed me to pull my files prior to the factory reset.
NJ72 said:
This happened to me and Google RMA'd the unit. I had to factory reset it, but if you want to retain the data on it I strongly recommend installing something along the lines of Airdroid so that you can access the file hierarchy remotely even if the device is locked.
Airdroid has its benefits in other areas, however I found it a lifesaver for that one incident which allowed me to pull my files prior to the factory reset.
Click to expand...
Click to collapse
Thanks I'll have to check into that app. I already did a factory reset this time and it worked but I'm just curious what caused it and if I should just not use a screen lock on it anymore? So when you say you RMA'd the unit you mean Google swapped the unit out for another one? Or they recommended you to do a factory reset? Thanks again for the advice.
1barlog17 said:
Thanks I'll have to check into that app. I already did a factory reset this time and it worked but I'm just curious what caused it and if I should just not use a screen lock on it anymore? So when you say you RMA'd the unit you mean Google swapped the unit out for another one? Or they recommended you to do a factory reset? Thanks again for the advice.
Click to expand...
Click to collapse
Yes, Google sent me a new unit. They didn't advise to do a factory reset, they just advised to return the unit. Part of their RMA process is that they recommend you wipe data (for data protection) so I ended up doing both.
I imagine that there are other apps which would offer access to your device data without unlocking, I just have experience with Airdroid.
I also had this problem, but I was using a pin instead of a pattern. Very concerning to be locked out of your own tablet. Had the tablet for about 3 months before it happened. Factory reset fixed it, hasn't returned since but only time will tell. Doesn't inspire a lot of confidence in the device knowing that maybe you could get locked out at any moment.
The same problem has been found on the Nexus 6p. Lockscreen not unlocking with the correct pin/password, appears to be a problem with the lockscreen as the phone can be booted or decrypted with the correct password.
The suggested fix was to ensure you have prey or another similar program installed. Changing your unlock password remotly via prey fixes the problem allowing you access to your phone.
Just had this problem today. Went to login with the same pattern I've been using for the past 3+ months, and it said "Wrong Pattern" over & over again. I tried to reboot and try again, same story. I used Android Device Manager to lock it & entered a password. Then my Pixel C confirmed that it was locked via the Android Device Manager, but when I went to log in, it asked me for a pattern, not a password! (Bad sign!) And, of course, I entered the right pattern and it told me it was the wrong pattern.
The Google support rep said I had to do a factory data reset. It is indeed disconcerting and frustrating. Next time I'll use Backup!
are you guys rooted? I had this problem on my N5X during rooting and trying to install ROMs. wiping data helped but I simply reset the device anyway. I noticed this also happened on some devices when an incompatible version of SuperSU was installed. If not rooted then you got me.
I am not rooted. I haven't done anything to the tablet except install & use apps and install a p12 certificate (which, I believe, unfortunately, requires you to use some kind of lock screen).
So, I used Android Device Manager to erase my tablet & the problem went away. Yay! I changed to using a PIN instead of a pattern. Now, today, just over a week later, the problem has recurred. <sob!> It says "Wrong PIN" when I try to login, even after powering off & on again, and I am facing the prospect of having to go through all that again.
Just had the same issue, tablet not rooted no developer options unlocked/used just left as factory with apps installed from play store.
Factory reset in progress...
Just happened to me (on the official beta ROM)
This just happened to me today on my Pixel C. I found threads on Google Forums that this has been happening for over a year without a fix.
If your bootloader is unlocked, you can always boot TWRP, Advanced > File Explorer, change to /data/system and delete locksettings.db, locksettings.db-wal and locksettings.db-shm.
Does anybody has an idea here? I'm confronted with this issue: Wrong PIN. No matter how many times i give the correct PIN
restarting Pixel C does not help. Is there any other way to fix this issue?
Shame on Google for this!
farsiray said:
Shame on Google for this!
Click to expand...
Click to collapse
Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.
bornheim2 said:
Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.
Click to expand...
Click to collapse
Looks you have no clue what you're talking about. Do some more reading before you give a useless comment.
This is an issue with Pixel C since 2016, Google still hasn't fixed it.
https://issuetracker.google.com/issues/62404336
https://productforums.google.com/fo...ce=footer#!msg/nexus/ImQsmQ8-8JA/n-1kqOv9AwAJ
Hey all,
I've done heaps of searching here and the wider web but only found reference to rooted phones failing to take updates.
I can't get a screenshot on here right now as I'm at work so no wifibut:
- Android OS _______________3.04GB :silly:
- Chrome__________________434MB
- Google Services ___________24.13MB
- etc
When I read about the failed update I checked in there and sure enough I have a 2017-5 patches system update sitting there failed, when I retry it it will download successfully then do step 1/2 of the installation then fail.
So it seems this would be the problem but the phone is definitely NOT rooted, any ideas??
thanks
You speak in codes, man. Could you explain your issue simpler? Right now I see an Android OS usage of 3.04GB. That seems abnormally large times 10. No one should have that, really. So it seems like your Android OS process downloaded multiple copies of system updates in error. Is that your problem?
Your post is still largely incomprehensible, so I won't make a final conclusion.
These are just suggestions:
1) If your phone is downloading system updates over and over, just damn update so it stops, or factory reset your phone.
2) If this is some kind of a rogue app, you are literally funked. Good luck trouble shooting it.
In any case, GL!
Yes, android OS used 3.04GB in ~5 days, my best guess is it was due to repeated attempts at '2017-5 patches system update'
Sorry, when I did a search I got heap of references to rooted phones having this issue so I guess I just talked from that reference point? It seemed to be a known issue but for rooted phones.
I just wanted to be clear that my issue matched those symptoms but was not rooted.
1) I've tried a manual update (many times) fails at the same point, I assume this is what is causing the data usage, as mentioned above.
2) Pretty sure it's not a rogue app
I'll try a factory reset, it's only a couple of weeks old (warranty replacement) so I hadn't really thought to reset straight away.
The phone doesn't necessarily need to be rooted to fail the update. A previously rooted phone can also fail to update as described, but typically that would mean an unlocked bootloader. I would have figured that the phone would have been reimaged and the bootloader locked on a refurbished phone, but maybe that doesn't happen. Is the bootloader unlocked? If so you could image the phone yourself to see if that works to fix it. If the bootloader is locked and a reset doesn't work, then I figure you might need to contact support about getting a different phone.
https://developers.google.com/android/images
I think you've gotten good information from everyone so far but just to add some clarity.
I had this exact same issue and was not rooted but did have an unlocked bootloader.
A factory reset did not resolve it. At the time I had issues, there were questions about rooting the stock images so I flashed PureNexus and have never looked back or had the issue again. Also, Verizon did add data to my plan and credit my account for the additional charges to negate the cost. Hope this helps!
It sounds like an issue with your phone that Pixel support might be able to help you with but they will certainly suggest a factory reset so you should do that first. Since you have a refurbished phone you don't know how the previous owner was using it and its possible a modification he made is still on the phone and causing you problems. If the failed system update isn't actually causing the excess data usage it could also be a carrier issue. I know some Project Fi users had that problem and it was related to the service. Google gave people credit for the excess data. You could also have an app that is interfering with the update so a factory reset should definitely be your first step and I'm guessing it's fairly likely to fix your problem.
Hi everyone,
So i know this is a long shot but there are some amazing folks on XDA so after scouring the web i figured this was my final hope.
So my niece has a stock S9 (G960U1) bought directly from Samsung. 2 days ago, her phone died overnight and when she put it on charge and booted her pattern no longer was being accepted. Same pattern used for quite some time. She kept trying it and then thought maybe she did forget it somehow and tried something else and of course now she only has a few attempts left before auto wipe (option was on in the settings ). She foolishly had everything on her phone out of which the most important is photos of someone who has passed and no recent backups.
It seems that most of the stuff was backed up to Samsung Cloud but the images and no backup turned on. So i've been desperately trying to help her as the only option seems to be wipe at this point but i don't know if recovery software will even be able to fully recover the images.
Tried so far:
Find My Mobile won't work as phone is on boot screen so no internet connection
ADB won't work because it won't accept the shell cmd
Aroma File Manager won't install (sig failure)
Tried a few programs available online (Dr Fone etc) but they either don't support the S9 or they wipe phone
Some mentioned the Extreme Syndicate thread but that also states you have to wipe
Friend works with Samsung sales and he's going to check with a tech but haven't heard back from him yet (not even sure they can do anything)
We do have the original receipt from Samsung (bought directly from them)
Really appreciate any help and if a wipe is the only option then let me know if you have a preferred recovery software that will hopefully be able to recover the images of concern.
Thanks
If she has a Samsung account, you can unlock the phone. Go to https://findmymobile.samsung.com and sign in, then look on the right menu, there is an option to unlock phone.
kenboyles72 said:
If she has a Samsung account, you can unlock the phone. Go to https://findmymobile.samsung.com and sign in, then look on the right menu, there is an option to unlock phone.
Click to expand...
Click to collapse
Thanks for the response but no internet access at boot up.
.
rodagola said:
Hello everyone on xda, please bare with me. Here's my story
I own a Redmi Note 8 pro, chinese rom model. It was running miui 11.0.3 over android 9 If I recall correctly.
Ok so... I was tired of some of the china apps pushing their notifications over and over and auto installing stuff, so I looked up how to apply adb commands to remove such bloatware, which was a fairly simple process. I copied and pasted a list of safe stuff to delete I found around some forums.
then... there were some other packages I checked out using an app called "app inspector", which directly tells you which app is under which package (totally useful for this purpose).
I tried to be careful not go overboard since I don't have any root access, or custom recovery, and wasn't really planning to have these, just wanted to keep this as my simple daily driver cellphone, but also perform this little maneuver to get rid of some bloatware.
little did I know, I was about to somehow softbrick it. More info: I did not use a screen lock method other than the "swipe up".
Ok, so I uninstalled some packages I cannot remember exactly how they went, but they had the terms "xman" and "yman" on them I think, I wasn't so sure about them because I looked them up on the web yet they didn't appear anywhere. I think they went something among the lines of "com.android.miui.xman". I also uninstalled 2 or 3 more, but after googling, they seemed unsuspecting.
Anyways, I'm aware there's a command to reinstall the packages because they're still on the phone's ROM image. That is in case I had to restore anything back to normal. Turns out I later rebooted the phone and when it launches the lock screen, I keep swiping up but it won't take me over to the actual MIUI launcher. The screen is frozen on the lock screen.
I'm not freaking out at this time because I still tried to connect the device to the pc, and it still shows as connected, I then go to the adb console and type "adb devices", it is still recognized, however, it says next to it that it is unauthorized... damn it. So now I might not be able to run the commands that allow me to reinstall the exact packages that are rendering the phone softbricked (I guess), plus I'm not really sure which package caused this.
After about a minute or two on the lock screen, the phone takes me to the "redmi-recovery 3.0",
which displays 3 options:
Reboot to system: which basically forms a loop
Wipe date: godforbid... really don't want to do it since I likely had many files not backedup
Contact miassistant: not sure what to do with this, says "pcsuite.mi.com" at the bottom
on the miassistant option you can apparently sideload stuff, idk how to go about this, maybe it allows me to install a slightly upgraded ROM, which in turn will work the same as if it was an OTA update (so it will keep my data as it was instead of wipe)? Because the point is not to erase my user data!!
I'm not sure how to feel or what to do without losing my pictures, notes and documents
I have hopes this situation can be turned around back to normal, and like the title implies... I'm WILLING to PAY you through paypal or something to WHOEVER offers to guide me through in the best way possible. Please if you have the knowledge/experience don't hesitate I'll also be grateful timelessly.
I'm not an expert at these scenarios so I might as well ask on xda where most are really skilled! Thanks in advance to those amazing souls
Click to expand...
Click to collapse
tldr;
If you can boot into fastboot mode you can just flash a official MIUI fastboot ROM:
Xiaomi Firmware Updater (where you can download official MIUI ROMS): https://xiaomifirmwareupdater.com/
This is the current hard unbrick method: https://telegra.ph/Installing-Redmi-Note-8-Pro-firmware-via-SP-Flash-Tool-01-21
It should also work in your case and there's even a video guide.
This is another video guide for fixing a hard brick:
Both methods above will format your phone though (afaik all data will be lost).
Compass.
.
rodagola said:
are these the kind of roms that you unzip and have the BL, AP, CP, CSC files? I could try that, but I've heard installing home_csc will not override/wipe my personal data. If this is what you meant, can you confirm? Or do you reckon these linked video tutorials would not wipe the data?
Click to expand...
Click to collapse
Nope, it doesn't.
If you can boot into Fastboot, flash the ROM using Mi Flash, otherwise, use this tutorial:
.
Compass Linux and juliusjr have told you the method, so I will just add supplemential infos.
In your case, I think simple upgrade will do the trick, dirty flash is applicable both via fastboot flash (mi flash) and recovery flash (the mi assistant method). If you want to stop the ads, I will recommend you to unlock your bootloader, move to global, root, and use an adblocker (a bare minimum config, in trade of some bangking apps being blocked).
I don't know the corresponding version for miui china rom, but in global rom, prior 12.0.0.7 (the one with the early 2021 security update), you can dirty flash back and forth while keeping your data.
.
rodagola said:
Hi, thanks for your info, I would like to try the mi flash tool as I've been told before the stock recovery thing has less chances of working. However, I had dev options turned on before but didn't manage to turn on the "OEM unlock" option, will flashing original ROMs work this way? or did I need that option toogled on? That's my last doubt, and thanks a lot. Btw, the China ROM this Redmi N8P had never ever showed me any ads, but thanks a lot as well for such input
Click to expand...
Click to collapse
You still have a locked bootloader? (How do I know? You will see "Unloked" on the bottom of the screen everytime your device reboots and showing mi logo if your device is unlocked)
Hmm, mechanically it work like normal ota update. Full recovery update will ony erase nessesary partitions (system, boot, and some other things) while keeping your data intact. So doing this to your phone technically safe. You can do this with MiFlashPro, do a recovery update using a recovery rom (the 2 gigs one) greater than your current MIUI version. But please bear in mind that I have never done this before to a locked phone. A same distribution version IS A MUST (i.e. global with global).
Oh and it will need you to log in to your xiaomi account. My guess is you need the flash permission open for your account (if you have unlocked your phone you shouldn't have a problem). I have never flashed with an account that never have been used to unlock a bootloader, so I might be wrong.
If your phone is bootloader unlocked, Mi Flash is the least demanding and it can retain your data with "save user data" in the bottom right corner option on, regardless your miui version (but I think there will be some problem with installed apps if you downgrade from A10 to A9).
Hope this help.
Hello all,
Please help me to detect the exactly issue on my Pixel phone - Google Pixel 6 pro:
+) Somtimes my screen goes black, I press the power button and it still makes a sound - I mean it looks like still working).
+) But tp get it working again as normal, the only way is to press and hold the power button in 30 seconds to reboot.
+) A my friend said that it was due to the current version software? But I am not sure, please help to detect exactly reason at here.
I attached the video about the issue and the picture about the current version sofware.
Appriciate alls.
I don't have much to say that can help. I just wanted to mention that my wife and I haven't had this issue in the 3 1/2 months we've had our P6Ps, including on this latest update (same as the version you're on).
There are several things you can try to see if it'll help.
A Factory Reset, or if you're going to do that anyway, might as well try Official Google Android Flash Tool with having the option chosen to do a full wipe and flash all partitions. With any luck, the issue would be solved. I would be careful about what apps you reinstall after resetting or reflashing, although I wouldn't expect any particular app to be the culprit, but this should be ruled out.
I am assuming your phone isn't rooted, or even have the bootloader unlocked. For Official Google Android Flash Tool, OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own.
roirraW edor ehT said:
I don't have much to say that can help. I just wanted to mention that my wife and I haven't had this issue in the 3 1/2 months we've had our P6Ps, including on this latest update (same as the version you're on).
There are several things you can try to see if it'll help.
A Factory Reset, or if you're going to do that anyway, might as well try Official Google Android Flash Tool with having the option chosen to do a full wipe and flash all partitions. With any luck, the issue would be solved. I would be careful about what apps you reinstall after resetting or reflashing, although I wouldn't expect any particular app to be the culprit, but this should be ruled out.
I am assuming your phone isn't rooted, or even have the bootloader unlocked. For Official Google Android Flash Tool, OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own.
Click to expand...
Click to collapse
Many thanks for your response, I tried flash to factory image sq1d.220105.007 last night yesterday. I will not try update, install some needed apps and continue monitor to see if it repeats or not? I will get back to you if need help anymore. Tks again.
hichichachac said:
Many thanks for your response, I tried flash to factory image sq1d.220105.007 last night yesterday. I will not try update, install some needed apps and continue monitor to see if it repeats or not? I will get back to you if need help anymore. Tks again.
Click to expand...
Click to collapse
Good luck! I hope it helps.