Guys
I need help with my S3
Device can't boot..
Samsung Logo loop...
E:failed to mount /efs (Invalid argument)
# Manual Mode #
-- Appling Multi-CSC...
Applied the CSC-code : Unknow
Succefuly applied multi-CSC.
Where does the error message come from?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
kar3ka said:
Guys
I need help with my S3
Device can't boot..
Samsung Logo loop...
E:failed to mount /efs (Invalid argument)
# Manual Mode #
-- Appling Multi-CSC...
Applied the CSC-code : Unknow
Succefuly applied multi-CSC.
Click to expand...
Click to collapse
Thanks to BaDaB!ng505
Must odin back to original rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drivedevice must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device*when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)reboot in recovery wipedata factory reset...done
factorymode: http://forum.xda-developers.com/attachment.php?attachmentid=1772304&d=1362190578
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Dont Think About What To Do Just Hit The THANK Button
---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------
But I didnt find for the s3 I am going do not download for the n8000
Dont Think About What To Do Just Hit The THANK Button
big thanks !!!
problem solved
kar3ka said:
big thanks !!!
problem solved
Click to expand...
Click to collapse
You are welcome I am here to help you.
I am not asking for Donations to help you find solutions I am just asking for a little click on the Thanks Button
hi,
I can't get pass the last command to mount it. it says can't find /dev/block/mmcblk0p3 in /etc/fstab
any ideas?
very think, unbridled my sgs3.
dear friend, my phone was bricked and the only tutorial that really worked was this here. but adbshell used to enter another command was desperate required. even more thanks.
Lalssa said:
Thanks to BaDaB!ng505
Must odin back to original rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drivedevice must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device*when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)reboot in recovery wipedata factory reset...done
factorymode: http://forum.xda-developers.com/attachment.php?attachmentid=1772304&d=1362190578
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Dont Think About What To Do Just Hit The THANK Button
---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------
But I didnt find for the s3 I am going do not download for the n8000
Dont Think About What To Do Just Hit The THANK Button
Click to expand...
Click to collapse
i need a help , i got this on the last step: can't find /dev/block/mmcblk0p3 in /etc/fstab
Lalssa said:
Thanks to BaDaB!ng505
Must odin back to original rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drivedevice must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
Click to expand...
Click to collapse
big thanks !!!
Hey Everyone,
So I have an Asus ZenPad C 7.0 Z170C and I was working on rooting the device. Long story short, I messed up and now I have a brick... or paper weight. I can at least use a paper weight for something....
Here is what my devices does currently:
When I try to boot the device, it gets stuck at the 2ND Asus screen and never actually boots up. I can get my device into fastboot (the GREEN background).
I can also get the device into RECOVERY mode by pressing (POWER + VOLUME DOWN) when booting the device.
However, I can only get the device to the screen with the DEAD ANDROID and "No Command" text screen. If I try getting the BOOTLOADER list to pop up, from the DEAD ANDROID screen, by pressing POWER + VOLUME UP, I get an error. The error is different depending on whether I have my EXTERNAL SD card in my device.
The error messages say the following:
EXTERNAL SD Card LEFT IN Device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/picture.php?albumid=13045&pictureid=52347
"
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/last_locale
"
----------------------------------------------------------------------
EXTERNAL SD Card Taken OUT of the Device:
http://forum.xda-developers.com/picture.php?albumid=13045&pictureid=52348
"
E: failed to mount /sdcard (No such file or directory
E: Can't mount /sdcard/P01Z_SDUPDATE.zip
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/lastlocale
"
Ive been searching and searching endlessly online all day and couldnt find anything that works. The closest I got was with the following:
Asus Flash Tool: Seems to work fine at first but then hangs. The "Unzip Image" step finishes and then it says "Rune Flash Image Script..." and does nothing. I let it run for over 1 hour and nothing changed.
Please let me know if there is anything else I can try. I do NOT care if my data is lost.
Thank you in advance!!
If you can get in the bootloader (POWER + VOLUME UP) and the device can be seen in the list on fastboot devices, then it should be easy to restore.
yes, I can do both.. whats your recommendation to restore?
InvisiBot said:
If you can get in the bootloader (POWER + VOLUME UP) and the device can be seen in the list on fastboot devices, then it should be easy to restore.
Click to expand...
Click to collapse
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
5.0.1
Excellent. Sounds simple enough... I will try this out when I get some time. Thanks you for your help!
Much Appreciated!
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
Click to expand...
Click to collapse
Deleted
So I FINALLY got around to trying your steps and.... IT WORKED!!
Can't thank you enough. I decided to "Apply Update using ADB" instead of the SD card and your step by step guide was perfect.
Thanks Again!!!!
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
Click to expand...
Click to collapse
..
deleted
i did al those steps with thw zenpad 7, because the thing stays in the logo, but im able to set it in recovery mode and fastboot; but when i flashed the latest firmware (from december) it asks for a newer one because the firmware on it is dated 10 april but that is not rolled out on the asus website; any adeas? gr bennie
C:\adb>fastboot flash recovery recovery.bin
(bootloader) recovery partition type: raw
target reported max download size of 1019215872 bytes
sending 'recovery' (8044 KB)...
(bootloader) Ready to receive: 0x007db000 size of da
OKAY [ 0.243s]
writing 'recovery'...
(bootloader) Flashing partition: recovery
FAILED (remote: Fail to flash partition: recovery)
finished. total time: 0.266s
why show error when i flash recovery ,...
i face problem in recovery
try in fastboot
fastboot format cache
fastboot format userdata
fastboot flash recovery (here the extract from above)
check recovery then!
I flash the zip with no errors but after reboot it says "ERROR FW image Verify Fail, Init: Tlv set update list fail" in the recovery menu
What is it mean what should i do?
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
Click to expand...
Click to collapse
can you extract recovery.bin and vrl.bin
from UL-P01V-WW-12.26.5.49-user from this firmware
my asus zenpad cant turn model number p01v
when i turn on it come no command stuck on there
what i will do
need system.img
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
Click to expand...
Click to collapse
Can you post the system.img file for the Zenpad C 7..0 and maybe the other factory images too? I accidentally overwrote it and have no way to recover it since I forgot to back up the ROM.
I need to flash a ROM on my device to root my VFD600, but can't flash it due to this message always showing up. How to fix it?
Android Recovery
Vodafone/VFD600/P809V50
6.0.1/MMB29M/20160927.133420
user/test-keys
Use volume up/down and power.
Supported API: 3
E:try to mount "/dev/block/mmcblk1p1" partition at "/sdcard" with exFAT filesystem
E:vfat mount failed, try to mount with fuse exfat
E:/sbin/mount.exfat failed with status 1
E:fangjun failed to mount /sdcard (No such file or directory)
-- Couldn't mount /sdcard.
Installation aborted.
Neither applying from ADB sideload or Fastboot commands other than "fastboot devices" work for me, so I can't even unlock the bootloader.
The phone can boot into Download Mode and Recovery mode. I've been googling about this problem for like a week now. the first attempt that I did was using Odin and downloading the *.md5.tar for my phone. It gave me several errors:
<Download mode details on the top left corner:>
ODIN MODE
PRODUCT NAME: GT-i9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM OFFICIAL: Official
<Odin GUI Errors:>
[FAIL]
ID/COM: [COM9]
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Next I tried recovery mode. While entering recovery. I got errors also:
Starting Recovery mode errors:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system (No such file or directory)
# MANUAL MODE #
-- Applying Multi-CSC...
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
E:failed to mount /cache (No such file or directory)
Can't mount /cache/recovery/last_recovery
E:failed to mount /data (No such file or directory)
E:Can't mount /data/log/recovery_log.txt
E:failed to mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (No such file or directory)
<After those errors stop appearing. The top part gets replaced with:>
Android system recovery <3e>
Volume up/down to move highlights;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
----------------------------------------
<When selecting "Apply update from ADB sideload / cache / external storage (also known as sdcard)". Errors are:>
E:failed to mount /system (Block device required)
E:failed to mount /cache (Block device required)
<If ADB is selected. the last lines say:>
Now send the package you want to apply
to the device with "adb sideload <filena
me>"...
<If external storage is selected. the last lines say:>
E:failed to mount /sd card (No such file or directory)
<When selecting "wipe data and fatory reset and/or wipe cache partition". Errors are:>
E:format_volume: make_extf4fs failed on /dev/block/MMCBLK0P12
E:format_volume: make_extf4fs failed on /dev/block/MMCBLK0P8
Please help
UPDATE: While I'm attempting to restore the *.zip update with ADB. The process goes to:
loading update.zip
sending update.zip ?? % (with underscores spazing from left to right)
and then looking from the phone.
it says:
<<<some things that I forgot after the sideload. the errors goes too fast for me>>>
Installation aborted
E: Can't mount /cache (Block device required)
E: Can't mount /system (Block device required)
E: Can't mount /efs (Block device required)
Try using different USB cables and USB ports to flash with Odin. I also recommend using Odin 3.07 as that has always worked for me.
Borked recovery. Flash back to stock is the best option but if that is failing then you don't really have much choice.
Beamed in by telepathy
audit13 said:
Try using different USB cables and USB ports to flash with Odin. I also recommend using Odin 3.07 as that has always worked for me.
Click to expand...
Click to collapse
I did borrow an original cable from my friend. The error is still there. I also tried plugging the cable from the rear usb port.
But thanks for the reply. I hope that others can find this helpful too
shivadow said:
Borked recovery. Flash back to stock is the best option but if that is failing then you don't really have much choice.
Beamed in by telepathy
Click to expand...
Click to collapse
Hmm.. "Borked recovery"? You mean that every command / operation that the recovery mode is performing are being blocked by the system itself? or you mean by errors in files inside the eMMC? There is no proof that the eMMC is damaged because it can boot to Download mode and recovery mode. I am still wondering if the recovery, download mode have their own eMMC.
BTW is it "ok" to use an SDHC for recovery image (selecting "Apply Update from external storage")? bcoz its the only one I have ATM (and no cash)
I am willing to go for SD card as an internal memory for the phone. I've read many articles about running your phone from SD card if the internal memory. But with one disadvantage. Read and Write are slower than eMMC. As much as I want to perform this operation but I don't have JTAG or other tools to start with. I also don't know what resistor to short.
=== Moto G Power (2020) XT2041-4-SS FIRMWARE: Android 10 "SOFIA_RETAIL_QPMS30.80-109-5" ===
1)
systemrw_1.32 (./makesysrw.sh size=50) => error code 73 (either way auto or manual)
2)
sysrw_repair_v1.32 (USB stick Ubuntu Mate 21.4) => Successfully created patched super image at /media/ubuntu-mate/Drive-C/sysrw_repair/img/super_fixed.bin
3)
"fastboot flash super super_fixed.bin" (in FASTBOOTD) => was sent 8 sparses SUPER out of 8, no errors
4)
restarted phone => OK
5)
adb shell
su
mount -o remount,rw /
mount -o remount,rw /system
mount -o remount,rw /product
mount -o remount,rw /vendor
6)
weird things started appear...
build.prop 0 Kb and copying saved earlier file build.prop to /system does not help it stays empty... I could change permissions in properties but it didn't help build.prop empty and nothing I could do... I repeated system rw remount but now I started getting bad returns like "mount: '/system' not in /proc/mounts" as I never flashed rw super image...
7)
flashed super image again in FASTBOOTD => same results: build.prop empty and nothing you can do with it
8)
flashed super image again now just in BOOTLOADER but weirdly in bootloader there were only 6 sparses SUPER out of 6 (in FASTBOOTD there were 8 sparses out of 8) => same results: build.prop empty and nothing you can do with it
9)
flashed and restored my FIRMWARE: SOFIA_RETAIL_QPMS30.80-109-5 (without erasing: boot, recovery, metadata and user data partitions) phone is fine but ROOT the same RO
-----------------------------------------
P.S. I was afraid to flash SUPER to slots A and B like:
fastboot flash super_a super_fixed.bin
fastboot flash super_b super_fixed.bin
and I didn't do it even though I remember some guy mentioned that it helped with two slots...
I didn't take a chance... I just got my phone back after being dead bricked from Motorola service... in the bricked phone i had perfect touch screen in TWRP (3.5.0_10) damn! in the phone of the same model they send me back TWRP touch screen does not work... (looks like the different drivers are set for the touch screen)
I've run into the same issue with the Self-Erasing Build.prop. Did you ever find a work-around? Maybe patching the build.prop on pc in SUPER and reflashing the Patched.Super.img would work?