Hi,
if anyone could help with any suggestions with the following situation I'd be more than grateful...:
My S10e is running LineageOS 19.1, rooted with Lygisk.
I rebooted it several times with different SIM cards, no problems.
After one specific reboot, it entered a boot loop where it shows the Lineage boot animation for a few minutes, then reboots.
I never get to the unlock screen anymore.
After several attempts of reinstalling bootloader etc. as well as dirty flashing Lineage, the phone boots but I don't get access to data.
The partition is accessible but all files/folders are encrypted. I did define the same lock pattern as previously.
So, my question is: can I in some way bring the phone's software to exactly the same state as before and making it recognise data, so that I can decrypt it? The lock pattern is known and the same as before.
I'm a bit desperate as there is some important data on it that is just newer than the most recent backup....
Thanks for any hints!
Related
Good day.
I got a Nexus 5 D820 from my mom who dropped it in the river about a year ago at which time the phone was dead. It had indication of power but would not turn on. It was in a drawer powered off until yesterday.
I was able to power the phone on although it would not boot. The Google logo appeared and the android loading animation, but it would always reboot or freeze at different points. From the bootloader the phone seemed stable and I never had an issue pushing/flashing files. At this point I flashed a few different recovery images for the device, but only Philz would work, while TWRP and CWM would only freeze or bootloop.
From Philz I was able to flash a few different ROMS including the latest official one from google and also a few custom roms with/out gapps. None of these would boot and had the same freeze/bootloop at the google logo or android animation with no consistency.
I figured at this point possibly the sdcard had become corrupted/damaged by the water since I was able to flash pretty much anything I wanted. This is where things went downhill.
I followed a guide to use the partition editor from within an ADB shell. The guide assumed I was formatting an external SD card and suggested deleting all partitions. I did make a backup of the configuration of the partitions just in case but followed the instructions and removed everything. I was concerned what would happen once I rebooted the device at this point so I looked around a bit and it was suggested that flashing a google factory image would recreate the missing partitions so I didn't have to do it manually, so I rebooted thinking I could just flash the google package from the bootloader. This was the last time the phone ever showed any indication of working.
Now I have no indication of even power, no LED's, no bootloader.
Please let me know what you think... Thanks.
Before deleting the partitions, did you perform a full factory wipe before or after flashing different ROMs?
Does the phone appear as a device in Windows Device Manager when connected via USB?
If you deleted all of the partitions you deleted the bootloader partition.
Hi! I'm quite new here and I'm not sure if this post breaks any rule. T_T
Anyway, I successfully rooted my Xperia XA (F3115), thanks to this guide: [F31xx][Video Guide] How to root your Xperia XA (as noob friendly as possible )
However, after rooting, when I tried to encrypt the internal storage again, it seems like there is a problem. The encryption started but when the process rebooted my phone, it is taking too long. It has been more than 3 hours and my phone is still stuck in the boot screen with the "Xperia" text. :crying::crying::crying:
I do not want to interrupt the boot as I'm afraid it might mess up my phone. Do you have any advice?
Thank you in advance!
~~Update:
Because I need to use the phone I decided to risk it and interrupted the boot loop by holding the power button + volume up.
The phone restarted and showed that the encryption failed, giving me an option to Reset the phone.
I opted to reset the Phone. It just booted to the setup screen you get when the phone is new.
I will try to encrypt the phone again after setup.
~~update:
I have confirmed the Super SU app was the culprit. If you want to encrypt the phone again you will have to do it before the step where you have to boot into recovery to install Super SU.
~~update:
After setting my own password and encrypting the phone, I tried booting to TWRP. It asked for the password so I typed in my password, but it failed. Any idea why?
I really want to have a rooted AND encrypted Xperia XA.
Enable OEM Unlocking
Factory Reset from settings
Encrypt your internal storage
Unlock Bootloader
Flash respective images.
When entering TWRP, do not try to decrypt, tap CANCEL
swipe to allow modification, Swipe it
Flash SuperSU
Restore DRM
Reboot
Done
Your phone is encrypted and rooted.
I have a rooted Lineage-OS Samsung Galaxy S4 that I just encrypted. And now after I put my password in to boot it, it starts booting..... then keeps on booting..... and won't stop booting.
I know the password, as it also works for recovery.
I would like to actually get it to boot so I can un-encrypt it (decrypt it permanently) but it just doesn't boot.
Is there a way to decrypt it (permanently) using TWRP or flashing something? I do know the password so it should work. I am looking for solutions that will preserve my settings, apps, files etc.
EDIT: New question: https://forum.xda-developers.com/general/help/restore-samsung-galaxy-s4-userdata-img-t3820348
I switched off my phone (Motorola Z2 force, XT1789-06) during ringing. I am not sure if this caused the problem, but since then I can't switch it on. During booting, when it starts to show the animated "Moto" logo, it restarts booting, so I can't get to the normal graphical user interface. If I don't touch it, it repeats rebooting until its battery gets empty. It is not rooted, has latest official Android (version 9, I think, nash_retail) on it.
Until now the only thing I could do is to boot into fastboot mode. There I can log in into recovery mode or do some diagnostics, check some logs etc. As far as I can tell they show no problems at all. Except maybe "failed to read fstab from dt" in /tmp/recovery.log -- is it normal in recovery mode?
I tried some manual reboots from fastboot/recovery menu (on the phone), with and without SIM card inserted, with and without being connected to the charger, but they changed nothing: the phone keeps rebooting at the same stage of booting.
I hoped to be able to adb connect to the phone and pull the files from it, hoping I could use these data after a reinstall. But adb devices show no connected devices. I guess adb is not available in this stage of Android loading. Or is it available somehow?
fastboot devices show the phone, but I am not sure what can I do without triggering a factory reset. E.g. what if I would 'fastboot flash boot boot.img' from the stock ROM? I guess something went wrong on the boot partition, so rewriting it could solve the issue. But I afraid rewriting the boot partition would result in a complete factory reset.
My questions:
* what to try to make the phone booting normally?
* can I change boot config to skip logo animation?
* if booting normally is not possible: can I somehow copy my files from the phone to my laptop (linux)? If I can copy them: is it realistic to be able to use those files to restore the apps' states after a reinstall (after a factory reset)? I would like to keep e.g. my phonebook, SMS, Whatsapp and Signal chat history, OsmAnd favorites, Colornote notes, AndOTP credentials, etc. (I have a backup of some of my files, like photos or gps tracks, synced to my laptop with SnycThing automatically, but many others are not backed up recently.)
* if backing up my data is not possible: can I try to fix the booting issue by e.g. flashing a new boot.img without risking a factory reset? What exactly should/could I flash?
* if none of the alternatives above work: are there any other thing I could try or shall I simply accept the data loss and do a factory reset from fastboot menu?
Thanks a lot for your help and ideas in advance,
Peter
I have a SM-986U1 with an unlocked bootloader. I had it rooted and running, but because of some issues with auto brightness not working, I factory reset it. Ever since, whenever the phone loads into Android, it restarts after maybe 20 seconds. When I'm in Android recovery or even twrp it doesn't do this, only android system. I have tried to nand erase it but after Odin says successful it reboots, it doesn't clear partitions at all. I have flashed multiple firmware and gsi but nothing has worked. I suspect it has to do with a corruption in the ftp lock. When I can get in fast enough there is no account to remove, but it always shows ftp lock in download mode. I have had this issue for months, and the phone can't be used. Any help is appreciated. Thanks in advance.
Here is similar issue: https://forum.xda-developers.com/t/sm-n9860-soft-brick-recovery.4193859/ and looks like no fix yet. But you can try to bring in the Samsung Repair Centre.