Sorry if this is a re post but I have stayed up late and have not found a answer to my problem. Or at least a way that I havent tried.
My problem is that I am stuck on the ATT white screen. I can get in download mode and recovery but cant seem to get past that. In recovery it states
Media files copy failed.
# Manual Mode#
--Appling Multi-CSC...
Installing Multi-SCS
Can't access to '/system/csc/ATT/system/'.
E:failed to mount /cache (invalid argument)
E:Cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Gailed to mount /cache (invalid argument)
E:Cant mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
E:failed to mount /cache (invalid argument)
Any help would be great minus the Noob Bashing please lol
Ok never mind now I finally got it with a combination of 2 things. One using I897UCJF6-final-OCD-REV0.zip from http://forum.xda-developers.com/showthread.php?t=731989 to rewrite the everything back, but it made it boot loop, so i used One Click Unbrick and all my problems went away.
My phone when rebooting will not get past the galaxy S start up screen.
I tried to install Team hacksungs ICS for samsung Galaxy S i9000.
I went through all the steps as correctly as I thought but when it restarted for the final time it would get into ICS and present a message and ask me to restart, so I did and it would get stuck changing between the regular boot and cyanogen mod.
To fix this I thought it would be best to re flash it back to a ginger bread stock. which I did and that worked, I tried the process again in the hopes that it was something random but to no prevail.
Upon going into download mode i thought i'll just go flash back to the rooted version of my phone
But when I rebooted after that it would not get past the start up screen
I've even flashed it with the custom rom and with the stock gingerbread but they both start up the same and won't get past he start up screen.
Oddly if I use the custom rom which has clockwork recovery pre installed the reboot menu screen will that instead of the regular one.
I would take a picture but my phone is my only access to a camera
Here's what i'm looking at on the reboot menu: (hope it helps)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet. please use UI men
u for format and rebbot actions
Media files copy failed.
# MANUAL MODE #
-- Appling multi CSC...
installing multi CSC
Can't access to '/system/csc/XEU/system/'.
Successfully applied multi CSC.
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/recovery_kernal_lo
g
E:copy_kernel_file :: Can't open /cache/revovery
/recover_kernal_log
E:Failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:Failed mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
panteliskyriacou said:
My phone when rebooting will not get past the galaxy S start up screen.
I tried to install Team hacksungs ICS for samsung Galaxy S i9000.
I went through all the steps as correctly as I thought but when it restarted for the final time it would get into ICS and present a message and ask me to restart, so I did and it would get stuck changing between the regular boot and cyanogen mod.
To fix this I thought it would be best to re flash it back to a ginger bread stock. which I did and that worked, I tried the process again in the hopes that it was something random but to no prevail.
Upon going into download mode i thought i'll just go flash back to the rooted version of my phone
But when I rebooted after that it would not get past the start up screen
I've even flashed it with the custom rom and with the stock gingerbread but they both start up the same and won't get past he start up screen.
Oddly if I use the custom rom which has clockwork recovery pre installed the reboot menu screen will that instead of the regular one.
I would take a picture but my phone is my only access to a camera
Here's what i'm looking at on the reboot menu: (hope it helps)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet. please use UI men
u for format and rebbot actions
Media files copy failed.
# MANUAL MODE #
-- Appling multi CSC...
installing multi CSC
Can't access to '/system/csc/XEU/system/'.
Successfully applied multi CSC.
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/recovery_kernal_lo
g
E:copy_kernel_file :: Can't open /cache/revovery
/recover_kernal_log
E:Failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:Failed mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
Click to expand...
Click to collapse
Reflash stock rom(eg. Jvu) with Odin, with pit file and repatition ticked and let it boot. Reroot with cf-root jvu kernel
Hello! I'm using Ubuntu 12.04 and can't get it working with htc vivid
here is my info:
Quote:
udevadm info -q all --path /sys/bus/usb/devices/2-3P: /devices/pci0000:00/0000:00:1d.7/usb2/2-3
N: bus/usb/002/023
E: BUSNUM=002
E: DEVNAME=/dev/bus/usb/002/023
E: DEVNUM=023
E: DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-3
E: DEVTYPE=usb_device
E: DRIVER=usb
E: ID_BUS=usb
E: ID_MODEL=Android_1.0
E: ID_MODEL_ENC=Android\x201.0
E: ID_MODEL_ID=0ff0
E: ID_REVISION=0100
E: ID_SERIAL=htc__Inc_Android_1.0_HT1ASVJ25491
E: ID_SERIAL_SHORT=HT1ASVJ25491
E: ID_USB_INTERFACES=:ff4203:
E: ID_VENDOR=htc__Inc
E: ID_VENDOR_ENC=htc\x2c\x20Inc
E: ID_VENDOR_ID=0bb4
E: MAJOR=189
E: MINOR=150
E: PRODUCT=bb4/ff0/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: UDEV_LOG=3
E: USEC_INITIALIZED=2423343578
and command udevadm test --action=SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="0bb4",ENV{ID_MODEL_ID}=="0ff0" , MODE="0666" gives me an error:
unable to open device '/sysENV{ID_VENDOR_ID}==0bb4,ENV{ID_MODEL_ID}==0ff0, '
please, help me with udev rule! It's for upgrading kernel by this tutorial addictivetips com/mobile/how-to-install-kernels-on-android-phones-custom-roms
Hi there,
Today morning I notice that my Nexus 6 switched off with no reason, no root or anything else, I tried to turn it on but it stuck on google logo, after that I decided to reset to factory from recovery using Wipe data/ factory reset, I surprised that I received these messages:
Formatting / data ...
E:failed to mount /cache (Invalid argument)
Formatting cache ...
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O Error)
E:failed to mount /cache (Invalid argument)
What can I do now ? I just put my mobile on charging at night and went to sleep
Thank you in advance.
This appears to be a common issue that has vexed Nexus 7 owners in the past. The problem is related to corruption from an update. The usual fix would be to flash a factory image, but to do that you would have to unlock the bootloader. I doubt you did. Fortunately, there still is a solution that may help: sideloading the Android N Preview 1 OTA zip Google provided some months back. It's a complete system image, and installing it should get your device running. Afterward, you can unlock the bootloader (recommended) and flash the latest factory image from Google. If unlocking the bootloader is something you don't wish to do, subscribing to then unsubscribing from the Android N Preview program should push an Android 6.0.1 factory image to your device.
Back up your pictures and documents on internal storage before doing this or else they will be lost.
Strephon Alkhalikoi said:
This appears to be a common issue that has vexed Nexus 7 owners in the past. The problem is related to corruption from an update. The usual fix would be to flash a factory image, but to do that you would have to unlock the bootloader. I doubt you did. Fortunately, there still is a solution that may help: sideloading the Android N Preview 1 OTA zip Google provided some months back. It's a complete system image, and installing it should get your device running. Afterward, you can unlock the bootloader (recommended) and flash the latest factory image from Google. If unlocking the bootloader is something you don't wish to do, subscribing to then unsubscribing from the Android N Preview program should push an Android 6.0.1 factory image to your device.
Back up your pictures and documents on internal storage before doing this or else they will be lost.
Click to expand...
Click to collapse
Thank you for your reply, i don't care about the data in my phone I will go with Android N.
If you have a link it may help I will be appreciated.
Thank you,
Check the General subforum. There should be an entire thread about the Android N Preview there, including how to install it.
I recently ran into some issues with my note 9, I appear to be in an update loop. My phone boots up into the blue android screen with the android robot saying "installing update" it then flashes the android on its side with a yellow "!" then it displays the text at the very bottom of this thread ** then reboots & repeats this. I cant find a way to exit it some of my issues are listed below;
I am unable to enter recovery mode
I am unable to turn the device off
I can reboot it using the power and volume down button, however it boots into the loop again
**the text at the bottom reads;
#reboot recovery case is [BL: Recovery Mode Set by key]#
support SINGLE-SKU
Block-Based OTA
Support API: 3
#MANUAL MODE v1.0.0#
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E: Cant mount /cache/recovery/last_locale
{
"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"
}
If anyone could help me out or point me in the right direction would be a massive help as im completely lost for ideas . I have done the usual google but had no luck so far. Thanks!
weelee01 said:
I recently ran into some issues with my note 9, I appear to be in an update loop. My phone boots up into the blue android screen with the android robot saying "installing update" it then flashes the android on its side with a yellow "!" then it displays the text at the very bottom of this thread ** then reboots & repeats this. I cant find a way to exit it some of my issues are listed below;
I am unable to enter recovery mode
I am unable to turn the device off
I can reboot it using the power and volume down button, however it boots into the loop again
**the text at the bottom reads;
#reboot recovery case is [BL: Recovery Mode Set by key]#
support SINGLE-SKU
Block-Based OTA
Support API: 3
#MANUAL MODE v1.0.0#
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E: Cant mount /cache/recovery/last_locale
If anyone could help me out or point me in the right direction would be a massive help as im completely lost for ideas . I have done the usual google but had no luck so far. Thanks!
Click to expand...
Click to collapse
please tell me how did you fix this??
need help as can't find anything about this over the internet
anyone?
up, i have the same problem
Me too. Now i dont know how to fix.
i have the same problem
still cannot be fixed ?
i guess ths is it
bye my note 9 :crying:
Samsung service centre
anyone could fix this???
Had the same issue on international note9.
Could not get in any menu (download mode or recovery)
Waited until phone battery died (let it sit for a day in boot loop)
After that hold Bixby + vol down and plug in charge cable.
Result: download mode. In download mode you can easily recover with odin and official firmware.
julianbl said:
How?? Please enlighten me!
Thanks!
Click to expand...
Click to collapse
does anyone know how to fixed this issue on samsung note 9 n960F/DS? please help i have the same issue?
ehly said:
does anyone know how to fixed this issue on samsung note 9 n960F/DS? please help i have the same issue?
Click to expand...
Click to collapse
... the information you want is literally in the post above yours...
oddbehreif said:
... the information you want is literally in the post above yours...
Click to expand...
Click to collapse
thanks a lot sir! but sad to say i already tried it but it wont work for my phone! Hopefully someone can share how to fix this issue on samsung note 9...
ehly said:
thanks a lot sir! but sad to say i already tried it but it wont work for my phone! Hopefully someone can share how to fix this issue on samsung note 9...
Click to expand...
Click to collapse
I'm sorry. That wasn't apparent, so jumps to conclusions were made. :angel:
What exactly happened on your attempt? Did flashing simply do nothing, did the flashing fail, or were you unable to enter download mode?
ehly said:
thanks a lot sir! but sad to say i already tried it but it wont work for my phone! Hopefully someone can share how to fix this issue on samsung note 9...
Click to expand...
Click to collapse
Pit ?
Sent from my SM-N960F using Tapatalk
hy press power button and volume down. your phone is off for 2 sec , on this 2 sec pres byxby and volume down and enter in download mode.
I have a Note 9 which has had a failed firmware update.
OEM unlocking isn’t activated, which might make things difficult. I was going to try to flash the Combination file to gain access to activate OEM unlocking, but only the Oreo files are available, not Pie. Anyway, I have to fix the bootloop first.
After failed firmware update, I was originally getting an “installing system update” bootloop as below until the battery ran out
Reboot Recovery Cause is [BL:recovery mode set by key]#
E:Failed to mount /cache: Invalid Argument
Support SINGLE-SKU
Blocked-based OTA
Supported API: 3
#Manual Mode v1.0.0#
E:Failed to mount /cache: Invalid Argument
E:Failed to mount /cache: Invalid Argument
E:Failed to mount /cache: Invalid Argument
E:Failed to mount /cache: Invalid Argument
E:Can’t mount /cache/recovery/last_locale
Once the battery ran out I could get into download mode, but not recovery
I used ODIN to flash the latest stock Pie firmware “N960NKSU3CSJ1” by flashing BL, AP, CP and CSC but I then get the blue android bot “Installing system update” bootloop and no other details. I tried ODIN again but just flashed AP to see what would happen, still bootloop but more details:
#no data on recovery_cause#
#Reboot Recovery Cause is [UNKNOWN]#
E:Failed to mount /cache: Invalid Argument
Support SINGLE-SKU
Blocked-based OTA
Supported API: 3
…Resizing data…
E:Failed to mount /data: (Invalid Argument)
Failed to mount /’data’: (Invalid Argument)
Failed the resizing-data
E:Failued to mount /cache: Invalid Argument
E:Can’t mount /cache/recovery/log
And so on
I’m out of ideas as to what to do. I have tried flashing the older combination files, but get 'kernel rev check fail device 3 binary 2 (boot)' due to it being the wrong version.
petal666 said:
I have a Note 9 which has had a failed firmware update.
OEM unlocking isn’t activated, which might make things difficult. I was going to try to flash the Combination file to gain access to activate OEM unlocking, but only the Oreo files are available, not Pie. Anyway, I have to fix the bootloop first.
After failed firmware update, I was originally getting an “installing system update” bootloop as below until the battery ran out
Reboot Recovery Cause is [BL:recovery mode set by key]#
E:Failed to mount /cache: Invalid Argument
Support SINGLE-SKU
Blocked-based OTA
Supported API: 3
#Manual Mode v1.0.0#
E:Failed to mount /cache: Invalid Argument
E:Failed to mount /cache: Invalid Argument
E:Failed to mount /cache: Invalid Argument
E:Failed to mount /cache: Invalid Argument
E:Can’t mount /cache/recovery/last_locale
Once the battery ran out I could get into download mode, but not recovery
I used ODIN to flash the latest stock Pie firmware “N960NKSU3CSJ1” by flashing BL, AP, CP and CSC but I then get the blue android bot “Installing system update” bootloop and no other details. I tried ODIN again but just flashed AP to see what would happen, still bootloop but more details:
#no data on recovery_cause#
#Reboot Recovery Cause is [UNKNOWN]#
E:Failed to mount /cache: Invalid Argument
Support SINGLE-SKU
Blocked-based OTA
Supported API: 3
…Resizing data…
E:Failed to mount /data: (Invalid Argument)
Failed to mount /’data’: (Invalid Argument)
Failed the resizing-data
E:Failued to mount /cache: Invalid Argument
E:Can’t mount /cache/recovery/log
And so on
I’m out of ideas as to what to do. I have tried flashing the older combination files, but get 'kernel rev check fail device 3 binary 2 (boot)' due to it being the wrong version.
Click to expand...
Click to collapse
you dont need a combo firmware for OEM unlock.
now just use frija or samfirm tool to dl latest firmware. because you seem to be trying for some reason to flash an older bootloader based firmware revision than the phone is on and thats the cause one of your problems.(as per the last part of your message)
also when you flash n960n firmware, flash the 5th userdata.md5 file aswell. ( so reflash all 5 .md5 instead of 4 and of course choose csc.md5 over home_csc.md5)
be sure to use odin 3.13.3 or 3.11.1 aswell.
bober10113 said:
you dont need a combo firmware for OEM unlock.
now just use frija or samfirm tool to dl latest firmware. because you seem to be trying for some reason to flash an older bootloader based firmware revision than the phone is on and thats the cause one of your problems.(as per the last part of your message)
also when you flash n960n firmware, flash the 5th userdata.md5 file aswell. ( so reflash all 5 .md5 instead of 4 and of course choose csc.md5 over home_csc.md5)
be sure to use odin 3.13.3 or 3.11.1 aswell.
Click to expand...
Click to collapse
Thanks. That worked. I almost flashed userdata as well at one point but didn't.
I'm aware the combination file is the wrong bootloader, not need now anyway. Thanks again.
How do you fix it? I can't change KG status: Locked because of bootloop
k19wm said:
Had the same issue on international note9.
Could not get in any menu (download mode or recovery)
Waited until phone battery died (let it sit for a day in boot loop)
After that hold Bixby + vol down and plug in charge cable.
Result: download mode. In download mode you can easily recover with odin and official firmware.
Click to expand...
Click to collapse
sir i tried it but after i get to download mode it again just restart again