Ok, so it is already 7/8 times in 2 months that I have to fully wipe my TF because it did not boot anymore and was stuck at ASUS logo screen.
Everytime I had to wipe it, reapply rooting and restore last backup (and I always loose something).
I am thinking that is a software problem: some applications create problem to filesystem or system files so that it will not boot anymore.
Is there some sort of safe mode while booting to identify what is stopping the boot process?
Or is there some way to investigate the problem after it happens?
Thank you
Chris
Hey everyone,
So my phone died and then I got it charged and turned on and it booted up to the encryption lock screen where it says to start up your device, enter your pin. So I enter my pin and then its says, "verified" and then "starting android". and then a padlock appears on the screen, it opens, and there's like a load up circle going around it. At first, I let the phone sit to see if it would do anything but after an hour, I figured something is wrong. I dont know why this happened, I think I might have accidentally turned on the secondary encryption, but this really sucks, I don't want to have to factory reset and lose all my pictures and data. I can boot into recovery mode but sometimes when i turn it on it shows a screen that says installing update and has like a google ring looking thing that should be spinning around but it looks like its glitching out, after that screen it will go to a no command screen, and then it will eventually reach recovery mode. I really hope someone can help or knows what is going on because, I really dont want to lose all my stuff.
Thanks for your time
I tried posting link but im new, if you look up s7 edge frozen encryption, its the first link , another person describes the same issue.
I had this issue. In recovery, tell it to clear the delvic cache. Then try a reboot.
It too a few attempts before the phone would not boot directly into recovery. But once i got it to do a normal boot, it started normally.
Then after it's running, back it all up, boot into recovery, and do a system restore.
Hi I wonder if anyone can help me. I restarted my phone, it asks for my pin which I enter correctly. It then gets stuck on spinning padlock. I've tried a soft reset (I think that's what it's called, holding down power and volume keys). It restarts, I enter pin, it says starting android then gets stuck again. I'm not very tech minded (typical girl). Can anyone help. I'd rather not lose all my photos and apps. Thank you so so much in advance. Toni x
I am facing the same issue, but with a Samsung Galaxy S8.
- Safe mode: doesn't boot
- Recovery mode: works, clear cache doesn't solve the problem.
So since nothing worked to make it work (except the Factory Reset, but I didn't tried this option), I decided to wait in the padlock screen. After 3 hours the phone started.
I guess that the phone is decrypting some big file during startup. Indeed, some days before before this problem happens, I downloaded some big files via torrent (~2-4 GB video files).
I'll delete these files and make some tests to understand the source of this problem.
Have same issue after recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.
Have exactly the same issue..Please help
After recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.
Good day! I wanted to ask how to remove the bootloader for zenfone max (the old one 2015 model) without using the app from ASUS as I cannot really use my phone. It boots then restarts. I already tried Wiping/Factory Data reset and Wipe cache with the Power and Volume down (Is it Recovery mode?) but still bootloops, by the way when I factory reset, my phone showed "Unknown volume for path /factory". My friend told me it could be that my OS was corrupted. So here I am wanting to unlock the bootloader so I could install OS for my phone.
**Note1: Sometimes it would boot to the "Welcome!" screen, then when I reach to the Wifi selection, it would always restart.
***Note2: This bootlooping happened when I restarted my phone because my wifi suddenly couldn't connect. After I restarted, it looped.
Noob here btw. Sorry and I would be glad to provide additional information if needed be.
Hello
My nexus 6p was working fine. i was downloading movie from torrent. when i last checked my cellphone i saw 'insufficient storage" message. i left the phone and after 15 minutes when i saw the phone it was stuck at boot animation. Now it wont load operating system i can access boot-loader the device is locked and i believe debugging mode is ON ( not sure about that )
what i want is to access my phone files and recover my data before i factory reset it. is it possible ?
Hi guys,
Trying to fix a friends x704f wifi only, but no luck.
It had Lineage 18.1 on it, and for whatever reason he did not like that, and went on to reflash stock with Lenovo's Rescue and Smart assistant which showed it a success rescue, but now Tablet boots to EULA, arrives to choose wifi and it crashes and reboots constantly, with no wifi icon being shown.
Lenovo rescue installed TB_X704_S000060_220916_ROW, so I factory reset it a few times from recovery, went through rescue again, installs same ROM, success, yet again it crashes at network selection, of if you do not touch anything, it crashes itself after about 20 seconds after being booted and if i hold the Power button and select shutdown, briefly the standard desktop shows with icons and than it crashes, so guessing ROM is there, it just can't boot.
Tried with QPST and latest ROM, but on eMMC xml selection I get error Document error on element program and name/value true.
Guessing baseband or some other thing should of been backed up before flashing stock again? if it helps, OEM lock is OFF, secure boot is ON what I can see from fastboot.
Thanks.
There must be something wrong with the persist partition, flash the persist.img again.