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

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.

Related

What's wrorg with this rom?

when i'm flashing[JB 4.1.1][AOSP+CM] Jellybean 4.1.1 PreAlpha2
CWM show's some thing like this:
Code:
finding update packge.........
opening update packge.........
installing update .........
assert failed: getprop("ro.product.device") =="
ST18i" ││ getprop("ro.build.product") == "ST18i"
││ getprop("ro.product.device") =="ST18
a" ││ getprop("ro.build.product") == "ST18a" ││
getprop("ro.product.device") =="urushi"
││ getprop("ro.build.product") =="urushi"
E:error in /sdcard/szl-urushi_jellybean-pre.alph
a_1.zip
(status 7 )
Installation aborted
can some one help me(teach me how can i flash this rom)?
(also i have this question on cm9 rc1,2

urushi my love said:
when i'm flashing[JB 4.1.1][AOSP+CM] Jellybean 4.1.1 PreAlpha2
CWM show's some thing like this:
Code:
finding update packge.........
opening update packge.........
installing update .........
assert failed: getprop("ro.product.device") =="
ST18i" ││ getprop("ro.build.product") == "ST18i"
││ getprop("ro.product.device") =="ST18
a" ││ getprop("ro.build.product") == "ST18a" ││
getprop("ro.product.device") =="urushi"
││ getprop("ro.build.product") =="urushi"
E:error in /sdcard/szl-urushi_jellybean-pre.alph
a_1.zip
(status 7 )
Installation aborted
can some one help me(teach me how can i flash this rom)?
(also i have this question on cm9 rc1,2
Click to expand...
Click to collapse
Hi I don't know anything about 'building roms' etc so I might be way of but from my 'troubleshooting' expirience I would say the following:
- If you have this problem on Jelly Bean & CM9 it's probably your phone that has the problem?
- If I read the error message I would somehow say that CWM thinks your phone is not a Xperia Ray (urushi) ST18a/i

your download is corrupt, try downloading again.
Sent from my ST18i using xda premium

Open up zip file. Head to meta-inf/Google/android/updater script edit with notepad++ and delete the 1st 3 lines.
They are there to make sure your installing it on the right device. But if your build.prop says different, then it will not flash.
Sent from my Xperia Ray using xda premium

this may fix your problem
have u download a differnt costum room?? ok try this one, that maybe something wrong in google script, open ur different room, make copy for that,,
after that, copy all that file system instead JB room, to replaced all system in another package room that you have, then flash again that new room, its donw...
tested on my ray..

*boy*racer* said:
Open up zip file. Head to meta-inf/Google/android/updater script edit with notepad++ and delete the 1st 3 lines.
They are there to make sure your installing it on the right device. But if your build.prop says different, then it will not flash.
Sent from my Xperia Ray using xda premium
Click to expand...
Click to collapse
Yeah he is correct. Status 7 and 6 errors are due to problems with updater script.
Sent from my ST18i using xda app-developers app

urushi my love said:
when i'm flashing[JB 4.1.1][AOSP+CM] Jellybean 4.1.1 PreAlpha2
CWM show's some thing like this:
Code:
finding update packge.........
opening update packge.........
installing update .........
assert failed: getprop("ro.product.device") =="
ST18i" ││ getprop("ro.build.product") == "ST18i"
││ getprop("ro.product.device") =="ST18
a" ││ getprop("ro.build.product") == "ST18a" ││
getprop("ro.product.device") =="urushi"
││ getprop("ro.build.product") =="urushi"
E:error in /sdcard/szl-urushi_jellybean-pre.alph
a_1.zip
(status 7 )
Installation aborted
can some one help me(teach me how can i flash this rom)?
(also i have this question on cm9 rc1,2
Click to expand...
Click to collapse
Man, just install stock ICS ROM first, and then install CM9 or JB4.1.1 ROM (do not format \system partition. only \datd and \cache)
That's 'cause your previous ROM changed your device ID in build.prop to something that is not ST18i. And up[dater script will not let you install ROM on not apropriate device.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
Knight47 said:
Yeah he is correct. Status 7 and 6 errors are due to problems with updater script.
Sent from my ST18i using xda app-developers app
Click to expand...
Click to collapse
It's not problem with updater script. it's problem in ugly custom ROM

Nothing of the above didn't worked for me! And rom was not the problem either.
Here is the solution! http: // androidtweak.in/rom/cyanogenmod/install-cm9-1latest-stable-in-xperia-2011-devices/
(spaces in link cause i'm new to forum and i can't post links......)

have done it
*boy*racer* said:
Open up zip file. Head to meta-inf/Google/android/updater script edit with notepad++ and delete the 1st 3 lines.
They are there to make sure your installing it on the right device. But if your build.prop says different, then it will not flash.
Sent from my Xperia Ray using xda premium
Click to expand...
Click to collapse
hey i have done it but again it give status 7 error
help

Try re downloading the rom(removing the three lines have never worked for me). Or u could try using another recovery.

[GUIDE] How to Port I9100 ICS or JB ROMS

Just thought I'd write up a flashing guide for people who love to use I9100 ROMS like myself. First the things you'll need before you start the porting process:
Notepad++
Winrar/7zip
For ICS ROMS:
Download an I9100 ROM of your choice
Download a kernel (Siyah (ICS)/Skyfire(ICS)/Fluxi(ICS))
Open the zip files (don't extract) and copy the zimage to your desktop
Change the sec_touchkey.kl found in system/usr/keylayout of your ROM zip
Change the modem.bin with either UCLE5 or UCKH7
Go to system and edit the build.prop, edit these particular lines exactly as shown using Notepad++(optional):
ro.product.model=SGH-I777
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.build.product=SGH-I777
Click to expand...
Click to collapse
Go to META-INF/com/google/android and open updater-script with Notepad++ and check if these line are there:
assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" ||
getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T");
Click to expand...
Click to collapse
Delete them, if not skip this step
Delete the zImage from the ROM zip and replace it with one from Siyah/Skyfire or Fluxi
You can replace the hosts found in system/etc for ad blocking
The red highlighted items can be found at bottom of post (Not for flashing)
Flash the ROM
For JB ROMS:
Download an I9100 ROM of your choice
Download a kernel Siyah (JB) or use extract boot.img from CM10/AOKP ROMS
Open the zip files (don't extract) and copy the zimage (for CM10/AOKP found in the respective ROM root directory) to your desktop
Change the sec_touchkey.kl found in system/usr/keylayout of your ROM zip
Go to system and edit the build.prop, edit these particular lines exactly as shown using Notepad++(optional):
ro.product.model=SGH-I777
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.build.product=SGH-I777
Click to expand...
Click to collapse
Go to META-INF/com/google/android and open updater-script with Notepad++ and check if these line are there:
assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" ||
getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T");
Click to expand...
Click to collapse
Delete these lines
Go to system/lib and replace the modules folders with the one provided
You can replace the hosts found in system/etc for ad blocking
The red highlighted items can be found at bottom of post (Not for flashing)
Additional:
To boot a zImage for JB ROMS if you replace the boot.img
You must edit this lines in the updater-script
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5"),
delete("/tmp/boot.img"));
Click to expand...
Click to collapse
To look like this:
assert(package_extract_file("zImage", "/tmp/zImage"),
write_raw_image("/tmp/zImage", "/dev/block/mmcblk0p5"),
delete("/tmp/zImage"));
Click to expand...
Click to collapse
In general just look for an assert near the bottom of the script and edit it to reflect the zImage and it will boot properly. Alternatively skip this step and just flash the kernel after flashing the ROM
Enjoy the ROMS in the I9100 Original and Android Development section and happy flashing

Do you need to be on a Unix system for this? Windows doesn't like the filenames (things ending in both "a" and "A" for example).
Edit: Oops, dropped a parentheses.

You don't need unix or a special system for this just Notepad++ and winrar/7 zip which are free and easy to find

Alright, looks like the duplicate filename error is a 7-Zip thing, WinRAR looks to be working ok.
Could you elaborate some on what to do with the Siyah kernel "zImage"? When I open the Siyah file there is the META-INF folder, a flash_image and a zImage file; however in the root of my ROM there is only a "boot.img".
Is something happening here that I'm missing:
"Open the zip files and copy the zimage (for CM10/AOKP found in the respective ROM root directory) to your desktop"
It looks like it could be much easier than that and it's just "replace boot.img with zImage and edit the assert... to reflect the changes". Is it really that simple?

IconRunner said:
Alright, looks like the duplicate filename error is a 7-Zip thing, WinRAR looks to be working ok.
Could you elaborate some on what to do with the Siyah kernel "zImage"? When I open the Siyah file there is the META-INF folder, a flash_image and a zImage file; however in the root of my ROM there is only a "boot.img".
Is something happening here that I'm missing:
"Open the zip files and copy the zimage (for CM10/AOKP found in the respective ROM root directory) to your desktop"
It looks like it could be much easier than that and it's just "replace boot.img with zImage and edit the assert... to reflect the changes". Is it really that simple?
Click to expand...
Click to collapse
Exactly, in Siyah zip just drag and drop the zImage, to your desktop for example, and in your ROM delete the boot.img, and insert the zImage in the root directory of ROM zip
then edit the updater-script as shown above so it boots from zImage and not boot.img, you can also just highlight boot.img and CTRL+F and replace all instances of boot.img with zImage. Yes it really is that simple
Also I found this awesome theme, thought I'd share:
http://forum.xda-developers.com/showthread.php?t=1931948

loco_jow said:
Awesome, I will give this a try today :fingers-crossed:
Edit: Thanks "asasione", I have successfully ported Paranoid Android 2.22 using your guide. Although my phone was acting a little sluggish at first, it is now working smoothly. The latest Siyah kernel did not work for me neither. Thanks again asasione.
Click to expand...
Click to collapse
Did you use the JB version cause I'm also on Paranoid Android and I've had no issues with it
Download v4.3.3 - CM10/AOKP MALI - CWM Flashable
WITH mic swap
http://www.mediafire.com/?tdgw4376kq0xrpz
Click to expand...
Click to collapse

When using winrar to zip roms back up for flashing do we use the "store" option?
JB 4.1.2 Rootbox Nightlies
Ktuned Siyah kernel Sooo Smoooose
I777 SGS2

Thanks, I used the procedure to port the Rootbox JB Rom. So far no problems! I am looking forward to porting others.

Thanks you very much! I'm needing

stevehkim said:
When using winrar to zip roms back up for flashing do we use the "store" option?
JB 4.1.2 Rootbox Nightlies
Ktuned Siyah kernel Sooo Smoooose
I777 SGS2
Click to expand...
Click to collapse
There's no need to zip ROMS back up, just open the zip don't extract and make your changes by dragging and dropping the files according to the guide and editing some files and flash the ROM, its pretty straight forward

asasione said:
There's no need to zip ROMS back up, just open the zip don't extract and make your changes by dragging and dropping the files according to the guide and editing some files and flash the ROM, its pretty straight forward
Click to expand...
Click to collapse
Yes,straight forward. Your guide works a treat. Nicely done. Now I prepare all i9100 ROMs before transfer to phone. No more after flash of kernels or other device specific files. Thank you asasione!

This method worked for me. The only thing I didn't do was change the boot image and flashed the kernel after the ROM which is an option. I will try replacing the boot img the next time. But the method allowed me to port my desired I9100 JB ROM to the I777without a problem. Thanks!

I have ported i9100 roms before but decided to use your great instructions since it has been awhile.
Thanks to you I'm rockin' AOKP Build 5 right now!!

Can't someone create a hellraiser like entropy instead of flashing kernel, modem and keylibs every time?
ShoStock ROM/ Flexreaper relix GT rev 1.1

anikiup said:
Can't someone create a hellraiser like entropy instead of flashing kernel, modem and keylibs every time?
ShoStock ROM/ Flexreaper relix GT rev 1.1
Click to expand...
Click to collapse
At no point are the kernel or anything else I attached meant for flashing they are simply zipped files, if you read the instructions they are supposed to be added and to replace the i9100 files within the zip, simple drag and drop, once you've ported a few ROMS it will take you less than 5mins doing it your own

Is there a way to go back to an original i777 ROM after being hell raised without reverting to stock first I always get build prop and status 7 errors when trying
Sent from my SGH-I777 using xda app-developers app

bocephus007 said:
Is there a way to go back to an original i777 ROM after being hell raised without reverting to stock first I always get build prop and status 7 errors when trying
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
And I'm assuming u searched that error and found a ton of information on what to do and how to fix it? I know that's what happens when I search for it

Can anyone confirm that this method will work for porting the XXLSJ leak in the i9100 forums?

ou812bkewl said:
Can anyone confirm that this method will work for porting the XXLSJ leak in the i9100 forums?
Click to expand...
Click to collapse
I just asked that question as well in siyah thread, no it won't work...

Will the JB porting steps mentioned work for the leaked 4.1.2 I9100 ROM from the below link
http://forum.xda-developers.com/showthread.php?t=1998205
I observed the below
1. sec_touchkey.kl file does not exist in system\usr\keylayout\ folder
2. there are no similar files (mentioned in moudles.rar) to be replaced in system\lib folder
3. Can we use Siyah 4.3.3 kernel in this leaked rom.
Please let me know.
I tried your ICS porting steps they worked Great!.. I very much appreciate you tutorial.

This guide will help u flash more better

assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
You do this with 7-Zip/WinRAR
Note: DO NOT EXTRACT ROM!
In the ROM go to:
/META-INF/com/google/android/updater-script
1)Open updater-script with a script editor such as notepad/notepad++ (makes things 10x easier), or gedit if you use linux
2)Delete the first line of code (all the way up to the first semicolon you see) and delete the first semi-colon as well
Do not go past the first semiclon when deleteing and DO NOT forget to delete the first semicolon.
Cheers!
Sent from my SPH-L710 using Tapatalk

lox2013 said:
assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
You do this with 7-Zip/WinRAR
Note: DO NOT EXTRACT ROM!
In the ROM go to:
/META-INF/com/google/android/updater-script
1)Open updater-script with a script editor such as notepad/notepad++ (makes things 10x easier), or gedit if you use linux
2)Delete the first line of code (all the way up to the first semicolon you see) and delete the first semi-colon as well
Do not go past the first semiclon when deleteing and DO NOT forget to delete the first semicolon.
Cheers!
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Please be careful doing this. The "assert getprop" is meant to keep you from flashing the wrong ROM onto your device. Flashing a ROM for a different device can really mess up your hardware. Only do this, if you are sure that the ROM you want to flash is the right one for your device and if you know why you are getting this error. For example you edited your build.prop so that you could mimic another device.

Here is my question I follow what it said but when I try to flash it it says installation aborted I did everything even I got my ROM here is virgin mobile l710
Sent from my SPH-L710 using Tapatalk

No incoming calls on recent CM12/other 5.x ROMs

Wondering if anyone else is having problems with incoming calls not arriving on Lollipop nightlies over the last few weeks.
I have been updating official CM12 nightlies every week or two, so sometime around 3/15 I would have installed a nightly and could still receiving calls, just as I had been before. Then I installed the 3/29 nightly (based on files in my Downloads folder) and since then I have not received a single incoming call (evidenced by call logs showing last incoming call on 3/27). I can make outbound calls fine, but incoming calls don't even show up on my phone; it is like the call never happened, but I get the voicemail notification if they choose to leave one. The callers say the call rings 4-6 times then goes to voicemail as if I just didn't answer, and it happens with every caller, not just certain ones.
I tried wiping data with no luck, also tried clean-flashing a few other nightlies from the last two weeks including 4/14 and it still doesn't work. Swapped SIMs with my wife (we both have i605's being used on T-Mobile) and incoming calls to my SIM worked on her phone, calls to her did not ring on my phone so it is something phone-related, not network related. Nightlies from before 3/29 seem to be deleted from the CM Downloads page so I can't go back and test CM12 nightlies that I know worked, but I installed the CM11 M10 (KK) snapshot and can receive calls, so I know it has to do with recent Lollipop builds - the problem is that nobody else has issues (other than a few issues with certain OPO nightlies a while back) so I can't find a fix.
I thought maybe it was just CM12 but other ROMS (PAC-MAN 4/8 and CyanideL 4/14) still have problems, presumably because they pull code from CM. I checked logcats and the phone doesn't give any indication that the call is even coming through the network, but the SIM swap shows that it isn't a network issue.
Is anyone else experiencing any of these problems? I don't want to go back to KK if I can get this working, but it seems to be leaving me no choice.

Yes I have a Verizon Note 2 unlocked using a net 10 At&t service sim card and after cm12 build 3/26
all calls go straight to voice mail with out notification or ringing. Other people are having this same problem on other phones too. I believe its in the telephone stack with the changes that were made. I believe we can revert the changes that were made and or flash the few files affected over the new builds. I cant get the rom to extract fully under windows the exe is giving my a python error and I have not had time to try it on my Linux machine.
Any one interested in helping figure this out, message me. I let you know How you can help and then we can post back in here

opalelement said:
Wondering if anyone else is having problems with incoming calls not arriving on Lollipop nightlies over the last few weeks.
Click to expand...
Click to collapse
I have the same problem on my i605. I've done factory reset, wiped everything, flashed the latest nightly (cm-12.1-20150511-NIGHTLY-flo.zip) and pa_gapps-stock-5.1-20150418-signed.zip to no avail.
Incoming calls still ring several times and then go to voicejail. Another anomaly is that outgoing calls don't want to hang up. Calling my bank's voice menu system or leaving a voice mail requires me to power-off or reboot the phone to terminate the call. Calls will end if the other end hangs up.
I've reverted to cm-12-20150130-NIGHTLY-i605.zip via a ROM copy found on AndroidHost at which does have a working phone section. I can't post a link as yet, but searching for "cm-12-20150130-NIGHTLY-i605.zip" will lead you to it.

Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.

jobren said:
Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.
Click to expand...
Click to collapse
Thank you ever so much! It worked to get my i605 back on the air as a CM 12.1 phone. There are some oddities such as the Settings->Security page missing Screen lock and the Owner info bits. Hopefully the developers will find and fix the phone issues in the i605 nightlies. For now my plan is to try the latest nightly every two weeks and revert back if there's no joy.

wiitwd said:
Thank you ever so much! It worked to get my i605 back on the air as a CM 12.1 phone. There are some oddities such as the Settings->Security page missing Screen lock and the Owner info bits. Hopefully the developers will find and fix the phone issues in the i605 nightlies. For now my plan is to try the latest nightly every two weeks and revert back if there's no joy.
Click to expand...
Click to collapse
Any good news? I noticed lots of updates going on in the nughtlies. I myself didn't get much luck with the nightly one week before.

jobren said:
Any good news? I noticed lots of updates going on in the nightlies. I myself didn't get much luck with the nightly one week before.
Click to expand...
Click to collapse
As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.

I am in the same boat. Any way other than described to get back to calling abilities? Like downgrading to KK maybe? I am in baseband MJ9

harjotsandhu said:
I am in the same boat. Any way other than described to get back to calling abilities? Like downgrading to KK maybe? I am in baseband MJ9
Click to expand...
Click to collapse
wiitwd said:
As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.
Click to expand...
Click to collapse
I tried the given method with 13 July 2015 nightly and it works. Saved my life. I upgraded my MJ9 baseband to ND7 with no effect. Only the given around is working.

jobren said:
Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.
Click to expand...
Click to collapse
I must be doing something Wrong, I copy the lines above and paste them into the appropriate file updater-script. just add the line in with the other very similar ones. Save the file and rezip it and flash using latest TWRP but It always fails. I tried blisspop and Cyanide L. from note 2 ATT forum. Does this only work with CM nightly s? any information would be appreciated
RJ

wiitwd said:
As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.
Click to expand...
Click to collapse
I have some new information. When using the i605 nightlies, telephony fails to hang up calls or to receive incoming calls while in a GSM service area, e.g., Guam. Now that I'm back stateside in CDMA/LTE land, the i605 nightlies work great. I offer as a working hypothesis, therefore, that GSM telephony is broken in the i605 nightlies. When I go back in October I'll bring the latest modified t0lte nightly as well as my GTA SIM card.

RJ803 said:
I must be doing something Wrong, I copy the lines above and paste them into the appropriate file updater-script. just add the line in with the other very similar ones. Save the file and rezip it and flash using latest TWRP but It always fails. I tried blisspop and Cyanide L. from note 2 ATT forum. Does this only work with CM nightly s? any information would be appreciated
RJ
Click to expand...
Click to collapse
I have not tried with other ROMs. It definitly works.
Might worth it to have a look at the file in I605 and check the difference.
Sorry I couldnt upload my file. It seems that I do not have the rights to upload files yet. :silly:

jobren said:
Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.
Click to expand...
Click to collapse
I've tried this a couple of times and the flash always fails quickly at "updating partition details." I've downloaded the cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte.zip, found the updater-script (in \cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte\META-INF\com\google\android) edited the file by adding in the getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || (added it right after the getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || entry. Saved the file and zipped the folder. Transfered back to the phone and tried to flash from recovery (TWRP v2.8.1.0), which is where things failed.
I'm pretty much a complete noob at this. I've only flashed my phone one time previously, and that was after a lot of false starts. So it is very likely I'm making a very basic error, but I'd appreciate any guidance given.

dmcgregor said:
I've tried this a couple of times and the flash always fails quickly at "updating partition details." I've downloaded the cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte.zip, found the updater-script (in \cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte\META-INF\com\google\android) edited the file by adding in the getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || (added it right after the getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || entry. Saved the file and zipped the folder. Transfered back to the phone and tried to flash from recovery (TWRP v2.8.1.0), which is where things failed.
I'm pretty much a complete noob at this. I've only flashed my phone one time previously, and that was after a lot of false starts. So it is very likely I'm making a very basic error, but I'd appreciate any guidance given.
Click to expand...
Click to collapse
Any chance that someone who has successfully done this could upload their updater-script file? I've tried a few different variations without any luck getting it to flash. Right now I'm stuck between going back to a known insecure version of Android, or not being able to receive calls, hoping for a 3rd option.

dmcgregor said:
Any chance that someone who has successfully done this could upload their updater-script file? I've tried a few different variations without any luck getting it to flash. Right now I'm stuck between going back to a known insecure version of Android, or not being able to receive calls, hoping for a 3rd option.
Click to expand...
Click to collapse
OK. Let's try this.
The following is the content of my script file. Copy it into a empty txt file and rename it as 'updater-script'.....Here we go.
assert(getprop("ro.product.device") == "t0lte" || getprop("ro.build.product") == "t0lte" || getprop("ro.product.device") == "t0ltexx" || getprop("ro.build.product") == "t0ltexx" || getprop("ro.product.device") == "GT-N7105" || getprop("ro.build.product") == "GT-N7105" || getprop("ro.product.device") == "t0ltedv" || getprop("ro.build.product") == "t0ltedv" || getprop("ro.product.device") == "GT-N7105T" || getprop("ro.build.product") == "GT-N7105T" || getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || getprop("ro.product.device") == "SGH-I317" || getprop("ro.build.product") == "SGH-I317" || getprop("ro.product.device") == "t0ltetmo" || getprop("ro.build.product") == "t0ltetmo" || getprop("ro.product.device") == "SGH-T889" || getprop("ro.build.product") == "SGH-T889" || getprop("ro.product.device") == "t0ltecan" || getprop("ro.build.product") == "t0ltecan" || getprop("ro.product.device") == "t0ltevl" || getprop("ro.build.product") == "t0ltevl" || getprop("ro.product.device") == "SGH-I317M" || getprop("ro.build.product") == "SGH-I317M" ||getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || abort("This package is for device: t0lte,t0ltexx,GT-N7105,t0ltedv,GT-N7105T,t0lteatt,SGH-I317,t0ltetmo,SGH-T889,t0ltecan,t0ltevl,SGH-I317M; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/SYSTEM", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/USERDATA", "/data", "");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/dw_mmc/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/SYSTEM", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/dw_mmc/by-name/BOOT");
show_progress(0.200000, 10);

A belated thanks as I'm just now seeing this. After struggling to get this to work for a few weeks I ended up rolling back to CM 11. But I'll give another try with CM 12.1 today and let you know how it goes. Either way I greatly appreciate you taking the time to post this.

No dice. Copied the text above into notepad. Saved it over the original updater script. Zipped everything back up and tried to flash, but it failed right away on "updating partition details." No clue what I'm doing wrong. Could it be my recovery? I'm using TWRP 2.8.1.0, which seems to work fine for flashing the i605 version.

Emmm…i really don't know now. I have been using this file for several months without any issue. I dont think it is the recovery, either…Could be some details in the formating of the script…or our phones are actually different…
BTW…how many posts it needs to unlock the attachments feature?

With the rom zip on your phone download and use ES file explorer. Locate your zip long press it then click the more button. then click extract and press ok. Navigate to the the META-INF\com\google\android\ folder and then long press on the file updater-script and then click rename and then ad .txt to the end so the file is now called updater-script.txt then click ok.
then click on updater-script.txt and open with es file editor. click the pencil in the top right corner to edit text. Then select the text I have shown here
Code:
assert(getprop("ro.product.device") == "epic4gtouch" ||
getprop("ro.build.product") == "epic4gtouch" ||
getprop("ro.product.device") == "SPH-D710" ||
getprop("ro.build.product") == "SPH-D710" ||
getprop("ro.product.device") == "d710" ||
getprop("ro.build.product") == "d710" ||
getprop("ro.product.device") == "smdk4210" ||
getprop("ro.build.product") == "smdk4210" ||
getprop("ro.product.device") == "SPH-D710VMUB" ||
getprop("ro.build.product") == "SPH-D710VMUB" ||
getprop("ro.product.device") == "SPH-D710BST" ||
getprop("ro.build.product") == "SPH-D710BST" ||
abort("This package is for device: epic4gtouch,SPH-D710,d710,smdk4210,SPH-D710VMUB,SPH-D710BST; this device is " + getprop("ro.product.device") + "."););
you want to sop at the ) + ".");
and right before the ifelse mount statement. delete the code above.
then press your back button once and then click save. Then RENAME updater-script.txt back to updater-script. press your back button a couple of time till you get back to the folder that has all the extracted files and then LONG PRESS and select all the files once they are highlighted then pres the bottom that says more and then click compress. then you can a -modded to the end of the file so you can tell them apart.
after it is done compressing you can delete the other files and keep your new zip.
after you get the hang of this you can do it in under 30 seconds, not including the time to extract and compress the rom.
WARNING THE ASSERT CHECK IS THERE SO YOU CAN NOT ACCIDENTALLY FLASH THIS TO THE WRONG PHONE AND PERMA BRICK YOUR DEVICE.
DELETING THE ASSERT TEXT WILL ALLOW YOU TO FLASH THE NEWLY MODDED ZIP
---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------
Stay off TWRP and philz cutom recovery I have never had a successfully boot, zips would fail halfway through flashing other phone would boot loop. this is back when i was flasinh I605 custom roms of 4.x.x and even cm 11.
I'm on cm 12.1 t0lte Nightly's now and I am using the actual Version I605 Clockword mode recovery with no problems. https://download.cyanogenmod.org/get/jenkins/139629/cm-12.1-20151217-NIGHTLY-i605-recovery.img

I just installed the latest nightly 12-22-15 and made a couple of calls and it rang every time, I am using VZW, so is this not a problem with this carrier, or will it eventually stop working?

How to use ROMs for other models on your model

Do this at your own risk.
It's not my fault if you brick your phone.
Don't do this with kernels.
This won't work on G531X phones because they have a different chipset.
Don't go to the thread of the rom you did this to for bug reports.
Some roms you can just flash but others need to be slightly modified.
PRO-TIP: Install PBRP recovery. You can change phone codename there which skips this entire tutorial.
My phone model: gprimeltedx (G530F)
Example ROM: Superior OS by itexpert.120 for fortuna3g (https://forum.xda-developers.com/t/...sis-fortuna3g-fortunave3g-26-12-2019.4025365/)
How to "slightly modify" the rom:
1- First try flashing the ROM. If you get an error about your model then continue
2- Download a text editor for Android or use Notepad++ for PC (Notepad works too but its harder)
3- Extract the ROM zip to a folder
4- Go into the folder you extracted the rom to
5- Go to /META-INF/com/google/android
6- Open updater-script with your text editor
7- At the top or near the top there should a line that goes like this.
Code:
assert(getprop("ro.product.device") == "fortuna3g" || getprop("ro.build.product") == "fortuna3g" ||
getprop("ro.product.device") == "fortuna3gxx" || getprop("ro.build.product") == "fortuna3gxx" || abort("E3004: This package is for device: fortuna3g,fortuna3gxx; this device is " + getprop("ro.product.device") + "."););
8- Delete it and save the file
9- Go back to the folder you extracted the rom to and select all of the files and folders, not the folder itself.
10- Compress the files to a zip and flash it with your recovery

will try. thx

zer0_Clover said:
Do this at your own risk.
It's not my fault if you brick your phone.
Don't do this with kernels.
This won't work on G531X phones because they have a different chipset.
Don't go to the thread of the rom you did this to for bug reports.
Some roms you can just flash but others need to be slightly modified.
PRO-TIP: Install PBRP recovery. You can change phone codename there which skips this entire tutorial.
My phone model: gprimeltedx (G530F)
Example ROM: Superior OS by itexpert.120 for fortuna3g (https://forum.xda-developers.com/t/...sis-fortuna3g-fortunave3g-26-12-2019.4025365/)
How to "slightly modify" the rom:
1- First try flashing the ROM. If you get an error about your model then continue
2- Download a text editor for Android or use Notepad++ for PC (Notepad works too but its harder)
3- Extract the ROM zip to a folder
4- Go into the folder you extracted the rom to
5- Go to /META-INF/com/google/android
6- Open updater-script with your text editor
7- At the top or near the top there should a line that goes like this.
Code:
assert(getprop("ro.product.device") == "fortuna3g" || getprop("ro.build.product") == "fortuna3g" ||
getprop("ro.product.device") == "fortuna3gxx" || getprop("ro.build.product") == "fortuna3gxx" || abort("E3004: This package is for device: fortuna3g,fortuna3gxx; this device is " + getprop("ro.product.device") + "."););
8- Delete it and save the file
9- Go back to the folder you extracted the rom to and select all of the files and folders, not the folder itself.
10- Compress the files to a zip and flash it with your recovery
Click to expand...
Click to collapse
btw can something dont work like camera or some?

wojtaszz said:
btw can something dont work like camera or some?
Click to expand...
Click to collapse
the only problem i had was internet not working on modded stock rom. Aosp roms should work np. I dont use gapps so i dont know if there will be any bugs with gapps

zer0_Clover said:
Do this at your own risk.
It's not my fault if you brick your phone.
Don't do this with kernels.
This won't work on G531X phones because they have a different chipset.
Don't go to the thread of the rom you did this to for bug reports.
Some roms you can just flash but others need to be slightly modified.
PRO-TIP: Install PBRP recovery. You can change phone codename there which skips this entire tutorial.
My phone model: gprimeltedx (G530F)
Example ROM: Superior OS by itexpert.120 for fortuna3g (https://forum.xda-developers.com/t/...sis-fortuna3g-fortunave3g-26-12-2019.4025365/)
How to "slightly modify" the rom:
1- First try flashing the ROM. If you get an error about your model then continue
2- Download a text editor for Android or use Notepad++ for PC (Notepad works too but its harder)
3- Extract the ROM zip to a folder
4- Go into the folder you extracted the rom to
5- Go to /META-INF/com/google/android
6- Open updater-script with your text editor
7- At the top or near the top there should a line that goes like this.
Code:
assert(getprop("ro.product.device") == "fortuna3g" || getprop("ro.build.product") == "fortuna3g" ||
getprop("ro.product.device") == "fortuna3gxx" || getprop("ro.build.product") == "fortuna3gxx" || abort("E3004: This package is for device: fortuna3g,fortuna3gxx; this device is " + getprop("ro.product.device") + "."););
8- Delete it and save the file
9- Go back to the folder you extracted the rom to and select all of the files and folders, not the folder itself.
10- Compress the files to a zip and flash it with your recovery
Click to expand...
Click to collapse
I tried it with maxicm 12.1 on FZ and touch didnt work

katruisya said:
I tried it with maxicm 12.1 on FZ and touch didnt work
Click to expand...
Click to collapse
I did say there could be bugs. Also why do you even need lolipop

zer0_Clover said:
I did say there could be bugs. Also why do you even need lolipop
Click to expand...
Click to collapse
I just wanna test stock cyanogenmod too

Better Mobile App

welcome