I want to port Beanstalk ROM to my phone so I can check it out, but all the guides I've found are outdated. How do I port a ROM?
I still seek wisdom from Senior Members with high post counts (carefully)
I apologize must be tired.
I would try Google.
Sent from my SGH-I777 using XDA Premium 4 mobile app
So the same thing applies to KitKat?
Pretty much. Don't know how others are doing it, but I simply flash the rom, then the kernel/modem and reboot (with the necessary wipes, of course). It's worked this way since the ICS days.
For KK, I've been using Renders' TWRP kernel for porting; had a few too many problems with the CWM version playing nicely with 9100 roms.
SteveMurphy said:
Pretty much. Don't know how others are doing it, but I simply flash the rom, then the kernel/modem and reboot (with the necessary wipes, of course). It's worked this way since the ICS days.
For KK, I've been using Renders' TWRP kernel for porting; had a few too many problems with the CWM version playing nicely with 9100 roms.
Click to expand...
Click to collapse
So I just need to install like normal, from what you are saying, that's all I need to do. Thanks!
azeem40 said:
So I just need to install like normal, from what you are saying, that's all I need to do. Thanks!
Click to expand...
Click to collapse
Yes, just remember to be on the 6.0.4.5 or TWRP-equivalent recovery first. Also, read the op of the rom you're installing for specific instructions: on one I had to mount /system after the flash... on others I didn't. Just be careful!
SteveMurphy said:
Yes, just remember to be on the 6.0.4.5 or TWRP-equivalent recovery first. Also, read the op of the rom you're installing for specific instructions: on one I had to mount /system after the flash... on others I didn't. Just be careful!
Click to expand...
Click to collapse
I am going to port Beanstalk ROM ( http://forum.xda-developers.com/showthread.php?t=2580489 ) to my phone (i777).
azeem40 said:
I am going to port Beanstalk ROM ( http://forum.xda-developers.com/showthread.php?t=2580489 ) to my phone (i777).
Click to expand...
Click to collapse
and you needed go to
updater-script: /META-INF/com/google/android/updater-script.
and delete this:
assert(getprop("ro.product.device") == "captivate" || getprop("ro.build.product") == "captivate" ||
getprop("ro.product.device") == "captivatemtd" || getprop("ro.build.product") == "captivatemtd" ||
getprop("ro.product.device") == "SGH-I896" || getprop("ro.build.product") == "SGH-I896" ||
getprop("ro.product.device") == "SGH-I897" || getprop("ro.build.product") == "SGH-I897");
build.prop :rename i9100 to i777
AlmasSD said:
and you needed go to
updater-script: /META-INF/com/google/android/updater-script.
and delete this:
assert(getprop("ro.product.device") == "captivate" || getprop("ro.build.product") == "captivate" ||
getprop("ro.product.device") == "captivatemtd" || getprop("ro.build.product") == "captivatemtd" ||
getprop("ro.product.device") == "SGH-I896" || getprop("ro.build.product") == "SGH-I896" ||
getprop("ro.product.device") == "SGH-I897" || getprop("ro.build.product") == "SGH-I897");
build.prop :rename i9100 to i777
Click to expand...
Click to collapse
So I don't get this wrong, here is the edited build.prop file (top) and the original below that (bottom):
http://pastebin.com/LDhnHyrA
azeem40 said:
So I don't get this wrong, here is the edited build.prop file (top) and the original below that (bottom):
http://pastebin.com/LDhnHyrA
Click to expand...
Click to collapse
It "looks" good, but you don't have to do all of that to get it to boot. As Almas suggested, make sure to check the getro properties in the updater script to see if you need to delete them. If they're not there you're fine.
SteveMurphy said:
It "looks" good, but you don't have to do all of that to get it to boot. As Almas suggested, make sure to check the getro properties in the updater script to see if you need to delete them. If they're not there you're fine.
Click to expand...
Click to collapse
I removed those from the updater-script.
azeem40 said:
So I don't get this wrong, here is the edited build.prop file (top) and the original below that (bottom):
http://pastebin.com/LDhnHyrA
Click to expand...
Click to collapse
hm.....can i see how you edit updater-script? if nothing happens-where the error....
just to jump aboard, you must install it View attachment CWM-KitKatCompatible-i777.zip
AlmasSD said:
hm.....can i see how you edit updater-script? if nothing happens-where the error....
just to jump aboard, you must install it View attachment 2521456
Click to expand...
Click to collapse
I have a few kernels in my sd card and that is one of them, but I will be trying TWRP as Steve suggested.
99 times out if a hundred I can just flash the rom, reboot into recovery, and flash the kernel.
Related
Hi guys,
I've found a topic while browsing around that teaches you how to port MIUI to gingerbread devices.
http://forum.xda-developers.com/showthread.php?p=22228486
It looks like it could work on these players. I will definitely try this when I have time, but just wanted to post here in the meantime if anyone is also interested in porting MIUI to the Galaxy Players.
Cheers!
Sent from my Galaxy Player 4.0 (YP-G1)
I haven't had a chance to completely read through the guide, but it contains nothing about creating a new device tree - in short, the MIUI team still does not have the technical skill to do a new device bringup. To this day, I do not know of a single MIUI release that hasn't relied on kanging the CyanogenMod team's work.
Sent from my GT-P7510 using Tapatalk
Don't want to sound like a noob here, but what is MIUI?
EcHoFiiVe said:
Don't want to sound like a noob here, but what is MIUI?
Click to expand...
Click to collapse
It's a custom ROM that's based off of cyanogen.
Sent from my Galaxy Player 4.0 (YP-G1)
Hmm why hasn't CyanogenMod even come out for these devices yet? I bet it's hard... And also, if this is based of Cyanogen, wouldn't that be a big step forward to getting CM7 on these devices?
EcHoFiiVe said:
Hmm why hasn't CyanogenMod even come out for these devices yet? I bet it's hard... And also, if this is based of Cyanogen, wouldn't that be a big step forward to getting CM7 on these devices?
Click to expand...
Click to collapse
Simple - there isn't anyone with enough spare time and the required skills to work on it.
I don't have the spare time, and I've never done an AOSP/CM bringup before - it's a pretty tough task, even on a device like this with no RIL to worry about.
Samsung devices are different from the others because the generic boot.img that comes with it just don't work. (CM7) You need several scripts to convert the ****ty rfs to something else like yaffs2 or ext4. Well I'm almost finished with CM7. I just need to change something at some init files at the kernel and I will finish it (I can't say if it will work or not.) Let's just hope!
zaclimon said:
Samsung devices are different from the others because the generic boot.img that comes with it just don't work. (CM7) You need several scripts to convert the ****ty rfs to something else like yaffs2 or ext4. Well I'm almost finished with CM7. I just need to change something at some init files at the kernel and I will finish it (I can't say if it will work or not.) Let's just hope!
Click to expand...
Click to collapse
Does that mean that when CM7 is succesfully ported, the MIUI won't be a hard job to do then? Or is MIUI completely different?
Rapydax said:
Does that mean that when CM7 is succesfully ported, the MIUI won't be a hard job to do then? Or is MIUI completely different?
Click to expand...
Click to collapse
CM7 has been ported succesfully. Porting MIUI isn't that hard, however you will need some java skills (if you use the patchrom) or you can find a guide to port. Per exemple people with CM9 for the 5.0 can follow this guide to port MIUI
Link: http://forum.xda-developers.com/showthread.php?t=1499411
zaclimon said:
CM7 has been ported succesfully. Porting MIUI isn't that hard, however you will need some java skills (if you use the patchrom) or you can find a guide to port. Per exemple people with CM9 for the 5.0 can follow this guide to port MIUI
Link: http://forum.xda-developers.com/showthread.php?t=1499411
Click to expand...
Click to collapse
Thanks for the link, will look at it soon. But the cm7 still doesn't work for my INTL 5.0.
I get the same error when I try to flash Alpha 2.
This post: http://forum.xda-developers.com/showpost.php?p=23801533&postcount=74
Rapydax said:
Thanks for the link, will look at it soon. But the cm7 still doesn't work for my INTL 5.0.
I get the same error when I try to flash Alpha 2.
This post: http://forum.xda-developers.com/showpost.php?p=23801533&postcount=74
Click to expand...
Click to collapse
The problem seems to be in the updater script. Does anyone else with an intl 5.0 got the same error? If not try to download the lastest rj's kernel (which is r13 I think)
I get the exact same error on my intl 5.0 with rj's kernel and the eryigit latest rom
glenb77 said:
I get the exact same error on my intl 5.0 with rj's kernel and the eryigit latest rom
Click to expand...
Click to collapse
I can't guarantee if will work but we can try. You will need notepad++ for this.
1. Unzip your rom.
2. Go to meta-inf/google/android folder.
3. Open updater-script with notepad++.
4. Erase these texts and save:
Code:
getprop("ro.product.device) == "venturi_usa" || getprop("ro.build.product") == "venturi_usa" || getprop("ro.product.board") == "venturi_usa" || getprop("ro.product.device") == "YP-G70" || getprop("ro.build.product") == "YP-G70" || getprop("ro.product.board") == "YP-G70"
5.Rezip the rom.
6.Flash!
7.Enjoy!
zaclimon said:
CM7 has been ported succesfully. Porting MIUI isn't that hard, however you will need some java skills (if you use the patchrom) or you can find a guide to port. Per exemple people with CM9 for the 5.0 can follow this guide to port MIUI
Link: http://forum.xda-developers.com/showthread.php?t=1499411
Click to expand...
Click to collapse
i have 5.0 intl with cm9 it will work on my device?
and it will fix the camera issue?
zaclimon said:
I can't guarantee if will work but we can try. You will need notepad++ for this.
1. Unzip your rom.
2. Go to meta-inf/google/android folder.
3. Open updater-script with notepad++.
4. Erase these texts and save:
Code:
getprop("ro.product.device) == "venturi_usa" || getprop("ro.build.product") == "venturi_usa" || getprop("ro.product.board") == "venturi_usa" || getprop("ro.product.device") == "YP-G70" || getprop("ro.build.product") == "YP-G70" || getprop("ro.product.board") == "YP-G70"
5.Rezip the rom.
6.Flash!
7.Enjoy!
Click to expand...
Click to collapse
Thank you very much it worked
i am going to work on this asap
Rapydax said:
Thank you very much it worked
Click to expand...
Click to collapse
and if i will do those things i will have miui on my intl player?
And i will have ics?not the pre alpha version?
Sent from my YP-G70 using xda premium
No its for cm7. But its already fixed by the developer in the cm7 thread.
Sent from my YP-G70 using xda premium
Rapydax said:
No its for cm7. But its already fixed by the developer in the cm7 thread.
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
So i will have miui but not with ics?
Sent from my YP-G70 using xda premium
kfirbep said:
So i will have miui but not with ics?
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
No you won't have MIUI then, because CM7 is not MIUI and it is also not CM9 (ICS).
Please be patient, ROMs are still under construction.
I-ve got a Gt s5830m that i bricked and flashed via odin to gt s5830i (anyways when i started download mode it would say s5830i). Currently i run with no problems MindCr_Rom_v2.7.
I want to update to icecream sandwich from this source
http://forum.xda-developers.com/showthread.php?t=2011671
using clockworkmod i try to install the zip but i get this error message
assert(getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" || getprop("ro.product.board") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.board") == "GT-S5830");
status 7
installation aborted
A website said that i had to delete those lines from the rom, using notepad ++. Did it but then i got status 0 error at installation. (didnt unzip the rom, just replace the file)
what i-m doing wrong? please help....
u cannot flash cm for s5830 on s5830I
we dont have ics
we have cm 9.1 but its very unstable
Sent from my GT-S5830i using xda premium
rrataraton said:
I-ve got a Gt s5830m that i bricked and flashed via odin to gt s5830i (anyways when i started download mode it would say s5830i). Currently i run with no problems MindCr_Rom_v2.7.
I want to update to icecream sandwich from this source
http://forum.xda-developers.com/showthread.php?t=2011671
using clockworkmod i try to install the zip but i get this error message
assert(getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" || getprop("ro.product.board") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.board") == "GT-S5830");
status 7
installation aborted
A website said that i had to delete those lines from the rom, using notepad ++. Did it but then i got status 0 error at installation. (didnt unzip the rom, just replace the file)
what i-m doing wrong? please help....
Click to expand...
Click to collapse
You are doing very wrong. S5830 rom is not for s5830 " i-c-m " phone.
Kind of suspected this...
So are there any other choices?. So far i should stay in gingerbread then.
rrataraton said:
So are there any other choices?. So far i should stay in gingerbread then.
Click to expand...
Click to collapse
Wait for a week..simplicity v5 will be available in few days it has jb user interfave
EDIT: v5 out now
Sent from my GT-S5830i using xda app-developers app
GT-S5830i.simplicity v5
srt99 said:
Wait for a week..simplicity v5 will be available in few days it has jb user interfave
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
I am waiting for simplicity v5. :highfive::good:
AW: Cant instal Icecream sandwich
subratsahu said:
I am waiting for simplicity v5. :highfive::good:
Click to expand...
Click to collapse
Simplicity v5 is already out :lol:
Tapatalked by S5830i
Ace vibration settings
Hi this is sudip here. A new joinee (not a very tech expert guy), I did not know where to post or ask this question.. I have the ace s5830i, and when we just tap and hold on any option or on the home screen a small vibration takes place and some relevant pop up options comes up .. is there any way to turn it off? i just want to make no vibration apart incoming calls... in sound settings i checked it with the vibration "never" but that does not make any difference...
sd.malakar said:
Hi this is sudip here. A new joinee (not a very tech expert guy), I did not know where to post or ask this question.. I have the ace s5830i, and when we just tap and hold on any option or on the home screen a small vibration takes place and some relevant pop up options comes up .. is there any way to turn it off? i just want to make no vibration apart incoming calls... in sound settings i checked it with the vibration "never" but that does not make any difference...
Click to expand...
Click to collapse
u can search for it on xda but this is a very irrelevant problem and i don't suppose there would be fix to only disable vibration for long click on homescreen!
still u can search!!
Tried it
Android-fany said:
Simplicity v5 is already out :lol:
Tapatalked by S5830i
Click to expand...
Click to collapse
I-ve tried the rom, seems fast and small (size) But i kind of prefer Mind Cr 2.7 rom iu better.
Its also gingerbread >o
I am ending support for this thread as there is already another thread for CM11 on the Note 10.1 2014 (P600). You guys can still download this rom and play around with it... I have no time to work on a rom that allready exists. It is hard to find time between school and the Android 5.0 rom for P600 i am working on... Finally thanks hitman1376 for helping me work on this rom and my other P600 rom... You were a great help in this rom devlopment.
CHECK OUT MY Paranoid Android ROM thread for this device.
Dropbox link to rom
https://www.dropbox.com/s/a0uhz0dcmvs0ane/CM11_BETA.zip?dl=0
Updater Script:
https://www.dropbox.com/s/nqfibslb27ier7w/updater-script?dl=0
Thanks
-Shawn5162 (Rom Dev)
Shawn5162 said:
This rom is ready for testing. It is a port from the Samsung Galaxy Tab S 10.5. I know they are some problems with the updater script that are forcing the ro not to install. COuld someone please install the rom and extract the Update-Script are try to fix the problem so it can successfully flash in recovery. Otherwise the rom is ready to be installed.
By the way... which program do u guys use to port and build roms (android kitchen, archi kitchen, rick's rom kitchen, etc.)
Dropbox link to rom
https://www.dropbox.com/s/a0uhz0dcmvs0ane/CM11_BETA.zip?dl=0
Thanks
-Shawn5162 (Rom Dev)
Click to expand...
Click to collapse
Dear friend ... if you provide me the Updater Script , I'll edit it for you ...
Thanks so much....
Well ... As I analized it ...
Shawn5162 said:
Thanks so much....
Click to expand...
Click to collapse
So ... What's wrong with it , Dear Friend ? ... Seems like everything should be Okay ... do you have any problem flashing the ZIP ? ... if yes , give me some details ( Recovery Name / Version / the Architecture / etc. ) ... Thanks in advance ...
With Best Wishes
Hitman1376
I have tried flashing it in TWRP and Philz touch. It says problem flashing (status 7). Try flashing the rom yourself... see if u get any errors.
Shawn5162 said:
I have tried flashing it in TWRP and Philz touch. It says problem flashing (status 7). Try flashing the rom yourself... see if u get any errors.
Click to expand...
Click to collapse
status 7 is most probably an attempt of a dirty flash. try wiping cache and data before flashing on twrp and with the edited updater script, that should do.
Could u try to flash it on ur Note 10.1 2014
I dont have TWPR anymore. I installed "equilibriumtr"'s Cyanogenmod and that installed CWM recovery and with that, your rom installed. Didnt get past "Samsung Galaxy Note 2014" Screen though. Would i need a wipe?
yes... thanks so much for trying to help... greatly appreciated
Sorry if i am not of much use, i just wanted to help because i had the exact same errors that you guys posted on this thread; ill quote myself:
META-INF>com>google>android>updater-script
For its to work i deleted the first line that says:
Quote:
assert(
getprop("ro.product.device") == "lt03wifi" ||
getprop("ro.build.product") == "lt03wifi" ||
abort("This package is for device: lt03wifi; this device is " + getprop("ro.product.device") + "."); );
After that and a data wipe on TWRP the installation went smooth. This will let you to flash the rom and also install cwm recovery that comes with CM roms so you can say bye to TWRP; from then, the "lt03wifieu" is not a problem for me on cwm as @equilibriumtr said. I can now flash the zip with the lines that didnt let me before.
I think we could recover the lost security from deleting that line by adding something like this:
Quote:
assert(
getprop("ro.product.device") == "lt03wifi" ||
getprop("ro.build.product") == "lt03wifi" ||
getprop("ro.product.device") == "lt03wifiue" ||
getprop("ro.build.product") == "lt03wifiue" ||
abort("This package is for device: lt03wifi; this device is " + getprop("ro.product.device") + "."); );
Can someone please add the lines instead of deleting them first and try flashing? Since with CWM i dont get the "lt03wifi is not lt03wifiue" error so I dont know if my theory is correct.
Click to expand...
Click to collapse
I have to add that after changing the updater script i also had the "error 7", just like you, but a simple wipe fixed that and now i am on CWM.
so at the end did it work
As I said, it worked for equilibriumtr's rom. I cant check if your rom has the same problem because i dont have twpr anymore but it sure sounds like it. I dont get any other problems flashing roms after the procedure, not in your rom nor in others and it is most probably because i already have cwm(In other words, i cant check if it is the same problem because i cant recreate the circumstances).
In what i think is unrelated to the recovery problem(because i successfully flashed your rom) your ROM got stock at "Samsung Galaxy Note 2014" Logo; I have some important stuff now on my tab(Cahnging HDD's on my computer so using it as a temp storage till windows is set up) so i cant do wipe, but that may be the problem here.
Thanks
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
Please refer to the main thread for details.
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here.
XDA:DevDB Information
FPBug-i777, Kernel for the AT&T Samsung Galaxy S II SGH-I777
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2014-12-19
looks promising! Can't wait for this to get worked into other i777 kernels
I haven't flashed anything since march but CM10.3 still seems like a step backwards. i guess i can wait a little longer
In the mean time, can I flash your music bug fix? Does it do the same thing? I'm on a 4.4.2 slimrom
fwiw I think we can flash an i1900 rom then flash a compatible i777 kernel after. this might be an easy way to get i777 users up to speed. just an idea
badger109 said:
looks promising! Can't wait for this to get worked into other i777 kernels
I haven't flashed anything since march but CM10.3 still seems like a step backwards. i guess i can wait a little longer
In the mean time, can I flash your music bug fix? Does it do the same thing? I'm on a 4.4.2 slimrom
fwiw I think we can flash an i1900 rom then flash a compatible i777 kernel after. this might be an easy way to get i777 users up to speed. just an idea
Click to expand...
Click to collapse
cm nightlies stopped on 10.2 (4.3). i can try and build a cm 11 kernel for i777 but have no idea if it would work. you could flash it atop a recent i9100 build. would u like to try that? note that if the device doesnt boot youll need to use heimdall/odin, since unfortunately recovery shares the main kernel.
would u like me to use nightly or snapshot branch?
Lanchon said:
cm nightlies stopped on 10.2 (4.3). i can try and build a cm 11 kernel for i777 but have no idea if it would work. you could flash it atop a recent i9100 build. would u like to try that? note that if the device doesnt boot youll need to use heimdall/odin, since unfortunately recovery shares the main kernel.
would u like me to use nightly or snapshot branch?
Click to expand...
Click to collapse
Thanks for the offer, but it wouldn't be worth your time. For one thing, I have no idea what I'm doing. 2nd, I thought that might be common practice but apparently not. All I know is that I did it before using a i9000 slim rom with render broken i777 kernel.
I'm not even familiar with the music/sd card bug, but it seems cool that it was fixed. Thanks
badger109 said:
Thanks for the offer, but it wouldn't be worth your time. For one thing, I have no idea what I'm doing. 2nd, I thought that might be common practice but apparently not. All I know is that I did it before using a i9000 slim rom with render broken i777 kernel.
I'm not even familiar with the music/sd card bug, but it seems cool that it was fixed. Thanks
Click to expand...
Click to collapse
it wouldnt be a problem for me to try. but this fix is spreading like wildfire to other kernels so i think your best bet would be to download a proper one with the fix incorporated?
meh... i'll try to build one anyway see what happens
badger109 said:
Thanks for the offer, but it wouldn't be worth your time. For one thing, I have no idea what I'm doing. 2nd, I thought that might be common practice but apparently not. All I know is that I did it before using a i9000 slim rom with render broken i777 kernel.
I'm not even familiar with the music/sd card bug, but it seems cool that it was fixed. Thanks
Click to expand...
Click to collapse
here it is, it'd be called a nightly if cm did them. care to try?
if it works i'll output trim kernels to speed up these devices
1) download i9100 latest nightly, make a copy of it, name it i9100-mod.zip.
2) edit file "/META-INF/com/google/android/updater-script" inside i9100-mod (it's a text file), remove these lines that check the device type:
Code:
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" ||
getprop("ro.product.device") == "SC-02C" ||
getprop("ro.build.product") == "SC-02C" ||
abort("This package is for device: galaxys2,i9100,GT-I9100,GT-I9100M,GT-I9100P,GT-I9100T,SC-02C; this device is " + getprop("ro.product.device") + "."););
3) remove the 3 files in "/META-INF/com/google/android/updater-script" inside i9100-mod (but not the directory!), these are the zip signature.
4) get these files on your phone:
-my kernel
-unmodified latest i9100 nightly (call it i9100-std)
-the modded version (i9100-mod)
-another working rom you use (recommended)
-and a separate kernel/recovery if you use one (recommended)
5) flash my kernel then reboot recovery (usually an option in "advanced").
-if it boots, my kernel worked
-IF NOT, YOU'LL NEED ODIN OR HEIMDALL TO FLASH ANOTHER KERNEL
6) flash i9100-std. it should fail, but test try it! if it fails, flash i9100-mod.
7) flash my kernel again
8) wipe, reboot!
Wildfire indeed.
I sincerely appreciate the effort that you, @zeitferne, @cgx, & @Entropy512 have put into figuring this out. If that wasn't enough, there are now published patchsets, which makes the fix joyously simple to implement.
Cheers & happy flashing
-Cyril
Lanchon said:
...this fix is spreading like wildfire to other kernels...
Click to expand...
Click to collapse
cyril279 said:
I sincerely appreciate the effort that you, @zeitferne, @cgx, & @Entropy512 have put into figuring this out. If that wasn't enough, there are now published patchsets, which makes the fix joyously simple to implement (I should probably wait until I have success to throw such accolades).
Cheers & happy flashing
-Cyril
Click to expand...
Click to collapse
@cgx kickstarted this whole thing, his initial debugging and discovery brought the issue to light and was instrumental for everything that happened next
Is this just for CM roms or will work on 4.1.2 as well ?
AAA118 said:
Is this just for CM roms or will work on 4.1.2 as well ?
Click to expand...
Click to collapse
this is CM only but the fix is being integrated into a lot of kernels
Hello fellow XDA users and developers, today I bring you four flashable scripts for I9100 ROMs on the I777/S959G Phones to completely make any I9100 ROM work on the two mentioned. UPDATE: KitKat flashable zips ready for download and might work for 4.3, 4.2, 4.1 and 4.0 ROMs on the I777/S959G. Feedback is welcome and I know it's a small hack but it's my first flashable mod for android
The Zips do the following:
For Lollipop ROMs only, you have been warned!:
I777_&_180.zip = Sets the model to SGH-I777, replaces the sec_touchkey.kl in /system/usr/keylayout, replaces the Telecom.apk in /system/priv-app and 180 LCD density
I777_&_240.zip = Sets the model to SGH-I777, replaces the sec_touchkey.kl in /system/usr/keylayout, replaces the Telecom.apk in /system/priv-app and and 240 LCD density
S959G_&_180.zip = Sets the model to SGH-S959G, replaces the sec_touchkey.kl in /system/usr/keylayout, replaces the Telecom.apk in /system/priv-app and and 180 LCD density
S959G_&_240.zip = Sets the model to SGH-S959G, replaces the sec_touchkey.kl in /system/usr/keylayout, replaces the Telecom.apk in /system/priv-app and and 240 LCD density
For Kit Kat ROMs:
I777_&_180_KK.zip = Sets the model to SGH-I777, replaces the sec_touchkey.kl in /system/usr/keylayout, and 180 LCD density
I777_&_240_KK.zip = Sets the model to SGH-I777, replaces the sec_touchkey.kl in /system/usr/keylayout, and and 240 LCD density
S959G_&_180_KK.zip = Sets the model to SGH-S959G, replaces the sec_touchkey.kl in /system/usr/keylayout, and and 180 LCD density
S959G_&_240_KK.zip = Sets the model to SGH-S959G, replaces the sec_touchkey.kl in /system/usr/keylayout, and and 240 LCD density
Patcher.zip = Includes a batch file with ADB, sec_touchkeys.kl and Telecom.apk for Lollipop users only, all fixes above are included, model to either SGH-I777/S959G, 240 or 180 DPI and Telecom.apk for patching in a single batch file.
Thank @dimoochka for the Telecom.apk and I hope you don't get mad at me dimoochka for including your hack, it's only in my zip for people who don't want to mess with /system files or if they feel like they might mess something up in the ROM with the call bug issue
If any issues occur in CWM or TWRP, let me know in a PM and I'll try to rework my zips for you guys and I hope I didn't post this in the wrong forum. ^^;
cidlover said:
Hello fellow XDA users and developers, today I bring you four flashable scripts for I9100 ROMs on the I777/S959G Phones to completely make any I9100 ROM work on the two mentioned.
The Zips do the following and currently work for lollipop only (also fixes the call out bug where you have to toggle speakerphone on and then off to hear the the other person), Kit Kat versions coming soon
I777_&_180.zip = Sets the model to SGH-I777, replaces the sec_touchkey.kl in /system/usr/keylayout, replaces the Telecom.apk in /system/priv-app and 180 LCD density
I777_&_240.zip = Sets the model to SGH-I777, replaces the sec_touchkey.kl in /system/usr/keylayout, replaces the Telecom.apk in /system/priv-app and and 240 LCD density
S959G_&_180.zip = Sets the model to SGH-S959G, replaces the sec_touchkey.kl in /system/usr/keylayout, replaces the Telecom.apk in /system/priv-app and and 180 LCD density
S959G_&_240 = Sets the model to SGH-S959G, replaces the sec_touchkey.kl in /system/usr/keylayout, replaces the Telecom.apk in /system/priv-app and and 240 LCD density
Thank @dimoochka for the Telecom.apk and I hope you don't get mad at me dimoochka for including your hack, it's only in my zip for people who don't want to mess with /system files or if they feel like they might mess something up in the ROM with the call bug issue
If any issues occur in CWM or TWRP, let me know in a PM and I'll try to rework my zips for you guys and I hope I didn't post this in the wrong forum. ^^;
Click to expand...
Click to collapse
Do I flash this before a rom or after the rom (and before gapps?)
coolerboyj said:
Do I flash this before a rom or after the rom (and before gapps?)
Click to expand...
Click to collapse
I9100 ROM first then one of my zips, if it don't have the KK at the end then it's for I9100 Lollipop ROMs for the callout bug to fix it but you can flash before or after Gapps is installed on the device. It don't matter as long as you have the ROM (any I9100 ROM since the kernel in any I9100 ROM works with the I777/S959G but the only hardware keys that would work before my zips are the Menu key and Back keys) installed first the order after the ROM is flashed don't matter.
Order:
ROM (I9100/I777/S959G)
I777_&_240 for Lollipop for the callbug fix or I777_&_240_KK for Kit Kat, No call bug issue
Gapps for that ROM
Maybe some extra zips?
cidlover said:
I9100 ROM first then one of my zips, if it don't have the KK at the end then it's for I9100 Lollipop ROMs for the callout bug to fix it but you can flash before or after Gapps is installed on the device. It don't matter as long as you have the ROM (any I9100 ROM since the kernel in any I9100 ROM works with the I777/S959G but the only hardware keys that would work before my zips are the Menu key and Back keys) installed first the order after the ROM is flashed don't matter.
Order:
ROM (I9100/I777/S959G)
I777_&_240 for Lollipop for the callbug fix or I777_&_240_KK for Kit Kat, No call bug issue
Gapps for that ROM
Maybe some extra zips?
Click to expand...
Click to collapse
I think this is somewhere in the forum but I haven't found it yet. How do you flash an i9100 rom when you get the error saying you have the wrong model phone (i777)?
Sent from my SAMSUNG-SM-G890A using XDA Free mobile app
radoo7701 said:
I think this is somewhere in the forum but I haven't found it yet. How do you flash an i9100 rom when you get the error saying you have the wrong model phone (i777)?
Sent from my SAMSUNG-SM-G890A using XDA Free mobile app
Click to expand...
Click to collapse
open the zip in WinRAR and find the updater-script in META-INF\com\google\android\updater-script and remove this line, it will vary from I9100 ROM to ROM.
Find this line and remove up to either ui_print or mount
Code:
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" || getprop("ro.product.device") == "SC-02C" || getprop("ro.build.product") == "SC-02C" || abort("This package is for device: galaxys2,i9100,GT-I9100,GT-I9100M,GT-I9100P,GT-I9100T,SC-02C; this device is " + getprop("ro.product.device") + ".");
Thanks, I was able to flash the rom (Validus 8.1.) However the soft keys are not working properly with your fix. (I flashed i777 & 240 zip) The back button and search button don't work. The home button functions as the back button. The menu button works. This is not a big deal as I can use Nav buttons, but they do take up precious screen space.
Sent from my SAMSUNG-SM-G890A using XDA Free mobile app
radoo7701 said:
Thanks, I was able to flash the rom (Validus 8.1.) However the soft keys are not working properly with your fix. (I flashed i777 & 240 zip) The back button and search button don't work. The home button functions as the back button. The menu button works. This is not a big deal as I can use Nav buttons, but they do take up precious screen space.
Sent from my SAMSUNG-SM-G890A using XDA Free mobile app
Click to expand...
Click to collapse
what recovery are you using to flash this script?
cidlover said:
what recovery are you using to flash this script?
Click to expand...
Click to collapse
I used TWRP when I flashed the ROM. Flashing the ROM changed it to CWM. I tried to flash again with that but still no luck.
Sent from my SGH-M919 using Tapatalk
radoo7701 said:
I used TWRP when I flashed the ROM. Flashing the ROM changed it to CWM. I tried to flash again with that but still no luck.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Try this one, I reworked some of the scrtipting and redid some files and folders.
cidlover said:
Try this one, I reworked some of the scrtipting and redid some files and folders.
Click to expand...
Click to collapse
No luck still. I even tried PhilZ just in case, as well as a new flash. Thanks I'm still happy I got the i9100 rom running.
Sent from my SAMSUNG-SM-G890A using XDA Free mobile app
radoo7701 said:
No luck still. I even tried PhilZ just in case, as well as a new flash. Thanks I'm still happy I got the i9100 rom running.
Sent from my SAMSUNG-SM-G890A using XDA Free mobile app
Click to expand...
Click to collapse
I might just take these down since I can't figure out why they don't work
cidlover said:
I might just take these down since I can't figure out why they don't work
Click to expand...
Click to collapse
!!!!!!!!! NEW !!!!!!!!!!!!!!!
Patcher.zip
A batch file version of the flashable zips, since my zips failed this might work for some of you people
WARNING, The Telecom.apk patch could brick your device, USE WITH CAUTION.
Please report feedback back to this forum if not working like the other patches i made.
cidlover said:
!!!!!!!!! NEW !!!!!!!!!!!!!!!
Patcher.zip
A batch file version of the flashable zips, since my zips failed this might work for some of you people
WARNING, The Telecom.apk patch could brick your device, USE WITH CAUTION.
Please report feedback back to this forum if not working like the other patches i made.
Click to expand...
Click to collapse
I'll try it out.
Sent from my GT-I9100 using XDA Free mobile app
---------- Post added at 02:04 AM ---------- Previous post was at 01:56 AM ----------
cidlover said:
!!!!!!!!! NEW !!!!!!!!!!!!!!!
Patcher.zip
A batch file version of the flashable zips, since my zips failed this might work for some of you people
WARNING, The Telecom.apk patch could brick your device, USE WITH CAUTION.
Please report feedback back to this forum if not working like the other patches i made.
Click to expand...
Click to collapse
So, since it's a batch file, do I need to flash it from my computer? I tried it with CWM and that didn't work.
Sent from my GT-I9100 using XDA Free mobile app
radoo7701 said:
I'll try it out.
Sent from my GT-I9100 using XDA Free mobile app
---------- Post added at 02:04 AM ---------- Previous post was at 01:56 AM ----------
So, since it's a batch file, do I need to flash it from my computer? I tried it with CWM and that didn't work.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
You connect your phone and then open the RUNME.bat file and select the options you want
cidlover said:
You connect your phone and then open the RUNME.bat file and select the options you want
Click to expand...
Click to collapse
I tried the i777 and touchkey patches but no luck.
Sent from my GT-I9100 using XDA Free mobile app
radoo7701 said:
I tried the i777 and touchkey patches but no luck.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Check for RUNMEv2.bat, I made some changes to the commands
Still did nothing for me.
Thanks
radoo7701 said:
Still did nothing for me.
Thanks
Click to expand...
Click to collapse
Then just replace the files needed on the phone itself, it should be working, maybe your phone is rejecting my scripts.