Can someone post a link to an odexed 4.0.3 rom or post the cameragoogle.apk and cameragoogle.odex files? I don't seem to be able to locate them.
I'm attempting to cure a few camera bugs on stock verizon lte gnex (rooted) running 4.0.2 by replacing with the (hopefully) updated app. Any help is appreciated.
Sent from my Galaxy Nexus using Tapatalk
Edit: i guess not...ok so i pulled a copy of the 4.0.3 ota update for nexus s and have "patch" files (like CameraGoogle.apk.p). Any ideas how to turn these into actual apk and odex files?
Bump
Sent from my Galaxy Nexus using Tapatalk
Best you will get is from aosp. I have one somewhere if you still want it. It may not work due to platform signing.
No such thing, AOSP comes deodexed once compiled
EddyOS said:
No such thing, AOSP comes deodexed once compiled
Click to expand...
Click to collapse
Interesting comment.
100% incorrect.
userdebug builds = deodexed.
user builds = odexed.
I have both.
All the ones I've seen come deodexed so assumed it was the norm (was the same for my own AOSP build too)
EddyOS said:
All the ones I've seen come deodexed so assumed it was the norm (was the same for my own AOSP build too)
Click to expand...
Click to collapse
If you build it as user and not userdebug, it odexes.
OTAs are user builds.
Here is this but here is why I don't think it will work for you:
http://www.multiupload.com/L7Y8L90241
1. 4.0.3 is a higher API level.
2. Stock retail roms have been signed with different platform keys and that may cause issue for certain apps.
adrynalyne said:
Here is this but here is why I don't think it will work for you:
http://www.multiupload.com/L7Y8L90241
1. 4.0.3 is a higher API level.
2. Stock retail roms have been signed with different platform keys and that may cause issue for certain apps.
Click to expand...
Click to collapse
Thank you! it was worth a try, but you were right about it being signed incorrectly for use on stock rom.
Sent from my Galaxy Nexus using Tapatalk
adrynalyne said:
If you build it as user and not userdebug, it odexes.
OTAs are user builds.
Click to expand...
Click to collapse
I've only ever built to .img files so guessing that's why they're deodexed. Thanks for the info
Sent from my Galaxy Nexus using xda premium
EddyOS said:
I've only ever built to .img files so guessing that's why they're deodexed. Thanks for the info
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Disregard if you already knew this:
if you add otapackage to your make line, it will make a cwr flashable package.
Related
If there's already source for 4.0.3 why don't devs (whom i'll always not thanks enough for their work) makes an update? Only Google can make an incremental update and we need a full AOSP rom ?
? There are 4.0.3 roms
all the main roms i see in the dev section are 4.0.3
Sorry if i wasn't clear enough.
I mean: i'm on stock 4.0.1 and i don't want to wipe now. Isn't there a way to make an incremental update 4.0.3 instead of flashing an entire rom?
Also as a Nexus device, wasn't one of the benefits that Google would put out the updates very quickly?
They have 4.0.3 just sitting there, is there any reason why they're not putting it out?
The 4.0.3 roms are based off from the uncompiled 4.0.3 source that google releases to the public, which developers can compile and test their apps on.
As for your 4.0.1, is your device a yakju, or jakjuux? Check with the GN checker app on the market. If its jakjuux, it wont be updated until samsung says so, meanwhile if you are running jakju, you should be able to go to 4.0.2, which has been released as an OTA through google. Hope this helps.
Sent from my MZ604 using xda premium
F0l3ert said:
The 4.0.3 roms are based off from the uncompiled 4.0.3 source that google releases to the public, which developers can compile and test their apps on.
As for your 4.0.1, is your device a yakju, or jakjuux? Check with the GN checker app on the market. If its jakjuux, it wont be updated until samsung says so, meanwhile if you are running jakju, you should be able to go to 4.0.2, which has been released as an OTA through google. Hope this helps.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
I'm yakju bu you didn't get my point or neither i'm not explaining what it could be only my imagination. BUT
If the source code it's released why it can't be a 6/10/20 mb packet that can upgrade my system like a FOTA update can do ?
Because 4.0.3 has some bugs that needs to be fixed. The 4.0.3 OTA was released for Nexus S then pulled because of the bugs it was having.
You think if it was ready, they'd release it. Give it time, people are so ungrateful when 95% of the Android Community are still on Android 2.3.X and below.
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
zephiK said:
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
Click to expand...
Click to collapse
I've never complained and you didn't answered my question
zephiK said:
Because 4.0.3 has some bugs that needs to be fixed. The 4.0.3 OTA was released for Nexus S then pulled because of the bugs it was having.
You think if it was ready, they'd release it. Give it time, people are so ungrateful when 95% of the Android Community are still on Android 2.3.X and below.
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
Click to expand...
Click to collapse
Not really, there's a source released for the GNex from Google.
Sugar0, I will try compiling that stock source and tell you how it goes.
Arrio said:
Not really, there's a source released for the GNex from Google.
Sugar0, I will try compiling that stock source and tell you how it goes.
Click to expand...
Click to collapse
You don't need to! It's plenty of stock untouched AOSP roms and modified.
What i'm asking is:
is there an unofficial small update that will bring 4.0.3 to my GN that i can flash in recovery ? Not the full rom!
sugar0 said:
You don't need to! It's plenty of stock untouched AOSP roms and modified.
What i'm asking is:
is there an unofficial small update that will bring 4.0.3 to my GN that i can flash in recovery ? Not the full rom!
Click to expand...
Click to collapse
Oh then no.. not at the moment.
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Finally an on-topic answer! Why aren't those updates around ? Do i miss something ?
No, you didn't "miss" anything. It's just that most people who are going to take the time to setup a build environment are doing so to tinker with the source -- not just build a vanilla package. Either way, its not terribly difficult to setup and build -- especially with all the guides floating around XDA.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
That's not strictly true. The 'OTA' package you make when compiling the ROM from source is still a complete ROM as opposed to a small OTA update
It won't require a system wipe and will apply just like an OTA, which is what (I'm assuming) the OP wanted.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
It won't require a system wipe and will apply just like an OTA, which is what (I'm assuming) the OP wanted.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yep! like nigthly build of Cyanogenmod. It doesen't matter if its 6mb or 120mb. So aren't there those updates around ? I can't understand why they don't make such updates
I just updated my Chrome from the market place, and now when I try to start it I get the message:
Chrome is not supported for your version of Android.
Version 4.0 (Ice Cream Sandwich is the minimal supported version.
Click to expand...
Click to collapse
I'm running CyanogenMod9, Android version 4.0.3 so it should work....
Any ideas?
Same symptom and likely same cause as this.
It doesn't work for me either
Damnit can anyone upload the original, or maybe a build prop tweak so we can use this? I cannot go back to any other browser after using this. I'm sure more people feel the same way
Edit: 1000th post. Awesome haha
Sent from my CM9 Epic 4G
jeremysv said:
Same symptom and likely same cause as this.
Click to expand...
Click to collapse
i running cm9 with the version you quoted it works still. maybe you did something to break it.
checking the market. there is an update its 0.16.4215.215, in my market it is. not 0.16.4130.199 which the one i have. used titanium backup to get the old one.
xopher.hunter said:
Damnit can anyone upload the original, or maybe a build prop tweak so we can use this? I cannot go back to any other browser after using this. I'm sure more people feel the same way
Sent from my CM9 Epic 4G
Click to expand...
Click to collapse
Old version courtesy of I Brick Phones
I Brick Phones said:
for those who accidentally updated Chrome i've uploaded the previous version http://db.tt/4onutkFj
Click to expand...
Click to collapse
Sent from my CM9 Epic 4G
You can find the original apk Here
Reinstall it over the updated one and you'll be good to go. Im sure the CM9 devs will figure this out quickly or Google might release a patch if the want to be friendly to us geeks.
xopher.hunter said:
Damnit can anyone upload the original, or maybe a build prop tweak so we can use this? I cannot go back to any other browser after using this. I'm sure more people feel the same way
Sent from my CM9 Epic 4G
Click to expand...
Click to collapse
i made these changes to build.prop. got from stock galaxy nexus. dont know if all need to be changed but it is what i did and new version is working. just find these lines and change to these.
ro.build.id=IMM30B
ro.build.display.id=IMM30B
ro.build.version.release=4.0.4
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.build.description=SPH-D700-user 4.0.4 IMM30B release-keys
ro.build.fingerprint=sprint/SPH-D700/SPH-D700:4.0.4/IMM30B/EI22:user/release-keys
s89281b said:
i made these changes to build.prop. got from stock galaxy nexus. dont know if all need to be changed but it is what i did and new version is working. just find these lines and change to these.
ro.build.id=IMM30B
ro.build.display.id=IMM30B
ro.build.version.release=4.0.4
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.build.description=SPH-D700-user 4.0.4 IMM30B release-keys
ro.build.fingerprint=sprint/SPH-D700/SPH-D700:4.0.4/IMM30B/EI22:user/release-keys
Click to expand...
Click to collapse
Worked like a charm thank you very much. Took all but 2 minutes to do with an app I found on the market and ICS's awesome copy and paste/multitasking enhancements.
Sent from my CM9 Epic 4G
s89281b said:
i made these changes to build.prop. got from stock galaxy nexus. dont know if all need to be changed but it is what i did and new version is working. just find these lines and change to these.
ro.build.id=IMM30B
ro.build.display.id=IMM30B
ro.build.version.release=4.0.4
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.build.description=SPH-D700-user 4.0.4 IMM30B release-keys
ro.build.fingerprint=sprint/SPH-D700/SPH-D700:4.0.4/IMM30B/EI22:user/release-keys
Click to expand...
Click to collapse
It turns out the only change necessary to make Chrome work is ro.build.id. I wrote a detailed analysis of this issue in this blog entry. Be sure to read the warning!
wtogami said:
It turns out the only change necessary to make Chrome work is ro.build.id. I wrote a detailed analysis of this issue in this blog entry. Be sure to read the warning!
Click to expand...
Click to collapse
yeah i figured it was only one line but i found gingerbread mentioned several times and i wanted to get rid of all mention of it. and i was to lazy to test one line at a time. thanks for clearing that up.
Chrome app working again
All you have to do is backup your data and reflash cm9 and gapps and reinstall the downloaded apk , the market may give you some problems .
Update to alpha 5... they fixed chrome beta update issue... otherwise find older versions of apps on applanet.net
Sent from my SPH-D700 using xda premium
Which versions of a custom rom of ICS 4.0 support Google Chrome?
---------- Post added at 11:44 AM ---------- Previous post was at 10:58 AM ----------
The reason I ask is because there are so many ICS themed roms, what constitutes one that'll work vs won't?
KC_RSX said:
Which versions of a custom rom of ICS 4.0 support Google Chrome?
---------- Post added at 11:44 AM ---------- Previous post was at 10:58 AM ----------
The reason I ask is because there are so many ICS themed roms, what constitutes one that'll work vs won't?
Click to expand...
Click to collapse
you would need to be using CM9, Alpha 5 if you wanted the latest update to work out of the box. To get CM9 Alpa 5 go here: http://epiccm.blogspot.com/p/cm9-install-guide.html
So ANY ROM using CM 9 and Alpha 5 will work? Not familiar with what Alpha 5 is, what's that? (had someone root me n do my flashing of roms.. Still pretty new to it)
THX
Sent from my SPH-D710 using XDA App
KC_RSX said:
So ANY ROM using CM 9 and Alpha 5 will work? Not familiar with what Alpha 5 is, what's that? (had someone root me n do my flashing of roms.. Still pretty new to it)
THX
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Are you using the Epic 4G (non-touch)? If so there is only one cm9 alpha 5. It is it's own ROM.
Sent from my SPH-D700 using Tapatalk
I can't seem to find one.
Where is the non-deodexed JB ROM for Toro devices?
I tried searching, but nothing is coming up. Only links to Viciouses' deodexed one.
We have one.
http://www.teambamf.net/topic/4064-rom-jellybamf-12/page__pid__88932#entry88932
Cool. Thanks.
I am wondering if its a stock build though. The OP says he changed some stuff 'under the hood' without providing a changelog.
Actually, I am wondering. Is there a way to un-deodex a ROM?
As in convert a deodexed rom to odexed.
Well, since there's not been source or an OTA for toro or toroplus, there inherently has to be something changed. The only completely stock image available is for GSM devices.
MultiDev said:
Cool. Thanks.
I am wondering if its a stock build though. The OP says he changed some stuff 'under the hood' without providing a changelog.
Click to expand...
Click to collapse
Its as stock as you will get and being I posted it, I should know
Stuff under the hood was port/performance/stability related, not adding or removing features.
I didn't give a changelog because it was all under the hood porting stuff anyway, that nobody cares about (unless it doesn't work).
MultiDev said:
Actually, I am wondering. Is there a way to un-deodex a ROM?
As in convert a deodexed rom to odexed.
Click to expand...
Click to collapse
There are some tools floating around.
adrynalyne said:
Its as stock as you will get and being I posted it, I should know
Stuff under the hood was port/performance/stability related, not adding or removing features.
Click to expand...
Click to collapse
I'm sure its "as stock as you will get". But its not 100% stock, out of necessity of having to add radios etc.. You said it yourself, its a port.
If OP wants a completely stock image, he's gonna have to wait for OTA or support images.
MultiDev said:
Actually, I am wondering. Is there a way to un-deodex a ROM?
As in convert a deodexed rom to odexed.
Click to expand...
Click to collapse
Get paulobrians rom. It has a app to do just what you mentioned.
Sent from my Galaxy Nexus using xda premium
martonikaj said:
Well, since there's not been source or an OTA for toro or toroplus, there inherently has to be something changed. The only completely stock image available is for GSM devices.
Click to expand...
Click to collapse
martonikaj said:
I'm sure its "as stock as you will get". But its not 100% stock, out of necessity of having to add radios etc.. You said it yourself, its a port.
If OP wants a completely stock image, he's gonna have to wait for OTA or support images.
Click to expand...
Click to collapse
I never said it was 100% stock, so why are you bringing it up, and twice at that? It is common knowledge that JB is currently a developer preview on GSM only.
adrynalyne said:
I never said it was 100% stock, so why are you bringing it up, and twice at that?
Click to expand...
Click to collapse
I'm bringing it up because that's what OP is looking for. I'm not belittling what you (or any other developer) have done to create 4.1 ROMs, but they're not stock, which is what he's asking for.
Just making it clear.
It is common knowledge that JB is currently a developer preview on GSM only.
Click to expand...
Click to collapse
You'd think it is, but it isn't. People assume a lot of things. They think "Jellybean is released, and it must be available for my Nexus variant." When its actually not officially released, and the only "stock" image is for GSM.
No more support for this rom
Something new the Toro+ is coming up in the world
Sent from my Galaxy Nexus using xda premium
Man I really like the look of this ROM. I'm just now getting started with it and I look forward to reporting back after a bit of use. Thanks for bringing this to the Toroplus OP, nice work.
I'll be installing this soon while im in my manager's meeting lol.
Sent from my Galaxy Nexus using Tapatalk 2
justen7723 said:
I'll be installing this soon while im in my manager's meeting lol.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey Bro, you're going to be pissed if you haven't modded the updater-script to change the two instances of "maguro" to "toroplus" b/c you'll get an error in CWM if you haven't made this modification.
Below is a link to the ROM in which I made the necessary changes to the updater-script to make the ROM flashable in CWM. The changes to the updater-script are simply changing two instances of "maguro" to "toroplus", and I've flashed the same file that I'm linking to and I'm running this ROM right now.
CLICK HERE to Download ROM w/ corrected updater-script (deleted "maguro", replaced it with "toroplus")
MoSeriouS said:
Hey Bro, you're going to be pissed if you haven't modded the updater-script to change the two instances of "maguro" to "toroplus" b/c you'll get an error in CWM if you haven't made this modification. I'll post a link in a short bit of the ROM with the correct updater-script so that the ROM can be flashed in CWM. Other than that you should be good to go..
Click to expand...
Click to collapse
THANKS!!! I'm on TWRP 2.1.2 (don't think it matters) I'll just hold off for now.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks will try!
Sent from my Galaxy Nexus using Tapatalk 2
MoSeriouS said:
Hey Bro, you're going to be pissed if you haven't modded the updater-script to change the two instances of "maguro" to "toroplus" b/c you'll get an error in CWM if you haven't made this modification.
Below is a link to the ROM in which I made the necessary changes to the updater-script to make the ROM flashable in CWM. The changes to the updater-script are simply changing two instances of "maguro" to "toroplus", and I've flashed the same file that I'm linking to and I'm running this ROM right now.
CLICK HERE to Download ROM w/ corrected updater-script (deleted "maguro", replaced it with "toroplus")
Click to expand...
Click to collapse
UPDATE:
Ok, well the version of the ROM that I made with the modified updater-script (see post above) flashed fine, but I think that maybe the OP needs to make additional changes to make data/3G work on our device. I cannot get a data connection for the life of me, and I've never had this issue before with any other build for this device. When I go into Settings>More I cannot choose between LTE/CDMA and CDMA, and when I go into Settings>About Phone it says my Baseband Version is "Unknown" and pretty much everything else says Maguro (instead of "Toroplus?). Can someone with more knowledge than I inform me what files I can copy from Toroplus AOKP 40 and replace in this ROM so that I can get data working yo? Thanks.
sorry,i posted in the wrong section
this rom is for maguro
MoSeriouS said:
UPDATE:
Ok, well the version of the ROM that I made with the modified updater-script (see post above) flashed fine, but I think that maybe the OP needs to make additional changes to make data/3G work on our device. I cannot get a data connection for the life of me, and I've never had this issue before with any other build for this device. When I go into Settings>More I cannot choose between LTE/CDMA and CDMA, and when I go into Settings>About Phone it says my Baseband Version is "Unknown" and pretty much everything else says Maguro (instead of "Toroplus?). Can someone with more knowledge than I inform me what files I can copy from Toroplus AOKP 40 and replace in this ROM so that I can get data working yo? Thanks.
Click to expand...
Click to collapse
I don't think there are big differences between maguro and toro,you can download both files to compare them
MoSeriouS said:
Hey Bro, you're going to be pissed if you haven't modded the updater-script to change the two instances of "maguro" to "toroplus" b/c you'll get an error in CWM if you haven't made this modification.
Below is a link to the ROM in which I made the necessary changes to the updater-script to make the ROM flashable in CWM. The changes to the updater-script are simply changing two instances of "maguro" to "toroplus", and I've flashed the same file that I'm linking to and I'm running this ROM right now.
CLICK HERE to Download ROM w/ corrected updater-script (deleted "maguro", replaced it with "toroplus")
Click to expand...
Click to collapse
Avoid doing that. It is more likely that the ROM is not for you. Only do it if you are 100% sure that the Dev made an oversight in the script which is much less likely than having the wrong ROM for your phone. You keep doing this and you might get a brick soon.
Etoy's theme is the default theme?
The title / ROM name doesn't seem appropriate, if you ask me
Please consider switching to JB ics is over.
Verstuurd van mijn Galaxy Nexus met Tapatalk
Formhault said:
The title / ROM name doesn't seem appropriate, if you ask me
Click to expand...
Click to collapse
what do you mean?do you have another suggestion?
costygsm2 said:
what do you mean?
Click to expand...
Click to collapse
It's not clean - it's got TouchWiz things in it .
Oh and I agree with schukje. ICS is pretty much dead. We'll only get one more ICS AOKP build, then we're all going to the jellybeans stores .
Anyway, nice ROM. Let's hope you stick around until JB is out and bring us some of that goodness as well.
Formhault said:
The title / ROM name doesn't seem appropriate, if you ask me
Click to expand...
Click to collapse
I agree its not officially tied to AOKP at all
schukje said:
Please consider switching to JB ics is over.
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
and thats not true, till AOSP releases tjhe code and everyone starts DEVn with JB , ICS is still the dominate OS for this device
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
so the consensus is this ROM is pretty good? Im curious
Yep very true... That's what I am waiting for, the ROM's to switch to JellyBean things to be officially released. JB to me is not out yet and how people are putting these ROM's out and claiming to be JB without AOSP having released the source is to scary for me to try on my phone so I'm avoiding anything stating it's JB. For now it's ICS for me though I am running franco's 200 ics kernel which is running pretty good.
nicknowsky said:
I agree its not officially tied to AOKP at all
and thats not true, till AOSP releases tjhe code and everyone starts DEVn with JB , ICS is still the dominate OS for this device
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
so the consensus is this ROM is pretty good? Im curious
Click to expand...
Click to collapse
Hi is this ROM for maguro? The GSM model?
Thanks
dan96815 said:
Hi is this ROM for maguro? The GSM model?
Thanks
Click to expand...
Click to collapse
Yes, it is
Hello all.
I saw that the binaries have been updated for the Galaxy Nexus on this page:
https://developers.google.com/android/nexus/drivers
Does anyone know how to actually pull and install the binaries? I tried running the script but I get an error saying that it couldn't display the license.
Thanks.
EDIT: I thought it was as simple as extracting and replacing an object file. According to this, it looks like you need to source to extract and then build.
https://groups.google.com/forum/m/#!msg/android-building/2fXGtHA98CI/wxGnntR7Za8J
I use those binaries just fine with the script.
Sent from my Galaxy Nexus using xda premium
Are you extracting within the source tree?
Noob question... will these binaries improve the existing roms that are around? I was looking to flash a new rom on my vzw nexus, but is it worth waiting for developers to integrate these binaries?
Sent from my cm_tenderloin using Tapatalk 2
andytseng said:
Noob question... will these binaries improve the existing roms that are around? I was looking to flash a new rom on my vzw nexus, but is it worth waiting for developers to integrate these binaries?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
In theory, they should.
The JRO03C aosp binaries for maguro and toro have been released for a few days now, and those scripts are to be run in a linux terminal. They work fine. They are also needed to build a rom for those devices from (aosp) source code (we dont have the source for those components, thats why we use the binaries provided by Google).
skinien said:
Are you extracting within the source tree?
Click to expand...
Click to collapse
This as well, thanks.
Sent from my i9250
bk201doesntexist said:
The JRO03C aosp binaries for maguro and toro have been released for a few days now, and those scripts are to be run in a linux terminal. They work fine. They are also needed to build a rom for those devices from (aosp) source code.
This as well, thanks.
Sent from my i9250
Click to expand...
Click to collapse
These are JRO03H and were released yesterday.
skinien said:
These are JRO03H and were released yesterday.
Click to expand...
Click to collapse
I've been busy as hell at work. Thanks for the heads up. make clobber. no hard feelings huh mate?
Edit: perhaps you could place JRO03H in the thread title.
Sent from my i9250
Can you install them to any 0H rom? If so, how?