I rooted my Xperia M4 Aqua E2306 and installed TWRP according to this tutorial: https://forum.xda-developers.com/m4-aqua/general/root-e2306-m4-aqua-guide-t3270521
Everything went fine, but after booting into TWRP and flashing a zip file, the error "E: unable to mount '/firmware'", appeared in the output in red letters, even though it said the flash was successful at the end, and the phone got stuck infinitely on the blue boot animation.
*UPDATE*: It turns out that the there was something wrong with the zip files that I was flashing, I found one after flashing which the phone booted as normal, even though the error still appeared in the TWRP output.
Related
Hello everybody!
Well...Like the title says, my phone (HDC S4 galaxy legend) isnt responding at all. I was using my phone when a message told me that sd card was with errors and asked me if i want to fomat. I´ve selected yes and the nighmare starts... Now when i power on the phone shows the logo and get stucks there... well, i thought that maybe recovey will fix this.. i have entered recovery and the first warnings appeared "e: cant mount sd card". I have tried format all the options, make wipes and stills appears message e: cant mount emmc or e: cant mount cache... i have tried to install the stock rom from the sd card and apparently shows that is installing, but then reboots and it get stuck in logo screen again. Another thing is that when i connect the phone to my pc, it doesnt recognize it, not even my PC make a sound when i connect the phone. I have tried to reflash with flash tools but it doesnt work cause the phone is not detected, is like a brick.. well.. then i have tried to make partition from cwm and nothing works and it doesnt installs the rom.
Now i can only access to recovey but nothing else, please someone help me :crying: :crying:
No one can help?
No one can help?
I have detected the problem. My internal card is bad formated, because it says can't mount emmc / data .... i have tried whith aroma wiper but i still cant recover the original partition (ext4). Someone have a tool to get back to my old partition????
Hi All,
I have an HTC One M7. Yesterday I unlocked the bootloader and rooted the phone. Then I tried to install the Android 4.4 on the phone by loading the downloaded zip file on the internal storage and ran it through the fastboot recovery option. It went through the installation and then when it all finished the phone refused to reboot. It only remains with the HTC logo with the white background.
I tried to go through the installation again once more and the same happened. Now I tried to repeat it again to find the message E: Cant mount/sdcard.
Now I am left with a phone which cannot boot and an sd card that cannot mount.
Please help me how to solve the problem.
Thanks,
Sachin
Hi there.
I tried to update a new ROM for my Lenovo A390. But sth was wrong with the phone I suppose. Firstly when I tried to start up with power button and vol+, firstly I got Android human logo with sth twisting next to its belly Then dead android humand with red exclamation mark showed up over. And nothing else happened.
When I was trying to flash custom room with Flash tool, the phone never answered to the 'call' from flash tool (after clicking 'Download' and connecting phone to PC - nothing happens ). So nothing could be done with Flash tool.
The next idea: I found some tips to use ADB and Fastboot. I had boot.img downloaded. It comes from 'A390_AllegroROM_v0.4a_SPFT'.
Then it went like this (in command prompt):
1.adb reboot-bootloader
2.fastboot flash boot boot.img
3. fastboot reboot.
answer for p.2 was OK, OK,
after p.3 as well
Now when try to switch phone on. It shows only lenovo logo and hangs up.
Is there a chance to get the phone working again?
After all this I discovered than when red ex. mark is being showed I can push power button and then I suppose recovery mode is shown?. But weird thing is I can not navigate through it. First option is set. It looks like:
Android system recovery <3e>
Android system recovery utility
Reboot system now(selected)
Apply sdcard: update.zip
Wipe data factory reset
Wipe cache Partition
(and below)
No .zip file in sdcard
So next idea was looking for 'lenovo a390 stock rom update.zip' file . I managed find sth (Lenovo_A390_Miui_Update.zip -> I changed to update.zip). I put it in root of sdcard, thinking that phone need this update.zip to do sth . Indeed, after switching into recovery mode (power + vol+) recovery mode looked similar but instead of 'No .zip file in sdcard' there was a few lines more:
Finding update package...
Opening update package...
Veryfing update package...
E: signature verification failed
Factory update failed.
Any suggestions? Do you think there is a chance to get the phone recovered ?
Hello everyone, I have had my moto g 2 for almost a year now and a few weeks ago I managed to finally root my device. Its been working fine, exactly how I wanted it to, until I did something I don't understand? I wanted to change my boot animation and I heard the using the jRummy's app it was as easy as clicking a few things. so I downloaded the app but instead of downloading an animation from the app I downloaded it from androidbootanimations.com . I managed to install the boot animation (PlayStation 2 for the feels) and I turned my phone off after it had completed and it works, the boot animation works but it loops forever (I turn my phone on and my "warning bootloader unlocked" message comes on and then my boot animation comes on and then the whole process repeats) I have tried rebooting my phone from fastboot mode (Power key and Volume Down) and I have also tried wiping cahe partition and wiping all user data but the boot animation still loops and no matter what I try it will not change. Any help would be greatly appreciated.
*Update*
I have downloaded a toolkit for my phone found on the forums and I have managed to persuade my phone to recognize the .zip file in recovery mode in the "apply update from SD card" section. However, when I attempt to install the .zip file it says installation aborted. I have searched the forums for relevant information but haven't found anything.
On my screen right now it says:
-- Install /sdcard/Toolkit.zip.zip ...
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted.
I am unsure how to adb sideload but have tried some methods found on the internet and it keeps saying that "adb is not recognised as an internal or external command" . I have a stock recovery and a stock rom, boot loader unlocked and rooted. I have lots of zip files (cyanogenmod, 5.0.2 original software, CWM recovery .zip file) but these all say the same thing, any help would again be greatly appreciated and any information you need I will post.
Hi All
I have samsung A5 2017. When i start my phone it shows no command and it continues to restart after 1 minute.
When i try to open recovery mode i get error "fail to open recovery_cause(No such file or directory)". I have also tried combination of key power and volume up but not getting recovery mode. I think it has been deleted or something else. I am also unable to load firmware.
I also tried to install twrp with odin 3.13 but get error unable to install frp locked.
Please tell me solution how can i get back recovery mode so that i can install firmware.
Please help me for this.
Hey there,
I have a similar issue and I can see your post dates back to 2020. Have you ever found a way?
I'm very curious about solving the issue on mine (I can't reboot at all, can't even access the reboot after getting the "no command" message. If you have any clue on how you accessed reboot mode and can be kind enough to share, this would be really appreciated )
I know this is an old thread, but did you find a solution?
On an unlocked J6, after flashing the stock rom, although I can open recovery, I get the same message. The options I tried (both reboot options, both wipe options, power off) work. I went ahead and installed twrp through odin, which passed, but when I boot into recovery, it boots into samsung recovery (with the same message) and not twrp.
I'm guessing the twrp problem is related to the error message.