I tried yesterday to encrypt my device (galaxy J500FN) and I got the impression my device was stuck in some loop, because every couple of minutes my device was rebooting and I had to enter my PIN-code, and this was going on all afternoon. So after having been busy for hours (seriously) I was getting tired of it and I decided to see what I could do to change the pattern, whenever I got into TWRP after rebooting again. I was fully aware that had the risk of resetting to factory settings, but I had made a backup before entering the process, so it didnât seem to be a big deal to me.
However, I am starting to believe a made a big mistake at that time, because now my device is entering TWRP whenever I boot the device. So I thought I could solve the issue by copying the e-image into internal-storage and then go through the installation-process again, but it seems my internal storage is wiped entirely. When I plug in my device by usb into desktop or laptop I canât find my internal storage, and also in TWRP it says my internal storage is 0 Bit.
So it seems I seriously screwed up.
I have to admit I donât entirely know what I am doing, butâŠ
*could somebody please roughly outline the steps I have to go through to bring my device back to life (assuming this is still possible, because I like to stay positive)?
Go to TWRP / Wipe menu.
format data (left side bottom) EDIT: I mean âRIGHTâ side
Reboot to TWRP
push e.zip to your device
flash e.zip with twrp install menu
reboot
and hope, everything will work again
EDIT: by the way. This: âWhen I plug in my device by usb into desktop or laptop I canât find my internal storage, and also in TWRP it says my internal storage is 0 Bit.â is, because your /data is enrypted. And thatâs why the new e-install fails. With format data as described above it should work,
I have the same device and know how to make the encryption work on Samsung devices when it doesnât work.
Have you tried Wipe > Advanced wipe > Select dalvik, cache, data, internal storage, system > And swipe to wipe ? Does it work or is there some red errors ?
When you start the encryption process I guess your phone will directly show the âeâ bootlogo and ask for the PIN code, and your phone wonât be encrypted. Is that correct ?
I hope you are still reachable. Your description seems to relate exactly to my error. I can no longer mount the /data partition, and I have the described boot loop (I can still draw the unlock pattern).
Also, TWRP now starts in recovery mode. If I perform the wipe now, will my personal data be preserved? Iâm a bit stuck on that.
Thank you very much for any help!!!
Jan
Info: I also didnât do anything special with the phone before the phone bricked into this state ⊠I am very confused, why this happend in the first place. :o
Hallo Harvey,
ich hoffe du bist noch erreichbar. Deine Beschreibung scheint sich auch genau auf meinen Fehler zu beziehen. Bei mir lÀsst sich die /data partition auch nicht mehr mounten und ich habe den beschriebenen Bootloop (das Entspeermuster kann ich noch einzeichnen).
Auch TWRP startet jetzt im Recovery Modus. Wenn nun den Wipe durhfĂŒhrt, bleiben dann die persönlichen Daten erhalten? Da stehe ich gerade auf dem Schlauch.
Vielen Dank fĂŒr jede Hilfe!!!
Jan
in TWRP, âWipingâ the /data partition will preserve the called âinternal_storageâ (mounted in /data/sdcard)
when âFormatingâ /data will also erase the âinternal_storageâ.
Hi aibid,
thank you so much for your reply! I guess you are years ahead of me. I just start trying to understand the concept after all.
I replaced the e-recovery with TWRP, like you suggested! And itâs possible to boot into TWRP.
Itâs a Samsung Galaxy S9+.
And now I fear there might be a reason why all this happened also!
First: I received a âsystem storage full warningâ the same day, but did not have the time to deal with it.
Second: I now understand that E-OS (per default?) encrypts the storage (wow ⊠actually I never âwantedâ that (I have no top-secret stuff x))
I guess the problem is: I guess I switched the phone off to save battery and after restarting it now trys to decrypt, but stops because the memory is full.
Could that be?
When I want to do a Backup with TWRP - it says âfailed to mount storageâ - Backup failed.
When I log into the phone with adbâ> the folders seem empty and I have very limited commands.
Good situation: I have a second S9 Phone (with e-os and working!) and here everything is exactly the same (no backup with twrp). But as soon as I enable adb via developer option ⊠access to the files is possible via adb and then suddenly the shell is also able to do more commands.
Hi Piero!
thank you so much for your reply! This might be exactly the thing I am missing here. I wiped the cash and Dalvik cash via TWRP. But I am afraid if I wipe Data than a lot might be destroyed.
So my pictures will stay intact with " Wiping /data" ? But the apps will be wiped?
It has been reported before that a user can easily be overtaken by this warning. I think this is the problem to solve.
Loosely speaking, the phone requires some âheadroomâ to restart. So if that required headroom exceeds the free space then system will fail to start and Recovery will start instead.
(One reason the the phone might suddenly overfill could be that some automatic backup occurred.)
I think that trying to understand as much as you can of the âencrypted /data partitionâ thread which you linked above is the way to go.
Your description seems to relate exactly to my error. I can no longer mount the /data partition, and I have the described boot loop (I can still draw the unlock pattern).
