Hello XDA-members,
Today I've tried to port over a Evo 3D CDMA rom to the GSM version, with succes! It really isn't that hard. The first thing I wanted to know is what files are acually different in those 2 versions. It seemed the warm team already figured that out, thanks guys!! Then I took a look at this rom, as it is a hybrid for the CDMA & GSM version.
In that zip file you will find a folder called "devices" this folder contains 2 more folders "shooter" & "shooteru". What I did was look at the files in the folder "shooter", find those files in a sense 3.0 rom(as I wanted to port Android Revolution) I used LeeDroid for this, and then simply replace all the files that I needed to. With as result a working CDMA rom on my GSM phone!
Now it's not fully working, for example it fails to find my wpa2 wifi network.. calling works though! (it did the first boot, 2nd boot it didn't get any signal or I didn't wait long enough) The rom is responsive and pretty fast! Now I don't know if this has been done before, but I would like to tell you guys it's pretty easy to port a rom from the CDMA version to the GSM, of course it still needs a lot of work.
I'm currently uploading the rom for the ones that want to try it out, I've removed some sprint crap as we can't use it anyway..
Please bare in mind I only replaced some files in the Android Revolution rom with files from Leedroid, All credits go to them!
Also the rom is not fully working as far as I know, flash at your own risk.
download link: http://www.multiupload.com/QWECW5FKDR
Congratulations on porting from CDMA to GSM! Hopefully you'll be able to fix the issue and have a lot of the CDMA ROMs on the GSM.
You should check out this guide which should probably get more stuff working: http://forum.xda-developers.com/showthread.php?t=1222746
But keep in mind even after doing that, some stuff still might not work.
yousefak said:
Congratulations on porting from CDMA to GSM! Hopefully you'll be able to fix the issue and have a lot of the CDMA ROMs on the GSM.
You should check out this guide which should probably get more stuff working: http://forum.xda-developers.com/showthread.php?t=1222746
But keep in mind even after doing that, some stuff still might not work.
Click to expand...
Click to collapse
Thanks
It's not that hard though, I'm also trying to get people to get more roms to the GSM version.
Also, no offense but that tutorial is aimed at porting sense from 1 device to another, but the shooter & shooteru are basically the same.. it's more the applications in the rom that need to be replaced I think. Applications like settings (so you can set your APN's) remove the CDMA compass thingy in the status bar etc. Because most stuff seemed to be working, camera worked both 2D & 3D, hw acc, wifi(only no wpa2 =( ), calls work, buttons work, etc.
ybinnenweg said:
Thanks
It's not that hard though, I'm also trying to get people to get more roms to the GSM version.
Also, no offense but that tutorial is aimed at porting sense from 1 device to another, but the shooter & shooteru are basically the same.. it's more the applications in the rom that need to be replaced I think. Applications like settings (so you can set your APN's) remove the CDMA compass thingy in the status bar etc. Because most stuff seemed to be working, camera worked both 2D & 3D, hw acc, wifi(only no wpa2 =( ), calls work, buttons work, etc.
Click to expand...
Click to collapse
thanks for the effort man.can you try porting some icecream roms from CDMA?that would be great
GREAT! I was thinking about that today when I have came across this ROM http://forum.xda-developers.com/showthread.php?t=1277431 it should be some superb ROM but only CDMA, they have Sense 3.0 & 3.5 versions.... do you think that you can quickly look on the 3.5 version? you know, just breaf look to see if it will be possible to push it into GSM...
ybinnenweg said:
Hello XDA-members,
Today I've tried to port over a Evo 3D CDMA rom to the GSM version, with succes! It really isn't that hard. The first thing I wanted to know is what files are acually different in those 2 versions. It seemed the warm team already figured that out, thanks guys!! Then I took a look at this rom, as it is a hybrid for the CDMA & GSM version.
In that zip file you will find a folder called "devices" this folder contains 2 more folders "shooter" & "shooteru". What I did was look at the files in the folder "shooter", find those files in a sense 3.0 rom(as I wanted to port Android Revolution) I used LeeDroid for this, and then simply replace all the files that I needed to. With as result a working CDMA rom on my GSM phone!
Now it's not fully working, for example it fails to find my wpa2 wifi network.. calling works though! (it did the first boot, 2nd boot it didn't get any signal or I didn't wait long enough) The rom is responsive and pretty fast! Now I don't know if this has been done before, but I would like to tell you guys it's pretty easy to port a rom from the CDMA version to the GSM, of course it still needs a lot of work.
I'm currently uploading the rom for the ones that want to try it out, I've removed some sprint crap as we can't use it anyway..
Please bare in mind I only replaced some files in the Android Revolution rom with files from Leedroid, All credits go to them!
Also the rom is not fully working as far as I know, flash at your own risk.
download link: http://www.multiupload.com/QWECW5FKDR
Click to expand...
Click to collapse
Awesome work! You should create a new thread in the dev section to list all successfully ported ROMs.
But be careful, some devs might not be that grateful to see they work ported. So you should ask for permission first.
Xda is a heartless cold place these days .
metamasterplay said:
Awesome work! You should create a new thread in the dev section to list all successfully ported ROMs.
But be careful, some devs might not be that grateful to see they work ported. So you should ask for permission first.
Xda is a heartless cold place these days .
Click to expand...
Click to collapse
I'll make a tutorial some everyone can do it for themselfs as I don't have time to find the right files for every single rom.
Check out the tutorial thread here: http://forum.xda-developers.com/showthread.php?p=21403127#post21403127
Related
Is there such a guide/tutorial/description?
I am interested in porting ROMs to the G1. I am a total beginner, and I could not find anything useful (except the automatic porting of dsixda's kitchen, what is great btw, but I want to learn how to do it by hand, etc).
Could please someone tell me how to do this, what to copy from original ROM for things to work, etc?
Thank you very much!
It's going to vary from ROM to ROM, depending on what device you are porting from and whether it's Sense/AOSP/etc.
You can get some ideas from a couple of my posts though.
http://forum.xda-developers.com/showthread.php?t=723319
http://forum.xda-developers.com/showthread.php?t=815265
Porting is not generally that hard to do... It's getting everything to work right that's a pain.
Also, look at vendor trees for your device. That will give you a good idea about which proprietary files (drivers, etc.) that need to be replaced.
gnarlyc said:
It's going to vary from ROM to ROM, depending on what device you are porting from and whether it's Sense/AOSP/etc.
You can get some ideas from a couple of my posts though.
http://forum.xda-developers.com/showthread.php?t=723319
http://forum.xda-developers.com/showthread.php?t=815265
Porting is not generally that hard to do... It's getting everything to work right that's a pain.
Also, look at vendor trees for your device. That will give you a good idea about which proprietary files (drivers, etc.) that need to be replaced.
Click to expand...
Click to collapse
This is really great, thanks Gnarlyc... been searching all over for tutorials/etc. I was able to port an N1 ROM to the EVO (using dsixda's kitchen); however sensors + radios failed to work after boot-up; probably missed a couple files/libs. Will look these links for tips. Thanks!
gnarlyc said:
It's going to vary from ROM to ROM, depending on what device you are porting from and whether it's Sense/AOSP/etc.
You can get some ideas from a couple of my posts though.
http://forum.xda-developers.com/showthread.php?t=723319
http://forum.xda-developers.com/showthread.php?t=815265
Porting is not generally that hard to do... It's getting everything to work right that's a pain.
Also, look at vendor trees for your device. That will give you a good idea about which proprietary files (drivers, etc.) that need to be replaced.
Click to expand...
Click to collapse
really nice, finaly a topic where i found more infos than just "use the kitchen and change kernel"
other questions :
how do you know you needed to replace some string values by other ? simply open the original rom for you device and compare, or simply guessing the name ???
I have recreated the romer tool. The purpose of this tool is to replace certain files to make D2 roms work on the droid 2 global. To use simply install my file after installing a droid 2 rom via recovery. This version is designed for ginger-blur based roms such as apex and liberty. Do not flash over aosp roms such as cyanogenmod and liquid. I am currently working on creating a aosp romer tool. Do not use on froyo eaither, as this will temporarily brick your phone. I have tested on both apex and liberty, and sensors,gsm,data, and phone are all working. Please enjoy
Disclaimer: I am not responsible for what you do to your phone. If your phones does not do what you like, becomes 100% useless, or explodes killing your wife and children, it is not my fault. I can garauntee that my file is safe, and works perfectly for what it is designed. Make sure to check before you flash a d2 rom that it does not contain a d2 kernel. This could permanently brick your phone! Just be careful
Download v2.2:
http://dl.dropbox.com/u/46535328/D2G-GingerBlur-Romerv2.2.zip
Thanks:
Thanks goes to fabolous for apex , which is were the majority of the files for my romer comes from.
ChangeLog:
V1.0: original, based off of GRD Rommer.
V2.0:completely remade with no more GRD remains.
V2.1:Liberty tweaks put in build.prop.
V2.2:moto boot logo and boot animation added. I can remove this if it is disliked.
Comments:
Has anyone tested out the aosp romer. I would be happy to fix things or add things as people like. I will gladly update this if anyone wants, I have just been working on other things. I have been taking a look at cm source code, and app development. Also eaither one of these will work on Droid X roms. Haptic feed back will not work though.
P.S. If you download this, and enjoy it, please press the thanks button.
**********************************************************************************************************************
This section is for my romer tool having to do with porting the new 2nd init roms or anything that is based off cyanogenmod 7 or aosp that is originaly designed for the droid 2 or Droid X. I have tested it and can approve that it will work for miui,liquid, and cm. I am not liable if this does anything negative to your phone. To use just flash over an aosp rom for the droid x or droid 2 and enjoy on your global. For now the only thing that does not work is gsm. If i can fix it I certainly will.
Thanks: I thank revnumbers for his cyanogenmod builds, as this is were I took the proprietary files for the d2g from.
Comments:
If any of you want me to add something, or try to fix something, please post and I will see what I can do.
Download/Aosp Romer V1.1:
http://dl.dropbox.com/u/46535328/D2G-Aosp-Romer_V1.1.zip
Thanks:
Thanks goes to RevNumbers for his cyanogenmod 7 build, which is were the majority of the files come from.
Change log:
V1.0: Original, fixes phone,cdma data,keyboard,camera,sensors,etc...
V1.1:Fixes su/root permission error.
Comments:
Don't worry if the phone does not receive signal immediately. It takes it a minute.
I accidently set the permissions for su binary wrong. V1.1 fixes this.
! I would HIGHLY not recomend using anything built of of the D2G's romer !
The reason for that is because that method of porting is considered vastly inferior AND because it had many bugs in it because of it. The romer team from Get R Done also had a lot of strife in it and a lack of knowledge. A straight update of the files will not work well.
It needs redone, not updated.
Thanks for the advice aceoyame . I have tested it, and it works, but I do not know what problems may arise from it. I will work on redoing it
also, if you have the time could you describe the problems into more depth of what is wrong with team get-r-done's flashing process. I am not quite as well educated in the art of writing an updater script as you are I am sure.
Well the biggest issue with a romer vs natively porting is that you have too many files that are for one type of rom vs working for others. The romer will only do Gingerblur based as you have it (that's if sensors and everything else works). It will not do any aosp based roms (liquid, CM, MIUI, etc.) The libs are way too different. If you wanted you could make an AOSP romer and Gingerblur romer. Just pointing out the flaws in it.
Thanks for replying ace. I natively ported liberty on another forum. The reason why I made this is so people can just flash it over any liberty gb rom, instead of me having to make an update for each individual version. I have only tested it on liberty, and on liberty sensors,backlights,gsm,phone,keyboard,and data are all working. I would guess that would apply to any gingerblur based rom. I knew that it would not work on cm,liquid, and miui, and did not really care since thanks to you and other devs we already have those roms made for are phone. This is for those roms that only exist on the d2 and not the d2g
Well grats on fixing the sensors then! Rewriting the romer is something we've been wanting to do but could never get around to it. If it is 100% bug free on liberty than it should work for any gingerblur rom. You got sensors to work which was the big issue with the GRD one then you at least fixed something! I would just test the hell out of it and if it works then you probably hammered out any bugs they had with it. An AOSP one would be nice for the other roms. Feel free to put this on Rootzwiki and the other forums.
Thanks, I will make a asop version when I get the time.
As of 8/25/12, this project is officially discontinued. All information below is for archival purposes only and will not be supported henceforth.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
INTRODUCTION
Now that Fattire has lifted his request that everyone build their own zips, I've decided to make available the nightly builds I've been generating. I've got an OS X system cranking out a new build every night at midnight, so there will always be an up to date zip available!
Credit for this rom goes to Fattire, Dalingrin, keyodi, nemith, arcee and the the other hard working people over in the development thread, as well as the the CyanogenMod developers and anyone who's done work on the Nook Color. I wish I could list everyone by name but there's so many great people who've made contributions I can't even begin to do so. I'm just building zips from the source; we'd be nowhere without the contributions these great developers have made to this community.
As nighty builds, these zips may not always work. I'll try to remove any zip found to be broken, but you know the drill: All files provided here are to be installed at your own risk. I'm making built zips available, but no warranty is expressed or implied by the hosting of said zips. I'll provide what support I'm able to, but that doesn't mean that there aren't potentially unknown bugs. If you have questions, you should check the development thread or try the #NookColor IRC channnel on irc.freenode.net.
As posted by Fattire slightly further down, anyone feeling adventurous should definitely consider building from source rather than downloading the built zips. Here's his two cents:
fattire said:
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
Click to expand...
Click to collapse
However, if you're not quite sold on setting up a development environment but you still want to try the goodness that is Ice Cream Sandwich, proceeed on down to the...
DOWNLOADS
Without further ado: The Ice Cream Sandwich zips!
Ice Cream Sandwich Nightly Builds.
The rom does not include the google apps, so you can/should flash the lastest version of those, which is available here.
Finally, I've hosted a few flashable zip files to make small tweaks to the rom. These are all located in the misc. folder on my server. Below is an explanation of each zip and its purpose.
MISC FOLDER INFO
If you notice that some apps are missing from the market, this may be due to the fact that these ICS builds for the nook do not include support for apps which request phone permissions. Although this ideally would be fixed by developers not requesting phone permissions for their app unless it absolutely needs to be phone-specific, you can also fix it by flashing the telephony-permissions-fix.zip file located in the misc folder. You will likely want to flash this file immediately after flashing your rom.
Secondly, if you prefer the old bootanimation from the galaxy nexus, you can also flash the fix-bootanimation.zip located in the Misc. folder, which replace the new CM9 animation it with Homer_S_xda's fixed version. Thanks to Homer for the fix!
NOTES ON INSTALLING TO SD
I've fixed Verygreen's sd installer image to work with ICS -- you should no longer have to flash SP1 first, or rename the gapps to gapps-gb. If you test out this image, please let me know how it works for you! More recently, Leapinlar has stepped up in helping to fix the image further, increasing its size to allow for the larger size of the new nightlies. Thanks to him for his help -- It's available for download here. Huge thanks to Verygreen for helping me to figure out what needed to be fixed -- in the words of HacDan, "He's not just super helpful, he's a genius". Once you've got the new image, you can use Verygreen's original instructions from his thread on SD Installs, replacing "cm7" with "cm9" where necessary.
IN CONCLUSION
Please remember to thank the developers working on this project, as they've done seriously awesome things for us in an amazingly short amount of time. If you have questions/comments specifically regarding my zips, please post them here, but if you have more general questions regarding Ice Cream Sandwich on the NC you may want to head on over to the development thread. Finally, if you're really enjoying the rom I'd strongly recommend that you try setting up a build environment and building your own zips -- even though I'm making prebuilt ones available they're no substitute for the experience gained by getting familiar with the build process yourself, and Fattire has done a great job of making it an extremely accessible and rewarding project.
Thank you!!!!
What bugs can we expect as far YouTube, flash player. Boot loop . A breakdown of what to expect and not to expect. I don't expect anything but like to know for flashing
And you can build too!
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
So awesome!
Youtube missing in latest gapps ?
I installed the latest nightly with the gapps and found youtube app is missing ?
Thanks for sharing! I love nook color devs community! You did an awesome job!
Brilliant work! I upgraded from CM7 and all my existing apps that ive checked worked no problem, it kept all my settings too! Speed-wise I would say its very close to CM7, i use ADW EX in preference to trebuchet, and it just flies!
One thing ive noticed is that NFS shift doesnt behave properly when using the tilt sensor to steer, its axis sensor wants the tablet to be in portrait orientation when the screen is in landscape. Hard to know if its the games fault or the sensor. If thats all there is to complain about this early in the development then the future looks promising
rajazeeshan said:
I installed the latest nightly with the gapps and found youtube app is missing ?
Click to expand...
Click to collapse
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Dual boot ?
I currently have a dual boot environment setup so I can boot into stock (primary boot partition is currently CM7). Does anyone know if this still supports that ? Anything specific I'd have to do with the install then ?
TIA
Thanks a bunch for hosting these nightlies.....let the fun begin!
I just want to point out for the sd-card users using verigreens 1.3 boot image to setup cm7 to run off of sd card and retain stock for various reasons.
That process will also work for ICS/cm9. Currently, you need to flash update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip first. It's found in the ics/cm9 dev. thread: http://forum.xda-developers.com/showthread.php?t=1370873
Then, flash Samiam's nightly builds otherwise you will get stuck in a boot loop right now.
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
I'm gonna stay on cm7 for a while. But I love the progress were seeing with ics.. thanks guys
pavlos46 said:
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
Click to expand...
Click to collapse
What version of the gapps did you have where the wifi location worked? If you link me to that I can see if there's something missing from my gapps zip.
YouTube is incompatible from the market. Actually, it appears any device I have that runs ICS is listed as incompatible.
youtube app missing in gapps
Samiam303 said:
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Click to expand...
Click to collapse
Unfortunately thats not the case when I search market it doesn't list YouTube app and when I
Google it takes me to mobile YouTube app in market that is not compatible with this device.
I salute you all dev. gurus.
Hat off and thanks for the ICS
Awesome thanks so much!
Hey,
awesome awesome work, thank you very much!
I have a slight problem with the GApps, though: I came from update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs and just updated over that with some ics-apps installed. Unfortunately, I do not remember which ones.
Now after the update all my apps are there, but the home screen wiped (not so bad), but my Google Account vanished and I cannot add a new one. Neither in the Settings, nor by opening GMail, Talk, whatever. These will just crash.
Any suggestions?
Thanks again for all your work and energy, I really appreciate that.
Greetz,
Felix
ZenoGia said:
Awesome thanks so much!
Click to expand...
Click to collapse
+1 .
LETS GET THIS LIST GOING!!
I know there are several threads on this allready, but finding the actual information of which roms work and which don't is very hard, so I've decided to make this thread to have a centralized place to list and discuss roms that work with the patch.
First things first:
The verizon patch and information about it can be found here. http://forum.xda-developers.com/showthread.php?t=2055218
Things to remember:
Do Not flash modems from any rom that doesn't have a Verizon Base.
Always make a backup before testing the patch with new roms.
(not sure if kernels are harmfull, or if you need to flash specific verizon kernel after flash, will update when I gather more info, for now this is a list of known working roms and how you got there.
Now the Good Stuff.
I thought since I was making this thread I would jump in and test first. here's what I have so far.
1) Ok, my first attempt wasn't so good. I installed the whompasaurus rom from the sprint forum. Device booted fine, but upon boot I got an Ecryption Failed screen with no way to go any further (to my knowledge anyway) I feel this is stll relevant to the thread. So post your experiences and I will update the op accordingly. I have seen a few roms on the at&t forum that say "no device check" therefore I assume they will work. Time will tell.
Please feel free to list roms that you have succesfully got working with the vzw patch and if you used build prop edits to achieve this as well then please be specific and I will add them to the op as they come in.
Ive got all the DLL1 and DLL4 roms to work in the att & tmobile forums.
The caveat with Scott's patch is that it is only designed to get TW roms from other carriers working on our devices. While most TW roms will boot fine after the patch, they will more than likely require some build.prop modification to get them completely up to snuff. In the case of porting AOSP roms, the patch isn't entirely useful, save for a few vzw specific system applications, as AOSP doesn't use CSC files. AOSP porting can be done with build.prop adjustments.
Can you elaborate on which build prop edits need to be done, ro.product.model, etc. As I stated above I tab into an encryption problem, would a stock Verizon build pro fix that?
Sent from my SCH-I605 using Tapatalk 2
Jsminnis please add me on gtalk. [email protected]
hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
+1
Sent from my SM-N900V using Tapatalk
hectorz321 said:
hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
Click to expand...
Click to collapse
Permission failure? Noob here too
I am guessing the ROM you tried to port checks for the Model number of the phone before flashing. What ROM did you try to port to and if you could post the instructions here we will make this the porting thread
Given that HTC One has all the custom ROM's and kernels we need devs or someone like us who can follow instructions to start doing it. I am sure we will get help from one another and end up with custom ROM's for the MAX.
I was also thinking of doing this but just to start with i don't want to look at the fingerprint scanner and may be later we could get it working.
I am certain most people would be willing to not have a working fingerprint scanner, as a trade off for a few custom roms/kernels...
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Murrda said:
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Click to expand...
Click to collapse
this was exciting to read, best of luck
I am going to get Ubuntu installed today and then Android Kitchen here i come!
pradeepvizz said:
I am going to get Ubuntu installed today and then Android Kitchen here i come!
Click to expand...
Click to collapse
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
DeadPhoenix said:
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
Click to expand...
Click to collapse
Thanks, i just installed it via virtual box without disturbing my system.
Just got android kitchen up and running, on prting sides of things got further this time, into aroma installes but error 7 which suggested earlyer is to do with mount points, if anyone could happen to help with theese it would be fab ))
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Click to expand...
Click to collapse
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
pradeepvizz said:
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
Click to expand...
Click to collapse
Murrda said:
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
Click to expand...
Click to collapse
heyy i could use some help doing this part in android kitchen. straight from android kitchens page but i can't seem to get the recovery.fstab out anyway! im on t6ul verson of the max by the way thanks
/HIDE (sorry dont know how to get this to work (forum noob here too)
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
hectorz321 said:
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
Click to expand...
Click to collapse
Good start mate! awesome!
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
hectorz321 said:
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
Click to expand...
Click to collapse
Which guide are you following? i just cooked a ROM today first time. I made the stock ROM for the T6UL.
---------- Post added at 08:34 PM ---------- Previous post was at 08:34 PM ----------
ooo, Merry Christmas everyone
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
HolyAngel said:
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
hectorz321 said:
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
Click to expand...
Click to collapse
Yeah, i know for the kernel, without being able to mess with the zimage, the sense max kernel lacks the init.environ.rc from gpe, the fstab file is different(at least file extension), and there's a few things that point to sense files or folders that don't exist on gpe. Currently there is no released source for the max yet :'( so unless someone knows how to do it manually and hasn't shared HOW to do so, I just have to wait.. Hopefully it won't be too long.
Sent from my HTC One using XDA Premium 4 mobile app