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
Related
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.
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.
I'm in the wrong area? sorry ... I am Brazilian and my English is the 'google translator. rs.
Then, I found no tutorial to my phone, and I heard that you are very intelligent and can make / modify a file so I can root my phone ..
thank you very much
and if possible move me to the correct area
Samsung Galaxy Pocket Duos GT-S5302B
Reply: How i root my Galaxy GT-S5302B?
DELETED
ArnabJain64 said:
Bro use Samsung Universal Gingerbread Root & Unroot 2.3.3 -> 2.3.7+
The First attachment will help u too root your mobile while the third one will help u too unroot it. If the First Attachmrnt Dose not work for u, try the 2nd Attachment.
--------------------------------------------------------------------------------------------------------------
Step wise tutorial to root and unroot your mobile:
1] 1st of all download all the three files into ur computer.
2] Copy the files to the root of your sd card[copy the files downloaded to usb storage if present,such as in Samsung Galaxy Pocket Duos/Samsung Galaxy Y Duos Lite].
3] Switch your mob off and then go to recovery mod with the key combination of Volume up + Home Key + Power Key.
4] Select install Zip from Sd card option And then Select universal_gb_root_v25.zip.
5] your phone will be succesfully rooted it not then install the 2nd attachment again.
Press thanxxx if my post helped u.
Click to expand...
Click to collapse
I have the same model and the above did not work.
I looked at the updater-script (META-INF/com/google/android/updater-script), and it have an assert for GT-S5302, but not for GT-S5302B.
Is it ok to add it to the assert?
Code:
getprop("ro.product.device") == "GT-S5302" ||
getprop("ro.build.product") == "GT-S5302" ||
getprop("ro.product.device") == "GT-S5302B" || # add these
getprop("ro.build.product") == "GT-S5302B" || # lines
ppires00 said:
i have the same model and the above did not work.
I looked at the updater-script (meta-inf/com/google/android/updater-script), and it have an assert for gt-s5302, but not for gt-s5302b.
Is it ok to add it to the assert?
Code:
getprop("ro.product.device") == "gt-s5302" ||
getprop("ro.build.product") == "gt-s5302" ||
getprop("ro.product.device") == "gt-s5302b" || # add these
getprop("ro.build.product") == "gt-s5302b" || # lines
Click to expand...
Click to collapse
no never do dat.
That will violet the law of xda.
I am not the owner of the files.
Ask stone boy[search for him in xda] or manoranjan2050.
If they allow to do so go forward n add those lines.
N ya 1more thing it may even ruin the updater script.
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.
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