Develop Bugs

[Q] Froyo update fails

Background:
I have an unbranded desire, which I rooted using Unrevoked 3.
For some reason, my phone says it's up to date, though I'm still running android 2.1.
Problem:
I downloaded froyo from the net (tried two versions, one which is 86,491kb and one which is 92,262kb), I tried updating using the recovery option, but I always get the following error dialogue:
"Install from sdcard...
Finding update package...
Installing update...
assert failed: file_getprop("system/build.prop"
, "ro.build.fingerprint") == "sprint/htc_supersonic/supersonic/supersonic:2.1-update1/ERE27/195459:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "sprint/htc_supersonic/supersonic/supersonic:2.2/FRF91/218634:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted."
If I enable the signature verification it fails with a signature verification failed error.
I'm going crazy already trying to update, would be glad to hear any suggestions,
Thanks,
Joel

You CAN'T upgrade on a rooted phone with the OTA update
Your choice is unroot and suffer the buggy OTA Froyo rom or rejoice and install a custom rom that has many fixes for Froyo already applied

sbdags said:
You CAN'T upgrade on a rooted phone with the OTA update
Your choice is unroot and suffer the buggy OTA Froyo rom or rejoice and install a custom rom that has many fixes for Froyo already applied
Click to expand...
Click to collapse
what's the best and most stable ROM and how's the best way to go about installing it?Cheers BTW i've got a rooted Desire which is unbranded and unlocked original.Just got it rooted today.

See the other thread where I answered this question but you should try Neophyte 1.6 which is the best Froyo Rom imo or Pays Rock Solid if you want a great 2.1 rom.

I had exactly this problem here is my thread
http://forum.xda-developers.com/showthread.php?t=748105
Hope it helps

why so many of you suggest Neophyte 1.6?

Update to Jelly Bean aborts (Status 7)

I've been trying to update to Jelly Bean, but every time I run the update in Clockwork 5.5.0.2, it fails with:
Code:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/takju/maguro:4.0.4/IMM30D/262866:user/release-keys" || takju.maguro:4.1/JRN84D/392829:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
What am I doing wrong? I have a GSM version and I'm pretty sure its the takju version as I bought it on the first day they released in the Google Play store. If there is a way to verify this, could someone tell me or point to a place that tells me?

Which .zip are you trying to flash? If its the official OTA you must be on IMM30D.

Yeah, I'm trying to use the official OTA... how would I go to IMM30D if I'm currently on IMM76I? I didn't see an image for IMM30D or anything on their factory images page.

It's not listed because IMM30D is a non-retail image.
Check out this sticky for instructions. http://forum.xda-developers.com/showthread.php?t=1737899

Same Problem with Yakju
I'm having the exact same problem with my GNEX GSM. I've got the YAKJU version, rooted, and i'm getting the same error message Status 7 Installation aborted. I tried to do the update via OTA when it came to my phone but it failed and since then I havent't been able to do it via OTA. I've even hard reset my phone and still no go via OTA or Manually. running CWM 5.5.0.2

[Q] Newbie stuck flashing JB onto Rogers i747m

1st time posting and rooting/flashing, so please be gentle...
Followed this link and successfully rooted my Rogers GS3 with the GS3 Toolkit (chose the #9 "Canada Rogers SGH-i747M" option when selecting phone).
Made nandroid backup successfully.
Now trying to flash latest CM10 build (cm-10-20121111-NIGHTLY-d2att.zip) from here: http://get.cm/?device=d2att using these instructions but the install fails pretty much immediately with this error:
assert failed: getprop ("ro.product.device) == "d2att" ||getprop("ro.build.product") == "d2att" E:Error in /sdcard/cm-10-20121111-NIGHTLY-d2att.zip (status7)
would be very grateful to anyone who can tell me what I am doing wrong and how to actually get CM10 on my phone.
Thanks in advance!

I received that error using an older version of cwm. Updated to current and fixed the issue. Not sure if twrp supports cm10 based roms.
Sent from my SAMSUNG-SGH-I747M

Trying to install CM10.1 Wont instal because I have newest bootloader.

So apparently I made the mistake of updating my phone to the new 4.1.2 rom.
I decided I wanted to give CM 10.1.2 a try, so I followed a tutorial on youtube on how to install it through TWRP.
Everything went fine without a hitch, until it came to actually flashing CM 10.1.2 and gapps.
It will leave a error similar to
Code:
assert failed: getprop("ro.bootloader") == "I747UCDLK3" |
| getprop("ro.bootloader") == "I747MVLCLK4" |
| getprop("ro.bootloader") == "I747MUMBLK3"|
| getprop("ro.bootloader") == "I747MUMBLL1"|
Which after some research is due to CM checking the bootloader version and rejecting it if it is not the "latest JB version". So my only guess is that it does not recognize the new 4.1.2 bootloader.
So now my only option is to somehow downgrade the bootloader, unless they release a updated 10.1.2 release to recognize the new bootloader.
What would be the best way to downgrade the bootloader? Could I just simply flash the 4.1.1 stock ROM with ODIN? Or am I just stuck without CM now? XD

Can't Update CM

Galaxy S3 SGHi747m on Bell (same as AT&T)
CM 11 (using installer)
My phone/the installer says I have an update but every time I attempt to install it automatically reboots into recovery, has an error and reboots to my current CM version. I've updated with the installer before without any problems, everything was automatic and easy.
I tried downloading the most recent snapshot and installing the zip from sdcard manually and it throws me an error as well.
Any idea what's going on here? My phone's data usage says the CM has eaten up 460mb of my data with this update that won't install.
Goal here is to not wipe my phone, yes I have a nandroid backup and yes I backup with TitaniumPro but it is still a pain in the ass restoring everything, especially SMS, various ringtones, etc.

Try installing a custom recovery such as TWRP or Philz Touch and dirty flash CM11.

audit13 said:
Try installing a custom recovery such as TWRP or Philz Touch and dirty flash CM11.
Click to expand...
Click to collapse
No luck with TWRP, I get the same error, i downloaded the correct zip again from download.cyanogenmod.com just to make sure it wasn't the file.
This is the error:
E: Error executing updater binary in zip '/sdcard/Download/cm-11-20140210-SNAPSHOT-M3-d2att.zip'
Error flashing zip '/sdcard/Download/cm-11-20140210-SNAPSHOT-M3-d2att.zip'

Try Philz Touch. It is based on cwm.

audit13 said:
Try Philz Touch. It is based on cwm.
Click to expand...
Click to collapse
Tried, still failed to update. Same error.. this is the entire string:
- - Installing: /sdcard/Download/cm-11-20140210-SNAPSHOT-M3-d2att.zip
Finding update package...
Opening update package...
Installing update package...
assert failed: getprop ("ro.bootloader") == "I747UCDMG2" | |
getprop ("ro.bootloader") == "I747UCEMJ2" | |
getprop ("ro.bootloader") == "I747UCEMJB" | |
getprop ("ro.bootloader") == "I747MVLDMF1" | |
getprop ("ro.bootloader") == "I747MVLUEMK5"
E: Error executing updater binary in zip '/sdcard/Download/cm-11-20140210-SNAPSHOT-M3-d2att.zip'
Error flashing zip '/sdcard/Download/cm-11-20140210-SNAPSHOT-M3-d2att.zip'
(Status 7)
Installation aborted
Thanks audit13, your help is appreciated!

Looks like your bootloader is not supported by the ROM. The ROM is looking for one of the bootloaders listed in your error message.

audit13 said:
Looks like your bootloader is not supported by the ROM. The ROM is looking for one of the bootloaders listed in your error message.
Click to expand...
Click to collapse
well that's weird, any way to fix/re-unlock the bootloader without wiping the phone?

To make sure it is a bootloader problem, determine the bootloader on your phone and compare it to the bootloaders in the error message. If you bootloader matches a bootloader in the list, there may be another problem.

audit13 said:
To make sure it is a bootloader problem, determine the bootloader on your phone and compare it to the bootloaders in the error message. If you bootloader matches a bootloader in the list, there may be another problem.
Click to expand...
Click to collapse
Under 'About Phone' it says my Baseband version is I747MVLDLK4, so yea it doesn't correspond to the list

You probably have a 4.1.1 bootloader. CM11 needs a 4.1.2 bootloader on the i747m. I recommend not updating to stock 4.3 because the update will install knox.
I run a 4.1.2 bootloader and have not had any problems loading Kit Kat ROMs.
You'll probably need an updated modem/radio to go with the updated bootloader. I don't know that there is a separate update to the i747m bootloader that can be flashed in Odin or via CWM. The easiest way may be for backup everything using Titanium Backup, install a stock 4.1.2 ROM via Odin, install Philz Touch via Odin, flash CM11, and restore your apps via Titanium Backup.
Although the i747 amd i747m are virtually identical, do not cross flash bootloaders as that may brick your phone.

audit13 said:
You probably have a 4.1.1 bootloader. CM11 needs a 4.1.2 bootloader on the i747m. I recommend not updating to stock 4.3 because the update will install knox.
I run a 4.1.2 bootloader and have not had any problems loading Kit Kat ROMs.
You'll probably need an updated modem/radio to go with the updated bootloader. I don't know that there is a separate update to the i747m bootloader that can be flashed in Odin or via CWM. The easiest way may be for backup everything using Titanium Backup, install a stock 4.1.2 ROM via Odin, install Philz Touch via Odin, flash CM11, and restore your apps via Titanium Backup.
Although the i747 amd i747m are virtually identical, do not cross flash bootloaders as that may brick your phone.
Click to expand...
Click to collapse
I started before i saw your post, using the i747m bootloader and modem from the following:
http://forum.xda-developers.com/showthread.php?t=2321310
http://forum.xda-developers.com/showthread.php?t=1831898
Installed each in recovery
Attempting to install CM11 update now, everything seems to be going good so far.
Thanks so much for the help, I'm curious as to how the bootloader got messed up, but if it works then that's all that matter... and actually the install is complete without error!
Thanks!