Let the fun begin, 4.3.1 AOKP goodness is upon us!
Thanks to aokp.co for their amazing aosp based rom.
If you have followed my 4.2.2 aokp unofficial build thread in the Canadian E973 forum you'll know I take pride in making a very solid and stable rom with ALL working features for our LGOG's.
Thanks to dvhexer for his initial kernel work.
Thanks to SnowleopardJB for his device and vendor work.
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
**Known bugs**
AOKP is still under heavy 4.3 development but this rom is pretty darn stable even now.
*After initial install and setup, NFC may be buggy until first reboot.*
I setup a "kerneltweaks" (look for "kerneltweaks" in /system/etc/init.d) file for colour settings, setting your own governor, io scheduler, and voltage levels at boot. I have a fast binned cpu and those are my voltage settings that cause no issues for me even under load. Use faux123 kernel app or trickster mod to see whats available.
Changelog:
One build for all 3 devices again. Maintaining/fixing two seperates is tough when I don't have either to test on.
Huge resync to AOKP (almost a gig of code changes!), reverted custom ril to unify the build, please let me know if you can add/save apn's or if you have gsm signal now for E970's. E971 should work just like before.
E970's will need to flash the nfc fix again.
LTE tethering should work from quick toggles or in main tethering settings window.
Latest E970/E971/E973 rom will be here - 10-31-2013:
http://www.androidfilehost.com/?fid=23203820527944669
Latest E970/E971/E973 md5sum will be here - 10-31-2013:
http://www.androidfilehost.com/?fid=23203820527944670
Download AOKP 4.3 V1 here [OLD BUILD BUT KNOWN WORKING WELL]:
http://d-h.st/Cas
Download E970 NFC fix here:
Dev Host:
http://d-h.st/4uH
Android File Host:
http://www.androidfilehost.com/?fid=23134718111255697
Download PA Gapps modular mini here:
http://d-h.st/koF
Download Modified for Geeb PA Photosphere here:
http://d-h.st/nfS
Post back results!
Sources:
Device:
https://github.com/Paulicat/android-device-geeb
Vendor:
https://github.com/Paulicat/aokp-geeb-vendor
Kernel:
https://github.com/Paulicat/aokp-geeb-kernel
Good stuff dude. I ran this for a while over the summer and loved it.
I have it installed on my e973. Running perfect so far.
Sent from my Optimus G using xda app-developers app
I knew this was coming so I patiently waited for it to arrive. Will definitely be posting back with feedback. Thank you for your hard work my friend!
Hi Pauli can you make a zip installer of your kernel?
slayp00n said:
Hi Pauli can you make a zip installer of your kernel?
Click to expand...
Click to collapse
Can I ask what you wanted to run it on??
PM me.
Any feedback folks? Please let me know, good or bad...
Hi Pauli, probably going to switch to this soon, getting fed up with constant reboots and issues on Pac Man
Hey is this based on JSS or hybrid with JWR?
Paulicat said:
Any feedback folks? Please let me know, good or bad...
Click to expand...
Click to collapse
When I tried, it wouldn't install (via twrp v2.6.3.0):
Code:
Installing '/external_sd/aokp-4.3-geeb-unofficial-V1.zip'...
Checking for MD5 file...
I:Cannot find file /external_sd/aokp-4.3-geeb-unofficial-V1.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: assert failed: getprop("ro.product.device") == "geeb" || getprop("ro.build.product") == "geeb"
assert failed: getprop("ro.product.device") == "geeb" || getprop("ro.build.product") == "geeb"
E:Error executing updater binary in zip '/external_sd/aokp-4.3-geeb-unofficial-V1.zip'
Error flashing zip '/external_sd/aokp-4.3-geeb-unofficial-V1.zip'
danial.aw said:
Hey is this based on JSS or hybrid with JWR?
Click to expand...
Click to collapse
JLS36G...
mong8se said:
When I tried, it wouldn't install (via twrp v2.6.3.0):
Code:
Installing '/external_sd/aokp-4.3-geeb-unofficial-V1.zip'...
Checking for MD5 file...
I:Cannot find file /external_sd/aokp-4.3-geeb-unofficial-V1.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: assert failed: getprop("ro.product.device") == "geeb" || getprop("ro.build.product") == "geeb"
assert failed: getprop("ro.product.device") == "geeb" || getprop("ro.build.product") == "geeb"
E:Error executing updater binary in zip '/external_sd/aokp-4.3-geeb-unofficial-V1.zip'
Error flashing zip '/external_sd/aokp-4.3-geeb-unofficial-V1.zip'
Click to expand...
Click to collapse
Under CWM, geeb is the device for ro.product.device, can you tell me what rom worked for you and I'll try to update the script.
I haven't tried twrp in quite a while.
Next build will also have an md5 file...
Paulicat said:
Any feedback folks? Please let me know, good or bad...
Click to expand...
Click to collapse
Running it for few days now. Nothing to report accept seems like battery drains a bit quick. Other than that it is now my DD.
Sent from my Optimus G using xda app-developers app
gentlemandroid17 said:
Running it for few days now. Nothing to report accept seems like battery drains a bit quick. Other than that it is now my DD.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Can you do me a favour and run BetterBatteryStats or something to see what might be draining battery for you?
I'm getting the same battery I got on cm10.2 on my phone.
Paulicat said:
Under CWM, geeb is the device for ro.product.device, can you tell me what rom worked for you and I'll try to update the script.
I haven't tried twrp in quite a while.
Next build will also have an md5 file...
Click to expand...
Click to collapse
I've been fine with shelnutt or dvhexer's CM 10.2 builds.
I had to flash the "alt" TeenyBin if that makes a difference. (I have a Google logo instead of LG when booting)
I flashed today is smooth as hell good work , so far so good I report any bug
Edit
Is there a way to change buttons I want to use menu button as multitask and change the time for the illumination of them
P.S sorry for the errors English its not my language
Cant install in TWRP
trying CWM now
Was working quite well for the day I tried it so far. NFC needed a reboot when trying to disable it the first time. Jumped to the nightly for some testing but will be back on AOKP soon and report more.
Paulicat, will your kernel work with the official nightlies you think? They are also based on JLS3G as well.
Sent from my LG-E973 using xda app-developers app
solanomes said:
I flashed today is smooth as hell good work , so far so good I report any bug
Edit
Is there a way to change buttons I want to use menu button as multitask and change the time for the illumination of them
P.S sorry for the errors English its not my language
Click to expand...
Click to collapse
Sorry changing buttons isn't built in, maybe something xposed framework can help with?
This is pure 100% straight AOKP.
Sent from my Nexus 7 using xda app-developers app
hv6478 said:
Was working quite well for the day I tried it so far. NFC needed a reboot when trying to disable it the first time. Jumped to the nightly for some testing but will be back on AOKP soon and report more.
Paulicat, will your kernel work with the official nightlies you think? They are also based on JLS3G as well.
Sent from my LG-E973 using xda app-developers app
Click to expand...
Click to collapse
My kernel and lights.geeb.so need to go together. I know they work on CM and a friend was going to try them on a PA ROM but I don't know outcome of that test yet.
As for the NFC needing a reboot, I would say with any ROM after initial setup give it a reboot to get things settled down.
Sent from my Nexus 7 using xda app-developers app
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.
Rom info
This rom is now out of support, I have removed all download links
I am leaving the thread just for historic reasons.
Hi, I have put together aosp 4.0.4 based on the work that yjwong started.
I have created a slightly modified device tree based of CM9 device tree and
cherrypicked patches from cm9. Mostly this rom use pure aosp 4.0.4 from Google.
all my sources can be found here: https://github.com/cleaton
rom philosophy and future
I will keep a code branch as close to aosp as possible for other developers
to base their rom from if they want. For my build open to small patches
for hardware improvements/optimizations and even UI enchantments
but overall it will stay very close to aosp.
I will also and keep my building close to the way Google intended release
builds to be meaning I do proper signing with my own release-keys
odex optimization,zipaligned and so on.
Changelog
V21.04.12:
updated kernel to 3.0.28 (thanks to myfluxi)
added touchscreen patches for better sensitivity (thanks to gokhanmoral and theamhacksung)
added gps patch recently added to cm9
changed camera focus release from 3 seconds to 15 seconds
(makes it easier to focus and re-frame before taking pictures)
V04.04.12-2:
changed signing keys
added signed gapps under download to work with this rom
enabled google backup (only works with the new signed gapps)
removed su, and voice dialer
forked and using LatinIME from cyanogenmod + added dictionaries
made my sources more independent from cm to be more stable
V30.03.12:
updated to 4.0.4 release
added scene, light, macro settings to camera from teamhacksug
added video recording fix from teamhacksung
added samsungservicemode from cm9
added galaxy s2 device settings app from teamhacksung
back to using aosp toolchain for compiling
moved to latest 3.0.15 kernel from teamhacksung
gps apps now shows more satellites and connection info, patch from cm9
using opensource hw codecs (again patches from teamhacksung)
many many thanks to teamhacksung for this great progress!
V24.03.12:
Changed default wallaper
system compiled with linaro 4.6 toolchain
compiled teamhacksung experimental 3.0.25 kernel
V21.03.12:
kernel compiled from teamhacksungs source
updated to LPQ proprietary libs
mtp fixed
better working edit effects for gallery (not 100% yet)
possible new bugs introduced.
V18.03.12:
system now mounted as ro
added quick toggle menu from teamkang via aospX
press settings button in notification bar for quick toggle (long press for settings)
V10.03.12:
Compiled with arm cortex optimization flag.
Fixed assert issue with install-script.
User build instead of userdebug but modified to allow adb root.
User build gives odex optimization of system.
Fixed proper build fingerprint override to be like Samsungs.
Backup/Upgrade script from CM to get smooth upgrades.
V06.03.12:
First release.
Disclaimer
I can not leave any guarantees or support for this rom, most of all I just build this for myself.
You are on your own and you have been warned.
Install
For install instructions, radio firmware and gapps look at the
CM9 user thread found here : http://forum.xda-developers.com/showthread.php?t=1419102
Upgrade from previous version:
Same instructions as in CM9 thread
but I will add Do your own backup
if you have something important!
Clearing cache and dalvik-cache is not needed
But is probably a good habit.
(I use this rom with XXLPQ modem)
If you can't figure out how to apply those instructions for my rom this rom is not for you...
This if for Galaxy S II I9100 (International galaxys2) nothing else.
Latest release
Download: v21.04.12 -*removed*- (SHA1 7cacc6732ef05dfa7e2b3b5bec8d397787b38505 koud-AOSP-4.0.4_v21.04.12.zip)
Gapps: -*removed*- (for v04.04.12 and up)
(SHA1 ad272390b92dc4b11e36d52aaa92f01d67df5af9 gapps-ics-20120317-kaosp-signed.zip)
Old
Download: v04.04.12-2 -*removed*- (SHA1 38b6a6d189ea82b5b8cdf95223720f90747bcb37 koud-AOSP-4.0.4_v04.04.12-2.zip)
Download: v30.03.12 -*removed*- (SHA1 bf5c611abe071c9b0b1578a63ef42ddc5accb2ef koud-AOSP-4.0.4_v30.03.12.zip)
Download: v24.03.12 -*removed*- (SHA1 3230452ebdac549ccea50125f5e4fa220e561778 koud-AOSP-4.0.3_v24.03.12.zip)
Download: v21.03.12 -*removed*- (SHA1 79979bfe67e30ef52e958efdd55b11b779e6fca2 koud-AOSP-4.0.3_v21.03.12.zip)
Download: v18.03.12 -*removed*- (SHA1 d09533994bc930042f0155800ddd804da485c780 koud-AOSP-4.0.3_v18.03.12.zip)
Download: v10.03.12 -*removed*- (SHA1 7b1938025a56527ab10120947b65414c9cefe96e koud-AOSP-4.0.3_v10.03.12.zip)
Download: v06.03.12 -*removed*- (SHA1 94654ccc555585696ac17b0ddeac090d199745bd koud-AOSP-4.0.3_v06.03.12.zip)
FAQ
Q: no root?
A: yes, no root.
If you want root you can take a look at what mikk_ wrote
http://forum.xda-developers.com/showpost.php?p=24791232&postcount=169
Not working
spell correction only works for english
disable spell correction and words wont be underlined, predictive word works.
3g data does not always work on first boot after clean install
reboot and it is fine after that.
fm radio and other smaller things
(check cm9, I try and keep up to date with cm9)
Credits
Credits to teamhacksung for their incredible work providing all the necessary
patches for sgs2, and also for their help in #aospsgs2 @ freen I find some of my kernel patches.ode
Thanks to CM team, teamkang, aospX and linaro-android for their great work with android patches
Thanks to gokhanmoral and myfluxi where I get some of my kernel patches.
Thanks to haramizuki for the awesome sign/banner
Enjoy!
Hey!
Could you tell me what the bugs are?
Thx!
Great Work
any bugs ore changes on cm9 base ?
hi have any changelog? or are mismatch on CM9 ..any screenshots? ..
Thanks..
netchip said:
Hey!
Could you tell me what the bugs are?
Thx!
Click to expand...
Click to collapse
I guess this as the Sam's bug which found in CM9...
BUGS KNOWN...:
1.video recording
2.MTP storage
3.Tethering(wifi)
Sent from my GT-I9100 using Tapatalk
Good job!
Envoyé depuis mon GT-I9100 avec Tapatalk
Super Koud! Thanks for your work, I'm downloading now!
Specific for sgs2 no, not that I know of, There are a few small features missing like the ability to choose macro mode and such in camera app. But I did include patch to get full 8mpix photo. AOSP bugs are included
i suggest you put a better and mature post with all the details or this thread will be spammed by noobs
Hey, lookimng forward to this! Good job
Are you looking to strip out CM features as you get more and more stable? Similar to this?That would be incredible, good luck and I'll be testing later.
bclark said:
Hey, lookimng forward to this! Good job
Are you looking to strip out CM features as you get more and more stable? Similar to this?That would be incredible, good luck and I'll be testing later.
Click to expand...
Click to collapse
Yes, it is possible. I am thinking about including some patches from linaro (mostly performance) and if there is something I miss from CM I might try and include it. I also want to try and implement some features of my own like use menu key for multitasking. It depends on how much time I need to spend on my studies
have problems installing it
in cwm got message:
assert failed:get prop("ro.product.device") == "galaxys2" || get prop(ro.build.product") == "galaxys2"
E:Error in /sdcard/download/koud-AOSP-4.0.3_v06.03.12.zip
(Status 7)
Installation abortet
I thought there might be error during download but I downloaded it 3 times (2 directly to phone and 1 to PC)
any avdice?
I'd download it again (different pc or browser). Or turn off signature checking in cwm.
Likely a corrupt download though
Sent from my GT-I9100 using XDA App
golcheck said:
have problems installing it
in cwm got message:
assert failed:get prop("ro.product.device") == "galaxys2" || get prop(ro.build.product") == "galaxys2"
E:Error in /sdcard/download/koud-AOSP-4.0.3_v06.03.12.zip
(Status 7)
Installation abortet
I thought there might be error during download but I downloaded it 3 times (2 directly to phone and 1 to PC)
any avdice?
Click to expand...
Click to collapse
It is not an error with the download, it is a mistake in the assert generation on my part. (I must have assert check turned off when I flashed)
edit: What rom are you coming from? It looks to be a mistake in install script but at the same time I can't replicate this coming from cm7.1 or cm9 with asserts enable/disabled and signing enabled/disabled. I have included SHA1 hash sum of the update.zip in first post so you can verify that the download is not corrupt.
koudd said:
It is not an error with the download, it is a mistake in the assert generation on my part. (I must have assert check turned off when I flashed)
edit: What rom are you coming from? It looks to be a mistake in install script but at the same time I can't replicate this coming from cm7.1 or cm9 with asserts enable/disabled and signing enabled/disabled. I have included SHA1 hash sum of the update.zip in first post so you can verify that the download is not corrupt.
Click to expand...
Click to collapse
Comming from latest CheckRom. Tried disable/enable asserts and signing but with no luck. Will try download it one more time
Can anyone else confirm if the rom works? so It is not just working for me.
Tested and working fine.
I once had the same install error, solved by flashing cm7/9 first, rebooting, then wiping and installing again ,and the problem was solved. It's def a script that conflicts with Cm/Samsung.
Regards
buzzboy said:
Tested and working fine.
I once had the same install error, solved by flashing cm7/9 first, rebooting, then wiping and installing again ,and the problem was solved. It's def a script that conflicts with Cm/Samsung.
Regards
Click to expand...
Click to collapse
It's weird that I have to flash another rom before flashing this one....
Another cause is flashing recovery through Rom manager:
http://forum.cyanogenmod.com/topic/40120-q-status-7-installation-aborted/
Cheers
buzzboy said:
Tested and working fine.
I once had the same install error, solved by flashing cm7/9 first, rebooting, then wiping and installing again ,and the problem was solved. It's def a script that conflicts with Cm/Samsung.
Regards
Click to expand...
Click to collapse
Thanks for the info, I guess it could also be that the rom got a bad cwm installed. Flashing cm7/cm9 before installing other rom might be good habit. Wish samsung would have a real recovery partition and not a ramdisk hack...
As of 18th May 2012 the fixes that are in the show content are kinda outdated. Simply use this:
KeiranFTW said:
The ROM is GSM, so if you are a CDMA user, flash this over the top.
Click to expand...
Click to collapse
Simply flash after installing aokp and be sure to thank Keiran & Atarii
First off I don't take all the credit for this as Supervenom did all the work originaly making the rom for Xperia and the CDMA fix was made by krabappel2548 & ICXPlay.
First, go to Supervenom's original thread and DL the Rom:
Link
As pricey2009 mentioned below using notepad can corrupt the update-script file so make sure to use notepad++ or Linux programs like (gedit, vi(m), pico).
Thx to Pax and Pricey for posting info on that.
Then change the update-script file in the zip you downloaded go to -> \META-INF\com\google\android and open updater-script find these lines:
Code:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus");
and delete them. Save it as it was with no .txt or . save it as update-script . And replace the old in the zip.
then download a slightly modified version of krabappel2548 cdma fix:
Mediafire
Or for milestone 5 download this with is the install zip with cdma libs:
cdma_aokp
Again thx to Supervenom, krabappel2548, ICXPlay, paxChristos, and anyone I forgot.
Pictures ---> attached
Change-log:
04/16/12
Released first fix
--noticed bugs as super user crashes upon opening preferences
--trying to sign-in to youtube crashes android core, both freeze phone, temporarily or forces a reboot.
Looking into fixing ^above and a fixed build.prop. Youtube is fine if you don't log-in fyi if you do you it starts getting buggy
04/19/12
-Found aonther bug google caneder and calender wigets are unstable. They don't acknowledge my account when adding activities at first but then brings me to the sync menu in settings and says account is already added.
-Forgot to actually post this sorry as it is a pretty big one. Usb connect is broken. sb development comes up ok no issues but no usb activity. This may just be my pc as some kernel's cwm usb isn't working either. Let me know if I'm the only one having this issue. <fixed in newest build
edit- 4/21/2012 Build.prop issuse fixed just download newest aokp from super venom's thread.
-5/6/12 aokp install zip with cdma libs, no more usb issues
if you have problems with market re-flash gapps
cj360 said:
Change-log:
04/16/12
Released first fix
--noticed bugs as super user crashes upon opening preferences
--trying to sign-in to youtube crashes android core, both freeze phone, temporarily or forces a reboot.
Looking into fixing ^above and a fixed build.prop.
Click to expand...
Click to collapse
So does this mean you've fixed these issues or you ARE going to
the last part is kinda confusing ?
any also wouldn't the person have to resign the .zip to make the edited files work when flashed in CWM recovery?
cj360 said:
Change-log:
04/16/12
Released first fix
--noticed bugs as super user crashes upon opening preferences
--trying to sign-in to youtube crashes android core, both freeze phone, temporarily or forces a reboot.
Looking into fixing ^above and a fixed build.prop.
Click to expand...
Click to collapse
Also, what CDMA is this for if it's not for the R800x?
Working on the fixes, upload them when I can. And I believe your thinking of apk editing as they have to be resigned after modding. As I haven't gotten errors in cwm as much as just running normally. And as for the build.prop it's not orginaly made for cdma. The Xperia devices it was made for were gsm but other than the mobile network setup being different everything else on the devices are identical.
Tried out the original rom with no changes to it, ran fine to what I found/saw wifi worked the only thing that didn't was the data.
cj360 said:
Working on the fixes, upload them when I can. And I believe your thinking of apk editing as they have to be resigned after modding. As I haven't gotten errors in cwm as much as just running normally. And as for the build.prop it's not orginaly made for cdma. The Xperia devices it was made for were gsm but other than the mobile network setup being different everything else on the devices are identical.
Tried out the original rom with no changes to it, ran fine to what I found/saw wifi worked the only thing that didn't was the data.
Click to expand...
Click to collapse
Aokp is built from CM9, correct? Do you just want the porting libs I use & the file that lists all the differences between gsm/cdma CM9?
Sent from my phone, please excuse any Swypos.
You cannot edit updater-script using just normal notepad.. it will become corrupt.
Use notepad++ instead
pricey2009 said:
You cannot edit updater-script using just normal notepad.. it will become corrupt.
Use notepad++ instead
Click to expand...
Click to collapse
Or anything in Linux (gedit, vi(m), pico, etc)
Sent from my phone, please excuse any Swypos.
@pax yes please!
@pricey2009 I've done it with notepad before when I flashed cm7. No issues
cj360 said:
@pax yes please!
Click to expand...
Click to collapse
As soon as I'm done building the newest CM9 for cdma, I'll send it your way (via pm) (Android building is using up all my system resources )
Sent from my phone, please excuse any Swypos.
cj360 said:
@pax yes please!
@pricey2009 I've done it with notepad before when I flashed cm7. No issues
Click to expand...
Click to collapse
Strange as I have done it lots and everytime I end up with corrupt script.. nevermind!
Quick question, a status 4 error during the installation of the zip file is the result of me messing with the script, but what exactly am i doing wrong??
HankKing said:
Quick question, a status 4 error during the installation of the zip file is the result of me messing with the script, but what exactly am i doing wrong??
Click to expand...
Click to collapse
Double check your updater-script. (if necessary, use notepad++)
Pax
Also if you like blue you might like Nitroz's Skycore theme folders and directories or the same so it works fine.
cj360 said:
Also if you like blue you might like Nitroz's Skycore theme folders and directories or the same so it works fine.
Click to expand...
Click to collapse
So its ok to flash this? Just double checking..
Don't see why not as I'm running it on my xperia play just fine.
cj360 said:
Don't see why not as I'm running it on my xperia play just fine.
Click to expand...
Click to collapse
Downloading now.. 1.4 rite?
Yup. Make Android to avoid disaster then simply install the zip from cwm
Sent from my R800x using xda premium
Its lagging my phone slightly... but the themes awwesome..
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