This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
androiddecoded said:
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
Click to expand...
Click to collapse
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
alteredlikeness said:
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
Click to expand...
Click to collapse
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
jimbridgman said:
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
Click to expand...
Click to collapse
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
alteredlikeness said:
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
Click to expand...
Click to collapse
so do I.... Don't forget who is on the cm coding team....
I did some looking internally at CM and found that these are semi-official, right now, with a big but, the kexec I am told is what is keeping it with the semi status...
They are looking into changing that for kexec based compiles, so.... Hopefully, that happens.
jimbridgman said:
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Click to expand...
Click to collapse
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
androiddecoded said:
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
Click to expand...
Click to collapse
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
I don't want to be the antagonist here , but I did everything in Windows until I started my attempts at building from source.
Dsixda's kitchen works fine in Windows with Cygwin. I started off building pseudo-ROMs (or rebuilding the stock ROMs) with the kitchen, and then I eventually just used 7-zip and other tools and did it manually.
I currently use Ubuntu 12.04 64-bit in Virtual Box in Windows on my laptop to compile from source. But I did just install 12.10 fully on my old PC... 32-bit unfortunately.. I need to upgrade that comp, or find a work-around to build in 32-bit.. Anyhow, it runs much nicer than windows xp did.
Sent from my paranoid phone's mind
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
androiddecoded said:
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
Click to expand...
Click to collapse
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
Thanks sir. Got that
Will try to contribute something if I can. Kudos to our dev team. You guys are doing a great job. Happy to be a part of a great community
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
androiddecoded said:
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
Click to expand...
Click to collapse
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
I will do it tomorrow. Really thank you for assisting me.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
androiddecoded said:
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
Click to expand...
Click to collapse
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
jimbridgman said:
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
Click to expand...
Click to collapse
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
4.1 leak is not a flashable zip.
The meta-inf folder items are for zips that are flashed in recovery.
And, not to dissuade you from jumping in to modding/dev'ing, but you may want to take things a bit slower... Start small.. And read/research a lot.
Sent from my paranoid phone's mind
androiddecoded said:
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
Click to expand...
Click to collapse
No, there is not a flashable "zip" for the Moto 4.1 leak, you will have to build that on your own with the Rom kitchen, since it is an FXZ, it will not have those flashable parts. The kitchen is very easy to use, it is menu driven and only takes about 30 min to an hour to do what it seems you want to do.
You can replace the launcher from within a flashable zip, but you might have issues, because the MOTO blur junk that is in their ROMS DEPENDS on it, if you do NOT leave it (moto blur launcher) in /system, then a number of things will not work that depend on the moto launcher (they are embedded in the xml files in the apks, and need to be edited to NOT look for the moto laucher), I think it is more trouble than it is worth, personally.
I would throw Apex in there if that is what you want, and then on first boot select it as your default launcher and be done with it, less issues and mess, other than the old moto launcher taking space in /system. BY the way ANYTHING that you put in /system is not really 100% upgrade-able by the market app, so like lets say you put apex in /system, then the market can not update the version in /system, since it is read only, and it will either fail the update, or try to put the newer updated files /data, so you will have things in two places for your 3rd party launcher. It is MUCH better to put any APKS that would come from the market into /data so they can get updates with out any odd issues, just a heads up...
--EDIT--
As alteredlikeness said about the same time I was posting, start a little smaller, and do a bunch of learning, because from what I see you asking about and posting in here, you have a good bit of learning to do, about how the directory structure and things are and work in android, as well as some ROM building basics.
Related
I have some news on my CM7 porting, good and bad.
The good new first.
Good:
I can get the FULL version including the kernel to run in safestrap, and it is like 97% working.
Bad:
I can not get the ROM, without the kernel, to boot properly when flashing it to the phone from the bootstrap. I have spoken with several experts and this may not be something we can work out until the bootloader is unlocked. There are hooks in almost every part of CM that make android calls, that are part of their own version of android (it is heavily customized, and the code is available, and how I got it) and the kernel they use. The reason this works in safestrap, is because I can load the kernel on top of our kernel, but it is slower this way. Think of running a VM on top of your current OS, and how that can have some lag if your computer is not real powerful.
The bottom line, I am not sure if we can get CM working for everyone just yet. I am not sure where lfaber06 is at with CM9 and if he has tested it directly on the phone without safestrap yet or not. Maybe he will post in here what his experience has been, with this.
I'd like to give it a whirl anyway.
mtnlion said:
I'd like to give it a whirl anyway.
Click to expand...
Click to collapse
ONLY with safestrap, right now. If you try to flash it with the bootstrap it will softbrick your phone.
--EDIT--
Remember safestrap is not really working right now... lfaber06 and I have some highly modified versions that really are not for the rest of the world yet, and my version has a custom compiled version of CWM, and is a little buggy.
jimbridgman said:
I have some news on my CM7 porting, good and bad.
The good new first.
Good:
I can get the FULL version including the kernel to run in safestrap, and it is like 97% working.
Bad:
I can not get the ROM, without the kernel, to boot properly when flashing it to the phone from the bootstrap. I have spoken with several experts and this may not be something we can work out until the bootloader is unlocked. There are hooks in almost every part of CM that make android calls, that are part of their own version of android (it is heavily customized, and the code is available, and how I got it) and the kernel they use. The reason this works in safestrap, is because I can load the kernel on top of our kernel, but it is slower this way. Think of running a VM on top of your current OS, and how that can have some lag if your computer is not real powerful.
The bottom line, I am not sure if we can get CM working for everyone just yet. I am not sure where lfaber06 is at with CM9 and if he has tested it directly on the phone without safestrap yet or not. Maybe he will post in here what his experience has been, with this.
Click to expand...
Click to collapse
I have made quite a bit of progress on cm9 in safestrap, the only real issue i have is the radio which i am constantly trying different things with. I have not tried flashing cm9 or cm7 in the bootstrap but I have a method for it..(I think, Remember the D3 can run cm7 from the bootstrap) I have a file I have modified for cm9 that im sure will work for cm7 flashing in bootstrap. You would need to add some modified files to /system/rootfs/ and preinstall support to boot init.d and also run the fixboot.zip at boot. Really running under safestrap (i'm using the /preinstall partition) does not seem to slow it down much. But tbh I havent really "run" it while it's booted I'm usally making edits and rebooting to check for service. I'm going to tear into hashcodes cm7 for the D3 and see what I can come up with. It seems like it had the kernel included but the scripts only called for it if the safe file existed on the /data partition.
lfaber06 said:
I have made quite a bit of progress on cm9 in safestrap, the only real issue i have is the radio which i am constantly trying different things with. I have not tried flashing cm9 or cm7 in the bootstrap but I have a method for it..(I think, Remember the D3 can run cm7 from the bootstrap) I have a file I have modified for cm9 that im sure will work for cm7 flashing in bootstrap. You would need to add some modified files to /system/rootfs/ and preinstall support to boot init.d and also run the fixboot.zip at boot. Really running under safestrap (i'm using the /preinstall partition) does not seem to slow it down much. But tbh I havent really "run" it while it's booted I'm usally making edits and rebooting to check for service. I'm going to tear into hashcodes cm7 for the D3 and see what I can come up with. It seems like it had the kernel included but the scripts only called for it if the safe file existed on the /data partition.
Click to expand...
Click to collapse
PM me a link to hashcodes d3 CM7 ported ROM (if you have one, I have had a hard time locating a completed one), and not the source code, that is what I used to compile my CM7 port with. I would like to test something, I have a theory on this, that I won't share with everyone here, since it really would not be very interesting here to anyone not trying to port these over.... we will talk more about this in PM.
Thanks!
Jim what about taking a look at the Droid X2, they have a alpha build of CM 7.2?
http://forum.xda-developers.com/showthread.php?t=1442803
JRW 28 said:
Jim what about taking a look at the Droid X2, they have a alpha build of CM 7.2?
http://forum.xda-developers.com/showthread.php?t=1442803
Click to expand...
Click to collapse
that is version 2.3.4 we are on 2.3.5 and we HAVE to use ports from 2.3.5 no way around it.
Missed that little details
CM9 does work when flash through bootstrap, I tried it the other day...
farshad525hou said:
CM9 does work when flash through bootstrap, I tried it the other day...
Click to expand...
Click to collapse
Care to share???? Plz.... it may be helpful.
Sent from my MB865 using Tapatalk
Yeah a couple days ago I flashed CM9 through Bootstrap. Everything booted okay and and everything ran fine. Again the only problems were that the phone didn't work, due to the telephony.apk issue and market wouldn't launch. Otherwise everything else ran a-okay!
farshad525hou said:
Yeah a couple days ago I flashed CM9 through Bootstrap. Everything booted okay and and everything ran fine. Again the only problems were that the phone didn't work, due to the telephony.apk issue and market wouldn't launch. Otherwise everything else ran a-okay!
Click to expand...
Click to collapse
Your right it does work but my ported verison does not!! That's actually good news BC now I know where to find the problem areas. Jim this has got to help you
Sent from my MB865 using Tapatalk
lfaber06 said:
Your right it does work but my ported verison does not!! That's actually good news BC now I know where to find the problem areas. Jim this has got to help you
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Yes it sure does thanks, I flashed it, played with it, and I am taking a look at a few things with your CM9 ROM, and since we PM'd I have been digging into the D3 CM7.2 version that hashcode had created. I am not quite ready to flash it yet, but maybe something tomorrow, once I have the ROM to the point that I am happy to play with it on my phone and see what works and what does not.
It looks like the issue with my old CM7 ROM, from the logs I grabbed a little while ago, with logcat, were due to kernel driver files not found during loading, so it looks like my compile had issues linking to our kernel. I so wish I had the source for our phones kernel, it would make compiling CM7 so much easier, and NO the ME865 source will not due, so don't mention it here.
Jim
Glad I could help! Also @lfaber06, what do you mean by your ported version doesn't work? That's the one I flashed.
**Edit** Also the camera doesn't work, if you guys want in to that. Probably an incorrect driver or something...
So... any news to report on either CM7 or CM9?
farshad525hou said:
So... any news to report on either CM7 or CM9?
Click to expand...
Click to collapse
By ported I mean the ones i've cooked up, their not ready for prime time so no sense in uploading them but they are good to share with jim. I don't think the camera works on any of the unofficial builds it uses a new type of "ion" driver that makes the camera uber responsive. Your post has however led me to build a few working ports for bootstrap but its still the same old radio driver issue.
lfaber06 said:
By ported I mean the ones i've cooked up, their not ready for prime time so no sense in uploading them but they are good to share with jim. I don't think the camera works on any of the unofficial builds it uses a new type of "ion" driver that makes the camera uber responsive. Your post has however led me to build a few working ports for bootstrap but its still the same old radio driver issue.
Click to expand...
Click to collapse
Cool Any ideas from what phone we can pull the radio drivers from? I'm assuming that it has to be a GSM phone running the TI's OMAP processor, that also has a CM9 port, right?
farshad525hou said:
Cool Any ideas from what phone we can pull the radio drivers from? I'm assuming that it has to be a GSM phone running the TI's OMAP processor, that also has a CM9 port, right?
Click to expand...
Click to collapse
Tbh, I have no idea... I have been looking at every moto phone google can find and so far I have had no luck. Call me crazy but I think our radio is more commonly found in sony's... (I'd welcome ANY input on the radio)
lfaber06 said:
Tbh, I have no idea... I have been looking at every moto phone google can find and so far I have had no luck. Call me crazy but I think our radio is more commonly found in sony's... (I'd welcome ANY input on the radio)
Click to expand...
Click to collapse
What exactly should I be looking for to find a phone with a similar radio? Here's a system dump for the xperia play, you could try pulling the telephony.apk... http://rapidshare.com/files/45600580..._Play_DUMP.rar Most of the sony's though run on Qualcomm's Snapdragon Processor
farshad525hou said:
What exactly should I be looking for to find a phone with a similar radio? Here's a system dump for the xperia play, you could try pulling the telephony.apk... http://rapidshare.com/files/45600580..._Play_DUMP.rar Most of the sony's though run on Qualcomm's Snapdragon Processor
Click to expand...
Click to collapse
That's the thing idk... I assumed that it was a Sony radio BC when I Google rlidu300-ril.so I get a device tree for a Sony. We need to know what radio we have then we can start checking sources.
Sent from my MB865 using Tapatalk
What would be involved in porting one of the Optimistic V (or other Optimistic One variants) really awesome ROMs to the LG Vortex (which is Verizion's version of the Optimums One) ?
My old Vortex is just sitting around and I wanna learn how to make ROMs. It can't be too hard to get a ROM working on it, the only difference is the radio, as far as I can tell, and that would be just replace some files, right?
So I'm hoping someone who knows a lil more than me can tell me what I need to change to make a ported ROM off someone's Optimistic One variant source.
ANYONE? not a hard question....
Not a hard question??? What do YOU think is involved. porting to a completely new phone AOSP or whatever is way harder than you think. You need to compile from source to get a fully working rom. I cannot do this but you should try first messing around. You don't even have CWM on the Vortex, so you should go and ask that first...
Sent from my LG-P500 using Tapatalk
You can port different kinds of Rom to your phone which are cdma-based.
If you use your stock kernel roms should boot (can't say anything about data/wifi/gsm)
If you want to build your own, look here for a base.
And don't forget to backup your rom! It has different libs you may need to use!
You can find CWM for your phone here!
You'll also find a CM7 for your phone to play with
Good luck!
Rores said:
Not a hard question??? What do YOU think is involved. porting to a completely new phone AOSP or whatever is way harder than you think. You need to compile from source to get a fully working rom. I cannot do this but you should try first messing around. You don't even have CWM on the Vortex, so you should go and ask that first...
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Actually, there is a custom recovery. And the hardware is identical to other optimus one variants, except for the radios. So there should be files that correspond to ththe radios that need to be replaced. Now I've never built a ROM before, just tinkered with one, but I don't expect it to be THAT hard to swap out a few files, maybe recompile the kernel.
_Arjen_ said:
You can port different kinds of Rom to your phone which are cdma-based.
If you use your stock kernel roms should boot (can't say anything about data/wifi/gsm)
If you want to build your own, look here for a base.
And don't forget to backup your rom! It has different libs you may need to use!
You can find CWM for your phone here!
You'll also find a CM7 for your phone to play with
Good luck!
Click to expand...
Click to collapse
There are several other CDMA Optimus One variants, I know they're available for sprint and virgin at least. If I keep the stock Verizon kernel how I change a sprint/virgin ROM to be compatible?
Its very easy, just go into the build.prop and change everything that calls for vm670 and change it to vs660 and do the same in the updater script. You'll be able to flash it and use it, but data, calling and sms wont work , you need to swap the telephony files from the same android version, I'm currently porting JB to the vortex
jacobmacek said:
Its very easy, just go into the build.prop and change everything that calls for vm670 and change it to vs660 and do the same in the updater script. You'll be able to flash it and use it, but data, calling and sms wont work , you need to swap the telephony files from the same android version, I'm currently porting JB to the vortex
Click to expand...
Click to collapse
Attempting to port this rom to the LG Vortex. Any advice?
So I found a tool on XDA that allows me to put the ROM of choice to be ported and the base ROM. I'm trying to port Paranoid Android 2.00 since we don't have it, and now that we have somewhat steady CM10 nightlies I *should* be able to use it as a base. (The tool is called RomPorter)
So I went ahead and compiled a ROM, but I'm not sure if I should flash. I mean if it was this easy to port ROM's wouldn't we have ROM's just popping up everywhere? I used the HTC One X International version's PA 2.00 as the input ROM btw. I have some coding experience in Java but if it's this easy to port without any coding required why hasn't it been done yet? Just curious. I looked at the CM9 guide to porting PA and I have to make a linux portal and all those things. Basically my main question is, will this work? I don't want to flash and end up hard bricking my phone. I went and checked the build.prop, and framework and it all seemed like a hybrid of CM10 nightly and Paranoid Android 2.00 but is there something I'm missing?
Thanks a lot guys! I'm tired of just being somebody who stands on the side and waits for things to get ported or created. I'm taking a heavy load in college but I want to try and port something at least to contribute.
Using the international base could cause a brick unless you ported an evita kernel too. The international one x has a different partition layout as well.
Read read read, check, double check and triple check. When your confident its possibly bootable, sure that it is not harmful THEN flash it to your device first. Ports are always going to start with bugs. Don't expect perfection, expect a WIP. Importantly, have fun learning. Most importantly , FIRST FLASH IS ALWAYS YOURS :beer::beer:
Added People port roms all the time for themselves. Now posting one on xda and maintaining a thread with dozens-hundreds of followers is a WHOLE DIFFERENT STORY
I just want to try it but I'm afraid it'll brick. I mean what's the worst case scenario? Boot loop then restore to my nandroid? Or being stuck with a brick forever? I don't have a backup phone at the moment lol. Maybe I should invest in one.
If you flash something that overwrites hboot you're hard bricked. That's what I meant by different partition layout.
Here's a easier start for jb paranoid Android port.....dload the HTC evo 4g lte jb paranoid port rom, unzip it, delete the included boot.img, use a hox boot.img from a hox jb rom to replace it with. Zip it and flash it.(use the one XL cm10 boot.img) It will give u a bootable port of jb paranoid Android. Then like most ports, you will start fixing bugs. Camera and wifi won't work, you will need to fix those for sure. But a lot will work so start with priority bug fix#1 and keep on goin
Added: paranoid android rom I would consider the land of the brave for first time porting. U may encounter fixes to be harder than some less modified roms.
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Shaddy-Z. said:
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Click to expand...
Click to collapse
make sure you pull out any radio images you find in the roms you look at.
Could I push the ones from a cm10 nightly?
No idea. Probably. Or just don't include one.
getting in contact with the developer for the Evo PA ROM. Hopefully this goes somewhere.
Don't we already have a pa rom? You've inspired me though. I'm going to look at porting roms too.
The PA ROM is still ICS, and the biggest killer is that the multi-touch fix is not incorporated because the ROM was cooked pre kernel release unfortunately. The latest update the dev was supposed to release didn't boot and I don't know what happened after that.
And do it! The more devs the better. I want some variety in this little community.
By the way, PARANOIDANDROID 2.00 is not out yet. The last OFFICIAL release is 1.992: Changelog. As for the port, I would love to port roms to our device, since it is my primary device.
I already port ROMs from the i9100 to i777(SGSII Internation to AT&T US Version), but this is a VERY simple operation. And you can use a pre-made program to port by ktoonsez called Flashaholics, but it is only for porting to the i777. I hope we eventually get that far but these 2 devices are far more similar that the One X/OneXL or Evo LTE/One XL.
Just use the latest paranoid rom with the latest cm10 boot.img. I did it a few times when I had my hox. And gunny is right. Either pull the radio or flash a hox radio after u flash ur port and u will get signal with working talk, text. 3g should work too, mms won't, streaming video will be iffy. Just run thru the major stuff, write down what's broken, prioritize it, then always make a nandroid of your previous build so u can revert back if fixes make things worse
---------- Post added at 01:09 AM ---------- Previous post was at 01:03 AM ----------
He's gonna work off a unofficial paranoidandroid jb 4.1 from the evo lte. It'll boot but there will be plenty of fixing to do. I think its for his use/learning, not sure if he plans on putting it up on forums
I don't plan on uploading it to the forums unless I get the features working. I'm off all day tomorrow so I'll probably give it a shot to see what I can do.
I also realized PA is not 2.00 after I posted that, buts its still a JB Paranoid ROM so it'll do for now while I learn.
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
stnguyen09 said:
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
Click to expand...
Click to collapse
Thanks! I appreciate it So I got a little ahead of myself and tried it tonight, I'm slowly following a guide and I THOUGHT I was doing everything correctly but it won't flash after "Verifying system partition size" and I got an error. This seems to be a common problem that leads to the updater script, so I'm going to take a look at it when I get up. Could just be a syntax error, or maybe I'm just building it wrong I'm kinda tired
U can always nab the updater script from cm10 hox also. Its been a while and I forgot to mention that. I had the same issue with the evo rooms and that did the trick:beer:
I tried: using the ports updater, the base, and a collaboration of the two and it still didn't go through. Maybe its something else ? I'll try it again to double check.
Perfect Android is a redistribution of the Android Open Source Project and Google software code that I have lightly modified to make as a daily driver for myself that I'm sharing with the community. This project doesn't have and won't focus on adding a ton of features and mods but instead focus on stability, and reliability so yes basically this is a stock like rom but not just stock my only efforts will be to make it run better, and be more polished, and complete.
GOOGLE APPS ARE INCLUDED
DOWNLOAD:
https://hotfile.com/dl/181925379/d84644d/perfect_grouper_ota_2012-12-01.zip.html
Mirrors:
If you have an error or something pops up I ask that before you post about it please make sure that you are running the ROM as provided. I cannot troubleshoot anything that is related to using other kernels, mods, or themes.
This ROM is basically like a stock rom of jelly bean so there is not a need for screen shots ........
Always remember that XDA started out as a great place and will remain a great place as long as we are great to each other anything used in this ROM is available upon request and feel free to use this as a base rom for any other project my ROM is un-branded just give me some mention .......
WANT TO CUSTOMIZE THIS ROM READ THIS:
Like the ROM and want to add or remove anything or customize for yourself use this http://forum.xda-developers.com/showthread.php?t=633246 DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs
CREDITS:
CyanogenMod Team
Google - I used their apps
AOSP - of course
Probably gonna add a changelog here
AOSP 4.2 ROM so quickly? That will be interesting
Can you have some screenshots?
yep its uploaded
it looks just like stock I built it to be at least as good as what you get from google if everything is working correctly that is when I will begin modifying but for now it looks like the stock ROM so I didn't think screenshots would be needed
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Patroy said:
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Click to expand...
Click to collapse
Its solely up to you guys if you want to flash it as this is an expensive hobby for me I'm just sharing what I do with the community so is it worth it, for me yeah, for you I really don't care, I hope I'm not coming off as an ass but I have to draw a line somewhere. I not making any claims with this ROM I just sharing it if you use it fine if not fine, I don't get into the whole screenshots large claims huge changelog thing I just post and share I also maintain this ROM for the Sprint Galaxy Nexus which it has done just fine so if you want you can do a search here and see what and where I come from .......
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
I will happily try your rom to see how it compares to CleanRom, give my feedback tomorrow
Patroy said:
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Click to expand...
Click to collapse
I'm not getting angry with you in fact I agree however, regardless of how you feel about those roms someone still put that effort into them. Honestly for me the N7 is a new device and before I go making claims that my ROM can start your car and end world hunger I want to make sure that it at least meets stock standards. AOSP has done a lot of work to somewhat remove google entries in their code so it has taken me a few days to re-build AOSP code to work correctly with G-APPS and other Google code I do NOT claim to be an over the top developer I just do this as a pastime I have certain things that I do not like and thats why I have started making my own ROMs so that I always get what I want. Now I can tell you this and I know this as a fact THIS IS NOT A WINZIP KITCHEN ROM IT IS BUILT FROM SOURCE it took hella work to get it up to a win zip ROM and thats where we're at so far lol. When I learn all the changes to the 4.2 coding I will start to add small feature to my ROM.
SuperBoUDS said:
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
Click to expand...
Click to collapse
yes it works with TWRP and the information in the About screen is correct
There isn't developer section in setting menu. Is this normal?
SuperBoUDS said:
There isn't developer section in setting menu. Is this normal?
Click to expand...
Click to collapse
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
PAULO76 said:
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
SuperBoUDS said:
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
Click to expand...
Click to collapse
lol who knows I might depends on how things go with this
Installed thid yesterday and so far no problems, nice deep sleep of 96%. Nice work
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
SuperBoUDS said:
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
Click to expand...
Click to collapse
haven't checked for myself but is leankernel updated for 4.2
Has anyone tweaked CROMi-X to be OpenPDroid compatible? Or is there any chance sbdags might be persuaded to bake it in? I'd prefer to stick with CROMi-X over CM 10.1, but really like the option of controlling individual app permissions.
http://forum.xda-developers.com/showthread.php?t=2098156
Without the Asus sources I can't see how this can be done easily as a lot of the framework is not stock google. Need to read more about it but it sounds like a lot of hard work. This bit scares me :
Currently we are not aware of any ROMs which include OpenPDroid: if you are aware of one, please notify us and we'll list it here.
Click to expand...
Click to collapse
sbdags said:
Without the Asus sources I can't see how this can be done easily as a lot of the framework is not stock google. Need to read more about it but it sounds like a lot of hard work. This bit scares me :
Click to expand...
Click to collapse
Thanks for at least taking a look. I didn't know how different the framework would be, but thought I'd put it out there.
I know I saw a list on one of the posts that did list some ROMs with it baked in, but the ones I remember being listed were mostly CM or AOSP based and so far typically for Nexus or Samsung devices.
I have run the OpenPDroid auto-patcher on a Slimbean (AOSP) port for my HTC Evo LTE. Everything works great on the phone after flashing the custom zip, and I was hoping to do the same with the tablet without having to go to Cyanogen. Guess I'll have to decide between some of the Asus features I like versus the ability to micromanage permissions.
APDRJRD said:
Thanks for at least taking a look. I didn't know how different the framework would be, but thought I'd put it out there.
I know I saw a list on one of the posts that did list some ROMs with it baked in, but the ones I remember being listed were mostly CM or AOSP based and so far typically for Nexus or Samsung devices.
I have run the OpenPDroid auto-patcher on a Slimbean (AOSP) port for my HTC Evo LTE. Everything works great on the phone after flashing the custom zip, and I was hoping to do the same with the tablet without having to go to Cyanogen. Guess I'll have to decide between some of the Asus features I like versus the ability to micromanage permissions.
Click to expand...
Click to collapse
You could try the auto patcher on cromi-x and let us know
Heh, unfortunately the auto-patcher only works on AOSP, AOKP, CM or PA based ROMs at the moment. It reads the build.prop of whatever ROM you want it to make the zip for and errors out with CROMi and the stock Asus build for the infinity. I wouldn't have troubled you if I hadn't already tried that
To anyone else interested in adding permission management to CROMi-X, Xprivacy appears to work and is pretty easy to install. No need for the autopatcher or special tweaks.
Here's where to go:
http://forum.xda-developers.com/showthread.php?t=2320783