Database Info

Tablet stuck in "Installing System Update to Error!" loop

My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.

Meth_Badger said:
My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.
Click to expand...
Click to collapse
If I read your post correctly, you selected the right icon which is a Wipe data from your bootloader. When you executed that Wipe data, it will wipe everything on your internal SD including your /media folder or your personal files and data... The chance is very slim unless someone knows how to recover data from a wipe. Technically, your data is still there but it is only a dumb files which contain only 0's and 1's. Some recovery tools may be able to retrieve your data but I don't have that knowledge.. I hope that someone will be able to help you out and good luck...:fingers-crossed:

I'm afraid LMK is right: Your data is gone.
Do I suspect correctly that you interrupted the Wipe Data process after selecting it "accidentally"?
Choosign Wipe Data from the bootloader causes the BL to write a command to the misc partition to start the recovery and wipe the data partition. If you interrupted the process, there's no telling what and where that got corrupted - unless you just let it loop and pray that it finishes the wipe process which would erase the BL command. Connect it to power and let it loop for a few hours. What have you got to loose?
But your data is gone either way - sorry.

Morning, cheeky question(s)
Where are you located, and would you be interested in selling your bricked TF700? I have a broken screen among other things and would be interested in buying your tablet for spares if you are getting a new one?
PM me if you are interested.
Thank you
Freddie

I'm not all too sure what the Icon on the left wad, but I'm sure it said RKU or some sort. I would have given up all hope if I had hit the wipe data on the right.
Days recovery aside, is there anyway I can get my looped tablet to work? I plugged it into a comp and it didn't recognise it.

"UIDs on the sytem are inconsistent" error message + deleted data partition

Hey,
yesterday i faced a problem i didn't knew of yet. As i mentioned sometimes, i came from an One M7 2 weeks ago as it didn't work the way it should - camera useless and awful battery life. I rooted the M7, had problems with it and so on - just how it is with a rooted phone + custom roms.
However, due to the DRM i didn't root my Z3 yet. Yesterday i took it out my pocket, thought it was a bit warm.. nevermind. It worked. 30 minutes later i pulled it out again, still warm, and screen wouldn't turn on. I reset it (power and vol+ for those who didn't know), tried to boot again.. well, it took several minutes and finally showed me the attached error message. The system performance was really, really low. Everything stuttered, i couldn't even enter my pin. A few forced reboots later i could finally enter my pin and get into my system only to notice that my data partition wasn't doing fine. I had to set language and so on in the initial setup process, apps kept force-closing in seconds. My own apps were still on the device, however when i tried to open WhatsApp there was no data there, i should have gone through the registration process. The phone froze after seconds each time. I tried to enter the fastboot menu (is it called that way?) while booting to just do a factory reset, didn't find the button combination. So finally, after i found home without navigation from no man's land (sure, why doesn't it happen at home anyway..), i managed to boot it, get through settings and initiate a factory reset. Of course, all the apps were deleted then and i could install all apps like LightFlow again. Had to re-enter all the settings i did in those kind of apps, it was kind of annoying.
So, my questions: Why the hell did this happen to my Z3? Not rooted, didn't even think of it. There wasn't a day on the One M7 without flashing anything and it never happened. It wouldn't have been as bad as it was on the Z3, as i HAD root, could have wiped data in TWRP in a matter of seconds and also had backups of my data, which i of course didn't have for my unrooted Z3.
Is it likely to happen again? Can any app do this on a non-rooted phone? I read a bit about the error, that it would be caused by some apps, but not in the extent as it happened on my phone. Most of the times it would just be an annoying error message.
I got a thing in always getting a defective unit, so i hope it isn't happening again on the Z3

Maybe the internal flash is corrupted/failing. I had a similar issue with my HTC One X I went to nap one day and half hour later it shut down, it restarted but boot looped. Eventually it showed no data partition as being mounted and completely died. They replaced the motherboard.
Better contact Sony, maybe you need a replacement.

Mh, actually that's the least thing i want to do.. I'd have to wait for at least 2 weeks to get it back and chances are that they won't do a thing or damage it (bad experiences with my former Razr i). It works just fine after the factory reset, no errors yet. If it should happen again, i'd of course send it in for repair but i think, until then i will use it normally, with more caution and backups of course.

Probably the cleanest solution HERE

Encryption password randomly reset

Hi! I have an S7edge with full encryption enabled with a password. My phone was acting slow and firefox was not being responsive, so I power cycled it. It came back to the normal black screen with "Your phone is encrypted for security. To start up your device, enter your password." I entered in my normal password, but it was rejected. I tried this several times, which resulted in a message asking me to restart my phone. I thought that this was odd, since I changed the setting to never wipe, but instead just lock out for an increasing amount of time. After a few iterations of this, I'm at the 7 attempts left until a full data wipe.
I'm thoroughly confused as to
1. How my password is no longer working?
2. How the setting for lock out time vs. data wipe was reset?
Is there any way to solve this issue, or I'm out of luck and will need to perform a full data reset?

Unknown bootlooping problem on Redmi Note 10

Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.

Tex2083 said:
Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.
Click to expand...
Click to collapse
ADB is useless at this stage, through the stock recovery.
By enabling OEM unlock, but not binding your Mi account, to start the unlocking process, it´s also useless, per se.
You can´t flash any partition through fastboot, if the bootloader is locked, by enabling OEM unlock, it´s not enough to.
Try booting to stock recovery, you can wipe your data/factory reset, in case this may help.
But, probably, the issue is with the battery or the battery connector, pay attention to the charger time, and test if the charge level is correct.
Just in case you need to power off your device, you may connect to the PC while you press the volume down button, you´ll get fastboot mode, then disconnect the cable to the PC, device will shut off itself, when the connection time expires, it may takes only seconds.

Tex2083 said:
Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.
Click to expand...
Click to collapse
Hey there. Was you issue fixed? I had somewhat of a similar issue. My phone did the same bootloop in two different days. First I thought it was some error after update. I didn't bother. It happened once again and after few times of crashing at lockscreen, it actually booted and I was able to use it for a day. I thought of backing up my stuff but didn't give much attention. Now it have happened once again and this time it is never getting into usable boot. If the battery is sufficient enough, it'll go into lockscreen and crashes repeatedly. Then soon it just crash after the MI Logo and the three loading dots. Safe mode does the same. It boots into lockscreen at times but the safe mode symbol is not seen.
I read you were able to get your data out of it. Did you resolve the issue?

Android Phone locks immediately after entering correct pattern

Samsung Note 10, SM-970F
Magisk Rooted
Android 10, N970FXXS6DTK8
It's my GF's, and she uses a pattern unlock along with fingerprint. No new apps were installed or settings changed that she recalls.
Began as phone locking immediately after correct pattern was entered, but using fingerprint would unlock correctly.
With this immediate locking, the phone will by itself turn off the screen then turn it back on for two seconds as though the power button was pressed, then turns the screen off again.
When entering incorrect pattern, it says incorrect pattern and does nothing else.
She tried restarting the phone, which disabled the fingerprint unlock feature until the phone is successfully unlocked once.
Phone still locks immediately after entering correct pattern, and now she can't unlock it using fingerprint.
Now unable to unlock phone.
EDIT: If I repeatedly enter the correct pattern, after a random number of tries it will go to the 'starting phone' screen, but then will either restart by itself or sit there until I restart the phone. It really is random, once it took 7 tries, another time 20 tries. The phone doesn't show up on my windows PC as a mounted device during any of this.
USB debugging was not enabled, so I don't believe I can run any ADB commands. She didn't backup her phone and our focus is at least to get the photos off the camera, at which point doing a factory reset would be acceptable.
I've tried:
Entering a lot of bad patterns, trying to get to an option of unlocking with the google account associated with the phone, but the option never comes up.
Removing the phone case, only external item on the phone now is the stock screen protector.
Starting into recovery, clearing cache, repairing apps.
Starting into safe mode.
Booting in and out of root.
Letting the battery discharge completely to do a hard power cycle.
But no luck. The phone still locks immediately after entering the correct pattern. I haven't tried taking the phone's stock screen protector off, but will probably do that in case there is something wrong with the proximity sensor.
This is the international two SIM version of the Note 10, the only Note 10 variant which was rootable. I haven't worked on the phone for at least a year since it was rooted and setup.

SEU or a hardware failure. Either way when this happens your only option is to backdoor in. If it was a SEU after resetting you're good to go. If hardware it will likely reoccur... Even with a hardware failure many times nothing happens if no lock is set, you still have access. Setting a lock password introduces added failure modes.
SEU's are very rare but they do happen, randomly and just one bit of data is flipped. Interesting they cause no hardware damage. Higher altitudes elevate the risk as does exposure to man made high energy particles. That's one reason why spacecraft have 3 or more redundant computers. Apollo fights have logged half dozen or more SEU's per flight.
I never screen lock my N10+'s, double tap on/off. This is one reason why. Same with PC bios, no password is ever set. Once bitten, twice shy as the user is always the most likely person to get locked out... as I learned the hard way

@blackhawk, I hear you on getting burned with device security. And for any electronic device, secured or not, backups and redundancy are the only reliable difference between your device being useful and useless. It's been hard not to say any 'I told you so' about this, since I was telling her both to use a pin instead of pattern and to let me setup a regular backup. I don't know that a pin would have been different, but I think it would have since the fingerprint was working before the restart.
Do you have any resources you could point me to on how to backdoor into an android with a password/encryption? I know you can unlock a device using ADB, but I believe you need USB debugging enabled first and I don't know how to make that happen without first unlocking the phone.

mc_squirrel said:
@blackhawk, I hear you on getting burned with device security. And for any electronic device, secured or not, backups and redundancy are the only reliable difference between your device being useful and useless. It's been hard not to say any 'I told you so' about this, since I was telling her both to use a pin instead of pattern and to let me setup a regular backup. I don't know that a pin would have been different, but I think it would have since the fingerprint was working before the restart.
Do you have any resources you could point me to on how to backdoor into an android with a password/encryption? I know you can unlock a device using ADB, but I believe you need USB debugging enabled first and I don't know how to make that happen without first unlocking the phone.
Click to expand...
Click to collapse
Samsung repair can do it. A local shop or yourself, maybe. If there's an associated Samsung or Google account, start there. I never had to do that but the information isn't hard to find. The data will likely be lost though.
Meh, it's a very rude surprise.