Phone starts to boot normally, then as soon as android starts and it shows the lock screen, it initiates another reboot. It loops this infinitely. Before this it was starting to grow unstable and was doing random crashes like this, but now it just crashes instantly as soon as it hits the lock screen on boot.
ROM is Mokee and my TWRP is 3.3.1-0. I can enter Recovery in TWRP atleast. Seems to be working fine inside there.
I would like to reset it, but my 2FA is attached, and so I need to get into the phone long enough to disengage all of them.
What can I do here?
Here's hoping:
Is there a way to backup Google 2FA from within TWRP so I can restore my phone and bring back Google Authenticator just the way it was?
Related
Hello everyone,
first of all thanks for your amazing work and all the stuff you provide. I was a silent reader for a long time, but now my phone is trolling that much, I cannot fix it on my own/with the guides I found here.
I do have an HTC One M7, rooted (superuser) and S-OFF (revone) with Androidd Revolution HD 71.1. I used to update my ROM every month, but I got stuck after the last update. My recovery was TWRP as CWM did not work properly when I rooted my phone.
My issues as a list:
- cannot enter recovery anymore
- cannot connect via USB (tried every port)
- screen turning randomly black on homescreen and sometimes in apps (but they usually work), screen does work, but i cannot see a thing
- since today graphical issues after a reboot (flickering screen, parts of the screen get duplicated)
Since the last update I cannot enter recovery anymore. Getting in bootloader is no problem but i get stuck in the "entering recovery...." screen. It does not move, tested it for some hours. I tried updating the recovery (-), trying to flash stock recovery and reflashing custom (-), trying cwm (-).
After I tried cwm i noticed that it didnt overwrite the recovery but i got both. cwm and twrp, but i cannot delete one of them (didn' work before either). I can start TWRP oder CWM on a booted phone, but updating both bugs and I can't enter recovery with these tools too.
Today I wanted to try again on my own, but my phone won't connect on USB. Tried every port on my computer with and without USB-Debugging. I will try on a other computer, but I could not do this until now. Additionaly I want to wait for some ideas of fixing, as I think "my" trys are not going to work suddenly .
Screen started to turn black a few days ago. Dont know why but I think it could be a software issue. but i cannot update (see above ). When i try to turn my screen on it often just turns instantly black. soft keys are enlightend and it does work (more or less). if i success in sliding down the service bar on the top, i can start my alarm clock app and from there use the soft keys to get in other started apps. From there it works most of the time. Sometimes i need a couple of trys, sometimes it just works as its intended without turning black and sometimes i need several minutes to succeed.
Cannot say more as I did to the graphical issues. Just had them once until I started an app (screen worked). could not reproduce this error.
I would prefer a solution without wiping, but if necessary i will ofc.
Thanks in advance for your help, as I am rather helpless right now.
I attached a photo of the bootloader.
Yours Laexxi
A couple of days ago, while sitting on the dresser, my XT1053 crashed and has not been able to fully boot and stay alive since. It will give the "bootloader unlocked" message, start all of boot animations, get to the blue-green one and then crash. To get a reboot, I have to hold the power button for 10 seconds, or it just drains the battery. Every once an awhile, the security screen pops up and it will crash, or I can get in, the launcher and services say they have crashed, then the phone shuts off.
I have an unlocked bootloader, but not rooted and was on 4.4.4 before the crash. I can usually get into the bootloader menu, and to recovery. If it crashes, I usually have to restart and do a hard close to get into the menu.
Fastboot works. I've followed this guide: http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148as well as the order in the .xml file that came with the 4.4.4 rom. Everything comes back "OK"
Is there something else that needs to be re-flashed to get it working?
The strange thing is that even though I have erased userdata and cache etc., on the rare occasions that I get beyond the boot animation, it still seems to have my custom message and the security pin. Is it possible that the cache and user data aren't actually getting erased? How do I check?
Any suggestions would be appreciated!
Hello all, this is my first time posting here, and I hope that my problem isn't permanent, but this morning my phone started to act strange. I reverted back to stock yet everything is still the same. Long splash screen time, and very laggy, very unresponsive recovery/UI when the phone is on. At first i thought that I had done something in my pocket on accident, so I clean flashed Chroma, my daily driver, and ElementalX. After rebooting from recovery, the Google splash screen had stayed on for about 20 seconds, compared to the 5 I had been seeing till today.
Now, when the phone actually booted, I was getting random restarts, screen becoming unresponsive along with the buttons. After setting up the phone, every app I tried opening would hang at the splash screen, like Hangouts, and would immediately stop responding, and eventually restart the phone.
TWRP also would freeze and the screen would lock on its own. When trying to swipe to unlock, the slider would freeze and behind it was another lock slide, which wasn't accessible. After reverting to stock, with TWRP once again, the boot and recovery still take 4 times longer than what they used to, and my phone is very sluggish to start. Has anyone else experienced this?
Currently on TWRP 3.0.0.2, stock 6.0.1, MMB30W image.
https://twrp.me/Devices/
Start with updating TWRP.
NLBeev said:
https://twrp.me/Devices/
Start with updating TWRP.
Click to expand...
Click to collapse
Flashed latest TWRP through fastboot, Google screen took 20 seconds again, TWRP started off fine, then froze after locking
Puuuddle said:
Flashed latest TWRP through fastboot, Google screen took 20 seconds again, TWRP started off fine, then froze after locking
Click to expand...
Click to collapse
You reverted back to stock. I assume you used a custom ROM. When you were unencrypted than stock forces encryption. That encryption process may last a very long time and depends on the amount of data.
You could think of wiping and formatting all partitions and do a factory reset.
Will try that soon, thanks ? completely forgot about encryption.
Hello there,
I've just found my old GT-S5300 from back in the day, and I tried turning it on to eventually use it again.
The issue is that when turning on, I get the usual "Welcome to GT-S5300" screen, and it tells me to "Touch the Android to begin"; when trying to do so, my phone doesn't let me go to the next screen to connect to Google and all the miscellaneous steps that come later. The touch screen does react, I can change the language/type a number in emergency call, the Android flashes when I touch it but it doesn't let me go to the next step.
I have tried factory resetting/wiping cache & data but nothing does it, I keep getting stuck on the same screen.
I even tried flashing a custom ROM and the stock ROM, but it seems my phone can't read the SD card I insert in it, I don't know why (32GB, works on other devices).
I have CWM Recovery installed so whenever I go to Recovery mode I have the CWM Recovery menu which appears.
Before burying it in my closet, my phone was indeed rooted.
Do you have any idea if there is a way to use this phone again? Thank you!
I originally was able to put GrapheneOS using their site's instruction and web based system. I was having lot of issues with it though, like I could not get group texting to work properly then found an app that supports it but I kept receiving old texts that were already sent to me before so kept trying to find a text app that works and was having no luck. Then I went to make a phone call and realized it was not even letting me do a phone call, it would just drop as soon as it tries to dial.
So I gave up with that and tried to load Lineage, following these instructions:
Install LineageOS on bramble | LineageOS Wiki
wiki.lineageos.org
Though maybe one thing I SHOULD have done that I didn't, is I did not bother putting in stock android back on, I just went straight to the steps for Lineage. I unsecured boot loader, enabled USB debug and all that too, then proceeded to load the recovery image. This is where things started to go south. After it was done loading, if I tried to boot into recovery, it did not do it. If I do try to boot into recovery I see the Google logo for a bit then it just goes back to fastboot. I also tried different ways to load it such as --slot all etc.
Now it's just doing the google logo, and then goes to the screen that warns about image being unsecure, then back to google logo and just doing that recursivly. If I try to hold down power button and any volume button (up or down) it will interrupt it and give me option to pause it, but that's it.
I put it in the freezer for now to see if it kills the battery faster as maybe it will stop doing this once the battery dies and it can actually shut down... but I am open to any other options.
Did I brick it? I have a feeling I got myself a $700 paperweight. I presume there must be a way to remove the storage chip and put a new one in or something right? Thanks in advance.
Ended up getting it going, letting it die completely so the loop stops let me get into fastboot mode again. It was quite painstaking but I eventually managed to get CalyxOS on it. I could not get Lineage because the recovery partition step of the install always failed, CalyxOS uses a different way to get the rom on that does not use that step.