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)
Related
Hi Friends,
I am new to the XDA community and was driven here as a lot of my friends recommended this.
I recently installed the InDroid 4.0 on my Samsung Galaxy I5801 handset. Everything went fine, no problems. After that i wanted to upgrade the version from 4.0 to 4.1, but the upgrade method didn't work.
I would get the following error :- E: Can’t mount /dev/block/mmcblk0 (or NULL) ( No Such file or directory) .
I have searched the forum and trust me, if there was a tool on this website which would tell you how long I have been searching, it would be nothing less than 8 hours straight.
I have read thru the forums about fastbooting and other options.
To begin with, I tried formatting my phone completely, used another SD card but I would get the same error. My phone is rooted but that error seems to keep popping up.
I get the following when I reach my Recovery Screen :-
------------------------------------------------------------------------------------
Android System Recovery
Samsung Recovery Utils – For BML-
Enter : ok key, select
Reboot system now
Apply sdcard:update.zip
Wipe data factory reset
Wipe cache partition
Finding the update package…
E: Can’t mount /dev/block/mmcblk0 (or NULL) ( No Such file or directory)
E: Can’t mount SDCARD:Update.zip. Installation Aborted.
------------------------------------------------------------------------------------
I followed the steps exactly as in the InDroid forum and also, I downloaded the videos off youtube, just in case, but no go.
I am faced with two issues:
1) With this update, my memory card would never show up in the PC.
2) I cannot upgrade the versions.
Is there any way that I can directly go to version 4.4 instead of following the upgrade path?
Is there any way that I can upgrade by resolving this issue.
I am back to my factory Default Installation and the memory card works fine and everything else works fine.
I know that you guys are professionals and busy, but Any help would be Really appreciated. I could just back away to the factory ROM but i don't want my efforts to go waste.
Please Help.
Regards,
Shashank Raj.
Samsung I5801.
I'm quite new to all of this flashing stuff-- sorry if I sound like a complete newbie.
So I'm trying to get CyanogenMod on my Samsung Mesmerize (Galaxy S), though to no avail. I tried to follow the guide on the wiki located at http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide though it's not working. I can't even get CWM Recovery on it.
To get CWM Recovery, I'm following http://forum.xda-developers.com/showthread.php?t=734166 -- it says flash back to a stock kernel first, which I did via Odin and by following http://forum.xda-developers.com/showthread.php?t=881064 (I downloaded the "EC10 Full Froyo Restore Package"... not sure what the difference is between that one and EE19 but it seems to work.)
I'll go over my steps from the beginning, starting from when I'm flashing back the stock kernel on my phone:
Flash back stock kernel (EC10 Full Froyo Restore Package) using Odin (I've also tried flashing the EE19 one)
It starts up after this, however it briefly displays "FOTA wipe failed" in red and "wipe_data failed" in yellow (along with some other stuff too, but no other errors - when I use EE19 these errors occur as well)
It starts up into the default Android system recovery - I choose reboot system now
Root my phone using SuperOneClick ('yes' to install Busybox prompt)
Insert SD card, Download & install ROM Manager from the Market (following this guide which I linked up above)
Select "Flash ClockworkMod Recovery" (Current/Latest Recovery: ClockworkMod 2.5.1.2)
Select "Galaxy S i9000"
Superuser prompt appears, I click accept
ROM Manager freezes for a bit, then displays "Successfully downloaded ClockworkMod recovery!"
Choose "Backup Current ROM" - freezes for a bit, then phone begins to restart... enters default Android Recovery mode:
Install from package... Finding/opening/verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted.
When I reboot and enter the recovery mode by holding volume-power-home,
it displays "E:Can't mount /dev/block/mmcblk0p2 (No such file or directory)" at the bottom.
Also, when I try to "wipe data/factory reset" in the stock Android recovery mode, it gives this error:
E:Can't mount /dev/block/mmcblk0p3 (No such file or directory)
E:install_application_for_customer:Can't mount HIDDENSDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
I also know there's a "Manual Flash Overrride" option in ROM Manager - could I flash CWM Recovery manually and go that route somehow?
My final goal is to get CyanogenMod installed on my Mesmerize, though-- however, I need CWM Recovery to do that. Any ideas as to why CWM Recovery isn't getting installed, and how to fix the mmcblk0p2 error message in recovery mode (and if that's affecting anything)?
Thanks!
MOD EDIT:
FORUM RULES:
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Yes, and i will add ROM manager only works for Mesmerize MTD systems, and CM7 IS MTD. SO, technically you need to be on CM7 already to use ROM manager.
You don't need to use ROM Manager period.
Hello everyone. I'm a new member here so if I forget to mention crucial information needed to get technical support, please let me know.
Surprisingly it all started when my Galaxy Note Pro 12.2 (SM-P900) was low on battery yesterday. I had to go to college so I took my external battery with me and charged it in my backpack. I didn't need my tablet so I left it in there (was working fine before) and I came back to it this morning to find that it had restarted. It was on the glowing blue Samsung logo, but it wouldn't load past that. I tried restarting it and it wouldn't boot past the logo no matter what. So I tried booting into Android System Recovery (Power + Volume UP) to wipe the cache and still, same results. This is where I can see the error "E: failed to mount /efs (Invalid argument)".
I also did the following:
*Download Samsung Kies (both version 3 and the other since each one says it's not supported and to download the other) and try to resolve the issue. Tablet could not be recognized by either version. No fix.
*Download ADB and the official firmware and flash it (adb gives various errors, ex: can't connect. I may be doing the commands wrong as I'm no expert at this). No fix.
*Download Odin in an attempt to flash it, but the first search result in google was a professional-looking website that actually had a trojan-horse for download; had to shut down my PC and run MalwareBytes, Avast! and McAffee to ensure that nothing remained.
I've been at this since morning. I've also looked at other topics and websites about this problem but I can't seem to find a straight-forward solution. Can anyone please help? I desperately need my tablet for work as soon as possible.
Thanks in advance, and please be precise and clear with your answers (because I'm not so good at Android/Linux commands, or rooting or anything that isn't spoon-fed).
Update: Still not working after I tried to apply TWRP 2.8.6.0 (zip) through System Recovery. After finding, opening and verifying the package it gives the following error message:
E: failed to seek in /tmp/sideload/package.zip (Value too large for defined data type), E: signature verification failed, E: failed to mount /efs (Invalid argument).
I should also note that throughout the entire time I used the official firmware, I haven't used any custom ROMs but I'm now open to it since I have to do all this.
Update 2: Downloaded Cyanogenmod Installer and while it was about to install, it detected the device needed to be repaired. My device was in Android System Recovery under the "apply update from ADB" selection, and these errors came up when Cyanogenmod tried to fix it: "E: footer is wrong, E: signature verification failed".
BIG Update (3): I managed to find the legit Odin application and flashed TWRP v2.8.6.0. However, I'm not sure what to do from this point on out. Help?
Hi.
I am in the same situation. Have you found a solution ?
Thanks in advance.
I love the liquidsmooth rom but a few months ago I suddenly couldn't install new updates or any other rom.
I'm using Team Win Recovery Project v2.7.0.0. I've been doing this for years exactly as the instructions say .
This is what it says at the end of installing zip:
Patching system image unconditionally...
Flashing SuperSU...
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/system at /system: Device or resource busy
script succeeded: result was [/system]
Updated partition details...
So then I reboot and it seems ok until I leave wifi and try to use mobile data, then it freaks out (freezing, image contouring, no phone reception). I found that I have to restart my phone in order to turn on mobile data and even then it only works half the time I do that and when it does work it's only while I keep the screen off. If I turn the screen off and go back to it a minute later it freaks out again...
I've scoured the internet trying to find a solution but everything seems to fail...
This is the last thing I tried:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
cmh436 said:
I love the liquidsmooth rom but a few months ago I suddenly couldn't install new updates or any other rom.
I'm using Team Win Recovery Project v2.7.0.0. I've been doing this for years exactly as the instructions say .
This is what it says at the end of installing zip:
Patching system image unconditionally...
Flashing SuperSU...
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/system at /system: Device or resource busy
script succeeded: result was [/system]
Updated partition details...
So then I reboot and it seems ok until I leave wifi and try to use mobile data, then it freaks out (freezing, image contouring, no phone reception). I found that I have to restart my phone in order to turn on mobile data and even then it only works half the time I do that and when it does work it's only while I keep the screen off. If I turn the screen off and go back to it a minute later it freaks out again...
I've scoured the internet trying to find a solution but everything seems to fail...
This is the last thing I tried:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Click to expand...
Click to collapse
I would do a reset with stock recovery.
So I would flash RUU boot to ROM, back to hboot do factory reset.
Then flash custom recovery flash ROM see how it goes.
cmh436 said:
I love the liquidsmooth rom but a few months ago I suddenly couldn't install new updates or any other rom.
I'm using Team Win Recovery Project v2.7.0.0. I've been doing this for years exactly as the instructions say .
This is what it says at the end of installing zip:
Patching system image unconditionally...
Flashing SuperSU...
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/system at /system: Device or resource busy
script succeeded: result was [/system]
Updated partition details...
So then I reboot and it seems ok until I leave wifi and try to use mobile data, then it freaks out (freezing, image contouring, no phone reception). I found that I have to restart my phone in order to turn on mobile data and even then it only works half the time I do that and when it does work it's only while I keep the screen off. If I turn the screen off and go back to it a minute later it freaks out again...
I've scoured the internet trying to find a solution but everything seems to fail...
This is the last thing I tried:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Click to expand...
Click to collapse
Is your firmware up to date?
Sent from my Nexus 6 using Tapatalk
blah
andybones said:
I would do a reset with stock recovery.
So I would flash RUU boot to ROM, back to hboot do factory reset.
Then flash custom recovery flash ROM see how it goes.
Click to expand...
Click to collapse
\
I've been trying to use these directions to do what you said:
[wouldn't let me post a link but it was using DOTTAT files]
The Option 1 didn't work because somehow the "format" option of my sd card has disappeared and I don't have a card reader on my computer.
The second one, I kept trying to run the program and it would just say that my phone battery was less than 30% even though it wasn't.
Do you have better directions?
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