Can anyone help unbrick my i9506? It will boot to the Samsung logo but then comes up with the message: “Encryption failed. Unable to complete encryption because of interruption. Perform factory data reset …” etc. I have never encrypted the phone and this came out of the blue, though I did delete cache and dalvik cache under TWRP the day before. The phone will boot into TWRP recovery where I tried doing a factory reset and data wipe but nothing works and all I get is “Unable to mount /data, Unable to mount /cache, Unable to mount storage” in TWRP.
I tried flashing a stock rom with Odin (3.07, 3.09, 3.10, 1.85, different USB ports, official samsung cable, different computers) but that also failed, and fastboot doesn’t work either. Looks like a corrupt partition? Is there any work around to this problem, or failing that, can I flash a stock recovery so I can take this in for repair under warranty?
Did the Odin flash work? If it flashed succesfully, then flash the firmware with a .pit file and check re-partition. That should fix it.
Tired flashing numerous times with Odin but all failed. Tried with .pit file but also failed.
OK, I’m just an old noob, but after three days of searching, downloading and flashing, I am ready to give up. I found a number of references to ‘Encryption failed’ but few answers. The constant mmc_write fail in Downloading when flashing suggests, according to some, a hardware failure with the mmc chip, and Knox also gets a mention as a cause. So it looks like a hardware and Samsung issue, and the only easy fixes reported come from those who get a replacement motherboard under warranty.
But I can still boot into twrp recovery, which suggests a soft brick, and some users experiencing similar issues have revived their phones. My numerous attempts to flash stock rom, stock recovery, CWD etc with Odin failed. In trwp, data and cache will not mount, nor will data mount through adb shell. Looks like a partition issue, though all partitions appear to exist under dev/block/ and flashing the i9506 pit file in Odin does nothing. Tried to wipe data, cache, system etc and do a manual reformat of /data (userdata partition 26 in i9506) through adb but all failed. Tried superwipe (doesn’t work), and while fastboot erase then rom flashing works for some to overcome the dreaded ‘Unable to mount /data failed’, Samsung phones don’t support fastboot. Some users report success through CWD recovery, the main problem solver, and flashing older ICS roms (I’m on 5.01 but also d tried 4.4.2 and 4.3 without success). Twrp crops up as a real suspect for many users – me too - but my attempts to get rid of it and flash either stock recovery or CWD/Philz failed.
So, I’ll try to get a hardware replacement for my phone, but given I’ve tripped Knox when rooting, I don’t fancy my chances. My conclusions, apart from don’t mess with your phone, are avoid Samsung and Knox, and twrp sucks but, hey … who knows?
Follow up. Got it fixed under warranty. They replaced the PCB (motherboard). Looks like I wasted all those hours trying to get it up and running, and it was hardware after all.
Related
I'm trying to restore this Galaxy S5 back to stock but allow me to give some back story.
It was meant to be simple, I have the correct stock recovery files from samfirmware. I load up Odin and begin to flash it as routine. I watch as it goes through all the steps and checks out just fine, but right at the end when it flashes the Modem.bin it fails.
So I attempt to flash a modem file on its on first. Same thing, immediately fails. Saying auth fail in Odin.
Then I flash Philz onto the phone so I can wipe Partition cache and Dalvik to try again. When I was in there, I went to advance > and unmount /Firmware-Modem but all I get is ERROR MOUNTING /FIRMWARE-MODEM
I don't know if it's possible that it's hardware faulty [failing NAND as an example. The phone has some other strange quirks going on with it too]
Any suggestions would be amazing. I don't know where to go from here at all seeing as that seems to be the road block.
Custom TW ROM Lollipop Galaxy S5 SM-G900F: multiple high-impact issues
In last 24hrs I managed to get away from several hard issues, so, I thought it might be good idea to share and start separate thread, as I found none to cover all that in the same time. It all started with no baseband - No SIM card error. For the starters no separate ODIN baseband flash turned out to help. One thing leading to another and I managed to soft brick the device. Trying this and that, I was finally struck with: Encryption failed, unable to complete encryption, reset phone to factory settings.
ODIN: reflash Stock: no ROM from SamFirmware for my country and carrier managed to boot up device, although full flash was successful. Turning on 'Nand Erase All' and 'Phone Bootloader Update' haven't helped, either.
ODIN: reflash PIT: no PIT file flashing has solved the problem
TWRP Recovery: Data/factory reset: no go
TWRP Recovery: /data, /system, /cache: no go - but there was this message that /data cannot be mounted and no crypto data can be found.
TWRP Recovery: Flash CyanogenMod: Success! - it is great ROM indeed, but there is no good camera for AOSP, so let's move on.
TWRP Recovery: Flash Custom TW ROM: Struck with looped encryption failed error.
TWRP Recovery: Wipe > Advanced Wipe > Repair or Change File System: /data was somehow, somewhere formatted as f2fs - changed it to ext4. Flash TW ROM, wait couple of minutes: SUCCESS!. (TWRP 3.0.1.0)
Hey there
Hello, i have the same "encryption failed" error on my s5. It has been a paper weight for a month now.
It started a few days after i updated to lollypop. I have never tried to mod the phone in the slightest.
Any help would be greatly appreciated!
Hello
I have a Galaxy Tab 4 7.0 SM-T230 that is not booting correctly.
I got it in a non working condition, kept rebooting when turned on.
I reflashed the stock ROM using Odin after installing TWRP but this would results in the tablet getting to the choose your language screen then restarting itself.
I tried the below versions of the stock ROM but they all have the same result:
T230XXU0ANG3_T230SER0ANG2_T230XXU0ANG3_HOME.tar.md 5
T230XXU0ANJ4_T230BTU0ANJ2_T230XXU0ANJ4_HOME.tar.md 5
T230XXU0ANK3_T230BSE0ANK1_T230XXU0ANK3_HOME.tar.md 5
StockRoms-Series_T230(NU)+V1.6.3
The custom ROMs I have tried get stuck on their startup/boot screen.
I have also tried:
Wiping all david, cache, data, system, internal.
Re partitioning using DEGASWIFI_HIDDEN_100M.pit
Using Odin 3.9 and 3.12 with the md5 file in the AP section
TWRP openrecovery-twrp-2.8.0.1-degas and TRWP_2.8.7.0_EUR_VERSION
The custom ROMs cm-v13-degaswifi-kids-unofficial-20170713, ACHERON_ROM_V2.3.5_SM_T230_NU and [KK] [SM-T231/T230/NU] + Android 5.0 Lollipop Material Design
Combinations of reflashing, factory reseting, cache wiping.
Kies recovery but it will not maintain a connection, keeps disconnecting the tablet
Fixing partitions in TWRP
The only thing left to do as far as I am aware is to NAND Erase all but I am not sure if recovering after doing that is feasible.
Update: Tried Nand erasing, then re partitioning and reflashing of stock firmware, no change.
Tried EFS clear and Phone bootloader update.
Now the partitions appear to be broken and re partitioning with the pit file and reflashing does not fix it, cannot mount data or system.
Any suggestions to resolve this issue?
Thank you
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
skorpien said:
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
ashyx said:
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
Click to expand...
Click to collapse
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
skorpien said:
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
Click to expand...
Click to collapse
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
ashyx said:
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
Click to expand...
Click to collapse
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
skorpien said:
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
Click to expand...
Click to collapse
Did you back up the efs partition with twrp?
If so try restoring it.
ashyx said:
Did you back up the efs partition with twrp?
If so try restoring it.
Click to expand...
Click to collapse
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
skorpien said:
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
Click to expand...
Click to collapse
Don't restore everything just EFS No need to keep wiping dalvik it serves no purpose when formatting or wiping the data partition.
Also FORMAT not wipe the data partition (note this wipes internal storage)
If it still doesn't boot install the combo firmware. Let it boot, factory reset from settings then reboot to download mode and install the stock firmware again.
Hi,
My s7 got a little bit strange so there very heavy lags.
After this I decided to try a cache wipe.
Aftrerwards I thought i going on the over to the factory reset and this will fix everything.
BUT still it didn´t worked and the reset failed
The output looks like this:
E:format_volume: make ext4 failed on /devblpck/platform/155a0000ufs/by-name/US
Data wipe failed!
Afterwards I reinstalled the OS several times with ODIN.
Still stuck in a Bootloop and a factory reset brings up the same error.
Even a nand erase aswell as a repartition with the correct pit file leeds to the same error.
At the moment I guess the phone is dead and there is no more help.
Or am I wrong and there is a way to bring this back to live?
How did you wipe the phone? You can wipe with twrp and also with adb.
I wiped it with the standard recovery delivered from the Phone.
I tried to flash it a couple of times with odin but still ran in to this error..
Try wipe it with adb. Can you boot into stock recovery? If you cant wipe, make sure you are flashing the correct csc for your phone. So it has to be explicitly for your region and network operator.