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
Related
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.
Stock Galaxy S7, no root, no dubious apps, only AirWatch Agent: play.google.com/store/apps/details?id=com.airwatch.androidagent required for installing a corporate email client on the personal phone.
Everything worked fine for months, until yesterday, when the app AirWatch crashed, and would not start.
The user decided to reboot the phone. On the reboot, the phone got stuck on the second Samsung logo animation.
Wipe cache, force restart, reboot, reboot bootloader were tried, hoping to fix this boot issue, but without success. The phone still stays stuck at the Samsung logo animation.
What I'm looking for: to avoid phone ROM reflashing, because it has no backup and the data on the microSD card is encrypted.
I want to recover the personal data, by any means.
Any suggestions on how to achieve this?
Thank you.
If you can't flash stock, and have already wiped cache, and the guy doesn't have a backup (dumb), then there's not much else you can do really
I'm not sure which part of the phone the encryption key is stored, but you could try flashing just the Bootloader part of the ROM with ODIN
Also not sure if flashing the same stock ROM over the top, but using HOME_CSC instead of CSC to avoid the factory reset, would mess up the encryption, but as a last resort it would be what I would do
Backups are good, if the data is so important to encrypt I can't see why it would not also be backed up
I understand your point and I agree with it.
As a sidenote, that encryption was required by the app AirWatch, not by the phone's owner.
We'll try those steps as a last resort, but for the moment, we're gathering information, since most of the options are a "no way back" process.
For example, I'm thinking about a way to inspect the boot process, and alter it if there's something there that hangs.
Could this be possible? Is there any documentation about this?
germanino said:
I understand your point and I agree with it.
As a sidenote, that encryption was required by the app AirWatch, not by the phone's owner.
We'll try those steps as a last resort, but for the moment, we're gathering information, since most of the options are a "no way back" process.
For example, I'm thinking about a way to inspect the boot process, and alter it if there's something there that hangs.
Could this be possible? Is there any documentation about this?
Click to expand...
Click to collapse
You could trying running a logcat with the phone connected to USB during boot, not sure if it will connect to adb though, worth a shot
https://www.xda-developers.com/install-adb-windows-macos-linux/
If it works it should show you what it's hanging on, no idea how you would fix it though without a custom recovery
Ok Masters, so I am having the same issue that this guy here:
https://forum.xda-developers.com/ga...mand-error-samsung-galaxy-j7-prime-s-t3929850
I can install any rom. However, the pin to register either face or fingerprint, does not work. So I cannot even get to the fingerprint screen because it returns me to enter pin, and when I re-enter it, it says is wrong. I guess it has something to do, the fingerprint so far, had just worked on Cerberus AOSP rom, but neither on one UI nor 8.1 based roms work. on 8.1 I get setting had stopped.
So, flash stock over odin was already tried and it gets stuck there. Already flashed no verity, no luck, flashed, bbos, godness, venom, no luck.
Any other advice? Seems that somehow I messed up with the encryption and that is making not registering the pin or pattern.
I managed to pass the screen with Magisk, but as soon as system boots and I try to set fingerprint, it says settings stopped. I am really frustrated now.
Thanks,
This was already solved. If anyone is interested in getting more details he they are:
The no command was because someway somehow, the system partition was "busy " or non-writteable, at least that was the message that I was able to read. I don't know how it got to that state, but my solution was the following:
- Select system partition in twrp and tapped on repair file system. I got an error immediately that twrp could not read system block. I changed file system to ext2 and rebooted twrp.
- once again I clicked on repair file system. No errors this time. Rebooted twrp. Changed file system to ext4. Rebooted twrp. Repaired file system again and rebooted twrp once again. Downloaded an aosp 8.1 rom and setted screen lock after the set up, it worked. Then, installed apollo v1. Screen got frozen for a second when setting pin, but it let me pass to set my fingerprints.
Then I knew that it was already working. Installed a One Ui rom to try and it worked again my screen lock with finger print.
Hopefully this helps someone as I found no solution whatsoever in any part of forums or internet, this was pure trial an error over 4 days.
Objective: I am hoping to be able to boot my existing system to recover data such as SMS, call logs, app data, and so on - obviously it was inadvisable to start messing around without backing up my data, particular with my amateurish capabilities. But that's the situation I am in. For some reason I thought that just replacing the Recovery was not going to risk my data. Its been over 5 years since the days when I would regularly flash my new phones with cyanogenmod, and my abilities were very basic even then.
Context: G930FD with stock rom, baseband ETC? - apparently for Dubai, which does not allow VoLTE or WiFi calling, which is what I was trying to fix when I got myself into this.
the Events:
- I enabled ADB and used Heimdall on Windows 7 to flash twrp-3.3.1-0-herolte.img
- initial attempts failed to complete download. I booted back into the system and applied OEM Unlock. Flashed successfully.
- chose the 'allow modification' option or whatever it says, not the Read-only option
- I did NOT check at that point to see if the system would reboot properly. I instead right away made a full back-up to my external SD.
That's all I did. After the back-up was complete I rebooted, and arrived at "SAMSUNG Galaxy S7" endless boot loop.
best guess: this is related to samsung encryption? TWRP file manager says that DATA is 0MB.
Again, I am desperately hoping that someone can help me recover my existing system. The threads I found on this subject all lead to wiping the phone and flashing a new rom.
thanks.
digging in deepr
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
t.krug said:
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
Click to expand...
Click to collapse
Reflash TWRP with Odin, boot TWRP, wipe cache, reboot.
Thanks.
I think greenman at sammobile had the answer --> NEW: S7 5 file firmware options (this forum wont let me post a link).
But I botched the execution and the CSC file overwrote my data. Crushing blow. I would say lesson learned, except that I already knew better and risked my data anyway. Sad.
I have a backup I made at the first launch of TWRP - but I assume its worthless since TWRP was not reading the encryption. Its only 3.7GB.
Side note - I did achieve the original goal of replacing the Emirati rom with one that activates WiFi calling and VoLTE.
Has this issue been solved?
I never recovered my data if that's what you mean. Did you look up greenman at sammobile? It sounds like someone followed his directions and was able to flash just the system files without overwriting their data. I think you had to modify the csc_home file. It was a bit beyond my skill level.
Oh, I was just wondering if your phone was still bricked. I didn't read your last message properly before replying lol. My bad.
I'm not personally having issues with a device, I was just curious if I could help at all.
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!