Hi guys !
I tried to install Lineage OS 17.1 on my Xperia Z3 compact and everything went well until I installed the openGapps (before reboot like tutorial said). I'm now stuck on the recovery screen where this message appears :
"Can't load Android system. Your data may be corrupt".
as well as the following error:
"E: Failed to bind mount /mtn/staging/emulated/media/0 to /storage/emulated: No such file directory"
I can "Try again" or "Factory Data reset" but neither option works! In both cases I'm stuck here again. I can't even turn off the phone or reboot via adb shell either since it is now recognized as "unauthorized".
I read a lot of topics but I have not find an answer.
Can it be an hard brick ? Please help. Thx
Try reinstalling stock ROM using Flashtool.
Related
Hello everybody,
first of all: congratulations for this helpful and amazing forum. I love reading and testing the roms which are offered here.
I just tried the Hybrid v 5.0 rom - the best i ever tested. Everything was smoothie and very harmonic.
Unfortunately it was not possible to write emails and to connect with Samsung Kies.
So i decided to use the known 2.3.4 version which works satisfiying.
To prepare the phone i made a wipe data/factory reset.
After reseting the phone shows me - when turned on and booting - the logo of Galaxian Kernel and the blue "loading beam" with the notice "is loading now."
But it doesnt quit loading.
The cwm shows me:
"E: can't mount /cache/recovery/command
E: unknown volume for path [/cache/recovery/log]
E: can't mount /cache recovery/log
E: can't open /cache/recovery/log
E: unknown volume for path [cache/recovery/last_log]
....
"
Maybe some important datas are erased?
I really don't know what to do now.
Could you please give me some helpful advices (please use the easiest words because i'm no expert...) ?
Greetings from Germany
dennish90 said:
Hello everybody,
first of all: congratulations for this helpful and amazing forum. I love reading and testing the roms which are offered here.
I just tried the Hybrid v 5.0 rom - the best i ever tested. Everything was smoothie and very harmonic.
Unfortunately it was not possible to write emails and to connect with Samsung Kies.
So i decided to use the known 2.3.4 version which works satisfiying.
To prepare the phone i made a wipe data/factory reset.
After reseting the phone shows me - when turned on and booting - the logo of Galaxian Kernel and the blue "loading beam" with the notice "is loading now."
But it doesnt quit loading.
The cwm shows me:
"E: can't mount /cache/recovery/command
E: unknown volume for path [/cache/recovery/log]
E: can't mount /cache recovery/log
E: can't open /cache/recovery/log
E: unknown volume for path [cache/recovery/last_log]
....
"
Maybe some important datas are erased?
I really don't know what to do now.
Could you please give me some helpful advices (please use the easiest words because i'm no expert...) ?
Greetings from Germany
Click to expand...
Click to collapse
For connecting kies you just have to install one patch, it will connect.
Regarding resetting, some files i deleted for utilizing space, which required for factory reset thats why you getting that.
let me explain why i delete that files, see when someone switch ROM ever developer want that user do fresh install but usualy people are lazy so they simply flash rom on other ROM, by deleting that files i conform that if someone want to change ROM then he had to flash first stock rom then other ROM so atleast he didnt got error or didnt able to claim that he coming from that ROM and so he getting this error.
btw for both issue why didnt u asked for patch, its easy task for me to make cwm for that and you able to connect kies and able to do factory reset.
Thank you very much for your fast answer.
i didn't thought about asking, sorry..
That's right. Before flashing your great rom i used the clear 2.3.4 firmware. I did the whole procedure as described here. Use a stock rom and than the other rom.
What could i do right now?
My phone doesn's start. "is loading now... " is written under the logo of Galaxian Kernel. The phone doesn't boot, isn't known by the PC, so i don't know what to do....
Boot to recovery and try wipe almost everything you can, factory reset, cache, dalvik-cache.
I remember one firmware gave me some errors about mounting and wiping stuff always fixed it.
I tried as you proposed but following message appears:
E: unknown volume for path [/data]
...
E: Unable process volume! Skipping...
Checking /cache...
Doesn't that mean that the necessary datas aren't there?
After wiping of all proposed things i tried to restart, but the blue beam under Galaxian still stops when it almost reached the end.
The main problem was Kies.
Phone couldn't be connected, so i couldn't fix the problem.
I just had to update the drivers so that the PC could connect to my little friend. Now it works
Thanks a lot for your help!!
Hi,
I've got the exact same problem.
Tried to flash Galaxian over Odin because my phone was in a boot loop. Then it just stuck when the Galaxian kernel "is now loading" screen appeared.
I can access Recovery and wiped data aswell as cache partition- then I just tried to flash Galaxian a second time with Odin but I have the same problem with the "is now loading" screen now.
Plus I updated Kies drivers.
What can I do? Im really not that experienced but I really NEED my phone!
Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.
Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031
hi, maybe any1 has already found a solution?
dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!
I've bought a used Moto G 2014 XT1068 with a software bug trusting that i can get it to work again.
It shows the message "Warning Bootloader Unlocked". So i activated AP fastboot mode by holding PowerButton and VolDown. Then I flashed TWRP_2.8.0.1_Titan_v2, TWRP2.7.1.1-titan-motog-2014 and twrp-2.8.6.0-titan via ADB but it none of them is starting when i select the recovery button in fastboot mode. Instead of Teamwin logo it goes to the laying android with red triangle.
Then i tried to boot the recovery.img via ADB with "fastboot boot XXX.img" and then the Teamwin logo arises but it stucked with any TWRP i used.
Then i tried to use CWM_Touch_Titan_v2.img in the same way and it worked (only with ADB command again). So i wanted to wipe all to install a new ROM but then it stucked while it says: Formatting /data...
When i try to install a ROM by choosing the .zip-file form /external_sd it seems to work but a few seconds later the message is:
PhilZ Touch 6
Clockworkmod v6.0.4.7
-- installing: /external_sd/Stock_XT1068_22.21.28-ROM.zip
Finding update package...
Opening update package...
installing update...
>>> XT1068 Stock Lollipop Firmware [22.21.28] <<<
Installing Android
Please wait...
symlink: no of symlinks failed = 1
E: Error in /external_sd/Stock_XT1068_22.21.28-ROM.zip
(Status 7)
Installation aborted.
E: cannot write to /sdcard/clockworkmod/.last_install_patch
press any key to continue
Click to expand...
Click to collapse
I don't know what to do anymore
nilsxvx said:
I've bought a used Moto G 2014 XT1068 with a software bug trusting that i can get it to work again.
It shows the message "Warning Bootloader Unlocked". So i activated AP fastboot mode by holding PowerButton and VolDown. Then I flashed TWRP_2.8.0.1_Titan_v2, TWRP2.7.1.1-titan-motog-2014 and twrp-2.8.6.0-titan via ADB but it none of them is starting when i select the recovery button in fastboot mode. Instead of Teamwin logo it goes to the laying android with red triangle.
Then i tried to boot the recovery.img via ADB with "fastboot boot XXX.img" and then the Teamwin logo arises but it stucked with any TWRP i used.
Then i tried to use CWM_Touch_Titan_v2.img in the same way and it worked (only with ADB command again). So i wanted to wipe all to install a new ROM but then it stucked while it says: Formatting /data...
When i try to install a ROM by choosing the .zip-file form /external_sd it seems to work but a few seconds later the message is:
I don't know what to do anymore
Click to expand...
Click to collapse
Try flashing using twrp. Some roms don't flash properly with cwm , connect ur phone to ur PC, enter bootloader mode, and open command window(shift + right click) from ur adb folder (place twrp 2.8.6 img in that folder, rename it as twrp ,remove the 2.8.6 n img ) and enter, adb devices (in cmd window) , if it shows connected, enter fastboot flash recovery twrp.img , then unplug and select recovery from bootloader menu. Take backup of rom, n wipe system, data and cache and flash rom, gapps n supersu.
Hope this helps, pm me if u need help.
Sent from my Moto G 2014 using Tapatalk
This is true, i had this same problem ,i rename as twrp , no 2.8.6 .img etc.. twrp flashed.
It worked now. I couldn't start twrp by selecting recovery from bootloader menu but i started twrp with ADB via "fastboot boot twrp". It showed just the teamwin logo first for about 15 minutes but then it started twrp. So i pressed the log button to see why it took so long. There were hundreds of red messages.
The Message is always like: "E: Unable to stat '/data/..."
I tried to wipe my data and cache. Dalvik cache und cache worked fine but when it comes to data there are always the messages "E: Unable to stat '/data/..."
I get the the same messages when i try to install a ROM.
Is it possible that my internal storage is broken? :crying:
Getting Failed to clear BCB message: failed to open /dev/block/boot/device/by-name/misc: No such file or directory after phone crash​
cant solve this please help
tried edl recovery flashed well but didnt solve problem
i have unlocked the bootloader and flashed many raw firmware didnt solved problem
flashed twrp sucessfully but cant mount storage intenal storage 0mb and cant swipe anything
get this message everytime in recovery
Getting Failed to clear BCB message: failed to open /dev/block/boot/device/by-name/misc: No such file or directory after phone crash​
please help
I have no idea it helps, I had my phone crash on me and me trying my old-and-tried flashing etc. I did not have such BCB message, but it sounds like there is an issue with the partitions or partitioning.
There are nice YouTube videos at least that show how to flash the stock ROM (not giving link here for advertising etc).
it boils down to (FIRST get your data off the phone as you are going to lose this)
- TWRP being bootable
- in TWRP: factory reset, wipe data
- flash stock ROM twice: to partition A and after reboot to TWRP, to partition B. I do not know why this needs to be done, love to learn it by myself.
- flash without wiping a custom recovery if wanted.
- restore your data
Dear guys,
I'm in a situation where I don't know what's best to do, honestly I was left with android 11 where everything was much simpler.
my xiaomi started from OEM miui 13 on which I installed twrp 3.7 with the " Onekey inject TWRP " method, I understood that the method was wrong with android 12 but the phone worked (in recovery mode it did not read the touch).
I loaded the same twrp from fastboot mode, I do a backup of everything (copied to the computer), and trying to install miui.eu, but the phone gave me the following "error "ERROR: 1 / can not mount system".
I tried with the twrp by skkk, launched from fastboot mode, I started the dirty installation of the miui.eu and when finish to install I pressed "Install Recovery Ramdisk".
I restart the phone but after two restarts it returns to recovery, i thought the problem was the dirty installation, so i went to "format data".
From this moment the phone restarts only in recovery, the phone memory is encrypted and cannot find any content (the phone has no password set), connecting it to the computer I cannot copy any content but it is read from fastboot mode.
The errors that appear on the phone are "Failed to mount '/system_ext' '/product' '/vendor' '/odm' (Invalid argument)"
How should you continue? I have no problem to losing any data.
do you recommend to flash a fastboot rom with Miflash?
Thanks a lot