where is ro.product.name - Android Q&A, Help & Troubleshooting

okay smart people this should be easy. i'm trying to install firmware (update.zip) and i need to get passed
assert(getprop("ro.product.name") == "P752D01_Cosmote_GR");
in the updater-script.
so the phone reboots into recovery, found and validated update.zip but it gets to product name and looks for P752D01_Cosmote_GR. but it's in recovery mode so i'm guessing it's not using build.prop to get this name (i tried changing build.prop anyway) and my default.prop only contains the following
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
so where is it getting my product name from?!
rooted KIS Lite v790
-cheers

---

anybody?

---

knifey_au said:
anybody?
Click to expand...
Click to collapse
I think that you should use grep.

---

tux-86 said:
I think that you should use grep.
Click to expand...
Click to collapse
i'll look for something like that for android otherwise i guess i'll... pull everything using adb which i don't really know how to do yet and use some windows version of grep

---

It is in your build.prop that can be found in /system ROM toolbox has an easy editor for the build.prop and that is probably the easiest way to do it. You can get it from the play store for free. A lot of flashable ROMs begin by checking to make sure that the device and the ROM are compatible and it usually checks the product name. SInce this is missing from your build.prop the flashing is aborted. So you can also fix your problem by deleting the get assert in the updater.script of your zip. It will be the first set of lines and looks something like this:
assert(getprop("ro.product.device") == "e730" || getprop("ro.build.product") == "e730" ||
getprop("ro.product.device") == "e739" || getprop("ro.build.product") == "e739");
Could be longer depending on your zip and may also check more than just ro.build.product.
Be a little bit careful doing this, you should be absolutely sure that the ROM you are flashing and your device are compatible because you could really bork your device.

---

justmpm said:
It is in your build.prop that can be found in /system ROM toolbox has an easy editor for the build.prop and that is probably the easiest way to do it. You can get it from the play store for free. A lot of flashable ROMs begin by checking to make sure that the device and the ROM are compatible and it usually checks the product name. SInce this is missing from your build.prop the flashing is aborted. So you can also fix your problem by deleting the get assert in the updater.script of your zip. It will be the first set of lines and looks something like this:
assert(getprop("ro.product.device") == "e730" || getprop("ro.build.product") == "e730" ||
getprop("ro.product.device") == "e739" || getprop("ro.build.product") == "e739");
Could be longer depending on your zip and may also check more than just ro.build.product.
Be a little bit careful doing this, you should be absolutely sure that the ROM you are flashing and your device are compatible because you could really bork your device.
Click to expand...
Click to collapse
yeah i said i already changed build.prop to match the assert in the zip and it's still stopping at that point in the install

---

I need build.prop for LG E 960 (Nexus 4)...please help me

---

knifey_au said:
yeah i said i already changed build.prop to match the assert in the zip and it's still stopping at that point in the install
Click to expand...
Click to collapse
I'm in the same situation as you, did you find out where its getting the ro.product.device from?

---

kr1shna said:
I'm in the same situation as you, did you find out where its getting the ro.product.device from?
Click to expand...
Click to collapse
Check META-INF/com/google/android/updater-script
These getProp() were in the first line itself.