Related
I just made a custom rom and have it CWM flashable, but the updater-script I obtained (through TUT) is mounting /dev/block/mmcblk0p2 as system, which is NOT a system block instead! (I found out it should be mmcblk0p3).
Now, my phone boot normally, just not prompting me for unlocking SIM, and I can't make call and all that, what should I do now?
Grab a modemfs and flash it back?
EDIT: Part of logcat which should have mentioned the causes:
I/MLR ( 1730): Waiting Modem to be ready...
I/MLR ( 1730): Waiting for RIL to be intialized, try 1...
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/APPL' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/BOOT' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/CONF' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/DO' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/LOG' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/PERM' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/TMP' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/PERM' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/CONF' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/PERM' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/PERM' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED mkdir(path='/modemfs/PERM' mode=0x1c0) ret=-1 errno=28 (No space left on device)
I/msa ( 1675): [MSA] FAILED rmdir(path='/modemfs/PERM') ret=-1 errno=2 (No such file or directory)
I/msa ( 1675): [MSA] FAILED stat(path='/modemfs/CONF' buf=0xbef3a850) ret=-1 errno=2 (No such file or directory)
Click to expand...
Click to collapse
Anyone could provide a backup of mmcblk0p2? Please T^T (edit2: my baseband: XAMD)
SOLUTION:
1. Downgrade it back to GB (http://forum.xda-developers.com/show....php?t=2195673)
2. Check if modem is working
3. (Optional) If yes, flash back the stock ICS (custom rom's results may vary) with ODIN. (use your own regions', suggest you to download from: http://www.sammobile.com/)
4. If no, post your question here, let us help you =D
milkgreen said:
I just made a custom rom and have it CWM flashable, but the updater-script I obtained (through TUT) is mounting /dev/block/mmcblk0p2 as system, which is NOT a system block instead! (I found out it should be mmcblk0p3).
Now, my phone boot normally, just not prompting me for unlocking SIM, and I can't make call and all that, what should I do now?
Grab a modemfs and flash it back?
EDIT: Part of logcat which should have mentioned the causes:
Anyone could provide a backup of mmcblk0p2? Please T^T (edit2: my baseband: XAMD)
Click to expand...
Click to collapse
Try to flash stock firmware with Odin.
Sent from my GT-I9070 using Tapatalk
shut_down said:
Try to flash stock firmware with Odin.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
it doesn't work, I tried looking into it but there's no modemfs.bin.md5
milkgreen said:
it doesn't work, I tried looking into it but there's no modemfs.bin.md5
Click to expand...
Click to collapse
How did you check that there is no modemfs.bin.md5??? In Serbian firmware:
{
"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"
}
You can try to downgrade to GB http://forum.xda-developers.com/showthread.php?t=2195673
shut_down said:
How did you check that there is no modemfs.bin.md5??? In Serbian firmware:
You can try to downgrade to GB http://forum.xda-developers.com/showthread.php?t=2195673
Click to expand...
Click to collapse
i got the '.tar.md5' files, that modem.bin is different from modemfs.bin, they are extracted to different partition (according to the PIT)
trying to downgrade now..
milkgreen said:
i got the '.tar.md5' files, that modem.bin is different from modemfs.bin, they are extracted to different partition (according to the PIT)
trying to downgrade now..
Click to expand...
Click to collapse
Sorry, I did not read it like I should. :angel:
shut_down said:
Sorry, I did not read it like I should. :angel:
Click to expand...
Click to collapse
it's ok :laugh:
anyway, I just wish I could send it for service, so that I could get everything stock, and be able to back them up,
shut_down said:
Sorry, I did not read it like I should. :angel:
Click to expand...
Click to collapse
ww, done!
I follow that downgrading guide, and I got the modem up again! (the 3g connecting speed is also improved, wow!)
Afterwards, I flashed it with stock ICS (with Odin), and the modem remains working, felt very nice!
I won't say thank you , I press it! haha
CM App Installer will pull the latest versions of the apps available that CyanogenMod exclusively develop, and give you the option to install them to your system either rooted or non-rooted. I cannot guarantee success with this, I don't develop the application, my job is simply to make it easier for you guys to get your favourite CyanogenMod apps on your own ROMs!
Use carefully! As ever, I do not take responsibilty for any damage done to your device as a result of this! The root features use the code specified in "code" in the options menu, or it's listed below. If you're paranoid, please give it a read
I have to emphasise, please try the non-root method first!. The root method is designed as a last ditch attempt to get it working, it does backup and restore your old versions but errors do happen, expect this as a possibility if you're rooted!
The list of apps available in the application are:
Apollo
Calculator
CM File Manager
Torch
Messaging
DSP Manager
Voice+
News and Weather Widget
Trebuchet Launcher
cLock Widget
Movie Studio
CM Wallpapers
Let me know if you have any more suggestions to add!
Code
This information is also available from within the application.
There are a number of commands that this application uses, it executes certain processes through the code to copy apps to the system directory.
These commands are ran as if they were ran inside the terminal emulator, and always consist of
process, remount to read-write, transfer/copy/rename, remount to read-only, close. (In this order).
I use a Process to get a SU Runtime instance
Code:
Process p = Runtime.getRuntime().exec("su");
And then I use a PrintStream to issue the commands listed below to it.
Remount the system partition as read-write
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Rename an app (use move command to move with a different extension - Creating backups)
Code:
mv /system/app/AppOfChoice.apk /system/app/AppOfChoice.bak
Copy an app from SD card to System directory
Code:
cat /sdcard/CMApps/AppOfChoice.apk > /system/app/AppOfChoice.apk
Remove an app from system partition
Code:
rm -r /system/app/AppOfChoice.apk
For permissions, I use chmod
Code:
chmod 644 /system/app/AppOfChoice.apk
Remount the system partition as read-only
Code:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
And that is it. The process commands get pushed over the course of about two seconds, and should work. Again, I can't promise everything.
Credit also goes to the Reddit member /u/wchill, his code helped with the system code (shown in the Code section above)
Similarly, I do not take any responsibility if this app causes your phone to be bricked, corrupted, broken, or to encounter an unfortunate case of spontaneous combustion. Use at your own risk.
In the mean time, enjoy!
{
"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"
}
Source:
See this xda thread
So I've been spending two days to get my HTC One to work. I've installed different recoveries, tried different ROM's and sadly my backup of my stock rom magically disappeared I am also S-ON. Here's what I get after wiping and installing:
Using CMW:
-- Installing /sdcard/cm-12-20141205-UNOFFICIAL-m7.zip
Finding update package...
Opening update package...
Installing update...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
script succeeded: result was [0.200000]
Install from sdcard complete.
press any key to continue.
---------------------------------------------
Suceeded? Suuuuuure. I flashed the boot.img before all this and my phone still won't boot up the ROM. It keeps saying I'm not rooted also when prompting to reboot. Says there is no OS. Also if I don't format system before installing in recovery I get this:
-- Installing /sdcard/cm-12-20141205-UNOFFICIAL-m7.zip
Finding update package...
Opening update package...
Installing update...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
E: Error in /data/media/0/cm-12-20141205-UNOFFICIAL-m7.zip
(Status 0)
Installation aborted.
--------------------------------------------
So yeah. Very ****ed, I really need to use my phone and geez how am I supposed to survive without music?
What should I do to fix this? Please give me stuff in with spoons because I am really bad with all these acronyms and technical terms.
Enitoni said:
So I've been spending two days to get my HTC One to work. I've installed different recoveries, tried different ROM's and sadly my backup of my stock rom magically disappeared I am also S-ON. Here's what I get after wiping and installing:
Using CMW:
-- Installing /sdcard/cm-12-20141205-UNOFFICIAL-m7.zip
Finding update package...
Opening update package...
Installing update...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
script succeeded: result was [0.200000]
Install from sdcard complete.
press any key to continue.
---------------------------------------------
Suceeded? Suuuuuure. I flashed the boot.img before all this and my phone still won't boot up the ROM. It keeps saying I'm not rooted also when prompting to reboot. Says there is no OS. Also if I don't format system before installing in recovery I get this:
-- Installing /sdcard/cm-12-20141205-UNOFFICIAL-m7.zip
Finding update package...
Opening update package...
Installing update...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
E: Error in /data/media/0/cm-12-20141205-UNOFFICIAL-m7.zip
(Status 0)
Installation aborted.
--------------------------------------------
So yeah. Very ****ed, I really need to use my phone and geez how am I supposed to survive without music?
What should I do to fix this? Please give me stuff in with spoons because I am really bad with all these acronyms and technical terms.
Click to expand...
Click to collapse
What version of CWM are you using?
Philz Touch 6
CWM Base version: v6.0.4.5
alray said:
What version of CWM are you using?
Click to expand...
Click to collapse
Philz Touch 6
CWM Base version: v6.0.4.5
Enitoni said:
Philz Touch 6
CWM Base version: v6.0.4.5
Click to expand...
Click to collapse
CM require block:by-name support form the recovery to be flashed, hence why you must use at least CWM 6.0.4.8+ or TWRP 2.7.0.8+ like said on the cyanogenmod install instruction page.
So short answer: update your recovery.
{
"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://wiki.cyanogenmod.org/w/M7_Info
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
alray said:
CM require block:by-name support form the recovery to be flashed, hence why you must use at least CWM 6.0.4.8+ or TWRP 2.7.0.8+ like said on the cyanogenmod install instruction page.
So short answer: update your recovery.
http://wiki.cyanogenmod.org/w/M7_Info
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Click to expand...
Click to collapse
Tried that so many times, do you happen to know a recovery that will work with CM? I ended up trying a AOSP rom and it worked, so my phone is no longer soft-bricked.
Enitoni said:
Tried that so many times, do you happen to know a recovery that will work with CM? I ended up trying a AOSP rom and it worked, so my phone is no longer soft-bricked.
Click to expand...
Click to collapse
twrp 2.7.1.1
alray said:
twrp 2.7.1.1
Click to expand...
Click to collapse
Alright I'll try it tomorrow, let you know if anything wrong happens!
alray said:
twrp 2.7.1.1
Click to expand...
Click to collapse
Success! Thanks for all the help! It finally booted, I'm waiting for it to prepare. Let's cross our fingers and hope it works! Again, thanks!
Flashing Custom Rom ; Updater error 7.
Same problem.
Failed to mount/dev/......../system: No such file or directory
Failed to unmount: No such volume.
Iam using twrp 3.0.1-0 version.
Mobile: MICROMAX Canvas Play Q355.
Error:
Unknown command [log]
Updater process ended with ERROR:7
I'm trying to install Cyanogen Mod on my phone. Unfortunately it fails due to the following
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details. . .
E:Unable to mount '/data'
. . . done
E:Unable to mount storage.
E:Unable to mount '/data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount '/data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
E:Unable to mount '/data'
E:Unknown MTP message type: 1
E:Unable to wipe '/data'
Updating partition details . . .
E:Unable to mount '/data'
. . . done
I cannot factory restore to get rid of the encrypted partition, TWRP cannot factory reset, nothing in advanced options seems to do it, I cannot install Cyanogen as it fails. It seems that the /data directory is mounted by the phone as /dev/block/dm-0 but when I open an adb shell in recovery, there is no /dev/block/dm-0.
Please help!
Not_Technically_Minded! said:
I'm trying to install Cyanogen Mod on my phone. Unfortunately it fails due to the following
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details. . .
E:Unable to mount '/data'
. . . done
E:Unable to mount storage.
E:Unable to mount '/data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount '/data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
E:Unable to mount '/data'
E:Unknown MTP message type: 1
E:Unable to wipe '/data'
Updating partition details . . .
E:Unable to mount '/data'
. . . done
I cannot factory restore to get rid of the encrypted partition, TWRP cannot factory reset, nothing in advanced options seems to do it, I cannot install Cyanogen as it fails. It seems that the /data directory is mounted by the phone as /dev/block/dm-0 but when I open an adb shell in recovery, there is no /dev/block/dm-0.
Please help!
Click to expand...
Click to collapse
Try to select data in advanced wipe and change it's file system to F2FS.
Just tried that.
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details. . .
E:Unable to mount '/data'
. . . done
E:Unable to mount storage
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled.
E:Unable to mount '/data'
E:Unknown MTP message type: 1
E:Error changing file system.
Updating partition . . .
E:Unable to mount '/data'
. . . done
Typos are my own as if I try and save the file it tries to save to /data
Not_Technically_Minded! said:
Just tried that.
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details. . .
E:Unable to mount '/data'
. . . done
E:Unable to mount storage
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled.
E:Unable to mount '/data'
E:Unknown MTP message type: 1
E:Error changing file system.
Updating partition . . .
E:Unable to mount '/data'
. . . done
Typos are my own as if I try and save the file it tries to save to /data
Click to expand...
Click to collapse
Try:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
in TWRP terminal
Yeah! That's a step forward! I have a new error lol once trying to install CM.
Code:
This package supports bootloader(s):0x4882, 0x4883, 0x4886; this device has bootloader 0x4807.
E:Error executing updater binary in zip '/sdcard1/cm-12.1-20151117-SNAPSHOT-YOG7DA01K5-titan.zip'
Error flashing zip '/sdcard1/cm-12.1-20151117-SNAPSHOT-YOG7DA01K5-titan.zip'
Just tried to follow this http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007/ to see if it improved anything. Same error.
Ah, the vital step I missed was "Once bootloader has been updated, reboot into bootloader and select recovery again".
Cyanogen is stuck in a bootloop with the cyan head with the waves coming out of it. Any further ideas?
Not_Technically_Minded! said:
Ah, the vital step I missed was "Once bootloader has been updated, reboot into bootloader and select recovery again".
Cyanogen is stuck in a bootloop with the cyan head with the waves coming out of it. Any further ideas?
Click to expand...
Click to collapse
Hmm, did you format it to F2FS back again?
Just to confirm, I should format /data to F2FS in TWRP?
Not_Technically_Minded! said:
Just to confirm, I should format /data to F2FS in TWRP?
Click to expand...
Click to collapse
yes
So I've just formatted data as F2FS and reinstalled CM + Gapps, let's see how it goes!
Edit: Still can't get beyond the splash screen.
Not_Technically_Minded! said:
So I've just formatted data as F2FS and reinstalled CM + Gapps, let's see how it goes!
Edit: Still can't get beyond the splash screen.
Click to expand...
Click to collapse
Hmm, can you try booting after fastboot -w?
Done that; not the expected message that came up?
Code:
erasing 'userdata'...
OKAY [ 0.653s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.001s]
erasing 'cache'...
OKAY [ 0.137s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.001s]
finished. total time: 0.792s
Talking about the filesystem of 'raw'? Doesn't seem to have changed anything? Still just on the splash screen.
Not_Technically_Minded! said:
Done that; not the expected message that came up?
Code:
erasing 'userdata'...
OKAY [ 0.653s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.001s]
erasing 'cache'...
OKAY [ 0.137s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.001s]
finished. total time: 0.792s
Talking about the filesystem of 'raw'? Doesn't seem to have changed anything? Still just on the splash screen.
Click to expand...
Click to collapse
Ahh! Optimizing apps!
Could you kindly confirm your personal paypal is the one mentioned in your signature?
The effort and time you've put in is worthy of a beer.
Ohhh! What a Newbie I am! I forgot to add root to the list of apps I need. Can I just go back and install it or do I need to reflash everything again? What's the 'best' root app at this point in time please?
Not_Technically_Minded! said:
Could you kindly confirm your personal paypal is the one mentioned in your signature?
The effort and time you've put in is worthy of a beer.
Click to expand...
Click to collapse
Yup it is my actual PP.
Not_Technically_Minded! said:
Ohhh! What a Newbie I am! I forgot to add root to the list of apps I need. Can I just go back and install it or do I need to reflash everything again? What's the 'best' root app at this point in time please?
Click to expand...
Click to collapse
You can enable root in the developer settings.
Wonderful. Thanks.
I made the stupid mistake of encrypting my device (why must I feel so security conscious?!). This means that you cannot flash anything in recovery. Is there a work around for this?
Not_Technically_Minded! said:
Wonderful. Thanks.
I made the stupid mistake of encrypting my device (why must I feel so security conscious?!). This means that you cannot flash anything in recovery. Is there a work around for this?
Click to expand...
Click to collapse
The TWRP images I provide for multirom stuff are mounting encrypted /data just fine but I'm not sure why encrypted data would prevent /system from being flashed...
Any ideas as to what's causing this?
{
"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"
}
Answer: RTFM. I found a answer which says to use the latest alpha. Alas, it appears to work. I don't normally like bleeding edge stuff, prefer stable. Debian > Ubuntu
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