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.
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
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.
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
closed
reserved
Thanks a bunch
is this Jelly bean 4.1.2?
sojay said:
is this Jelly bean 4.1.2?
Click to expand...
Click to collapse
Yes it is
Got it installed and it works good, Nice to have my gps working properly again!
Can I flash a kernel with this?
funbulton said:
Can I flash a kernel with this?
Click to expand...
Click to collapse
it better be touchwiz and be for this device.. LoL I dont know for sure but I bet Jedi would work or faux's kernel... no guarantees though, wait for someone to answer that knows LoL or google it... I never have played around with telus ROMs and TMO kernels together... it should work but again not sure. if you test it let us know the result.
Rushing said:
it better be touchwiz and be for this device.. LoL I dont know for sure but I bet Jedi would work or faux's kernel... no guarantees though, wait for someone to answer that knows LoL or google it... I never have played around with telus ROMs and TMO kernels together... it should work but again not sure. if you test it let us know the result.
Click to expand...
Click to collapse
On ICS they would generally mess up the auto rotation, but work otherwise.
Rushing, thanks a lot for this, will be flashing soon.
Any indication the new infamous wipes are needed for flashing the telus 4.1.2? (versus TMo?)
cchriss said:
On ICS they would generally mess up the auto rotation, but work otherwise.
Rushing, thanks a lot for this, will be flashing soon.
Any indication the new infamous wipes are needed for flashing the telus 4.1.2? (versus TMo?)
Click to expand...
Click to collapse
if on CWM then use the wipees.
Cooool ! Thanks a lot Rushing !
I'll make sure to try this ASAP
Rushing said:
if on CWM then use the wipees.
Click to expand...
Click to collapse
Clean install
- Factory reset on old ROM
- Infamous superwipe
- Telus Radio
- ROM
working great, you're awesome
cchriss said:
Clean install
- Factory reset on old ROM
- Infamous superwipe
- Telus Radio
- ROM
working great, you're awesome
Click to expand...
Click to collapse
Thanks brotha,
ROM COOKS AND USERS can use this as a base for their ROM(s).
All I ask is a thank you on this O.P. and mention of this base in your O.P.
That's it.. Enjoy
again great job...
btw... any way to get the volume wake for this? and is this deodexed?
iviorph said:
again great job...
btw... Any way to get the volume wake for this? And is this deodexed?
Click to expand...
Click to collapse
yes and yes =]
Thanks Rushing. Been waiting to try this, but didn't want to have to go through Kies or ODIN and reroot. Knew someone would come through.
Thanks, a lot. Maybe people can use the telus one for the base of their ROMs now. It's clean of bloat, tethering is native so you don't have to mess around, etc. I mean it's pure TW. I know most custom ROMs are debloated. But where TMO is concerned it can never be clean enough.
s3nr1 said:
Thanks, a lot. Maybe people can use the telus one for the base of their ROMs now. It's clean of bloat, tethering is native so you don't have to mess around, etc. I mean it's pure TW. I know most custom ROMs are debloated. But where TMO is concerned it can never be clean enough.
Click to expand...
Click to collapse
I agree, but TMO has wifi calling so that base is quite popular, but I am sure there will be a nice custom telus rom eventually.
IVIorph said:
again great job...
btw... any way to get the volume wake for this? and is this deodexed?
Click to expand...
Click to collapse
Take the android.policy out of /system/framework in my JB 4.666 Rom &add it in to your current system/framework (deodexed) ROM. And reboot.
Sent from my Nexus 4 premium
Rushing said:
Take the android.policy out of /system/framework in my JB 4.666 Rom &add it in to your current system/framework (deodexed) ROM. And reboot.
Sent from my Nexus 4 premium
Click to expand...
Click to collapse
Thanks!
In case anyone else wanted it, it's attached below. (copy to system/framework)
I really like the ability to use the HTC logo as a button, but the only way i know how to do this is the slim bean rom. So my question is, anyway to get this function on a sense based rom? All info would be greatly appreciated. thanks
delete
Androcles said:
there are many kernels for htc one... check the links below.
http://forum.xda-developers.com/showthread.php?t=2249774
http://forum.xda-developers.com/showthread.php?t=2307371
http://forum.xda-developers.com/showthread.php?t=2255900
Click to expand...
Click to collapse
Woah there!!!!!
OP DO NOT FLASH THOSE KERNELS!
You could brick!
Never flash anything that was not made specifically for your device. If you bother to read the first post in most of those threads they specifically say that Verizon and sprint are not supported.
Please do not post links to potential harmful threads.
We will have custom kernels as soon as HTC releases kernel source for our device. If you can't wait that long then a few of the AOSP ROMs have the HTC logo working as a button.
definitly not flashing any of those haha.
but thank you both for the responses
I'm sorry. didn't notice that. I flashed the aosp one on mine...work pretty well.
Androcles said:
I'm sorry. didn't notice that. I flashed the aosp one on mine...work pretty well.
Click to expand...
Click to collapse
Thanks for editing your post.
None of those kernels were made for our device and could potentially break stuff now that we are s-off.
GrayTheWolf said:
Thanks for editing your post.
None of those kernels were made for our device and could potentially break stuff now that we are s-off.
Click to expand...
Click to collapse
The aosp one works well.
Androcles said:
The aosp one works well.
Click to expand...
Click to collapse
How were you able to run a kernel made for a different variation?
Sent from my HTC6500LVW using Tapatalk
refreblast said:
How were you able to run a kernel made for a different variation?
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
flashed it month ago. no any problem. just flash it. i don't know about the google edition and sense, but aosp works
http://forum.xda-developers.com/showthread.php?t=2236121
That is the kernel I using on cm10.2. of course, I'm on verizon.
VanirAOSP uses a custom kernel that allows the HTC Logo to be used as a sleep/wake button.