So I encrypted my phone last night, it seemed to have worked, the little android encryption icon came on for a while then it rebooted and asked for my pin. I entered my pin and it went back to the android encryption icon and just stays there. I left it over night thinking it was just taking it's sweet time to encrypt, but it did not come back. I'm still able to access CWM and can mount everything but /data and /system.
I tried ODIN'ing the phone with the stock LEN tar but that didn't work. It still asks for my pin, takes it, then sits there at the android encryption guy. I'm fairly certain I need to just re-partition the phone but I cannot find the PIT to do so.
Anyone have any insight?
Edit: I've wiped data/factory reset and wiped cache, but whenever it tries to wipe data, it gives an error mounting data and system (likely as they are encrypted).
Managed to fix it. Had to re-flash the stock recovery and then do a factory reset. While it didn't look like it was successful (it appeared to hang on formatting data) it rebooted and went straight into the OS.
Hopefully this will help someone in the future.
Related
While installing the most recent update to my encrypted SG3-L710, the phone restarted and while booting up remained stuck on the blue/white Samsung logo.
-After removing the battery and attempting to get around this several times it appeared that the update had soft-bricked my phone. I was never prompted to put in my passcode to undo the encryption.
-I am able to access CWM Recovery and, being that the only significant thing I would lose are my contacts so I attempted to perform a factory restore which was unsuccessful. It appeared the error indicated it was the /sd_card and /data folders posing the problem.
-I attempted to mount and unmount the /sd_card and /data folders which was unsuccessful, formating them also did not work.
-I downloaded Odin and the PIT file as my last hope. I attempted to flash the stock ROM to the phone and hopefully wipe the old ROM from the system. Odin also encountered problems with the /sd_card and /data and was not able to progress past that point. Now I am attempting it a second time to obtain the specifics and it's stuck on "<ID:0/004> Send lock information...".
Any ideas on how to be able to bypass the encryption and wipe my phone so I can flash a new ROM on this?
I've been working on this problem for almost two days now and I would greatly prefer not having to send my phone into Samsung and spend $100 to do this for me! Thanks ahead of time, bear in mind I'm new to this and might be a bit slow.
Hey; first time on here.
I came across this app, exactly titled "TimeZone Fixer (ROOT)", and was curious about it. Downloaded and played around with it. The thing told me to restart to take on effect, so I did. Phone goes through the reboot process, I enter in my password to unencrypt my device (Yes, I've encrypted my device), then suddenly the boot animation stops abruptly and the phone reboots again by itself
I'm currently running on CyanogenMod 10.2.1 ("cm-10.2.1-jfltetmo.zip" precisely), so my automatic next step was to reflash and start over. I thought it would simply delete all of my encrypted data, but it appears I still have my encrypted data (It still asked me to enter my password for decryption after reflashing).
I'm lost. I think I broke my phone. :crying: Is there any way to recover my phone?
I got it.
All I had to do is boot into recovery mode, go into mounts and storage > format /data and /data/media (/sdcard)
From the mouth of Uncle Ben:
With great power, comes great responsibility.
Click to expand...
Click to collapse
First, this phone is converted from C72 to A42 by the seller.
I have enabled encryption and therefore I cannot use the "Fuse wipe data".
It went amok and start bootloop few days ago. I tried cache wipe with simcard and sdcard taken out. It still failed to enter into system UI.
Any idea what went wrong? I have not backed up my data and hopefully avoid hardware reset.
Looking for someone who can help me. TIA.
First of all: My method deletes everything on your phone. But it should work in mostly all cases.
Download this
Extract it, boot phone into bootloader, then run flashall - stock reco.bat and wait until the phone reboots on its own.
Was running the pixel experience rom, have been for a month.. and I had a very strange issue today, the whole phone just froze, I force restarted it, and everytime It would reboot it would just hang/freeze or unlock and display nothing on my screen but the wallpaper.. ended up trying to restore from an old backup I had, but realized it was when I was running an oreo rom.. got stuck in a loop for fastboot, used twrp to re-install this rom, and it was taking forever to boot, at the G logo.. so stupidly instead of having patience and waiting, I rebooted and formatted data, or tried too, (read it somewhere) and its just been hung on that for hours now "formatting data" Dunno what to do.. I should have just waited on the initial boot after re-installing this rom, forgot it took forever.. dunno if should just keep waiting.. or try an flash back stock rom, and re-do everything.. I think my data partition is corrupted, or unmountable.. so not for sure how to proceed.
Format data or wipe data ?? Formatting data will remove encryption and everything will be erased
Wipe data just erases data partition
Try to clean flash once again by wiping system data cache
Here is the issue now.. when I would go to format data, it would just stay stuck on formatting data with ext4 or w/e ... I left it for an hour or more, and nothing.... so decided to use miflash an restore everything. it goes all the way... but never actually says success just still says flashing, even with the green bar full and says finished 200s or something.. the last part of the log always stops after:
"[3:52:43 AM 49c50e2d]:err:writing 'vendor' 2/2...
[3:52:43 AM 49c50e2d]:errKAY [ -0.000s]
[3:52:43 AM 49c50e2d]:err:finished. total time: 23.850s"
so I've let that set for 20 minutes or more, then finally I just manually kick it out of fast boot, and it'll start to boot with MI Logo, and it has the white bar at the bottom, the bar loads all the way then it just hangs there, ive left it over night an its just stuck there
Even now I can fastboot flash a recovery image, and boot into it, but its unable to mount data, missing crypto header.. maybe I should just let the "format data" take its time maybe eventually it will?
Hi guys,
so yesterday from one moment to another, my S4 Mini LTE with Lineage 15.1 (https://forum.xda-developers.com/galaxy-s4-mini/orig-development/rom-lineageos-15-0-s4-mini-t3702272 ) just crashed while I was just using it normally. No response at all, so I removed the battery, which I think wasn't a good idea. After that, firstly nothing worked, no charging, no usual booting and no booting into recovery. Simply the phone didn't do anything.
This morning I managed to resurrect it a little, with removing the battery and pressing the ON button while putting it back in. After like 30 tries it worked.
But now I'm stuck in the Lineage boot screen. I can boot into TWRP again, but it seems to take unusually long. In TWRP it says, my Internal Storage is 0mb. Also it failed to mount data, cache, efs, persist and storage, only system seems to be fine.
I tried Format Data, and changing File System of data and cache, which where solutions I found on google, but nothing seems to have any effect. Also I reflashed TWRP using Odin, but that didn't change anything.
What can I do? I don't believe it is bricked so badly, I can't fix it anymore. I guess it's got something to do with encrypted storage, but the usual solutions won't work.
Many thanks in advance.
Update:
Tried some more things:
Restore Back up -> not working... can't mount /cache, /data, etc.
Flash Stock Recovery through odin -> success in Odin, still no difference.. TWRP remains on the phone
Flash Stock ROM -> success in Odin, but nothing changed
Unbrick through this guide
-> with bootloader -> odin fails cause my bootloader is v2
-> without bootloader -> again success in odin, but nothing changed
I think unless I find some v2 bootloader, it's unfixable.... still appreciate any suggestions though