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
Related
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
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....
So, lets start.
I have the mentioned Huawei Mate S, i flashed the TWRP bootloader and just wanted to root my device..
that have i done untill now:
- found a page (cant post the link cause i am new here) to root [search: "huawei-mate-s-root-twrp-recovery-v2-8-7-0/" in google and take the first page to get there (theandroidsoul .com) ]
- downloaded everything mentioned (TWRPand i got the SuperSU-File)
- first i loaded into bootloader, then made a backup of my system.
- then i installed the System again with the SuperSU.zip File
- i tried to boot the system, but it was stuck for 8 hours in the Huawei System Boot Page while i slept
- then i rebooted into the recoverymode of TWRP and restored the system again from the backup, but this time without installing the SuperSU. I could reboot but my phone wasnt rooted, so i tried again:
- this time i just installed the zip-file using the twrp-recoverymode
- didnt work
- and then i think i made a mistake, i tried to do a factory reset but after like 15 minutes i thought it would be stuck and i rebooted
- after the reboot no matter what i did there was always that problem: "E: unable to mount "/cache" "
- i tried a a couple different things and now i am at this point:
-> my android system isnt booting so its stuck in the bootpage
-> i dont have the backup (dont know where it went) anymore so i cant restore with that
-> i cant wipe the /cache cause everytime it says: "E: unable to mount "/cache" "
WHAT CAN I DO? maybe flash a custom rom?
PLEASE HELP, THANK YOU! <3
ccas
edit: phone is listed in pc so i can transfer any files, but its empty, there is only one file called "TWRP"
Flashing a custom ROM may fix it.
If not, I'd try to flash the original firmware. Huawei must have some software available that allows you to do it.
Hi,
I need your help as i can't get my Honor 8 (FRD-L09) unbricked:
1) It worked fine with firmware FRD-L09432B389 (except Bluetooth that won't be activated)
2) I flashed it with Lineage 14.1 using this website:
http://www.cyanogenmods.org/forums/topic/lineage-os-14-1-honor-8-nougat-7-1-rom/
3) It worked well but I got a strange message at bootup: To start Android please enter your password. This is probably due to encryption of prior partition. I made a format Data and wipe Data partition but it didn't helped.
No i still have access to TWRP but i'm unable to flash with any rom:
1) 3-Button force update mode doesn't work (it doesn't go the the update mode, even though dload/update.zip is existing on SD Card)
2) When i Try Unbrick mode from Huawei Multi-Tool i get this error message:
FAILED (remote: error partition error)
FAILED (remote: sparse flash write failure)
I confirm my bootloader is unlocked!
Thanks for your help!
Are you sure that you tried to install the exact dload file of your phone's region?
Bro just try the above post it works 100% .
Hi,
I'm trying to flash through adb sideload. I activated the ADB Sideload in TWRP As well. The transfer worked correctly.
In attachment the log of flash.
I tried to flash these stock roms:
FRD-L09C432B381_update.zip (1,3Gb)
FRD-L09C432B381_update_data_full_hw_eu.zip (1,1Gb)
My Honor 8 is from Europe, meaning these flash should be correct.
In the log i noticed these messages:
failed to mount /data: Device or resource busy
unmount of /system failed: no such volume
unmount of /cust failed: no such volume.
What do you think?
Thanks!
Yes it took approximately 50 seconds each.
For HW EU i got this message: Total xfer: 1,07x
For Update : Total xfer: 1,00x
No it is stuck at blue screen with Honor
When i'm in TWRP, I go to Wipe and Advanced Wipe:
- Dalvik / Art Cache: Invalid Partition Selection (when i click Repair of Change File System)
- Cache: ext4 - 247Mb (0Mb used)
- Data: f2fs - 24662Mb (0Mb used)
- Internal Storage: Invalid Partition Selection
- System: ext4 - 1891Mb (1781Mb used)
- Vendor: ext4 - 579Mb (481Mb used)
- Micro SD Card: vfat 59624Mb (6081Mb used)
Is it normal Internal Storage shows Invalid Partition Selection ?
What should i do after flashing both zip files (with adb sideload) ? Go to eRecovery and connect to Wifi?
Thanks,
Rommco05 said:
I must after flash boot to stock eRecovery and here do factory reset, u have this choice in?
edit:no isn't normal Invalid partion Selection
Click to expand...
Click to collapse
After flashing both zip files the welcome screen is stuck at blue screen with Honor Logo.
From this i went back to TWRP to Flash with Lineage 14.1:
- I firstly got a screen that says encryption is unsuccessful and i need to click to reset phone
- I got a second screen that looks to Recovery Screen and that Reset phones (takes 1-2minutes-
- I have a third screen saying: To start Android, enter your password.
I don't have that password since it is converted from fingerprint i assume.
Can you please details how to do this:
I must after flash boot to stock eRecovery and here do factory reset, u have this choice in?
Thanks!
Phone unbricked??
No Phone still not unbricked.
What i'm trying to do know is:
- Install TWRP 3.1.1.1 by OpenKirinProject on eRecovery partitition (Should i try Recovery Partition ?)
- Install FRD-L09C432B381_update_data_full_hw_eu.zip file
- Install FRD-L09C432B381_update.zip file
- Wipe Cache/Dalvik
-In TWPR, click Reboot - Recovery
- In Recovery, choose wipe data/factory reset + wipe cache partition.
- Reboot fingers crossed
But i still have significant issues:
Failed to mount /cust (Invalid Argument)
Failed to mount /vendor (Invalid Argument)
Failed to mount /product (Invalid Argument)
Any additional help, please do not hesitate!
In my opinion all the issues i have is because partitions that are corrupted i think. Not sure if they are recovered only by installing full flash zip file.
Thanks for the help!
PHONE FINALLY UNBRICKED !
Thanks very much for your help !
I did exactly what i mentioned earlier and it worked like a charm.
I'm not downloading OTA B389 Version and i will afterwards install Lineage 14.1 on the phone.
Any questions, please shoot.
Thanks very much,
PHONE FINALLY UNBRICKED !
Thanks very much for your help !
I did exactly what i mentioned earlier and it worked like a charm.
I'm not downloading OTA B389 Version and i will afterwards install Lineage 14.1 on the phone.
Any questions, please shoot.
Thanks very much,
sebastien_be said:
PHONE FINALLY UNBRICKED !
Thanks very much for your help !
I did exactly what i mentioned earlier and it worked like a charm.
I'm not downloading OTA B389 Version and i will afterwards install Lineage 14.1 on the phone.
Any questions, please shoot.
Thanks very much,
Click to expand...
Click to collapse
Go on
Rommco05 said:
Same what is mentioned in guide in second post, basically
Click to expand...
Click to collapse
Yes but it's not as easy as that for different reasons:
1) First of all thanks for your help and for your post (that explains how to unbrick) but as everyone has is own understanding and knowledge/experience level in these topics, your post lacks precise steps. Example: When you say "Flash firmware for your model" should be: Click install, select your firmware in ZIP format and click Install image. For your level this seems probably obvious but it's not for everyone.
2) Even though, it is not always working. Right now i bricked my phone again by trying to install Lineage 14.1. I just recovered it but it is again multiple steps in TWRP, sometimes clicking there and there, and it works sometimes with chance. I have the feeling that we still don't know 100% sure what to do in which case to have 100% success rate.
Now i have my phone fully working in B389, Bluetooth also.
Does anyone know how to install Lineage 14.1 ? Here is the link for Honor 8:
http://www.cyanogenmods.org/forums/topic/lineage-os-14-1-honor-8-nougat-7-1-rom/
Because they explain:
Wipe data factory reset, Cache partition, Dalvik Cache and Format the System partition.
Again that's not precise:
1) Wipe Data Factory Reset ?? Does that mean:
a) Click Wipe & Swipe to Factory Reset
b) Click Wipe - Click Advanced wipe - Select Data & Swipe to Wipe
2) Cache Partition & Dalvik Cache means : Click Wipe - Click Advanced Wipe - Select Dalvik Cache + Cache & Swipe to Wipe
3) Format the system Partition : Click Wipe, Click Advanced Wipe, Select System, Swipe to Wipe ??
Because i just tried to do it (according to my understanding) and i got bootloop and access to TWRP only.
Thanks for your help.
Hi,
Yes i think you should indeed (if possible of course ). For instance, what was new for me was also the fact 2 flash images were required, one called "update" and one called "region".
I'm trying to install LineageOS and then GAPPS on my Pixel XL from TWRP recovery. I'll try to `Advance Wipe` the `/systems` directory and `Format Data`, but I continue to get multiple errors:
Code:
Failed to mount '/system' (Device or resource busy)
Code:
Failed to mount '/vendor' (Device or resource busy)
And
Code:
Unable to wipe 'System'
Code:
Unable to wipe '/system'
If I just continue with `adb sideload lineageos.zip` most of the time it stops about halfway (PowerShell shows `47%`) through and then TWRP shell shows:
Code:
Installing zip file '/sideload/package.zip'
Step 1/2
Step 2/2
I then try to `sideload` the `gapps.zip` file and get another error saying `/system` doesn't have enough space. I've tried sideloading several different gapps versions including their smallest `pico` zip fie of `91.39 MiB`.
I am able to then boot into LineageOS, but no GAPPS show and I'm not able to run any new apps installed via APK without them crashing.
My assumption is that I need to fully wipe `system` and format it, but I've been trying for two days now and still get the above `(Device or resource busy)` errors. Any help would be much appreciated!
Make sure you have the latest tools.
Latest TWRP for marlin is 3.3.0-0
Latest platform-tools is 29.0.1
Not sure what's the cause of this, but if you want to wipe and start fresh I think the best option is reflash the stock factory image that completely wipes everything and restores everything stock.
Then, you can retry wiping the device using the latest TWRP (currently, marlin is 3.3.1-0, the zip is 3.3.0-0, try just boot it and don't flash the zip), flash LOS and then gapps.
Also, as pointed by @post-mortem, make sure you are using the latest adb version when flashing the factory image, just to avoid any potential issue.
Don't use 3.3.1-0. Try 3.3.0-0. I had the same issue.
Why doesn't TWRP Team provide an answer as to why this happens? It appears to affect everyone with the latest official Pixel ROM.
Twrp is for Android pie and has trouble mounting stock Android 10. They have announced this on their website. This shouldn't matter since you're installing lineage. You don't need to wipe system before installing lineage because it installs into the inactive slot. You need to sideload lineage then reboot into recovery to switch slot's. The instructions are on the lineage website.
Did OP manage to solve this issue?