Related
Hey everyone, well, ironically, I'm asking for help . I've wanted to create a AOSP ROM, but I can't find a guide on getting AOSP to the Sprint Hero. Is there a step by step guide for compiling it, with all the config files needed? Thanks, I really would appreciate it, and I'm sure you'll appreciate the future ROM's of mine too .
EXTREMELY tempted to post a lmgtfy
justinisyoung said:
EXTREMELY tempted to post a lmgtfy
Click to expand...
Click to collapse
Uhh... I will literally scream if it's on google. I went through, so many pages googling it. I have compiled android before, yes. But not for the hero.
This is what i have been trying to make work.
http://android.modaco.com/index.php?s=&showtopic=301857&view=findpost&p=1179830
Its only a peice of the puzzle. I havent been able to do much with it, I wasnt able to find where I needed to shove libcamera for our hw to get past an error.
PM Darch....
kkruse said:
This is what i have been trying to make work.
http://android.modaco.com/index.php?s=&showtopic=301857&view=findpost&p=1179830
Its only a peice of the puzzle. I havent been able to do much with it, I wasnt able to find where I needed to shove libcamera for our hw to get past an error.
Click to expand...
Click to collapse
what make errors have you been receiving. sometimes when you compile using that vendor tree some of the libs don't get pushed into the target.
I posted a "vendor overlay" ZIP for our CDMA hero elsewhere on this site (it's the LoX GSM hero overlay with edits for heroc plus some extra libs, etc, for 2.1), I was initially hoping for some feedback on it from some of the other devs. I was having the same issues darch mentions where some of the files don't copy over during the build so you just have to copy them into the target as the errors come up. Search my userID plus "vendor" and "voodoo" and it should come up.
5tr4t4 said:
I posted a "vendor overlay" ZIP for our CDMA hero elsewhere on this site (it's the LoX GSM hero overlay with edits for heroc plus some extra libs, etc, for 2.1), I was initially hoping for some feedback on it from some of the other devs. I was having the same issues darch mentions where some of the files don't copy over during the build so you just have to copy them into the target as the errors come up. Search my userID plus "vendor" and "voodoo" and it should come up.
Click to expand...
Click to collapse
you could do that to fix it... or we can fix the unzip scripts, because that is the root of all the problems in which the camera libs aren't making it to the target.
Btw, i'm gunna check out your vendor overlay. sounds like it'll help people compile cyanogenmod a bit more eaily.
darchstar said:
you could do that to fix it... or we can fix the unzip scripts, because that is the root of all the problems in which the camera libs aren't making it to the target.
Btw, i'm gunna check out your vendor overlay. sounds like it'll help people compile cyanogenmod a bit more eaily.
Click to expand...
Click to collapse
I never investigated it very deeply. If you know it's the unzip step, that would be great to have it fixed. BTW, there two extract-files.sh in my overlay, one that pulls needed files from the device, and another that pulls them from a ROM (came in handy at one point). I'm still not clear about how much variability there is with libs, etc, from version to version, you would know better.
Finally, the kernel zImage included is just Toast's .29 that I built from scratch the day I posted the overlay. There's probably a newer version now...and I assume you can just package with your own boot.img anyway.
darchstar said:
what make errors have you been receiving. sometimes when you compile using that vendor tree some of the libs don't get pushed into the target.
Click to expand...
Click to collapse
sorry to leave ya hanging but I just checked in... let me recompile it again and see.... Ill probably have the results back in the AM. Too tired now
Hi all,
I realize this is a post about a Motorola phone but please bear with me.
As you might know, the Milestone firmware is firmly locked, unlike its cousin Droid. Among many things, this forbids overclocking because we can't change the kernel and unlock new frequencies.
However I developed a solution that allows overclocking by changing key structures directly in the kernel memory in runtime. All you need is a rooted phone; no flashing involved. For this to work, the module must know two memory addresses that are specific to each kernel. Fortunately, Motorola appears to have reused its kernel on most 2.1 firmwares, and I've yet to come across a firmware where it doesn't work by default. Confirmed working are Central Europe, Telus and Brazilian firmwares. Testers are welcome to give it a try.
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone. You may say it's unneeded because you can already overclock; but you must flash a specific kernel to get a particular speed. It would be much better to be able to set any maximum frequency/voltage on the fly without flashing or rebooting. For instance, you could overclock to 1.0 GHz before a browsing or gaming session and then return to a lower frequency like 600 MHz, though still overcloked, for battery savings and safety. It's up to you.
Milestone users can try it out now:
http://code.google.com/p/milestone-overclock/
For the rest of you, what do you think?
sounds fantastic, I'd love to check it out but for the life of me I can't find the page.
If you want to pm it to me, I'll post it.
Nice. Telus Milestone User here. Would love to learn how to do this for mine.
Here is the project link:
http://code.google.com/p/milestone-overclock/
found it. looks like a fantastic idea.
How can we help get the addresses?
awesome .....wht there is no milestone/droid section here is beyond me ....wtf
Because it was decreed months ago by someone and no one seems to like changing their mind once they make a decision in this day and age.....
but it's need to root, could you fix it？
stevecai said:
but it's need to root, could you fix it？
Click to expand...
Click to collapse
what's the problem with rooting the milestone? There's plenty of solutions for that. Just no custom kernel/ramdisk, which this works around by using a kernel module.
hi,
i use the 2.1-reu version on my milestone,
but in order to prevent the 2.1 introduced alarm bug,
i have updated the kernel (only) to the 2.1-telus
(via a sbf).
is possible to use this mod to overlock my phone?
how?
if not, how help you to obtain the addresses?
thank's and continue your great work!
robert
gemini002 said:
awesome .....wht there is no milestone/droid section here is beyond me ....wtf
Click to expand...
Click to collapse
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.
staticshadow said:
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.
Click to expand...
Click to collapse
I have read this explanation several times.
I do not mind, but then because there are subforums dedicated to sonyericsson, hp, etc in xda.
modmymoto is good but the best developers site is, withous any doubt, xda-developers!
Re: milestone-overclock
Xda-developers is for htc and android is for porn.
Welcome to xda btw and great job. Now prepared to be flamed for uttering the M word.
-------------------------------------
sent via xda app from my milestone
ady said:
android is for porn.
Click to expand...
Click to collapse
are you Steve Jobs ?
miragu said:
Hi all,
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone.
Click to expand...
Click to collapse
Will the method to find the right address that will be posted at /wiki/Disassembly work with every phone and kernel,too?
Has the app something like a setting where you can just change the address to the one you found with the method above?
Would really love an overclocked 2.1 on the HTC HERO. There is no oc-2.1-kernel for the Hero, yet.
Thanks for the great work, til now!
this is a good via to mod any application.
please, publish the source code of your applicacion ASAP.
thx
Source code for the kernel module released
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.
miragu said:
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.
Click to expand...
Click to collapse
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx
The overclock.ko is created automatically when you press the "Load module" button in /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko. You don't need to copy it. I'm providing it separately so that people can load/bundle it without ever running the apk.
bartito said:
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx
Click to expand...
Click to collapse
ok,
if i'm interested on have overclocking on my milestone after boot the system, and don't interested on manually execute the apk on each reboot, i need only to copy the OverClock.ko to /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko on boot time ?
but in your wiki page says to execute "insmod overclock.ko max_rate=800000 max_vsel=62"
please, provide me instructions to set overclock in boot time
The module created by the apk is preserved across reboots. However, if you want to run the module completely standalone I recommend you put it in /data/local/overclock.ko and run insmod /data/local/overclock.ko max_rate=800000 max_vsel=62
Can anyone say is there any kitchen or tools to build rom for defy? How are cm7 and miui made. Can you give the links to those file? Really wanna know how its made
me too..
i also want to know..
Sainyam said:
me too..
i also want to know..
Click to expand...
Click to collapse
I reached xda completely but there is no ways mentioned for defy. I wonder how CM and MIUI guys are able to build. I know they get the codes from GOOGLE opensource. But when i saw, i couldn't understand anything from Android Development page
For god sake's can any DEV please say how to make custom roms for DEFY
If you want to know how CM7 needs to be build, check the CM7 wiki and search for 'how to build'. For examples of changes, check review.cyanogenmod.com
This is a complete new build if android (compiled from source). To modify existing build, search google for build prop changes, de-(and re-)compiling apks, res changes...
With miui you can only remove/add apps, translate,... The same things as with a Motorola ROM cause thre source code is closed.
There is no straight forward way. If there was, you get what happens with other devices. A million ROM's with no contribution at all.
You will have to search and learn a lot. If only I had the time
Sent from my MB525 using XDA
labsin said:
If you want to know how CM7 needs to be build, check the CM7 wiki and search for how to build. For examples of things that change, check review.cyanogenmod.com.
This are complete new builds if android. To modify existing build, search google for build prop changes, de-(and re-)compiling apks, res changes...
With miui you can only remove/add apps, translate,... The same things as a moto ROM cause three source is closed.
There is no straight forward way. If there was, you get what happens with other devices. A million ROM's with no contribution at all.
You will have to search and learn a lot. If only I had the time
Sent from my MB525 using XDA
Click to expand...
Click to collapse
Thanks. will check and see. It will be help for many people. Thanks man!!!
labsin said:
If you want to know how CM7 needs to be build, check the CM7 wiki and search for 'how to build'. For examples of changes, check review.cyanogenmod.com
This is a complete new build if android (compiled from source). To modify existing build, search google for build prop changes, de-(and re-)compiling apks, res changes...
With miui you can only remove/add apps, translate,... The same things as with a Motorola ROM cause thre source code is closed.
There is no straight forward way. If there was, you get what happens with other devices. A million ROM's with no contribution at all.
You will have to search and learn a lot. If only I had the time
Sent from my MB525 using XDA
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/wiki/Building_from_source i can't find the guide for DEFY here. Please help
Same as fe atrix but replace olympus with jordan.
The copying of proprietary files doesn't need to be done.
A useful utility for building could be the cm gui (somewhere on xda)
Gui:
http://forum.xda-developers.com/showthread.php?t=1415661
(check 2nt post for a better list of needed software then on cm wiki, these need to be installed like 'sudo apt-get instal ...')
Sent from my MB525 using XDA
labsin said:
Same as fe atrix but replace olympus with jordan.
The copying of proprietary files doesn't need to be done.
A useful utility for building could be the cm gui (somewhere on xda)
Gui:
http://forum.xda-developers.com/showthread.php?t=1415661
(check 2nt post for a better list of needed software then on cm wiki, these need to be installed like 'sudo apt-get instal ...')
Sent from my MB525 using XDA
Click to expand...
Click to collapse
Thanks very useful. Atleast now i can make custom ROMS for my taste. Thanks
I would also like to know
well we all love Fingering...but beaware
well i know it feels amazing while fingering our own mobile...getting something better out of it but b sure that what u r doing or u may break anything flash button light which i did
and ya thanks for the questioner and thanks for great answer
same question was running in my mind
INDIANs please b aware what u r doing because MOTO service centres are way bad
specially mumbai
asn39 said:
well i know it feels amazing while fingering our own mobile...getting something better out of it but b sure that what u r doing or u may break anything flash button light which i did
and ya thanks for the questioner and thanks for great answer
same question was running in my mind
INDIANs please b aware what u r doing because MOTO service centres are way bad
specially mumbai
Click to expand...
Click to collapse
Yep.In my place they don't sell Moto phones. If i break only i had to fix it myself.
How to port Sense.
Source: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/164989-guide-how-i-port.html (second post)
This is NOT my guide, just posting it here!
This is a very difficult process that I hope you'll understand.
First step is to find a device that is preferably VERY similar to your device, in this instance I guess we would use the htc thunderbolt, which I've been told multiple times that it is used for the MT.
You're going to want to use CM7 for parts. Simple enough.
I will be referring the Sense ROM to SENSE and CM7 as BASE to simple things up. So remember that.
When I say replace, I would recommend deleting from one and adding it with the other
Open up Sense and Base in different windows.
Put in the boot.img from Base into Sense (make sure you put the original boot.img in some other place that you'll remember)
go into /system/usr on both
replace keylayouts and keychars from Base into Sense (this is just your keys)
download dsixda's kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
Get the ROM you have so far set up in it and what not (I'm a little fuzzy at this part)
Once you get done with that, run the menu in terminal and navigate your way to decompile the boot.img (action key- "a") and then run the same thing except run the action key "w" to decompile the original boot.img. So the key here is to decompile both boot.img's.
Go into the ramdisk on both and go into init.rc
THE MOST IMPORTANT PART IN THIS (THE MATTER OF BOOT AND BOOTLOOP) IS THE LINE
"export BOOTCLASSPATH" near the top. It will have a bunch of lines after it. Now in the Base's boot.img, delete this whole line. Replace it with the lines from Sense's boot.img.
Now you can add anything else you want that looks like it belongs (preferably anything sense related)
Don't recompile the boot.img yet.
Now we add a2sd. To do this, just follow this guide (https://www.facebook.com/note.php?note_id=158823170833688)
The only thing you do in there is the edits to the init.rc, don't listen to the decompiling/recompiling mentions. Now you can go back into the menu for the kitchen and recompile the boot.img (action key - "b"). Now don't compile the WHOLE ROM, just take the new boot.img in working_** and put it into the Sense zip.
Now you're going to want to download my ROM (sorry, just don't feel like uploading each individual file) http://gannon5197.blogspot.nl/2012/03/got-sense-booted.html
And go into the /system/bin on both
these are the files you're going to need: a2sd, bash, apps2sd.hlp, busybox.a2sd, chka2sd, jita2sd, launcha2sd, starta2sd, and maybe possibly sh (try once without it)
And you're going to want to set permissions for each one of these in the updater-script (look at mine for references)
Now also look at my zip and you'll see move_cache_sd. Put that in yours and set permissions for it in updater-script (use mine for references)
After that, the other stuff is mainly just getting rid of all the bloatware, (look in /system/app and /system/media) I wouldn't delete any libs as of right now. If you try to flash it and it reboots recovery then it is too big.
If it is too big, you're probably going to want to move a lot of the apps to data. To do this, just make a file called data/app/put_your_apps_here on the root of the zip. You're going to have to set permissions for it in the updater-script, but use the test.zip I sent you in the original.
This will most likely get you booted. Nothing will likely work. Which is expected. If you have any problems, just use logcat. It will be your bestfriend. Have fun porting
Click to expand...
Click to collapse
reserved
Thanks for reopening it bro...
Sent from my LG-P500 using Tapatalk 2
No problem :thumbup:
Don't know how this above awesome thread is so blank
Have u tested if this way works
Sent from my LG-P500 using Tapatalk 2
great guide, gonna try out soon
hmm this one's new for me. saved
should come in handy sometimes
someone has to do this for the Galaxy S2.
Will it also work for ICS ROMs?
I must do this. Anybody know where I can get the firmware for the One S?
Can i use a Gingerbread ROM as a base instead of cm7?
Hello for lg p500 there is 2 sense rom but data and mic not working in both rom can you help to solving that problems????btw great tutorial.
in fact sensse porting is differnet from the tutorial showed it is a little bit more difficult and there are some libs needed that there is only for the devices you are porting to. so a general tread will not really work
QuBe2 said:
in fact sensse porting is differnet from the tutorial showed it is a little bit more difficult and there are some libs needed that there is only for the devices you are porting to. so a general tread will not really work
Click to expand...
Click to collapse
Well this is not my tutorial just found it on the internet so I don't know if it works
Lord Inglip said:
Well this is not my tutorial just found it on the internet so I don't know if it works
Click to expand...
Click to collapse
why sharing things on the internet
QuBe2 said:
why sharing things on the internet
Click to expand...
Click to collapse
Because it's the internet. This guide was the only thing I could find.
Well you ported a htc sense One x rom to the Nexus S, so can you show us how you did it?
Lord Inglip said:
How to port Sense.
Source: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/164989-guide-how-i-port.html (second post)
This is NOT my guide, just posting it here!
Click to expand...
Click to collapse
Similar phone means the same chipset,processor and gpu??
a2441918 said:
Similar phone means the same chipset,processor and gpu??
Click to expand...
Click to collapse
Yes it's better if the phones have the same hardware
Lord Inglip said:
Yes it's better if the phones have the same hardware
Click to expand...
Click to collapse
I have an xperia x10.. will the nexus one and HTC desire be suitable??
My cm7 rom which i downloaded doesn't have a boot.img file.. So how to get it?? Is it the system.img got from a nandroid backup?? and the sense rom which the post refers to is the stock sense rom of the phone in a zip format or a modded one??
Not working..stuck at boot logo
Hi,
I synced the CM10.1 source last weekend. I mucked about with the kernel. I pointed it to Christopher83's custom toolchain. I built it. It works. I'm content.
However my plan was to revive 4.2.2 and actually ADD to it, otherwise you could just go and download the zip which the Andromadus team uploaded. Unfortunately I've discovered that I'm completely incompetent when it comes to firstly finding things to add, secondly finding the commit, and then thirdly trying to cherry pick and apply the commit so it works. I haven't really got to stage 3 yet.
So here's my suggestion: could someone please work with me or if syncing sources etc. is not possible, at least help me by being knowledgeable enough to know some good features, point me to the commits, and help me fix conflicts so that I can apply them successfully. Therefore I either want a team, the 4.2.2 revival team as it were, or someone or some people to help me if they can't directly interact with the sources. Don't worry if you can't build for whatever reason: if you can sync specific repos, e.g. settings, frameworks base, and modify them, and push them, so that I can build the ROM, that's fine. Anyone who helps at all will be deemed equally if not more important than myself, as I expect I'll ultimately just end up being the builder.
Thanks very much for your support.
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
Click to expand...
Click to collapse
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
HTCDreamOn said:
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
Click to expand...
Click to collapse
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
Click to expand...
Click to collapse
That looks interesting, but it's for KitKat... I'll try later once I'm confident. In the meantime, how can I get this to work: https://github.com/SlimRoms/packages_apps_Settings/commit/fb2ea42468bea20f09b99048c9e7535b6cde643f I'm OK apart from the very last bit in UserInterface.java, although I'm applying that code to SystemSettings.java anyway. Thanks
@demkantor @_MarcoMarinho_ I've synced the PA source, can you help me at all setting up the vision.adds file? Thanks
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, as you know I synced the CM10.1 source a while ago so I used repo init --reference to sync the PA jellybean-legacy sources. Thanks for helping
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
demkantor said:
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
Click to expand...
Click to collapse
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
HTCDreamOn said:
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
Click to expand...
Click to collapse
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
demkantor said:
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
Click to expand...
Click to collapse
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
hmm... it looks like there will be a bit more to make than just the local_manifests
but i would attempt this first and if it doesnt work than follow the direction in that post as there me be a special way needed to build for pa, which i never have tried to build
most of what they are after will get pulled from local_manifests folder and placed appropriately. but at the same time... never used ./rom-build.sh before so this may be specific to pa, as in you need to follow their steps....
eh, just give it a try, if it doesnt work ill help you create those json files and build it the way laid out in their guide!
HTCDreamOn said:
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
Click to expand...
Click to collapse
Isn't easy, you need to add more repos to configure it for our phone.
This is very diferent:
http://forum.xda-developers.com/showpost.php?p=45827346&postcount=3467
As I said before, you need extra repos than CM needs. You can talk to the dev that made the SlimBean for our phone, as it's based on AOSP he needed to configure it as well.