Database Info

Error upgrading to Gingerbread!

Hey guys,
Every time I try to install the "Monster_2.3.2_4.5.153_updater_Rooted.zip" ROM from Droid Life the install aborts with an error message and I have nothing left to do but to remove the battery and reinsert it. When I do that however, I get to the boot loader with an error message and I have to revert to the stock SBF and re-root my phone, re-bootstrap recovery, boot in recovery, and try again - I'm feeling lucky. I have done this about seven or eight times, nine as we speak, and so far with absolutely no success. I would really like to know if I am doing something wrong here, I have installed other ROMs with success such as Fission and Liberty.
The last few lines of error message in the installer were as follows:
...
Unmounting Systen ...
updatinig radio image ...
assert failed: motorola.update_cdma_bp("/tmp/rdl.bin", "/tmp/bp.img")
E:Error in /sdcard/Monster_2.3.2_Rooted.zip
(Status 7)
Installation aborted.
---
The Device being used is a Droid 2 Global with the stock SBF running.
And that is all that I get, this problem has repeated itself many times and I have tried installing the above ROM while having another version and ROM installed both with no success. Any help is greatly appreciated.

Have you tried to apply that monster.zip file from the Bootstrap Recovery app & choose the option to choose the zipfile?
Do you have it in the root of the /sdcard directory?

[Q]OTA update to BJ failed

Hi Guys，
System version 0.7.2.xt926.Verizon.en.US
Android version 4.0.4
System has been ROOT
I want to update the Android to 4.1.1 from OTA. After download the update program,press "update now", the phone restart and update,but a few minutes，the phone restart.But update failure.The Android version still 4.0.4.
Then I change to use default Recovery to update.I used 2 ways:
1、use “apply update from external storage”
The update failure and show the information as follow
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
2、use "apply update from cache"
The update failure too and show the information as follow
assert failed：apply_patch_check("/system/app/BooksTablet.apk","1932fde58cef592d0ff957b1be0c22fe2afd912b","0d8c659f9228f05a774f1182f35ef1bf57eafb41")
E: Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Does anyone know the reason? Many thanks!

Gavin.Sun said:
Hi Guys，
System version 0.7.2.xt926.Verizon.en.US
Android version 4.0.4
System has been ROOT
I want to update the Android to 4.1.1 from OTA. After download the update program,press "update now", the phone restart and update,but a few minutes，the phone restart.But update failure.The Android version still 4.0.4.
Then I change to use default Recovery to update.I used 2 ways:
1、use “apply update from external storage”
The update failure and show the information as follow
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
2、use "apply update from cache"
The update failure too and show the information as follow
assert failed：apply_patch_check("/system/app/BooksTablet.apk","1932fde58cef592d0ff957b1be0c22fe2afd912b","0d8c659f9228f05a774f1182f35ef1bf57eafb41")
E: Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Does anyone know the reason? Many thanks!
Click to expand...
Click to collapse
My OTA update to JB initially failed to but my phone went into boot loop, I was able to get into safe mode and then do a factory data reset (after another 4 attemps to get past a boot loop) then the phone booted up and I was on JB.

XRCIST said:
My OTA update to JB initially failed to but my phone went into boot loop, I was able to get into safe mode and then do a factory data reset (after another 4 attemps to get past a boot loop) then the phone booted up and I was on JB.
Click to expand...
Click to collapse
Thank you for your reply, I'll try it after backup.

You can't do an OTA update if youre rooted with safestrap. You need to download voodoo and hide root, then uninstall safestrap.
If that still doesn't work (it probably won't because it didn't for me either), back up all your info and flash back to stock 4.0.4. Then install only superuser and voodoo, hide your root and download BOTH OTA updates before attempting to install safestrap and unhiding root.
Good luck
Sent from my DROID RAZR HD using xda app-developers app

OTA Update fails.

After a couple of tries to apply the 4.1.2 update, I decided to leave it alone, and root my device using CWM.
Problem is, once I succesfully used fastboot and restarted in CWM mode, the update which was previously stored is coming up, and now it gives this failure message:
E: signature verification failed
Installing update...
assert failed: getprop ("ro.product.device") == "
E: Error in /cache/Blur_Version.98.1.18002.XT925.Vodafone.en.FR.zip
(Status 7)
Installation aborted.
Now, my phone keeps restarting! and it tries to update to no avail. What can I do to stop this? Or even better, to make it work.

xdmatt said:
After a couple of tries to apply the 4.1.2 update, I decided to leave it alone, and root my device using CWM.
Problem is, once I succesfully used fastboot and restarted in CWM mode, the update which was previously stored is coming up, and now it gives this failure message:
E: signature verification failed
Installing update...
assert failed: getprop ("ro.product.device") == "
E: Error in /cache/Blur_Version.98.1.18002.XT925.Vodafone.en.FR.zip
(Status 7)
Installation aborted.
Now, my phone keeps restarting! and it tries to update to no avail. What can I do to stop this? Or even better, to make it work.
Click to expand...
Click to collapse
Hey can you tell me what "CWM" is? Thanks!

erj-drvr said:
Hey can you tell me what "CWM" is? Thanks!
Click to expand...
Click to collapse
To my understanding, ClockWorkMod.
I still need to find how to apply the update. I found a zip file, apparently it's the update that someone pulled off of their phone, but it gives me the same fail message

xdmatt said:
To my understanding, ClockWorkMod.
I still need to find how to apply the update. I found a zip file, apparently it's the update that someone pulled off of their phone, but it gives me the same fail message
Click to expand...
Click to collapse
Thanks....ClockWorkMod as in Rom Manger? Rom Manager was great....used it on my Evo!!

Problem with OTA

Hi, I am having problem updating htc sensation xe. When I start installing the update, it stops and I get a red triangle(with exclamantion mark). I haven't rooted the phone, neither have I installed any custom recovery.
When I go in to recovery mode I get this
Copying fotaBoot to /data/system for customise reload.
..
verifying current system....
assert failed: apply_patch_check("/system/app/BackupRestoreConfirmation.apk", '..............some combination of letters and numbers .........)
E:error in /sdcard/download/OTA_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153-3.33.401.106_release_281163td4zljtgipkwlha4.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse

[Q] cyanogen mod 10.1.3 RC2 fails install with "status 7"

I am super excited to see an official cyanogenmod for the photon Q 4G LTE. I quickly installed the motorola drivers for the phone, android sdk, unlocked the bootloader with motorola's unlocker, installed ClockworldMod Recovery 6.0.1.3 using fastboot.
Now using cw recovery I am trying to flash cm-10.1.3-RC2-xt897c.zip off my external SD card. The process starts fine buts ends up giving an error.
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /external_sd/cm-10.1.3-RC2-xt897c.zip
(Status 7)
Installation aborted.
I get the same result regardless if I "wipe data/factory reset", "wipe cache partition", and "advanced/wipe dalvik cache".
According to a google search, the status 7 means the rom does not think it is compatible with the phone its being installed to. Well, I checked META-INF/com/google/android/updater-script.txt as described and it contains an entry for
Code:
getprop("ro.product.device") == "xt897c" || getprop("ro.build.product") == "xt897c");
.
It seems like everything checks out. Any ideas why the install is failing?

nezzer said:
I am super excited to see an official cyanogenmod for the photon Q 4G LTE. I quickly installed the motorola drivers for the phone, android sdk, unlocked the bootloader with motorola's unlocker, installed ClockworldMod Recovery 6.0.1.3 using fastboot.
Now using cw recovery I am trying to flash cm-10.1.3-RC2-xt897c.zip off my external SD card. The process starts fine buts ends up giving an error.
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /external_sd/cm-10.1.3-RC2-xt897c.zip
(Status 7)
Installation aborted.
I get the same result regardless if I "wipe data/factory reset", "wipe cache partition", and "advanced/wipe dalvik cache".
According to a google search, the status 7 means the rom does not think it is compatible with the phone its being installed to. Well, I checked META-INF/com/google/android/updater-script.txt as described and it contains an entry for
Code:
getprop("ro.product.device") == "xt897c" || getprop("ro.build.product") == "xt897c");
.
It seems like everything checks out. Any ideas why the install is failing?
Click to expand...
Click to collapse
If it was not compatible, you would get an "assert failed", not "status 7" (I would think?)
If you think it is the assert that is failing, remove that line. Also, that updater-script file shouldn't be a .txt file - it should have no file extension.
In googling that error, everyone does seem to agree tho that status 7 is a mismatch, so I spose try removing that line. I usually would get an 'assert failed' message if these didn't match up - but I use TWRP, maybe that's the difference.

Bad to worse. I had booted the phone multiple times into recovery trying to apply the firmware. No matter what, when I later try to boot the OS, it just stayed stuck at the "boot loader unlocked" warning message, presumably because the firmware was never applied successfully. I left the phone at that screen overnight connected to the computer via USB.
Today I figured I would go ahead and try flashing TWRP to see if that changed anything. Now I am unable to get the phone to power on at all. Pressing the power button has no effect. Same for pressing vol down + pwr. When I plug it into USB the LED turns green but nothing happens on the display. Running adb devices or fastboot devices both say nothing is connected.
The thing appears completely dead. I took the case off and unscrewed the battery terminals for 5 minutes before screwing them back on. Still nothing. The display backlight never powers on.
This is a real bummer. Anyone run across anything like this before?
*Update* It would appear that the phone was not charging when stuck at the bootloader unlocked warning screen despite being connected to my PC. I left my phone on the charger for about 10 minutes and it popped back on to the bootloader unlocked screen. I was able to reboot to the fast boot screen. Since the state is reported as "battery low" I cant flash anything. I will report back once I can flash TWRP.

Mystery solved.
I flashed openrecovery-twrp-2.6.3.0-asanti_c.img and tried installing cm-10.1.3-RC2-xt897c.zip again. No go. Thankfully twrp has some nice features including a great file manager. I tried chmod 777 on the cm zip. No change. I then copied the cm zip from my external sd card to the internal memory. This failed a number of times before it went through successfully. That was my first clue.
I was able to flash cm from the internal sd card no problem. My guess is that my external SD card is experiencing read errors which caused the prior flash attempts to fail. Its working now.

I thought those problems have been solved and/or are nearly not existent.
My SD-Card became defective a few month after using it with my Photon Q. (Got a replacement within warranty.)
I guess that the Photon Q is kind of sensible which mSD's are working and which not.
My current mSD is working flawlessly.
But I flash nearly everytime over the internal storage, just to be sure that I don't get "invisible read errors" during flashing.
You should check your file, a hash may be the way to go.
I had problems with TWRP and CWM with my old mSD. (The flash process was terribly long.)
OpenRecovery was much faster but some flashes were still with issues.