Related
This is the beggining of my build.prop (CM7 7.1 Final)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GWK74
ro.build.display.id=Gingerbread GWK74
ro.build.version.incremental=20111009
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sun Oct 9 18:20:42 PDT 2011
ro.build.date.utc=1318209642
ro.build.type=user
ro.build.user=CyanogenDefy
ro.build.host=buildbot1
ro.build.tags=release-keys
ro.product.model=MB525
ro.product.brand=MOTO
ro.product.name=MB525_JOREM_U3
ro.product.device=umts_jordan
ro.product.board=jordan
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=umts_jordan
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=umts_jordan-user 2.3.7 JOREM_U3_3.4.2-179-4 1318209610 release-keys
ro.build.fingerprint=MOTO/MB525_JOREM_U3/umts_jordan/jordan:2.3.7/3.4.2-179-4/1318209610:user/release-keys
# end build properties
#
# system.prop for jordan
#
I would like to "convert" in a Motorola Milestone 2 to buy some Gameloft games in Market (in special for the 10 million promo). What changes must I do?
Thx.
P.S: WTF, Milestone 2 is not supported. Anyone knows how to buy apps not supported? I still interested in change my phone model
U can either change the product model &/or download market enabler for the android market
Sent from my MB526 using XDA App
Any example that allows me to buy Backstab HD and doesn't brick my phone?
Motorola droid x & samsung galaxy s are supported for back stab... & i think motorola defy can play samsung galaxy s games not sure abt droid x...
Oh! Games dont brick phones as far as i know
Sent from my MB526 using XDA App
I know that games maybe don't brick my Defy, but a bad edition of buil.prop I'm sure that at least will force me to reinstall my rom.
Can anyone help me? Can I "convert" my Defy in a Samsung Galaxy S for market? How do I it?
Thats true but changing ur brand or model on in the build prop file, wont brick ur fone... Many ppl do this as well, alter their build prop brand & model to either buy, install or download extra data for a game. Then simply restore their backed up build prop file
Sent from my MB526 using XDA App
thx. i need it.
I want to buy Backstab too, but have not been able to fake another phone model.
It worked when I changed from mb526 to 525 so Asphalt would work, but so far no luck with the change to SG S
Anyone know what to change?
Ps. you could still make a flasheable .zip, only with the build.prop. Just in case anything goes wrong
Gesendet von meinem CM7 Defy
SGS is not supported for Backstab.
How do I that flasheable zip?
Well, change build.prop has broken my rom, re-flashing again.
P.S: I did an update.zip with build.prop (\system\build.prop) but recovery didn't recognise it as an update. I tried to make a file bigger with more dirs, but it bricked my phone (before I did wipes, etc). I tried to come back to my original Vodafone firmware, it seemed to work but the phone beggin a bootloop. I did Power + voldown and then voldown+volup, wipe factory and it seems to work again.
Magnux said:
SGS is not supported for Backstab.
How do I that flasheable zip?
Click to expand...
Click to collapse
There are a few proper ways to make a flasheable CWM .zip, just search in google
I did the really dirty cheap way tho lol, took a working .ZIP that only installed a file on /system, removed that app and just added an untouched build.prop using WinRAR.
Zephyrot said:
I want to buy Backstab too, but have not been able to fake another phone model.
It worked when I changed from mb526 to 525 so Asphalt would work, but so far no luck with the change to SG S
Anyone know what to change?
Ps. you could still make a flasheable .zip, only with the build.prop. Just in case anything goes wrong
Gesendet von meinem CM7 Defy
Click to expand...
Click to collapse
Try changing to droid x
Sent from my MB526 using XDA App
Magnux said:
Well, change build.prop has broken my rom, re-flashing again.
P.S: I did an update.zip with build.prop (\system\build.prop) but recovery didn't recognise it as an update. I tried to make a file bigger with more dirs, but it bricked my phone (before I did wipes, etc). I tried to come back to my original Vodafone firmware, it seemed to work but the phone beggin a bootloop. I did Power + voldown and then voldown+volup, wipe factory and it seems to work again.
Click to expand...
Click to collapse
Sorry to hear... Okay. So, u only changed the product brand & model?
When editing ur build prop be sure not to add any extra spaces or lines
Feel free to try the following changevto the build prop (& back up ur rom to be on the safe side):
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
Sent from my MB526 using XDA App
After a day as yesterday I will not write more times in build.prop... at the moment XD
after changing my built.Prop for running some software my android market device changed and I don't know how to get the old one back, and that is Motorola.
Please help me!!!!!
Alex.... Which device u using & what rom are u on?
Sent from my MB526 using XDA App
Mariofrith said:
Sorry to hear... Okay. So, u only changed the product brand & model?
When editing ur build prop be sure not to add any extra spaces or lines
Feel free to try the following changevto the build prop (& back up ur rom to be on the safe side):
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
I just try on my Defy MB525 Bayer Device with 13 December 2011 CM9 Rom ICS .
Impossible to download Sygic Aura, i just buy it because when i go to market i see Sigyc Voucher but impossible to activate because say install Sygic Aura before ^^
Dont work i think i miss some information for google account say it's Samsung device with froyo or gingerbread .
Thanks if anyone can help me .
I changed ro.build.fingerprint and it works well for many Apps shown before as "incompatble to your phone" (in german Market it's called else "inkompatibel mit Ihrem Gerät")
ro.build.fingerprint=MOTO/MB526_RTDACH/umts_jordan:2.3.4/4.5.1-134_DFP-74/1313117579:user/release-keys
Mariofrith said:
Sorry to hear... Okay. So, u only changed the product brand & model?
When editing ur build prop be sure not to add any extra spaces or lines
Feel free to try the following changevto the build prop (& back up ur rom to be on the safe side):
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
Anyone has check it? Is it safe? Must I reboot my phone? Any kind of problem? I don't want to reinstall my rom again.
I can't buy NFS Hot Pursuit in the market (and there is a new promo).
I have Moto Defy CM7.1.
P.S: I tried it and it works but the brightness is ever low.
Well i will share my knowladge to you people, two years of learning stuff about android....
If this guide dont help you (0,01 possibilities) LOGCAT YOUR BUILD!! I WILL TRY TO HELP
Tools needed /by saranhai/:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
First to port an ics rom you need winrar.
This are the steps:
grab an ics rom like cm9 or aokp to take the libs and hw folders
Never unzip the rom.
1-from cm9/aokp copy all outside system, i mean boot.img mtd etc..... and past it over the rom you are porting (nexus s rom)
2-enter system/app and remove torch.apk, crespoparts.apk and replace camera.apk with aokp camera.
3-enter system bin and replace this files with aokp/cm9 ones
*dhcpcd
*bluetoothd
*vold
*wpa_client
*wpa_supplicant
Click to expand...
Click to collapse
4-enter system etc and replace this files with aokp/cm9 ones
*bluetooth folder
*dhcpcd folder
*Apnconf.xml
*wifi
*vold.fstab
*vold.conf
Click to expand...
Click to collapse
5-Then we go to the libs, enter system/lib and replace:
*HW folders
*modules folders
*egl folders
*libril.so
*libsec-ril.so
*libreference-ril.so
*libsec-ril-client.so
*libbluedroid.so
*libbluetooth.so
*libbluetoothhd.so
*lib_cameraclient.so
*libcameraservice.so
*libhardware_legncy.so (very important to wifi to work) hell this caused me problems
*libEGL
*libgles (the 3 files)
Click to expand...
Click to collapse
--------------replace usr and vendor folders-------------------
And last edit build.prop, well first check if it boots then you change this and add this.
edit this:
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ADD THIS TO SIGNAL TO WORK!!
additional build propieties
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3
=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
Click to expand...
Click to collapse
ADVANCED USERS ONLY (dont ask me how) :
for working external sd (emcc) you need to decompile/recompile framework-res.apk
you need to change this:
xml/storage_xml with other storage xml from aokp or cm9
Click to expand...
Click to collapse
I´m not responsible for bricked devices (this shouldnt brick it) but i dont want anyone crying because i will laugh at you, it works for me..
Libs functions
Lib:
*Libhardware_legancy.so (makes wifi works)
*all libs with ril: DATA and SIGNAL
*LibEGL, modules, hw: hw aceleration, lights,etc...
*Libgles (Gpu and cpu)
Click to expand...
Click to collapse
etc:
*apns-conf.xml (all related to apn and services)
*dchcpd,vold.ftsab,vold.conf: internal sd
*wifi,bluetooth: wifi bluetooth lol
Click to expand...
Click to collapse
someone correct me if im wrong but im preaty sure what im writing...
Thanks for this thread. It should give many new possibilities!
amazing guide thx for sharing
Things i would add:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows, used to edit build.prop and other text files)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
I will add more if i think of any
EDIT: Forgot this...
If you are experiencing issues booting up, here's how to get a logcat so you can figure out what's wrong:
connect phone to computer
open up command prompt
navigate to your android sdk tools folder i.e C:/androidsdk/platform-tools (ADB MUST BE SET UP BEFOREHAND)
type in:
Code:
adb logcat
watch as a whole bunch of text scroll by, don't bother reading it right now, do it later.
If you want to stop the logcat, just disconnect phone from computer.
-Saranhai
saranhai said:
Things i would add:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows, used to edit build.prop and other text files)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
I will add more if i think of any
-Saranhai
Click to expand...
Click to collapse
Okey i added them
Nice guide. Thanks.
Nice guide!!! Thanks!
Will try this out later
Sent from my PG86100 using xda premium
i have a question ... How you can test your own ported rom ? Because i dont want to brick my phone (again) ))
Driv said:
i have a question ... How you can test your own ported rom ? Because i dont want to brick my phone (again) ))
Click to expand...
Click to collapse
oh, haha i dont think there is another way rather than using your device as a lab rat.... lmao
I give you an unbrickeable guide, if you dont forget to swapp the boot.img and hw and modules folder you wont brick it since recovery is on the kernel, so you can restore or do what you want, if you flash a nexus s kernel (as example you forgot to remove it) you will soft brick it
Madflapjack respond to your pm's, I need some help!
EDIT: resurrected a dead thread sorry..
Sent from my GT-I9000 using xda app-developers app
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
malcho said:
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
Click to expand...
Click to collapse
exactly what i want to ask for. since nexus S got the OTA official update.
malcho said:
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
Click to expand...
Click to collapse
im ok thanks for asking !! i moved to the galaxy nexus thats why im not posting much lol, im playing with the baby!
to the point, you should try, it wont harm, but if you do try, dont port aosp, they need special coding in framework or something similar and you will get a nice dark screen on booting, well if its cyanogenmod or aokp then yes it should work..
Madflapjack said:
im ok thanks for asking !! i moved to the galaxy nexus thats why im not posting much lol, im playing with the baby!
to the point, you should try, it wont harm, but if you do try, dont port aosp, they need special coding in framework or something similar and you will get a nice dark screen on booting, well if its cyanogenmod or aokp then yes it should work..
Click to expand...
Click to collapse
Nice to see that you are ok.
My constant struggle with codenameandroid,trying few guides butt none work.
It's ok i will wait till sources are out.
Many regards
malcho said:
Nice to see that you are ok.
My constant struggle with codenameandroid,trying few guides butt none work.
It's ok i will wait till sources are out.
Many regards
Click to expand...
Click to collapse
jb codenameandroid? it should work, worth the try!! but well remember to replace the kernel so you dont lose your recovery and your good to go.
if i dont bad remember my codename android port was booting and all ok, i was talking about pure aosp,
T
Madflapjack said:
jb codenameandroid? it should work, worth the try!! but well remember to replace the kernel so you dont lose your recovery and your good to go.
if i dont bad remember my codename android port was booting and all ok, i was talking about pure aosp,
Click to expand...
Click to collapse
I tried butt it stuck on boot animation.
Trying tommorow again.
malcho said:
T
I tried butt it stuck on boot animation.
Trying tommorow again.
Click to expand...
Click to collapse
so it boots, try watever you know to make it boot, if not logcat. lol
I just wrote a script that would automatically port ANY carrier's gs3 roms to ANY other carrier's devices
So now u can use all the roms other carriers get
Let me know if there are any errors(not including not found errors)
THIS ON OMG! DROID
http://omgdroid.com/script-released...-iii-custom-rom-to-any-other-carriers-device/
The future of this:
1. Ill add all the proprietary files from all the carriers so u dont have to have a base. DONE
2. UNIVERSAL ZIPS FOR ALL US GS3S THIS WILL TAKE A LONG TIME CUZ I HAVE TO LEARN HOW TO USE AROMA OR WRITE AN UPDATER-SCRIPT BUT IT WILL COME!!!(If anyone wants to teach me how to do those just pm me.) DONE BUT NOT GONNA RELEASE YET
3.Ability to automatically port ANY phones ROM to ANY other phone as long as they have the same dpi, manufacturer, and arm version. WORKING ON THIS. LEARNING PYTHON
How to use:
Linux:
1. download the rom u want to port and a rom on the SAME android version as the rom u want to port
2. unzip both of them and place both folders in the same folder
3. download the script and place it in the folder with the two rom folders
4. open a terminal and cd to the directory
5. run:
Code:
chmod +x portscript.sh
./portscript.sh
6. PROFIT
FOR WINDOWS I RECOMMEND CYGWIN AND THE LINUX VERSION. THE WINDOWS VERSION IS KINDA MESSED UP.
Windows(experimental):
1. download the rom u want to port and a rom on the SAME android version as the rom u want to port
2. unzip both of them and place both folders in the same folder
3. download the script and place it in the folder with the two rom folders
4. rename the rom you want to port's folder to port
5. double-click on portscript.bat
6. PROFIT
How to port rom from galaxy nexus or any other xhdpi armv7 samsung device:
1. inside ur base rom, open META-INF/com/google/android/updater-script as a text file and copy the mount points (like mount(/dev/block/mmcblk0p8, /system) you would copy /dev/blockmmcblk0p8)
2. Download script and do the porting procedure
3. open up the rom u are porting's META-INF/com/google/android/updater-script and replace the mounting with the values u copied.
4. save and move the updater-script to ur base's META-INF/com/google/android/ and replace
NEW!!!
NO NEED FOR BASE:
1. download the nobase script zip and extract it somewhere
2. download a device's proprietary files zip and extract it into the folder of the script
3. run the script and follow directions!
how to add a device to the nobase script:
download and unpack the zip with ur desired carrier/android version
run the portdiffs.sh and follow directions!
Disclaimer:
Im not responsible for anything that might go wrong
Changelog:
v3: more fixes
v2: fixed update-binary being update_binary
DLs:
.bat s are windows, .sh is linux.
portscriptnobase is linux
https://docs.google.com/folder/d/0B2qlFDXo6JOreUY3RjFkRm1aeFU/edit
Thanks to d3athsd00r for helping
does this apply for international GS3????
ice3186 said:
does this apply for international GS3????
Click to expand...
Click to collapse
Probably
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
What!! No way dude!!
White Hot! GS3.
cpu999 said:
I just wrote a script that would automatically port ANY carrier's gs3 roms to ANY other carrier's devices
So now u can use all the roms other carriers get
Let me know if there are any errors(not including not found errors)
How to use:
1. download the rom u want to port and a rom on the SAME android version as the rom u want to port
2. unzip both of them and place both folders in the same folder
3. download the script and place it in the folder with the two rom folders
4. open a terminal and cd to the directory
5. run:
Code:
chmod +x portscript.sh
./portscript.sh
6. PROFIT
Disclaimer:
Im not responsible for anything that might go wrong
DLs:
Realease 1 (Prealpha)
Click to expand...
Click to collapse
I am probably treading into an area that I have no business going to - but I would love to try this - and don't have enough knowledge to follow your instructions - was hoping you could explain the last few steps - I am going to sound like a real noob - but I don't understand some of the language -
what do you mean when you say "open a terminal and cd to the directory" ? if you can simplify that a little - I think I can do this and would love to try -
I think it means that I need to put save the roms and the script you have provided and place them in my C drive - then open a command prompt in that file (shift and right click I believe) is that correct?
second question - when I tried to download the file you provided from the lnk - it opened GOOGLE DRIVE and said I needed to request permission to access the file - ? I clicked request and am now waiting for some kind of response
?
cpu999 said:
Probably
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
No that will not work. If this does simple recovery mount point changes & build prop changes that will work for the family of SGS3 that share the same hardware. It will not work for i9300 as that has a different set of hardware. Thus, different libs and what not.
I doubt this script has the ability to decompile & merge correctly smali. Or has a downloadable collection of libs for i9300. Probably only works for the SGS3 variants like AT&T, telus, tmobile, etc.
iBotPeaches said:
No that will not work. If this does simple recovery mount point changes & build prop changes that will work for the family of SGS3 that share the same hardware. It will not work for i9300 as that has a different set of hardware. Thus, different libs and what not.
I doubt this script has the ability to decompile & merge correctly smali. Or has a downloadable collection of libs for i9300. Probably only works for the SGS3 variants like AT&T, telus, tmobile, etc.
Click to expand...
Click to collapse
Thanks
will be adding that to the OP
mocsab said:
I am probably treading into an area that I have no business going to - but I would love to try this - and don't have enough knowledge to follow your instructions - was hoping you could explain the last few steps - I am going to sound like a real noob - but I don't understand some of the language -
what do you mean when you say "open a terminal and cd to the directory" ? if you can simplify that a little - I think I can do this and would love to try -
I think it means that I need to put save the roms and the script you have provided and place them in my C drive - then open a command prompt in that file (shift and right click I believe) is that correct?
second question - when I tried to download the file you provided from the lnk - it opened GOOGLE DRIVE and said I needed to request permission to access the file - ? I clicked request and am now waiting for some kind of response
?
Click to expand...
Click to collapse
this script only works in linux for now.
Ill create a windows one once I have time
LuRock said:
What!! No way dude!!
White Hot! GS3.
Click to expand...
Click to collapse
Its just an automation of my method of porting
yea it def will not work for 9300 youll have to change a lot of stuff just to get it booting
cpu999 said:
this script only works in linux for now.
Ill create a windows one once I have time
Click to expand...
Click to collapse
so if lets say i got a tmobile gs3 and want to port an att rom, will it add wifi calling too?
even if it ports the wifi calling from tmobile..it won't work on att. it'll not be recognized as it requires tmobile service to really work.
Sent from my SAMSUNG-SGH-I747 using xda premium
lazarat said:
so if lets say i got a tmobile gs3 and want to port an att rom, will it add wifi calling too?
Click to expand...
Click to collapse
no.
this is just a simple script that would port things.
it just makes the rom compatible wiht ur phone
cpu999 said:
no.
this is just a simple script that would port things.
it just makes the rom compatible wiht ur phone
Click to expand...
Click to collapse
Oh ok thanks..althogh up till this point i have had no problems using att roms on my tmo gs3
Being a windows user I have to wait until you create a version for that - can't wait to try i t- I am not a developer but if this works - it opens all kinds of opportunties to try new thing s- I am adventurous = and I ahve insurance on my phone - lol - looking forward to giving this a shot -
I was wondering when someone was going to do this. I was going to if I could ever get time away from my real job. Thanks for the contribution!
Sent from my GS3 using xda premium
Sorry of this is a dumb question but if this script works then I could use this to use T-Mobile roms on my att s3?
Sent from my htc_jewel using xda app-developers app
wwevoxnj said:
Sorry of this is a dumb question but if this script works then I could use this to use T-Mobile roms on my att s3?
Sent from my htc_jewel using xda app-developers app
Click to expand...
Click to collapse
its ANY us gs3 rom to ANY us gs3 rom
Wow I can't wait for a windows version of this!! I'm addicated to flashing roms haha.
Sent from my htc_jewel using xda app-developers app
I've flashed many T-Mobile roms on my at&t / rogers s3 already...
FreeGS3 r6, Gigajule, Wicked v5 all works great as long as you flash the right kernel and never flash a modem...
Sent from my SGH-T999 using Tapatalk 2
Morning managed to get 4.2.2 from the gsm version of galaxy nexus working on my vzw galaxy by changing the build prop and adding and deleting some files in the lib folder and adding and deleting xml's for the vpn.. the 4.2.2 I flashed isn't mine so I take no credit for it just used it to flash because it was deoxeded and rooted already... it was zipped by bigxie (bigxie_magurTA_JDQ39-signed.zip) just look in the gsm galaxy nexus thread. Flashed rom first then flashed current vzw radios and then moded files and set permissons. The files were:
sys-Vendor-lib" libsec-ril_lte.so from 4.2.1 and deleted libsec-ril.so from "lib"
"ECT" apns-conf.xml from 4.2.1 and deleted the original file
"ECT--PERMISSIONS" com.vzw.hardware.lte.xml from 4.2.1 and com.vzw.hardware.ehrpd.xml and deleted com.hardware.telephony.gsm.xml
Modded Build.prop for cdma and lte...(there wasn't to many but not gonna list them all)
wiped cache and dalvik and now have a strong 4G signal and fast data...not a developer here at all, just tried to figure out how to get lte and vpn on 4.2.2 so sorry for bad post...good luck..
Mwalt2 did a complete mod in zip form with bigxie rom that is a smoother and grabs signals better and no messing with permissions and everything like that so way easier...here is the link
http://forum.xda-developers.com/showthread.php?p=37928151&posted=1#post37928151
hmm somethings not right with a 909 KB file
proceed with caution
uninc4709 said:
hmm somethings not right with a 909 KB file
proceed with caution
Click to expand...
Click to collapse
the 4.2.2 rom isn't in there just the files I added, screen shots, and the modded build.prop, but just a weekend warrior here so not sure if I just got lucky but all is working good so far
pricematthew4143 said:
the 4.2.2 rom isn't in there just the files I added, screen shots, and the modded build.prop, but just a weekend warrior here so not sure if I just got lucky but all is working good so far
Click to expand...
Click to collapse
There are a few other things that will need changed. I'd think that your GPS and WiFi aren't going to work well or at all. I've posted a list of CDMA files that need to be included on this forum before and I think in the q&a gnex forum (search there first for posts by me and see of you can find it...I would but won't be on a PC for awhile).
Sent from my Galaxy Nexus using Tapatalk 2
mwalt2 said:
There are a few other things that will need changed. I'd think that your GPS and WiFi aren't going to work well or at all. I've posted a list of CDMA files that need to be included on this forum before and I think in the q&a gnex forum (search there first for posts by me and see of you can find it...I would but won't be on a PC for awhile).
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
They worked but weak better now though thanks for the help..I was just happy I got the 4g to work lol..thanks
Sent from my Galaxy Nexus using Tapatalk 2
notice any difference from 4.2.1.?
Yeah it seems to be smoother in the animations and the color band is a lot less..lock screen widgets are different, larger
Sent from my Nexus 7 using Tapatalk HD
cool, so for this to work should i flash
this:
http://forum.xda-developers.com/showthread.php?t=1737849
and then the zip you posted?
andrewlax120 said:
cool, so for this to work should i flash
this:
http://forum.xda-developers.com/showthread.php?t=1737849
and then the zip you posted?
Click to expand...
Click to collapse
That link is for the GSM Galaxy Nexus. I wouldnt flash that on your Verizon Galaxy Nexus. If I understand this right, the zip file given here are just the files you have to manually replace yourself in a file browser and not a flashable zip.
jsgraphicart said:
That link is for the GSM Galaxy Nexus. I wouldnt flash that on your Verizon Galaxy Nexus. If I understand this right, the zip file given here are just the files you have to manually replace yourself in a file browser and not a flashable zip.
Click to expand...
Click to collapse
i understand that thats a gsm version. but to get this going don't i have to flash that rom as a the base and follow the op by replacing the system files?
they would be set rw-r-r correct?
i may just hold off a few days but im anxious to get these bugs fixed :laugh:
andrewlax120 said:
i understand that thats a gsm version. but to get this going don't i have to flash that rom as a the base and follow the op by replacing the system files?
they would be set rw-r-r correct?
i may just hold off a few days but im anxious to get these bugs fixed :laugh:
Click to expand...
Click to collapse
I just re-read the OP and I guess thats what he did. Flash the GSM zip and replace files with Verizon files. I havent tried it. I, personally, am going to wait for something else.
andrewlax120 said:
cool, so for this to work should i flash
this:
http://forum.xda-developers.com/showthread.php?t=1737849
and then the zip you posted?
Click to expand...
Click to collapse
yeah that's what worked for me, the rooted 4.2.2 and those files and i got 4g, and the correct vpn showing afterwards...even the baseband showed correct after the build prop changes so Yep...should work out just don't forget to set permissions and delete the gsm files..
jsgraphicart said:
I just re-read the OP and I guess thats what he did. Flash the GSM zip and replace files with Verizon files. I havent tried it. I, personally, am going to wait for something else.
Click to expand...
Click to collapse
yes the permission are set rw-r-r or 644 and it was kind of easy you just have to get lte/cdma files in the lib or ect so the rom knows to look for lte or cdma and not gsm...all they are are xml files and just have to add a bunch of ro.cdma and change the name in build prop..i was actually surprised how easy it was when the baseband showed correct and I got a blue 4g signal
jsgraphicart said:
That link is for the GSM Galaxy Nexus. I wouldnt flash that on your Verizon Galaxy Nexus. If I understand this right, the zip file given here are just the files you have to manually replace yourself in a file browser and not a flashable zip.
Click to expand...
Click to collapse
no...I did flash the GSM 4.2.2 on my CDMA VZW GN, there is NO GSM RADIO IMAGE on the 4.2.2 GSM ROM the dev removed it.. so there is not damage to the CDMA GN... so you are just flashing a ROM meant to pick up GSM, all you have to do is replace the files so the rom picks up lte/cdma...and all they are are xml files and one .so file and the build prop to tell the phone where to look...thats all...it was actually really easy
jsgraphicart said:
I just re-read the OP and I guess thats what he did. Flash the GSM zip and replace files with Verizon files. I havent tried it. I, personally, am going to wait for something else.
Click to expand...
Click to collapse
yep, just replaced the gsm .so and xml's with lte/cdma and changed build prop so the phone can figure it out..that's it.
andrewlax120 said:
cool, so for this to work should i flash
this:
http://forum.xda-developers.com/showthread.php?t=1737849
and then the zip you posted?
Click to expand...
Click to collapse
and sorry for the confusion that zip is NOT flashable just the files I used to get the rom over to lte/cdma..I used root explorer to add the lte/cdma files and for setting perms
Hij,
I tried doing the same on Sprint Galaxy Nexus.. But it didn't work. Do you have any tips?
Cheers
mkalter said:
Hij,
I tried doing the same on Sprint Galaxy Nexus.. But it didn't work. Do you have any tips?
Cheers
Click to expand...
Click to collapse
the only way i figured it out was to look at the build prop especially the RIL lines..they give the exact file that needs to be replaced
ex. on the gsm: rild.libpath=/vendor/lib/libsec-ril.so libsec-ril.so is the driver the rom is looking for
I replaced the file in the "lib" folder and build.prop line with rild.libpath=/vendor/lib/libsec-ril_lte.so so the rom will now look for the lte driver
make sure the "telephony.lteOnCdmaDevice" line equals 1 it tells the phone that it is a lte/cdma device..if there is a 0 the phone thinks it is a gsm device
also don't forget to set permissions as rw-r-r as they are in screenshots and to delete out the gsm files ...they aren't named the same so there is no overwrite or replace.. you have to delete them. I don't know how sprint files and radios are setup though but I hope this helps...
You guys may as well replace the files in the gsm zip before flashing it and save yourselves some time. There's no reason to do it after unless you just like using a file explorer on your phone. Also, an easy way to see what is different is to compare CM roms for the gnex.
Sent from my Galaxy Nexus using Tapatalk 2
Have binaries for 4.2.2 been released yet
Sent from my Galaxy Nexus using Tapatalk 2
I've started to port Sense 4.1 lite from HTC Desire X 1.18.401.1 to our phone. I've been following this guide to port it, but when booting I always get a blackscreen and it doesn't do anything =/. I can't enable ADB, even though I've added persist.service adb.enable line in the build.prop. I know that it generates things in the data partition, because the ADB in recovery shows it. Does anyone have any ideas on how to get this working?
may be you have to edit res-framework.apk to make a rom working!
gulsher said:
may be you have to edit res-framework.apk to make a rom working!
Click to expand...
Click to collapse
Do you know what parts of it? I'm not so great at sense rom porting =/
Decompile
1. Download these files:
http://dl.dropbox.com/u/54258750/apktool1.4.2.31e6dc5.jar
md5: 38db374a2f733000b1b0309b2b99f74b
http://dl.dropbox.com/u/54258750/aapt.exe (from the latest R16 SDK)
md5: 26a35ee028ed08d7ad0d18ffb6bb587a
http://dl.dropbox.com/u/54258750/apktool.bat
md5: 2bf3b895011fc4b1801edcfbabfdc295
2. Copy all files to your 'Windows' directory and rename apktool1.4.2.31e6dc5.jar to apktool.jar
3. Open command prompt, and install framework (apktool if framework-res.apk)
4. Decompile with apktool1.4.2.31e6dc5.jar (everytime use this to decompile framework-res.apk)
apktool d framework-res.apk
Rebuild
1. Download http://code.google.com/p/android-apktool/downloads/detail?name=apktool1.4.3.tar.bz2 and copy to your windows directory (overwrite the old apktool.jar)
md5: 3d0478c4d23c7829edc024266697fef9
2. apktool b framework-res
3. extract all files from 'dist\apktool-res.apk' and create new archive with winrar or 7zip (archive type: zip | compression method: store)
4. resign
5. zipalign
6. Rename to famework-res.apk
---------- Post added at 09:04 PM ---------- Previous post was at 09:01 PM ----------
try to copy these lib
Libandroid_runtime.so
Libandroid_servers.so
Libmedia_jni.so
if rom is not booting
MameTozhio said:
I've started to port Sense 4.1 lite from HTC Desire X 1.18.401.1 to our phone. I've been following this guide to port it, but when booting I always get a blackscreen and it doesn't do anything =/. I can't enable ADB, even though I've added persist.service adb.enable line in the build.prop. I know that it generates things in the data partition, because the ADB in recovery shows it. Does anyone have any ideas on how to get this working?
Click to expand...
Click to collapse
Waiting for your Android 4.0.4 Sense 4.1 :good:
Well I managed to get it to show Boot animation, I edited the build.prop.
I still can't get a logcat, I tried to make an init.d script to logcat a file to the sdcard, but that didn't want to work.
I'm using my own guide now, but no matter what I do it doesn't boot.. anyone else able to help?
I've also switched base to Asia HK 2.24.708.1, it isn't much different from the telus_wwe base I was using.
That thread your using wont work for Sense. You have to use Rom Kitchen Porting. I managed to get the Desire X 1.14.401.1 working but the camera didn't. And it was real slow. I've been trying the same. I've had a bunch of working ones, they just sucked.
bandit97 said:
That thread your using wont work for Sense. You have to use Rom Kitchen Porting. I managed to get the Desire X 1.14.401.1 working but the camera didn't. And it was real slow. I've been trying the same. I've had a bunch of working ones, they just sucked.
Click to expand...
Click to collapse
I don't use that thread anymore to port. Link me to the ROM kitchen porting? Oh, and for camera:
libchromatix*.so
LibOlaEngine.so
LibOlaEngineNew.so
libhtccamera.so
liboemcamera.so
libcamera*.so
libmm*.so
In /system/etc:
media_profiles.xml
MameTozhio said:
I don't use that thread anymore to port. Link me to the ROM kitchen porting? Oh, and for camera:
libchromatix*.so
LibOlaEngine.so
LibOlaEngineNew.so
libhtccamera.so
liboemcamera.so
libcamera*.so
libmm*.so
In /system/etc:
media_profiles.xml
Click to expand...
Click to collapse
I don't know of a guide. Its pretty self explanatory in Rom Kitchen using its porting tool. Maybe I could give it a try and upload a base for you.
bandit97 said:
I don't know of a guide. Its pretty self explanatory in Rom Kitchen using its porting tool. Maybe I could give it a try and upload a base for you.
Click to expand...
Click to collapse
I'm going to try using the kitchen porter.. just downloaded the master from github, just waiting for 1.18.401.1 from DX to finish downloading.
Delete- figured it out!
I used the android kitchen to port it, I can't get it to boot now. Does anyone have any ideas? (Sorry for all the double posts ._.)
Sent from my Nexus 4 using xda app-developers app
Can you give a link to the base your using?
Sent from my HTC One V using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=36280811
The hTC Asia HK 2.24.701.1 version.
Sent from my Nexus 4 using xda app-developers app
Oh I ment what your trying to port.
Sent from my HTC One V using xda app-developers app
bandit97 said:
Oh I ment what your trying to port.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Oh.
http://forum.xda-developers.com/showpost.php?p=39658634&postcount=2
MameTozhio said:
Oh.
http://forum.xda-developers.com/showpost.php?p=39658634&postcount=2
Click to expand...
Click to collapse
Yeah I've been trying without luck as well. It probably has to do with different screen size, symlinks and or 4.03 as base. Ill mess around for a bit. I'm not sure if your just trying to get 4.04. I managed to port Desire S 4.0.4 but it was slow and the camera didn't work as I said.
bandit97 said:
Yeah I've been trying without luck as well. It probably has to do with different screen size, symlinks and or 4.03 as base. Ill mess around for a bit. I'm not sure if your just trying to get 4.04. I managed to port Desire S 4.0.4 but it was slow and the camera didn't work as I said.
Click to expand...
Click to collapse
I'm really only trying to get Sense 4.1 lite.
MameTozhio said:
I'm really only trying to get Sense 4.1 lite.
Click to expand...
Click to collapse
I got http://forum.xda-developers.com/showthread.php?t=2006392 working. For myself. Thats the one I had problems with though. You need to gut a lot of stuff out of it. And I don't know if he would allow public porting or not. If you want help we could do it together. I still have a booting rom from that. I know a bit more now so I think I could do it better.
bandit97 said:
I got http://forum.xda-developers.com/showthread.php?t=2006392 working. For myself. Thats the one I had problems with though. You need to gut a lot of stuff out of it. And I don't know if he would allow public porting or not. If you want help we could do it together. I still have a booting rom from that. I know a bit more now so I think I could do it better.
Click to expand...
Click to collapse
Yeah, I've also got my own method of porting that doesn't require a lot of gutting and produces a working ROM. It just doesn't work for Desire X sense ports..