Database Info

[Q] SGH-i896 bricked?

Hey everyone, today I tried to revert to my original stock rogers firmware via the clockwork recovery backup I made. After booting, it gets passed the i896 page and continues until it says ANDROID in a graphic image. This flashes every once in awhile. But after an hour of just leaving it, it's still in the same cycle. I can boot into recovery but when I try to install a new rom it says:
"E: Can't mount /dev/block/st19
(No such file or directory)
E: Can't mount SYSTEM:
E: Failure at line 2:
copy_dir PACKAGE:system SYSTEM:
Installation aborted"
If I go into the Mounts and Storage Menu it shows that /system isn't mounted and the same error occurs if I try to mount it. If I try to do a restore from either of my clockwork backups it says the MD5 sums don't match.
As I'm fairly knew to android I'm apprehensive to go any further because I think I'll probably make it worse. I'm thinking I'll use Odin, if there aren't any other suggestions, I've just never used it before and don't have windows installed at the moment.
What do you guys think is the best course of action?
Thanks for your help.

Get yourself into download mode and flash to stock using Odin. Then root and install the rom of your choosing (I recomend Assonance)

How to fix 'E: Can't Mount Cache' in CWM

This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.

syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS

dima234 said:
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS
Click to expand...
Click to collapse
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?

meriox said:
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?
Click to expand...
Click to collapse
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.

dima234 said:
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.
Click to expand...
Click to collapse
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.

meriox said:
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.
Click to expand...
Click to collapse
yea getting the same problem here.
cant mount system
cant mount cache
and most of all when install custom ROM. cannot continue since non of those partitions cannot mount properly.
and other errors are flooding the recovery, we have tried Philz, CWM, TWRP. same annoying problems.

Hello,
On another website I found this:
"All worked fine but that like of command in terminal you put there isn't right, i did this
$ su [and then enter]
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32 [and then enter]
# reboot recovery [and then enter]
PS: the $ comes automatically when you start the terminal emulator app; the # comes automatically after you allow the super user [in $ su]
Do consider all the "Spaces" between symbols and paths!"
Has anyone used this method?

syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
Thanks worked for me :good:

bricked
I've got these errors on my htc desire x, I made a backup, after that, I try to flash a new rom, with the steps written in the first post. The result was: after the htc logo, it showed a black screen! I try to restore the backup, but I cant restore!!!!! I've got soft brick, so I take it a service. I hope, they can fix it

[Q] Drive errors reported in TWRP and trying to change to F2FS

I just got a used TF700t 64gb US version and I'm trying to flash it to CROMBI-KK. I was able to get it unlocked and TWRP 2.8.3.0 installed (the latest version as of 12/22/2014). However, every time I boot to recovery, it begins with a serious looking error. The output screen always starts off with this:
Updating partition details...
... done
Full SELinux support is present.
E:Failed to get default contexts and file mode for storage files.
MTP Enabled
No other errors are shown at first and I was able to flash the ROM. I tweaked something and it failed to boot so I went back in to reflash it. The error was still there. I have tried several wipes and changed to F2FS but the same error remains. I don't know if it's related to the error or not, but when I try to install while configured for F2FS, it always ends with another error and no OS installed. I didn't get the exact wording, but something about recursion and that something failed (it's quite vague).
Right now it is back to working, but it had to be on regular EXT4 and data journaling to work. Anyone know if there is any way to remove the storage error? Are there any other options I could try to get F2FS working?

You are only changing /data to f2fs, right?
Try to get the recovery log whenever something fails that shouldn't.
In TWRP: Advanced > Copy log
From PC: adb pull /tmp/recovery.log

berndblb said:
You are only changing /data to f2fs, right?
Try to get the recovery log whenever something fails that shouldn't.
In TWRP: Advanced > Copy log
From PC: adb pull /tmp/recovery.log
Click to expand...
Click to collapse
I was trying to do F2FS on all three available locations (/system, /cache, and /data). I didn't realize that I was only supposed to do it on /data, though when I looked at my older device, that's how it was configured as well.
So the F2FS error is figured out, but then there was the issue of the error in TWRP immediately on loading it. I rebooted my older TF700 into recovery and it did not have the error line. However, I noticed that it was running TWRP 2.8.0.1 and my newer one was running TWRP 2.8.3.0. I upgraded the older device to 2.8.3.0 and, lo and behold, the error appeared. So I'm relieved that the error doesn't seem to be an actual problem with my new device, but I'm curious still on what it means and how to resolve it. Is this something that is just inherently funky with TWRP now, or is there something I can do to configure my device so it will register as TWRP is expecting?

techturtle said:
I was trying to do F2FS on all three available locations (/system, /cache, and /data). I didn't realize that I was only supposed to do it on /data, though when I looked at my older device, that's how it was configured as well.
So the F2FS error is figured out, but then there was the issue of the error in TWRP immediately on loading it. I rebooted my older TF700 into recovery and it did not have the error line. However, I noticed that it was running TWRP 2.8.0.1 and my newer one was running TWRP 2.8.3.0. I upgraded the older device to 2.8.3.0 and, lo and behold, the error appeared. So I'm relieved that the error doesn't seem to be an actual problem with my new device, but I'm curious still on what it means and how to resolve it. Is this something that is just inherently funky with TWRP now, or is there something I can do to configure my device so it will register as TWRP is expecting?
Click to expand...
Click to collapse
It seems to be a bug in TWRP 2.8.3. I just flashed that version (was on 2.8.1 before), flashed data2sd.zip an got the E: Failed to get default context.... error. I am dirty flashing ZOMBi now and got the same error although the flash seems to be going fine.
I'll post the logs in the TWRP thread. Let's see what the experts have to say....

M8 stuck at Blue Android after update to CM14

Hi everyone!
I'm having a problem with my HTC One M8 after updating to cm-14.1-20161130-NIGHTLY-m8.zip. I was waiting for an appointment and playing with my phone when I noticed that an update was available. I really wasn't paying full attention, (e.i I got stupid!), and I applied the update via TWRP. When I installed the update, I got the following error, but it didn't notice it at that time:
##
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/sdcard/cmupdater/cm-14.1-
20161130-NIGHTLY-m8.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1480477704
detected file system ext4 for /dev/block/platform/msm
_sdcc.1/by-name/system
Patching system image unconditionally
E:unknown command [log]
E:unknown command [log]
detected file system ext4 for /dev/block/platform/msm
_sdcc.1/by-name/system
detected file system ext4 for /dev/block/platform/msm
_sdcc.1/by-name/system
script succeeded: result was [1.000000]
Updating partition details...
...done
##
When I rebooted the phone, I was stuck at the blue android. I was able to reboot into developers mode and try to reflash which is when I saw the error warning. I powered off the phone and rebooted again and the phone booted, but it is not detecting the SIM chip or seeing wifi. Many apps are not working and error messages about apps not starting keep popping up, (com.android.phone has stopped, Google Play services keeps stopping, etc.). Some widgets are working, (Bob Clock 3D), but others like Beautiful Weather are not.
I tried to reflash with the previous rom, cm-13.020161010-NIGHTLY-m8, but that one, as well as cm-13.020160301-NIGHTLY-m8, but they just remain at the blue android. I then downloaded cm-14.1-20161201-NIGHTLY-m8 and tried to install that, but I got the same error. I also tried to reinstall Open GApps, both open_gapps-arm-6.0-mini-20160301 for cm-13 and open_gapps-arm-7.1-mini-20161201 for cm-14 with no results. I have also tried wiping the cache and the dalvik.
Does anyone have any suggestions on what I can try next?
Thanks
zog

Not able to flash Stock image with custom Recovery (TWRP 3.1.1.1.)

Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!

You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine