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

[Q] Problem Installing Roms

I've tried installing various custom roms (and versions) and they all seems to fail. The only successful flashes I've managed have been stock roms from this page. This is the log from when I attempted to install CM 10.2 in TWRP 2.6.6.3:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
I:Cannot find file /data/media/0/sideload.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: assert failed: getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" || getprop("ro.product.device") == "m7ul" || getprop("ro.build.product") =="m7ul"
assert failed: getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" || getprop("ro.product.device") == "m7ul" || getprop("ro.build.product") == "m7ul"
E:Error executing updater binary in zip '/data/media/0/sideload.zip'
Anyone recognise these errors?

robtherobot101 said:
I've tried installing various custom roms (and versions) and they all seems to fail. The only successful flashes I've managed have been stock roms from this page. This is the log from when I attempted to install CM 10.2 in TWRP 2.6.6.3:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Anyone recognise these errors?[/QUOTE]
CM10 is really old are you sure that's what you want ? and it may require a special version of recovery .. check the developers thread
[QUOTE]First time installing CyanogenMod 10.2 to your HTC One (GSM), or coming from another ROM:
- Read the official wiki
- Unlock your device via http://www.htcdev.com
- [COLOR="Red"]Flash the latest official ClockworkMod-Recovery via Fastboot[/COLOR]
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
[/QUOTE]
Click to expand...
Click to collapse

Here's the result of flashing CM 11:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
I:Cannot find file /data/media/0/sideload.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
mount: failed to mount /dev/block/mmcblk0p35 at /system: Device or resource busy
about to run program [/tmp/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 11
run_program: child exited with status 127
Creating filesystem with parameters:
Size: 1946152960
Block size: 4096
Blocks per group: 32768
Inodes per group: 7920
Inode size: 256
Journal blocks: 7423
Label:
Blocks: 475135
Block groups: 15
Reserved block group size: 119
Created filesystem with 11/118800 inodes and 15607/475135 blocks
minzip: Extracted file "/system/addon.d/50-cm.sh"
minzip: Extracted file "/system/addon.d/blacklist"
minzip: Extracted file "/system/app/Apollo.apk"
...
minzip: Extracted file "/system/xbin/strace"
minzip: Extracted file "/system/xbin/su"
minzip: Extracted file "/system/xbin/vim"
about to run program [/tmp/backuptool.sh] with 2 args
/tmp/backuptool.sh: cd: line 99: can't cd to /tmp/addon.d/
md5sum: can't open '*sh': No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
cp: can't stat '/tmp/addon.d/*': No such file or directory
script result was [/system]

On reboot TWRP reports that no OS is installed and the phone boots to a black screen

robtherobot101 said:
On reboot TWRP reports that no OS is installed and the phone boots to a black screen
Click to expand...
Click to collapse
Here is how to flash CM on the M7
just in case...
http://wiki.cyanogenmod.org/w/Install_CM_for_m7

What would cause the stock roms flash without a problem but all custom roms install improperly?

robtherobot101 said:
What would cause the stock roms flash without a problem but all custom roms install improperly?
Click to expand...
Click to collapse
Using the wrong custom recovery

TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working

robtherobot101 said:
TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working
Click to expand...
Click to collapse
Yeah, I'm not sure what's up with that. But it's for sure the reason why the other roms aren't working

When I bought the phone(supposedly brand new) the bootloader was locked but it was already S-OFF and had CID:11111111. The writing on the box is in German(I live in New Zealand) so I guess whoever I bought it off had fixed that for me...

Just in case anyone ever stumbles upon this thread in the distant future, let it be known that I managed to install this rom successfully and it's got all the useful features you'd expect from Cyanogenmod (and a few more).

robtherobot101 said:
Just in case anyone ever stumbles upon this thread in the distant future, let it be known that I managed to install this rom successfully and it's got all the useful features you'd expect from Cyanogenmod (and a few more).
Click to expand...
Click to collapse
or you just install maximus HD 50.0.0. this rom is super !

robtherobot101 said:
TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working
Click to expand...
Click to collapse
This is the exact same problem I have only the 2 recoveries you mentioned work for me too, I've tried updating to newer versions of TWRP but it gets stuck on the HTC Logo with "entering recovery" at the top, I have the international version I also had to replace the screen because it smashed maybe that has something to do with it.

Update error! HELP

So I'm running Scotts Clean ROM 5.1 (Tmo LMY47M)
ROM is amazing and runs perfectly. However, lately I've been getting prompted to update (OTA) to 5.1.1
I get this error in recovery.....
Installing '/cache/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: Package expects build fingerprint of google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy03260016:eng/test-keys.
Source: google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
Target: google/shamu/shamu:5.1.1/LYZ28E/1914015:user/release-keys
Verifying current system...
Package expects build fingerprint of google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy03260016:eng/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/cache/update.zip'
E:Error installing zip file '/cache/update.zip'
Done processing script file
I just did a clean install (wiped EVERYTHING), and still getting this error in recovery.
Does anyone know where it's looking for this because it's not in my build.prop
Thanks in advance.

ecatsab said:
So I'm running Scotts Clean ROM 5.1 (Tmo LMY47M)
ROM is amazing and runs perfectly. However, lately I've been getting prompted to update (OTA) to 5.1.1
I get this error in recovery.....
Installing '/cache/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: Package expects build fingerprint of google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy03260016:eng/test-keys.
Source: google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
Target: google/shamu/shamu:5.1.1/LYZ28E/1914015:user/release-keys
Verifying current system...
Package expects build fingerprint of google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy03260016:eng/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/cache/update.zip'
E:Error installing zip file '/cache/update.zip'
Done processing script file
I just did a clean install (wiped EVERYTHING), and still getting this error in recovery.
Does anyone know where it's looking for this because it's not in my build.prop
Thanks in advance.
Click to expand...
Click to collapse
You can no longer take ota's. You are already running what you want. just ignore it. otherwise you can use fastboot to update the files without fastboot flashing userdata and you are set.

[Q] [SOLVED] Error flashing rom (blkdiscard failed invalid argument)

Hi all,
I got error blkdiscard failed invalid argument while flashing [ROM][MI3/Mi4][CM-12.1][Android-5.1.1]CM-Cancro.
Many said that I had to extend partition to 1.2GB, which I already did. I can install Temasek rom with extended
partition, but failed with Bitti09 rom.
Here is what I have did before
-flash r11 cwm
-manually extend partition
-script extend partition
-flash TWRP
all step above failed to install [ROM][MI3/Mi4][CM-12.1][Android-5.1.1]CM-Cancro.
Now running with audahadi Temasek rom.
Here is my log from TWRP
PHP:
Installing '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
minzip: Extracted 4 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...blockimg version is 2
erasing 318848 blocks
script aborted: blkdiscard failed: Invalid argument
blkdiscard failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'
Error flashing zip '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'
Updating partition details...
Please help...

Finally I have solved this problem. Yes "blkdiscard failed: Invalid argument" is error of unsuitable partition space to install a rom.
Initially my partition was like this
system = 1242 MB (1.2GB)
system1= 100 MB
After google and reading most comment from partition thread, I found out there is three version of system partition size which is 730MB, 1242MB and 1337 MB.
I found that @audahadi partition script use
system = 1337 MB
system1= 5MB
Quote:
Originally Posted by audahadi
This Procedure May Will Brick Your Device!!!!!
Only for users who comfort with single partition layout only !!!
This is a script to partiton your system partition as like stated in OP. Tested with Clockworkmod recovery.
How to use? Just flash through recovery on either partition. Remember, this will wipe your system partition, do backup for safe or no if you like to live dangerously.
Repartition_MI3W_1_2GB.zip
Credit :
http://forum.xda-developers.com/show....php?t=2765846
http://forum.xda-developers.com/gala...-data-t2762594
Click to expand...
Click to collapse
So using that script, i have succeed install CM based rom.

sorry but could you please elaborate!! I don't get it.. how could I see my partitions?! and how can I change them?!
sorry for being noob.

Go to google play and install Disc Info app. You can see your partition
Sent from my MI 3W using XDA Forums

Can you give me the link for system = 1337 MB
system1= 5MB partition?

Here you go
http://forum.xda-developers.com/attachment.php?attachmentid=3321267&d=1432050198
Sent from my MI 3W using XDA Forums

How to install Stagefright fix on rooted XT1068

Hi,
so I'm having a little bit of a problem with my Moto G 2nd Gen. Dual SIM 2014 (XT1068). I got the notification for the Stagefright fix update a few days ago, but every time I try to install it the installer throws an error after the progress bar is at about 40%.
Now I've found the cause. In /cache/recovery/last_log it says that /system/bin/app_process32 has an unexpected SHA1 sum. The log:
Code:
Finding update package...
I:Update location: /cache/Blur_Version.22.26.1.titan_retde.retdeall.en.DE.zip
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1462 bytes; signature 1439 bytes from end
I:whole-file signature verified against RSA key 0
I:verify_file returned 0
Installing update...
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/platform/msm_sdcc.1/by-name/system , file system type :ext4Verifying current system...
file "/system/bin/app_process32" doesn't have any of expected sha1 sums; checking cache
file size of "/system/bin/app_process32" is 75364
sha1 of "/system/bin/app_process32" is f29d36738da21a7cef064326462d9d9e527ba121
expected sha1 is: fb3a1cfd2e27dd648cb7ae44b9283147ce44c5f1
c0dd7831406b1e243282a46983d4440578600417
402935808 bytes free on /cache (75364 needed)
dumping bad file /system/bin/app_process32 to /cache/recovery/last_badfile
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/app_process32" has unexpected contents.
"/system/bin/app_process32" has unexpected contents.
E:Error in /cache/Blur_Version.22.26.1.titan_retde.retdeall.en.DE.zip
(Status 7)
Installation aborted.
Installation aborted.
I:Saving locale "en_GB"
Rebooting...
The phone has an unlocked bootloader and was rooted with SuperSU but otherwise unmodified (I needed the root for the Sixaxis Controller). Some forum posts I found mentioned that the "Xposed Framework" is probably the cause, but I did not install that.
... I've found the original file in /system/bin/app_process32_original but system-recovery.sh also has a backup and was definitely modified by SuperSU
So I guess the question is: how can I install the Stagefright update without losing root?
System Version: 22.26.1.titan_retde.retdeall.en.DE retde
Update Version: 22.56.3.en.DE

drunken_m said:
Hi,
so I'm having a little bit of a problem with my Moto G 2nd Gen. Dual SIM 2014 (XT1068). I got the notification for the Stagefright fix update a few days ago, but every time I try to install it the installer throws an error after the progress bar is at about 40%.
Now I've found the cause. In /cache/recovery/last_log it says that /system/bin/app_process32 has an unexpected SHA1 sum. The log:
Code:
Finding update package...
I:Update location: /cache/Blur_Version.22.26.1.titan_retde.retdeall.en.DE.zip
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1462 bytes; signature 1439 bytes from end
I:whole-file signature verified against RSA key 0
I:verify_file returned 0
Installing update...
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/platform/msm_sdcc.1/by-name/system , file system type :ext4Verifying current system...
file "/system/bin/app_process32" doesn't have any of expected sha1 sums; checking cache
file size of "/system/bin/app_process32" is 75364
sha1 of "/system/bin/app_process32" is f29d36738da21a7cef064326462d9d9e527ba121
expected sha1 is: fb3a1cfd2e27dd648cb7ae44b9283147ce44c5f1
c0dd7831406b1e243282a46983d4440578600417
402935808 bytes free on /cache (75364 needed)
dumping bad file /system/bin/app_process32 to /cache/recovery/last_badfile
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/app_process32" has unexpected contents.
"/system/bin/app_process32" has unexpected contents.
E:Error in /cache/Blur_Version.22.26.1.titan_retde.retdeall.en.DE.zip
(Status 7)
Installation aborted.
Installation aborted.
I:Saving locale "en_GB"
Rebooting...
The phone has an unlocked bootloader and was rooted with SuperSU but otherwise unmodified (I needed the root for the Sixaxis Controller). Some forum posts I found mentioned that the "Xposed Framework" is probably the cause, but I did not install that.
... I've found the original file in /system/bin/app_process32_original but system-recovery.sh also has a backup and was definitely modified by SuperSU
So I guess the question is: how can I install the Stagefright update without losing root?
System Version: 22.26.1.titan_retde.retdeall.en.DE retde
Update Version: 22.56.3.en.DE
Click to expand...
Click to collapse
unroot or flash stock firmware from my signature

reefuge said:
unroot or flash stock firmware from my signature
Click to expand...
Click to collapse
Thanks, but that was exactly what I didn't want to do. But well, I still did it.
Unrooted (that reverted the necessary files back to normal),
Installed the update,
Rooted again with CF AutoRoot.

I need help!
drunken_m said:
Thanks, but that was exactly what I didn't want to do. But well, I still did it.
Unrooted (that reverted the necessary files back to normal),
Installed the update,
Rooted again with CF AutoRoot.
Click to expand...
Click to collapse
Hello , I am Brazilian and I wonder exactly how you installed the update . The XT1068 and I 'm having the same problem , however I can not solve. (Using the Google Translate)

drunken_m said:
Thanks, but that was exactly what I didn't want to do. But well, I still did it.
Unrooted (that reverted the necessary files back to normal),
Installed the update,
Rooted again with CF AutoRoot.
Click to expand...
Click to collapse
Thank but in which way i can unroot it ?
Thank
Hispa

Hi,
I'm using SuperSU which has an option to remove itself.
SuperSU -> Settings -> Cleanup
There you can choose between "Switch superuser app" or "Full unroot".
I used "Switch superuser app", that was enough for me to install the system update.