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
I would to install cyanogenmod 10... I started from GB stock firmware(overcome I think)... I rooted device, then I put the zip file on internal memory... I started device holding power on and volup key... I wiped data/factory reset, then wiped cache... I finally chose install zip card but I received this error:
Installing /sdcard/cm-10-20120908-NIGHTLY-p1.zip
Finding update package
Opening update package
Installing update
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-10-20120908-NIGHTLY-p1.zip
(status 7)
Installation aborted.
I did a sho log in advanced menu:
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknown volume: /external_sd
I:Can't partition unsafe device:/dev/block/mmcblk1p1
I don't understand what I should to do... Can you help me???
My device is a p1000(gsm)... Now is accessible only in download mode and in CWM recovery...
I solved with one more step... First I returned to stock GB, then installed CM9 and updated to CM10 with cdesai instruction... Installation finished...
Please help! My Droid 4 is rebooting after every few minutes, it is entirely unusable. As well, it is unwilling to accept my SIM card. IDK what happened, what triggered it, nor how to fix it. What I have done so far:
1. While rooted and using a lighter stock rom (myfishbear I believe), the phone started these loops. I turned it off, entered safestrap recovery and wiped dalvik, cache, and data. Rebooted, problems still occur.
2. Changed ROM to AOKP, reboots stop however SIM card does not function at all.
3. Changed back to stock, reboots continue, SIM card still not functioning.
4. Changed to CM10 patched to definitely work with GSM carriers (olegfusion's patch). SIM does not work. Not recognized, phone not connecting to network.
5. Went to "safe" system (if I understand correctly), the stock stock vanilla ICS system. Reboots continue, SIM still not working. Factory reset, dalvik wiped as well.
6. Decided to try to fastboot a recovery as a last resort. Fastboot works, however the problem still exhibits itself. SIM not working, reboots continue, and I cannot pass the activation screen to be able to try anything else.
Can anyone please help me? I saved any and all bug reports that were on internal before doing anything, I also created backups of the ROMs before going ahead and reflashing the thing. I have no idea what to do anymore
I've found out what is making it crash. Somehow the radio is not working anymore. I've tried fastboot flash radio radio.img, however it fails. Here is the log:
Code:
-- Install /cache ...
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
Formatting of Cache is required
Reading input Flash image....
Registering bp flash device
Registering lte flash device
Searching for flash devices...
Unable to find flash devices
Retry flashing
Searching for flash devices...
Unable to find flash devices
Retry flashing
Searching for flash devices...
Unable to find flash devices
Retry flashing
script aborted: assert failed: motorola.motoflash("/tmp/bp.img")
assert failed: motorola.motoflash("/tmp/bp.img")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory); trying /dev/block/mmcblk0
E:failed to mount /sdcard (No such file or directory)
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Please someone help me out! Is this a hardware problem? Can it be fixed with a flash to an older radio.img? Are there custom radio.img's out that are known to fix this problem? Is there a way for me to fix it myself? Am I sending it in to Moto?
I just installed CyanogenMod using the instructions from the CM wiki using the latest STABLE release.
When I booted my device, it was stuck on the CyanonMod loading screen (blue looping circle). I've wiped and reinstalled multiple times but cannot fix the problem.
I used the ClockWordMod "show log" command from the advanced menu, and got this:
I : Can't partition non-vfat: datamedia
I : Can't partition non-vfat: auto
I : Can't format unknown volume: /emmc
mount: mounting /dev/block/platform/msm/sdcc.1/by-name/userdata on /data failed: Invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (Invalid argument)
The last line probably refers to my attempt to wipe the dalvik cache
I've noticed that CWM can't mount /data
Solved by installing TWRP recovery. Apparently CWM does not support encrypted partitions.
I have an HTC One M8, and I installed Cyanogenmod 12.1 (I followed their guide and did HTCdev Unlock). For a little while, LTE was working fine with my phone, but then about a couple of weeks ago, my LTE connection stopped working, and it hasn't worked since. So ultimately that's the problem I'm looking to solve.
I had backed up my HTC factory ROM and restored that to see if LTE would work there. That's when I found that it wants me to do an update, but the update reboots me into TWRP and doesn't work. My thought is that to solve this, I will need to apply the update somehow, and if that's the case, then I could use some help figuring out how to do that. (I'm trying to run "Update Profile".)
If you have other ideas of what I can do to fix LTE, then I'm open to hearing them as well.
Thanks!
You need to install stock recovery to enable the update to install.
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
komi_9 said:
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
Click to expand...
Click to collapse
Yup sounds correct except being you are on 2.16 there will be a few updates you will need to do to get current.
I went through the process, and each step went fine (you were right about having to update a few times), but LTE is still not working in CM when I switched back over. It is working on the Stock ROM side of things; that's how I did my OTA update. (At least it says LTE in the status bar, so I assume that's what it's using, as opposed to just defaulting to LTE but switching to 3G when LTE is not present.)
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Thanks for the help again!
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
Click to expand...
Click to collapse
I don't use CM so can't answer but yeah your best bet would be to ask in their forum.
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Click to expand...
Click to collapse
If you took all the update to make you current you should have the latest stock recovery. You can always pull the stock recovery from the latest Full Firmware zip.
HK = Harmon Kardon Edition
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
komi_9 said:
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
Click to expand...
Click to collapse
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Sloth said:
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Click to expand...
Click to collapse
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
komi_9 said:
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
Click to expand...
Click to collapse
Have you updated your twrp recently?
I have 2.8.7.0 downloaded from here: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
komi_9 said:
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
Click to expand...
Click to collapse
Yes that might be the problem. A full wipe shouldn't wipe anything important.
If you have a backup and you need to use it you will be back to the ROM you made the backup of.
Sent from a Glade Plugin.
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
komi_9 said:
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
Click to expand...
Click to collapse
V7.4.2 is not the latest version...try the latest and see if it makes a difference. Usually status 7 error means the updater script is out of date (if I remember correctly).
When I do a full wipe I choose Advance Wipe then check the boxes next to cache/dal cache/data/system. From my experience wiping in twrp and then wiping again in Aroma usually causes problems. I prefer the twrp method myself.
I also put anything I'm going to flash on the EXT sdcard.
The 7.4.3 version is only available as a patch to 7.4.2 as far as I can tell. The full download is only available in 7.4.2. Or at least that's all I see.
Anyway, the point is moot now since I seem to have gotten LTE working. I went into APN settings and the option CDMA 0 was selected. Any of the other options pop me over to the Sprint LTE Internet option, but that one will just sit there and not work. I'm not quite sure how I got stuck on that APN. But oh well, since it's working now.
I really appreciate all the help! One day I might embark on trying out different ROMs again, but for now I'm happy that CM is working out OK.
Cool glad you got it sorted.