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?
Related
Source code .zip is available for download on opensource.samsung.com. Enjoy
Edit: Apparently I screwed up when I extracted the contents of the zip Sammy posted. There is way more stuff in the source .zip than just kernel sauce. There is platform sauce too, which should allow developers to modify and compile other parts of the firmware besides the kernel. OK devs, have at it!
Do you believe in magic?
Sent from my SPH-D700
Website:
https://opensource.samsung.com/
File Mirror -
SPH-D710_Opensource.zip - DROPBOX
.
.
.
What?! Is this what our devs will need and what we still don't have for the Epic?
Sent from my SPH-D700 using xda premium
JohnCorleone said:
What?! Is this what our devs will need and what we still don't have for the Epic?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Ikno right? Its sooo sad but yay source on the new touch (getting this weekend)
Sent from my Epic 4G
here's a mirror of my server
ftp://www.gooinside.me/Samsung Epic 4G touch/Source Code/SPH-D710_Opensource.zip
Are we there yet? Are we there yet?
Are we there yet? Are we there yet? Are we there yet? Are we there yet?
Are we there yet? Are we there yet? Are we there yet? Are we there yet?
Are we there yet? Are we there yet? Are we there yet? Are we there yet?
Are we there yet? Are we there yet? Are we there yet? Are we there yet?
Are we there yet? Are we there yet? Are we there yet? Are we there yet?
Are we there yet? Are we there yet? Are we there yet? Are we there yet?
Gimmeh sum rute!!!
Yeah, come on guys, I've had my phone for like 4 whole hours now, where's the root at?!?
datajosh said:
Yeah, come on guys, I've had my phone for like 4 whole hours now, where's the root at?!?
Click to expand...
Click to collapse
working on it right noW!!! as soon as i am done compiling kernel from source.
zedomax said:
working on it right noW!!! as soon as i am done compiling kernel from source.
Click to expand...
Click to collapse
gogogogogogogo!
zedomax said:
working on it right noW!!! as soon as i am done compiling kernel from source.
Click to expand...
Click to collapse
Awesome! When I saw the kernel source release last night I figured it wouldn't take long.
zedomax said:
working on it right noW!!! as soon as i am done compiling kernel from source.
Click to expand...
Click to collapse
Awesome
zedomax said:
working on it right noW!!! as soon as i am done compiling kernel from source.
Click to expand...
Click to collapse
Awesome man!
Sent from my SPH-D710 using XDA App
this code is junk
I've been trying all day long to get a kernel working, they compiled fine but no-go, I end up on boot freeze or bootloop, I've tried messing with the config file all day long, does anyone have any ideas why?
I think this open source code is junk, at least for now. There wasn't an official announcement from Samsung so this could be code from back in the days, the instructions also ask you to use an older arm compiler from 2009...
Damn it, my phone is bricked now.
I just found out how worthless my apps are without root. This touch whiz has forced me to lpp.
Sent from my SPH-D710 using XDA App
zedomax said:
I've been trying all day long to get a kernel working, they compiled fine but no-go, I end up on boot freeze or bootloop, I've tried messing with the config file all day long, does anyone have any ideas why?
I think this open source code is junk, at least for now. There wasn't an official announcement from Samsung so this could be code from back in the days, the instructions also ask you to use an older arm compiler from 2009...
Damn it, my phone is bricked now.
Click to expand...
Click to collapse
I've had the same problem since yesterday - the size of the compiled kernel doesn't make sense. I picked up a second phone (I have 2 now) and am wondering if there's a way to extract the stock kernel from it
r.kim said:
I've had the same problem since yesterday - the size of the compiled kernel doesn't make sense. I picked up a second phone (I have 2 now) and am wondering if there's a way to extract the stock kernel from it
Click to expand...
Click to collapse
With root you can...wait maybe you can adb pull the zimage!
Korey_Nicholson said:
With root you can...wait maybe you can adb pull the zimage!
Click to expand...
Click to collapse
Probably, and I rooted my phone yesterday by using a galaxy s2 kernel. All I needed to do after that was to reflash a stock kernel, however, I blew it away to root the phone..so catch 22
I was planning on compiling a kernel from source, but like zedomax saw, the compiled binaries didn't work and put the phone into a bootloop. I guess I should have warned him, though at the time, I thought I was doing something wrong (first time doing anything so involved with an android device).
Now, I've an stock Epic 4G Touch sitting next to my frankenrooted device from the other day...if I can get the stock kernel off of one onto the other...viola, proper root access.
I'm in the exact same boat you two are in: bootloop after trying out my self-compiled kernel from Samsung's source code. If anyone gets a hold of a working kernel, care to post it somewhere so I can at least have a working phone again?
NateTheGreat said:
I'm in the exact same boat you two are in: bootloop after trying out my self-compiled kernel from Samsung's source code. If anyone gets a hold of a working kernel, care to post it somewhere so I can at least have a working phone again?
Click to expand...
Click to collapse
lol, samsung just blew us by this time, those open source files were like not open source somehow.
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
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.
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
klobkelosh said:
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
Click to expand...
Click to collapse
I'm on a Windows machine and came across those on Google's site. I used a text editor to open the shell script and then deleted all lines above the binary data, then saved, then renamed the file with a .tar.gz extension. I could then open that and see all of the files. Try that.
Turns out I had a space on the file path! Thanks mmuzzy for pointing that out...
If anyone wants the TORO binaries as a flashable zip, here: http://d-h.st/fpN
Tested on cm 10.1 latest nightly. All ok. Even fixes a gps issue with cm.
Tiny did a few more tweaks. His version fixes the gps wakelock issue:
New link: URL=http://d-h.st/Lgo]422-JDQ39-toro-proprietaries.zip - 4.45 MB[/URL]
Tiny Pulled the file that caused dev-host to complain about a virus (fRom) that I originally included. Tiny can't find anything about this file so it's a false positive but to be sure, he uploaded a new zip and removed the old one
Thanks tiny!
Link fix
http://d-h.st/Lgo
Sent from my Galaxy Nexus using xda app-developers app
Maguro JB 4.2.2 JDQ39 Binaries
Hi guys!
Here's the Maguro JB 4.2.2 JDQ39 Binaries :good:
http://forum.xda-developers.com/showpost.php?p=38650434&postcount=2641
klobkelosh said:
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
Click to expand...
Click to collapse
I didn't know you were over here now :good:
CondemnedSoul said:
I didn't know you were over here now :good:
Click to expand...
Click to collapse
Hey hey cs! How you doing man?
Yeah, I've been over here since vzw gnex release day. You still deving?
klobkelosh said:
Hey hey cs! How you doing man?
Yeah, I've been over here since vzw gnex release day. You still deving?
Click to expand...
Click to collapse
Sweet.... I'm doing pretty good. Finally getting things in order with life. Yes, still deving.... just received a gnex yesterday. Checking things out over here and waiting on a sim card. Should have it Monday I think.
CondemnedSoul said:
Sweet.... I'm doing pretty good. Finally getting things in order with life. Yes, still deving.... just received a gnex yesterday. Checking things out over here and waiting on a sim card. Should have it Monday I think.
Click to expand...
Click to collapse
cool! Hoping you build for Toro!
I haven't pulled off my own ROM yet, but I've done a bunch of porting, theming, and tinkering, mostly for myself. See ya round!
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
kamil.trebunia said:
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
Click to expand...
Click to collapse
The binaries in this thread are for toro only. I wouldn't advise flashing them on maguro. There is a link to proper Gsm binaries a few posts back that can be flashed.
Sent from my Galaxy Nexus using Tapatalk 2
Nice.
Sent from my Paranoid Nexus 3.0
klobkelosh said:
cool! Hoping you build for Toro!
I haven't pulled off my own ROM yet, but I've done a bunch of porting, theming, and tinkering, mostly for myself. See ya round!
Click to expand...
Click to collapse
You should post them ... Don't be greedy! .... I will be soon
Sent from my ADR6400L using Tapatalk 2
kamil.trebunia said:
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
Click to expand...
Click to collapse
Any factory image for the same android build will have the same binaries (and probably others that can't be distributed as open source) as the ones posted for aosp.
I pulled the GPS, Wi-Fi, and Bluetooth drivers from mwalt2's deodex of last night's ota leak: VZW_JDQ39_GPS+WIFI_DRIVERS.zip - 1.22 MB. Not sure if they are any different than the AOSP binaries, but here they are if you want them. Phone is deep sleeping like a baby, GPS locks right on, and Wi-Fi seems good.
klobkelosh said:
I pulled the GPS, Wi-Fi, and Bluetooth drivers from mwalt2's deodex of last night's ota leak: VZW_JDQ39_GPS+WIFI_DRIVERS.zip - 1.22 MB. Not sure if they are any different than the AOSP binaries, but here they are if you want them. Phone is deep sleeping like a baby, GPS locks right on, and Wi-Fi seems good.
Click to expand...
Click to collapse
Flashing these over Mmuzzy's 3/2 Vanilla build is ok?
n99hockey said:
Flashing these over Mmuzzy's 3/2 Vanilla build is ok?
Click to expand...
Click to collapse
Yes, should work fine.
Can these be flashed on a 4.1.2 ROM and get improvement?
Galaxy Nexus+Baked+Lean+TWRP=BOOM SHAKALAKA
TMFGO45 said:
Can these be flashed on a 4.1.2 ROM and get improvement?
Galaxy Nexus+Baked+Lean+TWRP=BOOM SHAKALAKA
Click to expand...
Click to collapse
Let us know after you flash it!
This is just an extremely clean build based off of the Latest AOSP release. It's compiled with linaro. The only real differences from stock AOSP are that I added the embedded superuser. I figure that Android is such a good base to build other things off so of why not leave it be.
http://www.mediafire.com/?d5zo8s1g6ltm2bd
ill give it a run i been looking for a clean rooted stock with the superuser in the settings lol oddly enough no joke thankx
Do you think, I can install it on Maguro?
freezer2000 said:
Do you think, I can install it on Maguro?
Click to expand...
Click to collapse
No. Unless you don't mind not having data or voice/sms. Recovery normally fails on roms cross device on purpose.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
No. Unless you don't mind not having data or voice/sms. Recovery normally fails on roms cross device on purpose.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
OP can you in that case do a maguro build too... I can be the tester
This is the simplest ROM op I've ever seen xD
nitsua98 said:
This is the simplest ROM op I've ever seen xD
Click to expand...
Click to collapse
BAHAHAHA, yeah I usually flash CM or AOKP for a week and then say screw it I just want to go back to AOSP. Once I get back to my computer this week it'll probably be rebased on Master. It's not a complicated thing. Simply AOSP builds with LatinIMEGoogle being the only difference. ThinkFree is in there too I believe.
freezer2000 said:
OP can you in that case do a maguro build too... I can be the tester
Click to expand...
Click to collapse
I don't have a GSM so I'm a little scurred about building for something that I can't test out myself. Sometime this week I'll have a ROM that's built off of the Master repo and I'll get the Maguro Proprietaries and build that if you'd like.
I may just build once and provide a flashable to add the CDMA or GSM Proprietary files depending on what the person needs.
doobie711 said:
BAHAHAHA, yeah I usually flash CM or AOKP for a week and then say screw it I just want to go back to AOSP. Once I get back to my computer this week it'll probably be rebased on Master. It's not a complicated thing. Simply AOSP builds with LatinIMEGoogle being the only difference. ThinkFree is in there too I believe.
Click to expand...
Click to collapse
So this is like baldwinguy's shiny rom but built with linaro?