Database Develop

Clockwork FRF83

Flashing from CM 5.0.8 using Rom Managers FRF83. It downloads three files, ERE27, FRF50, and FRF83. I get this error when installing part two
Code:
Installing: SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
Opening update package...
I:Update file path: /sdcard/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
Installing update...
I:Trying update-binary.
installing HTC updater extensions
Failed to mount /dev/block/mtdblock3 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
Verifying current system...
mtd read matched size 2101248 sha e7f20e513e5bd5c30e20670e992092296ee731a0
0 bytes free on /cache (6762912 needed)
error opening /cache/recovery/otatest: No such file or directory
0 regular files in deletable directories
no files can be deleted to free space on /cache
unable to make 6762912 bytes available on /cache
script aborted: assert failed: apply_patch_space(6762912)
assert failed: apply_patch_space(6762912)
E:Error in /sdcard/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
(Status 7)
Installation aborted.
Failure at line 7:
install_zip SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
From what I'm reading, this means that the updater script from Rommanager doesn't release the mount on system after the first flash, because I can easily navigate to the directory after I receive this error and install it manually. I figure the way it works is after install it umounts.
Just as an FYI, if others are trying this, this is what I did to overcome. 1.Using clockwork recovery
2.mount SD
3.find FRF83fromFRF50
4. copy to /sdcard/update.zip
5. manually install ERE27toFRF50
6. let it boot
7. reboot into stock recovery
8. install update.zip through stock recovery
BOOM FRF83

Ooops, sorry MODs. It originated as a question, but I figured it out mid writing this. Please move to general. Sorry

Moto G - 2014 - Rooted - Encrypted - TWRP - Install Cyanogen?

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

EVA L19 bricked no userdata

HI!
I have problem with my phone.
I have twrp and can access fastboot.
When I try to install a rom via usb-otg or internal storage i get this:
Installingzip file '/usbotg/stockrom.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mount: failed to mount /dev/block/dm-0 at /data: No such file or directory
Target: HUAWEI/EVA-L19/HWEVA:6.0/HUAWEIEVA-L19/
C900B182:user/release-keys
mount: failed to mount /dev/block/platform/hi_mci.0/
by-name/system at /system: Device or resource busy
symlink: some symlinks failed
Updater process ended with ERROR: 7
Error installing zip file '/usbotg/stockrom.zip'
Updating partition details...
Failed to mount '/data' (invalid argument)
...done
Unable to mount storage
It all happened when I (stupid me) did update.app. I guess it's a wrong one because on pc it says EVA-L09.
thanks in advance and sorry for my grammar

Note 9 failed to mount cache bootloop: Help required

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

Asus ROG 2 stuck in boot Loop

Hey guys, i have encountered a weird problem i got stuck in boot loop. i have tried to install the firmwares from fast boot, edl and TWRP mode. nothing is working
while trying to factory reset/wipe data i am getting error for BCB messaged alerts for failed to open dev/block/bootdevice/by-name/misc: no such file or directory found.
while from twrp i am getting unable to mount storage. i will highly appreciate if anyone can help me. mostly i have tried all of the firmware's.
Wiping Data...
Done processing script file
Wiping Cache...
Unable to find partition for path '/cache'
Done processing script file
Wiping Dalvik Cache...
Failed to mount '/data' (Invalid argument)
Done processing script file
Pushing First Zip...
D:\UL-ASUS_I001_1-CN-16.0631.1910.63-1.1.252-user.zip: 1 file pushed. 36.4 MB/s (2608518787 bytes in 68.420s)
Flashing First Zip...
Installing zip file '/UL-ASUS_I001_1-CN-16.0631.1910.63-1.1.252-user.zip'
Checking for Digest file...
Unmounting System...
Flashing A/B zip to inactive slot: B
Failed to mount '/system_root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
First Zip Flashed
Deleting First Zip...
Press any key to continue . . .