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
Related
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!
Help! I can't install cm11 to my Samsung Galaxy S3 it keeps saying
assert failed: getprop("ro.bootloader") == "T999UVUENC2"
also im on Android 4.3 jb
What recovery are you using?
I suggest to flash a newer version of your recovery
Sent from my GalaxyS III
Cm11 Not Working On S3
I was using TWRP 2.7.1.0
What is your device model and current firmware build? (Not the rom, but the firmware)
In terminal emulator enter
getprop ro.bootloader
deal all
after fixing the hard bricked i found another problem there are no IMEI or baseband so i could not to mobile network
My phone is :-S3 SGH-I747 (Unlocked sim)
so how to solve this ,
restore imei and baseband
Well, I did a couple of weeks ago was to find a restoring image.
Here it is https://www.androidfilehost.com/?w=files&flid=21292 , here you can download the modem and image, flash both CWM! .
The files no are mine, just like I share the way I found it, good luck! Jeje sorry for my english, Greetings let me know if you could
Here is the modem, just flash with cwm, and download the ucu4_restore and the same, flash! Good luck
I ran through a recovery with the download you provided. Was working fine, then after the "preparing to Flash Baseband UCUFNE4" I got an error:
"assert failed: getprop("ro.bootloader") == "I747UCUFNE4"
E: Error in /data/media/ATT_GALAXYS3_UCUFNE4_Modem.zip
(Status 7)
Installation aborted."
Can someone please help me restore my IMEI and Baseband back onto my Galaxy S3. This almost worked, but then got the error.
vishulm said:
I ran through a recovery with the download you provided. Was working fine, then after the "preparing to Flash Baseband UCUFNE4" I got an error:
"assert failed: getprop("ro.bootloader") == "I747UCUFNE4"
E: Error in /data/media/ATT_GALAXYS3_UCUFNE4_Modem.zip
(Status 7)
Installation aborted."
Can someone please help me restore my IMEI and Baseband back onto my Galaxy S3. This almost worked, but then got the error.
Click to expand...
Click to collapse
Do you know what bootloader and modem you had on your phone prior to your problems? Knowing that is important for determining how to proceed. Samsung made this phone easy to brick messing with bootloaders or getting mismatched firmware.
You can install the Phone Info Samsung app by vndnguyen to get the bootloader and modem.
Or you can enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
jason2678 said:
Do you know what bootloader and modem you had on your phone prior to your problems? Knowing that is important for determining how to proceed. Samsung made this phone easy to brick messing with bootloaders or getting mismatched firmware.
You can install the Phone Info Samsung app by vndnguyen to get the bootloader and modem.
Or you can enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
Click to expand...
Click to collapse
My bootloader was I747UCUFNJ2
PDA Version: I747ucdlk3
CSC Version I747ATTDLK3
IMEI and Baseband is missing/removed.
Does that help?
Go here
https://forum.xda-developers.com/ga...ile-sgh-i747ucufne4v4-4-2attall-odin-t3305899
and scroll down to the 3rd post where you can download the NE4 Odin files off chuckles google drive. Then go get a copy of Odin. You will be connecting your phone to your PC for this. This process will get your baseband back, but you will lose everything as flashing these files is like doing a factory data reset.
Yes I know you're on NJ1 or 2, but this will jump you back to NE4 and you can just use TWRP to get back to NJx if you want. Personally I have my s3 stuck on NE4 because it can use towel root.
vishulm said:
My bootloader was I747UCUFNJ2
PDA Version: I747ucdlk3
CSC Version I747ATTDLK3
IMEI and Baseband is missing/removed.
Does that help?
Click to expand...
Click to collapse
I agree with @StoneyJSG. That odin flashable full firmware update he linked is your best bet.
It will downgrade your bootloader to NE4 and match it up with the NE4 modem, but that has been proven safe. We used to think you couldn't downgrade this phone's bootloader at all after the MJB (jellybean I think) firmware, but it turns out once you're on a kitkat booloader (NE4, NJ1, NJ2) you can downgrade as long as you don't try to roll back to something earlier than kitkat.
I have successfully used that to downgrade from NJ1 to NE4 for a full phone restore, and others have reported rolling back from NJ2 in that thread.