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..
Related
I found this link on internet
http://4pda.ru/forum/index.php?showtopic=269888&st=340#entry9732782
What about it? Any one have tested this ?
dragonnn said:
I found this link on internet
http://4pda.ru/forum/index.php?showtopic=269888&st=340#entry9732782
What about it? Any one have tested this ?
Click to expand...
Click to collapse
downloading it now. we'll see. so far the replies about 7.2 are good.
I'll also test it.
Waiting for your tests, if all will by good I will it test too .
not much of a difference in terms of feeling. but so far so good. but really... almost no difference.
Yes, almost no difference, but runs great.
the difference is under the hood.
not all changes is just about cosmetics u know
u can see changelog of cm 7.1 from cm site and compare it to cm 7.2 changelog, and see whats been added from 7.1 to 7.2.
edited: a link, http://forum.cyanogenmod.com/topic/36710-cm-72/
****, I am having a small problem with installing this package, I am getting an error
Code:
asset failed: getprop("ro.product.device") == "cooper" ||
....
Installation aborted
I have only write the begin of this because is very long. Any way to fix it?
EDIT
I have upload my recovery.log http://dl.dropbox.com/u/1664131/recovery.log i hope it helps.
Any way to fix it?
Click to expand...
Click to collapse
try to go with root explorer in /system and open the build.prop
find the line : ro.product.device and confirm if the name on the " " is cooper
ro.product.name=full_galaxyace
ro.product.device=galaxyace
ro.product.board=galaxyace
change this 3 lines to cooper in build.prop and try again!
This is very strange. Here is my bulid.prop
http://dl.dropbox.com/u/1664131/build.prop
I already have ro.product.device=cooper
http://www.sendspace.com/file/k8ko80
if u want to try, replace for my build.prop
I have fixed it, just update my recovery cwm from v4 to v5 and it works.
thnx your solution worked... now i have cm 7.2 thanks.......
I cant get wifi to connect and get ip address with this rom. I'm using the one from Ketut.
Got it to work, its just need some more time to connect (5 mins to get ip). That was strange, but works fine.
I had it for a short time, works good but jusada MIUI like battery bar don't work on it and I love this mod because this I go back to 7.1.
can anyone say if the facebook login problems have been fixed?
http://forum.xda-developers.com/showthread.php?p=19655160
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.
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
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
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.