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
Related
Need help flashed jm8 through Odin, used correct files and have tried with repartition checked and unchecked.
On reboot just get:
E: Cant mount /dev/block/st110
(Invalid Argument)
E:copy_dbdata_media: cant mount DBDATA
copy default media content failed.
When I reboot it turns turns on to the s screen and then goes off again, any advice please?
Hi,
I got this this msg on recovery:
E:Can't mount /dev/block/stl11
(Invalid argument)
upadate media, please wait...
upadate media, finished
# MANUAL MODE #
--Appling Multi-CSC...
Instaling Multi-CSC
mps_dat value: XEE
copy_multi_carrier from: XEE
multicsc : can not acces to /system/csc/XEE/syst
em/
copy_common_data E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount /dev/block/stl11
(Invalid argument)
I got this msg after my galaxy forced close, I guess it was was stuck on boot, it would not pass the S logo, was showing black screen and it was vibrating once_ pause_ twice every minute. I tried to flash with odin3 1.7 , pit 512, eclair, it worked, canot access market(msg still there), i flashed with froyo xxjpo, same message, and not able to download from market, and not have unmount option on sdcard...
thanks for helping guys, great forum!
try to see if you can format it
if not, then you are potentially looking at a dead internal SD
thanks for ansewer
I tried that it said fromat complete, but i still have the error message! the phone is working fine, other then being able to download from market...
u think that I can replace the sd card?
I had this same error using I think it was JM8 Firmware at the time, try a different firmware, fixed it for me =]
thanks I just flashed
http://forum.xda-developers.com/showpost.php?p=9289959&postcount=1
it's working!
rasdaq said:
it's working!
Click to expand...
Click to collapse
Good good
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
Please bear with this lengthy description of my problem.
I successfully rooted my stock Samsung Galaxy Tab S2 SM-T713 Nougat but made 2 mistakes in the process. I neglected to copy the Build Number for the tablet and, after rooting and checking that everything worked OK, I turned off OEM unlock. The next time I started the tablet I got the message "Verification Failed, Unable to restart your device" with a yellow triangle! The tablet was bricked.
Since I did not know the build number for the stock rom, I found an flashed a supposedly “generic” JazzRom which brought the tablet back to life and it was unrooted. I was able to discover that the stock rom (T713XXU2BRB2) which I downloaded and flashed, I then flashed TWRP. So far so good.
I then booted into TWRP recovery and tried to do a factory wipe which produced a number of errors:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)
Formatting Cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
I then flashed SuperSU and when the tablet restarted I got "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
Now, my question is - can this be fixed?
kgash said:
please bear with this lengthy description of my problem.
I successfully rooted my stock samsung galaxy tab s2 sm-t713 nougat but made 2 mistakes in the process. I neglected to copy the build number for the tablet and, after rooting and checking that everything worked ok, i turned off oem unlock. The next time i started the tablet i got the message "verification failed, unable to restart your device" with a yellow triangle! The tablet was bricked.
Since i did not know the build number for the stock rom, i found an flashed a supposedly “generic” jazzrom which brought the tablet back to life and it was unrooted. I was able to discover that the stock rom (t713xxu2brb2) which i downloaded and flashed, i then flashed twrp. So far so good.
I then booted into twrp recovery and tried to do a factory wipe which produced a number of errors:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (invalid argument)
unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (invalid argument)
...done
unable to mount storage
failed to mount '/data' (invalid argument)
full selinux support is present.
Unable to mount /data/media/twrp/.twrps
mtp enabled
failed to mount '/data' (invalid argument)
formatting cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (invalid argument)
...done
unable to mount storage
i then flashed supersu and when the tablet restarted i got "verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
now, my question is - can this be fixed?
Click to expand...
Click to collapse
FORMAT /data
ashyx said:
FORMAT /data
Click to expand...
Click to collapse
Thank you. Actually I had to format twice for some reason. The tablet is now rooted and everything is now working great.
kgash said:
Please bear with this lengthy description of my problem.
I successfully rooted my stock Samsung Galaxy Tab S2 SM-T713 Nougat but made 2 mistakes in the process. I neglected to copy the Build Number for the tablet and, after rooting and checking that everything worked OK, I turned off OEM unlock. The next time I started the tablet I got the message "Verification Failed, Unable to restart your device" with a yellow triangle! The tablet was bricked.
Since I did not know the build number for the stock rom, I found an flashed a supposedly “generic” JazzRom which brought the tablet back to life and it was unrooted. I was able to discover that the stock rom (T713XXU2BRB2) which I downloaded and flashed, I then flashed TWRP. So far so good.
I then booted into TWRP recovery and tried to do a factory wipe which produced a number of errors:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)
Formatting Cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
I then flashed SuperSU and when the tablet restarted I got "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
Now, my question is - can this be fixed?
Click to expand...
Click to collapse
Im glad you work it out. Quick question for, my friend, did you rooted t713 with the latest nougat update ->
NRD90M.T713XXU2BRB2?
Thx
netgar said:
Im glad you work it out. Quick question for, my friend, did you rooted t713 with the latest nougat update ->
NRD90M.T713XXU2BRB2?
Thx
Click to expand...
Click to collapse
Yes I did.
I am trying to odin the new T713 firmware but for some reason odin keeps failing in the end. Is there a certain odin I should be using?
Danilynne said:
I am trying to odin the new T713 firmware but for some reason odin keeps failing in the end. Is there a certain odin I should be using?
Click to expand...
Click to collapse
Post up the errors so there's more to go on.
Thanks I finally got it, I had the wrong firmware, I needed xarbrb2.
Sent from my SM-N950U using XDA Free mobile app
after update to U4 security phone does not start anyway nly samsung logo
in recovery :
Code:
#fail to open recovery_cause(no such file or directory)#
#reboot recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (invalid argument)
Supported API: 3
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
dm-verify verification failed...
phone is :
8.0.0/R16NW/N950NKSU4CRJ2
frp: ON
oem: ON
==================================
with combination U4 file got factory binay logo only
reset and wipe same result!
how to resolve this problem ???
thanks.
Looks like the internal storage might have been corrupted. You would have to reformat the internal storage and reinstall the OS back onto your device.
but how to do this ??? via jtag tools ???
thank you solved by combin. and a special file .
recan21 said:
thank you solved by combin. and a special file .
Click to expand...
Click to collapse
where is the special file
me also facing same problm
Abussabah said:
where is the special file
me also facing same problm
Click to expand...
Click to collapse
it's not for free bro !!