Failed encryption, the phone doesn't boot up anymore - Xiaomi Redmi 2 Questions & Answers

Hello. This morning my phone was off (2014813, 2 GB RAM, 16 GB storage), and I turned it on. When it booted up, it greeted me with a text, saying something like "the encryption was unsuccesful, so all your data is now inaccessible, you have to reset the device". now the problem is that I've NEVER wanted to do a full device encryption, and now the recovery was unable to mount the partitions, and even though I can access fastboot, I can't flash any image with MiFlash, beacuse it says "failed to write partition". If I power on the device now, it gets to the boot animation, and it never goes through that, it constantly shows the boot animation.

I'm able to boot a recovery from fastboot, but the recovery can't mount /data and /cache, but it can mount /system. So I can't format /data and /cache now. My phone is currently unusable because of this

I'm having this exact same problem. Where you able to fix it? I have tried countless method but nothing seems to be working
I'm afraid that the internal storage might have died.

gabika1941 said:
Hello. This morning my phone was off (2014813, 2 GB RAM, 16 GB storage), and I turned it on. When it booted up, it greeted me with a text, saying something like "the encryption was unsuccesful, so all your data is now inaccessible, you have to reset the device". now the problem is that I've NEVER wanted to do a full device encryption, and now the recovery was unable to mount the partitions, and even though I can access fastboot, I can't flash any image with MiFlash, beacuse it says "failed to write partition". If I power on the device now, it gets to the boot animation, and it never goes through that, it constantly shows the boot animation.
Click to expand...
Click to collapse
Did you flashed custom ROM too many times?
This may be the cause of Storage failure..
Around How much time did you flashed your device..
Any rough estimate..?

Related

/data error format and mounting

Suddenly my tablet went all apps to "Force close" so I immediately reboot my tablet...When I it boots it takes me hours and hours to boot and it doesn't work..
I'm using V8 bootloader when I go to CWM and do some formatting I notice that my /data couldn't perform a format or mount it then when I go to install .zip my internal storage couldn't opened as it recognizes it as /sdcard error mount. Is there a way to put those back again? I'm worried that I couldn't use my tablet anymore

[Q] Stuck on recovery after factory reset

I have a nexus 7 (2012) wi-fi model.
I loaded the factory image for 5.02 from google using their instructions and the device started up afterwords just fine. But using it with 5.02, it kept getting stuck/frozen and I had to hard-restart it a lot. So I decided to do a factory reset. I went into stock recovery and I selected factory reset. It formatted /data and /cache but after that it could not mount /cache or anything in it. Eventually it restarted back into recovery on its own and re-formatted /data and /cache but again gave the same errors and landed me on the recovery menu. Trying to "reboot system now" or "reboot to bootloader" just shuts it down. I then need to long press power to start it back up, but when it does, it again formats /data and /cache, goes through the errors and lands me in the recovery menu. Trying to get to the bootloader by pressing power and volume down results in the same (loads recovery where it formats /data and /cache and goes through the errors). And with no bootloader I can't even reflash anything.
Please help

Bricked Z00LD, all partition sizes are 0MB size

I had this phone bricked for almost 1-2 months, now I wanted to see if I can get it back to work, I'll list here the extensive list of thing that I tryed before finding this weird problem:
All I remember from 2 months ago is that I had the pre-rooted rom 21.40.1220.1998, had a no signal problem, tried rebooting the phone and it started bootlooping, bootloader was already unlocked when this happened.
I tryed varius flashes from stock recovery, TWRP, even tried installing lineage, but I don't recall the exact steps that I tried at that time. I'm sure that were a lot.
Now, today, booted phone, it started on fastboot mode, tried booting recovery, no way. Flashed stock recovery package found on internet, got stock recovery back.
Then I started doing as follows:
Flashing the oldest stock rom package I had, installation stuck on opening update package for 1 hour, removed battery from the device
tried downloading the package same as the one maked on the first line of the recovery screen, flashed without errors, rebooted: bootloop.
tried flashing a more recent recovery and boot img from fast boot, making sure to do a fastboot erase of both partitions before. recovery doesn't start.
Tried installing TWRP recovery, and rebooting, no way, phone boots on fastboot.
done a "fastboot boot twrprecovery.img" to wipe from there the partitions. Got a mount error for each partition.
I went to the partition repair screen for system, and then I noticed the partition size was 0MB. WTF!
Checked all other partitions, all 0MB size, 0MB used, 0MB free. except for the cahce one, it is 27MB and empty.
Now, I'm pretty sure I need to repartion theese partions, but I don't know the original size. Someone here does have the partion size for system and data (and I gues also recovery?)?
There is any other way to fix this problem and get the phone back to work? I literally spend all the day trying every solution I found on internet.
motherboard is faulty
R3DC0D3 said:
I had this phone bricked for almost 1-2 months, now I wanted to see if I can get it back to work, I'll list here the extensive list of thing that I tryed before finding this weird problem:
All I remember from 2 months ago is that I had the pre-rooted rom 21.40.1220.1998, had a no signal problem, tried rebooting the phone and it started bootlooping, bootloader was already unlocked when this happened.
I tryed varius flashes from stock recovery, TWRP, even tried installing lineage, but I don't recall the exact steps that I tried at that time. I'm sure that were a lot.
Now, today, booted phone, it started on fastboot mode, tried booting recovery, no way. Flashed stock recovery package found on internet, got stock recovery back.
Then I started doing as follows:
Flashing the oldest stock rom package I had, installation stuck on opening update package for 1 hour, removed battery from the device
tried downloading the package same as the one maked on the first line of the recovery screen, flashed without errors, rebooted: bootloop.
tried flashing a more recent recovery and boot img from fast boot, making sure to do a fastboot erase of both partitions before. recovery doesn't start.
Tried installing TWRP recovery, and rebooting, no way, phone boots on fastboot.
done a "fastboot boot twrprecovery.img" to wipe from there the partitions. Got a mount error for each partition.
I went to the partition repair screen for system, and then I noticed the partition size was 0MB. WTF!
Checked all other partitions, all 0MB size, 0MB used, 0MB free. except for the cahce one, it is 27MB and empty.
Now, I'm pretty sure I need to repartion theese partions, but I don't know the original size. Someone here does have the partion size for system and data (and I gues also recovery?)?
There is any other way to fix this problem and get the phone back to work? I literally spend all the day trying every solution I found on internet.
Click to expand...
Click to collapse
If all partition showing 0 Mb in twrp and u cant change extention repair or format and reboot your phone phone motherboard is faulty
better buy new phone.

Failed to mount any partition / Kernel Panic / boot loop / Galaxy S5 klte

Phone was running stock os. I rebooted my phone and it's now stuck in a boot loop. I tried to reinstall it through Smart Switch and it's still stuck in a boot loop.
After the reinstall it goes to "Installing system updates" and almost right after it stops and shows "Erasing" for a second. It then reboots a few times and it usually goes to the Kernel Panic error but it has also gone to Manual Mode once to try and install the updates but then it fails to mount any partition.
I've tried installing Lineage OS (I used it before I went back to stock os) through TWRP and I also got the same errors. I was unable to mount any partitions and left the phone without a battery for a few a day.
When I tried again just now I was able to mount the partitions but installing Lineage OS or stock OS was still not possible and it gave me the same errors again.
Is there anything I can do to fix this?
First error after boot loops: imgur.com/a/ZOTfR
Errors on TWRP: imgur.com/a/qYqsY
Manual install in recovery: imgur.com/a/YHeyS
Another error: imgur.com/a/xPHdm
EDIT: After trying for three days, it suddenly booted. I can boot to the OS but the phone still crashes and boot loops every time. If I go to recovery and wipe cache it will boot again. What can I do to stop it from crashing and going back to boot loops?

Phone only boots with factory mode. I did something wrong.

I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this

Categories

Resources