[ROM][JB][4.1.2] Black Bean AOKP v3.2.4 [26.10.2012] DISCONTINUED - Samsung Galaxy Nexus

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

Related

Updated Chrome and it no longer works with CM9 ICS?

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

[For Devs] android 4.1 jellybean

NOTE: DO NOT FLASH THIS TO YOUR PHONE> IT WILL HARD BRICK!
this is for any dev that wants to try and port android jellybean to the s3 Tmobile version. they already ported it to the internationl version so i think that might make it a little easier. here is the OP in the international section: http://forum.xda-developers.com/showthread.php?t=1737449
fcortes626 said:
NOTE: DO NOT FLASH THIS TO YOUR PHONE> IT WILL HARD BRICK!
this is for any dev that wants to try and port android jellybean to the s3 Tmobile version. they already ported it to the internationl version so i think that might make it a little easier. here is the OP in the international section: http://forum.xda-developers.com/showthread.php?t=1737449
Click to expand...
Click to collapse
Hmmm...
Wonder if we could take that ROM, change the updater-script to match our mounting points....then we just need a kernel....
Which we have one kernel already made. Not sure if it would work though.
If anyone would help set up a build environment that would work for our kernels and roms then I will gladly help and start learning.
Sent from my SGH-T999 using Tapatalk 2
brfield said:
Which we have one kernel already made. Not sure if it would work though.
If anyone would help set up a build environment that would work for our kernels and roms then I will gladly help and start learning.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I think we'd need a stock CM9 based kernel though. If I understand correctly.
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
Well, it shouldn't take too long. It may be possible to build a CM9 Kernel for our phones using parts of the stock kernel that we have access to.
Once the JB source is released, an S3 port might actually be viable. Otherwise it's essentially just flashing a gnex image and praying something/anything works.
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
a CM9 kernel shouldn't be needed, just a modded kernel for our specific phone from what i believe.
We know this, but it's more of an experiment. Also, it helps work out anything we may need to do early on with the modules and drivers
Sent from my SGH-T999 using Tapatalk 2
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
uoY_redruM said:
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
Click to expand...
Click to collapse
It could, in theory. But we would need to work on the modules for anything to work. Could you post our mount points?
why does it have to be a cm9 kernel?
to be completely honest, as soon as we get a cm9 alpha, we will see some worth while stuff! but until then. TouchWiz it iz. We will have team kang's AOKP in no time im sure. i cant wait to see wuts to come. especially since this phone is at all the major carriers and they are all basically exactly the same! should be epic.
Radsolutionz said:
to be completely honest, as soon as we get a cm9 alpha, we will see some worth while stuff! but until then. TouchWiz it iz. We will have team kang's AOKP in no time im sure. i cant wait to see wuts to come. especially since this phone is at all the major carriers and they are all basically exactly the same! should be epic.
Click to expand...
Click to collapse
yea i think once one of the other major carriers (or ares) get cm9 then we will see some awesome stuff for everyones phone!
I think that the only thing that makes them different is the radios in the phone
uoY_redruM said:
Hmmm...
Wonder if we could take that ROM, change the updater-script to match our mounting points....then we just need a kernel....
Click to expand...
Click to collapse
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
uoY_redruM said:
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
Click to expand...
Click to collapse
If aosp was that easy we would all be doing it but no... way more complex than that....
im on my phone. expect terrible typos.
howtomen said:
If aosp was that easy we would all be doing it but no... way more complex than that....
im on my phone. expect terrible typos.
Click to expand...
Click to collapse
Wishful thinking I suppose
in another note i found a mini tutorial on how to port it to other devices if anyone wants to try it here is the guide. it is an SDK port. note: i did not write this guide i am just posting a link to the authors op. you can thank him and/or donate to him. here isorum.xda-developers.com/showpost.php?p=28020178&postcount=36 the link:
fcortes626 said:
in another note i found a mini tutorial on how to port it to other devices if anyone wants to try it here is the guide. it is an SDK port. note: i did not write this guide i am just posting a link to the authors op. you can thank him and/or donate to him. here isorum.xda-developers.com/showpost.php?p=28020178&postcount=36 the link:
Click to expand...
Click to collapse
Link is broken, im not meaning to be a lazy pest.
sswb27 said:
Link is broken, im not meaning to be a lazy pest.
Click to expand...
Click to collapse
sorry about that :silly:
here you go: http://forum.xda-developers.com/showpost.php?p=28020178&postcount=36
fcortes626 said:
sorry about that :silly:
here you go: http://forum.xda-developers.com/showpost.php?p=28020178&postcount=36
Click to expand...
Click to collapse
i also have a deodexed system dump of jb if you want it let me know.
Source is out
Sent from my Galaxy Nexus using Tapatalk 2

[HOWTO] Port N7100 ROMs to I317 and N7105

I spent the entire day yesterday trying to make Android Revolution HD work on my I317. At the end of the day, success ! and here is how:
Please do not experiment with this stuff if you're not familiar with partitions and the way things work. You do run the risk of bricking your device permanently if you don't know what you're doing. I'll write this so that developers can start porting their ROMs to the LTE variants.
The two devices are identical except for the modem (and rild files) and the GPS initialization at bootup.
1. You'll need to rewrite the updater-script in most CWM flashable ROMs to make sure.. again, MAKE SURE that you do not flash anything else except /system /data and the boot partition. Overwriting your modem partition with a modem from the N7100 phone or the bootloader partitions will blow up your phone. You've been warned ! The partition labels and numbers are identical so you won't have to change that.
2. Make sure you bundle a kernel (boot.img) from one of I317/N7105 (depending on which device you own). Obviously we're talking about TW kernels here so for example stock JB kernels or Perseus will do just fine. Do not flash boot.img kernels from the N7100 section.
3. You'll need to add and remove a bunch of userland library files from your device. I won't attach these files here but you can grab them from any I317/N7105 ROM:
Files to ADD/REPLACE (Yes, every single one counts as they're dynamically linked). The stuff in /system/bin are started by the initramfs in the kernel so add them all in as well:
Code:
./system
./system/bin
./system/bin/qcks
./system/bin/sec-ril
./system/bin/qmuxd
./system/bin/efsks
./system/bin/diag_uart_log
./system/bin/netmgrd
./system/bin/gsiff_daemon
./system/bin/ks
./system/bin/rild
./system/bin/qmiproxy
./system/bin/secstarter
./system/etc
./system/etc/gps.conf
./system/lib
./system/lib/hw
./system/lib/hw/audio.primary.smdk4x12.so
./system/lib/hw/gps.default.so
./system/lib/hw/audio_policy.smdk4x12.so
./system/lib/libril-qc-qmi-1.so
./system/lib/libnetmgr.so
./system/lib/libaudio-ril.so
./system/lib/libloc_api_v02.so
./system/lib/libril-qcril-hook-oem.so
./system/lib/libqdp.so
./system/lib/libdsutils.so
./system/lib/libqmiservices.so
./system/lib/libqmi_client_qmux.so
./system/lib/libloc_adapter.so
./system/lib/libqmi_common_so.so
./system/lib/libqdi.so
./system/lib/libqmi.so
./system/lib/libcsd-client.so
./system/lib/libloc_eng.so
./system/lib/libqmi_encdec.so
./system/lib/libqcci_legacy.so
./system/lib/libqmi_cci.so
./system/lib/libssaudio-client.so
./system/lib/libidl.so
./system/lib/libril.so
./system/lib/libqmi_csi.so
./system/lib/libdiag.so
./system/lib/libdsi_netctrl.so
./system/lib/libgps.utils.so
./system/lib/libgps.so
To remove !!! Moi importante !
Code:
./system/lib/hw/gps.exynos4.so
If you don't remove that GPS exynos4 file, HAL will load it and never the gps.default.so file so your gps won't work. Took me three friggin hours to figure out.
4. Lastly, you'll need to change build.prop so that it loads our RILD files instead of the N7100's:
Code:
replace
rild.libpath=/system/lib/libsec-ril.so
with
rild.libpath=/system/lib/libril-qc-qmi-1.so
5. ???
6. Profit.
When I get sometime, I'll try to port CM10 from the N7100 tree. Done.
im going to try this I hope it works thanks
drakeymcmb said:
im going to try this I hope it works thanks
Click to expand...
Click to collapse
well, attached is what I'm seeing on my phone now
does signal and lte work ?
---------- Post added at 03:49 PM ---------- Previous post was at 03:46 PM ----------
can u please upload the ported android revolution thanks
this is good news to alot of 7105 users
thank u. from the bottom of my heart heh!
drakeymcmb said:
does signal and lte work ?
---------- Post added at 03:49 PM ---------- Previous post was at 03:46 PM ----------
can u please upload the ported android revolution thanks
Click to expand...
Click to collapse
LTE works. Si senior. Shows as proper "4G" on top.
I'm not going to upload it because I'm too lazy to ask for his permission. silly i know
il ask for u and then u can upload it but does calling work like can u call your voicemail ? and thanks so much me gusta lol
Thanks for this...are you looking at porting over imilka's CM10 build?
my day just got better
dammit.. phone call goes through but I can't hear anything!!
Lemme see if I can fix that.
madmack said:
dammit.. phone call goes through but I can't hear anything!!
Lemme see if I can fix that.
Click to expand...
Click to collapse
This is truly a breakthrough if you can get everything to work!!! Am really excited.
MonsterBandit said:
Thanks for this...are you looking at porting over imilka's CM10 build?
my day just got better
Click to expand...
Click to collapse
I don't think that will be possible until we have an cm10 kernel built for our device first, can't switch in a TW kernel for their cm10 kernel without possibly bricking our phones
And to the OP of this thread:
Great work man, I know they were having a little trouble getting the roms to port on our IRC channel, hopefully this opens the flood gates for more rom possibilities :good:
MonsterBandit said:
Thanks for this...are you looking at porting over imilka's CM10 build?
my day just got better
Click to expand...
Click to collapse
mjwhirly said:
I don't think that will be possible until we have an cm10 kernel built for our device first, can't switch in a TW kernel for their cm10 kernel without possibly bricking our phones
And to the OP of this thread:
Great work man, I know they were having a little trouble getting the roms to port on our IRC channel, hopefully this opens the flood gates for more rom possibilities :good:
Click to expand...
Click to collapse
I'm going to port the standard CM10 that is available at github.com/cyanogenmod Once this is completed, then we can incorporate that to all AOSP based roms.
The kernels are actually pretty close to each other. (have a look at the defconf for details). What's different is the initramfs and the userland binaries/libraries. I'll have a look at it but I need to get this audio going on TW roms first.
mjwhirly said:
I don't think that will be possible until we have an cm10 kernel built for our device first, can't switch in a TW kernel for their cm10 kernel without possibly bricking our phones
And to the OP of this thread:
Great work man, I know they were having a little trouble getting the roms to port on our IRC channel, hopefully this opens the flood gates for more rom possibilities :good:
Click to expand...
Click to collapse
Thats, what I thought, but he said he was gunna try CM10...I've been trying to learn more about Kernels all morning, and I understand we have a Qualcomm modem, but idk what would be needed to build a kernel for say CM...any thoughts?
Sorry for the OT OP.
---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------
madmack said:
I'm going to port the standard CM10 that is available at github.com/cyanogenmod Once this is completed, then we can incorporate that to all AOSP based roms.
The kernels are actually pretty close to each others. (have a look at the defconf for details). What's different is the initramfs and the userland binaries/libraries. I'll have a look at it but I need to get this audio going on TW roms first.
Click to expand...
Click to collapse
awesome...I'm very new to the development world, and I'm learning as much as I can to be able to help and maybe dev my own stuff
Audio phone calls work
PHONE CALLS..
FIXED
HOW U LIKE DEM APPLES amigos
lemme update the OP.
edit: done. OP's list of files to add/replace is updated to reflect this change. basically a bunch of libaudio* files and their dependencies.
madmack said:
PHONE CALLS..
FIXED
HOW U LIKE DEM APPLES amigos
lemme update the OP.
edit: done. OP's list of files to add/replace is updated to reflect this change. basically a bunch of libaudio* files and their dependencies.
Click to expand...
Click to collapse
Damn man you work too quickly, at this rate we should have CM10 in like 2 hours
mjwhirly said:
Damn man you work too quickly, at this rate we should have CM10 in like 2 hours
Click to expand...
Click to collapse
lol. it'll be a while til we get CM10 running. I've just quickly looked at the differences and have an idea where to go from here but that's about it.
It all depends on how much free time I get here at work.
Madmack, you sir are a freaking genius. Now I'm glad I didn't get the international version cause I have lte in my area. Can't wait for more ported roms and aosp goodness. Thank you sir!
Sent from my SAMSUNG-SGH-I317 using xda premium
./system/bin/secstarter
I can't find it in N7105 LJ4 Rom
deadman12 said:
./system/bin/secstarter
I can't find it in N7105 LJ4 Rom
Click to expand...
Click to collapse
I actually pulled it from a N7105 LJ4 Rom. Download the stock LJ4 ROM, it should include it. If not, well, then don't add it and see what happens.
madmack said:
lol. it'll be a while til we get CM10 running. I've just quickly looked at the differences and have an idea where to go from here but that's about it.
It all depends on how much free time I get here at work.
Click to expand...
Click to collapse
I'll gladly set up a Google Code Page for you...I'll do the same thing I did for randomblame and his original Jellytime Project...link to that project page is in my sig.

4.2.2 Nexus Binaries Released

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!

Android 4.3 on Korean Note 2?

Hi guys!
First of all I am sorry for posting in this forum but I believe Korean Note 2 is similar in many aspect to N7105 and also there are devs who can read and maybe come up with something.
I have a question for you. Has anyone tried an Android 4.3 custom ROM on e250s (Korean Note 2) ? I am currently on 4.1.2, a combination of Milan 3.0 and Milan 4.0 (I think this ROMs are also for N7105 because in About device section my phone appears to be a N7105 after flashing), with some stock kernel and cwm. I have tried a few 4.3 ROMs for N7105 (CM 10.2, Beanstalk, Illusion) but all get stuck at the boot logo (Samsung Galaxy Note 2). I even tried different kernels, compatible with 4.3 (SJKernel and NeKo) but again, with no luck.
Do you have a solution, link, idea?
Thanks in advance guys!
Any links?
Sent from the TermiNOTEr 2!
borijess said:
Any links?
Sent from the TermiNOTEr 2!
Click to expand...
Click to collapse
Here is a screenshot of my system.
razvan11malancus said:
Here is a screenshot of my system.
Click to expand...
Click to collapse
Ok that's 4.1.2 don't get it. Thought you had 4.3 touch wiz.
Sent from the TermiNOTEr 2!
borijess said:
Ok that's 4.1.2 don't get it. Thought you had 4.3 touch wiz.
Sent from the TermiNOTEr 2!
Click to expand...
Click to collapse
Yes. My actual ROM is 4.1.2. I have tried Jedi X19 (4.1.2) and also BeanStalk, Illusion, CM 10.2 (4.3), with the same result. Stuck at boot screen logo.
Ni hao
razvan11malancus said:
Hi guys!
First of all I am sorry for posting in this forum but I believe Korean Note 2 is similar in many aspect to N7105 and also there are devs who can read and maybe come up with something.
I have a question for you. Has anyone tried an Android 4.3 custom ROM on e250s (Korean Note 2) ? I am currently on 4.1.2, a combination of Milan 3.0 and Milan 4.0 (I think this ROMs are also for N7105 because in About device section my phone appears to be a N7105 after flashing), with some stock kernel and cwm. I have tried a few 4.3 ROMs for N7105 (CM 10.2, Beanstalk, Illusion) but all get stuck at the boot logo (Samsung Galaxy Note 2). I even tried different kernels, compatible with 4.3 (SJKernel and NeKo) but again, with no luck.
Do you have a solution, link, idea?
Thanks in advance guys!
Click to expand...
Click to collapse
bbs.gfan.com/forum.php?mod=viewthread&tid=5919447&extra=page%3D2
cbeta1111 said:
bbs.gfan.com/forum.php?mod=viewthread&tid=5919447&extra=page%3D2
Click to expand...
Click to collapse
Thanks.
I have finally installed 4.3 ROM after flashing a file that converts the kernel to e250s.
Vibration issue
Hi guys!
Is anyone else having issues with vibrations when using a N7105 ROM (with Android 4.2.2 or 4.3)? I mean the phone does not vibrate at all.
Do you know a fix or something?
Thanks!
razvan11malancus said:
Hi guys!
Is anyone else having issues with vibrations when using a N7105 ROM (with Android 4.2.2 or 4.3)? I mean the phone does not vibrate at all.
Do you know a fix or something?
Thanks!
Click to expand...
Click to collapse
Use AOSP e250s Thor's kernel (update-0.27-aosp-KO-LTE-e250s-lsi-n7100.zip)
download:
mediafire.com/folder/41s5eea1er9dt/0.27
original thread:
forum.tegraowners.com/viewtopic.php?f=41&t=872
cbeta1111 said:
bbs.gfan.com/forum.php?mod=viewthread&tid=5919447&extra=page%3D2
Click to expand...
Click to collapse
what is that?
Cannot read chinese
can you give us link of downalod?
I own note 2 e250 s
---------- Post added at 02:55 AM ---------- Previous post was at 02:53 AM ----------
razvan11malancus said:
Thanks.
I have finally installed 4.3 ROM after flashing a file that converts the kernel to e250s.
Click to expand...
Click to collapse
which 4.3 ROM did you installed and how?
can you tell us bit more about converting kernels
Rajaasim1980 said:
what is that?
Cannot read chinese
can you give us link of downalod?
I own note 2 e250 s
---------- Post added at 02:55 AM ---------- Previous post was at 02:53 AM ----------
which 4.3 ROM did you installed and how?
can you tell us bit more about converting kernels
Click to expand...
Click to collapse
Hi. This is the link to the boot converter.
http://forum.xda-developers.com/showpost.php?p=36885456
All you have to do is flash this zip file from cwm after you first flash the ROM.
I have tried Illusion and PAC-MAN ROMs (N7105, Android 4.3) and also MIUI v5 for N7105 (Android 4.2.2) and all work fine.
There may be some ROMs (PAC-MAN) that give you "error 7" when flashing. You have to change the first line from META-INF/com/google/android/update script.
How I do that. I prefer to change the ROMs extension from zip to apk, then unzip it using APK Tool and go to the file, change extention to .txt and delete the first line (the one that starts with assert), thus the first line becoming the one with "show progress" or "mount". After that I zip it again with APK Tool and sign the ROM with ApkSign. I do not know why, I cannot sign it with APK Tool. After that, the flashing process should go fine. You have to install the right GApps for the ROM you are being flashing and then the boot converter from the link.
The only issue I have found was the absence of vibrations, but I managed to get it back by flashing Thor Kernel for Note 2, like cbeta1111 and eggymustdie told me. So huge thanks to them.
Good luck! Hope you will manage to install the desired ROM. In my opinion, PAC-MAN ROM is the best so far, with many, many options from CM, AOKP and Paranoid Android ROMs.
cbeta1111 said:
Use AOSP e250s Thor's kernel (update-0.27-aosp-KO-LTE-e250s-lsi-n7100.zip)
download:
mediafire.com/folder/41s5eea1er9dt/0.27
original thread:
forum.tegraowners.com/viewtopic.php?f=41&t=872
Click to expand...
Click to collapse
Thanks a lot man! It works now!
razvan11malancus said:
Hi. This is the link to the boot converter.
http://forum.xda-developers.com/showpost.php?p=36885456
All you have to do is flash this zip file from cwm after you first flash the ROM.
I have tried Illusion and PAC-MAN ROMs (N7105, Android 4.3) and also MIUI v5 for N7105 (Android 4.2.2) and all work fine.
There may be some ROMs (PAC-MAN) that give you "error 7" when flashing. You have to change the first line from META-INF/com/google/android/update script.
How I do that. I prefer to change the ROMs extension from zip to apk, then unzip it using APK Tool and go to the file, change extention to .txt and delete the first line (the one that starts with assert), thus the first line becoming the one with "show progress" or "mount". After that I zip it again with APK Tool and sign the ROM with ApkSign. I do not know why, I cannot sign it with APK Tool. After that, the flashing process should go fine. You have to install the right GApps for the ROM you are being flashing and then the boot converter from the link.
The only issue I have found was the absence of vibrations, but I managed to get it back by flashing Thor Kernel for Note 2, like cbeta1111 and eggymustdie told me. So huge thanks to them.
Good luck! Hope you will manage to install the desired ROM. In my opinion, PAC-MAN ROM is the best so far, with many, many options from CM, AOKP and Paranoid Android ROMs.
Click to expand...
Click to collapse
Thanks for detail response
I am using TWRP touch custom recovery. would this process work for TWRP?
I did not get second part about changing first line from META-INF/com/google/android/update script. where is that? You mean first line of custom 4.3/4.2 ROMs we are going to install?
and also do call recoding work in 4.3/4.2 PAC ROMS because i actually use this function and multi windows ?
This is dev forum, not Q&A. All questions should go in questions forum.
Rajaasim1980 said:
Thanks for detail response
I am using TWRP touch custom recovery. would this process work for TWRP?
I did not get second part about changing first line from META-INF/com/google/android/update script. where is that? You mean first line of custom 4.3/4.2 ROMs we are going to install?
and also do call recoding work in 4.3/4.2 PAC ROMS because i actually use this function and multi windows ?
Click to expand...
Click to collapse
Hi. It should definitely work with TWRP recovery as it installs like a normal zip file ROM.
The update script file is located in the ROM. You have to unzip it and go to that location as I have said in the anterior post.
Call recording works but I did not figured yet how to play the file after it is saved. It saves the file as a .3gpp but I think the problem is with Android 4.3 codecs.
EDIT: It works if you try to play it from the built in file manager. Not with Root Explorer. Do not know why.
Multiwindows work great in PAC-MAN ROM:
TheATHEiST said:
This is dev forum, not Q&A. All questions should go in questions forum.
Click to expand...
Click to collapse
Sorry, I know that this section is for developers only but I think it has more visibility here. It wont happen again.
razvan11malancus said:
Sorry, I know that this section is for developers only but I think it has more visibility here. It wont happen again.
Click to expand...
Click to collapse
That is an extremely bad excuse. What on earth do you think the dev forums would look like if everybody just decided to post non-relevant topics anywhere they wanted to?
TheATHEiST said:
That is an extremely bad excuse. What on earth do you think the dev forums would look like if everybody just decided to post non-relevant topics anywhere they wanted to?
Click to expand...
Click to collapse
Are you moderator or what?
Leave it for them to.move or delete
Sent from my GT-N7105 using Tapatalk 2
Rajaasim1980 said:
Are you moderator or what?
Leave it for them to.move or delete
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Errr I did! and they have!!!!!
Doesn't mean I cant voice my opinion (Same as you did) as well as report post!

Categories

Resources