[Q] Updating to JB - RAZR i Q&A, Help & Troubleshooting

I'm on 12012 and I decided to upgrade to 20003 to later upgrade to JB. I've moved the OTA to the root of the SDcard and flashed through the stock recovery and it says :
Instaling update...
file_getprop: failed to stat "/system/build.prop": no such file or directory
E:Error in /tmp/sideload/package.zip
(Status 7)
What can I do now ? I'm on Retail BR.
Thanks to all who answer.
EDIT
WTH it's not even booting now...

Related

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

Clockwork Issues

Installing Rom Manager, did the Flash Recovery.....worked fine.
Created backup, it went into the recovery menu and gave me this:
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
--Applying Multi-CSC...
Installing Multi- CSC
Installation aborted
--Install from sdcard...
Finding update package
Opening update package
Verifying update package
E:failed to verify whole-file signature
E:signature verification aborted
Installation aborted.
Also does this when I try to flash a new rom from the internal sd (of course)
Any ideas?!?
("stock" rom i897ucji6)
JamesAK said:
Installing Rom Manager, did the Flash Recovery.....worked fine.
Created backup, it went into the recovery menu and gave me this:
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
--Applying Multi-CSC...
Installing Multi- CSC
Installation aborted
--Install from sdcard...
Finding update package
Opening update package
Verifying update package
E:failed to verify whole-file signature
E:signature verification aborted
Installation aborted.
Also does this when I try to flash a new rom from the internal sd (of course)
Any ideas?!?
("stock" rom i897ucji6)
Click to expand...
Click to collapse
What are you trying to flash?
Are you on the leaked froyo? You say Ji6. If you are the problem is because the recovery on that rom does not have a 2e recovery. I would stock flash through Odin then try to flash the rom
Captivate
Cog 2.2
Ahh that was the deal alright.....reverted to the stock eclair and everything fell right into place
THANK YOU MUCH!!!

[Q] set_metadata_recursive: some changes failed

Code:
set_metadata_recursive: some changes failed
E: Error in /storage/sdcard1/Gummy-M2.2-06-07-14-NIGHTLY-moto_msm8960.zip
(Status 7)
Installation aborted.
help pls!
Djullo said:
Code:
set_metadata_recursive: some changes failed
E: Error in /storage/sdcard1/Gummy-M2.2-06-07-14-NIGHTLY-moto_msm8960.zip
(Status 7)
Installation aborted.
help pls!
Click to expand...
Click to collapse
There's a Q & A Area that's appropriate for questions.....
Mine did that to, had to redownload it....something about how downloading a rom from a busy server while 2 Netflix steams are going on in the house can corrupt a download....

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.

I get a error in /tmp/sideload/package.zip (status 7) when every I try to flash

Hello guys, I was wondering if someone could take the time to help me out?
I'm trying to flash the Nightowl-cm13-beta3-n7000 rom onto my N7000, but I get the error message
Code:
error in /tmp/sideload/package.zip (status 7)
I also get the same error when trying to flash CyanogenMod Build 11 builds.
I did a little bit of gooling and tried the fix from androidgadgematic.com/2012/12/fix-custom-rom-installation-status-7.html of removing the first 3 lines of code, but that just give me a new error:
Code:
E: failed to verify whole-file signature
E: failed to verify whole-file signature
E: signature verification failed
Some info on my phone that may or may not help:
Model number GT-N7000
Android version 4.1.2
Baseband version N7000XXLT3
Kernel version 3.0.31-1103517
Install a kernel with newer recovery like bauners cm 11 or 12 then boot into that recovery and flash the new ROM. Keep in mind after flashing a kernel from another ROM you will not be able to boot into ROM so make backups prior to installing.

Categories

Resources