i just purchased a bell nexus and used the toolkit to root and recovery, created a backup, then donwloaded cm9 nightly. when trying to flash, i get an error regarding [get.prop] or something like that. how can i fix this? thx u in advance
i just reflashed clockwork from rom maanger then tried again for the same issue. the error says
assert failed: getprop9"ro.product.device") == "maguro" || getprop("ro.bwild.product")
anyone?
Sounds like it checking your model # and its getting a mismatch. What is the model # of your phones?
i got the rom flashed. i was trying to flash the gsm rom on my bell phone. but my issue is this. bell uses gsm signal but its a cdma enabled phone. so i can flash the cdma enabled rom but how can a cdma rom use a gsm baseband?
not to sure the model number, it just says galaxy nexus
but the working baseband is 19250ugkl1
Hi Guys,
So I am trying to update my 4.0.4 ICS to 4.1.1 JB .
My Nexus is unlocked and rooted , I am using nexus tool kit 1.5v for everything .
I do flash zip w/Temp CWM ( which is the latest version with touch )
but no luck I do get the below error every time .
I have re flashed the radio and bootloader since I thought there is a problem with those but nothing changed please Help.
assert failed: getprop("ro.build.device") == "maguro" ¦¦ getprop("ro.build.device") == "maguro"
E:Error in /sdcard/yakju-JRO03C - FROM - IMM76I.f946a412 (2).zip
(Status 7 )
installation aborted.
Are you using the correct radio for yakju? I updated to 4.1.1 from 4.0.4 yakju last night. First I flashed the correct radio for yakju, which I hadn't realised that I hadn't already done so when I switched from yakjus to yakju back in April.
I am using : Baseband version I9250 XXLA2
I think this is the correct one for 4.0.4 .
Yes, that's the correct radio.
Sent from my Galaxy Nexus using xda app-developers app
Use the regular CWM version instead of the touch one. CWM touch is buggy.
Yup it worked as you say , I used the non touch version.
Please keep in mind that NExus root tool kit 1.5 is coming with the touch version which caused the problem.
Thanks a lot again for the advice.
Cheers
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
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!
Can't seem to find an answer to my question, and I've been at this since 9:00 this morning.
Tried to OTA 4.4 update my AT&T SGS3 last night, and the update soft bricked the phone. Initially I could get it to the spinning Death Star logo, but would freeze up at that point. After hours of trying almost anything, I installed clockwork custom recovery. Had it wipe all data, and now it hangs at the Samsung Galaxy SIII boot screen. Trying to install Cyanogenmod from sideload (since I can't get a 4.3 ROM to work because Kies won't recognize the device), but that errors off telling me "assert failed: getprop ("ro.product.device"). I followed the suggestion to remove the first line from the updater-script file, but now I just get "assert failed: getprop ("ro bootloader") for multiple bootloaders. When I tried to load an updated bootloader, I get the above error, which shows no device (it just says "this is a " and leaves it at that).
I've tried multiple bootloaders and multiple Cyanogen packages (both stable and nightly). What am I missing? Or am I out of luck? Any help is appreciated.
I'm assuming you are on 4.3 since you tried to update via Ota. Try flashing this from recovery. 4.3 custom stock rom I found in development section.
https://www.androidfilehost.com/?fid=23212708291681250
Or verify your current firmware build using adb or the built in terminal emulator in recovery.
Enter this:
getprop ro.bootloader
If it returns a 4.3 build you can flash the MJB firmware found in the general section. Flash with Odin.
Sent from my SAMSUNG-SGH-T999 using Tapatalk